Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.06338143348693848s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.24198246002197266s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.41089701652526855s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 0.00042247772216796875s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 7.3909759521484375e-06s
INFO | --- Analysis for 2000-us-census-rdf took 5.506179332733154s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 1.756265640258789s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.26946067810058594s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.01970076560974121s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 3.933906555175781e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 4.76837158203125e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 6.4071691036224365s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.3392181396484375e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.25827598571777344s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.019915342330932617s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 2.7894973754882812e-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 4.402042627334595s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.3561253547668457s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.00021529197692871094s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.272519588470459s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.0199277400970459s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 9.942054748535156e-05s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for abs-linked-data took 2.7749335765838623s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 3.981590270996094e-05s
Availability | VoID file availability check for Academic Offer of UNL took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.2689790725708008s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.019949913024902344s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 2.9087066650390625e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 7.152557373046875e-06s
INFO | --- Analysis for academic-offer-of-unl took 2.9824390411376953s
Availability | SPARQL endpoint availability check for AcadOnto took 4.2438507080078125e-05s
Availability | VoID file availability check for AcadOnto took 0.00031757354736328125s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.23517179489135742s
Reputation | Calculation of the PageRank for AcadOnto took 0.02006983757019043s
Interlinking | Calculation of Degree of Connection for AcadOnto took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 2.7179718017578125e-05s
Believability | Calculation of trust value for AcadOnto took 7.3909759521484375e-06s
INFO | --- Analysis for acadonto took 2.869856357574463s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.36491847038269s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.2753136157989502s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.020160913467407227s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007205009460449219s
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 9.298324584960938e-06s
INFO | --- Analysis for acorn-sat took 35.77167582511902s
Availability | SPARQL endpoint availability check for Addgene took 4.2438507080078125e-05s
Availability | VoID file availability check for Addgene took 0.0008103847503662109s
Completeness | Calculation of interlinking completeness for Addgene took 0.2574951648712158s
Reputation | Calculation of the PageRank for Addgene took 0.019983291625976562s
Interlinking | Calculation of Degree of Connection for Addgene took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.719329833984375e-05s
Believability | Calculation of trust value for Addgene took 1.2636184692382812e-05s
INFO | --- Analysis for addgene took 17.092206716537476s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.4345855712890625e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0007703304290771484s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.2584371566772461s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.02004718780517578s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.202957153320312e-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.022748470306396s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.6101961135864258s
Availability | VoID file availability check for AEMET metereological dataset took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.26807165145874023s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.01999068260192871s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.5762786865234375e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 8.58306884765625e-06s
INFO | --- Analysis for aemet took 4.896761178970337s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 4.0531158447265625e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.00022530555725097656s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.2696397304534912s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.02011728286743164s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 3.0517578125e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 6.67572021484375e-06s
INFO | --- Analysis for agenda-de-zaragoza took 2.921462059020996s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.032506704330444336s
Availability | VoID file availability check for AgriNepalData took 0.00037360191345214844s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.2678186893463135s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020209074020385742s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 7.05718994140625e-05s
Believability | Calculation of trust value for AgriNepalData took 6.9141387939453125e-06s
INFO | --- Analysis for agrinepaldata took 2.479207754135132s
Availability | SPARQL endpoint availability check for AGRIS took 262.055734872818s
Availability | VoID file availability check for AGRIS took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for AGRIS took 0.3320915699005127s
Reputation | Calculation of the PageRank for AGRIS took 0.02039480209350586s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for AGRIS took 7.939338684082031e-05s
Believability | Calculation of trust value for AGRIS took 6.67572021484375e-06s
INFO | --- Analysis for agris took 557.1934065818787s
Availability | SPARQL endpoint availability check for AGROVOC took 5.602836608886719e-05s
Availability | VoID file availability check for AGROVOC took 0.00028324127197265625s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.250413179397583s
Reputation | Calculation of the PageRank for AGROVOC took 0.020404577255249023s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 5.936622619628906e-05s
Believability | Calculation of trust value for AGROVOC took 6.198883056640625e-06s
INFO | --- Analysis for agrovoc-skos took 3.4535326957702637s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 4.935264587402344e-05s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.26352524757385254s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.02013421058654785s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 2.86102294921875e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 8.344650268554688e-06s
INFO | --- Analysis for aksworg took 4.365392446517944s
Availability | SPARQL endpoint availability check for AlchemyAPI took 4.506111145019531e-05s
Availability | VoID file availability check for AlchemyAPI took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.2826671600341797s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.020203351974487305s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 2.8371810913085938e-05s
Believability | Calculation of trust value for AlchemyAPI took 8.106231689453125e-06s
INFO | --- Analysis for alchemyapi took 3.814657211303711s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 4.1484832763671875e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.2588987350463867s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.020027637481689453s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 2.8371810913085938e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 6.9141387939453125e-06s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 3.0017852783203125s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.129643440246582s
Availability | VoID file availability check for aliada-scanbit-net took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.26749730110168457s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.020322322845458984s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00011157989501953125s
Believability | Calculation of trust value for aliada-scanbit-net took 7.62939453125e-06s
INFO | --- Analysis for aliada-scanbit-net took 4.812502384185791s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 4.3392181396484375e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.26143574714660645s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.02030658721923828s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 3.0040740966796875e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 5.7220458984375e-06s
INFO | --- Analysis for allen-brain-atlas took 2.944185495376587s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 0.7426793575286865s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0006682872772216797s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 138.57162499427795s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.7241904735565186s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.4581031799316406s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.6742312908172607s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.0550129413605s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 4.283537864685059s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8943192958831787s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.7117753028869629s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.6586577892303467s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.6974406242370605s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.6536717414855957s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 34.630653858184814s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.5641398429870605s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.8715827465057373s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.1169097423553467s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.6470444202423096s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.6459329128265381s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.6458420753479004s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.825629472732544s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 7.462501525878906e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.6301400661468506s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.5732231140136719s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6001279354095459s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5579609870910645s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.6743626594543457s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.1328165531158447s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.1419198513031006s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 55.08041787147522s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5712888240814209s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6350288391113281s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6045141220092773s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 34.95241928100586s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.090714454650879s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.729031801223755s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.6126289367675781s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 10.957621812820435s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.93015193939209s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 31.507125854492188s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.3912575244903564s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.829248428344727s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.7603631019592285s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8321740627288818s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.5709702968597412s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 12302.202474832535s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 1.0641403198242188s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.02219104766845703s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 8.96453857421875e-05s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 8.58306884765625e-06s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 13053.071689367294s
Availability | SPARQL endpoint availability check for Alojamientos took 4.1961669921875e-05s
Availability | VoID file availability check for Alojamientos took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.6953387260437012s
Reputation | Calculation of the PageRank for Alojamientos took 0.02033853530883789s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 3.0994415283203125e-05s
Believability | Calculation of trust value for Alojamientos took 7.867813110351562e-06s
INFO | --- Analysis for alojamientos-zaragoza took 5.611284971237183s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.41033458709716797s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0005660057067871094s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.2356858253479004s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.020023107528686523s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.62396240234375e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 7.62939453125e-06s
INFO | --- Analysis for alpino-rdf took 3.9168431758880615s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 4.0531158447265625e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.2752084732055664s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.02001953125s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 2.8371810913085938e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 7.3909759521484375e-06s
INFO | --- Analysis for am-collections-online took 3.360297203063965s
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.0002579689025878906s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.26529932022094727s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.020373821258544922s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 2.8848648071289062e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 8.106231689453125e-06s
INFO | --- Analysis for amon took 2.9150311946868896s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.7629556655883789s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.29558324813842773s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.020228862762451172s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.369850158691406e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.0013580322265625e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 4.221220970153809s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 4.076957702636719e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.2782149314880371s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.020508766174316406s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 2.8848648071289062e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 7.3909759521484375e-06s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 2.954785108566284s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 4.029273986816406e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.27402615547180176s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.02028965950012207s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 2.8133392333984375e-05s
Believability | Calculation of trust value for Animal Diversity Web took 8.106231689453125e-06s
INFO | --- Analysis for animal-diversity-web took 2.9216127395629883s
Availability | SPARQL endpoint availability check for apache took 4.3392181396484375e-05s
Availability | VoID file availability check for apache took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for apache took 0.268460750579834s
Reputation | Calculation of the PageRank for apache took 0.020217180252075195s
Interlinking | Calculation of Degree of Connection for apache took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for apache took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for apache took 5.4836273193359375e-05s
Believability | Calculation of trust value for apache took 7.3909759521484375e-06s
INFO | --- Analysis for apache took 3.362377405166626s
Availability | SPARQL endpoint availability check for Apertium RDF took 0.00010061264038085938s
Availability | VoID file availability check for Apertium RDF took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.2883603572845459s
Reputation | Calculation of the PageRank for Apertium RDF took 0.02039027214050293s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf took 6.184678792953491s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0011184215545654297s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.25542211532592773s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.02053356170654297s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-ca-it took 5.827529668807983s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 4.291534423828125e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0007038116455078125s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.2628607749938965s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.020496368408203125s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-en-ca took 5.702295303344727s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.28441357612609863s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.02038860321044922s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.220008850097656e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-en-es took 6.011398792266846s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0006339550018310547s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.26090502738952637s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0009801387786865234s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 5.173683166503906e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-en-gl took 5.4879677295684814s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 4.291534423828125e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.2799084186553955s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.020162105560302734s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 6.127357482910156e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.615057945251465s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.2753727436065674s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.02021956443786621s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.1961669921875e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-eo-en took 6.430820465087891s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.26944780349731445s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.020245075225830078s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.1484832763671875e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-eo-es took 5.5212562084198s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 4.482269287109375e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.2652742862701416s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.020365238189697266s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.000858306884765625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.649162292480469e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.674266576766968s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 9.679794311523438e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.2778010368347168s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.020512819290161133s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.6253204345703125e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 8.58306884765625e-06s
INFO | --- Analysis for apertium-rdf-es-an took 5.604032754898071s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 6.985664367675781e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.2684977054595947s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.020709514617919922s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.553794860839844e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-es-ast took 5.6057655811309814s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 4.5299530029296875e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.26516222953796387s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020339250564575195s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 5.1975250244140625e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 8.344650268554688e-06s
INFO | --- Analysis for apertium-rdf-es-ca took 24.874332666397095s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.57763671875e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.2581348419189453s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.020719289779663086s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0011477470397949219s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 5.6743621826171875e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 8.344650268554688e-06s
INFO | --- Analysis for apertium-rdf-es-gl took 5.476621627807617s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 4.506111145019531e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0007014274597167969s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.25418853759765625s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.020051240921020508s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.38690185546875e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 5.604992866516113s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 4.410743713378906e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0013403892517089844s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.2947702407836914s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.02026224136352539s
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.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-es-ro took 6.6118128299713135s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 4.458427429199219e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.27354860305786133s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.019995927810668945s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.1961669921875e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-eu-en took 7.104577541351318s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 4.267692565917969e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0003361701965332031s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.26081275939941406s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.020299911499023438s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.220008850097656e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-eu-es took 7.122445821762085s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.26432132720947266s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.020178794860839844s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.172325134277344e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.503382444381714s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.2733585834503174s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020244836807250977s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.52587890625e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 5.456588268280029s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.24694204330444336s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.020689725875854492s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.8160552978515625e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.5263824462890625s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.2531166076660156s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.02055048942565918s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.410743713378906e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-oc-es took 5.634422302246094s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.267692565917969e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.26508665084838867s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.020250797271728516s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-pt-ca took 5.623599529266357s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 4.291534423828125e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.29230523109436035s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.020181655883789062s
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.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.744529724121094e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.527063846588135s
Availability | SPARQL endpoint availability check for AragoDBPedia took 2.0241284370422363s
Availability | VoID file availability check for AragoDBPedia took 0.0006642341613769531s
Extra | Recovery of all triples for AragoDBPedia took 3.603144407272339s
Performance | Total latancy measurement for AragoDBPedia took 1.8725471496582031s
Amount of data | Number of triples check for AragoDBPedia took 0.7452702522277832s
Interoperability | New terms check for AragoDBPedia took 2.159714698791504s
Versatility | Languages check for AragoDBPedia took 60.50471353530884s
Interpretability | Number of blank nodes check for AragoDBPedia took 6.7038633823394775s
Security | Check HTTPS for AragoDBPedia took 0.2750093936920166s
Interpretability | RDF structures check for AragoDBPedia took 1.397564172744751s
Versatility | Serialization formats check for AragoDBPedia took 1.5250706672668457s
Availability | RDF dump link check for AragoDBPedia took 0.459125280380249s
License | MR license check for AragoDBPedia took 1.1414835453033447s
License | HR license check for AragoDBPedia took 8.287192821502686s
Amount of data | Number of property check for AragoDBPedia took 0.3881685733795166s
Understandability | Number of label check for AragoDBPedia took 0.882366418838501s
Understandability | URI regex check for AragoDBPedia took 1.1245677471160889s
Understandability | Vocabs check for AragoDBPedia took 0.5011780261993408s
Verifiability | Authors check for AragoDBPedia took 0.5883851051330566s
Verifiability | Publishers check for AragoDBPedia took 0.39014768600463867s
Performance | Throughput check for AragoDBPedia took 11.635787010192871s
Amount of data | Check the number of entities for AragoDBPedia took 3.1948089599609375e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.6168646812438965s
Interlinking | sameAs chians check for AragoDBPedia took 0.5242695808410645s
Interlinking | skos check for AragoDBPedia took 0.8620586395263672s
Interlinking | skos check for AragoDBPedia took 0.39165282249450684s
Timeliness | dataset update frequency check for AragoDBPedia took 1.1032764911651611s
Currency | Creation date check for AragoDBPedia took 2.2163290977478027s
Currency | Modification date check for AragoDBPedia took 0.8441181182861328s
Rep.Conc. | URIs length for AragoDBPedia took 6.015606164932251s
Interoperability | New vocabularies check for AragoDBPedia took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.42493224143981934s
Accuracy | Check Functional Property for AragoDBPedia took 0.6124782562255859s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.641873836517334s
Accuracy | Check Empty annotation labels for AragoDBPedia took 1.3390014171600342s
Accuracy | Check White space in annotation for AragoDBPedia took 0.030127525329589844s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.02699899673461914s
Consistency | Disjoint class check for AragoDBPedia took 0.3676798343658447s
Consistency | Check Misplaced properties for AragoDBPedia took 4.785840034484863s
Consistency | Misplaced classes for AragoDBPedia took 0.6581039428710938s
Consistency | Check Ontology hijacking for AragoDBPedia took 2.8931655883789062s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.3380062580108643s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 5.595931529998779s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.0325469970703125s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.598027229309082s
Security | Sign check for AragoDBPedia took 1.1353938579559326s
Availability | Check URIs Dereferenciability for AragoDBPedia took 3475.733957052231s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 1.5263581275939941s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.021208763122558594s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 5.7697296142578125e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.430511474609375e-06s
Believability | Calculation of trust value for AragoDBPedia took 6.198883056640625e-06s
INFO | --- Analysis for aragodbpedia took 12491.99507689476s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.117355823516846s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0007228851318359375s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.2822842597961426s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.020498275756835938s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 4.9591064453125e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for archiveshub-linkeddata took 83.6913948059082s
Availability | SPARQL endpoint availability check for Archivi ISMA took 4.172325134277344e-05s
Availability | VoID file availability check for Archivi ISMA took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.25318145751953125s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.02028346061706543s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 2.9325485229492188e-05s
Believability | Calculation of trust value for Archivi ISMA took 8.344650268554688e-06s
INFO | --- Analysis for archivio-isma took 4.698678016662598s
Availability | SPARQL endpoint availability check for ARIADNE took 4.1961669921875e-05s
Availability | VoID file availability check for ARIADNE took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.7259171009063721s
Reputation | Calculation of the PageRank for ARIADNE took 0.02031564712524414s
Interlinking | Calculation of Degree of Connection for ARIADNE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ARIADNE took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 3.0279159545898438e-05s
Believability | Calculation of trust value for ARIADNE took 8.106231689453125e-06s
INFO | --- Analysis for ariadne took 4.377716064453125s
Availability | SPARQL endpoint availability check for Aristotle University took 4.124641418457031e-05s
Availability | VoID file availability check for Aristotle University took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.2638676166534424s
Reputation | Calculation of the PageRank for Aristotle University took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for Aristotle University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Aristotle University took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 3.170967102050781e-05s
Believability | Calculation of trust value for Aristotle University took 7.62939453125e-06s
INFO | --- Analysis for aristotle-university took 2.9075348377227783s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 4.841149806976318s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.26465702056884766s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.020836830139160156s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0009248256683349609s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 3.4332275390625e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 8.58306884765625e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 20.22213101387024s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.1961669921875e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.00041604042053222656s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.26752710342407227s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.02015852928161621s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 3.147125244140625e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 7.867813110351562e-06s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 2.9084465503692627s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.892887592315674s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.2616720199584961s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.02027726173400879s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.814697265625e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 7.867813110351562e-06s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 16.591379404067993s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 5.030632019042969e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007598400115966797s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.25847721099853516s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.02022075653076172s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0001010894775390625s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 7.3909759521484375e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 9.429022073745728s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.363059997558594e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.2627065181732178s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.02095627784729004s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.000110626220703125s
Believability | Calculation of trust value for Arthroscopy community took 8.58306884765625e-06s
INFO | --- Analysis for arthroscopy took 33.007715940475464s
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.0006244182586669922s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.26967573165893555s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.02057194709777832s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 7.104873657226562e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 8.58306884765625e-06s
INFO | --- Analysis for asit took 8.011175155639648s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.363059997558594e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.28319764137268066s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 3.910064697265625e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 7.62939453125e-06s
INFO | --- Analysis for asjp took 4.788866996765137s
Availability | SPARQL endpoint availability check for ASN:US took 2.3189609050750732s
Availability | VoID file availability check for ASN:US took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for ASN:US took 0.25844478607177734s
Reputation | Calculation of the PageRank for ASN:US took 0.020301103591918945s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for ASN:US took 7.009506225585938e-05s
Believability | Calculation of trust value for ASN:US took 5.0067901611328125e-06s
INFO | --- Analysis for asn-us took 12.812950372695923s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.38690185546875e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.25861072540283203s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.021956205368041992s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0008392333984375s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.4809112548828125e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 5.9604644775390625e-06s
INFO | --- Analysis for aspire-mmu took 4.6047327518463135s
Availability | SPARQL endpoint availability check for associations took 4.315376281738281e-05s
Availability | VoID file availability check for associations took 0.0008153915405273438s
Completeness | Calculation of interlinking completeness for associations took 0.2708747386932373s
Reputation | Calculation of the PageRank for associations took 0.020399093627929688s
Interlinking | Calculation of Degree of Connection for associations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for associations took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for associations took 7.510185241699219e-05s
Believability | Calculation of trust value for associations took 8.821487426757812e-06s
INFO | --- Analysis for associations took 7.478653192520142s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 4.267692565917969e-05s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.00029587745666503906s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.2550063133239746s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 2.9802322387695312e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 7.62939453125e-06s
INFO | --- Analysis for atc-publikovan--s-kl took 2.938213348388672s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 4.315376281738281e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.28942155838012695s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.020166397094726562s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 8.988380432128906e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.2636184692382812e-05s
INFO | --- Analysis for athelia-rfid took 5.177109479904175s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 4.1961669921875e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.2596113681793213s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.020888090133666992s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 3.337860107421875e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 1.049041748046875e-05s
INFO | --- Analysis for aueb-linked-open-data took 3.380258560180664s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.5854911804199219s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.28162217140197754s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.02040696144104004s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007338523864746094s
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 6.9141387939453125e-06s
INFO | --- Analysis for austrian_ski_racers took 3.778836727142334s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2894930839538574s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0005850791931152344s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 194.21515798568726s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.7892265319824219s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0760974884033s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 188.39835000038147s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.08423352241516s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0929651260376s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.23281049728393555s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14522886276245117s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11781501770019531s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09464859962463379s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 52.65183639526367s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.03157901763916s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1161196231842041s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 211.81793904304504s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2532367706298828s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09654951095581055s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09980368614196777s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12372159957885742s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.456284523010254s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.177757263183594e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10426831245422363s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.07688903808594s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14591431617736816s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1305711269378662s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12092161178588867s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.23154640197753906s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2348008155822754s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 364.85737323760986s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13497328758239746s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.94344186782837s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.2216737270355225s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.730482339859009s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12776446342468262s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1937208175659s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 101.26308369636536s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.334007978439331s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.56316924095154s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.837284803390503s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15499019622802734s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.0956475734710693s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.7450735569000244s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.021055221557617188s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.343292236328125e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.6689300537109375e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 5.4836273193359375e-06s
INFO | --- Analysis for b3kat took 3881.302993774414s
Availability | SPARQL endpoint availability check for BabelNet took 0.547879695892334s
Availability | VoID file availability check for BabelNet took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for BabelNet took 0.2732276916503906s
Reputation | Calculation of the PageRank for BabelNet took 0.02075982093811035s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.0001766681671142578s
Believability | Calculation of trust value for BabelNet took 8.344650268554688e-06s
INFO | --- Analysis for babelnet took 6.135332345962524s
Availability | SPARQL endpoint availability check for BAMS took 4.315376281738281e-05s
Availability | VoID file availability check for BAMS took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for BAMS took 0.29099035263061523s
Reputation | Calculation of the PageRank for BAMS took 0.020798683166503906s
Interlinking | Calculation of Degree of Connection for BAMS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for BAMS took 3.123283386230469e-05s
Believability | Calculation of trust value for BAMS took 7.152557373046875e-06s
INFO | --- Analysis for bams took 3.004801034927368s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 4.482269287109375e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.28029417991638184s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.020625591278076172s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.2438507080078125e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 8.58306884765625e-06s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 3.4295928478240967s
Availability | SPARQL endpoint availability check for BBC Music took 0.2902243137359619s
Availability | VoID file availability check for BBC Music took 0.000690460205078125s
Completeness | Calculation of interlinking completeness for BBC Music took 0.2790679931640625s
Reputation | Calculation of the PageRank for BBC Music took 0.020557880401611328s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00012922286987304688s
Believability | Calculation of trust value for BBC Music took 7.3909759521484375e-06s
INFO | --- Analysis for bbc-music took 3.9439949989318848s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.2608325481414795s
Availability | VoID file availability check for BBC Programmes took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.2728288173675537s
Reputation | Calculation of the PageRank for BBC Programmes took 0.02064371109008789s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010347366333007812s
Believability | Calculation of trust value for BBC Programmes took 7.62939453125e-06s
INFO | --- Analysis for bbc-programmes took 10.287845373153687s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.20006060600280762s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0003857612609863281s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.29146504402160645s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.02054452896118164s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.000102996826171875s
Believability | Calculation of trust value for BBC Wildlife Finder took 6.9141387939453125e-06s
INFO | --- Analysis for bbc-wildlife-finder took 9.166519165039062s
Availability | SPARQL endpoint availability check for BBOP took 4.267692565917969e-05s
Availability | VoID file availability check for BBOP took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for BBOP took 0.28517723083496094s
Reputation | Calculation of the PageRank for BBOP took 0.020833492279052734s
Interlinking | Calculation of Degree of Connection for BBOP took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.24249267578125e-05s
Believability | Calculation of trust value for BBOP took 1.621246337890625e-05s
INFO | --- Analysis for bbop took 2.9273183345794678s
Availability | SPARQL endpoint availability check for BBOP took 4.458427429199219e-05s
Availability | VoID file availability check for BBOP took 0.0007987022399902344s
Completeness | Calculation of interlinking completeness for BBOP took 0.26886439323425293s
Reputation | Calculation of the PageRank for BBOP took 0.020816326141357422s
Interlinking | Calculation of Degree of Connection for BBOP took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BBOP took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.4809112548828125e-05s
Believability | Calculation of trust value for BBOP took 6.67572021484375e-06s
INFO | --- Analysis for bbop-selected took 20.544591426849365s
Availability | SPARQL endpoint availability check for Bdgp took 1.5039091110229492s
Availability | VoID file availability check for Bdgp took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for Bdgp took 0.2870051860809326s
Reputation | Calculation of the PageRank for Bdgp took 0.0205230712890625s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.123283386230469e-05s
Believability | Calculation of trust value for Bdgp took 8.58306884765625e-06s
INFO | --- Analysis for bdgp took 8.675315856933594s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 0.14988946914672852s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.2842283248901367s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.02049565315246582s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.842613220214844e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 5.7220458984375e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 2.7747323513031006s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 4.100799560546875e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.271573543548584s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.020368337631225586s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 3.0040740966796875e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 7.152557373046875e-06s
INFO | --- Analysis for berlin-offener-haushalt took 3.3523268699645996s
Availability | SPARQL endpoint availability check for berlios took 4.315376281738281e-05s
Availability | VoID file availability check for berlios took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for berlios took 0.2553520202636719s
Reputation | Calculation of the PageRank for berlios took 0.02026200294494629s
Interlinking | Calculation of Degree of Connection for berlios took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for berlios took 9.870529174804688e-05s
Believability | Calculation of trust value for berlios took 7.62939453125e-06s
INFO | --- Analysis for berlios took 2.750614881515503s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.45720911026000977s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.25351643562316895s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.020404338836669922s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 8.7738037109375e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for bfs-linked-data took 3.0208144187927246s
Availability | SPARQL endpoint availability check for BibBase took 0.07528924942016602s
Availability | VoID file availability check for BibBase took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for BibBase took 0.2814817428588867s
Reputation | Calculation of the PageRank for BibBase took 0.020568132400512695s
Interlinking | Calculation of Degree of Connection for BibBase took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.918212890625e-05s
Believability | Calculation of trust value for BibBase took 7.152557373046875e-06s
INFO | --- Analysis for bibbase took 2.5938355922698975s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 4.38690185546875e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.28142762184143066s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.020351648330688477s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.00010013580322265625s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 1.2159347534179688e-05s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 8.290456771850586s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 4.363059997558594e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.2728993892669678s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.02074122428894043s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 9.870529174804688e-05s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 6.9141387939453125e-06s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 8.263062000274658s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 4.1961669921875e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.27648067474365234s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.020627498626708984s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.147125244140625e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 9.775161743164062e-06s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 2.907329797744751s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 4.553794860839844e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0007619857788085938s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.29379868507385254s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.020816564559936523s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0009431838989257812s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.600120544433594e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 8.821487426757812e-06s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 4.792178630828857s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 4.267692565917969e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.27262091636657715s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.020281553268432617s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.24249267578125e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 8.821487426757812e-06s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.639263153076172s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 4.267692565917969e-05s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.2824888229370117s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.021245956420898438s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 3.2901763916015625e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-acfsid took 2.908822536468506s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 1.9558424949645996s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0005838871002197266s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 20.718868494033813s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.5081722736358643s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 44.26257610321045s
Interoperability | New terms check for Bio2RDF::Affymetrix took 47.980244398117065s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.12854623794556s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.1341710090637207s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.5203299522399902s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.22582626342773438s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 0.2646157741546631s
License | MR license check for Bio2RDF::Affymetrix took 0.37555885314941406s
License | HR license check for Bio2RDF::Affymetrix took 60.095651149749756s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.15021181106567383s
Understandability | Number of label check for Bio2RDF::Affymetrix took 9.855528116226196s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.43003058433532715s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.13716578483581543s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.13787198066711426s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.14057278633117676s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.735309362411499s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 76.08470702171326s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.5928394794464111s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.2212543487548828s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.6838028430938721s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.2829296588897705s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.13243794441223145s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.2717711925506592s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.23952937126159668s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 113.5026364326477s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.34896230697631836s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.16143584251403809s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.13569188117980957s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 7.052272081375122s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.9045214653015137s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6538064479827881s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.31154680252075195s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 64.94309973716736s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.238176107406616s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.74076771736145s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.2911787033081055s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.37890386581421s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.7085323333740234s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.31354403495788574s
Security | Sign check for Bio2RDF::Affymetrix took 0.12274694442749023s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 12.06022047996521s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.8750793933868408s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020369291305541992s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 9.1552734375e-05s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-affymetrix took 1009.489226102829s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.5155496597290039s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.000606536865234375s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 19.443861722946167s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.2317922115325928s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 43.68380832672119s
Interoperability | New terms check for Bio2RDF::Biomodels took 41.47535705566406s
Versatility | Languages check for Bio2RDF::Biomodels took 60.23750042915344s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.2625160217285156s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.16727662086486816s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.7115845680236816s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.33919548988342285s
Availability | RDF dump link check for Bio2RDF::Biomodels took 0.29283642768859863s
License | MR license check for Bio2RDF::Biomodels took 0.5816161632537842s
License | HR license check for Bio2RDF::Biomodels took 60.260507345199585s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.2566337585449219s
Understandability | Number of label check for Bio2RDF::Biomodels took 9.852135419845581s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5584757328033447s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.2897365093231201s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.2717399597167969s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.27881622314453125s
Performance | Throughput check for Bio2RDF::Biomodels took 11.068529605865479s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 74.46736240386963s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 0.591794490814209s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.4163787364959717s
Interlinking | skos check for Bio2RDF::Biomodels took 1.1128370761871338s
Interlinking | skos check for Bio2RDF::Biomodels took 0.39996957778930664s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.2790191173553467s
Currency | Creation date check for Bio2RDF::Biomodels took 0.5284328460693359s
Currency | Modification date check for Bio2RDF::Biomodels took 0.5028376579284668s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 110.45988821983337s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.4163475036621094s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.28989171981811523s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.2872157096862793s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 7.465391397476196s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.8977575302124023s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6592700481414795s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.47848963737487793s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.36828851699829s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.391634702682495s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 6.492081880569458s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.2871572971343994s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.5748393535614s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.6970663070678711s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.414156436920166s
Security | Sign check for Bio2RDF::Biomodels took 0.27385878562927246s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 11.65102219581604s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.9728751182556152s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.02041482925415039s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00011587142944335938s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-biomodels took 1004.5846858024597s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.25143909454345703s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.020702362060546875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.00081634521484375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.218650817871094e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 4.14485239982605s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 1.2771286964416504s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0006139278411865234s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 19.5352566242218s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.2960896492004395s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 44.08489632606506s
Interoperability | New terms check for Bio2RDF::Bioportal took 41.8781361579895s
Versatility | Languages check for Bio2RDF::Bioportal took 60.242703914642334s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.2647831439971924s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.15542173385620117s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 1.0129063129425049s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.31833577156066895s
Availability | RDF dump link check for Bio2RDF::Bioportal took 0.3086979389190674s
License | MR license check for Bio2RDF::Bioportal took 0.7159221172332764s
License | HR license check for Bio2RDF::Bioportal took 60.246779441833496s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.2592015266418457s
Understandability | Number of label check for Bio2RDF::Bioportal took 10.77007246017456s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.5759735107421875s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.2581942081451416s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.25107550621032715s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.25304555892944336s
Performance | Throughput check for Bio2RDF::Bioportal took 11.250831365585327s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 79.82485604286194s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.7491240501403809s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.35649824142456055s
Interlinking | skos check for Bio2RDF::Bioportal took 1.0444998741149902s
Interlinking | skos check for Bio2RDF::Bioportal took 0.35161352157592773s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.28620219230651855s
Currency | Creation date check for Bio2RDF::Bioportal took 0.5327255725860596s
Currency | Modification date check for Bio2RDF::Bioportal took 0.5143640041351318s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 111.77557635307312s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.4500408172607422s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.28290510177612305s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.2848019599914551s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 7.474102020263672s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.9074816703796387s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6947500705718994s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.2862858772277832s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 65.66061854362488s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.4324533939361572s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.265974998474121s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.276517391204834s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.508713722229004s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7302742004394531s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.4061264991760254s
Security | Sign check for Bio2RDF::Bioportal took 0.2738957405090332s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 11.925355911254883s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.9091532230377197s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.021925926208496094s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004279613494873047s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-bioportal took 1023.0226819515228s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.1388707160949707s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.27468395233154297s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.020302534103393555s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 6.008148193359375e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 9.059906005859375e-06s
INFO | --- Analysis for bio2rdf-chembl took 17.89564061164856s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.47777557373046875s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0006098747253417969s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 19.82708501815796s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.2997610569000244s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 43.85773801803589s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 41.601505517959595s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.234445333480835s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.262540340423584s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.15515518188476562s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.707313060760498s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.29274725914001465s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 0.303084135055542s
License | MR license check for Bio2RDF::Clinicaltrials took 0.5681424140930176s
License | HR license check for Bio2RDF::Clinicaltrials took 60.260849714279175s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.2541313171386719s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 10.833630561828613s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.5812728404998779s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.26725077629089355s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.24577045440673828s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.2595815658569336s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 11.48119306564331s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 79.06913232803345s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.6057906150817871s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.3659932613372803s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.8678989410400391s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.3854680061340332s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.27797484397888184s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.52213454246521s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.5233290195465088s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 109.95763349533081s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.45047760009765625s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.28879237174987793s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.30306339263916016s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 7.414059638977051s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.9075837135314941s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6686539649963379s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.43189334869384766s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 65.51515102386475s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.370164632797241s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 6.362731218338013s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.2822341918945312s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.50507307052612s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.6935689449310303s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.40419697761535645s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.25639915466308594s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 11.59368634223938s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.7021372318267822s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.02054595947265625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 5.412101745605469e-05s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1011.2539601325989s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 1.2560877799987793s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0007598400115966797s
Extra | Recovery of all triples for Bio2RDF::Ctd took 19.049915552139282s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.3003716468811035s
Amount of data | Number of triples check for Bio2RDF::Ctd took 44.20333170890808s
Interoperability | New terms check for Bio2RDF::Ctd took 42.110307931900024s
Versatility | Languages check for Bio2RDF::Ctd took 60.235443353652954s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.2741363048553467s
Security | Check HTTPS for Bio2RDF::Ctd took 0.1438753604888916s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.5927271842956543s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.3310708999633789s
Availability | RDF dump link check for Bio2RDF::Ctd took 0.3074357509613037s
License | MR license check for Bio2RDF::Ctd took 0.5246295928955078s
License | HR license check for Bio2RDF::Ctd took 60.25161409378052s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.2635807991027832s
Understandability | Number of label check for Bio2RDF::Ctd took 10.001391410827637s
Understandability | URI regex check for Bio2RDF::Ctd took 0.5771946907043457s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.2515740394592285s
Verifiability | Authors check for Bio2RDF::Ctd took 0.2784767150878906s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.25513696670532227s
Performance | Throughput check for Bio2RDF::Ctd took 11.010862112045288s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 72.93363285064697s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.595975399017334s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.35278749465942383s
Interlinking | skos check for Bio2RDF::Ctd took 0.8191380500793457s
Interlinking | skos check for Bio2RDF::Ctd took 0.3521721363067627s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.2810633182525635s
Currency | Creation date check for Bio2RDF::Ctd took 0.5082576274871826s
Currency | Modification date check for Bio2RDF::Ctd took 0.5142714977264404s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 111.94366693496704s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.4034404754638672s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.273423433303833s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.259537935256958s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 6.812024831771851s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8958539962768555s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6772148609161377s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.28572916984558105s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.18871641159058s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.396591901779175s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.199204444885254s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.3261077404022217s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.58558130264282s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.7017338275909424s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.42920804023742676s
Security | Sign check for Bio2RDF::Ctd took 0.27520012855529785s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 11.814574718475342s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.40213751792907715s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.020937442779541016s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.914138793945312e-05s
Believability | Calculation of trust value for Bio2RDF::Ctd took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-ctd took 1011.1273698806763s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 7.009506225585938e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0007250308990478516s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.25219011306762695s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.020462512969970703s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 5.030632019042969e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-dataset took 5.252693176269531s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.4488213062286377s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0005671977996826172s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 20.261284351348877s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.2644448280334473s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 43.54868531227112s
Interoperability | New terms check for Bio2RDF::Dbsnp took 40.72010684013367s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.23365306854248s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.24779963493347168s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.1666855812072754s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.492659330368042s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.31826257705688477s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 0.30504512786865234s
License | MR license check for Bio2RDF::Dbsnp took 0.506004810333252s
License | HR license check for Bio2RDF::Dbsnp took 60.24827194213867s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.2587251663208008s
Understandability | Number of label check for Bio2RDF::Dbsnp took 10.244144439697266s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.5992119312286377s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.2618119716644287s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.2543191909790039s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.2478475570678711s
Performance | Throughput check for Bio2RDF::Dbsnp took 10.830344200134277s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 74.89887738227844s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.5935013294219971s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.38532090187072754s
Interlinking | skos check for Bio2RDF::Dbsnp took 1.02915358543396s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.34433412551879883s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.2659120559692383s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.526700496673584s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.5141880512237549s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 108.89303779602051s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.41272997856140137s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.28886866569519043s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.28021788597106934s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 7.524017572402954s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.9473557472229004s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6824784278869629s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.4370133876800537s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 65.48227882385254s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.3568668365478516s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.672086477279663s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.331226110458374s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.552722692489624s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7219524383544922s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.41977477073669434s
Security | Sign check for Bio2RDF::Dbsnp took 0.27182555198669434s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 11.554247379302979s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.9495465755462646s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.020825862884521484s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 7.772445678710938e-05s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 1005.5891244411469s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.4665966033935547s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0005602836608886719s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 20.236543893814087s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.2489807605743408s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 45.198508739471436s
Interoperability | New terms check for Bio2RDF::Drugbank took 42.71331262588501s
Versatility | Languages check for Bio2RDF::Drugbank took 60.24730587005615s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.26421499252319336s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.16689610481262207s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.9619436264038086s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.3083484172821045s
Availability | RDF dump link check for Bio2RDF::Drugbank took 0.2975022792816162s
License | MR license check for Bio2RDF::Drugbank took 0.5861837863922119s
License | HR license check for Bio2RDF::Drugbank took 60.2557315826416s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.2797555923461914s
Understandability | Number of label check for Bio2RDF::Drugbank took 10.1073477268219s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.6035847663879395s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.2569596767425537s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.27854013442993164s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.2480168342590332s
Performance | Throughput check for Bio2RDF::Drugbank took 11.164209127426147s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 74.16766476631165s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.6088802814483643s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.3688042163848877s
Interlinking | skos check for Bio2RDF::Drugbank took 0.9666709899902344s
Interlinking | skos check for Bio2RDF::Drugbank took 0.34723544120788574s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.2673656940460205s
Currency | Creation date check for Bio2RDF::Drugbank took 0.5036411285400391s
Currency | Modification date check for Bio2RDF::Drugbank took 0.48576927185058594s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 110.05197501182556s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.4343833923339844s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.28687143325805664s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.29212260246276855s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 7.981370687484741s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.8989162445068359s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.6685361862182617s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.452770471572876s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 65.80857992172241s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.3591725826263428s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 6.357601881027222s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.3238134384155273s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.55060696601868s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.6955535411834717s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.42652177810668945s
Security | Sign check for Bio2RDF::Drugbank took 0.26148128509521484s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 11.613668441772461s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 1.2918059825897217s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020215511322021484s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00010538101196289062s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-drugbank took 1009.4845516681671s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.4629545211791992s
Availability | VoID file availability check for Bio2RDF::Genage took 0.000701904296875s
Extra | Recovery of all triples for Bio2RDF::Genage took 18.86640501022339s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.2116107940673828s
Amount of data | Number of triples check for Bio2RDF::Genage took 44.26992726325989s
Interoperability | New terms check for Bio2RDF::Genage took 41.912400245666504s
Versatility | Languages check for Bio2RDF::Genage took 60.24256920814514s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.26366686820983887s
Security | Check HTTPS for Bio2RDF::Genage took 0.15607190132141113s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.6293566226959229s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.2909665107727051s
Availability | RDF dump link check for Bio2RDF::Genage took 0.2983381748199463s
License | MR license check for Bio2RDF::Genage took 0.5538504123687744s
License | HR license check for Bio2RDF::Genage took 60.249131202697754s
Amount of data | Number of property check for Bio2RDF::Genage took 0.26058506965637207s
Understandability | Number of label check for Bio2RDF::Genage took 10.537324905395508s
Understandability | URI regex check for Bio2RDF::Genage took 0.5851285457611084s
Understandability | Vocabs check for Bio2RDF::Genage took 0.2564845085144043s
Verifiability | Authors check for Bio2RDF::Genage took 0.2659602165222168s
Verifiability | Publishers check for Bio2RDF::Genage took 0.2698369026184082s
Performance | Throughput check for Bio2RDF::Genage took 10.801204919815063s
Amount of data | Check the number of entities for Bio2RDF::Genage took 77.32673192024231s
Verifiability | Contribs. check for Bio2RDF::Genage took 0.5745954513549805s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.37459492683410645s
Interlinking | skos check for Bio2RDF::Genage took 0.940920352935791s
Interlinking | skos check for Bio2RDF::Genage took 0.3482396602630615s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.2793731689453125s
Currency | Creation date check for Bio2RDF::Genage took 0.5194127559661865s
Currency | Modification date check for Bio2RDF::Genage took 0.49356508255004883s
Rep.Conc. | URIs length for Bio2RDF::Genage took 112.76053047180176s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.4436612129211426s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.290698766708374s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.2805635929107666s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 7.110638380050659s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.8900089263916016s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6827423572540283s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.4680922031402588s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 65.56985592842102s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.428821086883545s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.523799896240234s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.3491461277008057s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.55638599395752s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.708054780960083s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.4279766082763672s
Security | Sign check for Bio2RDF::Genage took 0.27383899688720703s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 11.742936134338379s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 1.0250015258789062s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.02036571502685547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 6.031990051269531e-05s
Believability | Calculation of trust value for Bio2RDF::Genage took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-genage took 1010.6481490135193s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 7.128715515136719e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.27754950523376465s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.020681381225585938s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 5.91278076171875e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-genbank took 4.184280633926392s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 1.272782802581787s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0003390312194824219s
Extra | Recovery of all triples for Bio2RDF::Gendr took 19.219804525375366s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.2239835262298584s
Amount of data | Number of triples check for Bio2RDF::Gendr took 44.18269157409668s
Interoperability | New terms check for Bio2RDF::Gendr took 41.091784715652466s
Versatility | Languages check for Bio2RDF::Gendr took 60.26698017120361s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.2707192897796631s
Security | Check HTTPS for Bio2RDF::Gendr took 0.14591097831726074s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.9709749221801758s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.30990123748779297s
Availability | RDF dump link check for Bio2RDF::Gendr took 0.2994263172149658s
License | MR license check for Bio2RDF::Gendr took 0.5943310260772705s
License | HR license check for Bio2RDF::Gendr took 60.23723554611206s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.26349520683288574s
Understandability | Number of label check for Bio2RDF::Gendr took 10.028210639953613s
Understandability | URI regex check for Bio2RDF::Gendr took 0.5979509353637695s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.27000951766967773s
Verifiability | Authors check for Bio2RDF::Gendr took 0.27211523056030273s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.2541165351867676s
Performance | Throughput check for Bio2RDF::Gendr took 11.061726570129395s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 79.73396849632263s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.7550442218780518s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.34543800354003906s
Interlinking | skos check for Bio2RDF::Gendr took 0.8177568912506104s
Interlinking | skos check for Bio2RDF::Gendr took 0.35761404037475586s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.26183390617370605s
Currency | Creation date check for Bio2RDF::Gendr took 0.525780439376831s
Currency | Modification date check for Bio2RDF::Gendr took 0.4991490840911865s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 111.03176927566528s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.46393346786499023s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.28550291061401367s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.2825155258178711s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 7.257532835006714s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.8971710205078125s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6449306011199951s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.44903111457824707s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 65.0465395450592s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.3954429626464844s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.543527126312256s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.2746829986572266s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.51495027542114s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.6904025077819824s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.42368316650390625s
Security | Sign check for Bio2RDF::Gendr took 0.2677445411682129s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 11.905055522918701s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.42763829231262207s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.02039933204650879s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.745887756347656e-05s
Believability | Calculation of trust value for Bio2RDF::Gendr took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-gendr took 1012.9894616603851s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.4823315143585205s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0006003379821777344s
Extra | Recovery of all triples for Bio2RDF::Goa took 19.64137101173401s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.2618672847747803s
Amount of data | Number of triples check for Bio2RDF::Goa took 43.42667484283447s
Interoperability | New terms check for Bio2RDF::Goa took 41.3126745223999s
Versatility | Languages check for Bio2RDF::Goa took 60.24777579307556s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.2609109878540039s
Security | Check HTTPS for Bio2RDF::Goa took 0.16774964332580566s
Interpretability | RDF structures check for Bio2RDF::Goa took 1.3164925575256348s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.30957674980163574s
Availability | RDF dump link check for Bio2RDF::Goa took 0.2664358615875244s
License | MR license check for Bio2RDF::Goa took 0.5333423614501953s
License | HR license check for Bio2RDF::Goa took 60.23453688621521s
Amount of data | Number of property check for Bio2RDF::Goa took 0.2610130310058594s
Understandability | Number of label check for Bio2RDF::Goa took 10.131881952285767s
Understandability | URI regex check for Bio2RDF::Goa took 0.5742049217224121s
Understandability | Vocabs check for Bio2RDF::Goa took 0.27541017532348633s
Verifiability | Authors check for Bio2RDF::Goa took 0.2665576934814453s
Verifiability | Publishers check for Bio2RDF::Goa took 0.24411654472351074s
Performance | Throughput check for Bio2RDF::Goa took 11.22374939918518s
Amount of data | Check the number of entities for Bio2RDF::Goa took 73.03352785110474s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.5858249664306641s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.3903930187225342s
Interlinking | skos check for Bio2RDF::Goa took 0.9202117919921875s
Interlinking | skos check for Bio2RDF::Goa took 0.3435835838317871s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.26339125633239746s
Currency | Creation date check for Bio2RDF::Goa took 0.506267786026001s
Currency | Modification date check for Bio2RDF::Goa took 0.5284886360168457s
Rep.Conc. | URIs length for Bio2RDF::Goa took 109.27948832511902s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.42858409881591797s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.2742195129394531s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.28659725189208984s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 7.610452890396118s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.8931357860565186s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6901164054870605s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.46436095237731934s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 66.05167484283447s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.424760103225708s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 6.683862686157227s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.3111815452575684s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.55811953544617s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.7007913589477539s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.41105222702026367s
Security | Sign check for Bio2RDF::Goa took 0.2705233097076416s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 11.791404485702515s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 1.0142195224761963s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.020458221435546875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.651878356933594e-05s
Believability | Calculation of trust value for Bio2RDF::Goa took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-goa took 1011.8856883049011s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 1.297936201095581s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0006461143493652344s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 19.389012098312378s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.2628753185272217s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 43.740495920181274s
Interoperability | New terms check for Bio2RDF::Hgnc took 45.978352308273315s
Versatility | Languages check for Bio2RDF::Hgnc took 60.23949384689331s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.2726888656616211s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.16680240631103516s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 1.1777586936950684s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.3188769817352295s
Availability | RDF dump link check for Bio2RDF::Hgnc took 0.28604722023010254s
License | MR license check for Bio2RDF::Hgnc took 0.6503374576568604s
License | HR license check for Bio2RDF::Hgnc took 60.23998427391052s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.2571256160736084s
Understandability | Number of label check for Bio2RDF::Hgnc took 9.846518993377686s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.6250545978546143s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.2598109245300293s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.2706143856048584s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.2781968116760254s
Performance | Throughput check for Bio2RDF::Hgnc took 11.036879301071167s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 75.3377730846405s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.763239860534668s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.4285154342651367s
Interlinking | skos check for Bio2RDF::Hgnc took 1.0292611122131348s
Interlinking | skos check for Bio2RDF::Hgnc took 0.4017627239227295s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.2825496196746826s
Currency | Creation date check for Bio2RDF::Hgnc took 0.5460367202758789s
Currency | Modification date check for Bio2RDF::Hgnc took 0.4928250312805176s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 109.98606657981873s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.42519092559814453s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.2802262306213379s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.2848856449127197s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 7.3400514125823975s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.9066402912139893s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6611897945404053s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.4501328468322754s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.21558737754822s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.3928163051605225s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 6.424237251281738s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.3091533184051514s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.554696559906006s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7091972827911377s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.4014472961425781s
Security | Sign check for Bio2RDF::Hgnc took 0.29056501388549805s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 11.647027254104614s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.40019941329956055s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.02037191390991211s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00011110305786132812s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 9.059906005859375e-06s
INFO | --- Analysis for bio2rdf-hgnc took 1013.6496877670288s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.4558100700378418s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0006778240203857422s
Extra | Recovery of all triples for Bio2RDF::Homologene took 19.676032543182373s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.2389366626739502s
Amount of data | Number of triples check for Bio2RDF::Homologene took 43.72786545753479s
Interoperability | New terms check for Bio2RDF::Homologene took 41.7242751121521s
Versatility | Languages check for Bio2RDF::Homologene took 60.250354528427124s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.2501182556152344s
Security | Check HTTPS for Bio2RDF::Homologene took 0.1568617820739746s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.3432273864746094s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.317873477935791s
Availability | RDF dump link check for Bio2RDF::Homologene took 0.29159975051879883s
License | MR license check for Bio2RDF::Homologene took 0.6001143455505371s
License | HR license check for Bio2RDF::Homologene took 60.262757301330566s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.252216100692749s
Understandability | Number of label check for Bio2RDF::Homologene took 9.405195474624634s
Understandability | URI regex check for Bio2RDF::Homologene took 0.5804815292358398s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.25806379318237305s
Verifiability | Authors check for Bio2RDF::Homologene took 0.26021409034729004s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.2723245620727539s
Performance | Throughput check for Bio2RDF::Homologene took 11.288676261901855s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 75.465744972229s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.5866658687591553s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.366241455078125s
Interlinking | skos check for Bio2RDF::Homologene took 1.0090034008026123s
Interlinking | skos check for Bio2RDF::Homologene took 0.3403804302215576s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.27768397331237793s
Currency | Creation date check for Bio2RDF::Homologene took 0.4968254566192627s
Currency | Modification date check for Bio2RDF::Homologene took 0.49279141426086426s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 112.55118131637573s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.4472665786743164s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.2896301746368408s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.28604841232299805s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 7.1987810134887695s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8910002708435059s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6749470233917236s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.5239593982696533s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.5017831325531s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.4195847511291504s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.33154034614563s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.3018336296081543s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.540339946746826s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7134592533111572s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.4168272018432617s
Security | Sign check for Bio2RDF::Homologene took 0.26317882537841797s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 11.401670694351196s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 1.0847549438476562s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.020391225814819336s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0008401870727539062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 7.796287536621094e-05s
Believability | Calculation of trust value for Bio2RDF::Homologene took 9.775161743164062e-06s
INFO | --- Analysis for bio2rdf-homologene took 1009.9197633266449s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 4.00543212890625e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.7287342548370361s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.020581960678100586s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-inoh took 4.302889108657837s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.4841935634613037s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.000659942626953125s
Extra | Recovery of all triples for Bio2RDF::Interpro took 18.372695446014404s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.2514300346374512s
Amount of data | Number of triples check for Bio2RDF::Interpro took 45.352198123931885s
Interoperability | New terms check for Bio2RDF::Interpro took 42.507503032684326s
Versatility | Languages check for Bio2RDF::Interpro took 60.245317220687866s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.2661778926849365s
Security | Check HTTPS for Bio2RDF::Interpro took 0.15670156478881836s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.8917453289031982s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.40410828590393066s
Availability | RDF dump link check for Bio2RDF::Interpro took 0.31221437454223633s
License | MR license check for Bio2RDF::Interpro took 0.5705764293670654s
License | HR license check for Bio2RDF::Interpro took 60.257073163986206s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.2709829807281494s
Understandability | Number of label check for Bio2RDF::Interpro took 9.884434223175049s
Understandability | URI regex check for Bio2RDF::Interpro took 0.5634918212890625s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.27576327323913574s
Verifiability | Authors check for Bio2RDF::Interpro took 0.2648937702178955s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.25641846656799316s
Performance | Throughput check for Bio2RDF::Interpro took 11.25180196762085s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 74.49175500869751s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.5850880146026611s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.39371204376220703s
Interlinking | skos check for Bio2RDF::Interpro took 1.1894810199737549s
Interlinking | skos check for Bio2RDF::Interpro took 0.3861119747161865s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.2695629596710205s
Currency | Creation date check for Bio2RDF::Interpro took 0.5196890830993652s
Currency | Modification date check for Bio2RDF::Interpro took 0.5147199630737305s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 111.63395953178406s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.42431116104125977s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.2864997386932373s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.28606605529785156s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 7.042970418930054s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.8924908638000488s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.648629903793335s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.44471001625061035s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.5145628452301s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.381523847579956s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.786765098571777s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.3161232471466064s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.51352906227112s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.7035694122314453s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.4410679340362549s
Security | Sign check for Bio2RDF::Interpro took 0.2822403907775879s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 11.825865030288696s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.37076544761657715s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.02030038833618164s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 9.72747802734375e-05s
Believability | Calculation of trust value for Bio2RDF::Interpro took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-interpro took 1008.9178049564362s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.13422036170959473s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0006427764892578125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.2869436740875244s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.019955158233642578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 8.130073547363281e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-iproclass took 17.023903608322144s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.48660755157470703s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0006053447723388672s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 20.45401692390442s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.292222261428833s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 43.99162840843201s
Interoperability | New terms check for Bio2RDF::Irefindex took 43.64169788360596s
Versatility | Languages check for Bio2RDF::Irefindex took 60.23753499984741s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.2532980442047119s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.14508318901062012s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.8207309246063232s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.3622264862060547s
Availability | RDF dump link check for Bio2RDF::Irefindex took 0.31623387336730957s
License | MR license check for Bio2RDF::Irefindex took 0.5450253486633301s
License | HR license check for Bio2RDF::Irefindex took 60.255293130874634s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.2708585262298584s
Understandability | Number of label check for Bio2RDF::Irefindex took 9.829959392547607s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.5855803489685059s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.26849889755249023s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.29004859924316406s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.27074694633483887s
Performance | Throughput check for Bio2RDF::Irefindex took 11.692327737808228s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 76.25536727905273s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.5760934352874756s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.3754723072052002s
Interlinking | skos check for Bio2RDF::Irefindex took 0.9505753517150879s
Interlinking | skos check for Bio2RDF::Irefindex took 0.3304634094238281s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.27146410942077637s
Currency | Creation date check for Bio2RDF::Irefindex took 0.5548903942108154s
Currency | Modification date check for Bio2RDF::Irefindex took 0.5174152851104736s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 111.65693736076355s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.43224549293518066s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.2755777835845947s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.28147006034851074s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 7.498018026351929s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.8955819606781006s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6505124568939209s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.4507927894592285s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 65.24216842651367s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.332282781600952s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.890806674957275s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.3232152462005615s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.5465567111969s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7192280292510986s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.45762062072753906s
Security | Sign check for Bio2RDF::Irefindex took 0.27027320861816406s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 11.20476770401001s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.9691545963287354s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.0202789306640625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 8.249282836914062e-05s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-irefindex took 1015.7952213287354s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 0.00011730194091796875s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.27266359329223633s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.020313501358032227s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.413459777832031e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-kegg took 4.818317651748657s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 4.1484832763671875e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.26593685150146484s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.02062821388244629s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 6.127357482910156e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-kegg-biopax took 3.408442974090576s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.13762426376342773s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0004105567932128906s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.2777893543243408s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020378589630126953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.647804260253906e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 10.003703594207764s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.5076136589050293s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0012848377227783203s
Extra | Recovery of all triples for Bio2RDF::Lsr took 20.319515228271484s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.2797088623046875s
Amount of data | Number of triples check for Bio2RDF::Lsr took 44.86497473716736s
Interoperability | New terms check for Bio2RDF::Lsr took 42.79365015029907s
Versatility | Languages check for Bio2RDF::Lsr took 60.24980711936951s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.2807505130767822s
Security | Check HTTPS for Bio2RDF::Lsr took 0.15709996223449707s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.8536760807037354s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.3918910026550293s
Availability | RDF dump link check for Bio2RDF::Lsr took 0.29053783416748047s
License | MR license check for Bio2RDF::Lsr took 0.5133354663848877s
License | HR license check for Bio2RDF::Lsr took 60.24775218963623s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.25414180755615234s
Understandability | Number of label check for Bio2RDF::Lsr took 10.262463569641113s
Understandability | URI regex check for Bio2RDF::Lsr took 0.5992481708526611s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.26192545890808105s
Verifiability | Authors check for Bio2RDF::Lsr took 0.34139418601989746s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.26737189292907715s
Performance | Throughput check for Bio2RDF::Lsr took 10.79379940032959s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 73.52658224105835s
Verifiability | Contribs. check for Bio2RDF::Lsr took 2.02933669090271s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.3774240016937256s
Interlinking | skos check for Bio2RDF::Lsr took 0.8598835468292236s
Interlinking | skos check for Bio2RDF::Lsr took 0.34391188621520996s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.2924468517303467s
Currency | Creation date check for Bio2RDF::Lsr took 0.5139126777648926s
Currency | Modification date check for Bio2RDF::Lsr took 0.5132977962493896s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 112.99994134902954s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.4218924045562744s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.3111884593963623s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.2909512519836426s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 7.054753541946411s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.8965644836425781s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.6549475193023682s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.4558589458465576s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 65.59684634208679s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.3711557388305664s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.443408727645874s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.3075032234191895s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.50861883163452s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.7022547721862793s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.39606595039367676s
Security | Sign check for Bio2RDF::Lsr took 0.29208874702453613s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 11.485494375228882s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 1.2913143634796143s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.020836353302001953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 5.507469177246094e-05s
Believability | Calculation of trust value for Bio2RDF::Lsr took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-lsr took 1012.558865070343s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.463059663772583s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0006282329559326172s
Extra | Recovery of all triples for Bio2RDF::Mesh took 20.02452039718628s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.2341935634613037s
Amount of data | Number of triples check for Bio2RDF::Mesh took 43.67437982559204s
Interoperability | New terms check for Bio2RDF::Mesh took 43.70670700073242s
Versatility | Languages check for Bio2RDF::Mesh took 60.23851132392883s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.26384997367858887s
Security | Check HTTPS for Bio2RDF::Mesh took 0.1547248363494873s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.3834059238433838s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.31615114212036133s
Availability | RDF dump link check for Bio2RDF::Mesh took 0.3027222156524658s
License | MR license check for Bio2RDF::Mesh took 0.5315501689910889s
License | HR license check for Bio2RDF::Mesh took 60.258880376815796s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.283935546875s
Understandability | Number of label check for Bio2RDF::Mesh took 10.902865409851074s
Understandability | URI regex check for Bio2RDF::Mesh took 0.563230037689209s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.24998974800109863s
Verifiability | Authors check for Bio2RDF::Mesh took 0.267986536026001s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.2688882350921631s
Performance | Throughput check for Bio2RDF::Mesh took 11.23992395401001s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 72.81036901473999s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.5590779781341553s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.39469051361083984s
Interlinking | skos check for Bio2RDF::Mesh took 0.952646017074585s
Interlinking | skos check for Bio2RDF::Mesh took 0.328202486038208s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.2549738883972168s
Currency | Creation date check for Bio2RDF::Mesh took 0.5235583782196045s
Currency | Modification date check for Bio2RDF::Mesh took 0.49202680587768555s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 110.2297420501709s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.4581644535064697s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.2655792236328125s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.2892189025878906s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 7.398263454437256s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.9015171527862549s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6530449390411377s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.4235720634460449s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 65.43759608268738s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.3409574031829834s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.348528146743774s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.3009510040283203s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.524482011795044s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.6993682384490967s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.4281787872314453s
Security | Sign check for Bio2RDF::Mesh took 0.267960786819458s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 11.140526533126831s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 1.1776676177978516s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.020775318145751953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 8.893013000488281e-05s
Believability | Calculation of trust value for Bio2RDF::Mesh took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-mesh took 1010.5147800445557s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.4904615879058838s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.000347137451171875s
Extra | Recovery of all triples for Bio2RDF::Mgi took 18.63422966003418s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.2386338710784912s
Amount of data | Number of triples check for Bio2RDF::Mgi took 43.776646852493286s
Interoperability | New terms check for Bio2RDF::Mgi took 42.213621377944946s
Versatility | Languages check for Bio2RDF::Mgi took 60.236345052719116s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.26468777656555176s
Security | Check HTTPS for Bio2RDF::Mgi took 0.16722893714904785s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.8198666572570801s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.3402445316314697s
Availability | RDF dump link check for Bio2RDF::Mgi took 0.32360148429870605s
License | MR license check for Bio2RDF::Mgi took 0.623396635055542s
License | HR license check for Bio2RDF::Mgi took 60.24410080909729s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.2661287784576416s
Understandability | Number of label check for Bio2RDF::Mgi took 9.927218198776245s
Understandability | URI regex check for Bio2RDF::Mgi took 0.6007533073425293s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.2586190700531006s
Verifiability | Authors check for Bio2RDF::Mgi took 0.2760741710662842s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.2624545097351074s
Performance | Throughput check for Bio2RDF::Mgi took 11.551571369171143s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 77.18309354782104s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.7075674533843994s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.38799262046813965s
Interlinking | skos check for Bio2RDF::Mgi took 0.8886692523956299s
Interlinking | skos check for Bio2RDF::Mgi took 0.3490285873413086s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.27663230895996094s
Currency | Creation date check for Bio2RDF::Mgi took 0.48316121101379395s
Currency | Modification date check for Bio2RDF::Mgi took 0.5193428993225098s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 108.87196779251099s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.4581024646759033s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.2746093273162842s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.2879829406738281s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 7.620023727416992s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.8887770175933838s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.7019259929656982s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.4938089847564697s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.35841751098633s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.384145498275757s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 6.405017375946045s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.3585121631622314s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.57892823219299s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7229478359222412s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.46353816986083984s
Security | Sign check for Bio2RDF::Mgi took 0.27384066581726074s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 11.226582765579224s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 1.328399419784546s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.020703554153442383s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 9.72747802734375e-05s
Believability | Calculation of trust value for Bio2RDF::Mgi took 9.5367431640625e-06s
INFO | --- Analysis for bio2rdf-mgi took 1011.3643946647644s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.47083425521850586s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0006253719329833984s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 21.086496353149414s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.289919137954712s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 44.36244034767151s
Interoperability | New terms check for Bio2RDF::Ncbigene took 44.34922170639038s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.25374221801758s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.2834923267364502s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.1662755012512207s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.658656120300293s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.35418128967285156s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 0.29148006439208984s
License | MR license check for Bio2RDF::Ncbigene took 0.49045681953430176s
License | HR license check for Bio2RDF::Ncbigene took 60.2499566078186s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.2530362606048584s
Understandability | Number of label check for Bio2RDF::Ncbigene took 9.700274229049683s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.5915341377258301s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.2883021831512451s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.34157371520996094s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.24746298789978027s
Performance | Throughput check for Bio2RDF::Ncbigene took 11.290055990219116s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 73.894287109375s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 2.552124261856079s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.38253355026245117s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.931710958480835s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.345048189163208s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.27150726318359375s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.5136198997497559s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.503525972366333s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 108.783762216568s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.4152050018310547s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2682969570159912s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.28881144523620605s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 7.781561374664307s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.8961682319641113s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6537032127380371s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.5254991054534912s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.62732577323914s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.3979837894439697s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.827526092529297s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.2826454639434814s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.5132269859314s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.70731520652771s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.39803552627563477s
Security | Sign check for Bio2RDF::Ncbigene took 0.2783048152923584s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 10.889955282211304s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.9835395812988281s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.0205686092376709s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0008115768432617188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.0001366138458251953s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 9.298324584960938e-06s
INFO | --- Analysis for bio2rdf-ncbigene took 1037.5424354076385s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.48906493186950684s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0005655288696289062s
Extra | Recovery of all triples for Bio2RDF::Ndc took 21.377387762069702s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.2347595691680908s
Amount of data | Number of triples check for Bio2RDF::Ndc took 47.10596251487732s
Interoperability | New terms check for Bio2RDF::Ndc took 43.50690817832947s
Versatility | Languages check for Bio2RDF::Ndc took 60.23618769645691s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.27721405029296875s
Security | Check HTTPS for Bio2RDF::Ndc took 0.15548324584960938s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.4707319736480713s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.3771488666534424s
Availability | RDF dump link check for Bio2RDF::Ndc took 0.3105168342590332s
License | MR license check for Bio2RDF::Ndc took 0.5214822292327881s
License | HR license check for Bio2RDF::Ndc took 60.268102169036865s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.2626028060913086s
Understandability | Number of label check for Bio2RDF::Ndc took 10.515711545944214s
Understandability | URI regex check for Bio2RDF::Ndc took 0.5860178470611572s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.27808642387390137s
Verifiability | Authors check for Bio2RDF::Ndc took 0.3852529525756836s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.2536013126373291s
Performance | Throughput check for Bio2RDF::Ndc took 10.988014459609985s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 78.32344913482666s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.5971250534057617s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.409238338470459s
Interlinking | skos check for Bio2RDF::Ndc took 0.914804220199585s
Interlinking | skos check for Bio2RDF::Ndc took 0.3587789535522461s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.2598707675933838s
Currency | Creation date check for Bio2RDF::Ndc took 0.5378291606903076s
Currency | Modification date check for Bio2RDF::Ndc took 0.5318799018859863s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 111.18129396438599s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.44879841804504395s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.28054261207580566s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.278458833694458s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 7.9636077880859375s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.9039890766143799s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6771767139434814s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.47896909713745117s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 66.04114127159119s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.4033443927764893s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.271709680557251s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.3438365459442139s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.66138458251953s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7756049633026123s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.46749114990234375s
Security | Sign check for Bio2RDF::Ndc took 0.2668890953063965s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 3.713230848312378s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.39714741706848145s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 5.888938903808594e-05s
Believability | Calculation of trust value for Bio2RDF::Ndc took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-ndc took 1010.2568628787994s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 4.792213439941406e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.00034809112548828125s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.28655266761779785s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.02079463005065918s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 3.790855407714844e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-netpath took 3.86855149269104s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.1339106559753418s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0006108283996582031s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.304241418838501s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.020653486251831055s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.075599670410156e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-nextprot took 3.4408721923828125s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.4821150302886963s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0007965564727783203s
Extra | Recovery of all triples for Bio2RDF::Omim took 20.74189257621765s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.2751975059509277s
Amount of data | Number of triples check for Bio2RDF::Omim took 43.85484027862549s
Interoperability | New terms check for Bio2RDF::Omim took 45.02681040763855s
Versatility | Languages check for Bio2RDF::Omim took 60.24605083465576s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.2957127094268799s
Security | Check HTTPS for Bio2RDF::Omim took 0.16732120513916016s
Interpretability | RDF structures check for Bio2RDF::Omim took 1.0718750953674316s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.35921359062194824s
Availability | RDF dump link check for Bio2RDF::Omim took 0.2998688220977783s
License | MR license check for Bio2RDF::Omim took 0.6086416244506836s
License | HR license check for Bio2RDF::Omim took 60.25850987434387s
Amount of data | Number of property check for Bio2RDF::Omim took 0.25058770179748535s
Understandability | Number of label check for Bio2RDF::Omim took 10.894331455230713s
Understandability | URI regex check for Bio2RDF::Omim took 0.5799736976623535s
Understandability | Vocabs check for Bio2RDF::Omim took 0.2586967945098877s
Verifiability | Authors check for Bio2RDF::Omim took 0.3161351680755615s
Verifiability | Publishers check for Bio2RDF::Omim took 0.2700495719909668s
Performance | Throughput check for Bio2RDF::Omim took 10.860673666000366s
Amount of data | Check the number of entities for Bio2RDF::Omim took 77.54082560539246s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.5945296287536621s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.4849104881286621s
Interlinking | skos check for Bio2RDF::Omim took 1.445410966873169s
Interlinking | skos check for Bio2RDF::Omim took 0.6692001819610596s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.27083754539489746s
Currency | Creation date check for Bio2RDF::Omim took 0.518601655960083s
Currency | Modification date check for Bio2RDF::Omim took 0.531853437423706s
Rep.Conc. | URIs length for Bio2RDF::Omim took 114.33711123466492s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.43534255027770996s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.2852797508239746s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.28446531295776367s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 7.500613451004028s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.8932995796203613s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6655950546264648s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.45784497261047363s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 65.1124017238617s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.3489673137664795s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 7.058023929595947s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.274355173110962s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.607256174087524s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.7235441207885742s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.45584750175476074s
Security | Sign check for Bio2RDF::Omim took 0.27779316902160645s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 3.434810161590576s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.6067714691162109s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.02016282081604004s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00012946128845214844s
Believability | Calculation of trust value for Bio2RDF::Omim took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-omim took 1046.0391254425049s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 4.8160552978515625e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.26417112350463867s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.020392179489135742s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.9577484130859375e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 3.6729533672332764s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.5334203243255615s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0005812644958496094s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 21.364354372024536s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.1934130191802979s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 45.10604763031006s
Interoperability | New terms check for Bio2RDF::Orphanet took 43.297454833984375s
Versatility | Languages check for Bio2RDF::Orphanet took 60.23710584640503s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.27663254737854004s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.16925978660583496s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.6705577373504639s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.39148402214050293s
Availability | RDF dump link check for Bio2RDF::Orphanet took 0.29421234130859375s
License | MR license check for Bio2RDF::Orphanet took 0.5439856052398682s
License | HR license check for Bio2RDF::Orphanet took 60.255247592926025s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.26282477378845215s
Understandability | Number of label check for Bio2RDF::Orphanet took 10.713190078735352s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.6149239540100098s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.26592183113098145s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.3084075450897217s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.2864236831665039s
Performance | Throughput check for Bio2RDF::Orphanet took 11.318112134933472s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 76.80366921424866s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.7374484539031982s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.3871028423309326s
Interlinking | skos check for Bio2RDF::Orphanet took 0.8645892143249512s
Interlinking | skos check for Bio2RDF::Orphanet took 0.3573269844055176s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.2832019329071045s
Currency | Creation date check for Bio2RDF::Orphanet took 0.5298056602478027s
Currency | Modification date check for Bio2RDF::Orphanet took 0.5271155834197998s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 109.42500710487366s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.44182300567626953s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.3015291690826416s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.2696549892425537s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 8.669470071792603s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.9039592742919922s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6984939575195312s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.469818115234375s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 67.07665467262268s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.3707752227783203s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.835944175720215s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.3255105018615723s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.52895760536194s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7025532722473145s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.42618608474731445s
Security | Sign check for Bio2RDF::Orphanet took 0.27332329750061035s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 10.647575616836548s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 1.3575670719146729s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.020296573638916016s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 8.440017700195312e-05s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-orphanet took 1032.480213880539s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.13524651527404785s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.7161445617675781s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.02024531364440918s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.123283386230469e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 9.880805253982544s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.4755520820617676s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0005986690521240234s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 19.860751390457153s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.2167928218841553s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 44.69852256774902s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 43.56816029548645s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.24108290672302s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.3038666248321533s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.1451401710510254s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.7705326080322266s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.3837890625s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 0.2880125045776367s
License | MR license check for Bio2RDF::Pharmgkb took 0.4979424476623535s
License | HR license check for Bio2RDF::Pharmgkb took 60.24574613571167s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.25572967529296875s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 10.251770734786987s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.6048269271850586s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.26787710189819336s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.2709929943084717s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.2581291198730469s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.095195531845093s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 77.61584448814392s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.5919497013092041s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.39412379264831543s
Interlinking | skos check for Bio2RDF::Pharmgkb took 1.2891764640808105s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.34688377380371094s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.27536582946777344s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.526010274887085s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.5228872299194336s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 111.26007342338562s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.4520838260650635s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.2790515422821045s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.27342724800109863s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 7.358906984329224s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.8967957496643066s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6641836166381836s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.46475911140441895s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 65.30012035369873s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.354271650314331s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 7.040642499923706s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.307424783706665s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.527894020080566s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7144997119903564s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.4389021396636963s
Security | Sign check for Bio2RDF::Pharmgkb took 0.2539980411529541s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 10.941119194030762s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 1.4336590766906738s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.02027297019958496s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.128715515136719e-05s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-pharmgkb took 1017.9640784263611s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 4.220008850097656e-05s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.0007808208465576172s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.2654750347137451s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.020258188247680664s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 3.123283386230469e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 4.231957912445068s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 4.172325134277344e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.24837183952331543s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.0204010009765625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.266334533691406e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-pid took 3.3641083240509033s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 4.267692565917969e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.27939534187316895s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.02053380012512207s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0008611679077148438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 3.62396240234375e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-pubchem-2 took 2.9586403369903564s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.46126365661621094s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0005877017974853516s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 19.19183874130249s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.308558702468872s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 43.45046830177307s
Interoperability | New terms check for Bio2RDF::Pubmed took 41.33926200866699s
Versatility | Languages check for Bio2RDF::Pubmed took 60.24338960647583s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.26859259605407715s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.15860891342163086s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.9561731815338135s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.3472740650177002s
Availability | RDF dump link check for Bio2RDF::Pubmed took 0.3042025566101074s
License | MR license check for Bio2RDF::Pubmed took 0.5325136184692383s
License | HR license check for Bio2RDF::Pubmed took 60.25844740867615s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.2771000862121582s
Understandability | Number of label check for Bio2RDF::Pubmed took 9.892860412597656s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.5779798030853271s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.4509727954864502s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.24995994567871094s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.26743531227111816s
Performance | Throughput check for Bio2RDF::Pubmed took 11.456902027130127s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 76.1987669467926s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.5945093631744385s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.38518595695495605s
Interlinking | skos check for Bio2RDF::Pubmed took 1.0874311923980713s
Interlinking | skos check for Bio2RDF::Pubmed took 0.33402395248413086s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.2603323459625244s
Currency | Creation date check for Bio2RDF::Pubmed took 0.5108017921447754s
Currency | Modification date check for Bio2RDF::Pubmed took 0.5139596462249756s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 113.62975311279297s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.3997368812561035s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.28639674186706543s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.29099559783935547s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 7.890048265457153s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.8944945335388184s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6696012020111084s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.4440426826477051s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.5174400806427s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.317227840423584s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.704730987548828s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.2718110084533691s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.52547740936279s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.6995422840118408s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.4316065311431885s
Security | Sign check for Bio2RDF::Pubmed took 0.274993896484375s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 10.71592664718628s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.3538391590118408s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.02025008201599121s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00013971328735351562s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 9.059906005859375e-06s
INFO | --- Analysis for bio2rdf-pubmed took 1029.1764633655548s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.7264430522918701s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.020285367965698242s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 7.271766662597656e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-reactome took 5.101073741912842s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 4.410743713378906e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.0003025531768798828s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.26832103729248047s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.020360231399536133s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 5.459785461425781e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-rhea took 3.815122365951538s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.13631844520568848s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0006520748138427734s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.3070995807647705s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.020612716674804688s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.82012939453125e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-sabiork took 9.9290132522583s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.5336964130401611s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0006129741668701172s
Extra | Recovery of all triples for Bio2RDF::Sgd took 20.12018895149231s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.207167625427246s
Amount of data | Number of triples check for Bio2RDF::Sgd took 45.23062705993652s
Interoperability | New terms check for Bio2RDF::Sgd took 45.21458625793457s
Versatility | Languages check for Bio2RDF::Sgd took 60.24794602394104s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.3049445152282715s
Security | Check HTTPS for Bio2RDF::Sgd took 0.15574932098388672s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.9987306594848633s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.4330766201019287s
Availability | RDF dump link check for Bio2RDF::Sgd took 0.29051709175109863s
License | MR license check for Bio2RDF::Sgd took 0.5076353549957275s
License | HR license check for Bio2RDF::Sgd took 60.26449680328369s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.26671433448791504s
Understandability | Number of label check for Bio2RDF::Sgd took 10.044091939926147s
Understandability | URI regex check for Bio2RDF::Sgd took 0.5788819789886475s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.2774982452392578s
Verifiability | Authors check for Bio2RDF::Sgd took 0.2863762378692627s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.26007986068725586s
Performance | Throughput check for Bio2RDF::Sgd took 10.614591121673584s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 76.20808434486389s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.5926790237426758s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.3978312015533447s
Interlinking | skos check for Bio2RDF::Sgd took 0.9421029090881348s
Interlinking | skos check for Bio2RDF::Sgd took 0.3887779712677002s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.2569844722747803s
Currency | Creation date check for Bio2RDF::Sgd took 0.5105268955230713s
Currency | Modification date check for Bio2RDF::Sgd took 0.5399243831634521s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 112.15714073181152s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.42913174629211426s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.2647526264190674s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.2784562110900879s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 7.75586199760437s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.8926699161529541s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6548306941986084s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.4635777473449707s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 65.62007069587708s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.4046928882598877s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 7.112683057785034s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.3288073539733887s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.57446908950806s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.7178092002868652s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.41524267196655273s
Security | Sign check for Bio2RDF::Sgd took 0.26863932609558105s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 10.664052724838257s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.6964209079742432s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.02027297019958496s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00010800361633300781s
Believability | Calculation of trust value for Bio2RDF::Sgd took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-sgd took 1024.0053713321686s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.291534423828125e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.2688877582550049s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.020087242126464844s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.600120544433594e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-sgd-resources took 3.7140207290649414s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.48061633110046387s
Availability | VoID file availability check for Bio2RDF::Sider took 0.00033974647521972656s
Extra | Recovery of all triples for Bio2RDF::Sider took 22.28934121131897s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.286034107208252s
Amount of data | Number of triples check for Bio2RDF::Sider took 54.52872633934021s
Interoperability | New terms check for Bio2RDF::Sider took 45.18365240097046s
Versatility | Languages check for Bio2RDF::Sider took 60.2411322593689s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.28107118606567383s
Security | Check HTTPS for Bio2RDF::Sider took 0.15804338455200195s
Interpretability | RDF structures check for Bio2RDF::Sider took 1.000688076019287s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.3712155818939209s
Availability | RDF dump link check for Bio2RDF::Sider took 0.2868623733520508s
License | MR license check for Bio2RDF::Sider took 0.6220748424530029s
License | HR license check for Bio2RDF::Sider took 60.26092886924744s
Amount of data | Number of property check for Bio2RDF::Sider took 0.27521347999572754s
Understandability | Number of label check for Bio2RDF::Sider took 10.88652777671814s
Understandability | URI regex check for Bio2RDF::Sider took 0.553250789642334s
Understandability | Vocabs check for Bio2RDF::Sider took 0.2908778190612793s
Verifiability | Authors check for Bio2RDF::Sider took 0.3857889175415039s
Verifiability | Publishers check for Bio2RDF::Sider took 0.2669849395751953s
Performance | Throughput check for Bio2RDF::Sider took 11.282247066497803s
Amount of data | Check the number of entities for Bio2RDF::Sider took 74.38481783866882s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.769373893737793s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.38916444778442383s
Interlinking | skos check for Bio2RDF::Sider took 1.0511131286621094s
Interlinking | skos check for Bio2RDF::Sider took 0.34638261795043945s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.2770986557006836s
Currency | Creation date check for Bio2RDF::Sider took 0.5210607051849365s
Currency | Modification date check for Bio2RDF::Sider took 0.5243871212005615s
Rep.Conc. | URIs length for Bio2RDF::Sider took 115.10511040687561s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.4124746322631836s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.2668023109436035s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.29465341567993164s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 8.58944582939148s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.8942394256591797s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6522760391235352s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.46325135231018066s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 65.25419902801514s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.4102797508239746s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 6.806902170181274s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.3098177909851074s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.51696991920471s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7026941776275635s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.4324488639831543s
Security | Sign check for Bio2RDF::Sider took 0.2723681926727295s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 10.92508339881897s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 1.2770261764526367s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.02055644989013672s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.38690185546875e-05s
Believability | Calculation of trust value for Bio2RDF::Sider took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-sider took 1061.8759422302246s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 4.696846008300781e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.0003001689910888672s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.6964206695556641s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.02014780044555664s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-spike took 5.131321668624878s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.363059997558594e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.25345683097839355s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.020203113555908203s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.00543212890625e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-taxon took 3.0235400199890137s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.5416779518127441s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0006613731384277344s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 21.36458730697632s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.2382028102874756s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 45.61505198478699s
Interoperability | New terms check for Bio2RDF::Taxonomy took 43.04121208190918s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.22658967971802s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.28333020210266113s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.17444634437561035s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.6938827037811279s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.3589200973510742s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 0.2820601463317871s
License | MR license check for Bio2RDF::Taxonomy took 0.6464662551879883s
License | HR license check for Bio2RDF::Taxonomy took 60.25848317146301s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.28325986862182617s
Understandability | Number of label check for Bio2RDF::Taxonomy took 9.923054456710815s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.5850176811218262s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.2438342571258545s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.2672157287597656s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.267120361328125s
Performance | Throughput check for Bio2RDF::Taxonomy took 11.078430652618408s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 76.42157483100891s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 1.1022143363952637s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.3818364143371582s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.7418675422668457s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.31777334213256836s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.2848551273345947s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.5061414241790771s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.5013420581817627s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 110.29372835159302s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.41897153854370117s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.25013232231140137s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.3002746105194092s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 7.611979961395264s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8868145942687988s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6985311508178711s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.47766613960266113s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 65.35298871994019s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.385524034500122s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 7.026842355728149s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.3243489265441895s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.56552195549011s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7264409065246582s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.4016134738922119s
Security | Sign check for Bio2RDF::Taxonomy took 0.2686924934387207s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 10.674540042877197s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 1.432701826095581s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.020464420318603516s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.0001087188720703125s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-taxonomy took 1021.6081757545471s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.9398252964019775s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0003528594970703125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.2770247459411621s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.0200955867767334s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.266334533691406e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 18.393535137176514s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 1.26385498046875s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0006163120269775391s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 21.35920214653015s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.222630500793457s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 45.58429312705994s
Interoperability | New terms check for Bio2RDF::Wormbase took 45.95134425163269s
Versatility | Languages check for Bio2RDF::Wormbase took 60.25731039047241s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.2738966941833496s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.15485477447509766s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.269484281539917s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.3922877311706543s
Availability | RDF dump link check for Bio2RDF::Wormbase took 0.30760812759399414s
License | MR license check for Bio2RDF::Wormbase took 0.5588037967681885s
License | HR license check for Bio2RDF::Wormbase took 60.23705434799194s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.2534043788909912s
Understandability | Number of label check for Bio2RDF::Wormbase took 9.911120653152466s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.5693621635437012s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.27227234840393066s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.2948634624481201s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.2398543357849121s
Performance | Throughput check for Bio2RDF::Wormbase took 10.574452877044678s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 74.51574945449829s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 2.05940580368042s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.3778960704803467s
Interlinking | skos check for Bio2RDF::Wormbase took 1.014901876449585s
Interlinking | skos check for Bio2RDF::Wormbase took 0.412121057510376s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.2816886901855469s
Currency | Creation date check for Bio2RDF::Wormbase took 0.5412180423736572s
Currency | Modification date check for Bio2RDF::Wormbase took 0.5165445804595947s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 112.79071068763733s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.448134183883667s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.28766775131225586s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.3012962341308594s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 8.592981815338135s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.8933823108673096s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.669081449508667s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.45317864418029785s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 65.67037105560303s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.3453028202056885s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 6.395718812942505s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.2842397689819336s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.521544218063354s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7052707672119141s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.437042236328125s
Security | Sign check for Bio2RDF::Wormbase took 0.2771635055541992s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 11.254085540771484s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.8550775051116943s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.020253419876098633s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.034706115722656e-05s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-wormbase took 1041.191913843155s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.2641878128051758s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.28464579582214355s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020259380340576172s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.726119995117188e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 4.5299530029296875e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 3.148510456085205s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 4.100799560546875e-05s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0003139972686767578s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.2790670394897461s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.020391464233398438s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 2.956390380859375e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for biolit took 3.8087282180786133s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.5249319076538086s
Availability | VoID file availability check for BioModels RDF took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.2762601375579834s
Reputation | Calculation of the PageRank for BioModels RDF took 0.02018427848815918s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.528594970703125e-05s
Believability | Calculation of trust value for BioModels RDF took 6.4373016357421875e-06s
INFO | --- Analysis for biomodels-rdf took 4.170291185379028s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 4.410743713378906e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.28171539306640625s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.020331621170043945s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006115436553955078s
Believability | Calculation of trust value for Amphibian gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-aao took 3.2425436973571777s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.363059997558594e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.26302552223205566s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.020436763763427734s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.00032806396484375s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-aba took 2.6462321281433105s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.26271700859069824s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.020519495010375977s
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.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015187263488769531s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-acgt took 2.669874668121338s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 4.839897155761719e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0007505416870117188s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.2499990463256836s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.020841121673583984s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003361701965332031s
Believability | Calculation of trust value for Animal natural history and life history took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-adw took 2.5783023834228516s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0004153251647949219s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.2854623794555664s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.022038936614990234s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0008335113525390625s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0005104541778564453s
Believability | Calculation of trust value for Anatomical Entity Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-aeo took 2.652632236480713s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 5.364418029785156e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.000354766845703125s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.2615480422973633s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.020343542098999023s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.000978231430053711s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-aero took 3.0684545040130615s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.38690185546875e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0004124641418457031s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.26407527923583984s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.021077632904052734s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0008764266967773438s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.000476837158203125s
Believability | Calculation of trust value for AI/RHEUM took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-air took 2.6265337467193604s
Availability | SPARQL endpoint availability check for Amino Acid took 4.5299530029296875e-05s
Availability | VoID file availability check for Amino Acid took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.2615654468536377s
Reputation | Calculation of the PageRank for Amino Acid took 0.020937681198120117s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.0002758502960205078s
Believability | Calculation of trust value for Amino Acid took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-amino-acid took 2.6145660877227783s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.26750612258911133s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020739316940307617s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.00028061866760253906s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-apo took 2.6658718585968018s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 4.839897155761719e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.2634398937225342s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.02032613754272461s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00024271011352539062s
Believability | Calculation of trust value for African Traditional Medicine took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-atmo took 2.741807699203491s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.2438507080078125e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.2551875114440918s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.020766019821166992s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0008034706115722656s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 0.00010228157043457031s
Believability | Calculation of trust value for Amphibian taxonomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ato took 2.6628191471099854s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 4.7206878662109375e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.27400851249694824s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.02080678939819336s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013267993927001953s
Believability | Calculation of trust value for BioAssay Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bao took 2.6581671237945557s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 4.267692565917969e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.2689228057861328s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020316123962402344s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0003743171691894531s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 2.697510242462158s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.2752254009246826s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.020400524139404297s
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.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003643035888671875s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bcgo took 2.646620273590088s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.24407720565795898s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.02044677734375s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0014088153839111328s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bdo took 2.5288124084472656s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 7.033348083496094e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.2727646827697754s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.020125389099121094s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0004994869232177734s
Believability | Calculation of trust value for Basic Formal Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bfo took 2.620760440826416s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.267692565917969e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.28450560569763184s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.020261764526367188s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007259845733642578s
Believability | Calculation of trust value for Bleeding History Phenotype took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-bho took 2.7034220695495605s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 5.793571472167969e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.2604184150695801s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.020420074462890625s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007958412170410156s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004458427429199219s
Believability | Calculation of trust value for Bilateria anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bila took 2.663935661315918s
Availability | SPARQL endpoint availability check for BIRNLex took 4.2438507080078125e-05s
Availability | VoID file availability check for BIRNLex took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.2541079521179199s
Reputation | Calculation of the PageRank for BIRNLex took 0.020767688751220703s
Interlinking | Calculation of Degree of Connection for BIRNLex took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014939308166503906s
Believability | Calculation of trust value for BIRNLex took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-birnlex took 2.639082193374634s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.257612943649292s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020634174346923828s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0008921623229980469s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0008223056793212891s
Believability | Calculation of trust value for Gene Regulation Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bootstrep took 2.6891815662384033s
Availability | SPARQL endpoint availability check for BioPAX took 4.220008850097656e-05s
Availability | VoID file availability check for BioPAX took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for BioPAX took 0.2915475368499756s
Reputation | Calculation of the PageRank for BioPAX took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0007827281951904297s
Interlinking | Calculation of Clustering coefficient for BioPAX took 0.0001049041748046875s
Believability | Calculation of trust value for BioPAX took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bp took 2.6005234718322754s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 5.435943603515625e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.25171422958374023s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.020509958267211914s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003197193145751953s
Believability | Calculation of trust value for Biomedical Resource Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-bro_x1 took 2.59201979637146s
Availability | SPARQL endpoint availability check for Spatial Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Spatial Ontology took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.2566993236541748s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.02049875259399414s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00024175643920898438s
Believability | Calculation of trust value for Spatial Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bspo took 2.6499855518341064s
Availability | SPARQL endpoint availability check for BioTop took 4.744529724121094e-05s
Availability | VoID file availability check for BioTop took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for BioTop took 0.268887996673584s
Reputation | Calculation of the PageRank for BioTop took 0.020457744598388672s
Interlinking | Calculation of Degree of Connection for BioTop took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006575584411621094s
Believability | Calculation of trust value for BioTop took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bt took 2.696800708770752s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 6.580352783203125e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.2713494300842285s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020528078079223633s
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.0008034706115722656s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0009238719940185547s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bto took 2.6444544792175293s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 6.866455078125e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.329531192779541s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.020378589630126953s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018398761749267578s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-canco took 3.1127328872680664s
Availability | SPARQL endpoint availability check for CAO took 4.3392181396484375e-05s
Availability | VoID file availability check for CAO took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for CAO took 0.2690253257751465s
Reputation | Calculation of the PageRank for CAO took 0.02034902572631836s
Interlinking | Calculation of Degree of Connection for CAO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CAO took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0006136894226074219s
Believability | Calculation of trust value for CAO took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cao took 2.680842638015747s
Availability | SPARQL endpoint availability check for CareLex took 4.220008850097656e-05s
Availability | VoID file availability check for CareLex took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for CareLex took 0.2617065906524658s
Reputation | Calculation of the PageRank for CareLex took 0.020312786102294922s
Interlinking | Calculation of Degree of Connection for CareLex took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for CareLex took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.1975250244140625e-05s
Believability | Calculation of trust value for CareLex took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-carelex took 2.5738911628723145s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.27695202827453613s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.020623445510864258s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0008449554443359375s
Believability | Calculation of trust value for Cell Cycle Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cco took 2.636441707611084s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.2635939121246338s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020190715789794922s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.0003292560577392578s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-cdao took 2.608595132827759s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 4.6253204345703125e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2544565200805664s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.020251989364624023s
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.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0008456707000732422s
Believability | Calculation of trust value for Chemical entities of biological interest took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-chebi took 2.734825849533081s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 4.458427429199219e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.25772953033447266s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.020219802856445312s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002582073211669922s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 2.6298720836639404s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.2607238292694092s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.020163297653198242s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007719993591308594s
Believability | Calculation of trust value for Chemical Information Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cheminf took 2.585193395614624s
Availability | SPARQL endpoint availability check for Cell type took 4.267692565917969e-05s
Availability | VoID file availability check for Cell type took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for Cell type took 0.2673530578613281s
Reputation | Calculation of the PageRank for Cell type took 0.02036142349243164s
Interlinking | Calculation of Degree of Connection for Cell type took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.00044345855712890625s
Believability | Calculation of trust value for Cell type took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cl took 2.6645264625549316s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 5.269050598144531e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.2610034942626953s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.02025151252746582s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008137226104736328s
Believability | Calculation of trust value for Cell Line Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-clo took 2.6369006633758545s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.2706019878387451s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.020412206649780273s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00017571449279785156s
Believability | Calculation of trust value for Clinical Measurement Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-cmo took 2.6318609714508057s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.25406432151794434s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.020521163940429688s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.0002288818359375s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cno took 2.6064369678497314s
Availability | SPARQL endpoint availability check for Wheat trait took 4.267692565917969e-05s
Availability | VoID file availability check for Wheat trait took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.2648632526397705s
Reputation | Calculation of the PageRank for Wheat trait took 0.020451068878173828s
Interlinking | Calculation of Degree of Connection for Wheat trait took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.435943603515625e-05s
Believability | Calculation of trust value for Wheat trait took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-co_wheat took 2.674372434616089s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 5.3882598876953125e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.27257299423217773s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.020281553268432617s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003390312194824219s
Believability | Calculation of trust value for Cognitive Atlas took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-cogat took 2.662937879562378s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.2518739700317383s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020482778549194336s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007355213165283203s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-cogpo took 2.6386804580688477s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 4.315376281738281e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.2763404846191406s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.020226240158081055s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004379749298095703s
Believability | Calculation of trust value for Current Procedural Terminology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cpt took 2.752596139907837s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 4.3392181396484375e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.30118513107299805s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020656347274780273s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0018475055694580078s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-csp took 3.0470497608184814s
Availability | SPARQL endpoint availability check for COSTART took 4.2438507080078125e-05s
Availability | VoID file availability check for COSTART took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for COSTART took 0.26430511474609375s
Reputation | Calculation of the PageRank for COSTART took 0.020650863647460938s
Interlinking | Calculation of Degree of Connection for COSTART took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.00098419189453125s
Believability | Calculation of trust value for COSTART took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cst took 2.633655309677124s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.1961669921875e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.26166200637817383s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0005357265472412109s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ctcae took 2.652226686477661s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 0.00046896934509277344s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.2728230953216553s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.02037644386291504s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004813671112060547s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-ctx took 2.68182373046875s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.3392181396484375e-05s
Availability | VoID file availability check for Dendritic cell took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.2595784664154053s
Reputation | Calculation of the PageRank for Dendritic cell took 0.02044367790222168s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Dendritic cell took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.00031566619873046875s
Believability | Calculation of trust value for Dendritic cell took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-dc_cl took 2.641472578048706s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 4.4345855712890625e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.2793405055999756s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.020416736602783203s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.511543273925781e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 3.266334533691406e-05s
INFO | --- Analysis for bioportal-ddanat took 2.6381852626800537s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 5.6743621826171875e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.2710537910461426s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.02021932601928711s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009305477142333984s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ddi took 2.660008430480957s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.24862241744995117s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.020650386810302734s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.487701416015625e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-diagnosticont took 2.601374864578247s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.27482151985168457s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.020464658737182617s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00016260147094726562s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 2.9802322387695312e-05s
INFO | --- Analysis for bioportal-dikb-evidence took 2.664043664932251s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Human disease ontology took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2797222137451172s
Reputation | Calculation of the PageRank for Human disease ontology took 0.02033257484436035s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006308555603027344s
Believability | Calculation of trust value for Human disease ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-doid took 2.6172354221343994s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.25481295585632324s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.020587444305419922s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0007894039154052734s
Believability | Calculation of trust value for Electrocardiography Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ecg took 2.584711790084839s
Availability | SPARQL endpoint availability check for Evidence codes took 4.363059997558594e-05s
Availability | VoID file availability check for Evidence codes took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.2722654342651367s
Reputation | Calculation of the PageRank for Evidence codes took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.0517578125e-05s
Believability | Calculation of trust value for Evidence codes took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-eco took 2.6284518241882324s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 5.5789947509765625e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.3075275421142578s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020734071731567383s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017321109771728516s
Believability | Calculation of trust value for Experimental Factor Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-efo took 3.0379014015197754s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.4345855712890625e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.3396949768066406s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.020554304122924805s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.001146078109741211s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-ehda took 2.822563648223877s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.315376281738281e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.27827930450439453s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.020110607147216797s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0006995201110839844s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ehdaa took 2.685641288757324s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.315376281738281e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.25216150283813477s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.020073890686035156s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005133152008056641s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 2.524653196334839s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.2438507080078125e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.26450061798095703s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.020341157913208008s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 2.9325485229492188e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-emap took 2.717979907989502s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Environment Ontology took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.26064324378967285s
Reputation | Calculation of the PageRank for Environment Ontology took 0.020511865615844727s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0005052089691162109s
Believability | Calculation of trust value for Environment Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-envo took 2.6886520385742188s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 5.173683166503906e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.279491662979126s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.020117998123168945s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.0003018379211425781s
Believability | Calculation of trust value for Plant environmental conditions took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-eo took 2.6871635913848877s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.27324700355529785s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.02049088478088379s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012021064758300781s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ep took 2.632560968399048s
Availability | SPARQL endpoint availability check for Epilepsy took 4.076957702636719e-05s
Availability | VoID file availability check for Epilepsy took 0.0003085136413574219s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.26246047019958496s
Reputation | Calculation of the PageRank for Epilepsy took 0.028286218643188477s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0010466575622558594s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.0001621246337890625s
Believability | Calculation of trust value for Epilepsy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-epileponto took 2.7070882320404053s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.291534423828125e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.2594125270843506s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020168542861938477s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011386871337890625s
Believability | Calculation of trust value for eagle-i research resource ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-ero took 2.6295249462127686s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.100799560546875e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.25698184967041016s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020164966583251953s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011534690856933594s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ev took 2.614362955093384s
Availability | SPARQL endpoint availability check for ExO took 0.00010323524475097656s
Availability | VoID file availability check for ExO took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for ExO took 0.27707481384277344s
Reputation | Calculation of the PageRank for ExO took 0.020700931549072266s
Interlinking | Calculation of Degree of Connection for ExO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ExO took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for ExO took 0.0002689361572265625s
Believability | Calculation of trust value for ExO took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-exo took 2.6474506855010986s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 4.172325134277344e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.2679736614227295s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.02040886878967285s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00011706352233886719s
Believability | Calculation of trust value for Fungal gross anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fao took 2.5913472175598145s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.172325134277344e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.2725062370300293s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.020093441009521484s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00020003318786621094s
Believability | Calculation of trust value for Biological imaging methods took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-fbbi took 2.691584587097168s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 5.555152893066406e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.2808187007904053s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.020380020141601562s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006511211395263672s
Believability | Calculation of trust value for Drosophila gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fbbt took 2.665030002593994s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 4.267692565917969e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.2653045654296875s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.020372867584228516s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004353523254394531s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-fbcv took 2.7251698970794678s
Availability | SPARQL endpoint availability check for Drosophila development took 7.152557373046875e-05s
Availability | VoID file availability check for Drosophila development took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.285677433013916s
Reputation | Calculation of the PageRank for Drosophila development took 0.02051377296447754s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.744529724121094e-05s
Believability | Calculation of trust value for Drosophila development took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-fbdv took 2.702580451965332s
Availability | SPARQL endpoint availability check for Fly taxonomy took 5.1021575927734375e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.29308199882507324s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.020336627960205078s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003643035888671875s
Believability | Calculation of trust value for Fly taxonomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fbsp took 2.6501049995422363s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.315376281738281e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.2570304870605469s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.02025151252746582s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 2.765655517578125e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00022077560424804688s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 2.592489719390869s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.2792932987213135s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020256757736206055s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0004010200500488281s
Believability | Calculation of trust value for Family Health History Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-fhho took 2.6450812816619873s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.792213439941406e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.2587285041809082s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.02052617073059082s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0011548995971679688s
Believability | Calculation of trust value for Influenza Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-flu took 2.6944847106933594s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 4.2438507080078125e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.23846006393432617s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.02048659324645996s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007178783416748047s
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 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-fma took 2.639631509780884s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.265669584274292s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.020354032516479492s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00012922286987304688s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-fypo took 2.5864593982696533s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.25528383255004883s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.020772695541381836s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 9.012222290039062e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-geospecies took 2.643198013305664s
Availability | SPARQL endpoint availability check for General Formal Ontology took 5.269050598144531e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.2589740753173828s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00016736984252929688s
Believability | Calculation of trust value for General Formal Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-gfo took 2.5345618724823s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.2438507080078125e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.2698204517364502s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.02062225341796875s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0006299018859863281s
Believability | Calculation of trust value for General Formal Ontology: Biology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-gfo-bio took 2.7094976902008057s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.315376281738281e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.2532942295074463s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.020535945892333984s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008788108825683594s
Believability | Calculation of trust value for Gene Ontology Extension took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-go_x1 took 2.6347169876098633s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Gene Ontology took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.2514793872833252s
Reputation | Calculation of the PageRank for Gene Ontology took 0.020934343338012695s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0008666515350341797s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0009932518005371094s
Believability | Calculation of trust value for Gene Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-go_x2 took 2.6770970821380615s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.5299530029296875e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.26758909225463867s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.02077770233154297s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.218650817871094e-05s
Believability | Calculation of trust value for Cereal Plant Development took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-gro took 2.780247926712036s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.601478576660156e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.26149439811706543s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.020546913146972656s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004487037658691406s
Believability | Calculation of trust value for Cereal plant gross anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-gro_x1 took 2.590636968612671s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 9.298324584960938e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2914469242095947s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02042365074157715s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007293224334716797s
Believability | Calculation of trust value for Gene Regulation Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-gro_x2 took 2.655893087387085s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 6.866455078125e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.2753770351409912s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.02038884162902832s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005626678466796875s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-hao took 2.6639366149902344s
Availability | SPARQL endpoint availability check for HCPCS took 4.100799560546875e-05s
Availability | VoID file availability check for HCPCS took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for HCPCS took 0.28295350074768066s
Reputation | Calculation of the PageRank for HCPCS took 0.0203399658203125s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.0002498626708984375s
Believability | Calculation of trust value for HCPCS took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hcpcs took 2.6505417823791504s
Availability | SPARQL endpoint availability check for Health Level Seven took 4.267692565917969e-05s
Availability | VoID file availability check for Health Level Seven took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.26972103118896484s
Reputation | Calculation of the PageRank for Health Level Seven took 0.02057647705078125s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012912750244140625s
Believability | Calculation of trust value for Health Level Seven took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hl7 took 2.7346982955932617s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 5.6743621826171875e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.28073716163635254s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020292997360229492s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0003418922424316406s
Believability | Calculation of trust value for HEALTH_INDICATORS took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-hlth_indics took 2.6561381816864014s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.00043129920959472656s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.27885937690734863s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.0205690860748291s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.0994415283203125e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-hom took 2.6688919067382812s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.2438507080078125e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.2506716251373291s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.020210981369018555s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.147125244140625e-05s
Believability | Calculation of trust value for HOM-HARVARD took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-hom_harvard took 2.5606534481048584s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 5.3882598876953125e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.2693912982940674s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.0206606388092041s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006883144378662109s
Believability | Calculation of trust value for Human Phenotype Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-hp_x1 took 2.5966176986694336s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.25877857208251953s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.020342111587524414s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0011265277862548828s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hpio took 2.635857105255127s
Availability | SPARQL endpoint availability check for HUGO took 4.1961669921875e-05s
Availability | VoID file availability check for HUGO took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for HUGO took 0.2727022171020508s
Reputation | Calculation of the PageRank for HUGO took 0.020763158798217773s
Interlinking | Calculation of Degree of Connection for HUGO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for HUGO took 8.535385131835938e-05s
Believability | Calculation of trust value for HUGO took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-hugo took 2.6080191135406494s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.2601044178009033s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.021097898483276367s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0007407665252685547s
Believability | Calculation of trust value for Information Artifact Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-iao took 2.6262052059173584s
Availability | SPARQL endpoint availability check for ICD10 took 4.220008850097656e-05s
Availability | VoID file availability check for ICD10 took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for ICD10 took 0.25817108154296875s
Reputation | Calculation of the PageRank for ICD10 took 0.020254135131835938s
Interlinking | Calculation of Degree of Connection for ICD10 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ICD10 took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0007922649383544922s
Believability | Calculation of trust value for ICD10 took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-icd10 took 2.6222574710845947s
Availability | SPARQL endpoint availability check for ICD10CM took 4.172325134277344e-05s
Availability | VoID file availability check for ICD10CM took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.27666473388671875s
Reputation | Calculation of the PageRank for ICD10CM took 0.020333051681518555s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006730556488037109s
Believability | Calculation of trust value for ICD10CM took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icd10cm took 2.7142043113708496s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.935264587402344e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.2724323272705078s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.020267009735107422s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00015211105346679688s
Believability | Calculation of trust value for ICD-10-PCS took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-icd10pcs took 2.657576322555542s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 4.291534423828125e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.24140405654907227s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020729541778564453s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006749629974365234s
Believability | Calculation of trust value for International Classification of Diseases took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-icd9cm took 2.546112060546875s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 6.67572021484375e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.272611141204834s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.020242691040039062s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.000476837158203125s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icf_x1 took 2.667847156524658s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 4.172325134277344e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.24503731727600098s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.020387887954711914s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012166500091552734s
Believability | Calculation of trust value for International Classification for Nursing Practice took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icnp took 2.6189887523651123s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 4.315376281738281e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.2675740718841553s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.020872831344604492s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.00046133995056152344s
Believability | Calculation of trust value for International Classification of Primary Care took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-icpc took 2.638848304748535s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 4.315376281738281e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.2919769287109375s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.02043604850769043s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.00099945068359375s
Believability | Calculation of trust value for ICPC-2 PLUS took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-icpc2p took 2.6015989780426025s
Availability | SPARQL endpoint availability check for ICPS Network took 4.458427429199219e-05s
Availability | VoID file availability check for ICPS Network took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.27171874046325684s
Reputation | Calculation of the PageRank for ICPS Network took 0.020311594009399414s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.0002288818359375s
Believability | Calculation of trust value for ICPS Network took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-icps took 2.5957438945770264s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.23955631256103516s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.021042346954345703s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0009007453918457031s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0010154247283935547s
Believability | Calculation of trust value for Infectious Disease Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ido took 2.605600118637085s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.27112674713134766s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.02055048942565918s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0012578964233398438s
Believability | Calculation of trust value for Brucellosis Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-idobru took 2.6769495010375977s
Availability | SPARQL endpoint availability check for Malaria Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.2854118347167969s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.022664785385131836s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0013730525970458984s
Believability | Calculation of trust value for Malaria Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-idomal took 2.730846405029297s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 4.100799560546875e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.25514817237854004s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007948875427246094s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0003230571746826172s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-iev took 2.6232259273529053s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.4345855712890625e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.2636864185333252s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.02193427085876465s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00018024444580078125s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-imgt took 2.8159232139587402s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.3392181396484375e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0012118816375732422s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.26023244857788086s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020855426788330078s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0009541511535644531s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005924701690673828s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-imr took 2.619601249694824s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.255216121673584s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.020411014556884766s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0008411407470703125s
Believability | Calculation of trust value for Interaction Network Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-ino took 2.677330493927002s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 8.797645568847656e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.2563905715942383s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.020923614501953125s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.2901763916015625e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-invertebrata took 2.613455057144165s
Availability | SPARQL endpoint availability check for IxnO took 4.2438507080078125e-05s
Availability | VoID file availability check for IxnO took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for IxnO took 0.26073479652404785s
Reputation | Calculation of the PageRank for IxnO took 0.020086050033569336s
Interlinking | Calculation of Degree of Connection for IxnO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00018787384033203125s
Believability | Calculation of trust value for IxnO took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ixno took 2.6676077842712402s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.267692565917969e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.2653942108154297s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.020209074020385742s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.00037026405334472656s
Believability | Calculation of trust value for SysMO-JERM took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-jerm took 2.628540515899658s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.27471256256103516s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.02025461196899414s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.504753112792969e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-kisao took 2.6517598628997803s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.124641418457031e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.2812187671661377s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.020279407501220703s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00021648406982421875s
Believability | Calculation of trust value for Loggerhead nesting took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-lhn took 2.6182026863098145s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.2803528308868408s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020442485809326172s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.0002219676971435547s
Believability | Calculation of trust value for Lipid Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-lipro took 2.6642870903015137s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.410743713378906e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.30988216400146484s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.020468473434448242s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.001802206039428711s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-lnc took 3.1570231914520264s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.1484832763671875e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.2776632308959961s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020568132400512695s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006244182586669922s
Believability | Calculation of trust value for Mouse adult gross anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ma took 2.690121650695801s
Availability | SPARQL endpoint availability check for Multiple alignment took 4.172325134277344e-05s
Availability | VoID file availability check for Multiple alignment took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.2796609401702881s
Reputation | Calculation of the PageRank for Multiple alignment took 0.02028799057006836s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00021338462829589844s
Believability | Calculation of trust value for Multiple alignment took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mao took 2.6129109859466553s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.38690185546875e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.24958443641662598s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.020383834838867188s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0007493495941162109s
Believability | Calculation of trust value for Minimal anatomical terminology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mat took 2.60300612449646s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 4.1961669921875e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.28024911880493164s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020428895950317383s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.00041937828063964844s
Believability | Calculation of trust value for Breast tissue cell lines took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mcbcc took 2.6717302799224854s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Cell line ontology took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.26972460746765137s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020087718963623047s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007867813110351562s
Believability | Calculation of trust value for Cell line ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mccl took 2.5988261699676514s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Cell line ontology took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2592778205871582s
Reputation | Calculation of the PageRank for Cell line ontology took 0.02062082290649414s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.00139617919921875s
Believability | Calculation of trust value for Cell line ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 2.7149319648742676s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 4.291534423828125e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.26656460762023926s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.020227909088134766s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.00023698806762695312s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mcv took 2.6633267402648926s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.220008850097656e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.2519845962524414s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.02022409439086914s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00017380714416503906s
Believability | Calculation of trust value for Master Drug Data Base took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mddb took 2.6482057571411133s
Availability | SPARQL endpoint availability check for MedDRA took 4.172325134277344e-05s
Availability | VoID file availability check for MedDRA took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for MedDRA took 0.28386521339416504s
Reputation | Calculation of the PageRank for MedDRA took 0.020235300064086914s
Interlinking | Calculation of Degree of Connection for MedDRA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MedDRA took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011539459228515625s
Believability | Calculation of trust value for MedDRA took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-mdr took 2.6498806476593018s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 4.267692565917969e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0003514289855957031s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.27210044860839844s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.020392417907714844s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008800029754638672s
Believability | Calculation of trust value for MedlinePlus Health Topics took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-medlineplus took 2.6486945152282715s
Availability | SPARQL endpoint availability check for MeGO took 4.2438507080078125e-05s
Availability | VoID file availability check for MeGO took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for MeGO took 0.2725203037261963s
Reputation | Calculation of the PageRank for MeGO took 0.020272016525268555s
Interlinking | Calculation of Degree of Connection for MeGO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MeGO took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.0001621246337890625s
Believability | Calculation of trust value for MeGO took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mego took 2.6039459705352783s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.3392181396484375e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.3402070999145508s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.020554304122924805s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0018024444580078125s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mesh-owl took 3.0337300300598145s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.2452714443206787s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.020383834838867188s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006692409515380859s
Believability | Calculation of trust value for Mental Functioning Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-mf took 2.595984935760498s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.2438507080078125e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.2609288692474365s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.02035665512084961s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005750656127929688s
Believability | Calculation of trust value for Medaka fish anatomy and development took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mfo took 2.5857200622558594s
Availability | SPARQL endpoint availability check for Emotion Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.2597086429595947s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.020211219787597656s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007827281951904297s
Believability | Calculation of trust value for Emotion Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-mfoem took 2.6780548095703125s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.2685227394104004s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.020293712615966797s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00010895729064941406s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mhc took 2.701483964920044s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.220008850097656e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.26546573638916016s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.020113706588745117s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006616115570068359s
Believability | Calculation of trust value for Protein-protein interaction took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mi took 2.625331401824951s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.220008850097656e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.23710966110229492s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020293235778808594s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007464885711669922s
Believability | Calculation of trust value for Mosquito insecticide resistance took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-miro took 2.5612616539001465s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.29496288299560547s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00015473365783691406s
Believability | Calculation of trust value for Measurement Method Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mmo took 2.7503771781921387s
Availability | SPARQL endpoint availability check for MGED Ontology took 5.841255187988281e-05s
Availability | VoID file availability check for MGED Ontology took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.249053955078125s
Reputation | Calculation of the PageRank for MGED Ontology took 0.02081155776977539s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.00039458274841308594s
Believability | Calculation of trust value for MGED Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mo took 2.494196891784668s
Availability | SPARQL endpoint availability check for Protein modification took 4.220008850097656e-05s
Availability | VoID file availability check for Protein modification took 0.0005421638488769531s
Completeness | Calculation of interlinking completeness for Protein modification took 0.27776265144348145s
Reputation | Calculation of the PageRank for Protein modification took 0.020158052444458008s
Interlinking | Calculation of Degree of Connection for Protein modification took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Protein modification took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.0002181529998779297s
Believability | Calculation of trust value for Protein modification took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mod took 2.6851348876953125s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.220008850097656e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.25899767875671387s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.02040243148803711s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.000682830810546875s
Believability | Calculation of trust value for Mammalian phenotype took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mp took 2.7183265686035156s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.7206878662109375e-05s
Availability | VoID file availability check for Mouse pathology took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.25879693031311035s
Reputation | Calculation of the PageRank for Mouse pathology took 0.020262479782104492s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.00048422813415527344s
Believability | Calculation of trust value for Mouse pathology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mpath took 2.6339261531829834s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.291534423828125e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.2667410373687744s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.020339488983154297s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0003936290740966797s
Believability | Calculation of trust value for Mass spectrometry took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ms took 2.6071434020996094s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 4.315376281738281e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0007331371307373047s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.3210639953613281s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020746469497680664s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018856525421142578s
Believability | Calculation of trust value for Medical Subject Headings took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-msh took 3.064528465270996s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 6.985664367675781e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.2786734104156494s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.020451068878173828s
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.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.0002613067626953125s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mthch took 2.6431925296783447s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.25380706787109375s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020529985427856445s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0008420944213867188s
Believability | Calculation of trust value for Natural Products Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-natpro took 2.584317207336426s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 4.410743713378906e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.2628180980682373s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.020416975021362305s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008053779602050781s
Believability | Calculation of trust value for NCBI organismal classification took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 2.6679861545562744s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.3021352291107178s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020687580108642578s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0019876956939697266s
Believability | Calculation of trust value for NCI Thesaurus took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ncit took 3.11350417137146s
Availability | SPARQL endpoint availability check for National Drug Data File took 4.3392181396484375e-05s
Availability | VoID file availability check for National Drug Data File took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.2667684555053711s
Reputation | Calculation of the PageRank for National Drug Data File took 0.02039480209350586s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006577968597412109s
Believability | Calculation of trust value for National Drug Data File took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-nddf took 2.6611435413360596s
Availability | SPARQL endpoint availability check for National Drug File took 4.1961669921875e-05s
Availability | VoID file availability check for National Drug File took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for National Drug File took 0.27210116386413574s
Reputation | Calculation of the PageRank for National Drug File took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for National Drug File took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for National Drug File took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012211799621582031s
Believability | Calculation of trust value for National Drug File took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ndfrt took 2.628523349761963s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.315376281738281e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.283905029296875s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.02025914192199707s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011572837829589844s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 2.688850164413452s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 4.76837158203125e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.26612424850463867s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020499467849731445s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0007202625274658203s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-neomark took 2.6846303939819336s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.2735557556152344s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.02078533172607422s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00012254714965820312s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-neomarkontology took 2.690159320831299s
Availability | SPARQL endpoint availability check for NIFSTD took 7.867813110351562e-05s
Availability | VoID file availability check for NIFSTD took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.32070088386535645s
Reputation | Calculation of the PageRank for NIFSTD took 0.020499467849731445s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.001894235610961914s
Believability | Calculation of trust value for NIFSTD took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nif took 3.0834999084472656s
Availability | SPARQL endpoint availability check for NIF Cell took 4.172325134277344e-05s
Availability | VoID file availability check for NIF Cell took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.28315138816833496s
Reputation | Calculation of the PageRank for NIF Cell took 0.020295381546020508s
Interlinking | Calculation of Degree of Connection for NIF Cell took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013282299041748047s
Believability | Calculation of trust value for NIF Cell took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-nif_cell took 2.6320855617523193s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.315376281738281e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.2811102867126465s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020604610443115234s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0013813972473144531s
Believability | Calculation of trust value for NIF Dysfunction took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 2.6636359691619873s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.2632617950439453s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.020720720291137695s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005526542663574219s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nigo took 2.621368885040283s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 4.2438507080078125e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.2581453323364258s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.02028799057006836s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005652904510498047s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-nmr took 2.611841917037964s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 5.459785461425781e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.28792881965637207s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.020647764205932617s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00011515617370605469s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-nonrctontology took 2.6859068870544434s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.2591845989227295s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020422935485839844s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0011713504791259766s
Believability | Calculation of trust value for NanoParticle Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-npo took 2.500704765319824s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.887580871582031e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.2809140682220459s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.020362138748168945s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007338523864746094s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-oae took 2.6800851821899414s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 4.124641418457031e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.26506876945495605s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.02046370506286621s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0015189647674560547s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-obi took 2.6596529483795166s
Availability | SPARQL endpoint availability check for OBOE took 4.315376281738281e-05s
Availability | VoID file availability check for OBOE took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for OBOE took 0.2674596309661865s
Reputation | Calculation of the PageRank for OBOE took 0.020456314086914062s
Interlinking | Calculation of Degree of Connection for OBOE took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OBOE took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00010895729064941406s
Believability | Calculation of trust value for OBOE took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-oboe took 2.5582518577575684s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.2438507080078125e-05s
Availability | VoID file availability check for OBOE SBC took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.25669097900390625s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020179271697998047s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0008304119110107422s
Believability | Calculation of trust value for OBOE SBC took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 2.692850351333618s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.363059997558594e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.2604343891143799s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020737171173095703s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005979537963867188s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ocre took 2.651055097579956s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 4.267692565917969e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.2604193687438965s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008738040924072266s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-odgi took 2.634061098098755s
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.0005204677581787109s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.26460909843444824s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.02040266990661621s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0009324550628662109s
Believability | Calculation of trust value for Ontology for Genetic Interval took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ogi took 2.5829007625579834s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 4.1961669921875e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.27191853523254395s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.020342111587524414s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.0003216266632080078s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ogmd took 2.6235086917877197s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.2864978313446045s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.020378828048706055s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0007386207580566406s
Believability | Calculation of trust value for Ontology for General Medical Science took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ogms took 2.684185743331909s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.2438507080078125e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.286637544631958s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020589590072631836s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011262893676757812s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-omim took 2.6362197399139404s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.38690185546875e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.00033020973205566406s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.25624704360961914s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020877361297607422s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0008723735809326172s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.00042557716369628906s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-omit took 2.672199249267578s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 5.6743621826171875e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.2709617614746094s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.020666837692260742s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0006201267242431641s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-omrse took 2.4057767391204834s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.2957026958465576s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.020363569259643555s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007648468017578125s
Believability | Calculation of trust value for Ontology of Data Mining took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ontodm took 2.6237404346466064s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.2580282688140869s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.02024102210998535s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.0002644062042236328s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ontodt took 2.7058725357055664s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.291534423828125e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.2538013458251953s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020141124725341797s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.00060272216796875s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ontoorpha took 2.5527329444885254s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 4.38690185546875e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.26061058044433594s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.02023601531982422s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009267330169677734s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-opl took 2.638854742050171s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.315376281738281e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.2555551528930664s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.02032923698425293s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0009429454803466797s
Believability | Calculation of trust value for Phenotypic quality took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-pato took 2.5650670528411865s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.2438507080078125e-05s
Availability | VoID file availability check for Physician Data Query took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.24772167205810547s
Reputation | Calculation of the PageRank for Physician Data Query took 0.020263195037841797s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008556842803955078s
Believability | Calculation of trust value for Physician Data Query took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-pdq took 2.6539790630340576s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.220008850097656e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.23960089683532715s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.02029109001159668s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0007708072662353516s
Believability | Calculation of trust value for Pediatric Terminology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-pedterm took 2.64443302154541s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.2696690559387207s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020320892333984375s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.0002162456512451172s
Believability | Calculation of trust value for Parasite Experiment Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-peo took 2.6070809364318848s
Availability | SPARQL endpoint availability check for PHARE took 4.220008850097656e-05s
Availability | VoID file availability check for PHARE took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for PHARE took 0.2855417728424072s
Reputation | Calculation of the PageRank for PHARE took 0.020315885543823242s
Interlinking | Calculation of Degree of Connection for PHARE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006849765777587891s
Believability | Calculation of trust value for PHARE took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-phare took 2.6743016242980957s
Availability | SPARQL endpoint availability check for PKO_Re took 5.269050598144531e-05s
Availability | VoID file availability check for PKO_Re took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.31134748458862305s
Reputation | Calculation of the PageRank for PKO_Re took 0.020317792892456055s
Interlinking | Calculation of Degree of Connection for PKO_Re took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00016736984252929688s
Believability | Calculation of trust value for PKO_Re took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-pko took 2.7052805423736572s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.291534423828125e-05s
Availability | VoID file availability check for PMA 2010 took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.24283099174499512s
Reputation | Calculation of the PageRank for PMA 2010 took 0.02044820785522461s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0009031295776367188s
Believability | Calculation of trust value for PMA 2010 took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pma took 2.650658130645752s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 4.3392181396484375e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.27008581161499023s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.020342588424682617s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00018835067749023438s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-pmr took 2.63489031791687s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.220008850097656e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.2770512104034424s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.020235538482666016s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.000392913818359375s
Believability | Calculation of trust value for Plant Anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-po took 2.6397929191589355s
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.0005471706390380859s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.26819801330566406s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.020400285720825195s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 7.700920104980469e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-po_x1 took 2.5786893367767334s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Plant Ontology took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.261948823928833s
Reputation | Calculation of the PageRank for Plant Ontology took 0.020394086837768555s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004391670227050781s
Believability | Calculation of trust value for Plant Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-po_x2 took 2.6653835773468018s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 4.7206878662109375e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.26798009872436523s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.020280838012695312s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.00066375732421875s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pr took 2.612602949142456s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.3392181396484375e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.2683889865875244s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.020343303680419922s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.0002574920654296875s
Believability | Calculation of trust value for Proteomics data and process provenance took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-propreo took 2.673671245574951s
Availability | SPARQL endpoint availability check for Pathway ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Pathway ontology took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.26502490043640137s
Reputation | Calculation of the PageRank for Pathway ontology took 0.02037811279296875s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00012922286987304688s
Believability | Calculation of trust value for Pathway ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-pw took 2.5500614643096924s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.26393866539001465s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.020344018936157227s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.0279159545898438e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-qibo took 2.61907696723938s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.291534423828125e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.3127319812774658s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.02043628692626953s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017745494842529297s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-rcd took 3.0912911891937256s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 4.744529724121094e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.2692992687225342s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.02124810218811035s
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.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00014543533325195312s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-rctontology took 2.623497247695923s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.2690548896789551s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.020359516143798828s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.679794311523438e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-repo took 2.571073293685913s
Availability | SPARQL endpoint availability check for Physico-chemical process took 4.38690185546875e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.26099181175231934s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020387887954711914s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00020766258239746094s
Believability | Calculation of trust value for Physico-chemical process took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-rex took 2.612762212753296s
Availability | SPARQL endpoint availability check for RadLex took 4.7206878662109375e-05s
Availability | VoID file availability check for RadLex took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for RadLex took 0.2731924057006836s
Reputation | Calculation of the PageRank for RadLex took 0.02062702178955078s
Interlinking | Calculation of Degree of Connection for RadLex took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0007915496826171875s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.001531362533569336s
Believability | Calculation of trust value for RadLex took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rid took 2.631530523300171s
Availability | SPARQL endpoint availability check for RNA ontology took 4.1961669921875e-05s
Availability | VoID file availability check for RNA ontology took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.2615046501159668s
Reputation | Calculation of the PageRank for RNA ontology took 0.020486116409301758s
Interlinking | Calculation of Degree of Connection for RNA ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005650520324707031s
Believability | Calculation of trust value for RNA ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-rnao took 2.6367456912994385s
Availability | SPARQL endpoint availability check for Role Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Role Ontology took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.27071714401245117s
Reputation | Calculation of the PageRank for Role Ontology took 0.020494699478149414s
Interlinking | Calculation of Degree of Connection for Role Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00018787384033203125s
Believability | Calculation of trust value for Role Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-roleo took 2.6088428497314453s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.28440260887145996s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.020109891891479492s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00017404556274414062s
Believability | Calculation of trust value for Rat Strain Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rs took 2.69177508354187s
Availability | SPARQL endpoint availability check for RxNORM took 4.2438507080078125e-05s
Availability | VoID file availability check for RxNORM took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for RxNORM took 0.24934673309326172s
Reputation | Calculation of the PageRank for RxNORM took 0.020496368408203125s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006661415100097656s
Believability | Calculation of trust value for RxNORM took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-rxnorm took 2.640374183654785s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 6.008148193359375e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.2822458744049072s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.02035379409790039s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010099411010742188s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-sao took 2.6629176139831543s
Availability | SPARQL endpoint availability check for Systems Biology took 4.315376281738281e-05s
Availability | VoID file availability check for Systems Biology took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.25469541549682617s
Reputation | Calculation of the PageRank for Systems Biology took 0.020123004913330078s
Interlinking | Calculation of Degree of Connection for Systems Biology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.00048542022705078125s
Believability | Calculation of trust value for Systems Biology took 3.2901763916015625e-05s
INFO | --- Analysis for bioportal-sbo took 2.6272075176239014s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.29006099700927734s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.020326614379882812s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00011110305786132812s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-sbro took 2.6518754959106445s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.30077600479125977s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.020467042922973633s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0008611679077148438s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0014181137084960938s
Believability | Calculation of trust value for Sleep Domain Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sdo took 2.6409194469451904s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.1961669921875e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.2527186870574951s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.02023148536682129s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003733634948730469s
Believability | Calculation of trust value for Sample processing and separation techniques took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-sep took 2.617661952972412s
Availability | SPARQL endpoint availability check for Student Health Record took 4.2438507080078125e-05s
Availability | VoID file availability check for Student Health Record took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.259753942489624s
Reputation | Calculation of the PageRank for Student Health Record took 0.020113468170166016s
Interlinking | Calculation of Degree of Connection for Student Health Record took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004489421844482422s
Believability | Calculation of trust value for Student Health Record took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-shr took 2.6547012329101562s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.26272034645080566s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.020385265350341797s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.001215219497680664s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sio took 3.290536880493164s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 4.792213439941406e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.2906215190887451s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.02030467987060547s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.0002396106719970703s
Believability | Calculation of trust value for Situation-Based Access Control took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-sitbac took 2.641840934753418s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.410743713378906e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.3026926517486572s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.020528554916381836s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.002016305923461914s
Believability | Calculation of trust value for SNOMED Clinical Terms took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-snomedct took 3.13545298576355s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.2628936767578125s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.020289182662963867s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006821155548095703s
Believability | Calculation of trust value for SNP-Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-snpo took 2.637354612350464s
Availability | SPARQL endpoint availability check for Sequence types and features took 5.173683166503906e-05s
Availability | VoID file availability check for Sequence types and features took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.25142836570739746s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020801782608032227s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005779266357421875s
Believability | Calculation of trust value for Sequence types and features took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-so_x1 took 2.6275572776794434s
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.0005128383636474609s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.30779385566711426s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.020800352096557617s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015895366668701172s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-sopharm took 2.926882743835449s
Availability | SPARQL endpoint availability check for SoyOntology took 4.172325134277344e-05s
Availability | VoID file availability check for SoyOntology took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.26860547065734863s
Reputation | Calculation of the PageRank for SoyOntology took 0.020465850830078125s
Interlinking | Calculation of Degree of Connection for SoyOntology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00013566017150878906s
Believability | Calculation of trust value for SoyOntology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-soy took 2.6046032905578613s
Availability | SPARQL endpoint availability check for Spider Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Spider Ontology took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.2682962417602539s
Reputation | Calculation of the PageRank for Spider Ontology took 0.020370960235595703s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00031375885009765625s
Believability | Calculation of trust value for Spider Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-spd took 2.7158570289611816s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.27089428901672363s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.020675182342529297s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.0002837181091308594s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-spto took 2.579911947250366s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 5.888938903808594e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.25832366943359375s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.02046060562133789s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.00046515464782714844s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-sso took 2.7393198013305664s
Availability | SPARQL endpoint availability check for Software Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Software Ontology took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.2524447441101074s
Reputation | Calculation of the PageRank for Software Ontology took 0.02035808563232422s
Interlinking | Calculation of Degree of Connection for Software Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Software Ontology took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00042366981506347656s
Believability | Calculation of trust value for Software Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-swo took 2.7820801734924316s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.76837158203125e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.25717782974243164s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.020290851593017578s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.0002574920654296875s
Believability | Calculation of trust value for Tick gross anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-tads took 2.6015055179595947s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 5.435943603515625e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.2532989978790283s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.02034616470336914s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008685588836669922s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-tao took 2.6303937435150146s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.1961669921875e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.25554871559143066s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.021586179733276367s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 9.560585021972656e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-taxrank took 2.6305060386657715s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 4.482269287109375e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.2831554412841797s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.020676374435424805s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.43865966796875e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-teddy took 2.7036619186401367s
Availability | SPARQL endpoint availability check for Time Event Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.2669179439544678s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.020560026168823242s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008451938629150391s
Believability | Calculation of trust value for Time Event Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-teo took 2.5810937881469727s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 4.3392181396484375e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.000377655029296875s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.2517421245574951s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.02059149742126465s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.00040030479431152344s
Believability | Calculation of trust value for Mosquito gross anatomy took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-tgma took 2.598781108856201s
Availability | SPARQL endpoint availability check for thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for thesaurus took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for thesaurus took 0.25204992294311523s
Reputation | Calculation of the PageRank for thesaurus took 0.020311594009399414s
Interlinking | Calculation of Degree of Connection for thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for thesaurus took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.67572021484375e-05s
Believability | Calculation of trust value for thesaurus took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-thesaurus took 2.6043665409088135s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.220008850097656e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.25441861152648926s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.02068614959716797s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003712177276611328s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 2.5697531700134277s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.27251553535461426s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.020349502563476562s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.000885009765625s
Believability | Calculation of trust value for Translational Medicine Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-tmo took 2.7343850135803223s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.00048828125s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.2527623176574707s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.02043604850769043s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00015687942504882812s
Believability | Calculation of trust value for Plant Trait Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-to took 2.5830705165863037s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for TOK_Ontology took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.2763514518737793s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.02071976661682129s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00018906593322753906s
Believability | Calculation of trust value for TOK_Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-tok took 2.700282335281372s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.792213439941406e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.24736404418945312s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020425796508789062s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00019168853759765625s
Believability | Calculation of trust value for Teleost taxonomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-tto took 2.6281816959381104s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.27892351150512695s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.021579742431640625s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010139942169189453s
Believability | Calculation of trust value for Uber anatomy ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-uberon took 2.684670925140381s
Availability | SPARQL endpoint availability check for Units Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Units Ontology took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.26909351348876953s
Reputation | Calculation of the PageRank for Units Ontology took 0.020566701889038086s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.00024628639221191406s
Believability | Calculation of trust value for Units Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-unitsontology took 2.7148778438568115s
Availability | SPARQL endpoint availability check for Units of measurement took 4.1961669921875e-05s
Availability | VoID file availability check for Units of measurement took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.2625577449798584s
Reputation | Calculation of the PageRank for Units of measurement took 0.020343542098999023s
Interlinking | Calculation of Degree of Connection for Units of measurement took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0002875328063964844s
Believability | Calculation of trust value for Units of measurement took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-uo took 2.578282356262207s
Availability | SPARQL endpoint availability check for VANDF took 4.1961669921875e-05s
Availability | VoID file availability check for VANDF took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for VANDF took 0.26664280891418457s
Reputation | Calculation of the PageRank for VANDF took 0.0202939510345459s
Interlinking | Calculation of Degree of Connection for VANDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for VANDF took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0006759166717529297s
Believability | Calculation of trust value for VANDF took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-vandf took 2.731311082839966s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 4.744529724121094e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.27715349197387695s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.02022719383239746s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.00041985511779785156s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-vao took 2.6182801723480225s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 4.220008850097656e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.27663373947143555s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.02028203010559082s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006661415100097656s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-vhog took 2.677133083343506s
Availability | SPARQL endpoint availability check for VIVO took 4.2438507080078125e-05s
Availability | VoID file availability check for VIVO took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for VIVO took 0.28908205032348633s
Reputation | Calculation of the PageRank for VIVO took 0.024089336395263672s
Interlinking | Calculation of Degree of Connection for VIVO took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for VIVO took 0.00083160400390625s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.00041031837463378906s
Believability | Calculation of trust value for VIVO took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-vivo took 2.6456525325775146s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 5.4836273193359375e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.2722179889678955s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.020322084426879883s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.001249074935913086s
Believability | Calculation of trust value for Vaccine Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-vo took 2.601524591445923s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.264254093170166s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.02016305923461914s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00020766258239746094s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-vt took 2.54127836227417s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.1961669921875e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.23261022567749023s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020237207412719727s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.00048828125s
Believability | Calculation of trust value for C. elegans gross anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-wbbt took 2.5001511573791504s
Availability | SPARQL endpoint availability check for C. elegans development took 4.2438507080078125e-05s
Availability | VoID file availability check for C. elegans development took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.2605245113372803s
Reputation | Calculation of the PageRank for C. elegans development took 0.020377635955810547s
Interlinking | Calculation of Degree of Connection for C. elegans development took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.4345855712890625e-05s
Believability | Calculation of trust value for C. elegans development took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-wbls took 2.530186414718628s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 4.2438507080078125e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0003581047058105469s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.24225664138793945s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.020279884338378906s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 9.393692016601562e-05s
Believability | Calculation of trust value for C. elegans phenotype took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-wbphenotype took 2.6436219215393066s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 4.124641418457031e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.26116037368774414s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.020247459411621094s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0005962848663330078s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-who took 2.679219961166382s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 4.2438507080078125e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.2447507381439209s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020246505737304688s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006721019744873047s
Believability | Calculation of trust value for Xenopus anatomy and development took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-xao took 2.6116158962249756s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.26981258392333984s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.02046036720275879s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00023794174194335938s
Believability | Calculation of trust value for Experimental Conditions Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-xco took 2.7023987770080566s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 5.2928924560546875e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.23969793319702148s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020275354385375977s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.00027823448181152344s
Believability | Calculation of trust value for Yeast phenotypes took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ypo took 2.57892107963562s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 4.315376281738281e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.25301480293273926s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.02040696144104004s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007543563842773438s
Believability | Calculation of trust value for Zebrafish anatomy and development took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-zfa took 2.601823329925537s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.41788458824157715s
Availability | VoID file availability check for BioSamples RDF took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.2811288833618164s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.021925926208496094s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0008292198181152344s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.719329833984375e-05s
Believability | Calculation of trust value for BioSamples RDF took 7.62939453125e-06s
INFO | --- Analysis for biosamples-rdf took 3.411576986312866s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.512230634689331s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0003635883331298828s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.2518444061279297s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.020520448684692383s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011444091796875s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for bis-linked-data took 2.873931884765625s
Availability | SPARQL endpoint availability check for Bitzi took 7.200241088867188e-05s
Availability | VoID file availability check for Bitzi took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Bitzi took 0.25539445877075195s
Reputation | Calculation of the PageRank for Bitzi took 0.02051520347595215s
Interlinking | Calculation of Degree of Connection for Bitzi took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bitzi took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Bitzi took 3.0040740966796875e-05s
Believability | Calculation of trust value for Bitzi took 7.62939453125e-06s
INFO | --- Analysis for bitzi took 2.8902840614318848s
Availability | SPARQL endpoint availability check for BizkaiSense took 4.1484832763671875e-05s
Availability | VoID file availability check for BizkaiSense took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.255035400390625s
Reputation | Calculation of the PageRank for BizkaiSense took 0.020308732986450195s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 3.0994415283203125e-05s
Believability | Calculation of trust value for BizkaiSense took 7.3909759521484375e-06s
INFO | --- Analysis for bizkaisense took 2.907895565032959s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.100799560546875e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.26860642433166504s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020273923873901367s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.647804260253906e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.62939453125e-06s
INFO | --- Analysis for blabla-itemlist took 2.9475512504577637s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.076957702636719e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0002868175506591797s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.2537827491760254s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020434141159057617s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.1948089599609375e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.3909759521484375e-06s
INFO | --- Analysis for blabla_itemlist took 2.9207630157470703s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.3613662719726562s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0007524490356445312s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.2777731418609619s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.02046966552734375s
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.0007956027984619141s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.914138793945312e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 5.9604644775390625e-06s
INFO | --- Analysis for bluk-bnb took 13.78221344947815s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 17.979896306991577s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007565021514892578s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 21.23378825187683s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 18.37256407737732s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 18.00908851623535s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 70.42823243141174s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.2408883571624756s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 10.200906038284302s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 30.3365740776062s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 29.36925745010376s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4056422710418701s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 26.262375593185425s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 30.341598749160767s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 24.242412090301514s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 29.522958278656006s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 50.46667504310608s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 30.317045211791992s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 15.756672859191895s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 24.992191791534424s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.2901763916015625e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.315066337585449s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.005668878555298s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 19.624221086502075s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 17.461276531219482s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 18.29052209854126s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 24.68286919593811s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.868209362030029s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 25.907519340515137s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.690906763076782s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.40167498588562s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.352036714553833s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.245896100997925s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030950069427490234s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02685999870300293s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.450894832611084s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 30.126360654830933s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 14.056488513946533s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.09885311126709s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.277054786682129s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 26.632967948913574s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030058622360229492s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 19.971924543380737s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 8.789042472839355s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 10.94194483757019s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7199208736419678s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.020760297775268555s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 9.584426879882812e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.76837158203125e-07s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.3909759521484375e-06s
INFO | --- Analysis for bpr took 4994.67391037941s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 4.76837158203125e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.7233374118804932s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.020679712295532227s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0010113716125488281s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 0.00010943412780761719s
Believability | Calculation of trust value for Brazilian Politicians took 5.9604644775390625e-06s
INFO | --- Analysis for brazilian-politicians took 4.2974629402160645s
Availability | SPARQL endpoint availability check for BrazilianCities took 4.124641418457031e-05s
Availability | VoID file availability check for BrazilianCities took 0.00031876564025878906s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.27209949493408203s
Reputation | Calculation of the PageRank for BrazilianCities took 0.020464658737182617s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 5.14984130859375e-05s
Believability | Calculation of trust value for BrazilianCities took 8.821487426757812e-06s
INFO | --- Analysis for braziliancities took 4.25356125831604s
Availability | SPARQL endpoint availability check for Bricklink took 1.5768322944641113s
Availability | VoID file availability check for Bricklink took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Bricklink took 0.2585892677307129s
Reputation | Calculation of the PageRank for Bricklink took 0.020386934280395508s
Interlinking | Calculation of Degree of Connection for Bricklink took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bricklink took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Bricklink took 7.843971252441406e-05s
Believability | Calculation of trust value for Bricklink took 8.344650268554688e-06s
INFO | --- Analysis for bricklink took 10.40022897720337s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.316842079162598s
Availability | VoID file availability check for British Museum Collection took 0.0004150867462158203s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.26407766342163086s
Reputation | Calculation of the PageRank for British Museum Collection took 0.021233558654785156s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.790855407714844e-05s
Believability | Calculation of trust value for British Museum Collection took 8.58306884765625e-06s
INFO | --- Analysis for british-museum-collection took 73.2552592754364s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 5.054473876953125e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0009222030639648438s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.27626705169677734s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.020326852798461914s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 3.6716461181640625e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 6.9141387939453125e-06s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 3.5005056858062744s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 4.0531158447265625e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.2644011974334717s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.02022075653076172s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 2.7894973754882812e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 7.867813110351562e-06s
INFO | --- Analysis for bsv took 3.3757236003875732s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 4.267692565917969e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.0003228187561035156s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.27469563484191895s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.020894527435302734s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 3.075599670410156e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 1.8835067749023438e-05s
INFO | --- Analysis for bund-offener-haushalt took 2.8425850868225098s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 4.100799560546875e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.2694716453552246s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.020179271697998047s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 2.9087066650390625e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 7.152557373046875e-06s
INFO | --- Analysis for bundestagnebeneinkuenfte took 3.255281448364258s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.27612757682800293s
Availability | VoID file availability check for business.data.gov.uk took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.25835680961608887s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.02045464515686035s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007510185241699219s
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.769071578979492s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 4.291534423828125e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.272122859954834s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.020314931869506836s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 3.0994415283203125e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 7.3909759521484375e-06s
INFO | --- Analysis for cabbage took 2.911111354827881s
Availability | SPARQL endpoint availability check for cablegate took 1.462160348892212s
Availability | VoID file availability check for cablegate took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for cablegate took 0.2676818370819092s
Reputation | Calculation of the PageRank for cablegate took 0.020245075225830078s
Interlinking | Calculation of Degree of Connection for cablegate took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for cablegate took 8.797645568847656e-05s
Believability | Calculation of trust value for cablegate took 6.9141387939453125e-06s
INFO | --- Analysis for cablegate took 16.7494215965271s
Availability | SPARQL endpoint availability check for Calames took 4.38690185546875e-05s
Availability | VoID file availability check for Calames took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for Calames took 0.2470550537109375s
Reputation | Calculation of the PageRank for Calames took 0.020470380783081055s
Interlinking | Calculation of Degree of Connection for Calames took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Calames took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Calames took 4.6253204345703125e-05s
Believability | Calculation of trust value for Calames took 7.62939453125e-06s
INFO | --- Analysis for calames took 4.172936916351318s
Availability | SPARQL endpoint availability check for can-link took 4.1484832763671875e-05s
Availability | VoID file availability check for can-link took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for can-link took 0.26656556129455566s
Reputation | Calculation of the PageRank for can-link took 0.020320653915405273s
Interlinking | Calculation of Degree of Connection for can-link took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for can-link took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for can-link took 2.9802322387695312e-05s
Believability | Calculation of trust value for can-link took 7.152557373046875e-06s
INFO | --- Analysis for can-link took 2.99605655670166s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.07906055450439453s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.2831535339355469s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.020991802215576172s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 7.62939453125e-06s
INFO | --- Analysis for cap-italy-rdf took 2.593778371810913s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 4.291534423828125e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.24401164054870605s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020573139190673828s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 3.933906555175781e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 9.298324584960938e-06s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 2.899977684020996s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 4.1961669921875e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.281109094619751s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.020295143127441406s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 2.9325485229492188e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 8.344650268554688e-06s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 2.9961037635803223s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.4345855712890625e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0003077983856201172s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.26662158966064453s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.020367860794067383s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00010037422180175781s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 6.67572021484375e-06s
INFO | --- Analysis for ce4r took 15.163718700408936s
Availability | SPARQL endpoint availability check for Charging Stations took 4.3392181396484375e-05s
Availability | VoID file availability check for Charging Stations took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.27963781356811523s
Reputation | Calculation of the PageRank for Charging Stations took 0.02074742317199707s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 3.075599670410156e-05s
Believability | Calculation of trust value for Charging Stations took 8.58306884765625e-06s
INFO | --- Analysis for charging-stations took 2.9850971698760986s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.3392181396484375e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0007383823394775391s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.28218913078308105s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.020517826080322266s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.62396240234375e-05s
Believability | Calculation of trust value for Chat Game corpus took 8.106231689453125e-06s
INFO | --- Analysis for chat-game-corpus took 12.565730810165405s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 6.794929504394531e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.2907588481903076s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.02088618278503418s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.552436828613281e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 8.821487426757812e-06s
INFO | --- Analysis for chebi took 2.989511489868164s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.410743713378906e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0008494853973388672s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.26315760612487793s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.020944833755493164s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0011200904846191406s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 6.508827209472656e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 7.3909759521484375e-06s
INFO | --- Analysis for chem2bio2rdf took 134.72487449645996s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.48542046546936035s
Availability | VoID file availability check for ChEMBL RDF took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.24809527397155762s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.02008962631225586s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 4.9114227294921875e-05s
Believability | Calculation of trust value for ChEMBL RDF took 8.106231689453125e-06s
INFO | --- Analysis for chembl-rdf took 3.5000526905059814s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 5.054473876953125e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0007753372192382812s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.29496026039123535s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.02025318145751953s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 2.9087066650390625e-05s
Believability | Calculation of trust value for ChemPedia RDF took 7.62939453125e-06s
INFO | --- Analysis for chempedia-rdf took 8.688649654388428s
Availability | SPARQL endpoint availability check for Chronicling America took 4.506111145019531e-05s
Availability | VoID file availability check for Chronicling America took 0.0007143020629882812s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.27228307723999023s
Reputation | Calculation of the PageRank for Chronicling America took 0.02048206329345703s
Interlinking | Calculation of Degree of Connection for Chronicling America took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.0001049041748046875s
Believability | Calculation of trust value for Chronicling America took 8.344650268554688e-06s
INFO | --- Analysis for chronicling-america took 6.740097522735596s
Availability | SPARQL endpoint availability check for ciard-ring took 4.3392181396484375e-05s
Availability | VoID file availability check for ciard-ring took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.2633495330810547s
Reputation | Calculation of the PageRank for ciard-ring took 0.02060246467590332s
Interlinking | Calculation of Degree of Connection for ciard-ring took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.553794860839844e-05s
Believability | Calculation of trust value for ciard-ring took 7.867813110351562e-06s
INFO | --- Analysis for ciard-ring took 3.269620895385742s
Availability | SPARQL endpoint availability check for CIPFA took 7.510185241699219e-05s
Availability | VoID file availability check for CIPFA took 0.0006682872772216797s
Completeness | Calculation of interlinking completeness for CIPFA took 0.28619384765625s
Reputation | Calculation of the PageRank for CIPFA took 0.02060532569885254s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.5762786865234375e-05s
Believability | Calculation of trust value for CIPFA took 5.9604644775390625e-06s
INFO | --- Analysis for cipfa took 2.715451240539551s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 0.3000829219818115s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.2689495086669922s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.02031087875366211s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.0003886222839355469s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 6.4373016357421875e-06s
INFO | --- Analysis for ckan took 2.9420065879821777s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 1.7788383960723877s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.2698800563812256s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.02062225341796875s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0010085105895996094s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 0.00010824203491210938s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 5.7220458984375e-06s
INFO | --- Analysis for clean-energy-data-reegle took 11.351487874984741s
Availability | SPARQL endpoint availability check for CLLD-afbo took 6.103515625e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.2711920738220215s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.021641969680786133s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0010156631469726562s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 9.465217590332031e-05s
Believability | Calculation of trust value for CLLD-afbo took 1.2874603271484375e-05s
INFO | --- Analysis for clld-afbo took 3.405726671218872s
Availability | SPARQL endpoint availability check for CLLD-APICS took 4.363059997558594e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0011370182037353516s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.25534987449645996s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.020438194274902344s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 9.584426879882812e-05s
Believability | Calculation of trust value for CLLD-APICS took 8.58306884765625e-06s
INFO | --- Analysis for clld-apics took 3.55997896194458s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.291534423828125e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0006020069122314453s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.2685236930847168s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.020697832107543945s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 4.172325134277344e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 8.821487426757812e-06s
INFO | --- Analysis for clld-ewave took 3.5363752841949463s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 4.410743713378906e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.2900693416595459s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.03593850135803223s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0015676021575927734s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00016736984252929688s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 1.2636184692382812e-05s
INFO | --- Analysis for clld-glottolog took 3.4292027950286865s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.410743713378906e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0011150836944580078s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.2779252529144287s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.020172834396362305s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 9.083747863769531e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 7.3909759521484375e-06s
INFO | --- Analysis for clld-phoible took 3.531512498855591s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 4.363059997558594e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.26404547691345215s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.021733999252319336s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0008215904235839844s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 8.225440979003906e-05s
Believability | Calculation of trust value for CLLD-SAILS took 7.152557373046875e-06s
INFO | --- Analysis for clld-sails took 3.5506532192230225s
Availability | SPARQL endpoint availability check for CLLD-WALS took 5.316734313964844e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.26506519317626953s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.02050471305847168s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 9.083747863769531e-05s
Believability | Calculation of trust value for CLLD-WALS took 7.62939453125e-06s
INFO | --- Analysis for clld-wals took 3.4137606620788574s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.38690185546875e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0012428760528564453s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.291642427444458s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.02283453941345215s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 8.20159912109375e-05s
Believability | Calculation of trust value for CLLD-WOLD took 7.62939453125e-06s
INFO | --- Analysis for clld-wold took 3.5713775157928467s
Availability | SPARQL endpoint availability check for COD inventory took 4.553794860839844e-05s
Availability | VoID file availability check for COD inventory took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for COD inventory took 0.2686736583709717s
Reputation | Calculation of the PageRank for COD inventory took 0.020430564880371094s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for COD inventory took 3.24249267578125e-05s
Believability | Calculation of trust value for COD inventory took 7.152557373046875e-06s
INFO | --- Analysis for cod-inventory took 3.015834331512451s
Availability | SPARQL endpoint availability check for CODE Endpoint took 5.53131103515625e-05s
Availability | VoID file availability check for CODE Endpoint took 0.00032591819763183594s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.2663259506225586s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.021651744842529297s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0010080337524414062s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 3.552436828613281e-05s
Believability | Calculation of trust value for CODE Endpoint took 8.344650268554688e-06s
INFO | --- Analysis for code-endpoint took 2.9738941192626953s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 0.5260002613067627s
Availability | VoID file availability check for OpenUpLabs COINS took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.2726576328277588s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.020412206649780273s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 2.8848648071289062e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 5.0067901611328125e-06s
INFO | --- Analysis for coins-openuplabs took 2.9407222270965576s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.05065202713012695s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.2740006446838379s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.02045750617980957s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.814697265625e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for colinda took 2.5065085887908936s
Availability | SPARQL endpoint availability check for CN  2012 took 25.0523202419281s
Availability | VoID file availability check for CN  2012 took 0.0008144378662109375s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.2976071834564209s
Reputation | Calculation of the PageRank for CN  2012 took 0.020432233810424805s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 3.457069396972656e-05s
Believability | Calculation of trust value for CN  2012 took 6.4373016357421875e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 123.87937450408936s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 4.2438507080078125e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.2843611240386963s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.021179676055908203s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.000904083251953125s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 3.409385681152344e-05s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 8.58306884765625e-06s
INFO | --- Analysis for comments-on-literature-in-literature took 3.050633668899536s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 4.172325134277344e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.26761746406555176s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 2.9802322387695312e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 7.62939453125e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 2.9490702152252197s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 4.1961669921875e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.2649250030517578s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.02062058448791504s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 3.0279159545898438e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 8.106231689453125e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 2.9029011726379395s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 4.124641418457031e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.2805976867675781s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.020842552185058594s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0008707046508789062s
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 9.5367431640625e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 2.9257912635803223s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 5.269050598144531e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.2581298351287842s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.02069687843322754s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 3.170967102050781e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 9.059906005859375e-06s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 2.932222604751587s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 2.7134103775024414s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.2813711166381836s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.020383119583129883s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.409385681152344e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 7.867813110351562e-06s
INFO | --- Analysis for comsode-d3-2 took 8.35087251663208s
Availability | SPARQL endpoint availability check for ConceptNet took 5.269050598144531e-05s
Availability | VoID file availability check for ConceptNet took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.26939821243286133s
Reputation | Calculation of the PageRank for ConceptNet took 0.020831584930419922s
Interlinking | Calculation of Degree of Connection for ConceptNet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ConceptNet took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 3.886222839355469e-05s
Believability | Calculation of trust value for ConceptNet took 7.867813110351562e-06s
INFO | --- Analysis for conceptnet took 2.9411258697509766s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 7.224082946777344e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.2796592712402344s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.020779132843017578s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 3.123283386230469e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 7.867813110351562e-06s
INFO | --- Analysis for connectivity-of-lod-datasets took 2.92958664894104s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 4.1484832763671875e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.24873948097229004s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.02042675018310547s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 2.9802322387695312e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 8.344650268554688e-06s
INFO | --- Analysis for copac-library-catalogue took 2.918123960494995s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 4.4345855712890625e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.251009464263916s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.021062135696411133s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0008172988891601562s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 8.416175842285156e-05s
Believability | Calculation of trust value for CopyrightTermBank took 7.62939453125e-06s
INFO | --- Analysis for copyrighttermbank took 35.31664276123047s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 1.643237590789795s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0008227825164794922s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.2674694061279297s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020215511322021484s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.790855407714844e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 8.821487426757812e-06s
INFO | --- Analysis for core took 6.646429538726807s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 4.172325134277344e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.23736119270324707s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.020340919494628906s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 2.7894973754882812e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 6.9141387939453125e-06s
INFO | --- Analysis for corn took 2.9558675289154053s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 4.076957702636719e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.2584550380706787s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.020378828048706055s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0008180141448974609s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 3.1948089599609375e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 7.152557373046875e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 2.8741321563720703s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 4.0531158447265625e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.2572944164276123s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.020296573638916016s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 2.9802322387695312e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.9311904907226562e-05s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 2.858375310897827s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 5.53131103515625e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.262070894241333s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.02022242546081543s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.841255187988281e-05s
Believability | Calculation of trust value for Cornetto1.2 took 6.4373016357421875e-06s
INFO | --- Analysis for cornetto took 12.421130657196045s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 4.124641418457031e-05s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.270831823348999s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.020482540130615234s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 2.765655517578125e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for corscheck took 3.0132977962493896s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.06778144836425781s
Availability | VoID file availability check for Courts thesaurus took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.2526075839996338s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.020736217498779297s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 7.104873657226562e-05s
Believability | Calculation of trust value for Courts thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for courts-thesaurus took 2.399596929550171s
Availability | SPARQL endpoint availability check for CPA 2008 took 24.48390483856201s
Availability | VoID file availability check for CPA 2008 took 0.0008783340454101562s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.36132073402404785s
Reputation | Calculation of the PageRank for CPA 2008 took 0.021251916885375977s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 4.291534423828125e-05s
Believability | Calculation of trust value for CPA 2008 took 5.7220458984375e-06s
INFO | --- Analysis for cpa-2008 took 130.91385054588318s
Availability | SPARQL endpoint availability check for CPC 2008 took 27.351555824279785s
Availability | VoID file availability check for CPC 2008 took 0.0008442401885986328s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.27457308769226074s
Reputation | Calculation of the PageRank for CPC 2008 took 0.02091670036315918s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 4.9114227294921875e-05s
Believability | Calculation of trust value for CPC 2008 took 1.049041748046875e-05s
INFO | --- Analysis for cpc-2008 took 126.24410247802734s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.56582736968994s
Availability | VoID file availability check for CPV  2003 took 0.0008108615875244141s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.7093806266784668s
Reputation | Calculation of the PageRank for CPV  2003 took 0.020893096923828125s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 4.100799560546875e-05s
Believability | Calculation of trust value for CPV  2003 took 5.9604644775390625e-06s
INFO | --- Analysis for cpv-2003 took 115.14695501327515s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.340861558914185s
Availability | VoID file availability check for CPV 2008 took 0.0009007453918457031s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.2660956382751465s
Reputation | Calculation of the PageRank for CPV 2008 took 0.020288944244384766s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 4.649162292480469e-05s
Believability | Calculation of trust value for CPV 2008 took 5.9604644775390625e-06s
INFO | --- Analysis for cpv-2008 took 131.54166555404663s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 260.25375175476074s
Availability | VoID file availability check for crowdsourcing-fb took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.7165405750274658s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.458427429199219e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 7.62939453125e-06s
INFO | --- Analysis for crowdsourcing-fb took 535.2317390441895s
Availability | SPARQL endpoint availability check for CRTM took 4.506111145019531e-05s
Availability | VoID file availability check for CRTM took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for CRTM took 0.2634410858154297s
Reputation | Calculation of the PageRank for CRTM took 0.020353078842163086s
Interlinking | Calculation of Degree of Connection for CRTM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for CRTM took 2.8848648071289062e-05s
Believability | Calculation of trust value for CRTM took 7.62939453125e-06s
INFO | --- Analysis for crtm took 3.917444944381714s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 4.315376281738281e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.25693845748901367s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.020587682723999023s
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.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 3.075599670410156e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 7.62939453125e-06s
INFO | --- Analysis for crystal-eye took 3.032106876373291s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 7.213266849517822s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.31987571716308594s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.02042388916015625s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 4.863739013671875e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 6.67572021484375e-06s
INFO | --- Analysis for ctic-public-dataset took 45.309208154678345s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 4.029273986816406e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.29148006439208984s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.02056097984313965s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 2.9087066650390625e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 7.867813110351562e-06s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 3.046525001525879s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.5597150325775146s
Availability | VoID file availability check for CulturaLinkedData took 0.0005791187286376953s
Extra | Recovery of all triples for CulturaLinkedData took 133.64023661613464s
Performance | Total latancy measurement for CulturaLinkedData took 4.567877769470215s
Amount of data | Number of triples check for CulturaLinkedData took 4.989877939224243s
Interoperability | New terms check for CulturaLinkedData took 2.2104907035827637s
Versatility | Languages check for CulturaLinkedData took 62.23901915550232s
Interpretability | Number of blank nodes check for CulturaLinkedData took 2.024876117706299s
Interpretability | RDF structures check for CulturaLinkedData took 0.47113823890686035s
Versatility | Serialization formats check for CulturaLinkedData took 0.49800968170166016s
Availability | RDF dump link check for CulturaLinkedData took 2.0843923091888428s
License | MR license check for CulturaLinkedData took 0.73014235496521s
License | HR license check for CulturaLinkedData took 65.4269790649414s
Amount of data | Number of property check for CulturaLinkedData took 0.20238780975341797s
Understandability | Number of label check for CulturaLinkedData took 2.9413833618164062s
Understandability | URI regex check for CulturaLinkedData took 2.2995381355285645s
Understandability | Vocabs check for CulturaLinkedData took 2.091358184814453s
Verifiability | Authors check for CulturaLinkedData took 2.049311637878418s
Verifiability | Publishers check for CulturaLinkedData took 0.2760918140411377s
Performance | Throughput check for CulturaLinkedData took 21.991910219192505s
Amount of data | Check the number of entities for CulturaLinkedData took 6.127357482910156e-05s
Verifiability | Contribs. check for CulturaLinkedData took 0.2458202838897705s
Interlinking | sameAs chians check for CulturaLinkedData took 0.3921079635620117s
Interlinking | skos check for CulturaLinkedData took 0.5608539581298828s
Interlinking | skos check for CulturaLinkedData took 0.1820516586303711s
Timeliness | dataset update frequency check for CulturaLinkedData took 2.1390717029571533s
Currency | Creation date check for CulturaLinkedData took 0.45614027976989746s
Currency | Modification date check for CulturaLinkedData took 0.3692905902862549s
Rep.Conc. | URIs length for CulturaLinkedData took 66.12179756164551s
Interoperability | New vocabularies check for CulturaLinkedData took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 1.8850867748260498s
Accuracy | Check Functional Property for CulturaLinkedData took 0.1846010684967041s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 1.8969862461090088s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 40.2711296081543s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.613077163696289s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.3352303504943848s
Consistency | Disjoint class check for CulturaLinkedData took 2.013457775115967s
Consistency | Check Misplaced properties for CulturaLinkedData took 14.172054290771484s
Consistency | Misplaced classes for CulturaLinkedData took 4.137160301208496s
Consistency | Check Ontology hijacking for CulturaLinkedData took 44.29771327972412s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.3794846534729004s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 9.58779788017273s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.3848421573638916s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 2.0298006534576416s
Security | Sign check for CulturaLinkedData took 2.886901617050171s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 10.818388223648071s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.322094202041626s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.02107858657836914s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 4.1961669921875e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 1.9073486328125e-06s
Believability | Calculation of trust value for CulturaLinkedData took 7.152557373046875e-06s
INFO | --- Analysis for culturalinkeddata took 648.8720123767853s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.1378772258758545s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0008356571197509766s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.7425353527069092s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.020404338836669922s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 4.6253204345703125e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 6.67572021484375e-06s
INFO | --- Analysis for cz-ares-or took 4.043972015380859s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.11796927452087402s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.6753406524658203s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.02021622657775879s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.4332275390625e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 6.198883056640625e-06s
INFO | --- Analysis for cz-ares-rzp took 3.9681999683380127s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.10628557205200195s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.00043201446533203125s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.25598716735839844s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.020406246185302734s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.361701965332031e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 5.4836273193359375e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 2.8042171001434326s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.09502363204956055s
Availability | VoID file availability check for Integrated pollution registry took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.2607269287109375s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.020627737045288086s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.6716461181640625e-05s
Believability | Calculation of trust value for Integrated pollution registry took 5.4836273193359375e-06s
INFO | --- Analysis for cz-cenia-pollution took 3.219120740890503s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.11578798294067383s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.2639307975769043s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.020364999771118164s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.504753112792969e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 5.4836273193359375e-06s
INFO | --- Analysis for cz-contracts took 3.188404083251953s
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.00028395652770996094s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.2671995162963867s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.020313262939453125s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 3.0040740966796875e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 7.867813110351562e-06s
INFO | --- Analysis for cz-courts took 2.9011173248291016s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.1126101016998291s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.25794553756713867s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.02097487449645996s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.4809112548828125e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 1.0251998901367188e-05s
INFO | --- Analysis for cz-ctia-bans took 5.018897294998169s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.11711716651916504s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0008094310760498047s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.27500462532043457s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020224332809448242s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.933906555175781e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ctia-confiscations took 2.707240104675293s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.10502123832702637s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.28586268424987793s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.020417451858520508s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.4332275390625e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 5.9604644775390625e-06s
INFO | --- Analysis for cz-ctia-focus took 2.7969324588775635s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.10494637489318848s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.2457139492034912s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020578384399414062s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.124641418457031e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ctia-inspections took 2.7278923988342285s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.1096954345703125s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.718982458114624s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.020833492279052734s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.743171691894531e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 5.7220458984375e-06s
INFO | --- Analysis for cz-ctia-sanctions took 5.120540618896484s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.1575477123260498s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.2632889747619629s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.020276308059692383s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 3.719329833984375e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 5.7220458984375e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 2.7786550521850586s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.10830807685852051s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.2515881061553955s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.020267486572265625s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.266334533691406e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 9.775161743164062e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 2.7296340465545654s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 1.0081775188446045s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.2584385871887207s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.020444393157958984s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.9577484130859375e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-average-salaries took 3.956886053085327s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.40562891960144043s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.25892090797424316s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.020260095596313477s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 3.7670135498046875e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 5.7220458984375e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.285794258117676s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.3874549865722656s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.24511432647705078s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.020446300506591797s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.029273986816406e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.337203025817871s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.41803765296936035s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0010530948638916016s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.2540912628173828s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.020534276962280273s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 4.100799560546875e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 5.9604644775390625e-06s
INFO | --- Analysis for cz-czso-job-applicants took 3.268798828125s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.37012267112731934s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.2687528133392334s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.02078866958618164s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 4.649162292480469e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.2706027030944824s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.3909037113189697s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.25400662422180176s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.02065873146057129s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.814697265625e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-regions took 3.043419122695923s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.40093231201171875s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.2898674011230469s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.02080059051513672s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 4.57763671875e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 1.430511474609375e-05s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.3220763206481934s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.3829071521759033s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.2546553611755371s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.021008014678955078s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 4.172325134277344e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 5.7220458984375e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.2265286445617676s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.40756988525390625s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.26685476303100586s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.020701169967651367s
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.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 4.172325134277344e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 3.281751871109009s
Availability | SPARQL endpoint availability check for ATC groups took 0.10878133773803711s
Availability | VoID file availability check for ATC groups took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for ATC groups took 0.26382017135620117s
Reputation | Calculation of the PageRank for ATC groups took 0.020670175552368164s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0008432865142822266s
Interlinking | Calculation of Clustering coefficient for ATC groups took 6.914138793945312e-05s
Believability | Calculation of trust value for ATC groups took 6.9141387939453125e-06s
INFO | --- Analysis for cz-eh-1-atc took 2.7024168968200684s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.11260104179382324s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.2718691825866699s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.020741701126098633s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.6716461181640625e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 9.059906005859375e-06s
INFO | --- Analysis for cz-fulfillments took 2.705824375152588s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.029601097106933594s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0006165504455566406s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.27413415908813477s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.020396709442138672s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.8160552978515625e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 6.198883056640625e-06s
INFO | --- Analysis for cz-ic took 3.446607828140259s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.22825050354003906s
Availability | VoID file availability check for List of Czech data boxes took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.25235414505004883s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.020695924758911133s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 3.3855438232421875e-05s
Believability | Calculation of trust value for List of Czech data boxes took 5.0067901611328125e-06s
INFO | --- Analysis for cz-list-of-databoxes took 4.284339189529419s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.23259854316711426s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.24093151092529297s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.02063131332397461s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.170967102050781e-05s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 4.5299530029296875e-06s
INFO | --- Analysis for cz-nace took 4.2302405834198s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2787058353424072s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0005536079406738281s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 45.73891735076904s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8039052486419678s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2934105396270752s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.6053974628448486s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 18.469510555267334s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5296859741210938s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17336559295654297s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.3555207252502441s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5555510520935059s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3804471492767334s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5732421875s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.20275020599365234s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.7506253719329834s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3606133460998535s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2231903076171875s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2383120059967041s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.299177885055542s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.2 took 10.28803539276123s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.2 took 7.939338684082031e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16849994659423828s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.211195707321167s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3478829860687256s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.14987421035766602s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.972442626953125s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.42150115966796875s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3686838150024414s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.2 took 66.35127902030945s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.18610239028930664s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.18319964408874512s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1701047420501709s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.2 took 50.1403923034668s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.4347214698791504s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.6908411979675293s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.20131134986877441s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.7686691284179688s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.589598655700684s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.2 took 81.23395204544067s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.633342981338501s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.9973046779632568s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.0891807079315186s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.23621416091918945s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4278073310852051s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.2 took 1170.0405938625336s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.5315403938293457s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.023015975952148438s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 6.794929504394531e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 9.846687316894531e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.6689300537109375e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 7.152557373046875e-06s
INFO | --- Analysis for cz-nkod took 66539.81824493408s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.24120306968688965s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.2831125259399414s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.020129919052124023s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.457069396972656e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 5.0067901611328125e-06s
INFO | --- Analysis for cz-orders took 3.8957607746124268s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.3112504482269287s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.25411224365234375s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.020281314849853516s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 4.38690185546875e-05s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-ovm took 5.663151502609253s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.10434985160827637s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0004169940948486328s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.27904272079467773s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.0204010009765625s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.457069396972656e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 5.7220458984375e-06s
INFO | --- Analysis for cz-ovm-agendas took 3.6171438694000244s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.29161977767944336s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0002803802490234375s
Extra | Recovery of all triples for Registry of territorial identification, addresses and real estate of the Czech Republic took 109.99049925804138s
Performance | Total latancy measurement for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.5771358013153076s
Amount of data | Number of triples check for Registry of territorial identification, addresses and real estate of the Czech Republic took 45.78673553466797s
Interoperability | New terms check for Registry of territorial identification, addresses and real estate of the Czech Republic took 21.39205574989319s
Versatility | Languages check for Registry of territorial identification, addresses and real estate of the Czech Republic took 300.1864368915558s
Interpretability | Number of blank nodes check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2470099925994873s
Interpretability | RDF structures check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.6241021156311035s
Versatility | Serialization formats check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12968158721923828s
Availability | RDF dump link check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.793879508972168s
License | MR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11115455627441406s
License | HR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1059560775756836s
Amount of data | Number of property check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10505509376525879s
Understandability | Number of label check for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.3215651512145996s
Understandability | URI regex check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.21680665016174316s
Understandability | Vocabs check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10982966423034668s
Verifiability | Authors check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.15259504318237305s
Verifiability | Publishers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10330867767333984s
Performance | Throughput check for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.247434616088867s
Amount of data | Check the number of entities for Registry of territorial identification, addresses and real estate of the Czech Republic took 3.266334533691406e-05s
Verifiability | Contribs. check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11243367195129395s
Interlinking | sameAs chians check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13589763641357422s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12371492385864258s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11281919479370117s
Timeliness | dataset update frequency check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11563706398010254s
Currency | Creation date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2546567916870117s
Currency | Modification date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12336540222167969s
Rep.Conc. | URIs length for Registry of territorial identification, addresses and real estate of the Czech Republic took 156.9884901046753s
Interoperability | New vocabularies check for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11200809478759766s
Accuracy | Check Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12196803092956543s
Accuracy | Check Inverse Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12789535522460938s
Accuracy | Check Empty annotation labels for Registry of territorial identification, addresses and real estate of the Czech Republic took 21.547861576080322s
Accuracy | Check White space in annotation for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.2751963138580322s
Accuracy | Check Datatype consistency for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.585395574569702s
Consistency | Disjoint class check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12716889381408691s
Consistency | Check Misplaced properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 106.30361413955688s
Consistency | Misplaced classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.30615234375s
Consistency | Check Ontology hijacking for Registry of territorial identification, addresses and real estate of the Czech Republic took 40.302183866500854s
Consistency | Check Invalid usage of undefined classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.4252207279205322s
Consistency | Check Invalid usage of undefined properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 106.51205134391785s
Conciseness | Check Extensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.8993113040924072s
Conciseness | Check Intensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2759974002838135s
Security | Sign check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1356067657470703s
Availability | Check URIs Dereferenciability for Registry of territorial identification, addresses and real estate of the Czech Republic took 11.06912612915039s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.8963794708251953s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.021368741989135742s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.796287536621094e-05s
Interoperability | Check the re-using of existing vocabs for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.430511474609375e-06s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ruian took 1479.7150144577026s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.8691997528076172s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.692025899887085s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.020834922790527344s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 9.179115295410156e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 6.9141387939453125e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 4.7957398891448975s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.4725208282470703s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.278989315032959s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.020737409591674805s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 4.1961669921875e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 7.152557373046875e-06s
INFO | --- Analysis for cz-sao-check-actions took 5.3478569984436035s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.4554331302642822s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.27440595626831055s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020426511764526367s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.075599670410156e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 6.9141387939453125e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 4.516849517822266s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.10283255577087402s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.26009297370910645s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.020737409591674805s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.6716461181640625e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 9.298324584960938e-06s
INFO | --- Analysis for cz-sidc-drug-ingredients took 3.6725540161132812s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.1106410026550293s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.2618143558502197s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.020821571350097656s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.4809112548828125e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 5.7220458984375e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 2.6885366439819336s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.11524415016174316s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.25091981887817383s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.020547866821289062s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.8623809814453125e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 7.3909759521484375e-06s
INFO | --- Analysis for cz-sidc-drugs took 3.705662965774536s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.2470109462738037s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.6861989498138428s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.020644187927246094s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 3.552436828613281e-05s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 5.9604644775390625e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 5.631182909011841s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.10977435111999512s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.2733328342437744s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.02011871337890625s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.600120544433594e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 1.0013580322265625e-05s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 2.8038527965545654s
Availability | SPARQL endpoint availability check for State funding providers took 0.11313009262084961s
Availability | VoID file availability check for State funding providers took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for State funding providers took 0.2769021987915039s
Reputation | Calculation of the PageRank for State funding providers took 0.020354747772216797s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for State funding providers took 4.7206878662109375e-05s
Believability | Calculation of trust value for State funding providers took 5.9604644775390625e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 2.8827385902404785s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.10538673400878906s
Availability | VoID file availability check for Organizations active in R&D took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.2558927536010742s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.02080082893371582s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 4.172325134277344e-05s
Believability | Calculation of trust value for Organizations active in R&D took 5.0067901611328125e-06s
INFO | --- Analysis for cz-vavai-organizations took 2.9672391414642334s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.10908007621765137s
Availability | VoID file availability check for R&D Programmes took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.2627096176147461s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020444869995117188s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.315376281738281e-05s
Believability | Calculation of trust value for R&D Programmes took 5.7220458984375e-06s
INFO | --- Analysis for cz-vavai-programmes took 2.781346559524536s
Availability | SPARQL endpoint availability check for R&D Projects took 0.12051653861999512s
Availability | VoID file availability check for R&D Projects took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.2570669651031494s
Reputation | Calculation of the PageRank for R&D Projects took 0.020291805267333984s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.076957702636719e-05s
Believability | Calculation of trust value for R&D Projects took 5.9604644775390625e-06s
INFO | --- Analysis for cz-vavai-projects took 2.7988204956054688s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.1150979995727539s
Availability | VoID file availability check for Institutional research plans took 0.0007622241973876953s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.2662653923034668s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020287036895751953s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.029273986816406e-05s
Believability | Calculation of trust value for Institutional research plans took 5.9604644775390625e-06s
INFO | --- Analysis for cz-vavai-research-plans took 2.7492780685424805s
Availability | SPARQL endpoint availability check for Results of R&D took 0.11364221572875977s
Availability | VoID file availability check for Results of R&D took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.26912903785705566s
Reputation | Calculation of the PageRank for Results of R&D took 0.02061009407043457s
Interlinking | Calculation of Degree of Connection for Results of R&D took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 3.9577484130859375e-05s
Believability | Calculation of trust value for Results of R&D took 9.298324584960938e-06s
INFO | --- Analysis for cz-vavai-results took 2.7849621772766113s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.11947917938232422s
Availability | VoID file availability check for Tenders in R&D took 0.0007746219635009766s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.2806093692779541s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.020272254943847656s
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.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.0531158447265625e-05s
Believability | Calculation of trust value for Tenders in R&D took 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.832953453063965s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.3724641799926758s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0006935596466064453s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 136.1835334300995s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.02236008644104s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 13.062077760696411s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.20083212852478s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.31357312202454s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.2539362907409668s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.1260676383972168s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.6629936695098877s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.4056272506713867s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.2341766357421875s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.2363581657409668s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 70.70572447776794s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.2608351707458496s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 0.7306311130523682s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.43779730796813965s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.23297643661499023s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.24048209190368652s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.24270415306091309s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.540244579315186s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 9.059906005859375e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.2275848388671875s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.3948707580566406s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 1.2644333839416504s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.24674725532531738s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.21983671188354492s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 1.2473423480987549s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 2.1755917072296143s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 88.30620408058167s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.22112798690795898s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.3316652774810791s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.5110816955566406s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 38.44896960258484s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.237853765487671s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.807232618331909s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.42121243476867676s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 12.827722787857056s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.6930513381958s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 50.79665994644165s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.5495436191558838s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 13.834561347961426s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.843259334564209s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.23270511627197266s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.22910356521606445s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 9.060649394989014s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.5866391658782959s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.021148204803466797s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00014781951904296875s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 1.9073486328125e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 9.059906005859375e-06s
INFO | --- Analysis for data-bnf-fr took 780.802969455719s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.17871618270874023s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0006108283996582031s
Extra | Recovery of all triples for Open Data from the Italian National Research Council took 0.8327107429504395s
Performance | Total latancy measurement for Open Data from the Italian National Research Council took 0.3013880252838135s
Amount of data | Number of triples check for Open Data from the Italian National Research Council took 4.143444299697876s
Interoperability | New terms check for Open Data from the Italian National Research Council took 2.4082703590393066s
Versatility | Languages check for Open Data from the Italian National Research Council took 0.0835261344909668s
Interpretability | Number of blank nodes check for Open Data from the Italian National Research Council took 0.5881426334381104s
Security | Check HTTPS for Open Data from the Italian National Research Council took 0.03955841064453125s
Interpretability | RDF structures check for Open Data from the Italian National Research Council took 0.0969705581665039s
Versatility | Serialization formats check for Open Data from the Italian National Research Council took 0.08928942680358887s
Availability | RDF dump link check for Open Data from the Italian National Research Council took 0.09366321563720703s
License | MR license check for Open Data from the Italian National Research Council took 0.0962533950805664s
License | HR license check for Open Data from the Italian National Research Council took 11.998870849609375s
Amount of data | Number of property check for Open Data from the Italian National Research Council took 0.09691643714904785s
Understandability | Number of label check for Open Data from the Italian National Research Council took 4.003766298294067s
Understandability | URI regex check for Open Data from the Italian National Research Council took 0.219635009765625s
Understandability | Vocabs check for Open Data from the Italian National Research Council took 0.08338022232055664s
Verifiability | Authors check for Open Data from the Italian National Research Council took 0.08436155319213867s
Verifiability | Publishers check for Open Data from the Italian National Research Council took 0.08014655113220215s
Performance | Throughput check for Open Data from the Italian National Research Council took 10.490676403045654s
Amount of data | Check the number of entities for Open Data from the Italian National Research Council took 5.841255187988281e-05s
Verifiability | Contribs. check for Open Data from the Italian National Research Council took 0.0789954662322998s
Interlinking | sameAs chians check for Open Data from the Italian National Research Council took 0.0855708122253418s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.08169794082641602s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.05569815635681152s
Timeliness | dataset update frequency check for Open Data from the Italian National Research Council took 0.09315776824951172s
Currency | Creation date check for Open Data from the Italian National Research Council took 0.16754698753356934s
Currency | Modification date check for Open Data from the Italian National Research Council took 0.18233585357666016s
Rep.Conc. | URIs length for Open Data from the Italian National Research Council took 11.488653659820557s
Interoperability | New vocabularies check for Open Data from the Italian National Research Council took 2.677128553390503s
Consistency | Deprecated classes/propertiers check for Open Data from the Italian National Research Council took 0.0798196792602539s
Accuracy | Check Functional Property for Open Data from the Italian National Research Council took 0.07933640480041504s
Accuracy | Check Inverse Functional Property for Open Data from the Italian National Research Council took 0.07896852493286133s
Accuracy | Check Empty annotation labels for Open Data from the Italian National Research Council took 0.41154026985168457s
Accuracy | Check White space in annotation for Open Data from the Italian National Research Council took 0.03217458724975586s
Accuracy | Check Datatype consistency for Open Data from the Italian National Research Council took 0.028955936431884766s
Consistency | Disjoint class check for Open Data from the Italian National Research Council took 0.08242416381835938s
Consistency | Check Misplaced properties for Open Data from the Italian National Research Council took 10.277970314025879s
Consistency | Misplaced classes for Open Data from the Italian National Research Council took 0.18752026557922363s
Consistency | Check Ontology hijacking for Open Data from the Italian National Research Council took 1.7383289337158203s
Consistency | Check Invalid usage of undefined classes for Open Data from the Italian National Research Council took 1.4690327644348145s
Consistency | Check Invalid usage of undefined properties for Open Data from the Italian National Research Council took 11.447402000427246s
Conciseness | Check Extensional conciseness for Open Data from the Italian National Research Council took 0.03471660614013672s
Conciseness | Check Intensional conciseness for Open Data from the Italian National Research Council took 0.10222792625427246s
Security | Sign check for Open Data from the Italian National Research Council took 0.08347892761230469s
Availability | Check URIs Dereferenciability for Open Data from the Italian National Research Council took 645.1491422653198s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.8704354763031006s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.021221399307250977s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 6.961822509765625e-05s
Interoperability | Check the re-using of existing vocabs for Open Data from the Italian National Research Council took 2.5851657390594482s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 6.4373016357421875e-06s
INFO | --- Analysis for data-cnr-it took 751.818564414978s
Availability | SPARQL endpoint availability check for Data.gov took 1.7163162231445312s
Availability | VoID file availability check for Data.gov took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for Data.gov took 0.2822892665863037s
Reputation | Calculation of the PageRank for Data.gov took 0.02067089080810547s
Interlinking | Calculation of Degree of Connection for Data.gov took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Data.gov took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.0517578125e-05s
Believability | Calculation of trust value for Data.gov took 5.0067901611328125e-06s
INFO | --- Analysis for data-gov took 19.50145983695984s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.4360239505767822s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.25770998001098633s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.020571231842041016s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 6.604194641113281e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 5.245208740234375e-06s
INFO | --- Analysis for data-gov-ie took 3.8773295879364014s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 4.267692565917969e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0009238719940185547s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.2697303295135498s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.020381689071655273s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.104873657226562e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 5.7220458984375e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.9673259258270264s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 21.821608781814575s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.30393218994140625s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.02075958251953125s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.198883056640625e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 6.9141387939453125e-06s
INFO | --- Analysis for data-hnm-hu took 167.44181323051453s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.15315914154052734s
Availability | VoID file availability check for Climb Dataincubator took 0.001066446304321289s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.2829437255859375s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.02118825912475586s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0009481906890869141s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 8.606910705566406e-05s
Believability | Calculation of trust value for Climb Dataincubator took 7.152557373046875e-06s
INFO | --- Analysis for data-incubator-climb took 3.4272048473358154s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.06346702575683594s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.00036263465881347656s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.6940441131591797s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.020806074142456055s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.507469177246094e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 4.5299530029296875e-06s
INFO | --- Analysis for data-incubator-metoffice took 6.390118837356567s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.05938553810119629s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0008015632629394531s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.697643518447876s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.02064681053161621s
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.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.630752563476562e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 5.7220458984375e-06s
INFO | --- Analysis for data-incubator-moseley took 10.074281930923462s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.05650186538696289s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.27095961570739746s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.020672321319580078s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 9.179115295410156e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 5.7220458984375e-06s
INFO | --- Analysis for data-incubator-musicbrainz took 2.4296631813049316s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.6866352558135986s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.25750303268432617s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.02057671546936035s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.296966552734375e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 4.5299530029296875e-06s
INFO | --- Analysis for data-incubator-nasa took 7.591465473175049s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.0645284652709961s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.2603752613067627s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.020650386810302734s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.43865966796875e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 5.7220458984375e-06s
INFO | --- Analysis for data-incubator-our-airports took 2.901414632797241s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.05663013458251953s
Availability | VoID file availability check for Pokedex data in RDF took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.2658975124359131s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.020802736282348633s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.632110595703125e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 6.198883056640625e-06s
INFO | --- Analysis for data-incubator-pokedex took 4.048410177230835s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.058167219161987305s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.25032615661621094s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.020576953887939453s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 9.179115295410156e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 7.3909759521484375e-06s
INFO | --- Analysis for data-incubator-smcjournals took 2.544537305831909s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.5185024738311768s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0005164146423339844s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 104.58799266815186s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 1.321885347366333s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 16.900854349136353s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.6712820529937744s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.336761236190796s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.32716417312622s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.18836307525634766s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.3187124729156494s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.34882450103759766s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.30441808700561523s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.30689334869384766s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.316275596618652s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.7982356548309326s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 26.99642276763916s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 0.6694300174713135s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.3699805736541748s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.4588747024536133s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.3670351505279541s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 12.23683786392212s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 7.295608520507812e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.38486170768737793s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.8024005889892578s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.487515926361084s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.46284031867980957s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.46643543243408203s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.7892913818359375s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.7425022125244141s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 51.354154109954834s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.3292515277862549s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.3293893337249756s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.3357534408569336s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 44.855045318603516s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 3.0014679431915283s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.132206201553345s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.5668869018554688s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 0.8975238800048828s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 8.048331499099731s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 34.643548011779785s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.5237221717834473s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 2.5288662910461426s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 2.8802764415740967s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.5148587226867676s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.3782939910888672s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 0.13550162315368652s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.5353033542633057s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.020812034606933594s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 7.772445678710938e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 1.6689300537109375e-06s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 7.62939453125e-06s
INFO | --- Analysis for data-open-ac-uk took 687.8628854751587s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.9551358222961426s
Availability | VoID file availability check for Persée in RDF took 0.0008313655853271484s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.2692248821258545s
Reputation | Calculation of the PageRank for Persée in RDF took 0.020467758178710938s
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.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00010657310485839844s
Believability | Calculation of trust value for Persée in RDF took 7.62939453125e-06s
INFO | --- Analysis for data-persee-fr took 7.846635341644287s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 4.172325134277344e-05s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.310197114944458s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.0203704833984375s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 3.62396240234375e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 8.58306884765625e-06s
INFO | --- Analysis for data-southampton-ac-uk took 3.429516553878784s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.1464414596557617s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.27559709548950195s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.0202486515045166s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.000118255615234375s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 8.344650268554688e-06s
INFO | --- Analysis for data-szepmuveszeti-hu took 9.004887819290161s
Availability | SPARQL endpoint availability check for DataFAQs took 4.458427429199219e-05s
Availability | VoID file availability check for DataFAQs took 0.0003006458282470703s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.2623147964477539s
Reputation | Calculation of the PageRank for DataFAQs took 0.020773649215698242s
Interlinking | Calculation of Degree of Connection for DataFAQs took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DataFAQs took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 3.075599670410156e-05s
Believability | Calculation of trust value for DataFAQs took 8.106231689453125e-06s
INFO | --- Analysis for datafaqs took 2.888253927230835s
Availability | SPARQL endpoint availability check for datahub took 4.38690185546875e-05s
Availability | VoID file availability check for datahub took 0.001360177993774414s
Completeness | Calculation of interlinking completeness for datahub took 0.2709465026855469s
Reputation | Calculation of the PageRank for datahub took 0.020920276641845703s
Interlinking | Calculation of Degree of Connection for datahub took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for datahub took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for datahub took 4.839897155761719e-05s
Believability | Calculation of trust value for datahub took 8.58306884765625e-06s
INFO | --- Analysis for datahub took 4.127138376235962s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.323101282119751s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.27844762802124023s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.02059149742126465s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.700920104980469e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 8.106231689453125e-06s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 5.451362371444702s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.391400575637817s
Availability | VoID file availability check for datos-artium-org took 0.0007843971252441406s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.8541631698608398s
Reputation | Calculation of the PageRank for datos-artium-org took 0.020793437957763672s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.000118255615234375s
Believability | Calculation of trust value for datos-artium-org took 7.152557373046875e-06s
INFO | --- Analysis for datos-artium-org took 165.15509629249573s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.9311058521270752s
Availability | VoID file availability check for Datos.bcn.cl took 0.0006129741668701172s
Extra | Recovery of all triples for Datos.bcn.cl took 64.9111738204956s
Performance | Total latancy measurement for Datos.bcn.cl took 5.974773406982422s
Amount of data | Number of triples check for Datos.bcn.cl took 13.96628212928772s
Interoperability | New terms check for Datos.bcn.cl took 3.8727731704711914s
Versatility | Languages check for Datos.bcn.cl took 300.9539234638214s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.2819151878356934s
Security | Check HTTPS for Datos.bcn.cl took 0.7493793964385986s
Interpretability | RDF structures check for Datos.bcn.cl took 1.3406455516815186s
Versatility | Serialization formats check for Datos.bcn.cl took 1.3011624813079834s
Availability | RDF dump link check for Datos.bcn.cl took 1.2226998805999756s
License | MR license check for Datos.bcn.cl took 1.3014285564422607s
License | HR license check for Datos.bcn.cl took 31.768868684768677s
Amount of data | Number of property check for Datos.bcn.cl took 1.2137579917907715s
Understandability | Number of label check for Datos.bcn.cl took 1.7500486373901367s
Understandability | URI regex check for Datos.bcn.cl took 2.380521059036255s
Understandability | Vocabs check for Datos.bcn.cl took 1.219604730606079s
Verifiability | Authors check for Datos.bcn.cl took 1.2757840156555176s
Verifiability | Publishers check for Datos.bcn.cl took 1.1934704780578613s
Performance | Throughput check for Datos.bcn.cl took 11.997950315475464s
Amount of data | Check the number of entities for Datos.bcn.cl took 8.106231689453125e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.1962599754333496s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.2310106754302979s
Interlinking | skos check for Datos.bcn.cl took 1.229055643081665s
Interlinking | skos check for Datos.bcn.cl took 1.1974568367004395s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.2085363864898682s
Currency | Creation date check for Datos.bcn.cl took 2.458860397338867s
Currency | Modification date check for Datos.bcn.cl took 1.2318129539489746s
Rep.Conc. | URIs length for Datos.bcn.cl took 53.54704761505127s
Interoperability | New vocabularies check for Datos.bcn.cl took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.261267900466919s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.2030904293060303s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.1857261657714844s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 22.100494861602783s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.23859167098999023s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.26463913917541504s
Consistency | Disjoint class check for Datos.bcn.cl took 1.2059130668640137s
Consistency | Check Misplaced properties for Datos.bcn.cl took 7.169392108917236s
Consistency | Misplaced classes for Datos.bcn.cl took 2.0378477573394775s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 34.12759017944336s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.3918542861938477s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 11.779402017593384s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.29764485359191895s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.4046602249145508s
Security | Sign check for Datos.bcn.cl took 1.2031514644622803s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 11.114720106124878s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 0.8101754188537598s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.02129960060119629s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 7.343292236328125e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.9073486328125e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 5.0067901611328125e-06s
INFO | --- Analysis for datos-bcn-cl took 931.9269533157349s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.33086466789245605s
Availability | VoID file availability check for datos.bne.es took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.7134909629821777s
Reputation | Calculation of the PageRank for datos.bne.es took 0.020572423934936523s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011968612670898438s
Believability | Calculation of trust value for datos.bne.es took 8.106231689453125e-06s
INFO | --- Analysis for datos-bne-es took 5.519565582275391s
Availability | SPARQL endpoint availability check for DBkWik took 0.3319516181945801s
Availability | VoID file availability check for DBkWik took 0.0006151199340820312s
Extra | Recovery of all triples for DBkWik took 2.4706645011901855s
Performance | Total latancy measurement for DBkWik took 0.5365400314331055s
Amount of data | Number of triples check for DBkWik took 4.1955885887146s
Interoperability | New terms check for DBkWik took 2.2725913524627686s
Versatility | Languages check for DBkWik took 61.199976205825806s
Interpretability | Number of blank nodes check for DBkWik took 0.1161201000213623s
Interpretability | RDF structures check for DBkWik took 0.5933592319488525s
Versatility | Serialization formats check for DBkWik took 0.2376270294189453s
Availability | RDF dump link check for DBkWik took 2.7560579776763916s
License | MR license check for DBkWik took 0.5352349281311035s
License | HR license check for DBkWik took 60.337947845458984s
Amount of data | Number of property check for DBkWik took 0.13939237594604492s
Understandability | Number of label check for DBkWik took 2.20247220993042s
Understandability | URI regex check for DBkWik took 0.32150816917419434s
Understandability | Vocabs check for DBkWik took 0.12285828590393066s
Verifiability | Authors check for DBkWik took 0.1494734287261963s
Verifiability | Publishers check for DBkWik took 0.09850811958312988s
Performance | Throughput check for DBkWik took 10.502670049667358s
Amount of data | Check the number of entities for DBkWik took 3.170967102050781e-05s
Verifiability | Contribs. check for DBkWik took 0.14289546012878418s
Interlinking | sameAs chians check for DBkWik took 0.4935925006866455s
Interlinking | skos check for DBkWik took 0.4634816646575928s
Interlinking | skos check for DBkWik took 0.08326983451843262s
Timeliness | dataset update frequency check for DBkWik took 0.2066793441772461s
Currency | Creation date check for DBkWik took 0.4779834747314453s
Currency | Modification date check for DBkWik took 0.23987650871276855s
Rep.Conc. | URIs length for DBkWik took 11.862024068832397s
Interoperability | New vocabularies check for DBkWik took 2.537844181060791s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.11859130859375s
Accuracy | Check Functional Property for DBkWik took 0.32466983795166016s
Accuracy | Check Inverse Functional Property for DBkWik took 0.2698230743408203s
Accuracy | Check Empty annotation labels for DBkWik took 0.8423705101013184s
Accuracy | Check White space in annotation for DBkWik took 0.023356199264526367s
Accuracy | Check Datatype consistency for DBkWik took 0.03766655921936035s
Consistency | Disjoint class check for DBkWik took 0.16536855697631836s
Consistency | Check Misplaced properties for DBkWik took 12.467301607131958s
Consistency | Misplaced classes for DBkWik took 0.8078291416168213s
Consistency | Check Ontology hijacking for DBkWik took 2.00878643989563s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.301408290863037s
Consistency | Check Invalid usage of undefined properties for DBkWik took 12.15036153793335s
Conciseness | Check Extensional conciseness for DBkWik took 0.03400778770446777s
Conciseness | Check Intensional conciseness for DBkWik took 1.0486245155334473s
Security | Sign check for DBkWik took 0.3447732925415039s
Availability | Check URIs Dereferenciability for DBkWik took 10.908625364303589s
Completeness | Calculation of interlinking completeness for DBkWik took 0.7326316833496094s
Reputation | Calculation of the PageRank for DBkWik took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for DBkWik took 7.033348083496094e-05s
Interoperability | Check the re-using of existing vocabs for DBkWik took 2.7144992351531982s
Believability | Calculation of trust value for DBkWik took 7.3909759521484375e-06s
INFO | --- Analysis for dbkwik took 1319.8968620300293s
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.000579833984375s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.7529864311218262s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.020766258239746094s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00012540817260742188s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 8.58306884765625e-06s
INFO | --- Analysis for dblp-deusto-gnoss took 5.245147943496704s
Availability | SPARQL endpoint availability check for dbnary took 0.29320764541625977s
Availability | VoID file availability check for dbnary took 0.0005519390106201172s
Extra | Recovery of all triples for dbnary took 2.4371187686920166s
Performance | Total latancy measurement for dbnary took 0.3724696636199951s
Amount of data | Number of triples check for dbnary took 1.2502474784851074s
Interoperability | New terms check for dbnary took 3.7189602851867676s
Versatility | Languages check for dbnary took 61.47980189323425s
Interpretability | Number of blank nodes check for dbnary took 4.878609657287598s
Security | Check HTTPS for dbnary took 0.15181565284729004s
Interpretability | RDF structures check for dbnary took 0.11499929428100586s
Versatility | Serialization formats check for dbnary took 0.5026240348815918s
Availability | RDF dump link check for dbnary took 0.06791043281555176s
License | MR license check for dbnary took 0.09702539443969727s
License | HR license check for dbnary took 58.882164001464844s
Amount of data | Number of property check for dbnary took 0.09993982315063477s
Understandability | Number of label check for dbnary took 0.9336631298065186s
Understandability | URI regex check for dbnary took 0.14228248596191406s
Understandability | Vocabs check for dbnary took 0.4589107036590576s
Verifiability | Authors check for dbnary took 0.10940241813659668s
Verifiability | Publishers check for dbnary took 0.10751533508300781s
Performance | Throughput check for dbnary took 10.447962284088135s
Amount of data | Check the number of entities for dbnary took 7.367134094238281e-05s
Verifiability | Contribs. check for dbnary took 0.07045483589172363s
Interlinking | sameAs chians check for dbnary took 0.10728764533996582s
Interlinking | skos check for dbnary took 0.4655611515045166s
Interlinking | skos check for dbnary took 0.06994462013244629s
Timeliness | dataset update frequency check for dbnary took 0.28435564041137695s
Currency | Creation date check for dbnary took 0.16673755645751953s
Currency | Modification date check for dbnary took 0.19699811935424805s
Rep.Conc. | URIs length for dbnary took 11.564444541931152s
Interoperability | New vocabularies check for dbnary took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for dbnary took 0.09319567680358887s
Accuracy | Check Functional Property for dbnary took 0.14639854431152344s
Accuracy | Check Inverse Functional Property for dbnary took 0.15078425407409668s
Accuracy | Check Empty annotation labels for dbnary took 1.1065590381622314s
Accuracy | Check White space in annotation for dbnary took 0.024847030639648438s
Accuracy | Check Datatype consistency for dbnary took 0.028676271438598633s
Consistency | Disjoint class check for dbnary took 0.10008406639099121s
Consistency | Check Misplaced properties for dbnary took 9.020842552185059s
Consistency | Misplaced classes for dbnary took 0.2338273525238037s
Consistency | Check Ontology hijacking for dbnary took 1.9673655033111572s
Consistency | Check Invalid usage of undefined classes for dbnary took 1.3214662075042725s
Consistency | Check Invalid usage of undefined properties for dbnary took 10.086040258407593s
Conciseness | Check Extensional conciseness for dbnary took 0.03720569610595703s
Conciseness | Check Intensional conciseness for dbnary took 0.1778564453125s
Security | Sign check for dbnary took 0.17431044578552246s
Availability | Check URIs Dereferenciability for dbnary took 10.192461490631104s
Completeness | Calculation of interlinking completeness for dbnary took 0.26192402839660645s
Reputation | Calculation of the PageRank for dbnary took 0.020949125289916992s
Interlinking | Calculation of Degree of Connection for dbnary took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for dbnary took 6.127357482910156e-05s
Interoperability | Check the re-using of existing vocabs for dbnary took 1.6689300537109375e-06s
Believability | Calculation of trust value for dbnary took 9.298324584960938e-06s
INFO | --- Analysis for dbnary took 308.9150176048279s
Availability | SPARQL endpoint availability check for DBpedia took 0.42561769485473633s
Availability | VoID file availability check for DBpedia took 0.0006196498870849609s
Extra | Recovery of all triples for DBpedia took 1.4882538318634033s
Performance | Total latancy measurement for DBpedia took 0.9357528686523438s
Amount of data | Number of triples check for DBpedia took 0.7101588249206543s
Interoperability | New terms check for DBpedia took 6.2798237800598145s
Versatility | Languages check for DBpedia took 33.441110134124756s
Interpretability | Number of blank nodes check for DBpedia took 0.19107961654663086s
Security | Check HTTPS for DBpedia took 0.11987638473510742s
Interpretability | RDF structures check for DBpedia took 0.19388031959533691s
Versatility | Serialization formats check for DBpedia took 0.6962103843688965s
Availability | RDF dump link check for DBpedia took 0.5939478874206543s
License | MR license check for DBpedia took 1.3229758739471436s
License | HR license check for DBpedia took 31.509838581085205s
Amount of data | Number of property check for DBpedia took 0.19719910621643066s
Understandability | Number of label check for DBpedia took 5.251372337341309s
Understandability | URI regex check for DBpedia took 0.38538098335266113s
Understandability | Vocabs check for DBpedia took 0.44565415382385254s
Verifiability | Authors check for DBpedia took 0.3251199722290039s
Verifiability | Publishers check for DBpedia took 0.20434355735778809s
Performance | Throughput check for DBpedia took 10.91158676147461s
Amount of data | Check the number of entities for DBpedia took 7.295608520507812e-05s
Verifiability | Contribs. check for DBpedia took 0.20421123504638672s
Interlinking | sameAs chians check for DBpedia took 2.5000298023223877s
Interlinking | skos check for DBpedia took 0.6051273345947266s
Interlinking | skos check for DBpedia took 0.1793966293334961s
Timeliness | dataset update frequency check for DBpedia took 0.23146343231201172s
Currency | Creation date check for DBpedia took 0.500307559967041s
Currency | Modification date check for DBpedia took 0.4581639766693115s
Rep.Conc. | URIs length for DBpedia took 36.910531759262085s
Interoperability | New vocabularies check for DBpedia took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.20145630836486816s
Accuracy | Check Functional Property for DBpedia took 0.2692294120788574s
Accuracy | Check Inverse Functional Property for DBpedia took 0.27350354194641113s
Accuracy | Check Empty annotation labels for DBpedia took 2.7373149394989014s
Accuracy | Check White space in annotation for DBpedia took 0.044055938720703125s
Accuracy | Check Datatype consistency for DBpedia took 0.03777170181274414s
Consistency | Disjoint class check for DBpedia took 0.17951416969299316s
Consistency | Check Misplaced properties for DBpedia took 32.04731106758118s
Consistency | Misplaced classes for DBpedia took 0.8219325542449951s
Consistency | Check Ontology hijacking for DBpedia took 2.788841485977173s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.278959035873413s
Consistency | Check Invalid usage of undefined properties for DBpedia took 1.5994174480438232s
Conciseness | Check Extensional conciseness for DBpedia took 0.031177520751953125s
Conciseness | Check Intensional conciseness for DBpedia took 1.1105124950408936s
Security | Sign check for DBpedia took 0.23450970649719238s
Availability | Check URIs Dereferenciability for DBpedia took 2284.746534347534s
Completeness | Calculation of interlinking completeness for DBpedia took 1.2444639205932617s
Reputation | Calculation of the PageRank for DBpedia took 0.020912647247314453s
Interlinking | Calculation of Degree of Connection for DBpedia took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0009064674377441406s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.6689300537109375e-06s
Believability | Calculation of trust value for DBpedia took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia took 2751.674291610718s
Availability | SPARQL endpoint availability check for DBpedia Commons took 303.232896566391s
Availability | VoID file availability check for DBpedia Commons took 0.0002884864807128906s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.3222980499267578s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.020993709564208984s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 7.843971252441406e-05s
Believability | Calculation of trust value for DBpedia Commons took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-commons took 314.7386133670807s
Availability | SPARQL endpoint availability check for DBpedia in German took 5.602836608886719e-05s
Availability | VoID file availability check for DBpedia in German took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.24469566345214844s
Reputation | Calculation of the PageRank for DBpedia in German took 0.02022075653076172s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 6.961822509765625e-05s
Believability | Calculation of trust value for DBpedia in German took 1.049041748046875e-05s
INFO | --- Analysis for dbpedia-de took 4.364328861236572s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 11.080408811569214s
Availability | VoID file availability check for DBpedia in Greek took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.24854421615600586s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.02044057846069336s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0009305477142333984s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00021600723266601562s
Believability | Calculation of trust value for DBpedia in Greek took 5.245208740234375e-06s
INFO | --- Analysis for dbpedia-el took 47.57455348968506s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.4550502300262451s
Availability | VoID file availability check for DBpedia in Spanish took 0.0005125999450683594s
Extra | Recovery of all triples for DBpedia in Spanish took 2.92742657661438s
Performance | Total latancy measurement for DBpedia in Spanish took 1.1815497875213623s
Amount of data | Number of triples check for DBpedia in Spanish took 4.043654441833496s
Interoperability | New terms check for DBpedia in Spanish took 2.7958154678344727s
Versatility | Languages check for DBpedia in Spanish took 61.25690174102783s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.3948357105255127s
Security | Check HTTPS for DBpedia in Spanish took 0.13704133033752441s
Interpretability | RDF structures check for DBpedia in Spanish took 1.4885797500610352s
Versatility | Serialization formats check for DBpedia in Spanish took 0.6328527927398682s
Availability | RDF dump link check for DBpedia in Spanish took 0.39233875274658203s
License | MR license check for DBpedia in Spanish took 1.3646905422210693s
License | HR license check for DBpedia in Spanish took 61.77647423744202s
Amount of data | Number of property check for DBpedia in Spanish took 0.31861448287963867s
Understandability | Number of label check for DBpedia in Spanish took 3.139648675918579s
Understandability | URI regex check for DBpedia in Spanish took 0.7865109443664551s
Understandability | Vocabs check for DBpedia in Spanish took 0.3991115093231201s
Verifiability | Authors check for DBpedia in Spanish took 0.5309023857116699s
Verifiability | Publishers check for DBpedia in Spanish took 0.5510470867156982s
Performance | Throughput check for DBpedia in Spanish took 11.38100266456604s
Amount of data | Check the number of entities for DBpedia in Spanish took 7.43865966796875e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 0.5045571327209473s
Interlinking | sameAs chians check for DBpedia in Spanish took 0.579448938369751s
Interlinking | skos check for DBpedia in Spanish took 1.323746681213379s
Interlinking | skos check for DBpedia in Spanish took 0.222273588180542s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.5076441764831543s
Currency | Creation date check for DBpedia in Spanish took 0.9785802364349365s
Currency | Modification date check for DBpedia in Spanish took 0.6216123104095459s
Rep.Conc. | URIs length for DBpedia in Spanish took 7.531001091003418s
Interoperability | New vocabularies check for DBpedia in Spanish took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 0.2855653762817383s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.3802490234375s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.3933522701263428s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 1.2155449390411377s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.03027510643005371s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.02697277069091797s
Consistency | Disjoint class check for DBpedia in Spanish took 0.30964016914367676s
Consistency | Check Misplaced properties for DBpedia in Spanish took 8.241538763046265s
Consistency | Misplaced classes for DBpedia in Spanish took 2.4760043621063232s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 5.417884588241577s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.2816882133483887s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 7.120502710342407s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.03291034698486328s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 1.3807744979858398s
Security | Sign check for DBpedia in Spanish took 0.3642094135284424s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 10.473427057266235s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.299746036529541s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.021223783493041992s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00010848045349121094s
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.9604644775390625e-06s
INFO | --- Analysis for dbpedia-es took 939.9427227973938s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.2169921398162842s
Availability | VoID file availability check for DBpedia in Basque took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.7313394546508789s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.02061772346496582s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.5762786865234375e-05s
Believability | Calculation of trust value for DBpedia in Basque took 1.0967254638671875e-05s
INFO | --- Analysis for dbpedia-eu took 8.192224264144897s
Availability | SPARQL endpoint availability check for DBpedia in French took 30.022818088531494s
Availability | VoID file availability check for DBpedia in French took 0.0007207393646240234s
Extra | Recovery of all triples for DBpedia in French took 10.098551034927368s
Amount of data | Number of triples check for DBpedia in French took 10.006748676300049s
Versatility | Languages check for DBpedia in French took 10.001929759979248s
Interpretability | Number of blank nodes check for DBpedia in French took 10.001887798309326s
Security | Check HTTPS for DBpedia in French took 20.877038717269897s
Interpretability | RDF structures check for DBpedia in French took 71.52176904678345s
Versatility | Serialization formats check for DBpedia in French took 43.21918439865112s
Availability | RDF dump link check for DBpedia in French took 837.660523891449s
License | MR license check for DBpedia in French took 5.66457986831665s
License | HR license check for DBpedia in French took 300.0676028728485s
Amount of data | Number of property check for DBpedia in French took 130.2870409488678s
Understandability | Number of label check for DBpedia in French took 10.085306167602539s
Understandability | URI regex check for DBpedia in French took 125.56672549247742s
Understandability | Vocabs check for DBpedia in French took 27.008054971694946s
Verifiability | Authors check for DBpedia in French took 20.8885281085968s
Verifiability | Publishers check for DBpedia in French took 10.366881370544434s
Performance | Throughput check for DBpedia in French took 82.25720739364624s
Amount of data | Check the number of entities for DBpedia in French took 0.00012135505676269531s
Verifiability | Contribs. check for DBpedia in French took 7.12117338180542s
Interlinking | sameAs chians check for DBpedia in French took 3.598285436630249s
Interlinking | skos check for DBpedia in French took 13.874966621398926s
Interlinking | skos check for DBpedia in French took 7.85549521446228s
Timeliness | dataset update frequency check for DBpedia in French took 3.8939878940582275s
Currency | Creation date check for DBpedia in French took 11.220083475112915s
Currency | Modification date check for DBpedia in French took 24.61391019821167s
Rep.Conc. | URIs length for DBpedia in French took 348.1132833957672s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 10.01220989227295s
Consistency | Disjoint class check for DBpedia in French took 13.101150035858154s
Consistency | Check Misplaced properties for DBpedia in French took 93.66579794883728s
Consistency | Misplaced classes for DBpedia in French took 13.251227617263794s
Consistency | Check Ontology hijacking for DBpedia in French took 109.45488142967224s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 11.389760494232178s
Conciseness | Check Extensional conciseness for DBpedia in French took 0.00015854835510253906s
Security | Sign check for DBpedia in French took 10.096708536148071s
Completeness | Calculation of interlinking completeness for DBpedia in French took 1.6015286445617676s
Reputation | Calculation of the PageRank for DBpedia in French took 0.021340608596801758s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 9.584426879882812e-05s
Believability | Calculation of trust value for DBpedia in French took 1.049041748046875e-05s
INFO | --- Analysis for dbpedia-fr took 3835.8132388591766s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.960688591003418s
Availability | VoID file availability check for DBpedia in Japanese took 4.046579360961914s
Extra | Recovery of all triples for DBpedia in Japanese took 5.524209976196289s
Performance | Total latancy measurement for DBpedia in Japanese took 6.640380144119263s
Amount of data | Number of triples check for DBpedia in Japanese took 33.90808987617493s
Interoperability | New terms check for DBpedia in Japanese took 19.26963233947754s
Versatility | Languages check for DBpedia in Japanese took 1.3405725955963135s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.3434977531433105s
Security | Check HTTPS for DBpedia in Japanese took 0.8023128509521484s
Interpretability | RDF structures check for DBpedia in Japanese took 1.3744378089904785s
Versatility | Serialization formats check for DBpedia in Japanese took 1.3730237483978271s
Availability | RDF dump link check for DBpedia in Japanese took 1.324336051940918s
License | MR license check for DBpedia in Japanese took 1.369417428970337s
License | HR license check for DBpedia in Japanese took 92.91175174713135s
Amount of data | Number of property check for DBpedia in Japanese took 1.3274900913238525s
Understandability | Number of label check for DBpedia in Japanese took 8.10145354270935s
Understandability | URI regex check for DBpedia in Japanese took 2.6696853637695312s
Understandability | Vocabs check for DBpedia in Japanese took 1.3514084815979004s
Verifiability | Authors check for DBpedia in Japanese took 1.3495509624481201s
Verifiability | Publishers check for DBpedia in Japanese took 1.3256020545959473s
Performance | Throughput check for DBpedia in Japanese took 13.28323745727539s
Amount of data | Check the number of entities for DBpedia in Japanese took 7.43865966796875e-05s
Verifiability | Contribs. check for DBpedia in Japanese took 1.3534753322601318s
Interlinking | sameAs chians check for DBpedia in Japanese took 2.9371719360351562s
Interlinking | skos check for DBpedia in Japanese took 1.3283205032348633s
Interlinking | skos check for DBpedia in Japanese took 1.3221046924591064s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.3559885025024414s
Currency | Creation date check for DBpedia in Japanese took 2.6948001384735107s
Currency | Modification date check for DBpedia in Japanese took 2.6906023025512695s
Rep.Conc. | URIs length for DBpedia in Japanese took 78.88335275650024s
Interoperability | New vocabularies check for DBpedia in Japanese took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.3564236164093018s
Accuracy | Check Inverse Functional Property for DBpedia in Japanese took 32.963016748428345s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 2.9092519283294678s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.02531909942626953s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.027325153350830078s
Consistency | Disjoint class check for DBpedia in Japanese took 1.4416885375976562s
Consistency | Check Misplaced properties for DBpedia in Japanese took 94.13172793388367s
Consistency | Misplaced classes for DBpedia in Japanese took 2.987701654434204s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 4.226740837097168s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.2896199226379395s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 62.62067532539368s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.03289437294006348s
Security | Sign check for DBpedia in Japanese took 1.3328418731689453s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 10.46960186958313s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.8590662479400635s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.0213930606842041s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0008702278137207031s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.0001227855682373047s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 5.7220458984375e-06s
INFO | --- Analysis for dbpedia-ja took 1012.124650478363s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.38690185546875e-05s
Availability | VoID file availability check for dbpedia lite took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.7300546169281006s
Reputation | Calculation of the PageRank for dbpedia lite took 0.020782470703125s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.00010585784912109375s
Believability | Calculation of trust value for dbpedia lite took 6.198883056640625e-06s
INFO | --- Analysis for dbpedia-lite took 25.096721410751343s
Availability | SPARQL endpoint availability check for DBpedia-Live took 4.1961669921875e-05s
Availability | VoID file availability check for DBpedia-Live took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.6980016231536865s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.020613670349121094s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 3.0994415283203125e-05s
Believability | Calculation of trust value for DBpedia-Live took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-live took 3.779383897781372s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.28426647186279297s
Availability | VoID file availability check for DBpedia in Dutch took 0.0006387233734130859s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.27398252487182617s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.020479917526245117s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00017213821411132812s
Believability | Calculation of trust value for DBpedia in Dutch took 6.198883056640625e-06s
INFO | --- Analysis for dbpedia-nl took 3.3403472900390625s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 0.55104660987854s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.261821985244751s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.020722627639770508s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.320808410644531e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 1.2636184692382812e-05s
INFO | --- Analysis for dbpedia-pt took 4.019095182418823s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 4.100799560546875e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.2823803424835205s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.020321130752563477s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 2.8133392333984375e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 1.2159347534179688e-05s
INFO | --- Analysis for dbpedia-spotlight took 3.383190631866455s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.220008850097656e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.2543807029724121s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.02041029930114746s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 6.67572021484375e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 7.867813110351562e-06s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 14.30014157295227s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 4.1961669921875e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.2670567035675049s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.02028369903564453s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 2.765655517578125e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 7.867813110351562e-06s
INFO | --- Analysis for dbpedia-wikidata took 3.0172550678253174s
Availability | SPARQL endpoint availability check for DBpedia took 4.3392181396484375e-05s
Availability | VoID file availability check for DBpedia took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for DBpedia took 0.25076818466186523s
Reputation | Calculation of the PageRank for DBpedia took 0.020297527313232422s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for DBpedia took 2.8848648071289062e-05s
Believability | Calculation of trust value for DBpedia took 7.62939453125e-06s
INFO | --- Analysis for dbpedia_ took 2.9042704105377197s
Availability | SPARQL endpoint availability check for DBTropes took 4.38690185546875e-05s
Availability | VoID file availability check for DBTropes took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for DBTropes took 0.3730311393737793s
Reputation | Calculation of the PageRank for DBTropes took 0.020244598388671875s
Interlinking | Calculation of Degree of Connection for DBTropes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBTropes took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.655952453613281e-05s
Believability | Calculation of trust value for DBTropes took 7.62939453125e-06s
INFO | --- Analysis for dbtropes took 3.1482045650482178s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 4.172325134277344e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.2584822177886963s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.029128551483154297s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 4.482269287109375e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 7.152557373046875e-06s
INFO | --- Analysis for dbtune took 2.879971981048584s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 4.410743713378906e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.26224517822265625s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.020401477813720703s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 7.081031799316406e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 7.867813110351562e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 8.684457063674927s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 7.939338684082031e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.27032995223999023s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.020411014556884766s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.314018249511719e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 6.198883056640625e-06s
INFO | --- Analysis for dbtune-audioscrobbler took 5.95318603515625s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 6.89510440826416s
Availability | VoID file availability check for DBTune.org/classical took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.2706301212310791s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.02039623260498047s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 8.296966552734375e-05s
Believability | Calculation of trust value for DBTune.org/classical took 8.58306884765625e-06s
INFO | --- Analysis for dbtune-classical took 22.448004722595215s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 8.348055601119995s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0006487369537353516s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.26555943489074707s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.02083277702331543s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0010597705841064453s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 8.535385131835938e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 6.9141387939453125e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 26.9027156829834s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 8.383236646652222s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.27376747131347656s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.020313739776611328s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0008537769317626953s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 7.43865966796875e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 1.0967254638671875e-05s
INFO | --- Analysis for dbtune-magnatune took 23.91855764389038s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 8.375362634658813s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.23863840103149414s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.020164966583251953s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00010418891906738281s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 7.152557373046875e-06s
INFO | --- Analysis for dbtune-musicbrainz took 23.92102575302124s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 8.365088701248169s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.00031685829162597656s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.2659571170806885s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.0205228328704834s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.030632019042969e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 7.62939453125e-06s
INFO | --- Analysis for dbtune-myspace took 17.904956340789795s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 4.1484832763671875e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.38790369033813477s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.020473480224609375s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 2.956390380859375e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 7.867813110351562e-06s
INFO | --- Analysis for dclg-openuplabs took 2.9646434783935547s
Availability | SPARQL endpoint availability check for data.dcs took 4.315376281738281e-05s
Availability | VoID file availability check for data.dcs took 0.0006864070892333984s
Completeness | Calculation of interlinking completeness for data.dcs took 0.31340718269348145s
Reputation | Calculation of the PageRank for data.dcs took 0.02087259292602539s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.914138793945312e-05s
Believability | Calculation of trust value for data.dcs took 7.62939453125e-06s
INFO | --- Analysis for dcs-sheffield took 2.489567518234253s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 4.458427429199219e-05s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.26540684700012207s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.020601272583007812s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 2.9325485229492188e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 1.9311904907226562e-05s
INFO | --- Analysis for de-budget took 2.8796792030334473s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 4.363059997558594e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0006268024444580078s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.26221776008605957s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.02044367790222168s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007457733154296875s
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 7.62939453125e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.3063647747039795s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 4.1961669921875e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0006916522979736328s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.24190855026245117s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.020579099655151367s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.172325134277344e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 1.1444091796875e-05s
INFO | --- Analysis for debian-package-tracking-system took 4.461132049560547s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0001201629638671875s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.00031638145446777344s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.25975966453552246s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.021180152893066406s
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.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 3.4332275390625e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 7.62939453125e-06s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 2.895451545715332s
Availability | SPARQL endpoint availability check for Demografie took 4.291534423828125e-05s
Availability | VoID file availability check for Demografie took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Demografie took 0.2702178955078125s
Reputation | Calculation of the PageRank for Demografie took 0.020790815353393555s
Interlinking | Calculation of Degree of Connection for Demografie took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Demografie took 3.170967102050781e-05s
Believability | Calculation of trust value for Demografie took 6.67572021484375e-06s
INFO | --- Analysis for demografie took 2.9490740299224854s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.267692565917969e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.24907255172729492s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.020448923110961914s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 0.00010752677917480469s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 7.152557373046875e-06s
INFO | --- Analysis for deustoentrepreneurship took 5.1051483154296875s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 4.3392181396484375e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0011928081512451172s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.27589869499206543s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.020596742630004883s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.000110626220703125s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 8.58306884765625e-06s
INFO | --- Analysis for deustotech took 4.914110898971558s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.4129090309143066s
Availability | VoID file availability check for Deutsche Biographie took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.24473214149475098s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.020356416702270508s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 3.7670135498046875e-05s
Believability | Calculation of trust value for Deutsche Biographie took 6.198883056640625e-06s
INFO | --- Analysis for deutsche-biographie took 4.173301935195923s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 4.38690185546875e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.00036787986755371094s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.25693464279174805s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.020273685455322266s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.5789947509765625e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 7.62939453125e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 6.732358694076538s
Availability | SPARQL endpoint availability check for dev8d took 4.1961669921875e-05s
Availability | VoID file availability check for dev8d took 0.00042057037353515625s
Completeness | Calculation of interlinking completeness for dev8d took 0.265380859375s
Reputation | Calculation of the PageRank for dev8d took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for dev8d took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for dev8d took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for dev8d took 7.05718994140625e-05s
Believability | Calculation of trust value for dev8d took 8.106231689453125e-06s
INFO | --- Analysis for dev8d took 2.951263427734375s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.223827123641968s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0007300376892089844s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.363513708114624s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.020676136016845703s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0010571479797363281s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 9.918212890625e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 7.62939453125e-06s
INFO | --- Analysis for dewey_decimal_classification took 93.04623866081238s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 4.2438507080078125e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.2530174255371094s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 2.956390380859375e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 8.106231689453125e-06s
INFO | --- Analysis for diachronic-ontologies-peoples-daily took 2.9633495807647705s
Availability | SPARQL endpoint availability check for Diavgeia took 4.673004150390625e-05s
Availability | VoID file availability check for Diavgeia took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.25532007217407227s
Reputation | Calculation of the PageRank for Diavgeia took 0.0201566219329834s
Interlinking | Calculation of Degree of Connection for Diavgeia took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.058547973632812e-05s
Believability | Calculation of trust value for Diavgeia took 5.4836273193359375e-06s
INFO | --- Analysis for diavgeia took 5.403876543045044s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.4345855712890625e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0003478527069091797s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.2575383186340332s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.02035808563232422s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011920928955078125s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.0967254638671875e-05s
INFO | --- Analysis for didactalia took 8.1591956615448s
Availability | SPARQL endpoint availability check for diigo.feed took 5.316734313964844e-05s
Availability | VoID file availability check for diigo.feed took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.269026517868042s
Reputation | Calculation of the PageRank for diigo.feed took 0.020350933074951172s
Interlinking | Calculation of Degree of Connection for diigo.feed took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 2.86102294921875e-05s
Believability | Calculation of trust value for diigo.feed took 7.867813110351562e-06s
INFO | --- Analysis for diigo-feed took 2.903884172439575s
Availability | SPARQL endpoint availability check for DisGeNET took 0.26305389404296875s
Availability | VoID file availability check for DisGeNET took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.2517530918121338s
Reputation | Calculation of the PageRank for DisGeNET took 0.020277976989746094s
Interlinking | Calculation of Degree of Connection for DisGeNET took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.0001590251922607422s
Believability | Calculation of trust value for DisGeNET took 6.9141387939453125e-06s
INFO | --- Analysis for disgenet took 3.312256097793579s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 4.100799560546875e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.26025390625s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.020637989044189453s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 2.5510787963867188e-05s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 2.9087066650390625e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 9.059906005859375e-06s
INFO | --- Analysis for disk took 2.8778235912323s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 4.124641418457031e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.2583043575286865s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.023230552673339844s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 3.123283386230469e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 7.3909759521484375e-06s
INFO | --- Analysis for distritos-zaragoza took 2.929063558578491s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.172325134277344e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.2780745029449463s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.02054595947265625s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.075599670410156e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 8.58306884765625e-06s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 8.977832317352295s
Availability | SPARQL endpoint availability check for DM2E took 4.4345855712890625e-05s
Availability | VoID file availability check for DM2E took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for DM2E took 0.28905534744262695s
Reputation | Calculation of the PageRank for DM2E took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for DM2E took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DM2E took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00011181831359863281s
Believability | Calculation of trust value for DM2E took 7.3909759521484375e-06s
INFO | --- Analysis for dm2e took 3.2061564922332764s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 4.458427429199219e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.2648038864135742s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 3.218650817871094e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 6.9141387939453125e-06s
INFO | --- Analysis for dmoz_rdf_dump took 2.9305834770202637s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 1.6862099170684814s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.2916743755340576s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00017404556274414062s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 7.3909759521484375e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 10.475435495376587s
Availability | SPARQL endpoint availability check for DOAP Store took 5.364418029785156e-05s
Availability | VoID file availability check for DOAP Store took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.26211977005004883s
Reputation | Calculation of the PageRank for DOAP Store took 0.020543575286865234s
Interlinking | Calculation of Degree of Connection for DOAP Store took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DOAP Store took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 3.0040740966796875e-05s
Believability | Calculation of trust value for DOAP Store took 3.1948089599609375e-05s
INFO | --- Analysis for doap_store took 2.917118787765503s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 5.507469177246094e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.000576019287109375s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.27469730377197266s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.02053999900817871s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.318092346191406e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 9.059906005859375e-06s
INFO | --- Analysis for doi took 7.535610675811768s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 6.098123073577881s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.2673225402832031s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.020145893096923828s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.3855438232421875e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 8.106231689453125e-06s
INFO | --- Analysis for drug-data-hifm took 38.91561269760132s
Availability | SPARQL endpoint availability check for dspace took 4.076957702636719e-05s
Availability | VoID file availability check for dspace took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for dspace took 0.28685665130615234s
Reputation | Calculation of the PageRank for dspace took 0.02038741111755371s
Interlinking | Calculation of Degree of Connection for dspace took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for dspace took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for dspace took 2.9802322387695312e-05s
Believability | Calculation of trust value for dspace took 6.9141387939453125e-06s
INFO | --- Analysis for dspace took 2.8762168884277344s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 4.220008850097656e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.2460157871246338s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.021750450134277344s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 3.075599670410156e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 1.3589859008789062e-05s
INFO | --- Analysis for duraark-linked-building-data took 2.849250316619873s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 270.9668724536896s
Availability | VoID file availability check for MetaLex Document Server took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.26901841163635254s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.02077507972717285s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 3.790855407714844e-05s
Believability | Calculation of trust value for MetaLex Document Server took 6.9141387939453125e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 554.2712872028351s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 1.6991569995880127s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.28049397468566895s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020679473876953125s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 4.458427429199219e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 8.106231689453125e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 13.608862161636353s
Availability | SPARQL endpoint availability check for DWS-Group took 4.744529724121094e-05s
Availability | VoID file availability check for DWS-Group took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.7406706809997559s
Reputation | Calculation of the PageRank for DWS-Group took 0.020380496978759766s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010442733764648438s
Believability | Calculation of trust value for DWS-Group took 6.198883056640625e-06s
INFO | --- Analysis for dws-group took 4.400452136993408s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.08117485046386719s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.28396058082580566s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.02032184600830078s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00012087821960449219s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-alaska took 3.4766273498535156s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.04080843925476074s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.26909351348876953s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020633935928344727s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.507469177246094e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 8.58306884765625e-06s
INFO | --- Analysis for eagle-i-cau took 2.9358417987823486s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.054727792739868164s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.2894430160522461s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.020549297332763672s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.628036499023438e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.4809956550598145s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.03934025764465332s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.2498331069946289s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.020303010940551758s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.918212890625e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-cdrewu took 2.4791882038116455s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.042812347412109375s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.24090790748596191s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.022498130798339844s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0010285377502441406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.0001666545867919922s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-dartmouth took 2.4220404624938965s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.04012632369995117s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.26172947883605957s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.02062201499938965s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.869171142578125e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 6.4373016357421875e-06s
INFO | --- Analysis for eagle-i-famu took 2.500913381576538s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.04801511764526367s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.25168681144714355s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.020739316940307617s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00013208389282226562s
Believability | Calculation of trust value for eagle-i @ Harvard University took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-harvard took 2.4219093322753906s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.041794538497924805s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.24502062797546387s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00012636184692382812s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 8.821487426757812e-06s
INFO | --- Analysis for eagle-i-hawaii took 2.4930288791656494s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.048352956771850586s
Availability | VoID file availability check for eagle-i @ Howard University took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.2662367820739746s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.020516633987426758s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.532669067382812e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-howard took 2.464653968811035s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.04296731948852539s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0004062652587890625s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.2696049213409424s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020762205123901367s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.794929504394531e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.4776339530944824s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.045181989669799805s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.25712156295776367s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.02051687240600586s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011539459228515625s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-jsu took 2.507143974304199s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.03947710990905762s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.00038909912109375s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.26579976081848145s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.020626544952392578s
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.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 4.410743713378906e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 6.4373016357421875e-06s
INFO | --- Analysis for eagle-i-meharry took 2.4937736988067627s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.04289436340332031s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.28543519973754883s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.020641088485717773s
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.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 0.00010895729064941406s
Believability | Calculation of trust value for eagle-i @ Montana State University took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-montana took 2.5116851329803467s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.03887438774108887s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0003485679626464844s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.24190711975097656s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.02051067352294922s
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.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.441375732421875e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-msm took 2.452363967895508s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.04020285606384277s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.2753438949584961s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.020398616790771484s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00012755393981933594s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-ohsu took 2.5077717304229736s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.0617833137512207s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.2703428268432617s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.02085566520690918s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.890296936035156e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-psm took 2.4609766006469727s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.04696846008300781s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.28321266174316406s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020802736282348633s
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.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.67572021484375e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-tsu took 2.529649257659912s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.03853440284729004s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.26535964012145996s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.02066826820373535s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.651878356933594e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-tuskegee took 2.422778844833374s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.03300213813781738s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.2511558532714844s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.021537065505981445s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0008058547973632812s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.00011610984802246094s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 8.58306884765625e-06s
INFO | --- Analysis for eagle-i-uccaribe took 2.449622631072998s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.04863929748535156s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0004322528839111328s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.31018996238708496s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.020607709884643555s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0001270771026611328s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-upr took 2.5473406314849854s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.05007219314575195s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.25960850715637207s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.020403385162353516s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.437301635742188e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 8.58306884765625e-06s
INFO | --- Analysis for eagle-i-utep took 2.4665775299072266s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.045185089111328125s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.270737886428833s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.020196199417114258s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 7.200241088867188e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-utsa took 2.4714200496673584s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.16330933570861816s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.25322747230529785s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.020296335220336914s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.608268737792969e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-vanderbilt took 2.5242042541503906s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.02807164192199707s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.2544984817504883s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.020462751388549805s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.510185241699219e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-xula took 2.3690695762634277s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.8589200973510742s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.264329195022583s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.020827293395996094s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010251998901367188s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for ecb-linked-data took 3.2763895988464355s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 0.14860749244689941s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.2807302474975586s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.020284175872802734s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.647804260253906e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 5.9604644775390625e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 2.607459783554077s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 2.589055299758911s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.2535884380340576s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.020583391189575195s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.556510925292969e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for ecco-tcp-linked-data took 6.9033026695251465s
Availability | SPARQL endpoint availability check for ECLAP took 20.708009004592896s
Availability | VoID file availability check for ECLAP took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for ECLAP took 0.24378013610839844s
Reputation | Calculation of the PageRank for ECLAP took 0.020711421966552734s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for ECLAP took 4.410743713378906e-05s
Believability | Calculation of trust value for ECLAP took 7.3909759521484375e-06s
INFO | --- Analysis for eclap took 53.15662169456482s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.291534423828125e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.28130674362182617s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02019476890563965s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.316734313964844e-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.4628753662109375s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 4.0531158447265625e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.2677583694458008s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.020306825637817383s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 2.7894973754882812e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 8.58306884765625e-06s
INFO | --- Analysis for edificios-historicos-zaragoza took 3.4299395084381104s
Availability | SPARQL endpoint availability check for Edublogs took 4.315376281738281e-05s
Availability | VoID file availability check for Edublogs took 0.0006132125854492188s
Completeness | Calculation of interlinking completeness for Edublogs took 0.24983930587768555s
Reputation | Calculation of the PageRank for Edublogs took 0.020486831665039062s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for Edublogs took 9.942054748535156e-05s
Believability | Calculation of trust value for Edublogs took 8.106231689453125e-06s
INFO | --- Analysis for edublogs took 3.346769094467163s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.4410550594329834s
Availability | VoID file availability check for education.data.gov.uk took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.24637484550476074s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.020708560943603516s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 9.036064147949219e-05s
Believability | Calculation of trust value for education.data.gov.uk took 6.67572021484375e-06s
INFO | --- Analysis for education-data-gov-uk took 4.372801303863525s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 4.100799560546875e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.2813451290130615s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.020464181900024414s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 3.814697265625e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 6.4373016357421875e-06s
INFO | --- Analysis for education-openuplabs took 2.866910696029663s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 392.12542724609375s
Availability | VoID file availability check for Educational programs - SISVU took 0.0009114742279052734s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 1.166846752166748s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.021079063415527344s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 5.7697296142578125e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 6.9141387939453125e-06s
INFO | --- Analysis for educationalprograms_sisvu took 1322.415399312973s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 0.8002612590789795s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.2784702777862549s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.02059173583984375s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 3.790855407714844e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 5.245208740234375e-06s
INFO | --- Analysis for eea took 8.279328346252441s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.5012133121490479s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.7628507614135742s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020207881927490234s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.1975250244140625e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 5.245208740234375e-06s
INFO | --- Analysis for eea-rod took 7.078701496124268s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.18070006370544434s
Availability | VoID file availability check for EEA Vocabularies took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.2797267436981201s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.02086639404296875s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.344650268554688e-05s
Believability | Calculation of trust value for EEA Vocabularies took 8.821487426757812e-06s
INFO | --- Analysis for eea-vocabularies took 5.740445852279663s
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.0002722740173339844s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.28080058097839355s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.020888805389404297s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 3.1948089599609375e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 8.106231689453125e-06s
INFO | --- Analysis for ege-university-linked-open-data took 3.3748292922973633s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 7.653236389160156e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.2640078067779541s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.020383119583129883s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010633468627929688s
Believability | Calculation of trust value for EIONET RDF Data took 5.9604644775390625e-06s
INFO | --- Analysis for eionet-rdf took 3.399658203125s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 4.7206878662109375e-05s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.3011798858642578s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.020946025848388672s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0008280277252197266s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 3.147125244140625e-05s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 7.62939453125e-06s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 2.956580638885498s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 9.30076289176941s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.2684786319732666s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.021084308624267578s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 7.534027099609375e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 6.67572021484375e-06s
INFO | --- Analysis for elviajero took 27.967345476150513s
Availability | SPARQL endpoint availability check for EMN took 7.915496826171875e-05s
Availability | VoID file availability check for EMN took 0.0008006095886230469s
Completeness | Calculation of interlinking completeness for EMN took 0.26550865173339844s
Reputation | Calculation of the PageRank for EMN took 0.02068471908569336s
Interlinking | Calculation of Degree of Connection for EMN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for EMN took 4.172325134277344e-05s
Believability | Calculation of trust value for EMN took 8.106231689453125e-06s
INFO | --- Analysis for emn took 12.837298393249512s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 4.363059997558594e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0004143714904785156s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.2642848491668701s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.020760536193847656s
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.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.125999450683594e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 5.7220458984375e-06s
INFO | --- Analysis for enakting-co2emission took 2.3854048252105713s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 5.245208740234375e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0011057853698730469s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.27756285667419434s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.021326065063476562s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 4.5299530029296875e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 5.9604644775390625e-06s
INFO | --- Analysis for enakting-crime took 2.952022075653076s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.649162292480469e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.2826724052429199s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.0214078426361084s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0008370876312255859s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 4.5299530029296875e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 5.9604644775390625e-06s
INFO | --- Analysis for enakting-energy took 2.4100446701049805s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 4.458427429199219e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0009286403656005859s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.27352070808410645s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.020565271377563477s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 9.226799011230469e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 5.9604644775390625e-06s
INFO | --- Analysis for enakting-mortality took 2.420468330383301s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 5.054473876953125e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.3100278377532959s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.020406007766723633s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.62396240234375e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 5.0067901611328125e-06s
INFO | --- Analysis for enakting-nhs took 2.497175693511963s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 4.220008850097656e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.2780320644378662s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.020481348037719727s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 4.9591064453125e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 6.198883056640625e-06s
INFO | --- Analysis for enakting-population took 2.37966251373291s
Availability | SPARQL endpoint availability check for Enel Shops took 4.172325134277344e-05s
Availability | VoID file availability check for Enel Shops took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.23747920989990234s
Reputation | Calculation of the PageRank for Enel Shops took 0.020259857177734375s
Interlinking | Calculation of Degree of Connection for Enel Shops took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Enel Shops took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 2.8848648071289062e-05s
Believability | Calculation of trust value for Enel Shops took 7.3909759521484375e-06s
INFO | --- Analysis for enel-shops took 2.880715847015381s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 4.553794860839844e-05s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.0003943443298339844s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.25342273712158203s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.02067852020263672s
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.0008037090301513672s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 3.337860107421875e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 7.867813110351562e-06s
INFO | --- Analysis for energy-efficiency took 2.9061667919158936s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 4.2438507080078125e-05s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.28065967559814453s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for English Heritage Archaeological Sciences Thesaurus took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for English Heritage Archaeological Sciences Thesaurus took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 2.9325485229492188e-05s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for english-heritage-archaeological-sciences-thesaurus took 2.9547221660614014s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 4.1961669921875e-05s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.2641439437866211s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.02045750617980957s
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.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 2.9087066650390625e-05s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for english-heritage-building-materials-thesaurus took 2.992007255554199s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 4.124641418457031e-05s
Availability | VoID file availability check for English Heritage Components Thesaurus took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.2652103900909424s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.02029871940612793s
Interlinking | Calculation of Degree of Connection for English Heritage Components Thesaurus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for English Heritage Components Thesaurus took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 2.8133392333984375e-05s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for english-heritage-components-thesaurus took 2.924663782119751s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 4.482269287109375e-05s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.26452088356018066s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.020084142684936523s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 2.7179718017578125e-05s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 2.940995454788208s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.00029921531677246094s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 0.269564151763916s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.020358800888061523s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 3.075599670410156e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 2.951158046722412s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.267183780670166s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.020351648330688477s
Interlinking | Calculation of Degree of Connection for English Heritage Maritime Craft Thesaurus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for English Heritage Maritime Craft Thesaurus took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 2.9087066650390625e-05s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for english-heritage-maritime-craft-thesaurus took 2.9170925617218018s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 8.440017700195312e-05s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.28134584426879883s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.020539283752441406s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 2.8848648071289062e-05s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for english-heritage-monument-types-thesaurus took 2.916430950164795s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.7259140014648438s
Availability | VoID file availability check for English Heritage Periods List took 0.0007205009460449219s
Extra | Recovery of all triples for English Heritage Periods List took 0.4490046501159668s
Performance | Total latancy measurement for English Heritage Periods List took 2.1196963787078857s
Amount of data | Number of triples check for English Heritage Periods List took 0.6584672927856445s
Versatility | Languages check for English Heritage Periods List took 0.36612653732299805s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.6773707866668701s
Security | Check HTTPS for English Heritage Periods List took 0.2927391529083252s
Interpretability | RDF structures check for English Heritage Periods List took 0.36775708198547363s
Versatility | Serialization formats check for English Heritage Periods List took 0.6374015808105469s
Availability | RDF dump link check for English Heritage Periods List took 0.42529869079589844s
License | MR license check for English Heritage Periods List took 0.5931460857391357s
License | HR license check for English Heritage Periods List took 0.48137354850769043s
Amount of data | Number of property check for English Heritage Periods List took 0.4864335060119629s
Understandability | Number of label check for English Heritage Periods List took 0.5922868251800537s
Understandability | URI regex check for English Heritage Periods List took 0.891326904296875s
Understandability | Vocabs check for English Heritage Periods List took 0.5584161281585693s
Verifiability | Authors check for English Heritage Periods List took 0.5755021572113037s
Verifiability | Publishers check for English Heritage Periods List took 0.48288464546203613s
Performance | Throughput check for English Heritage Periods List took 12.706886529922485s
Amount of data | Check the number of entities for English Heritage Periods List took 0.00010037422180175781s
Verifiability | Contribs. check for English Heritage Periods List took 0.4860403537750244s
Interlinking | sameAs chians check for English Heritage Periods List took 0.4278256893157959s
Interlinking | skos check for English Heritage Periods List took 0.5129356384277344s
Interlinking | skos check for English Heritage Periods List took 0.46984219551086426s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.6153082847595215s
Currency | Creation date check for English Heritage Periods List took 1.8818104267120361s
Currency | Modification date check for English Heritage Periods List took 1.0722649097442627s
Rep.Conc. | URIs length for English Heritage Periods List took 0.8976480960845947s
Interoperability | New vocabularies check for English Heritage Periods List took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.4787302017211914s
Accuracy | Check Functional Property for English Heritage Periods List took 0.42178916931152344s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.42058348655700684s
Consistency | Disjoint class check for English Heritage Periods List took 0.47308993339538574s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.5340456962585449s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.8118796348571777s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.0001544952392578125s
Security | Sign check for English Heritage Periods List took 0.44667482376098633s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.29168152809143066s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.020372867584228516s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.528594970703125e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 9.5367431640625e-07s
Believability | Calculation of trust value for English Heritage Periods List took 6.9141387939453125e-06s
INFO | --- Analysis for english-heritage-periods-list took 67.87277746200562s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.4232184886932373s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0006248950958251953s
Extra | Recovery of all triples for English Index of Multiple Deprivation Ranking 2010 took 0.902177095413208s
Performance | Total latancy measurement for English Index of Multiple Deprivation Ranking 2010 took 0.8845012187957764s
Amount of data | Number of triples check for English Index of Multiple Deprivation Ranking 2010 took 0.24496889114379883s
Interoperability | New terms check for English Index of Multiple Deprivation Ranking 2010 took 1.627922773361206s
Versatility | Languages check for English Index of Multiple Deprivation Ranking 2010 took 0.28837132453918457s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Ranking 2010 took 0.30246734619140625s
Security | Check HTTPS for English Index of Multiple Deprivation Ranking 2010 took 0.10649728775024414s
Interpretability | RDF structures check for English Index of Multiple Deprivation Ranking 2010 took 0.25661635398864746s
Versatility | Serialization formats check for English Index of Multiple Deprivation Ranking 2010 took 0.41841602325439453s
Availability | RDF dump link check for English Index of Multiple Deprivation Ranking 2010 took 50.87973475456238s
License | MR license check for English Index of Multiple Deprivation Ranking 2010 took 0.25547218322753906s
License | HR license check for English Index of Multiple Deprivation Ranking 2010 took 0.2550532817840576s
Amount of data | Number of property check for English Index of Multiple Deprivation Ranking 2010 took 0.14935517311096191s
Understandability | Number of label check for English Index of Multiple Deprivation Ranking 2010 took 0.25402212142944336s
Understandability | URI regex check for English Index of Multiple Deprivation Ranking 2010 took 1.006432294845581s
Understandability | Vocabs check for English Index of Multiple Deprivation Ranking 2010 took 0.14223647117614746s
Verifiability | Authors check for English Index of Multiple Deprivation Ranking 2010 took 0.140655517578125s
Verifiability | Publishers check for English Index of Multiple Deprivation Ranking 2010 took 0.33733129501342773s
Performance | Throughput check for English Index of Multiple Deprivation Ranking 2010 took 12.112934112548828s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Ranking 2010 took 0.00010919570922851562s
Verifiability | Contribs. check for English Index of Multiple Deprivation Ranking 2010 took 0.15709209442138672s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Ranking 2010 took 0.35260438919067383s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.2386164665222168s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.673572301864624s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Ranking 2010 took 0.16291284561157227s
Currency | Creation date check for English Index of Multiple Deprivation Ranking 2010 took 0.43122076988220215s
Currency | Modification date check for English Index of Multiple Deprivation Ranking 2010 took 0.2567164897918701s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Ranking 2010 took 0.5544602870941162s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Ranking 2010 took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Ranking 2010 took 0.13538861274719238s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.6576459407806396s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.16939949989318848s
Consistency | Disjoint class check for English Index of Multiple Deprivation Ranking 2010 took 0.29619908332824707s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Ranking 2010 took 0.7808346748352051s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Ranking 2010 took 0.19994235038757324s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Ranking 2010 took 1.5856199264526367s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.0002300739288330078s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.32015419006347656s
Security | Sign check for English Index of Multiple Deprivation Ranking 2010 took 0.49917054176330566s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.264695405960083s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.02034926414489746s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.4332275390625e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Ranking 2010 took 1.430511474609375e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 4.5299530029296875e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 176.63758087158203s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.19640898704528809s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0006794929504394531s
Extra | Recovery of all triples for English Index of Multiple Deprivation Score 2010 took 0.23000335693359375s
Performance | Total latancy measurement for English Index of Multiple Deprivation Score 2010 took 0.7426657676696777s
Amount of data | Number of triples check for English Index of Multiple Deprivation Score 2010 took 0.5519726276397705s
Interoperability | New terms check for English Index of Multiple Deprivation Score 2010 took 1.4782519340515137s
Versatility | Languages check for English Index of Multiple Deprivation Score 2010 took 0.2633819580078125s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Score 2010 took 0.23376679420471191s
Security | Check HTTPS for English Index of Multiple Deprivation Score 2010 took 0.633847713470459s
Interpretability | RDF structures check for English Index of Multiple Deprivation Score 2010 took 0.15607714653015137s
Versatility | Serialization formats check for English Index of Multiple Deprivation Score 2010 took 0.13497471809387207s
Availability | RDF dump link check for English Index of Multiple Deprivation Score 2010 took 46.57987666130066s
License | MR license check for English Index of Multiple Deprivation Score 2010 took 0.12997198104858398s
License | HR license check for English Index of Multiple Deprivation Score 2010 took 0.236342191696167s
Amount of data | Number of property check for English Index of Multiple Deprivation Score 2010 took 0.17575621604919434s
Understandability | Number of label check for English Index of Multiple Deprivation Score 2010 took 0.1938762664794922s
Understandability | URI regex check for English Index of Multiple Deprivation Score 2010 took 0.7125341892242432s
Understandability | Vocabs check for English Index of Multiple Deprivation Score 2010 took 0.14691901206970215s
Verifiability | Authors check for English Index of Multiple Deprivation Score 2010 took 0.13912343978881836s
Verifiability | Publishers check for English Index of Multiple Deprivation Score 2010 took 0.14253520965576172s
Performance | Throughput check for English Index of Multiple Deprivation Score 2010 took 10.770833015441895s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Score 2010 took 6.151199340820312e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Score 2010 took 0.1550283432006836s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Score 2010 took 0.18650269508361816s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.13024592399597168s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.1433110237121582s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Score 2010 took 0.14134669303894043s
Currency | Creation date check for English Index of Multiple Deprivation Score 2010 took 1.067887306213379s
Currency | Modification date check for English Index of Multiple Deprivation Score 2010 took 0.11818814277648926s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Score 2010 took 0.9586524963378906s
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.14341115951538086s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Score 2010 took 0.12237286567687988s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Score 2010 took 0.12827515602111816s
Consistency | Disjoint class check for English Index of Multiple Deprivation Score 2010 took 0.15717601776123047s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Score 2010 took 0.4622795581817627s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Score 2010 took 0.21284747123718262s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Score 2010 took 1.5713865756988525s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.0001423358917236328s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.20354795455932617s
Security | Sign check for English Index of Multiple Deprivation Score 2010 took 0.1264946460723877s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.2931947708129883s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.02049875259399414s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.838539123535156e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Score 2010 took 1.6689300537109375e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 5.245208740234375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 162.42397379875183s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 4.1961669921875e-05s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 0.26812243461608887s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.02048969268798828s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 2.9325485229492188e-05s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 7.3909759521484375e-06s
INFO | --- Analysis for english-indices-of-multiple-deprivation took 3.3863766193389893s
Availability | SPARQL endpoint availability check for English Heritage Places took 4.029273986816406e-05s
Availability | VoID file availability check for English Heritage Places took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for English Heritage Places took 0.29630160331726074s
Reputation | Calculation of the PageRank for English Heritage Places took 0.020491361618041992s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 2.956390380859375e-05s
Believability | Calculation of trust value for English Heritage Places took 8.821487426757812e-06s
INFO | --- Analysis for englishheritage_places took 2.920534610748291s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.16706466674804688s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.24924802780151367s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.020870208740234375s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 9.512901306152344e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 6.198883056640625e-06s
INFO | --- Analysis for enipedia took 2.5867114067077637s
Availability | SPARQL endpoint availability check for Entrez Gene took 4.2438507080078125e-05s
Availability | VoID file availability check for Entrez Gene took 0.0008871555328369141s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.2836611270904541s
Reputation | Calculation of the PageRank for Entrez Gene took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.9577484130859375e-05s
Believability | Calculation of trust value for Entrez Gene took 8.106231689453125e-06s
INFO | --- Analysis for entrez_gene took 27.670830726623535s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 4.172325134277344e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.00029277801513671875s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 0.2502424716949463s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.0205080509185791s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 3.147125244140625e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 1.2636184692382812e-05s
INFO | --- Analysis for entrez_gene_extract took 2.917003631591797s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.0729594230651855s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.255922794342041s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.02038097381591797s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 4.9114227294921875e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 5.245208740234375e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 11.791569709777832s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.30948758125305176s
Availability | VoID file availability check for environment.data.gov.uk took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.24792695045471191s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.020585060119628906s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.7206878662109375e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 6.4373016357421875e-06s
INFO | --- Analysis for environment-data-gov-uk took 9.77730393409729s
Availability | SPARQL endpoint availability check for EARTh took 271.29584097862244s
Availability | VoID file availability check for EARTh took 0.0007650852203369141s
Completeness | Calculation of interlinking completeness for EARTh took 0.2779545783996582s
Reputation | Calculation of the PageRank for EARTh took 0.02073812484741211s
Interlinking | Calculation of Degree of Connection for EARTh took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00011539459228515625s
Believability | Calculation of trust value for EARTh took 1.1920928955078125e-05s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 566.894609451294s
Availability | SPARQL endpoint availability check for EPA-CDR took 4.38690185546875e-05s
Availability | VoID file availability check for EPA-CDR took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.3144810199737549s
Reputation | Calculation of the PageRank for EPA-CDR took 0.020528316497802734s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 4.4345855712890625e-05s
Believability | Calculation of trust value for EPA-CDR took 5.7220458984375e-06s
INFO | --- Analysis for epa-cdr took 9.907752275466919s
Availability | SPARQL endpoint availability check for EPA-FRS took 5.078315734863281e-05s
Availability | VoID file availability check for EPA-FRS took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.25186657905578613s
Reputation | Calculation of the PageRank for EPA-FRS took 0.02021050453186035s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.343292236328125e-05s
Believability | Calculation of trust value for EPA-FRS took 5.9604644775390625e-06s
INFO | --- Analysis for epa-frs took 8.121994972229004s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.315376281738281e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.264232873916626s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020319223403930664s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.218650817871094e-05s
Believability | Calculation of trust value for EPA-RCRA took 5.4836273193359375e-06s
INFO | --- Analysis for epa-rcra took 6.244277715682983s
Availability | SPARQL endpoint availability check for EPA-SRS took 4.291534423828125e-05s
Availability | VoID file availability check for EPA-SRS took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.27683496475219727s
Reputation | Calculation of the PageRank for EPA-SRS took 0.020657062530517578s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.62939453125e-05s
Believability | Calculation of trust value for EPA-SRS took 5.9604644775390625e-06s
INFO | --- Analysis for epa-srs took 7.8416173458099365s
Availability | SPARQL endpoint availability check for EPA-TRI took 6.532669067382812e-05s
Availability | VoID file availability check for EPA-TRI took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.26268768310546875s
Reputation | Calculation of the PageRank for EPA-TRI took 0.020818233489990234s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0010848045349121094s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.8623809814453125e-05s
Believability | Calculation of trust value for EPA-TRI took 5.0067901611328125e-06s
INFO | --- Analysis for epa-tri took 6.431030750274658s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 4.076957702636719e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 0.290302038192749s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.02924942970275879s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.0011053085327148438s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 9.655952453613281e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 7.62939453125e-06s
INFO | --- Analysis for epo took 2.922764778137207s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.034728288650512695s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.2698638439178467s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.02102828025817871s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00013899803161621094s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 9.059906005859375e-06s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.4894967079162598s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.5731453895568848s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.28069281578063965s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.020254135131835938s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.130073547363281e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 9.059906005859375e-06s
INFO | --- Analysis for eprtr took 3.695010185241699s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.14578890800476074s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.2582666873931885s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.020970582962036133s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.24249267578125e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 9.5367431640625e-06s
INFO | --- Analysis for es-msssi-drug-prices took 3.312063455581665s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 4.6253204345703125e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.000762939453125s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.2732524871826172s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.02071380615234375s
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.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 9.608268737792969e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 6.67572021484375e-06s
INFO | --- Analysis for esd-standards took 3.9244906902313232s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 4.1961669921875e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0007445812225341797s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.2549779415130615s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.020803451538085938s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.2479248046875e-05s
Believability | Calculation of trust value for ESD-Toolkit took 7.3909759521484375e-06s
INFO | --- Analysis for esd-toolkit took 3.2031891345977783s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 0.14967584609985352s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.2535374164581299s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.020795345306396484s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 8.893013000488281e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 9.775161743164062e-06s
INFO | --- Analysis for eu-agencies-bodies took 2.6889567375183105s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 6.318092346191406e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0003211498260498047s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.2673187255859375s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.02108311653137207s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 3.4332275390625e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 9.298324584960938e-06s
INFO | --- Analysis for eu-dgt-tm took 2.8885393142700195s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 4.506111145019531e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0010309219360351562s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.2576894760131836s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.020786762237548828s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.939338684082031e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 5.9604644775390625e-06s
INFO | --- Analysis for eu-institutions took 2.659876585006714s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 0.11556792259216309s
Availability | VoID file availability check for EU Parliament Media Library took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.2694237232208252s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.02068924903869629s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0009572505950927734s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 4.1484832763671875e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 6.4373016357421875e-06s
INFO | --- Analysis for eu-parliament-media took 2.720221757888794s
Availability | SPARQL endpoint availability check for EU Who Is Who took 0.08925151824951172s
Availability | VoID file availability check for EU Who Is Who took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.2786128520965576s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020895719528198242s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0008726119995117188s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 4.4345855712890625e-05s
Believability | Calculation of trust value for EU Who Is Who took 6.198883056640625e-06s
INFO | --- Analysis for eu-who-is-who took 2.621607542037964s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 0.10486578941345215s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.25816917419433594s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.020814180374145508s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.100799560546875e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 6.198883056640625e-06s
INFO | --- Analysis for eumida-linked-data took 2.5534446239471436s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.28199028968811035s
Availability | VoID file availability check for European Nature Information System took 0.0003688335418701172s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.2753171920776367s
Reputation | Calculation of the PageRank for European Nature Information System took 0.020964622497558594s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0010492801666259766s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00012731552124023438s
Believability | Calculation of trust value for European Nature Information System took 9.298324584960938e-06s
INFO | --- Analysis for eunis took 50.757115602493286s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 0.152679443359375s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.2636418342590332s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.020557880401611328s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.081031799316406e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 6.9141387939453125e-06s
INFO | --- Analysis for eur-lex-rdf took 2.7323546409606934s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 0.08910036087036133s
Availability | VoID file availability check for Standard Eurobarometer took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.2860534191131592s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.020894527435302734s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.00081634521484375s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.601478576660156e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 9.5367431640625e-06s
INFO | --- Analysis for eurobarometer-standard took 3.1819305419921875s
Availability | SPARQL endpoint availability check for European Election Results took 0.09730839729309082s
Availability | VoID file availability check for European Election Results took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for European Election Results took 0.2640345096588135s
Reputation | Calculation of the PageRank for European Election Results took 0.02052760124206543s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.552436828613281e-05s
Believability | Calculation of trust value for European Election Results took 5.4836273193359375e-06s
INFO | --- Analysis for european-election-results took 2.643594741821289s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 5.340576171875e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.2833380699157715s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.02057170867919922s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 3.814697265625e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 9.059906005859375e-06s
INFO | --- Analysis for europeana-lod took 2.942099094390869s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 4.291534423828125e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.323986291885376s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.02054905891418457s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.465217590332031e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 1.0728836059570312e-05s
INFO | --- Analysis for europeana-lod-v1 took 7.330368280410767s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.04375123977661133s
Availability | VoID file availability check for Europeana SPARQL took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.2586936950683594s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.020735502243041992s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 4.9591064453125e-05s
Believability | Calculation of trust value for Europeana SPARQL took 6.4373016357421875e-06s
INFO | --- Analysis for europeana-sparql took 2.5892703533172607s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.07871007919311523s
Availability | VoID file availability check for EuroSentiment took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.3078169822692871s
Reputation | Calculation of the PageRank for EuroSentiment took 0.02084803581237793s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.933906555175781e-05s
Believability | Calculation of trust value for EuroSentiment took 7.867813110351562e-06s
INFO | --- Analysis for eurosentiment took 3.2466466426849365s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 4.363059997558594e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.2686643600463867s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.020720958709716797s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 8.392333984375e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 5.7220458984375e-06s
INFO | --- Analysis for eurostat-rdf took 11.75764775276184s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 4.5299530029296875e-05s
Availability | VoID file availability check for EUROVOC in SKOS took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 0.2692747116088867s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.020562171936035156s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 3.981590270996094e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 8.106231689453125e-06s
INFO | --- Analysis for eurovoc-in-skos took 2.996840715408325s
Availability | SPARQL endpoint availability check for European Television Heritage took 4.1484832763671875e-05s
Availability | VoID file availability check for European Television Heritage took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.280925989151001s
Reputation | Calculation of the PageRank for European Television Heritage took 0.02067422866821289s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 2.9802322387695312e-05s
Believability | Calculation of trust value for European Television Heritage took 6.4373016357421875e-06s
INFO | --- Analysis for euscreen took 2.9186856746673584s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 4.363059997558594e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.2722616195678711s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.0206756591796875s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.7206878662109375e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 4.76837158203125e-06s
INFO | --- Analysis for euskadi-farmacias took 5.506430387496948s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.26760101318359375s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0008165836334228516s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.2682163715362549s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.02044224739074707s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.152557373046875e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 8.344650268554688e-06s
INFO | --- Analysis for eutc-productions took 6.8891496658325195s
Availability | SPARQL endpoint availability check for EventMedia took 0.3868558406829834s
Availability | VoID file availability check for EventMedia took 0.0007309913635253906s
Completeness | Calculation of interlinking completeness for EventMedia took 0.26816701889038086s
Reputation | Calculation of the PageRank for EventMedia took 0.020360946655273438s
Interlinking | Calculation of Degree of Connection for EventMedia took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EventMedia took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.000102996826171875s
Believability | Calculation of trust value for EventMedia took 6.67572021484375e-06s
INFO | --- Analysis for event-media took 10.843387842178345s
Availability | SPARQL endpoint availability check for Eventseer took 2.3992486000061035s
Availability | VoID file availability check for Eventseer took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for Eventseer took 0.2613494396209717s
Reputation | Calculation of the PageRank for Eventseer took 0.02024102210998535s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.553794860839844e-05s
Believability | Calculation of trust value for Eventseer took 8.106231689453125e-06s
INFO | --- Analysis for eventseer took 5.09833836555481s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 4.0531158447265625e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.25880002975463867s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.02055525779724121s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 2.8848648071289062e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 7.3909759521484375e-06s
INFO | --- Analysis for facebook-lids took 2.8771204948425293s
Availability | SPARQL endpoint availability check for Fact Forge took 6.270408630371094e-05s
Availability | VoID file availability check for Fact Forge took 0.0003008842468261719s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.27620720863342285s
Reputation | Calculation of the PageRank for Fact Forge took 0.02054286003112793s
Interlinking | Calculation of Degree of Connection for Fact Forge took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Fact Forge took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 2.8848648071289062e-05s
Believability | Calculation of trust value for Fact Forge took 7.867813110351562e-06s
INFO | --- Analysis for fact-forge took 2.92028546333313s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 4.38690185546875e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.2583627700805664s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.02129507064819336s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 9.608268737792969e-05s
Believability | Calculation of trust value for FAO geopolitical ontology took 5.245208740234375e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 10.510001182556152s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.1628251075744629s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.26360273361206055s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.020430326461791992s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00010085105895996094s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 4.291534423828125e-06s
INFO | --- Analysis for fao-linked-data took 2.6134307384490967s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.663682460784912s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.00041866302490234375s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.26613569259643555s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.02163076400756836s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0009253025054931641s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 5.054473876953125e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 8.58306884765625e-06s
INFO | --- Analysis for farmbio-chembl took 64.44219541549683s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 6.747245788574219e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.25136661529541016s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.0208280086517334s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 3.695487976074219e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 8.106231689453125e-06s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 2.9340200424194336s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.26428675651550293s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.020809412002563477s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 3.24249267578125e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 1.33514404296875e-05s
INFO | --- Analysis for farolapp-dataset took 2.981415033340454s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 4.1961669921875e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.25182056427001953s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.020457029342651367s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Fatal Traffic Accidents in greek roads took 3.218650817871094e-05s
Believability | Calculation of trust value for Fatal Traffic Accidents in greek roads took 8.106231689453125e-06s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 2.864636182785034s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 4.076957702636719e-05s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 0.27333545684814453s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.020598411560058594s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 2.9325485229492188e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 8.344650268554688e-06s
INFO | --- Analysis for federal-economic-rdf took 2.901174783706665s
Availability | SPARQL endpoint availability check for Feed Wrapper took 4.124641418457031e-05s
Availability | VoID file availability check for Feed Wrapper took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 0.26389360427856445s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.02102804183959961s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 3.218650817871094e-05s
Believability | Calculation of trust value for Feed Wrapper took 8.106231689453125e-06s
INFO | --- Analysis for feedwrapper-lids took 2.925729751586914s
Availability | SPARQL endpoint availability check for FiESTA took 4.744529724121094e-05s
Availability | VoID file availability check for FiESTA took 0.0007202625274658203s
Completeness | Calculation of interlinking completeness for FiESTA took 0.368194580078125s
Reputation | Calculation of the PageRank for FiESTA took 0.020679950714111328s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for FiESTA took 3.910064697265625e-05s
Believability | Calculation of trust value for FiESTA took 8.821487426757812e-06s
INFO | --- Analysis for fiesta took 12.688091278076172s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 4.3392181396484375e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.2815666198730469s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.020655393600463867s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 7.176399230957031e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 5.4836273193359375e-06s
INFO | --- Analysis for finnish-municipalities took 12.89039945602417s
Availability | SPARQL endpoint availability check for firmao took 4.220008850097656e-05s
Availability | VoID file availability check for firmao took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for firmao took 0.2919328212738037s
Reputation | Calculation of the PageRank for firmao took 0.0212705135345459s
Interlinking | Calculation of Degree of Connection for firmao took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for firmao took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for firmao took 3.123283386230469e-05s
Believability | Calculation of trust value for firmao took 5.9604644775390625e-06s
INFO | --- Analysis for firmao took 2.867976427078247s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.27722597122192383s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.020874738693237305s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 3.218650817871094e-05s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 1.0967254638671875e-05s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 2.9324631690979004s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.2438507080078125e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.2834796905517578s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.02025604248046875s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 9.1552734375e-05s
Believability | Calculation of trust value for Fishes of Texas took 6.9141387939453125e-06s
INFO | --- Analysis for fishes-of-texas took 3.6773016452789307s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.1961669921875e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.2573375701904297s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.020737171173095703s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.393692016601562e-05s
Believability | Calculation of trust value for flickr? wrappr took 8.58306884765625e-06s
INFO | --- Analysis for flickr-wrappr took 3.3742997646331787s
Availability | SPARQL endpoint availability check for flickr.person took 4.124641418457031e-05s
Availability | VoID file availability check for flickr.person took 0.00032067298889160156s
Completeness | Calculation of interlinking completeness for flickr.person took 0.2541537284851074s
Reputation | Calculation of the PageRank for flickr.person took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for flickr.person took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for flickr.person took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for flickr.person took 2.9325485229492188e-05s
Believability | Calculation of trust value for flickr.person took 6.9141387939453125e-06s
INFO | --- Analysis for flickr_person took 2.8541693687438965s
Availability | SPARQL endpoint availability check for flickr.videoobject took 7.009506225585938e-05s
Availability | VoID file availability check for flickr.videoobject took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 0.2712361812591553s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.020854711532592773s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 3.075599670410156e-05s
Believability | Calculation of trust value for flickr.videoobject took 8.344650268554688e-06s
INFO | --- Analysis for flickr_videoobject took 2.9428117275238037s
Availability | SPARQL endpoint availability check for Fly-TED took 4.315376281738281e-05s
Availability | VoID file availability check for Fly-TED took 0.0002231597900390625s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.24922943115234375s
Reputation | Calculation of the PageRank for Fly-TED took 0.02062392234802246s
Interlinking | Calculation of Degree of Connection for Fly-TED took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Fly-TED took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 3.0517578125e-05s
Believability | Calculation of trust value for Fly-TED took 6.67572021484375e-06s
INFO | --- Analysis for fly-ted took 2.926589250564575s
Availability | SPARQL endpoint availability check for FlyAtlas took 5.53131103515625e-05s
Availability | VoID file availability check for FlyAtlas took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.2522313594818115s
Reputation | Calculation of the PageRank for FlyAtlas took 0.02089095115661621s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 3.1948089599609375e-05s
Believability | Calculation of trust value for FlyAtlas took 6.4373016357421875e-06s
INFO | --- Analysis for flyatlas took 2.960078716278076s
Availability | SPARQL endpoint availability check for Flybase took 1.857745885848999s
Availability | VoID file availability check for Flybase took 0.0007245540618896484s
Completeness | Calculation of interlinking completeness for Flybase took 0.2669506072998047s
Reputation | Calculation of the PageRank for Flybase took 0.02068948745727539s
Interlinking | Calculation of Degree of Connection for Flybase took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Flybase took 4.291534423828125e-05s
Believability | Calculation of trust value for Flybase took 6.67572021484375e-06s
INFO | --- Analysis for flybase took 10.1909499168396s
Availability | SPARQL endpoint availability check for Flyted took 2.7821028232574463s
Availability | VoID file availability check for Flyted took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for Flyted took 0.24596047401428223s
Reputation | Calculation of the PageRank for Flyted took 0.020812034606933594s
Interlinking | Calculation of Degree of Connection for Flyted took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.123283386230469e-05s
Believability | Calculation of trust value for Flyted took 7.62939453125e-06s
INFO | --- Analysis for flyted took 12.424623250961304s
Availability | SPARQL endpoint availability check for Foodista took 0.9629790782928467s
Availability | VoID file availability check for Foodista took 0.0007402896881103516s
Completeness | Calculation of interlinking completeness for Foodista took 0.2770678997039795s
Reputation | Calculation of the PageRank for Foodista took 0.02065110206604004s
Interlinking | Calculation of Degree of Connection for Foodista took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Foodista took 3.24249267578125e-05s
Believability | Calculation of trust value for Foodista took 6.4373016357421875e-06s
INFO | --- Analysis for foodista took 9.785188913345337s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.18196368217468262s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.27533698081970215s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.026837825775146484s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0014929771423339844s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0001049041748046875s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 8.821487426757812e-06s
INFO | --- Analysis for foodpedia took 2.6747384071350098s
Availability | SPARQL endpoint availability check for FORGE Course information took 4.220008850097656e-05s
Availability | VoID file availability check for FORGE Course information took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.24996137619018555s
Reputation | Calculation of the PageRank for FORGE Course information took 0.020772457122802734s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 2.956390380859375e-05s
Believability | Calculation of trust value for FORGE Course information took 5.9604644775390625e-06s
INFO | --- Analysis for forge-course-information took 2.9579601287841797s
Availability | SPARQL endpoint availability check for FrameNet took 4.124641418457031e-05s
Availability | VoID file availability check for FrameNet took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for FrameNet took 0.2556421756744385s
Reputation | Calculation of the PageRank for FrameNet took 0.020647764205932617s
Interlinking | Calculation of Degree of Connection for FrameNet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for FrameNet took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for FrameNet took 3.361701965332031e-05s
Believability | Calculation of trust value for FrameNet took 7.62939453125e-06s
INFO | --- Analysis for framenet took 2.9168848991394043s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.15327978134155273s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.2582864761352539s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.0209047794342041s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.940696716308594e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for frb-linked-data took 2.6511330604553223s
Availability | SPARQL endpoint availability check for Freebase took 5.7220458984375e-05s
Availability | VoID file availability check for Freebase took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Freebase took 0.27506017684936523s
Reputation | Calculation of the PageRank for Freebase took 0.02069258689880371s
Interlinking | Calculation of Degree of Connection for Freebase took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Freebase took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.00026917457580566406s
Believability | Calculation of trust value for Freebase took 1.0013580322265625e-05s
INFO | --- Analysis for freebase took 3.872842788696289s
Availability | SPARQL endpoint availability check for French School Program took 4.172325134277344e-05s
Availability | VoID file availability check for French School Program took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for French School Program took 0.2996039390563965s
Reputation | Calculation of the PageRank for French School Program took 0.020422697067260742s
Interlinking | Calculation of Degree of Connection for French School Program took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for French School Program took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for French School Program took 2.86102294921875e-05s
Believability | Calculation of trust value for French School Program took 6.9141387939453125e-06s
INFO | --- Analysis for french-school-program took 2.9609625339508057s
Availability | SPARQL endpoint availability check for French School System took 4.649162292480469e-05s
Availability | VoID file availability check for French School System took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for French School System took 0.256777286529541s
Reputation | Calculation of the PageRank for French School System took 0.02066516876220703s
Interlinking | Calculation of Degree of Connection for French School System took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for French School System took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for French School System took 3.504753112792969e-05s
Believability | Calculation of trust value for French School System took 6.67572021484375e-06s
INFO | --- Analysis for french-school-system took 7.807282209396362s
Availability | SPARQL endpoint availability check for French TimeBank took 4.1484832763671875e-05s
Availability | VoID file availability check for French TimeBank took 0.000244140625s
Completeness | Calculation of interlinking completeness for French TimeBank took 0.2739412784576416s
Reputation | Calculation of the PageRank for French TimeBank took 0.020440101623535156s
Interlinking | Calculation of Degree of Connection for French TimeBank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for French TimeBank took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 2.86102294921875e-05s
Believability | Calculation of trust value for French TimeBank took 7.152557373046875e-06s
INFO | --- Analysis for french-timebank took 2.8598785400390625s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.7456765174865723s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.26354455947875977s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.224082946777344e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 5.0067901611328125e-06s
INFO | --- Analysis for fu-berlin-cordis took 4.318905591964722s
Availability | SPARQL endpoint availability check for DailyMed took 0.708503246307373s
Availability | VoID file availability check for DailyMed took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for DailyMed took 0.2708275318145752s
Reputation | Calculation of the PageRank for DailyMed took 0.02063608169555664s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.799003601074219e-05s
Believability | Calculation of trust value for DailyMed took 7.62939453125e-06s
INFO | --- Analysis for fu-berlin-dailymed took 5.493714809417725s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.7010507583618164s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0003452301025390625s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.26993894577026367s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.020404338836669922s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.463859558105469e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-dblp took 4.321974515914917s
Availability | SPARQL endpoint availability check for Diseasome took 0.7093648910522461s
Availability | VoID file availability check for Diseasome took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for Diseasome took 0.2703976631164551s
Reputation | Calculation of the PageRank for Diseasome took 0.02049875259399414s
Interlinking | Calculation of Degree of Connection for Diseasome took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00010657310485839844s
Believability | Calculation of trust value for Diseasome took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-diseasome took 5.714324235916138s
Availability | SPARQL endpoint availability check for DrugBank took 0.6935920715332031s
Availability | VoID file availability check for DrugBank took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for DrugBank took 0.3008410930633545s
Reputation | Calculation of the PageRank for DrugBank took 0.02015399932861328s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011849403381347656s
Believability | Calculation of trust value for DrugBank took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-drugbank took 5.6022279262542725s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.7025771141052246s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.26598048210144043s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.02056121826171875s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 2.9802322387695312e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 6.67572021484375e-06s
INFO | --- Analysis for fu-berlin-ec-competition took 4.418864011764526s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.7222893238067627s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.25579357147216797s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.022011518478393555s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0011723041534423828s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 9.846687316894531e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 5.4836273193359375e-06s
INFO | --- Analysis for fu-berlin-euraxess took 4.432557582855225s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.7028272151947021s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.246354341506958s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.02042222023010254s
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.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.748603820800781e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 5.245208740234375e-06s
INFO | --- Analysis for fu-berlin-eures took 4.417245149612427s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.6985774040222168s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0005824565887451172s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.2660832405090332s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.020658016204833984s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.72747802734375e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 5.7220458984375e-06s
INFO | --- Analysis for fu-berlin-eurostat took 5.033744812011719s
Availability | SPARQL endpoint availability check for MediCare took 0.7060611248016357s
Availability | VoID file availability check for MediCare took 0.0005841255187988281s
Completeness | Calculation of interlinking completeness for MediCare took 0.2976207733154297s
Reputation | Calculation of the PageRank for MediCare took 0.021658658981323242s
Interlinking | Calculation of Degree of Connection for MediCare took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for MediCare took 0.001230001449584961s
Interlinking | Calculation of Clustering coefficient for MediCare took 6.651878356933594e-05s
Believability | Calculation of trust value for MediCare took 9.775161743164062e-06s
INFO | --- Analysis for fu-berlin-medicare took 5.079448461532593s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.7525830268859863s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.24878716468811035s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.02036595344543457s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.510185241699219e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 4.466819763183594s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.7348136901855469s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.25212812423706055s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.020416975021362305s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.489059448242188e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 8.344650268554688e-06s
INFO | --- Analysis for fu-berlin-sider took 5.027308225631714s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.7610793113708496s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.2792956829071045s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020749330520629883s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.748603820800781e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 7.867813110351562e-06s
INFO | --- Analysis for fu-berlin-stitch took 4.430911540985107s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 4.1484832763671875e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.24999260902404785s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.02053093910217285s
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.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 3.075599670410156e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 1.430511474609375e-05s
INFO | --- Analysis for galen_from_co-odeorg took 2.8798179626464844s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 4.363059997558594e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007250308990478516s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.2545187473297119s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.020635128021240234s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.172325134277344e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 8.344650268554688e-06s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 5.991900682449341s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 4.3392181396484375e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0003726482391357422s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.2651669979095459s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.02263784408569336s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0009236335754394531s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.0001163482666015625s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 1.0013580322265625e-05s
INFO | --- Analysis for garnicaplywood took 3.2668983936309814s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 4.458427429199219e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.2778787612915039s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.02039813995361328s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.00010085105895996094s
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.525472640991211s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.2648136615753174s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.2790071964263916s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.0205538272857666s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 9.369850158691406e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for gemet took 4.662987470626831s
Availability | SPARQL endpoint availability check for gemet-annotated took 4.220008850097656e-05s
Availability | VoID file availability check for gemet-annotated took 0.0007452964782714844s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.26047420501708984s
Reputation | Calculation of the PageRank for gemet-annotated took 0.020686626434326172s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.743171691894531e-05s
Believability | Calculation of trust value for gemet-annotated took 1.8596649169921875e-05s
INFO | --- Analysis for gemet-annotated took 2.9177768230438232s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.8460474014282227s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.24139928817749023s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.02043914794921875s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 4.029273986816406e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 6.4373016357421875e-06s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.328207015991211s
Availability | SPARQL endpoint availability check for geo.place took 4.506111145019531e-05s
Availability | VoID file availability check for geo.place took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for geo.place took 0.27169275283813477s
Reputation | Calculation of the PageRank for geo.place took 0.020540714263916016s
Interlinking | Calculation of Degree of Connection for geo.place took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for geo.place took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for geo.place took 3.218650817871094e-05s
Believability | Calculation of trust value for geo.place took 8.106231689453125e-06s
INFO | --- Analysis for geo_place took 2.942467451095581s
Availability | SPARQL endpoint availability check for geodomainwn took 4.267692565917969e-05s
Availability | VoID file availability check for geodomainwn took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.28261590003967285s
Reputation | Calculation of the PageRank for geodomainwn took 0.020364999771118164s
Interlinking | Calculation of Degree of Connection for geodomainwn took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for geodomainwn took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 4.6253204345703125e-05s
Believability | Calculation of trust value for geodomainwn took 6.67572021484375e-06s
INFO | --- Analysis for geodomainwn took 6.714436054229736s
Availability | SPARQL endpoint availability check for GeoEcuador took 4.315376281738281e-05s
Availability | VoID file availability check for GeoEcuador took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.26109933853149414s
Reputation | Calculation of the PageRank for GeoEcuador took 0.023658037185668945s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0021691322326660156s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 0.00017714500427246094s
Believability | Calculation of trust value for GeoEcuador took 5.7220458984375e-06s
INFO | --- Analysis for geoecuador took 12.51487398147583s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.527510404586792s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0006997585296630859s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.27181529998779297s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.020727872848510742s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 7.62939453125e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 7.3909759521484375e-06s
INFO | --- Analysis for geographic-names-information-system-gnis took 47.87303805351257s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 4.172325134277344e-05s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.2704010009765625s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.020772218704223633s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 3.695487976074219e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 8.344650268554688e-06s
INFO | --- Analysis for geographic-openuplabs took 2.9447884559631348s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.5313224792480469s
Availability | VoID file availability check for GeoLinkedData took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.2690110206604004s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.021008014678955078s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0008788108825683594s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 0.00010323524475097656s
Believability | Calculation of trust value for GeoLinkedData took 1.430511474609375e-05s
INFO | --- Analysis for geolinkeddata took 3.943589687347412s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.19163727760314941s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0005948543548583984s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 8.987863540649414s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.39923930168151855s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.1849973201751709s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.5586838722229004s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.18946146965026855s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.1994023323059082s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.21689319610595703s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.0952908992767334s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.08818173408508301s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.07604503631591797s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.09475827217102051s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 1.994225263595581s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.09612250328063965s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.09437394142150879s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.13736891746520996s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.10253429412841797s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.062413692474365234s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.09456872940063477s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.401991605758667s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 7.128715515136719e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.0778350830078125s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.06857657432556152s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.09474802017211914s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.062071800231933594s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.07633304595947266s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.16739749908447266s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.1711122989654541s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.3379175662994385s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.10158705711364746s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.061109066009521484s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06779623031616211s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.34235715866088867s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.007377147674560547s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.23221945762634277s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.06126046180725098s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.24681997299194336s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5280251502990723s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 3.247274875640869s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.5438756942749023s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.7418079376220703s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.17905092239379883s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.061862945556640625s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 1.0542466640472412s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.3735625743865967s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.020542383193969727s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.726119995117188e-05s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 112.42450594902039s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 0.00011849403381347656s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.27114200592041016s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.0203096866607666s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0004742145538330078s
Believability | Calculation of trust value for GeoNames Semantic Web took 7.152557373046875e-06s
INFO | --- Analysis for geonames-semantic-web took 3.294546127319336s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.545753002166748s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.24159693717956543s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.0201723575592041s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00013756752014160156s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 1.0728836059570312e-05s
INFO | --- Analysis for geospecies took 5.72711968421936s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.3392181396484375e-05s
Availability | VoID file availability check for GeoWordNet took 0.0004038810729980469s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.2631566524505615s
Reputation | Calculation of the PageRank for GeoWordNet took 0.0201265811920166s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 5.1021575927734375e-05s
Believability | Calculation of trust value for GeoWordNet took 7.62939453125e-06s
INFO | --- Analysis for geowordnet took 7.182528734207153s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.08139562606811523s
Availability | VoID file availability check for German labor law thesaurus took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.2706730365753174s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.020203351974487305s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 8.559226989746094e-05s
Believability | Calculation of trust value for German labor law thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for german-labor-law-thesaurus took 2.4723682403564453s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.2438507080078125e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.00041961669921875s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.26370835304260254s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.020439624786376953s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.601478576660156e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 7.867813110351562e-06s
INFO | --- Analysis for germlex took 2.7084121704101562s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.5642032623291016s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0003502368927001953s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.27018284797668457s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020613431930541992s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.00010132789611816406s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 8.106231689453125e-06s
INFO | --- Analysis for gesis-thesoz took 5.964763641357422s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.7660369873046875s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.2785348892211914s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.020087242126464844s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.605552673339844e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for getty-aat took 16.230583667755127s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.3413386344909668s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.00030541419982910156s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.27020955085754395s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020299911499023438s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.316734313964844e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 7.152557373046875e-06s
INFO | --- Analysis for getty-tgn took 13.13397479057312s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 0.2980003356933594s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.24973344802856445s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.020531415939331055s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.075599670410156e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 5.4836273193359375e-06s
INFO | --- Analysis for gipuzkoademografia took 2.8644888401031494s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 4.291534423828125e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.2833104133605957s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.020450353622436523s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.075599670410156e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 6.198883056640625e-06s
INFO | --- Analysis for glastonbury-2011 took 5.641218423843384s
Availability | SPARQL endpoint availability check for Global Change Information System took 4.0531158447265625e-05s
Availability | VoID file availability check for Global Change Information System took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.24774551391601562s
Reputation | Calculation of the PageRank for Global Change Information System took 0.020289897918701172s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 2.956390380859375e-05s
Believability | Calculation of trust value for Global Change Information System took 6.67572021484375e-06s
INFO | --- Analysis for global-change-information-system took 2.9168426990509033s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 4.839897155761719e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.00032830238342285156s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.2568960189819336s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.020418167114257812s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 4.649162292480469e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 7.867813110351562e-06s
INFO | --- Analysis for global-hunger-index-2011 took 2.9921863079071045s
Availability | SPARQL endpoint availability check for Glottolog took 4.291534423828125e-05s
Availability | VoID file availability check for Glottolog took 0.00034427642822265625s
Completeness | Calculation of interlinking completeness for Glottolog took 0.23297476768493652s
Reputation | Calculation of the PageRank for Glottolog took 0.02060222625732422s
Interlinking | Calculation of Degree of Connection for Glottolog took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Glottolog took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Glottolog took 4.839897155761719e-05s
Believability | Calculation of trust value for Glottolog took 7.867813110351562e-06s
INFO | --- Analysis for glottolog took 6.862756252288818s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 4.267692565917969e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.00035381317138671875s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.2747802734375s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.020830154418945312s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0008120536804199219s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00011324882507324219s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 7.867813110351562e-06s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 9.94807505607605s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 4.887580871582031e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.26215052604675293s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.020305633544921875s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 3.0040740966796875e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 8.58306884765625e-06s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 2.9270026683807373s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 6.365776062011719e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.23935222625732422s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0204010009765625s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 3.0517578125e-05s
Believability | Calculation of trust value for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 8.106231689453125e-06s
INFO | --- Analysis for go_annotations_from_ncbi_and_ebi took 2.895517587661743s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 4.649162292480469e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0006995201110839844s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.27137064933776855s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020346879959106445s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.054473876953125e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 7.62939453125e-06s
INFO | --- Analysis for gold took 4.122287034988403s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 4.315376281738281e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.26973605155944824s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.02462315559387207s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0014176368713378906s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 0.00010347366333007812s
Believability | Calculation of trust value for GoogleArt wrapper took 8.344650268554688e-06s
INFO | --- Analysis for googleart-wrapper took 2.77579665184021s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.13850069046020508s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.24060297012329102s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.020916223526000977s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 4.1484832763671875e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 7.3909759521484375e-06s
INFO | --- Analysis for govagribus-denmark took 34.887465715408325s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.408944606781006s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.27429914474487305s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020580053329467773s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 8.726119995117188e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 23.92273712158203s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.6501469612121582s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.00036644935607910156s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.24110054969787598s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.02061009407043457s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 8.893013000488281e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 5.0067901611328125e-06s
INFO | --- Analysis for govtrack took 10.186445951461792s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 4.2438507080078125e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.26773858070373535s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.021008968353271484s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 6.341934204101562e-05s
Believability | Calculation of trust value for greek-administrative-geography took 7.3909759521484375e-06s
INFO | --- Analysis for greek-administrative-geography took 2.612929582595825s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.1463623046875s
Availability | VoID file availability check for Greek Wordnet took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.27377939224243164s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.020708799362182617s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.076957702636719e-05s
Believability | Calculation of trust value for Greek Wordnet took 1.1920928955078125e-05s
INFO | --- Analysis for greek-wordnet took 2.4798150062561035s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 5.2928924560546875e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0007901191711425781s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.26212430000305176s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.0205535888671875s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.00011229515075683594s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 5.9604644775390625e-06s
INFO | --- Analysis for green-competitiveness-gnoss took 7.679397344589233s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 1.2791259288787842s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.2785313129425049s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.020688772201538086s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 5.269050598144531e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 1.7404556274414062e-05s
INFO | --- Analysis for grrp took 3.8056421279907227s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.1828186511993408s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.26318979263305664s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.020495176315307617s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 7.05718994140625e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 6.4373016357421875e-06s
INFO | --- Analysis for grrt took 3.6934750080108643s
Availability | SPARQL endpoint availability check for Project Gutenberg took 5.626678466796875e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.25646328926086426s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.023049116134643555s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 7.152557373046875e-05s
Believability | Calculation of trust value for Project Gutenberg took 9.059906005859375e-06s
INFO | --- Analysis for gutenberg took 8.258565187454224s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 4.172325134277344e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.27993178367614746s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.020587444305419922s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 3.147125244140625e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 8.58306884765625e-06s
INFO | --- Analysis for hcls-knowledge-base took 2.9676496982574463s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 5.3882598876953125e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.2732968330383301s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.022020578384399414s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0009641647338867188s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 8.654594421386719e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 9.5367431640625e-06s
INFO | --- Analysis for heartfailure took 3.0602853298187256s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.582086324691772s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.3083961009979248s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.02055501937866211s
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.9788742065429688e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 3.790855407714844e-05s
Believability | Calculation of trust value for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 7.3909759521484375e-06s
INFO | --- Analysis for hebis-bibliographic-resources took 120.7517204284668s
Availability | SPARQL endpoint availability check for Hedatuz took 0.2622952461242676s
Availability | VoID file availability check for Hedatuz took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.2640552520751953s
Reputation | Calculation of the PageRank for Hedatuz took 0.02040863037109375s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 3.743171691894531e-05s
Believability | Calculation of trust value for Hedatuz took 7.3909759521484375e-06s
INFO | --- Analysis for hedatuz took 3.075307607650757s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.13434958457946777s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0004458427429199219s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.2705726623535156s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.020297765731811523s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00012421607971191406s
Believability | Calculation of trust value for Hellenic Fire Brigade took 9.5367431640625e-06s
INFO | --- Analysis for hellenic-fire-brigade took 3.4015817642211914s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.02475571632385254s
Availability | VoID file availability check for Hellenic Police took 0.0004112720489501953s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.2770419120788574s
Reputation | Calculation of the PageRank for Hellenic Police took 0.020433902740478516s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00012612342834472656s
Believability | Calculation of trust value for Hellenic Police took 5.245208740234375e-06s
INFO | --- Analysis for hellenic-police took 2.5828733444213867s
Availability | SPARQL endpoint availability check for Homologene took 4.00543212890625e-05s
Availability | VoID file availability check for Homologene took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for Homologene took 0.2762014865875244s
Reputation | Calculation of the PageRank for Homologene took 0.02043938636779785s
Interlinking | Calculation of Degree of Connection for Homologene took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Homologene took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Homologene took 2.956390380859375e-05s
Believability | Calculation of trust value for Homologene took 6.67572021484375e-06s
INFO | --- Analysis for homologene took 2.9693045616149902s
Availability | SPARQL endpoint availability check for Noticias Universia took 5.364418029785156e-05s
Availability | VoID file availability check for Noticias Universia took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.24110198020935059s
Reputation | Calculation of the PageRank for Noticias Universia took 0.02130913734436035s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 3.4332275390625e-05s
Believability | Calculation of trust value for Noticias Universia took 7.3909759521484375e-06s
INFO | --- Analysis for http-data-noticias-universia-net took 2.87125563621521s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 4.291534423828125e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.25618600845336914s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.020384550094604492s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 3.218650817871094e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 7.3909759521484375e-06s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 2.96035099029541s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 4.363059997558594e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.3230586051940918s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.0207059383392334s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 3.123283386230469e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 1.3589859008789062e-05s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 3.0571439266204834s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 4.1961669921875e-05s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.3002622127532959s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.020522356033325195s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 3.0517578125e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 6.67572021484375e-06s
INFO | --- Analysis for hud-library-usagedata took 2.9912302494049072s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.3564765453338623s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.2526383399963379s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.020566940307617188s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00010633468627929688s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 6.9141387939453125e-06s
INFO | --- Analysis for hungarian-national-library-catalog took 4.100787878036499s
Availability | SPARQL endpoint availability check for IATE RDF took 4.172325134277344e-05s
Availability | VoID file availability check for IATE RDF took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.26511645317077637s
Reputation | Calculation of the PageRank for IATE RDF took 0.0203704833984375s
Interlinking | Calculation of Degree of Connection for IATE RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.600120544433594e-05s
Believability | Calculation of trust value for IATE RDF took 6.4373016357421875e-06s
INFO | --- Analysis for iate-rdf took 3.0578536987304688s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.13945198059082s
Availability | VoID file availability check for IATI as Linked Data took 0.0004143714904785156s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.24231362342834473s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.02065563201904297s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.392333984375e-05s
Believability | Calculation of trust value for IATI as Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for iati-as-linked-data took 13.328696966171265s
Availability | SPARQL endpoint availability check for ICANE took 0.3436753749847412s
Availability | VoID file availability check for ICANE took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for ICANE took 0.28685736656188965s
Reputation | Calculation of the PageRank for ICANE took 0.020365476608276367s
Interlinking | Calculation of Degree of Connection for ICANE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.535385131835938e-05s
Believability | Calculation of trust value for ICANE took 5.4836273193359375e-06s
INFO | --- Analysis for icane took 3.7054128646850586s
Availability | SPARQL endpoint availability check for ichoose took 0.16124391555786133s
Availability | VoID file availability check for ichoose took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for ichoose took 0.26234912872314453s
Reputation | Calculation of the PageRank for ichoose took 0.020913362503051758s
Interlinking | Calculation of Degree of Connection for ichoose took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ichoose took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for ichoose took 7.534027099609375e-05s
Believability | Calculation of trust value for ichoose took 7.3909759521484375e-06s
INFO | --- Analysis for ichoose took 42.49401593208313s
Availability | SPARQL endpoint availability check for Identifiers.org took 4.4345855712890625e-05s
Availability | VoID file availability check for Identifiers.org took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for Identifiers.org took 0.24985694885253906s
Reputation | Calculation of the PageRank for Identifiers.org took 0.02066969871520996s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 3.886222839355469e-05s
Believability | Calculation of trust value for Identifiers.org took 8.106231689453125e-06s
INFO | --- Analysis for identifiers-org took 2.8844921588897705s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 4.458427429199219e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0007963180541992188s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.2564420700073242s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.02055978775024414s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0008037090301513672s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.724761962890625e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 2.6226043701171875e-05s
INFO | --- Analysis for idreffr took 3.657358169555664s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.890704870223999s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.27921438217163086s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.02062392234802246s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 4.935264587402344e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 8.106231689453125e-06s
INFO | --- Analysis for ids took 3.856581926345825s
Availability | SPARQL endpoint availability check for ietflang took 4.220008850097656e-05s
Availability | VoID file availability check for ietflang took 0.001384735107421875s
Completeness | Calculation of interlinking completeness for ietflang took 0.27778029441833496s
Reputation | Calculation of the PageRank for ietflang took 0.02019047737121582s
Interlinking | Calculation of Degree of Connection for ietflang took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ietflang took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.601478576660156e-05s
Believability | Calculation of trust value for ietflang took 7.62939453125e-06s
INFO | --- Analysis for ietflang took 12.663312673568726s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 1.0167748928070068s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.26070713996887207s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.020414352416992188s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 3.123283386230469e-05s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 8.58306884765625e-06s
INFO | --- Analysis for iislod-test took 3.4448623657226562s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.135765790939331s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0006427764892578125s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 15.121942281723022s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.422804832458496s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 9.993269681930542s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.6384804248809814s
Versatility | Languages check for Imagesnippets Image Descriptions took 10.681385517120361s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 7.831971645355225s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.6811800003051758s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7425391674041748s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.7151069641113281s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7086806297302246s
License | MR license check for Imagesnippets Image Descriptions took 0.6819040775299072s
License | HR license check for Imagesnippets Image Descriptions took 10.68562126159668s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.7121171951293945s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.722372531890869s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.4162101745605469s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.7029104232788086s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.7009787559509277s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.7156023979187012s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.593561172485352s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 7.62939453125e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.6866793632507324s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.7140316963195801s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7089986801147461s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7213914394378662s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.7265603542327881s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.4292240142822266s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.3923077583312988s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 20.537851572036743s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.727971076965332s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.7001163959503174s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.7315406799316406s
Accuracy | Check Empty annotation labels for Imagesnippets Image Descriptions took 10.523171663284302s
Accuracy | Check White space in annotation for Imagesnippets Image Descriptions took 2.2438113689422607s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.7201788425445557s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.704177618026733s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 4.011327505111694s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.43055510520935s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 0.00014901161193847656s
Security | Sign check for Imagesnippets Image Descriptions took 0.7143006324768066s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.3210623264312744s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.020932912826538086s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 9.417533874511719e-05s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 1.6689300537109375e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 8.106231689453125e-06s
INFO | --- Analysis for imagesnippets took 216.80330109596252s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.47138404846191406s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.7162024974822998s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 9.298324584960938e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 1.33514404296875e-05s
INFO | --- Analysis for imf-linked-data took 3.787191867828369s
Availability | SPARQL endpoint availability check for IMGpedia took 8.368492126464844e-05s
Availability | VoID file availability check for IMGpedia took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.2559337615966797s
Reputation | Calculation of the PageRank for IMGpedia took 0.02077960968017578s
Interlinking | Calculation of Degree of Connection for IMGpedia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IMGpedia took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 3.0279159545898438e-05s
Believability | Calculation of trust value for IMGpedia took 8.344650268554688e-06s
INFO | --- Analysis for imgpedia took 2.8856213092803955s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 4.124641418457031e-05s
Availability | VoID file availability check for Import Status of GMO Crops took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 0.26648712158203125s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.020770788192749023s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 2.9802322387695312e-05s
Believability | Calculation of trust value for Import Status of GMO Crops took 1.4781951904296875e-05s
INFO | --- Analysis for import-status-of-gmo-crops took 2.8760387897491455s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 4.1961669921875e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 0.25966691970825195s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.020641565322875977s
Interlinking | Calculation of Degree of Connection for Income and production cost of grape by year took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Income and production cost of grape by year took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 3.123283386230469e-05s
Believability | Calculation of trust value for Income and production cost of grape by year took 8.106231689453125e-06s
INFO | --- Analysis for income-and-production-cost-of-grape-by-year took 2.9581761360168457s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 5.221366882324219e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.26064229011535645s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.020434856414794922s
Interlinking | Calculation of Degree of Connection for Income and production cost of pear by year took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Income and production cost of pear by year took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Income and production cost of pear by year took 3.24249267578125e-05s
Believability | Calculation of trust value for Income and production cost of pear by year took 7.3909759521484375e-06s
INFO | --- Analysis for income-and-production-cost-of-pear-by-year took 2.8947951793670654s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 4.076957702636719e-05s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0003020763397216797s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.2684643268585205s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.02474069595336914s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.001219034194946289s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 4.124641418457031e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.1205673217773438e-05s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 2.938345193862915s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 4.2438507080078125e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.2691764831542969s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00011205673217773438s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 8.821487426757812e-06s
INFO | --- Analysis for ineverycrea took 26.69910454750061s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 4.3392181396484375e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007865428924560547s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.2680654525756836s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.02047896385192871s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.918212890625e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 3.170967102050781e-05s
INFO | --- Analysis for ineverycrea-argentina took 16.633146286010742s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 0.05130195617675781s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.26219701766967773s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.020685195922851562s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 7.128715515136719e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 8.106231689453125e-06s
INFO | --- Analysis for influence-tracker-dataset took 12.978399515151978s
Availability | SPARQL endpoint availability check for INSEMTIVES took 4.7206878662109375e-05s
Availability | VoID file availability check for INSEMTIVES took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.26308631896972656s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.020960330963134766s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 3.218650817871094e-05s
Believability | Calculation of trust value for INSEMTIVES took 7.3909759521484375e-06s
INFO | --- Analysis for insemtives took 2.947988748550415s
Availability | SPARQL endpoint availability check for instagram.person took 4.100799560546875e-05s
Availability | VoID file availability check for instagram.person took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for instagram.person took 0.27968573570251465s
Reputation | Calculation of the PageRank for instagram.person took 0.020408153533935547s
Interlinking | Calculation of Degree of Connection for instagram.person took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for instagram.person took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for instagram.person took 3.123283386230469e-05s
Believability | Calculation of trust value for instagram.person took 8.106231689453125e-06s
INFO | --- Analysis for instagram_person took 2.8675761222839355s
Availability | SPARQL endpoint availability check for instagram.videoobject took 4.673004150390625e-05s
Availability | VoID file availability check for instagram.videoobject took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 0.2496788501739502s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.02048325538635254s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 2.9802322387695312e-05s
Believability | Calculation of trust value for instagram.videoobject took 7.62939453125e-06s
INFO | --- Analysis for instagram_videoobject took 2.8660120964050293s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 4.3392181396484375e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.00029587745666503906s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.2778749465942383s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.020986557006835938s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 3.457069396972656e-05s
Believability | Calculation of trust value for Instance Hub Countries took 8.106231689453125e-06s
INFO | --- Analysis for instance-hub-countries took 2.9630448818206787s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.363059997558594e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.2608170509338379s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.020259618759155273s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 2.8371810913085938e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 7.867813110351562e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 2.340059757232666s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 5.173683166503906e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.27212023735046387s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.020442485809326172s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 3.0040740966796875e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-organizations took 2.9189653396606445s
Availability | SPARQL endpoint availability check for Instance Hub People took 4.100799560546875e-05s
Availability | VoID file availability check for Instance Hub People took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.27886033058166504s
Reputation | Calculation of the PageRank for Instance Hub People took 0.020433425903320312s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 2.86102294921875e-05s
Believability | Calculation of trust value for Instance Hub People took 6.9141387939453125e-06s
INFO | --- Analysis for instance-hub-people took 2.958343267440796s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 4.076957702636719e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.26732826232910156s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.020262956619262695s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 2.7894973754882812e-05s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 1.3113021850585938e-05s
INFO | --- Analysis for instance-hub-us-civil-servants took 2.8961105346679688s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 4.076957702636719e-05s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.25357937812805176s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.020325183868408203s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 2.9087066650390625e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-us-congressional-committees took 2.9416160583496094s
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.0004725456237792969s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.2380235195159912s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.020560503005981445s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.0008416175842285156s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 2.9325485229492188e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-us-congressional-districts took 2.890423536300659s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 4.100799560546875e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.273087739944458s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.020449399948120117s
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.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 2.9325485229492188e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-us-crops took 2.9209604263305664s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 4.076957702636719e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.2574889659881592s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.02026057243347168s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 2.7894973754882812e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-us-federal-agencies took 2.9097771644592285s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 4.1484832763671875e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.24425339698791504s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.02064228057861328s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 2.8371810913085938e-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.941373348236084s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 4.172325134277344e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.26822471618652344s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.020441055297851562s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 3.4809112548828125e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 8.106231689453125e-06s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 3.007284164428711s
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.0002586841583251953s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.2615208625793457s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.020406484603881836s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 2.86102294921875e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 7.867813110351562e-06s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 2.9388647079467773s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.2438507080078125e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.27431344985961914s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.020366907119750977s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.465217590332031e-05s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for interactivemaps-gnoss took 9.153808832168579s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 4.124641418457031e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.0007212162017822266s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.266845703125s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.020348310470581055s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 3.147125244140625e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 9.775161743164062e-06s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 3.1712076663970947s
Availability | SPARQL endpoint availability check for intervalue took 0.15433216094970703s
Availability | VoID file availability check for intervalue took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for intervalue took 0.2919495105743408s
Reputation | Calculation of the PageRank for intervalue took 0.020328283309936523s
Interlinking | Calculation of Degree of Connection for intervalue took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for intervalue took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.699562072753906e-05s
Believability | Calculation of trust value for intervalue took 7.3909759521484375e-06s
INFO | --- Analysis for intervalue took 2.56723952293396s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.3392181396484375e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.26212120056152344s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.020168542861938477s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.172325134277344e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 1.9073486328125e-05s
INFO | --- Analysis for iptc-newscodes took 3.4313108921051025s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 4.100799560546875e-05s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.2700841426849365s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.020337581634521484s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 2.8133392333984375e-05s
Believability | Calculation of trust value for Irstea Weather Dataset of the Montoldre Experimental Farm took 8.106231689453125e-06s
INFO | --- Analysis for irstea-weather-dataset-of-the-montoldre-experimental-farm took 2.873880386352539s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 2.3539562225341797s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0007276535034179688s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.23637723922729492s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.02015829086303711s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.655952453613281e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 1.2159347534179688e-05s
INFO | --- Analysis for iserve took 9.214966773986816s
Availability | SPARQL endpoint availability check for ISIC V4 took 20.79114031791687s
Availability | VoID file availability check for ISIC V4 took 0.0008826255798339844s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.2721855640411377s
Reputation | Calculation of the PageRank for ISIC V4 took 0.021834850311279297s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 3.886222839355469e-05s
Believability | Calculation of trust value for ISIC V4 took 5.9604644775390625e-06s
INFO | --- Analysis for isic-v4 took 117.149729013443s
Availability | SPARQL endpoint availability check for Isidore took 4.124641418457031e-05s
Availability | VoID file availability check for Isidore took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Isidore took 0.2794654369354248s
Reputation | Calculation of the PageRank for Isidore took 0.020379304885864258s
Interlinking | Calculation of Degree of Connection for Isidore took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Isidore took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for Isidore took 2.956390380859375e-05s
Believability | Calculation of trust value for Isidore took 8.344650268554688e-06s
INFO | --- Analysis for isidore took 3.011413335800171s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 4.076957702636719e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.26653432846069336s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.020257234573364258s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 3.075599670410156e-05s
Believability | Calculation of trust value for Linked ISO 3166-2 Data took 7.62939453125e-06s
INFO | --- Analysis for iso-3166-2-data took 2.9554948806762695s
Availability | SPARQL endpoint availability check for ISOcat took 4.363059997558594e-05s
Availability | VoID file availability check for ISOcat took 0.0006973743438720703s
Completeness | Calculation of interlinking completeness for ISOcat took 0.27568817138671875s
Reputation | Calculation of the PageRank for ISOcat took 0.020373821258544922s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.151199340820312e-05s
Believability | Calculation of trust value for ISOcat took 7.867813110351562e-06s
INFO | --- Analysis for isocat took 33.1800262928009s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 4.482269287109375e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.27085185050964355s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.02025604248046875s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.600120544433594e-05s
Believability | Calculation of trust value for ISOcat-metadata took 8.344650268554688e-06s
INFO | --- Analysis for isocat-metadata took 4.89163064956665s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 4.38690185546875e-05s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 0.27910828590393066s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.020384550094604492s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 2.86102294921875e-05s
Believability | Calculation of trust value for ISPRA - Mitigation measures in Italy for national soil protection took 8.106231689453125e-06s
INFO | --- Analysis for ispra-lod-ihi took 2.9297568798065186s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.8102900981903076s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0006461143493652344s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 5.936376094818115s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.7879433631896973s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.21290969848632812s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 3.0892953872680664s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.00587153434753s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2087087631225586s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.10048651695251465s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1653447151184082s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1457834243774414s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.16951560974121094s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.21686291694641113s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.64366602897644s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1608884334564209s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.2129461765289307s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.4155771732330322s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.19581174850463867s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2106175422668457s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1667771339416504s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.603451251983643s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0001049041748046875s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.21696877479553223s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.276688814163208s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.5153653621673584s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.5143535137176514s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20736169815063477s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.348712682723999s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15907716751098633s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 13.967803239822388s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1676328182220459s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14340853691101074s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15410113334655762s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.8751795291900635s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3135411739349365s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2642645835876465s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14391326904296875s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.70685863494873s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9426734447479248s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 3.0746285915374756s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.305464506149292s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.85322618484497s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.28444743156433105s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2361917495727539s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.19330215454101562s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 11.255319595336914s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.41611719131469727s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.02067875862121582s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00010132789611816406s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.6689300537109375e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.239776611328125e-05s
INFO | --- Analysis for ispra-lod-place took 462.374107837677s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 4.673004150390625e-05s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.2725789546966553s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.020975351333618164s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 2.86102294921875e-05s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 8.106231689453125e-06s
INFO | --- Analysis for ispra-lod-rmn took 4.843611478805542s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.16071796417236328s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0005545616149902344s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 6.6210527420043945s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.799670934677124s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.2172083854675293s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 3.0479304790496826s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 91.97215437889099s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.17149662971496582s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.10985136032104492s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.19561409950256348s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.18559622764587402s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.1497809886932373s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.20216727256774902s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 92.36426663398743s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.202070951461792s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.1554985046386719s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.46622300148010254s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.1819758415222168s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.1876366138458252s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.17698884010314941s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.484968423843384s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 3.4809112548828125e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.1842339038848877s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.24149036407470703s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.4987518787384033s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.48223137855529785s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.20372486114501953s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.3372642993927002s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.13566327095031738s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 14.123438596725464s
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.1282498836517334s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.15179848670959473s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.15805387496948242s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 3.0465314388275146s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.31580400466918945s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.26256608963012695s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.1474745273590088s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 9.629623889923096s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.9570727348327637s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 3.10595965385437s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.3084285259246826s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.92140817642212s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.2850825786590576s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.20869135856628418s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.1756880283355713s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 10.225605487823486s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.5907309055328369s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.021028995513916016s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 4.291534423828125e-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 9.059906005859375e-06s
INFO | --- Analysis for ispra-lod-ron took 458.3785104751587s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 5.412101745605469e-05s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 0.7268579006195068s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.020752429962158203s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 3.2901763916015625e-05s
Believability | Calculation of trust value for ISPRA - Soil Consumption Indicators in Italy took 7.152557373046875e-06s
INFO | --- Analysis for ispra-lod-sc took 4.784231424331665s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 1.6629798412322998s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.23833703994750977s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.020520925521850586s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 9.036064147949219e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 5.4836273193359375e-06s
INFO | --- Analysis for istat-immigration took 5.00370454788208s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 4.291534423828125e-05s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 0.2715873718261719s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.02074408531188965s
Interlinking | Calculation of Degree of Connection for ISTAT Immigrazione (Linkedopendata.it) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ISTAT Immigrazione (Linkedopendata.it) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 3.147125244140625e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 8.58306884765625e-06s
INFO | --- Analysis for istat-immigrazione took 3.3537850379943848s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.13058161735534668s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.2690470218658447s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.02033376693725586s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 2.9087066650390625e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 5.245208740234375e-06s
INFO | --- Analysis for it-aifa-drug-prices took 2.761854887008667s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.0365290641784668s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.27619123458862305s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.020377635955810547s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.319450378417969e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 6.9141387939453125e-06s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 3.4258086681365967s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 4.076957702636719e-05s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.271176815032959s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.020533084869384766s
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.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 2.86102294921875e-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.8368124961853027s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 4.887580871582031e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.0003018379211425781s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.27350282669067383s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.020468950271606445s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 3.0279159545898438e-05s
Believability | Calculation of trust value for IWMI Research Reports took 1.2874603271484375e-05s
INFO | --- Analysis for iwmi-research-reports took 3.3458187580108643s
Availability | SPARQL endpoint availability check for IWN took 4.220008850097656e-05s
Availability | VoID file availability check for IWN took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for IWN took 0.27034974098205566s
Reputation | Calculation of the PageRank for IWN took 0.020652294158935547s
Interlinking | Calculation of Degree of Connection for IWN took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IWN took 0.0007262229919433594s
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 5.8541364669799805s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 4.124641418457031e-05s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.2659149169921875s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.02061939239501953s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 3.266334533691406e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 7.3909759521484375e-06s
INFO | --- Analysis for j-global-knowledge took 3.39646053314209s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 6.961822509765625e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.26152658462524414s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.020670175552368164s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 3.123283386230469e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 9.298324584960938e-06s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 2.938769578933716s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 9.106744766235352s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.27288341522216797s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.020573854446411133s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.413459777832031e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 5.7220458984375e-06s
INFO | --- Analysis for jamendo-dbtune took 25.251795291900635s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 4.291534423828125e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.269289493560791s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.022312164306640625s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 5.054473876953125e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for japan-radioactivity-stat took 4.32899284362793s
Availability | SPARQL endpoint availability check for JEL Classification took 9.942054748535156e-05s
Availability | VoID file availability check for JEL Classification took 0.0005943775177001953s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.2546992301940918s
Reputation | Calculation of the PageRank for JEL Classification took 0.020635366439819336s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 3.695487976074219e-05s
Believability | Calculation of trust value for JEL Classification took 8.106231689453125e-06s
INFO | --- Analysis for jel-classification took 4.659597396850586s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.1565656661987305s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0007054805755615234s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.27228474617004395s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.021169424057006836s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.170967102050781e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 1.1682510375976562e-05s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 7.604511022567749s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 260.99245953559875s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.30678725242614746s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 8.034706115722656e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 8.344650268554688e-06s
INFO | --- Analysis for jita took 539.8231468200684s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 4.38690185546875e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.2723519802093506s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.02044844627380371s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 2.8371810913085938e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 7.62939453125e-06s
INFO | --- Analysis for jmdict took 4.283429861068726s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.056774854660034s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0006132125854492188s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.7176434993743896s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.020403385162353516s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 8.96453857421875e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 7.3909759521484375e-06s
INFO | --- Analysis for john-goodwins-family-tree took 64.75771498680115s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 1.166494607925415s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.25388360023498535s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.020279884338378906s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.771087646484375e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 7.867813110351562e-06s
INFO | --- Analysis for jrc-names-mlode took 4.712559223175049s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.315376281738281e-05s
Availability | VoID file availability check for JudaicaLink took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.28197479248046875s
Reputation | Calculation of the PageRank for JudaicaLink took 0.020218610763549805s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00010442733764648438s
Believability | Calculation of trust value for JudaicaLink took 7.3909759521484375e-06s
INFO | --- Analysis for judaicalink took 22.555779695510864s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 4.100799560546875e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.2797226905822754s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.020424604415893555s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 2.8133392333984375e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 6.67572021484375e-06s
INFO | --- Analysis for kaist-silver-standard-corpus took 3.3421716690063477s
Availability | SPARQL endpoint availability check for KAKEN took 4.220008850097656e-05s
Availability | VoID file availability check for KAKEN took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for KAKEN took 0.2875943183898926s
Reputation | Calculation of the PageRank for KAKEN took 0.02015852928161621s
Interlinking | Calculation of Degree of Connection for KAKEN took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for KAKEN took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for KAKEN took 2.8371810913085938e-05s
Believability | Calculation of trust value for KAKEN took 8.344650268554688e-06s
INFO | --- Analysis for kaken took 3.332420825958252s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.06823110580444336s
Availability | VoID file availability check for Kallikratis municipalities took 0.0003643035888671875s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.26352953910827637s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.020420312881469727s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.34600830078125e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 5.0067901611328125e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.3868725299835205s
Availability | SPARQL endpoint availability check for Openflights Routes took 5.555152893066406e-05s
Availability | VoID file availability check for Openflights Routes took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Openflights Routes took 0.27101564407348633s
Reputation | Calculation of the PageRank for Openflights Routes took 0.020322084426879883s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 2.8371810913085938e-05s
Believability | Calculation of trust value for Openflights Routes took 7.62939453125e-06s
INFO | --- Analysis for kasabi-openflights-routes took 3.3547091484069824s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 5.078315734863281e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0007457733154296875s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.27588677406311035s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.020450830459594727s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 7.200241088867188e-05s
Believability | Calculation of trust value for Klappstuhlclub took 5.245208740234375e-06s
INFO | --- Analysis for klappstuhlclub took 12.493854761123657s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.829614400863647s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.2634134292602539s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.02065563201904297s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 5.9604644775390625e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 6.67572021484375e-06s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.27885365486145s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.0531158447265625e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.2616596221923828s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020380496978759766s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.9325485229492188e-05s
Believability | Calculation of trust value for Knowledge Forest took 7.152557373046875e-06s
INFO | --- Analysis for knowledge-map took 2.884230375289917s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 6.127357482910156e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.28112149238586426s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.02030038833618164s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.67572021484375e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 7.867813110351562e-06s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.26196575164795s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 4.172325134277344e-05s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.2648046016693115s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.020433902740478516s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 7.867813110351562e-06s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 2.8985061645507812s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 4.100799560546875e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.26726555824279785s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.020295381546020508s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 2.7894973754882812e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 7.3909759521484375e-06s
INFO | --- Analysis for ktr took 2.972074270248413s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.06058478355407715s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.0007476806640625s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.2535552978515625s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.020400524139404297s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.7670135498046875e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 8.58306884765625e-06s
INFO | --- Analysis for kupkb took 10.932919025421143s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 4.124641418457031e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.2636435031890869s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.020351648330688477s
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.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 3.0279159545898438e-05s
Believability | Calculation of trust value for Léčivé přípravky ze SÚKL took 8.58306884765625e-06s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 2.8413071632385254s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 8.502727746963501s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.2760579586029053s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.02029275894165039s
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.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 7.510185241699219e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 7.152557373046875e-06s
INFO | --- Analysis for l3s-dblp took 47.136064767837524s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 24.643192052841187s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.2695348262786865s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.02069878578186035s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 7.700920104980469e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 7.152557373046875e-06s
INFO | --- Analysis for lak-dataset took 78.45790815353394s
Availability | SPARQL endpoint availability check for LATC Linksets took 5.173683166503906e-05s
Availability | VoID file availability check for LATC Linksets took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for LATC Linksets took 0.24965310096740723s
Reputation | Calculation of the PageRank for LATC Linksets took 0.02039480209350586s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 2.9325485229492188e-05s
Believability | Calculation of trust value for LATC Linksets took 7.62939453125e-06s
INFO | --- Analysis for latc-linksets took 3.1422648429870605s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 4.172325134277344e-05s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 0.27788734436035156s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.020404338836669922s
Interlinking | Calculation of Degree of Connection for Leipzig Corpora Collection (LCC) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Leipzig Corpora Collection (LCC) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 7.3909759521484375e-06s
INFO | --- Analysis for lcc took 2.9395010471343994s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 4.315376281738281e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0007567405700683594s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.2702479362487793s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.030188798904418945s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0014042854309082031s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.0001766681671142578s
Believability | Calculation of trust value for Library of Congress Subject Headings took 7.3909759521484375e-06s
INFO | --- Analysis for lcsh took 6.167937278747559s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 4.649162292480469e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.26081252098083496s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.020761728286743164s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.344650268554688e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 5.7220458984375e-06s
INFO | --- Analysis for lcsubjects took 2.507746696472168s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 4.863739013671875e-05s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 0.25330162048339844s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.020411968231201172s
Interlinking | Calculation of Degree of Connection for LDQM - Accessibility of DBpedia resources took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LDQM - Accessibility of DBpedia resources took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 3.218650817871094e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 7.152557373046875e-06s
INFO | --- Analysis for ldqm-dbpedia-2016 took 2.9228153228759766s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 4.124641418457031e-05s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 0.27228498458862305s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.020446300506591797s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Eng took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Learned Genre Ontology Eng took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Eng took 2.9325485229492188e-05s
Believability | Calculation of trust value for Learned Genre Ontology Eng took 2.288818359375e-05s
INFO | --- Analysis for learned-genre-ontology-eng took 2.8873934745788574s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 4.172325134277344e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.2608213424682617s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Intl took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Learned Genre Ontology Intl took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 2.7894973754882812e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 7.867813110351562e-06s
INFO | --- Analysis for learned-genre-ontology-intl took 2.926530599594116s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 4.7206878662109375e-05s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.24046564102172852s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.02036309242248535s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 2.7418136596679688e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 9.298324584960938e-06s
INFO | --- Analysis for legislation-openuplabs took 2.8956680297851562s
Availability | SPARQL endpoint availability check for lemonUby took 4.220008850097656e-05s
Availability | VoID file availability check for lemonUby took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for lemonUby took 0.2536747455596924s
Reputation | Calculation of the PageRank for lemonUby took 0.02029561996459961s
Interlinking | Calculation of Degree of Connection for lemonUby took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for lemonUby took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.29425048828125e-05s
Believability | Calculation of trust value for lemonUby took 7.3909759521484375e-06s
INFO | --- Analysis for lemonuby took 3.222350597381592s
Availability | SPARQL endpoint availability check for LemonWiktionary took 4.315376281738281e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.2685227394104004s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.020432233810424805s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.266334533691406e-05s
Believability | Calculation of trust value for LemonWiktionary took 7.62939453125e-06s
INFO | --- Analysis for lemonwiktionary took 4.5362303256988525s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 2.4529736042022705s
Availability | VoID file availability check for LEXIN-RDF took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.2623586654663086s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.019976139068603516s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 2.8848648071289062e-05s
Believability | Calculation of trust value for LEXIN-RDF took 7.152557373046875e-06s
INFO | --- Analysis for lexin-rdf took 6.988553524017334s
Availability | SPARQL endpoint availability check for lexinfo took 4.267692565917969e-05s
Availability | VoID file availability check for lexinfo took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for lexinfo took 0.26424217224121094s
Reputation | Calculation of the PageRank for lexinfo took 0.020210742950439453s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for lexinfo took 9.751319885253906e-05s
Believability | Calculation of trust value for lexinfo took 7.152557373046875e-06s
INFO | --- Analysis for lexinfo took 2.7804152965545654s
Availability | SPARQL endpoint availability check for Lexvo took 4.3392181396484375e-05s
Availability | VoID file availability check for Lexvo took 0.0007565021514892578s
Completeness | Calculation of interlinking completeness for Lexvo took 0.23645997047424316s
Reputation | Calculation of the PageRank for Lexvo took 0.020770788192749023s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00019550323486328125s
Believability | Calculation of trust value for Lexvo took 7.62939453125e-06s
INFO | --- Analysis for lexvo took 42.75758099555969s
Availability | SPARQL endpoint availability check for LIBRIS took 0.3441886901855469s
Availability | VoID file availability check for LIBRIS took 0.0007359981536865234s
Extra | Recovery of all triples for LIBRIS took 6.265982389450073s
Performance | Total latancy measurement for LIBRIS took 0.7596871852874756s
Amount of data | Number of triples check for LIBRIS took 24.876096487045288s
Interoperability | New terms check for LIBRIS took 14.138745546340942s
Versatility | Languages check for LIBRIS took 0.18615150451660156s
Interpretability | Number of blank nodes check for LIBRIS took 300.02755856513977s
Security | Check HTTPS for LIBRIS took 0.35805702209472656s
Interpretability | RDF structures check for LIBRIS took 0.3017425537109375s
Versatility | Serialization formats check for LIBRIS took 0.26384568214416504s
Availability | RDF dump link check for LIBRIS took 0.15588808059692383s
License | MR license check for LIBRIS took 0.2753610610961914s
License | HR license check for LIBRIS took 0.23485183715820312s
Amount of data | Number of property check for LIBRIS took 0.19690346717834473s
Understandability | Number of label check for LIBRIS took 0.5400581359863281s
Understandability | URI regex check for LIBRIS took 0.35245847702026367s
Understandability | Vocabs check for LIBRIS took 0.1560993194580078s
Verifiability | Authors check for LIBRIS took 0.21032238006591797s
Verifiability | Publishers check for LIBRIS took 0.20397663116455078s
Performance | Throughput check for LIBRIS took 11.12477159500122s
Amount of data | Check the number of entities for LIBRIS took 7.152557373046875e-05s
Verifiability | Contribs. check for LIBRIS took 0.19340085983276367s
Interlinking | sameAs chians check for LIBRIS took 0.22494006156921387s
Interlinking | skos check for LIBRIS took 0.2128448486328125s
Interlinking | skos check for LIBRIS took 0.13942193984985352s
Timeliness | dataset update frequency check for LIBRIS took 0.16701602935791016s
Currency | Creation date check for LIBRIS took 0.38587498664855957s
Currency | Modification date check for LIBRIS took 0.6031310558319092s
Rep.Conc. | URIs length for LIBRIS took 80.83769202232361s
Interoperability | New vocabularies check for LIBRIS took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.6862897872924805s
Accuracy | Check Functional Property for LIBRIS took 0.53896164894104s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.15108299255371094s
Accuracy | Check Datatype consistency for LIBRIS took 0.2647676467895508s
Consistency | Disjoint class check for LIBRIS took 0.20447182655334473s
Consistency | Check Misplaced properties for LIBRIS took 60.06686067581177s
Consistency | Misplaced classes for LIBRIS took 1.1330525875091553s
Consistency | Check Ontology hijacking for LIBRIS took 3.697984457015991s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.3236515522003174s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 61.164079666137695s
Conciseness | Check Extensional conciseness for LIBRIS took 0.27441906929016113s
Conciseness | Check Intensional conciseness for LIBRIS took 0.4145967960357666s
Security | Sign check for LIBRIS took 0.4205458164215088s
Availability | Check URIs Dereferenciability for LIBRIS took 10.87020206451416s
Completeness | Calculation of interlinking completeness for LIBRIS took 1.2403452396392822s
Reputation | Calculation of the PageRank for LIBRIS took 0.020307540893554688s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 9.751319885253906e-05s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.1920928955078125e-06s
Believability | Calculation of trust value for LIBRIS took 7.3909759521484375e-06s
INFO | --- Analysis for libris took 1072.8975751399994s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.06944394111633301s
Availability | VoID file availability check for Public Library of Veroia took 0.0006492137908935547s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.702573299407959s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.020873546600341797s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 8.296966552734375e-05s
Believability | Calculation of trust value for Public Library of Veroia took 9.298324584960938e-06s
INFO | --- Analysis for libver took 4.538779020309448s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.13083434104919434s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.00022554397583007812s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.7253885269165039s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.02053046226501465s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 8.344650268554688e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 6.4373016357421875e-06s
INFO | --- Analysis for lichfield-spending took 3.4145822525024414s
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.0008254051208496094s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.24638795852661133s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.020694971084594727s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.457069396972656e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 8.344650268554688e-06s
INFO | --- Analysis for lime took 6.480539798736572s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 4.315376281738281e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.27167510986328125s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.02048468589782715s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0001049041748046875s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 7.3909759521484375e-06s
INFO | --- Analysis for lingvoj took 5.72754693031311s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 4.839897155761719e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.26927709579467773s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.020926713943481445s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 8.58306884765625e-05s
Believability | Calculation of trust value for Linked Crunchbase took 5.7220458984375e-06s
INFO | --- Analysis for linked-crunchbase took 2.733524799346924s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 5.749229192733765s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0008080005645751953s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.2748112678527832s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.020497798919677734s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.343292236328125e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 8.821487426757812e-06s
INFO | --- Analysis for linked-drugs took 19.108932733535767s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.4345855712890625e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.2909119129180908s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.020371675491333008s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.465217590332031e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 5.9604644775390625e-06s
INFO | --- Analysis for linked-edgar took 3.900547981262207s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 4.553794860839844e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.27692341804504395s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.02059316635131836s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 0.00012159347534179688s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 6.67572021484375e-06s
INFO | --- Analysis for linked-eurostat took 4.212926149368286s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.363059997558594e-05s
Availability | VoID file availability check for linked hypernyms took 0.0011181831359863281s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.27988243103027344s
Reputation | Calculation of the PageRank for linked hypernyms took 0.02037358283996582s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.176399230957031e-05s
Believability | Calculation of trust value for linked hypernyms took 7.867813110351562e-06s
INFO | --- Analysis for linked-hypernyms took 3.314013719558716s
Availability | SPARQL endpoint availability check for Linked Life Data took 208.59128761291504s
Availability | VoID file availability check for Linked Life Data took 0.0007841587066650391s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.3550732135772705s
Reputation | Calculation of the PageRank for Linked Life Data took 0.020768404006958008s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 5.459785461425781e-05s
Believability | Calculation of trust value for Linked Life Data took 6.9141387939453125e-06s
INFO | --- Analysis for linked-life-data took 691.8596789836884s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.4861276149749756s
Availability | VoID file availability check for Linked Logainm took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.24475407600402832s
Reputation | Calculation of the PageRank for Linked Logainm took 0.020777225494384766s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 8.130073547363281e-05s
Believability | Calculation of trust value for Linked Logainm took 8.344650268554688e-06s
INFO | --- Analysis for linked-logainm took 5.1519691944122314s
Availability | SPARQL endpoint availability check for Linked NUTS took 4.506111145019531e-05s
Availability | VoID file availability check for Linked NUTS took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.2630927562713623s
Reputation | Calculation of the PageRank for Linked NUTS took 0.020655155181884766s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.364418029785156e-05s
Believability | Calculation of trust value for Linked NUTS took 5.0067901611328125e-06s
INFO | --- Analysis for linked-nuts took 2.938527822494507s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 4.220008850097656e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.2747688293457031s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.020649194717407227s
Interlinking | Calculation of Degree of Connection for Linked Open Aalto Data Service took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Aalto Data Service took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Linked Open Aalto Data Service took 2.9325485229492188e-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 3.7941677570343018s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 1.5721628665924072s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.2575373649597168s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020543813705444336s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.62396240234375e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 6.67572021484375e-06s
INFO | --- Analysis for linked-open-camera took 4.012096405029297s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 3.588324785232544s
Availability | VoID file availability check for Linked Open Commerce took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.25516438484191895s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.02033066749572754s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 3.0994415283203125e-05s
Believability | Calculation of trust value for Linked Open Commerce took 7.867813110351562e-06s
INFO | --- Analysis for linked-open-commerce took 13.91570258140564s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 1.7422552108764648s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.26802802085876465s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.020316123962402344s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00010061264038085938s
Believability | Calculation of trust value for Linked Open Data of Ecology took 8.58306884765625e-06s
INFO | --- Analysis for linked-open-data-of-ecology took 4.279490232467651s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 5.054473876953125e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.24790000915527344s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.020541667938232422s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 8.797645568847656e-05s
Believability | Calculation of trust value for Linked Open Numbers took 5.245208740234375e-06s
INFO | --- Analysis for linked-open-numbers took 2.614833354949951s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 5.745887756347656e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.00030732154846191406s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.2708454132080078s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.02048969268798828s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 3.0279159545898438e-05s
Believability | Calculation of trust value for Linked Open Piracy took 4.76837158203125e-06s
INFO | --- Analysis for linked-open-piracy took 7.0048253536224365s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 4.00543212890625e-05s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 0.2833828926086426s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.02043914794921875s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 3.075599670410156e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 8.344650268554688e-06s
INFO | --- Analysis for linked-open-senate took 2.9163055419921875s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 1.1764342784881592s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.2668604850769043s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.02067852020263672s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007958412170410156s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 4.9591064453125e-05s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 1.2636184692382812e-05s
INFO | --- Analysis for linked-open-vocabularies-lov took 6.581065893173218s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.3392181396484375e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0003020763397216797s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.2420651912689209s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.020855188369750977s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 4.2438507080078125e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 5.0067901611328125e-06s
INFO | --- Analysis for linked-periodicals took 2.4744982719421387s
Availability | SPARQL endpoint availability check for Linked Index took 4.291534423828125e-05s
Availability | VoID file availability check for Linked Index took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for Linked Index took 0.25919604301452637s
Reputation | Calculation of the PageRank for Linked Index took 0.020659685134887695s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.654594421386719e-05s
Believability | Calculation of trust value for Linked Index took 1.6927719116210938e-05s
INFO | --- Analysis for linked-stockindex took 2.3452982902526855s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 5.0073089599609375s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.2518429756164551s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.02051234245300293s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 3.695487976074219e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 1.5974044799804688e-05s
INFO | --- Analysis for linked-structured-product-labels took 12.461971998214722s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.950554609298706s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.28033971786499023s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.02061319351196289s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.3855438232421875e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 6.9141387939453125e-06s
INFO | --- Analysis for linked-taiwan-geo-names took 3.416389226913452s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.39292621612549s
Availability | VoID file availability check for Linked TCGA took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.257828950881958s
Reputation | Calculation of the PageRank for Linked TCGA took 0.020676612854003906s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 8.130073547363281e-05s
Believability | Calculation of trust value for Linked TCGA took 6.4373016357421875e-06s
INFO | --- Analysis for linked-tcga took 62.79159998893738s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.21771979331970215s
Availability | VoID file availability check for Linked User Feedback took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.2537844181060791s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.020429134368896484s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.790855407714844e-05s
Believability | Calculation of trust value for Linked User Feedback took 9.059906005859375e-06s
INFO | --- Analysis for linked-user-feedback took 3.1555519104003906s
Availability | SPARQL endpoint availability check for USPTO Patent data took 5.1975250244140625e-05s
Availability | VoID file availability check for USPTO Patent data took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.264542818069458s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.0204770565032959s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 7.414817810058594e-05s
Believability | Calculation of trust value for USPTO Patent data took 6.4373016357421875e-06s
INFO | --- Analysis for linked-uspto-patent-data took 54.100987911224365s
Availability | SPARQL endpoint availability check for Linked Web APIs dataset took 4.1484832763671875e-05s
Availability | VoID file availability check for Linked Web APIs dataset took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.2487335205078125s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.020534515380859375s
Interlinking | Calculation of Degree of Connection for Linked Web APIs dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Web APIs dataset took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Linked Web APIs dataset took 2.8133392333984375e-05s
Believability | Calculation of trust value for Linked Web APIs dataset took 7.62939453125e-06s
INFO | --- Analysis for linked-web-apis took 2.8100757598876953s
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.00025653839111328125s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.2625114917755127s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.021305322647094727s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0009202957153320312s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 3.409385681152344e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 8.58306884765625e-06s
INFO | --- Analysis for linkedarc took 2.8356590270996094s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.06804466247558594s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.24164342880249023s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.020636320114135742s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.314018249511719e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 6.4373016357421875e-06s
INFO | --- Analysis for linkedcrowdsourceddata took 2.6611647605895996s
Availability | SPARQL endpoint availability check for LinkedCT took 1.641519546508789s
Availability | VoID file availability check for LinkedCT took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.252532958984375s
Reputation | Calculation of the PageRank for LinkedCT took 0.020872116088867188s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 0.00010085105895996094s
Believability | Calculation of trust value for LinkedCT took 8.344650268554688e-06s
INFO | --- Analysis for linkedct took 5.213839292526245s
Availability | SPARQL endpoint availability check for LinkedGeoData took 392.07028555870056s
Availability | VoID file availability check for LinkedGeoData took 0.0006647109985351562s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.903954029083252s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.020876646041870117s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00013256072998046875s
Believability | Calculation of trust value for LinkedGeoData took 1.3113021850585938e-05s
INFO | --- Analysis for linkedgeodata took 929.1369676589966s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 4.124641418457031e-05s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.26082897186279297s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.020407676696777344s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 2.6941299438476562e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 7.867813110351562e-06s
INFO | --- Analysis for linkedgeodata-aerodromes took 4.537066698074341s
Availability | SPARQL endpoint availability check for LinkedLCCN took 1.0182693004608154s
Availability | VoID file availability check for LinkedLCCN took 0.000804901123046875s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.2827718257904053s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.02024245262145996s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00010132789611816406s
Believability | Calculation of trust value for LinkedLCCN took 7.152557373046875e-06s
INFO | --- Analysis for linkedlccn took 13.296830415725708s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 5.030632019042969e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.26514673233032227s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.020448684692382812s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.409385681152344e-05s
Believability | Calculation of trust value for LinkedMarkMail took 6.67572021484375e-06s
INFO | --- Analysis for linkedmarkmail took 2.938634157180786s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.62270379066467s
Availability | VoID file availability check for Linked Movie DataBase took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.2769458293914795s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.020542383193969727s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00014781951904296875s
Believability | Calculation of trust value for Linked Movie DataBase took 8.58306884765625e-06s
INFO | --- Analysis for linkedmdb took 133.83605289459229s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.513697624206543s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 0.2880992889404297s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.021750450134277344s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 7.486343383789062e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 6.4373016357421875e-06s
INFO | --- Analysis for linkedspending took 4.227521896362305s
Availability | SPARQL endpoint availability check for LinkedStats took 4.220008850097656e-05s
Availability | VoID file availability check for LinkedStats took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for LinkedStats took 0.2623870372772217s
Reputation | Calculation of the PageRank for LinkedStats took 0.020631074905395508s
Interlinking | Calculation of Degree of Connection for LinkedStats took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedStats took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 3.170967102050781e-05s
Believability | Calculation of trust value for LinkedStats took 9.5367431640625e-06s
INFO | --- Analysis for linkedstats took 4.307627201080322s
Availability | SPARQL endpoint availability check for LinkedUp Catalogue of Educational Datasets took 4.220008850097656e-05s
Availability | VoID file availability check for LinkedUp Catalogue of Educational Datasets took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 0.24157929420471191s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.02147197723388672s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for LinkedUp Catalogue of Educational Datasets took 3.337860107421875e-05s
Believability | Calculation of trust value for LinkedUp Catalogue of Educational Datasets took 8.106231689453125e-06s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 3.3476855754852295s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 5.7220458984375e-05s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 0.27544236183166504s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.020569324493408203s
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.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Linking Open Drug Data (LODD) took 3.123283386230469e-05s
Believability | Calculation of trust value for Linking Open Drug Data (LODD) took 1.811981201171875e-05s
INFO | --- Analysis for linking-open-drug-data took 2.9196088314056396s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.04990243911743164s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.32102274894714355s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.02032923698425293s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00011038780212402344s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 9.059906005859375e-06s
INFO | --- Analysis for linklion took 2.6181392669677734s
Availability | SPARQL endpoint availability check for Lion's Den took 4.00543212890625e-05s
Availability | VoID file availability check for Lion's Den took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.26656603813171387s
Reputation | Calculation of the PageRank for Lion's Den took 0.020745038986206055s
Interlinking | Calculation of Degree of Connection for Lion's Den took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lion's Den took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 3.123283386230469e-05s
Believability | Calculation of trust value for Lion's Den took 8.106231689453125e-06s
INFO | --- Analysis for lionsden took 3.333582878112793s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 37.489367961883545s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.2692551612854004s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.02028632164001465s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 4.9114227294921875e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 7.152557373046875e-06s
INFO | --- Analysis for lista-encabezamientos-materia took 42.85796284675598s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 4.172325134277344e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 0.2568092346191406s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.0208742618560791s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 3.0517578125e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 6.67572021484375e-06s
INFO | --- Analysis for livtdm took 2.8235483169555664s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 4.00543212890625e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.26074743270874023s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.02073383331298828s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 3.266334533691406e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 6.4373016357421875e-06s
INFO | --- Analysis for livtdm2017 took 2.8256583213806152s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 4.0531158447265625e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.26134824752807617s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.02077651023864746s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 3.1948089599609375e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 7.3909759521484375e-06s
INFO | --- Analysis for lobi took 3.3253562450408936s
Availability | SPARQL endpoint availability check for lobid-organisations took 1.2550218105316162s
Availability | VoID file availability check for lobid-organisations took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.2787179946899414s
Reputation | Calculation of the PageRank for lobid-organisations took 0.02058553695678711s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.5367431640625e-05s
Believability | Calculation of trust value for lobid-organisations took 1.1920928955078125e-05s
INFO | --- Analysis for lobid-organisations took 5.711822986602783s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 1.118302345275879s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0011169910430908203s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.25722479820251465s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.020839214324951172s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 0.00011038780212402344s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 7.867813110351562e-06s
INFO | --- Analysis for lobid-resources took 8.56677794456482s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.5299530029296875e-05s
Availability | VoID file availability check for Linked Open Colors took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.2670292854309082s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.020694494247436523s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 7.963180541992188e-05s
Believability | Calculation of trust value for Linked Open Colors took 7.62939453125e-06s
INFO | --- Analysis for loc took 7.34729528427124s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 5.5789947509765625e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.26439809799194336s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 3.075599670410156e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 7.3909759521484375e-06s
INFO | --- Analysis for locv took 35.812071323394775s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.7607190608978271s
Availability | VoID file availability check for LOD-a-lot took 0.0007596015930175781s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.27178430557250977s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.02059483528137207s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 3.170967102050781e-05s
Believability | Calculation of trust value for LOD-a-lot took 6.67572021484375e-06s
INFO | --- Analysis for lod-a-lot took 14.094927310943604s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 4.172325134277344e-05s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.25092172622680664s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.020541667938232422s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 3.266334533691406e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 6.67572021484375e-06s
INFO | --- Analysis for lod-it_scuole-italiane took 2.908956527709961s
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.0002484321594238281s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.2770192623138428s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.020563125610351562s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Open Data Web - a CKAN based linked open data repository in Taiwan took 3.075599670410156e-05s
Believability | Calculation of trust value for Open Data Web - a CKAN based linked open data repository in Taiwan took 8.344650268554688e-06s
INFO | --- Analysis for lod-taiwan took 2.9644341468811035s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.4345855712890625e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.27834105491638184s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.020663022994995117s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.845329284667969e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 6.9141387939453125e-06s
INFO | --- Analysis for lod2-project-wiki took 3.731529474258423s
Availability | SPARQL endpoint availability check for LODAC BDLS took 2.9301493167877197s
Availability | VoID file availability check for LODAC BDLS took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.2503821849822998s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.020636558532714844s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 7.462501525878906e-05s
Believability | Calculation of trust value for LODAC BDLS took 7.867813110351562e-06s
INFO | --- Analysis for lodac-bdls took 13.855075120925903s
Availability | SPARQL endpoint availability check for LODRussia Math took 4.2438507080078125e-05s
Availability | VoID file availability check for LODRussia Math took 0.0002243518829345703s
Completeness | Calculation of interlinking completeness for LODRussia Math took 0.2595663070678711s
Reputation | Calculation of the PageRank for LODRussia Math took 0.020779848098754883s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LODRussia Math took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 3.0279159545898438e-05s
Believability | Calculation of trust value for LODRussia Math took 7.152557373046875e-06s
INFO | --- Analysis for lodrussia-math took 2.8889708518981934s
Availability | SPARQL endpoint availability check for LODRussia Nano took 4.267692565917969e-05s
Availability | VoID file availability check for LODRussia Nano took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 0.28526782989501953s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.020617008209228516s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 3.075599670410156e-05s
Believability | Calculation of trust value for LODRussia Nano took 7.62939453125e-06s
INFO | --- Analysis for lodrussia-nano took 2.9035215377807617s
Availability | SPARQL endpoint availability check for LODStats took 4.1484832763671875e-05s
Availability | VoID file availability check for LODStats took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for LODStats took 0.2723817825317383s
Reputation | Calculation of the PageRank for LODStats took 0.020771265029907227s
Interlinking | Calculation of Degree of Connection for LODStats took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LODStats took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for LODStats took 3.075599670410156e-05s
Believability | Calculation of trust value for LODStats took 6.9141387939453125e-06s
INFO | --- Analysis for lodstats took 2.925352096557617s
Availability | SPARQL endpoint availability check for LODUM took 4.3392181396484375e-05s
Availability | VoID file availability check for LODUM took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for LODUM took 0.2749752998352051s
Reputation | Calculation of the PageRank for LODUM took 0.02071857452392578s
Interlinking | Calculation of Degree of Connection for LODUM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LODUM took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for LODUM took 3.0040740966796875e-05s
Believability | Calculation of trust value for LODUM took 6.198883056640625e-06s
INFO | --- Analysis for lodum took 3.0136749744415283s
Availability | SPARQL endpoint availability check for lofd took 0.13955473899841309s
Availability | VoID file availability check for lofd took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for lofd took 0.26227402687072754s
Reputation | Calculation of the PageRank for lofd took 0.020765066146850586s
Interlinking | Calculation of Degree of Connection for lofd took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for lofd took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for lofd took 3.1948089599609375e-05s
Believability | Calculation of trust value for lofd took 6.198883056640625e-06s
INFO | --- Analysis for lofd took 2.5152039527893066s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 271.4245479106903s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0007078647613525391s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.6855192184448242s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.02071690559387207s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 5.8650970458984375e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 6.198883056640625e-06s
INFO | --- Analysis for loius took 585.4793374538422s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 4.744529724121094e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.3347647190093994s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.02167510986328125s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 2.9325485229492188e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 8.106231689453125e-06s
INFO | --- Analysis for loius-linking-italian-university-statistics took 5.785938739776611s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 0.6880829334259033s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.7065250873565674s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.02031874656677246s
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.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.078315734863281e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 5.245208740234375e-06s
INFO | --- Analysis for london-gazette took 5.423846244812012s
Availability | SPARQL endpoint availability check for Weather Stations took 4.315376281738281e-05s
Availability | VoID file availability check for Weather Stations took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.2657349109649658s
Reputation | Calculation of the PageRank for Weather Stations took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 8.273124694824219e-05s
Believability | Calculation of trust value for Weather Stations took 7.152557373046875e-06s
INFO | --- Analysis for los_metar took 6.948863506317139s
Availability | SPARQL endpoint availability check for Lotico took 0.9276082515716553s
Availability | VoID file availability check for Lotico took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for Lotico took 0.2667195796966553s
Reputation | Calculation of the PageRank for Lotico took 0.020314455032348633s
Interlinking | Calculation of Degree of Connection for Lotico took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Lotico took 7.915496826171875e-05s
Believability | Calculation of trust value for Lotico took 7.152557373046875e-06s
INFO | --- Analysis for lotico took 7.274189233779907s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.2812483310699463s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0006678104400634766s
Extra | Recovery of all triples for Lower Layer Super Output Areas took 0.5573346614837646s
Performance | Total latancy measurement for Lower Layer Super Output Areas took 0.8569869995117188s
Amount of data | Number of triples check for Lower Layer Super Output Areas took 0.16494417190551758s
Interoperability | New terms check for Lower Layer Super Output Areas took 1.4895846843719482s
Versatility | Languages check for Lower Layer Super Output Areas took 0.23766636848449707s
Interpretability | Number of blank nodes check for Lower Layer Super Output Areas took 0.9570736885070801s
Security | Check HTTPS for Lower Layer Super Output Areas took 0.09285879135131836s
Interpretability | RDF structures check for Lower Layer Super Output Areas took 0.14761853218078613s
Versatility | Serialization formats check for Lower Layer Super Output Areas took 0.16637825965881348s
Availability | RDF dump link check for Lower Layer Super Output Areas took 46.23889112472534s
License | MR license check for Lower Layer Super Output Areas took 0.1921389102935791s
License | HR license check for Lower Layer Super Output Areas took 0.7739923000335693s
Amount of data | Number of property check for Lower Layer Super Output Areas took 0.15152549743652344s
Understandability | Number of label check for Lower Layer Super Output Areas took 0.13573002815246582s
Understandability | URI regex check for Lower Layer Super Output Areas took 0.2831587791442871s
Understandability | Vocabs check for Lower Layer Super Output Areas took 0.12075448036193848s
Verifiability | Authors check for Lower Layer Super Output Areas took 0.15002894401550293s
Verifiability | Publishers check for Lower Layer Super Output Areas took 0.13247990608215332s
Performance | Throughput check for Lower Layer Super Output Areas took 11.37769603729248s
Amount of data | Check the number of entities for Lower Layer Super Output Areas took 7.271766662597656e-05s
Verifiability | Contribs. check for Lower Layer Super Output Areas took 0.19199228286743164s
Interlinking | sameAs chians check for Lower Layer Super Output Areas took 0.14521312713623047s
Interlinking | skos check for Lower Layer Super Output Areas took 0.13706064224243164s
Interlinking | skos check for Lower Layer Super Output Areas took 0.15200495719909668s
Timeliness | dataset update frequency check for Lower Layer Super Output Areas took 0.13547015190124512s
Currency | Creation date check for Lower Layer Super Output Areas took 0.2930612564086914s
Currency | Modification date check for Lower Layer Super Output Areas took 0.18783164024353027s
Rep.Conc. | URIs length for Lower Layer Super Output Areas took 0.4335925579071045s
Interoperability | New vocabularies check for Lower Layer Super Output Areas took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Lower Layer Super Output Areas took 0.21236014366149902s
Accuracy | Check Functional Property for Lower Layer Super Output Areas took 0.14462852478027344s
Accuracy | Check Inverse Functional Property for Lower Layer Super Output Areas took 0.12764763832092285s
Consistency | Disjoint class check for Lower Layer Super Output Areas took 0.1453084945678711s
Consistency | Check Misplaced properties for Lower Layer Super Output Areas took 0.37558674812316895s
Consistency | Check Ontology hijacking for Lower Layer Super Output Areas took 0.3239603042602539s
Consistency | Check Invalid usage of undefined properties for Lower Layer Super Output Areas took 1.5070428848266602s
Conciseness | Check Extensional conciseness for Lower Layer Super Output Areas took 0.00014829635620117188s
Conciseness | Check Intensional conciseness for Lower Layer Super Output Areas took 0.25669407844543457s
Security | Sign check for Lower Layer Super Output Areas took 0.1284792423248291s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.26724672317504883s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.020382165908813477s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 3.361701965332031e-05s
Interoperability | Check the re-using of existing vocabs for Lower Layer Super Output Areas took 9.5367431640625e-07s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 7.152557373046875e-06s
INFO | --- Analysis for lower-layer-super-output-areas took 167.99555897712708s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 4.3392181396484375e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.2600843906402588s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.02029705047607422s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 2.8848648071289062e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 1.2636184692382812e-05s
INFO | --- Analysis for lremap-auth took 3.904268503189087s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 4.363059997558594e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.26531219482421875s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.02065253257751465s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 2.9802322387695312e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 8.344650268554688e-06s
INFO | --- Analysis for lremap-conf took 4.432585954666138s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 5.054473876953125e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.26032280921936035s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.020963430404663086s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 3.0517578125e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 8.344650268554688e-06s
INFO | --- Analysis for lremap-ri took 2.6844687461853027s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 4.291534423828125e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.26249170303344727s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.020522356033325195s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 3.0994415283203125e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 9.298324584960938e-06s
INFO | --- Analysis for lremap-sub took 3.1204097270965576s
Availability | SPARQL endpoint availability check for LSQ took 4.57763671875e-05s
Availability | VoID file availability check for LSQ took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for LSQ took 0.24652814865112305s
Reputation | Calculation of the PageRank for LSQ took 0.02049851417541504s
Interlinking | Calculation of Degree of Connection for LSQ took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LSQ took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for LSQ took 3.3855438232421875e-05s
Believability | Calculation of trust value for LSQ took 7.152557373046875e-06s
INFO | --- Analysis for lsq took 3.497870922088623s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 4.220008850097656e-05s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.23846173286437988s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.0213925838470459s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0007956027984619141s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 3.457069396972656e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 7.867813110351562e-06s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 2.8940277099609375s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 6.508827209472656e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.00031447410583496094s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.2575345039367676s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.02054738998413086s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.3855438232421875e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 7.152557373046875e-06s
INFO | --- Analysis for manchester-university-reading-lists took 3.5972673892974854s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá, Distrito Capital took 4.267692565917969e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.28192782402038574s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.020622968673706055s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.0008046627044677734s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 3.147125244140625e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 8.821487426757812e-06s
INFO | --- Analysis for mapa-referencia-bogota took 2.8896279335021973s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá D.C took 4.172325134277344e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá D.C took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.26849913597106934s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.020149707794189453s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 2.7894973754882812e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 1.049041748046875e-05s
INFO | --- Analysis for mapa-referencia-bogota-dc took 2.9148385524749756s
Availability | SPARQL endpoint availability check for MARC Codes List took 4.410743713378906e-05s
Availability | VoID file availability check for MARC Codes List took 0.00032782554626464844s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.2604944705963135s
Reputation | Calculation of the PageRank for MARC Codes List took 0.02055072784423828s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.0001354217529296875s
Believability | Calculation of trust value for MARC Codes List took 7.62939453125e-06s
INFO | --- Analysis for marc-codes took 14.256747245788574s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.3392181396484375e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.261063814163208s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.02188563346862793s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0009317398071289062s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.315376281738281e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 9.059906005859375e-06s
INFO | --- Analysis for masc took 6.4029693603515625s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 4.2438507080078125e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.2659456729888916s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.02053380012512207s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.528594970703125e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 8.106231689453125e-06s
INFO | --- Analysis for masc-bn-nif took 2.4469306468963623s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.3313188552856445s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.2877652645111084s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.021187543869018555s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 2.9325485229492188e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 7.62939453125e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 3.902829647064209s
Availability | SPARQL endpoint availability check for medline took 4.482269287109375e-05s
Availability | VoID file availability check for medline took 0.0007293224334716797s
Completeness | Calculation of interlinking completeness for medline took 0.28868961334228516s
Reputation | Calculation of the PageRank for medline took 0.020733118057250977s
Interlinking | Calculation of Degree of Connection for medline took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for medline took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for medline took 3.62396240234375e-05s
Believability | Calculation of trust value for medline took 1.1444091796875e-05s
INFO | --- Analysis for medline took 7.360178470611572s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 10.6044602394104s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.2733898162841797s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.020673751831054688s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 7.414817810058594e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 8.106231689453125e-06s
INFO | --- Analysis for meducator took 23.55304765701294s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 5.555152893066406e-05s
Availability | VoID file availability check for Finnish translation of mesh took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.2560458183288574s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.020547151565551758s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 3.075599670410156e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 8.344650268554688e-06s
INFO | --- Analysis for mesh-finnish took 2.8534867763519287s
Availability | SPARQL endpoint availability check for MeSH headings took 4.9114227294921875e-05s
Availability | VoID file availability check for MeSH headings took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for MeSH headings took 0.26741981506347656s
Reputation | Calculation of the PageRank for MeSH headings took 0.020508527755737305s
Interlinking | Calculation of Degree of Connection for MeSH headings took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MeSH headings took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 3.147125244140625e-05s
Believability | Calculation of trust value for MeSH headings took 9.059906005859375e-06s
INFO | --- Analysis for mesh_headings took 2.963346004486084s
Availability | SPARQL endpoint availability check for MeSH, IPSV - SKOS RDF took 4.124641418457031e-05s
Availability | VoID file availability check for MeSH, IPSV - SKOS RDF took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 0.2513587474822998s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.020703554153442383s
Interlinking | Calculation of Degree of Connection for MeSH, IPSV - SKOS RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MeSH, IPSV - SKOS RDF took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 2.9325485229492188e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 7.152557373046875e-06s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 2.896601915359497s
Availability | SPARQL endpoint availability check for MeSH pairs took 4.100799560546875e-05s
Availability | VoID file availability check for MeSH pairs took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for MeSH pairs took 0.24068832397460938s
Reputation | Calculation of the PageRank for MeSH pairs took 0.02047872543334961s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MeSH pairs took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 2.765655517578125e-05s
Believability | Calculation of trust value for MeSH pairs took 8.58306884765625e-06s
INFO | --- Analysis for mesh_pairs took 2.8048369884490967s
Availability | SPARQL endpoint availability check for MeSH titles took 7.867813110351562e-05s
Availability | VoID file availability check for MeSH titles took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.2565455436706543s
Reputation | Calculation of the PageRank for MeSH titles took 0.022307634353637695s
Interlinking | Calculation of Degree of Connection for MeSH titles took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MeSH titles took 0.0010788440704345703s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 3.528594970703125e-05s
Believability | Calculation of trust value for MeSH titles took 7.867813110351562e-06s
INFO | --- Analysis for mesh_titles took 2.8159608840942383s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 4.2438507080078125e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.27625036239624023s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.020266294479370117s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 2.8848648071289062e-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.941514492034912s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 4.38690185546875e-05s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.26957035064697266s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0202634334564209s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 2.7179718017578125e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 7.867813110351562e-06s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 2.932337999343872s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 4.1961669921875e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.24724245071411133s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.020394086837768555s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 7.2479248046875e-05s
Believability | Calculation of trust value for MetaShare metadata model took 8.106231689453125e-06s
INFO | --- Analysis for metashare took 2.390834093093872s
Availability | SPARQL endpoint availability check for MExiCo took 4.2438507080078125e-05s
Availability | VoID file availability check for MExiCo took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for MExiCo took 0.27462053298950195s
Reputation | Calculation of the PageRank for MExiCo took 0.02057623863220215s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0009922981262207031s
Interlinking | Calculation of Clustering coefficient for MExiCo took 6.079673767089844e-05s
Believability | Calculation of trust value for MExiCo took 7.62939453125e-06s
INFO | --- Analysis for mexico took 22.406901597976685s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 4.506111145019531e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.2535829544067383s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00010204315185546875s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 9.5367431640625e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 5.707557201385498s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 4.38690185546875e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.27135586738586426s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.020268678665161133s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00011181831359863281s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 6.67572021484375e-06s
INFO | --- Analysis for mismuseos-gnoss took 8.06540060043335s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.11485600471496582s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.28002047538757324s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.020270109176635742s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.124641418457031e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 7.3909759521484375e-06s
INFO | --- Analysis for mlsa took 3.0771701335906982s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 8.392333984375e-05s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.26877570152282715s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.020339488983154297s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 2.765655517578125e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 7.62939453125e-06s
INFO | --- Analysis for mond took 2.8853752613067627s
Availability | SPARQL endpoint availability check for MONDIS took 4.1484832763671875e-05s
Availability | VoID file availability check for MONDIS took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for MONDIS took 0.28844571113586426s
Reputation | Calculation of the PageRank for MONDIS took 0.02019667625427246s
Interlinking | Calculation of Degree of Connection for MONDIS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MONDIS took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for MONDIS took 2.8371810913085938e-05s
Believability | Calculation of trust value for MONDIS took 8.344650268554688e-06s
INFO | --- Analysis for mondis took 2.912768840789795s
Availability | SPARQL endpoint availability check for Monumentos took 4.124641418457031e-05s
Availability | VoID file availability check for Monumentos took 0.0002994537353515625s
Completeness | Calculation of interlinking completeness for Monumentos took 0.2522456645965576s
Reputation | Calculation of the PageRank for Monumentos took 0.02057933807373047s
Interlinking | Calculation of Degree of Connection for Monumentos took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Monumentos took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Monumentos took 3.314018249511719e-05s
Believability | Calculation of trust value for Monumentos took 8.344650268554688e-06s
INFO | --- Analysis for monumentos-zaragoza took 2.8040590286254883s
Availability | SPARQL endpoint availability check for MORElab took 0.8863105773925781s
Availability | VoID file availability check for MORElab took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for MORElab took 0.24170899391174316s
Reputation | Calculation of the PageRank for MORElab took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for MORElab took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for MORElab took 8.559226989746094e-05s
Believability | Calculation of trust value for MORElab took 7.3909759521484375e-06s
INFO | --- Analysis for morelab took 4.702646493911743s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 1.8856139183044434s
Availability | VoID file availability check for Mathematics Subject Classification took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.2646925449371338s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.020482301712036133s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.821487426757812e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 8.344650268554688e-06s
INFO | --- Analysis for msc took 6.213772535324097s
Availability | SPARQL endpoint availability check for Multext-East took 4.458427429199219e-05s
Availability | VoID file availability check for Multext-East took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for Multext-East took 0.24968862533569336s
Reputation | Calculation of the PageRank for Multext-East took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.314018249511719e-05s
Believability | Calculation of trust value for Multext-East took 7.3909759521484375e-06s
INFO | --- Analysis for multext-east took 2.3555121421813965s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 4.029273986816406e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.26954197883605957s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.020438432693481445s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 4.863739013671875e-05s
Believability | Calculation of trust value for The DGT Multilingual Translation Memory of the Acquis Communautaire took 8.106231689453125e-06s
INFO | --- Analysis for multilingualeulaw took 2.963346004486084s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.291534423828125e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.2738626003265381s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.020537137985229492s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.314018249511719e-05s
Believability | Calculation of trust value for Multimedia Lab took 6.9141387939453125e-06s
INFO | --- Analysis for multimedia-lab took 2.4551594257354736s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 4.00543212890625e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.0014295578002929688s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.2576713562011719s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.020961523056030273s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 3.1948089599609375e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 6.67572021484375e-06s
INFO | --- Analysis for munich-offener-haushalt took 2.8708837032318115s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.829392671585083s
Availability | VoID file availability check for Muninn World War I took 0.0008521080017089844s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.24812746047973633s
Reputation | Calculation of the PageRank for Muninn World War I took 0.020206928253173828s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.606910705566406e-05s
Believability | Calculation of trust value for Muninn World War I took 8.344650268554688e-06s
INFO | --- Analysis for muninn-world-war-i took 10.67969536781311s
Availability | SPARQL endpoint availability check for Musei Italiani took 4.1484832763671875e-05s
Availability | VoID file availability check for Musei Italiani took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.26380038261413574s
Reputation | Calculation of the PageRank for Musei Italiani took 0.020703554153442383s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Musei Italiani took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 3.409385681152344e-05s
Believability | Calculation of trust value for Musei Italiani took 1.3589859008789062e-05s
INFO | --- Analysis for musei-italiani took 2.904114246368408s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 4.4345855712890625e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.25795483589172363s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.02081465721130371s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007266998291015625s
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 6.67572021484375e-06s
INFO | --- Analysis for museosespania-gnoss took 173.90579462051392s
Availability | SPARQL endpoint availability check for Italian Museums took 1.922020435333252s
Availability | VoID file availability check for Italian Museums took 0.0003638267517089844s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.2746083736419678s
Reputation | Calculation of the PageRank for Italian Museums took 0.020275115966796875s
Interlinking | Calculation of Degree of Connection for Italian Museums took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 8.058547973632812e-05s
Believability | Calculation of trust value for Italian Museums took 7.62939453125e-06s
INFO | --- Analysis for museums-in-italy took 4.861347675323486s
Availability | SPARQL endpoint availability check for MusicBrainz took 4.1961669921875e-05s
Availability | VoID file availability check for MusicBrainz took 0.00039696693420410156s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.26307153701782227s
Reputation | Calculation of the PageRank for MusicBrainz took 0.020667314529418945s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MusicBrainz took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 3.528594970703125e-05s
Believability | Calculation of trust value for MusicBrainz took 8.344650268554688e-06s
INFO | --- Analysis for musicbrainz_ took 2.9393038749694824s
Availability | SPARQL endpoint availability check for MusicNet Codex took 4.2438507080078125e-05s
Availability | VoID file availability check for MusicNet Codex took 0.0002999305725097656s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.2931210994720459s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.020650863647460938s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 2.9087066650390625e-05s
Believability | Calculation of trust value for MusicNet Codex took 8.58306884765625e-06s
INFO | --- Analysis for musicnet_codex took 2.92185115814209s
Availability | SPARQL endpoint availability check for myExperiment took 0.27051401138305664s
Availability | VoID file availability check for myExperiment took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for myExperiment took 0.2710113525390625s
Reputation | Calculation of the PageRank for myExperiment took 0.020689725875854492s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.00010442733764648438s
Believability | Calculation of trust value for myExperiment took 7.3909759521484375e-06s
INFO | --- Analysis for my-experiment took 3.427652359008789s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.07149529457092285s
Availability | VoID file availability check for My Family Lineage took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.26229000091552734s
Reputation | Calculation of the PageRank for My Family Lineage took 0.020392894744873047s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.440017700195312e-05s
Believability | Calculation of trust value for My Family Lineage took 9.059906005859375e-06s
INFO | --- Analysis for my-family-lineage took 4.02288293838501s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 0.17031025886535645s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.2915945053100586s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.020616769790649414s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 6.914138793945312e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for n-lex-as-linked-data took 2.7320218086242676s
Availability | SPARQL endpoint availability check for NAICS 2007 took 27.70316481590271s
Availability | VoID file availability check for NAICS 2007 took 0.0008416175842285156s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.24909734725952148s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 3.814697265625e-05s
Believability | Calculation of trust value for NAICS 2007 took 5.4836273193359375e-06s
INFO | --- Analysis for naics-2007 took 126.89906692504883s
Availability | SPARQL endpoint availability check for NAICS 2012 took 24.297001600265503s
Availability | VoID file availability check for NAICS 2012 took 0.0009031295776367188s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.273484468460083s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.02132129669189453s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007891654968261719s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 4.887580871582031e-05s
Believability | Calculation of trust value for NAICS 2012 took 5.4836273193359375e-06s
INFO | --- Analysis for naics-2012 took 123.9691846370697s
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.00027179718017578125s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 0.7429370880126953s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.02060413360595703s
Interlinking | Calculation of Degree of Connection for National Agricultural Library Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for National Agricultural Library Thesaurus took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 5.173683166503906e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 8.58306884765625e-06s
INFO | --- Analysis for nalt took 3.4822676181793213s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 1.3092989921569824s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0006909370422363281s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 1.0257799625396729s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 1.9958899021148682s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 12.902997970581055s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 29.86398720741272s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.40410804748535156s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.800113916397095s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.3853745460510254s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.3753829002380371s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.35482263565063477s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.39790916442871094s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.4387857913970947s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.80656361579895s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.9162604808807373s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 5.785804033279419s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 0.7594273090362549s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.3685581684112549s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.36316919326782227s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.3628237247467041s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 11.369357347488403s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 8.606910705566406e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.3399622440338135s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.5176308155059814s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.6199634075164795s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.5313689708709717s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.39835047721862793s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.0551033020019531s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 0.7714018821716309s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 1.0032563209533691s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.36594343185424805s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.42163634300231934s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.36284422874450684s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.4042079448699951s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0008759498596191406s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0010752677917480469s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.39208173751831055s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.749427080154419s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.3630242347717285s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.6863625049591064s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.3003137111663818s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.6883447170257568s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0006268024444580078s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.3575930595397949s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 3.6954331398010254s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.878563404083252s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.02035045623779297s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 6.604194641113281e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.6689300537109375e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 5.4836273193359375e-06s
INFO | --- Analysis for national-diet-library-authorities took 242.59770917892456s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.37282609939575195s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.00064849853515625s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 1.4789197444915771s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 1.981412410736084s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.82752537727356s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.9167196750640869s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 16.169706106185913s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.3650486469268799s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.40953516960144043s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.38713574409484863s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.35828185081481934s
License | MR license check for National Diet Library of Japan subject headings took 0.37119221687316895s
License | HR license check for National Diet Library of Japan subject headings took 91.83265352249146s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.8663122653961182s
Understandability | Number of label check for National Diet Library of Japan subject headings took 5.4599549770355225s
Understandability | URI regex check for National Diet Library of Japan subject headings took 0.7797837257385254s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.39806604385375977s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.4011194705963135s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.3971078395843506s
Performance | Throughput check for National Diet Library of Japan subject headings took 11.637551307678223s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 8.678436279296875e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.3717334270477295s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.5502653121948242s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.508941650390625s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.5208492279052734s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.4608786106109619s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.1906373500823975s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.7180707454681396s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 0.9972457885742188s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.3204345703125s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.4153311252593994s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.3445594310760498s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.4026169776916504s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.00032711029052734375s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0005145072937011719s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.35483288764953613s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.6956226825714111s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.42125582695007324s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.7079105377197266s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.3036346435546875s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.696789264678955s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0006177425384521484s
Security | Sign check for National Diet Library of Japan subject headings took 0.3966860771179199s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 3.659207820892334s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.8132748603820801s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.02092742919921875s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 5.14984130859375e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.430511474609375e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 7.3909759521484375e-06s
INFO | --- Analysis for national-diet-library-subject-headings took 304.7369577884674s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 0.7737987041473389s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0006439685821533203s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.7322549819946289s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.02034592628479004s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.38690185546875e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 8.106231689453125e-06s
INFO | --- Analysis for national-library-of-greece-authority-records took 5.703494071960449s
Availability | SPARQL endpoint availability check for Naturopathy took 4.1961669921875e-05s
Availability | VoID file availability check for Naturopathy took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Naturopathy took 0.27755236625671387s
Reputation | Calculation of the PageRank for Naturopathy took 0.020352840423583984s
Interlinking | Calculation of Degree of Connection for Naturopathy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Naturopathy took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 2.8133392333984375e-05s
Believability | Calculation of trust value for Naturopathy took 8.821487426757812e-06s
INFO | --- Analysis for naturopathy2 took 2.8694393634796143s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 6.079673767089844e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0002961158752441406s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.27649950981140137s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 3.0517578125e-05s
Believability | Calculation of trust value for NCI Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for nci-thesaurus took 2.9737133979797363s
Availability | SPARQL endpoint availability check for NDF-RT took 4.172325134277344e-05s
Availability | VoID file availability check for NDF-RT took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.2535722255706787s
Reputation | Calculation of the PageRank for NDF-RT took 0.02066826820373535s
Interlinking | Calculation of Degree of Connection for NDF-RT took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NDF-RT took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 3.504753112792969e-05s
Believability | Calculation of trust value for NDF-RT took 1.2874603271484375e-05s
INFO | --- Analysis for ndf-rt took 2.9191932678222656s
Availability | SPARQL endpoint availability check for Near took 4.267692565917969e-05s
Availability | VoID file availability check for Near took 0.0007646083831787109s
Completeness | Calculation of interlinking completeness for Near took 0.2938969135284424s
Reputation | Calculation of the PageRank for Near took 0.020699739456176758s
Interlinking | Calculation of Degree of Connection for Near took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Near took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Near took 0.00010156631469726562s
Believability | Calculation of trust value for Near took 8.821487426757812e-06s
INFO | --- Analysis for near took 9.054770231246948s
Availability | SPARQL endpoint availability check for Neel took 4.124641418457031e-05s
Availability | VoID file availability check for Neel took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for Neel took 0.283491849899292s
Reputation | Calculation of the PageRank for Neel took 0.021056175231933594s
Interlinking | Calculation of Degree of Connection for Neel took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Neel took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Neel took 3.0994415283203125e-05s
Believability | Calculation of trust value for Neel took 7.3909759521484375e-06s
INFO | --- Analysis for neel took 2.9380264282226562s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 6.580352783203125e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.2585458755493164s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.02076244354248047s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 3.0279159545898438e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 8.106231689453125e-06s
INFO | --- Analysis for neurocommons_text_mining_pilot took 2.88586688041687s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 4.38690185546875e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.2564849853515625s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.020315885543823242s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 2.8848648071289062e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 7.62939453125e-06s
INFO | --- Analysis for neurolex-wiki took 2.349144220352173s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 4.172325134277344e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.24582600593566895s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.021735668182373047s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0008025169372558594s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 0.00010561943054199219s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 8.106231689453125e-06s
INFO | --- Analysis for news-100-nif-ner-corpus took 4.378014087677002s
Availability | SPARQL endpoint availability check for Newsweek took 5.269050598144531e-05s
Availability | VoID file availability check for Newsweek took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Newsweek took 0.272444486618042s
Reputation | Calculation of the PageRank for Newsweek took 0.020389795303344727s
Interlinking | Calculation of Degree of Connection for Newsweek took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Newsweek took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Newsweek took 2.765655517578125e-05s
Believability | Calculation of trust value for Newsweek took 7.62939453125e-06s
INFO | --- Analysis for newsweek took 2.9678456783294678s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 6.580352783203125e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.29712843894958496s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.020630598068237305s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00011205673217773438s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 7.867813110351562e-06s
INFO | --- Analysis for nextweb-gnoss took 10.953677654266357s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 4.1484832763671875e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0007100105285644531s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.27755022048950195s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.020390033721923828s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 8.249282836914062e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 5.4836273193359375e-06s
INFO | --- Analysis for nhs-jargon took 2.771733522415161s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 4.363059997558594e-05s
Availability | VoID file availability check for NLM 2007 MeSH took 0.0002999305725097656s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.27637577056884766s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 3.409385681152344e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 1.4781951904296875e-05s
INFO | --- Analysis for nlm_2007_mesh took 2.940303087234497s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.26794981956481934s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.020321369171142578s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.0517578125e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 8.58306884765625e-06s
INFO | --- Analysis for nlr-dataset-mod took 4.036298990249634s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.9325485229492188s
Availability | VoID file availability check for Nobel Prizes took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.2761499881744385s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.020517349243164062s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.226799011230469e-05s
Believability | Calculation of trust value for Nobel Prizes took 9.298324584960938e-06s
INFO | --- Analysis for nobelprizes took 8.912461757659912s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 24.987396955490112s
Availability | VoID file availability check for Nomenclator Asturias took 0.0008273124694824219s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.2930288314819336s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.020786285400390625s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 8.988380432128906e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 5.9604644775390625e-06s
INFO | --- Analysis for nomenclator-asturias took 136.69563698768616s
Availability | SPARQL endpoint availability check for nomisma took 4.6253204345703125e-05s
Availability | VoID file availability check for nomisma took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for nomisma took 0.25397634506225586s
Reputation | Calculation of the PageRank for nomisma took 0.020946264266967773s
Interlinking | Calculation of Degree of Connection for nomisma took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for nomisma took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for nomisma took 3.075599670410156e-05s
Believability | Calculation of trust value for nomisma took 8.58306884765625e-06s
INFO | --- Analysis for nomisma took 3.345987558364868s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.3991725444793701s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.2595348358154297s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.020847320556640625s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 5.435943603515625e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 1.4066696166992188e-05s
INFO | --- Analysis for norwegian-geo-divisions took 7.276587247848511s
Availability | SPARQL endpoint availability check for NorwegianSoE took 4.172325134277344e-05s
Availability | VoID file availability check for NorwegianSoE took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 0.2543504238128662s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.020235538482666016s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 2.9087066650390625e-05s
Believability | Calculation of trust value for NorwegianSoE took 8.344650268554688e-06s
INFO | --- Analysis for norwegiansoe took 2.916729211807251s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.38690185546875e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.25498008728027344s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.02109360694885254s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0010831356048583984s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 4.124641418457031e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 7.152557373046875e-06s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 2.7522006034851074s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 4.2438507080078125e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.251187801361084s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.02065873146057129s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 3.0517578125e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 8.344650268554688e-06s
INFO | --- Analysis for npg took 2.8757388591766357s
Availability | SPARQL endpoint availability check for NPM took 4.410743713378906e-05s
Availability | VoID file availability check for NPM took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for NPM took 0.25493288040161133s
Reputation | Calculation of the PageRank for NPM took 0.020228862762451172s
Interlinking | Calculation of Degree of Connection for NPM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NPM took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for NPM took 3.2901763916015625e-05s
Believability | Calculation of trust value for NPM took 7.62939453125e-06s
INFO | --- Analysis for npm took 3.2937328815460205s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.026720523834228516s
Availability | VoID file availability check for NTNU special collections took 0.0006902217864990234s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.28581833839416504s
Reputation | Calculation of the PageRank for NTNU special collections took 0.020442962646484375s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.793571472167969e-05s
Believability | Calculation of trust value for NTNU special collections took 7.867813110351562e-06s
INFO | --- Analysis for ntnusc took 5.392469644546509s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 4.57763671875e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.2581191062927246s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.02031111717224121s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 9.72747802734375e-05s
Believability | Calculation of trust value for NUTS (GeoVocab) took 5.9604644775390625e-06s
INFO | --- Analysis for nuts-geovocab took 2.4763453006744385s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.40636253356933594s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0006649494171142578s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.2692091464996338s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.020685672760009766s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 7.319450378417969e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 8.344650268554688e-06s
INFO | --- Analysis for nvd took 4.036773204803467s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.8127841949462891s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0006690025329589844s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.2707040309906006s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.02060699462890625s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 8.630752563476562e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 8.106231689453125e-06s
INFO | --- Analysis for nvs took 8.37529444694519s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 7.557868957519531e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.26287007331848145s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.020847320556640625s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.00018739700317382812s
Believability | Calculation of trust value for New York Times - Linked Open Data took 8.344650268554688e-06s
INFO | --- Analysis for nytimes-linked-open-data took 2.4339025020599365s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 5.078315734863281e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.26425981521606445s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.020673751831054688s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 3.2901763916015625e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 8.821487426757812e-06s
INFO | --- Analysis for o-anc took 2.9546899795532227s
Availability | SPARQL endpoint availability check for OANetzwerk took 4.482269287109375e-05s
Availability | VoID file availability check for OANetzwerk took 0.0003304481506347656s
Completeness | Calculation of interlinking completeness for OANetzwerk took 0.28871703147888184s
Reputation | Calculation of the PageRank for OANetzwerk took 0.020764827728271484s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OANetzwerk took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 3.0994415283203125e-05s
Believability | Calculation of trust value for OANetzwerk took 8.344650268554688e-06s
INFO | --- Analysis for oanetzwerk took 3.0219132900238037s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 4.267692565917969e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.27684998512268066s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.020824193954467773s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 3.0279159545898438e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 8.58306884765625e-06s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 3.0026919841766357s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 60.83259606361389s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0007386207580566406s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.353503942489624s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.020874977111816406s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.00010466575622558594s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 7.3909759521484375e-06s
INFO | --- Analysis for ocd took 357.3018329143524s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 4.38690185546875e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0007176399230957031s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.2547173500061035s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.020907163619995117s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 4.029273986816406e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 7.62939453125e-06s
INFO | --- Analysis for oceandrilling-borehole took 5.602042198181152s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 1.665381908416748s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.00113677978515625s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.2800600528717041s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0008115768432617188s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 9.202957153320312e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 8.106231689453125e-06s
INFO | --- Analysis for oceandrilling-codices took 7.760287284851074s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 1.2657670974731445s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.25391387939453125s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.020658016204833984s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.528594970703125e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 8.821487426757812e-06s
INFO | --- Analysis for oceandrilling-dbseabed took 6.923703670501709s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 1.181072473526001s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.298084020614624s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.020482301712036133s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.266334533691406e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 6.9141387939453125e-06s
INFO | --- Analysis for oceandrilling-forams took 5.872186899185181s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 1.3687787055969238s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0007121562957763672s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.26654744148254395s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.02069687843322754s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.528594970703125e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 7.3909759521484375e-06s
INFO | --- Analysis for oceandrilling-janus took 6.0697081089019775s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 10.962048768997192s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0007555484771728516s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.28448057174682617s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020284414291381836s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.5762786865234375e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 7.867813110351562e-06s
INFO | --- Analysis for oceandrilling-janusamp took 15.611778736114502s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.3265459537506104s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.28028225898742676s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.020626306533813477s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.123283386230469e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 7.152557373046875e-06s
INFO | --- Analysis for oceandrilling-ldeo took 5.95851469039917s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 4.267692565917969e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0007188320159912109s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.2561659812927246s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.020722627639770508s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 6.699562072753906e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 1.0967254638671875e-05s
INFO | --- Analysis for oclc-fast took 12.103824138641357s
Availability | SPARQL endpoint availability check for Open Data Communities took 4.315376281738281e-05s
Availability | VoID file availability check for Open Data Communities took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.2546093463897705s
Reputation | Calculation of the PageRank for Open Data Communities took 0.020516633987426758s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data Communities took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 3.1948089599609375e-05s
Believability | Calculation of trust value for Open Data Communities took 7.62939453125e-06s
INFO | --- Analysis for odc took 3.4129202365875244s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.76837158203125e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.29286623001098633s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.02060532569885254s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 3.123283386230469e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.9073486328125e-05s
INFO | --- Analysis for odc-imd-environment-score took 5.204475164413452s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 4.172325134277344e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.2769181728363037s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.020577430725097656s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation Ranking, 2007 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation Ranking, 2007 took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 3.0517578125e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 7.3909759521484375e-06s
INFO | --- Analysis for odc-imd-rank-2007 took 2.9607529640197754s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.15507817268371582s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0006375312805175781s
Extra | Recovery of all triples for Open Data Communities - Lower layer Super Output Areas took 0.24109268188476562s
Performance | Total latancy measurement for Open Data Communities - Lower layer Super Output Areas took 0.8232266902923584s
Amount of data | Number of triples check for Open Data Communities - Lower layer Super Output Areas took 0.1992354393005371s
Interoperability | New terms check for Open Data Communities - Lower layer Super Output Areas took 1.5422461032867432s
Versatility | Languages check for Open Data Communities - Lower layer Super Output Areas took 0.4100620746612549s
Interpretability | Number of blank nodes check for Open Data Communities - Lower layer Super Output Areas took 0.36350178718566895s
Security | Check HTTPS for Open Data Communities - Lower layer Super Output Areas took 0.1244509220123291s
Interpretability | RDF structures check for Open Data Communities - Lower layer Super Output Areas took 0.14043664932250977s
Versatility | Serialization formats check for Open Data Communities - Lower layer Super Output Areas took 0.15868234634399414s
Availability | RDF dump link check for Open Data Communities - Lower layer Super Output Areas took 43.872437477111816s
License | MR license check for Open Data Communities - Lower layer Super Output Areas took 0.12787437438964844s
License | HR license check for Open Data Communities - Lower layer Super Output Areas took 0.24161028861999512s
Amount of data | Number of property check for Open Data Communities - Lower layer Super Output Areas took 0.13397979736328125s
Understandability | Number of label check for Open Data Communities - Lower layer Super Output Areas took 0.206925630569458s
Understandability | URI regex check for Open Data Communities - Lower layer Super Output Areas took 0.9864857196807861s
Understandability | Vocabs check for Open Data Communities - Lower layer Super Output Areas took 0.21872687339782715s
Verifiability | Authors check for Open Data Communities - Lower layer Super Output Areas took 0.1345837116241455s
Verifiability | Publishers check for Open Data Communities - Lower layer Super Output Areas took 0.14939522743225098s
Performance | Throughput check for Open Data Communities - Lower layer Super Output Areas took 11.711318492889404s
Amount of data | Check the number of entities for Open Data Communities - Lower layer Super Output Areas took 8.177757263183594e-05s
Verifiability | Contribs. check for Open Data Communities - Lower layer Super Output Areas took 0.14043664932250977s
Interlinking | sameAs chians check for Open Data Communities - Lower layer Super Output Areas took 0.15848159790039062s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.13693618774414062s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.134796142578125s
Timeliness | dataset update frequency check for Open Data Communities - Lower layer Super Output Areas took 0.18761396408081055s
Currency | Creation date check for Open Data Communities - Lower layer Super Output Areas took 0.35813307762145996s
Currency | Modification date check for Open Data Communities - Lower layer Super Output Areas took 0.14881181716918945s
Rep.Conc. | URIs length for Open Data Communities - Lower layer Super Output Areas took 0.4333188533782959s
Interoperability | New vocabularies check for Open Data Communities - Lower layer Super Output Areas took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Open Data Communities - Lower layer Super Output Areas took 0.20157623291015625s
Accuracy | Check Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.19178056716918945s
Accuracy | Check Inverse Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.14897394180297852s
Consistency | Disjoint class check for Open Data Communities - Lower layer Super Output Areas took 0.1382126808166504s
Consistency | Check Misplaced properties for Open Data Communities - Lower layer Super Output Areas took 0.35712623596191406s
Consistency | Check Ontology hijacking for Open Data Communities - Lower layer Super Output Areas took 0.21228575706481934s
Consistency | Check Invalid usage of undefined properties for Open Data Communities - Lower layer Super Output Areas took 1.5936071872711182s
Conciseness | Check Extensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.00014781951904296875s
Conciseness | Check Intensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.26931023597717285s
Security | Sign check for Open Data Communities - Lower layer Super Output Areas took 0.14136314392089844s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.2760794162750244s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.020568132400512695s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 5.602836608886719e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Communities - Lower layer Super Output Areas took 2.1457672119140625e-06s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 4.5299530029296875e-06s
INFO | --- Analysis for odc-lsoa took 162.501056432724s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 4.1484832763671875e-05s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.2660374641418457s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.02052164077758789s
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.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 3.337860107421875e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 8.58306884765625e-06s
INFO | --- Analysis for odc-population-2005 took 2.964099407196045s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 4.1961669921875e-05s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.2542271614074707s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.020743370056152344s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 9.059906005859375e-06s
INFO | --- Analysis for ods took 3.4027037620544434s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.4365379810333252s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.2800416946411133s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.020433902740478516s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.441375732421875e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for oecd-linked-data took 3.273483991622925s
Availability | SPARQL endpoint availability check for Offener Haushalt took 4.100799560546875e-05s
Availability | VoID file availability check for Offener Haushalt took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 0.2377917766571045s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.02111053466796875s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 3.0040740966796875e-05s
Believability | Calculation of trust value for Offener Haushalt took 8.106231689453125e-06s
INFO | --- Analysis for offener-haushalt took 2.9512174129486084s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.41790509223938s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0007216930389404297s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.3237624168395996s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.020304441452026367s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.5299530029296875e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 7.3909759521484375e-06s
INFO | --- Analysis for ogolod took 103.0682315826416s
Availability | SPARQL endpoint availability check for OLiA took 4.291534423828125e-05s
Availability | VoID file availability check for OLiA took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for OLiA took 0.2665228843688965s
Reputation | Calculation of the PageRank for OLiA took 0.021016597747802734s
Interlinking | Calculation of Degree of Connection for OLiA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00012969970703125s
Believability | Calculation of trust value for OLiA took 8.58306884765625e-06s
INFO | --- Analysis for olia took 19.962255239486694s
Availability | SPARQL endpoint availability check for OLiA Discourse took 4.5299530029296875e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.2733123302459717s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.02081465721130371s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 4.0531158447265625e-05s
Believability | Calculation of trust value for OLiA Discourse took 7.62939453125e-06s
INFO | --- Analysis for olia-discourse took 8.486993074417114s
Availability | SPARQL endpoint availability check for OmegaWiki took 4.1961669921875e-05s
Availability | VoID file availability check for OmegaWiki took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for OmegaWiki took 0.25767064094543457s
Reputation | Calculation of the PageRank for OmegaWiki took 0.020476341247558594s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for OmegaWiki took 0.0009951591491699219s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 3.838539123535156e-05s
Believability | Calculation of trust value for OmegaWiki took 9.059906005859375e-06s
INFO | --- Analysis for omegawiki took 3.0004117488861084s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 4.423199653625488s
Availability | VoID file availability check for OntoBeef Domain took 0.0006189346313476562s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.2586088180541992s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.020351886749267578s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.076957702636719e-05s
Believability | Calculation of trust value for OntoBeef Domain took 7.152557373046875e-06s
INFO | --- Analysis for ontobeef-domain took 31.644855260849s
Availability | SPARQL endpoint availability check for Ontos News Portal took 5.4836273193359375e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.2642073631286621s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.020385026931762695s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 9.369850158691406e-05s
Believability | Calculation of trust value for Ontos News Portal took 7.62939453125e-06s
INFO | --- Analysis for ontos-news-portal took 3.6065800189971924s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 6.29425048828125e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.25658750534057617s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.020703792572021484s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.838539123535156e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 7.62939453125e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 9.629799604415894s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 6.4849853515625e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.23927807807922363s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.020685195922851562s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 3.0517578125e-05s
Believability | Calculation of trust value for Open Courseware Consortium metadata in RDF took 8.344650268554688e-06s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 2.884883165359497s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 4.220008850097656e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.2658371925354004s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.020714759826660156s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 5.0067901611328125e-05s
Believability | Calculation of trust value for Open Data Euskadi took 6.67572021484375e-06s
INFO | --- Analysis for open-data-euskadi took 9.214680910110474s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 4.410743713378906e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0007939338684082031s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.25733256340026855s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.020602703094482422s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00010132789611816406s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 7.3909759521484375e-06s
INFO | --- Analysis for open-data-risp took 8.620712041854858s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.2584996223449707s
Availability | VoID file availability check for Open Data Thesaurus took 0.0006999969482421875s
Extra | Recovery of all triples for Open Data Thesaurus took 1.1468772888183594s
Performance | Total latancy measurement for Open Data Thesaurus took 0.5194427967071533s
Amount of data | Number of triples check for Open Data Thesaurus took 0.12936782836914062s
Interoperability | New terms check for Open Data Thesaurus took 1.4864552021026611s
Versatility | Languages check for Open Data Thesaurus took 0.11458969116210938s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.14188241958618164s
Security | Check HTTPS for Open Data Thesaurus took 0.30205464363098145s
Interpretability | RDF structures check for Open Data Thesaurus took 0.10548639297485352s
Versatility | Serialization formats check for Open Data Thesaurus took 0.11393618583679199s
Availability | RDF dump link check for Open Data Thesaurus took 1.2346436977386475s
License | MR license check for Open Data Thesaurus took 0.11973953247070312s
License | HR license check for Open Data Thesaurus took 0.10518980026245117s
Amount of data | Number of property check for Open Data Thesaurus took 0.11238360404968262s
Understandability | Number of label check for Open Data Thesaurus took 0.1273946762084961s
Understandability | URI regex check for Open Data Thesaurus took 0.19119501113891602s
Understandability | Vocabs check for Open Data Thesaurus took 0.1299457550048828s
Verifiability | Authors check for Open Data Thesaurus took 0.11336421966552734s
Verifiability | Publishers check for Open Data Thesaurus took 0.11302733421325684s
Performance | Throughput check for Open Data Thesaurus took 10.345582008361816s
Amount of data | Check the number of entities for Open Data Thesaurus took 7.343292236328125e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.11143660545349121s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.12917637825012207s
Interlinking | skos check for Open Data Thesaurus took 0.12773919105529785s
Interlinking | skos check for Open Data Thesaurus took 0.07890534400939941s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.10906410217285156s
Currency | Creation date check for Open Data Thesaurus took 0.2067577838897705s
Currency | Modification date check for Open Data Thesaurus took 0.2124464511871338s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.4643733501434326s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.11969900131225586s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.08229351043701172s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.0785057544708252s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.1886904239654541s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011210441589355469s
Consistency | Disjoint class check for Open Data Thesaurus took 0.09885191917419434s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.22056984901428223s
Consistency | Misplaced classes for Open Data Thesaurus took 0.11846351623535156s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.4747910499572754s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.455503225326538s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.00013184547424316406s
Security | Sign check for Open Data Thesaurus took 0.0971364974975586s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.261366605758667s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.020148754119873047s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 7.748603820800781e-05s
Believability | Calculation of trust value for Open Data Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for open-data-thesaurus took 66.99607110023499s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 4.100799560546875e-05s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.2831881046295166s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.020581722259521484s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 2.86102294921875e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 7.62939453125e-06s
INFO | --- Analysis for open-data-tor-vergata took 2.9447367191314697s
Availability | SPARQL endpoint availability check for Open Election Data Project took 4.3392181396484375e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.2591068744659424s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.020220279693603516s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0008928775787353516s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.604194641113281e-05s
Believability | Calculation of trust value for Open Election Data Project took 1.0251998901367188e-05s
INFO | --- Analysis for open-election-data-project took 3.189347267150879s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 3.7519583702087402s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0006871223449707031s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.24912714958190918s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 8.845329284667969e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 5.4836273193359375e-06s
INFO | --- Analysis for open-energy-info-wiki took 10.657595872879028s
Availability | SPARQL endpoint availability check for Open Library took 4.458427429199219e-05s
Availability | VoID file availability check for Open Library took 0.0007338523864746094s
Completeness | Calculation of interlinking completeness for Open Library took 0.26055383682250977s
Reputation | Calculation of the PageRank for Open Library took 0.020446300506591797s
Interlinking | Calculation of Degree of Connection for Open Library took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Open Library took 6.747245788574219e-05s
Believability | Calculation of trust value for Open Library took 7.867813110351562e-06s
INFO | --- Analysis for open-library took 9.818873882293701s
Availability | SPARQL endpoint availability check for Open Directory took 4.2438507080078125e-05s
Availability | VoID file availability check for Open Directory took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Open Directory took 0.2903587818145752s
Reputation | Calculation of the PageRank for Open Directory took 0.020548343658447266s
Interlinking | Calculation of Degree of Connection for Open Directory took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Directory took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Open Directory took 2.8848648071289062e-05s
Believability | Calculation of trust value for Open Directory took 8.344650268554688e-06s
INFO | --- Analysis for open_directory took 3.0349442958831787s
Availability | SPARQL endpoint availability check for flyatlas took 1.6509323120117188s
Availability | VoID file availability check for flyatlas took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for flyatlas took 0.2662782669067383s
Reputation | Calculation of the PageRank for flyatlas took 0.020815610885620117s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for flyatlas took 2.8848648071289062e-05s
Believability | Calculation of trust value for flyatlas took 7.867813110351562e-06s
INFO | --- Analysis for openbiomed-flyatlas took 9.88694453239441s
Availability | SPARQL endpoint availability check for OpenCalais took 5.5789947509765625e-05s
Availability | VoID file availability check for OpenCalais took 0.0005919933319091797s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.2901804447174072s
Reputation | Calculation of the PageRank for OpenCalais took 0.0203397274017334s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00010943412780761719s
Believability | Calculation of trust value for OpenCalais took 7.867813110351562e-06s
INFO | --- Analysis for opencalais took 5.321675539016724s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 4.315376281738281e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.2860534191131592s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.02040386199951172s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.271766662597656e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 5.4836273193359375e-06s
INFO | --- Analysis for opencorporates took 2.785285472869873s
Availability | SPARQL endpoint availability check for OpenCyc took 4.2438507080078125e-05s
Availability | VoID file availability check for OpenCyc took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.24002838134765625s
Reputation | Calculation of the PageRank for OpenCyc took 0.020402193069458008s
Interlinking | Calculation of Degree of Connection for OpenCyc took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00010657310485839844s
Believability | Calculation of trust value for OpenCyc took 7.62939453125e-06s
INFO | --- Analysis for opencyc took 2.3517558574676514s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.2550027370452881s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.020531654357910156s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.528594970703125e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 3.822930335998535s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.26726269721984863s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.02037334442138672s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 3.1007189750671387s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.506111145019531e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0006988048553466797s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.2682325839996338s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.020409345626831055s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.9114227294921875e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.3272905349731445s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 4.839897155761719e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.26007533073425293s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.0202789306640625s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.3794338703155518s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 5.53131103515625e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.2722949981689453s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.020316123962402344s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 3.205502510070801s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0004074573516845703s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.25379133224487305s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.020879030227661133s
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.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-households-projections-population took 2.9844071865081787s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0006315708160400391s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.2800471782684326s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.020208358764648438s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 3.7702343463897705s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.2807810306549072s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.020320653915405273s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.673004150390625e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.400059700012207s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007989406585693359s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.266709566116333s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.020187854766845703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.004451036453247s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.2554609775543213s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.020520925521850586s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-housing-market took 2.952899932861328s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0007317066192626953s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.2555258274078369s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.030574798583984375s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0011174678802490234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 5.555152893066406e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 3.13016676902771s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.25603175163269043s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.020411014556884766s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 3.1300389766693115s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 5.316734313964844e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.2654697895050049s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.021524667739868164s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 3.1640279293060303s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.27086782455444336s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.02094411849975586s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.3677988052368164s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.2780113220214844s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.020641088485717773s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0009865760803222656s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.649162292480469e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 3.137028455734253s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.24108600616455078s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.023221254348754883s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.00127410888671875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 5.602836608886719e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 3.0952436923980713s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 5.435943603515625e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.3171265125274658s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.020260334014892578s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.006669759750366s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.26899218559265137s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.02042078971862793s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 3.2120754718780518s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.25710630416870117s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.02053380012512207s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 9.059906005859375e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.3343117237091064s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.28189945220947266s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.02011418342590332s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 3.0905566215515137s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.00033402442932128906s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.25891590118408203s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.020282506942749023s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 3.199791669845581s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0003647804260253906s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.24160194396972656s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-service-expenditure took 3.9894745349884033s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.601478576660156e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.25325536727905273s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020317792892456055s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 3.837249755859375s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.2688283920288086s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.020298480987548828s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 3.9244561195373535s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0003674030303955078s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.2658116817474365s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.02029275894165039s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 3.507603168487549s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.00044035911560058594s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.272136926651001s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.020790815353393555s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0008387565612792969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 5.054473876953125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 3.713041305541992s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.24294543266296387s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0008194446563720703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.673004150390625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 9.298324584960938e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.065540313720703s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.28716039657592773s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.020974159240722656s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 3.73532772064209s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.000637054443359375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.23969745635986328s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.839897155761719e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.128175497055054s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.57763671875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007059574127197266s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.26807260513305664s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.020905017852783203s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.6253204345703125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 3.754082679748535s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007326602935791016s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.26888346672058105s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.020615339279174805s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.394200563430786s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.2692446708679199s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.020341157913208008s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.9591064453125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 3.719329833984375e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 3.6621272563934326s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.553794860839844e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.2913980484008789s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.020476341247558594s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.57763671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 3.884410858154297s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.26079511642456055s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.020409584045410156s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.792213439941406e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 8.821487426757812e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.3232297897338867s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 5.53131103515625e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.2702972888946533s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.02066659927368164s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.3719403743743896s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.506111145019531e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.2821934223175049s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.020397186279296875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.57763671875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 3.501162052154541s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 5.650520324707031e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007092952728271484s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.25444531440734863s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.020910978317260742s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.639199495315552s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.2612721920013428s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.020467281341552734s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 3.347895622253418s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.257551908493042s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.020474672317504883s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 2.968480110168457s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.00035572052001953125s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.2426767349243164s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.020554542541503906s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.863739013671875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 3.381293773651123s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0003731250762939453s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.2653207778930664s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.020655155181884766s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.868807554244995s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007262229919433594s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.27562379837036133s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.020646333694458008s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 5.245208740234375e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.5054609775543213s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.2760579586029053s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.02047109603881836s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 4.596773147583008s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 5.983729839324951s
Availability | VoID file availability check for Open Data of Ecuador took 0.000396728515625s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.25573062896728516s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.02021956443786621s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.916854858398438e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 7.867813110351562e-06s
INFO | --- Analysis for opendataec took 11.09883737564087s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.26160669326782227s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.02080702781677246s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0008463859558105469s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.7206878662109375e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 8.58306884765625e-06s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 17.74336004257202s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 5.745887756347656e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.2578885555267334s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.02036452293395996s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.6716461181640625e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 8.821487426757812e-06s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 3.65181565284729s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0010292530059814453s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.26442527770996094s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020615339279174805s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 2.7670528888702393s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 9.489059448242188e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.2526066303253174s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 7.152557373046875e-06s
INFO | --- Analysis for opendatascotland-simd-education-rank took 2.7072768211364746s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 5.888938903808594e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.29024314880371094s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.020377159118652344s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 2.7078516483306885s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 4.291534423828125e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.28158092498779297s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.020457983016967773s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 6.9141387939453125e-06s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 2.799917697906494s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 4.1961669921875e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0006020069122314453s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.2536466121673584s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.62396240234375e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 7.152557373046875e-06s
INFO | --- Analysis for opendatascotland-simd-health-rank took 2.768765926361084s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.26755714416503906s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.0202486515045166s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 7.867813110351562e-06s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 2.66449236869812s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 4.1961669921875e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.26377201080322266s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.020384550094604492s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 3.62396240234375e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 6.9141387939453125e-06s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.329958200454712s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.51609778404236s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.2739126682281494s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.020539283752441406s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 2.9802322387695312e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 7.152557373046875e-06s
INFO | --- Analysis for openlink-lod-cache took 62.94849491119385s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 6.628036499023438e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.28099679946899414s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.020367860794067383s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.608268737792969e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 5.245208740234375e-06s
INFO | --- Analysis for openlylocal took 9.028215885162354s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 1.0477657318115234s
Availability | VoID file availability check for OpenMobileNetwork took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.26346397399902344s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.020484209060668945s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.486343383789062e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 6.67572021484375e-06s
INFO | --- Analysis for openmobilenetwork took 3.993523597717285s
Availability | SPARQL endpoint availability check for OpenTox took 4.1961669921875e-05s
Availability | VoID file availability check for OpenTox took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for OpenTox took 0.2674293518066406s
Reputation | Calculation of the PageRank for OpenTox took 0.020426511764526367s
Interlinking | Calculation of Degree of Connection for OpenTox took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenTox took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for OpenTox took 2.8133392333984375e-05s
Believability | Calculation of trust value for OpenTox took 8.344650268554688e-06s
INFO | --- Analysis for opentox took 2.9017744064331055s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 4.1484832763671875e-05s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.27793121337890625s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.020385265350341797s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 2.9325485229492188e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 7.152557373046875e-06s
INFO | --- Analysis for openuplabs took 2.9330790042877197s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 4.100799560546875e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.00022411346435546875s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.25905656814575195s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.020278453826904297s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 2.8371810913085938e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 7.3909759521484375e-06s
INFO | --- Analysis for opus took 2.876121759414673s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 4.696846008300781e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.24621057510375977s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.02034592628479004s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 3.62396240234375e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 7.152557373046875e-06s
INFO | --- Analysis for orcid took 2.9016928672790527s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 1.0095205307006836s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.2447812557220459s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.020222902297973633s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 9.679794311523438e-05s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 7.62939453125e-06s
INFO | --- Analysis for ordnance-survey-linked-data took 5.37213397026062s
Availability | SPARQL endpoint availability check for oreilly took 4.291534423828125e-05s
Availability | VoID file availability check for oreilly took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for oreilly took 0.27222132682800293s
Reputation | Calculation of the PageRank for oreilly took 0.02037954330444336s
Interlinking | Calculation of Degree of Connection for oreilly took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for oreilly took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for oreilly took 4.8160552978515625e-05s
Believability | Calculation of trust value for oreilly took 8.821487426757812e-06s
INFO | --- Analysis for oreilly took 4.4233176708221436s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.0676717758178711s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.27840137481689453s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.020659923553466797s
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.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 7.033348083496094e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 8.344650268554688e-06s
INFO | --- Analysis for organic-edunet took 9.345995664596558s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 3.1334288120269775s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.2694556713104248s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.02035665512084961s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 8.177757263183594e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 7.62939453125e-06s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 29.25238800048828s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.4940502643585205s
Availability | VoID file availability check for OSM Semantic Network took 0.0007202625274658203s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.2801046371459961s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.020630836486816406s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.695487976074219e-05s
Believability | Calculation of trust value for OSM Semantic Network took 6.67572021484375e-06s
INFO | --- Analysis for osm-semantic-network took 8.140480041503906s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 4.482269287109375e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.2485337257385254s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.02077794075012207s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 3.0994415283203125e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 8.106231689453125e-06s
INFO | --- Analysis for ounl-dspace-in-rdf took 2.9222893714904785s
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.0002522468566894531s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.27123522758483887s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020604848861694336s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 7.867813110351562e-06s
INFO | --- Analysis for ox-ac-uk-catalogue took 2.796541213989258s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.220008850097656e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.24677658081054688s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020387649536132812s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 3.0517578125e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 7.3909759521484375e-06s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 2.821646213531494s
Availability | SPARQL endpoint availability check for OpenMeters (University of Oxford) took 4.076957702636719e-05s
Availability | VoID file availability check for OpenMeters (University of Oxford) took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.2549736499786377s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.02069830894470215s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 3.0994415283203125e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 7.867813110351562e-06s
INFO | --- Analysis for ox-ac-uk-openmeters took 2.8060269355773926s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 4.1961669921875e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.0003032684326171875s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.25799131393432617s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.020789146423339844s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Time-series metadata (University of Oxford) took 8.344650268554688e-06s
INFO | --- Analysis for ox-ac-uk-timeseries took 2.7792887687683105s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 4.267692565917969e-05s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.00028705596923828125s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.23634052276611328s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.02094888687133789s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 3.075599670410156e-05s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 8.821487426757812e-06s
INFO | --- Analysis for ox-ac-uk-vacancies took 2.730534315109253s
Availability | SPARQL endpoint availability check for Events calendar for the University (University of Oxford) took 4.2438507080078125e-05s
Availability | VoID file availability check for Events calendar for the University (University of Oxford) took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.2596731185913086s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.02072000503540039s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for Events calendar for the University (University of Oxford) took 3.0517578125e-05s
Believability | Calculation of trust value for Events calendar for the University (University of Oxford) took 9.059906005859375e-06s
INFO | --- Analysis for ox-ac-uk-www-ox-ac-uk-events took 2.832913398742676s
Availability | SPARQL endpoint availability check for OxPoints (University of Oxford) took 4.267692565917969e-05s
Availability | VoID file availability check for OxPoints (University of Oxford) took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.25521183013916016s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.02060556411743164s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 3.719329833984375e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 8.344650268554688e-06s
INFO | --- Analysis for oxpoints took 2.833488702774048s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.8293366432189941s
Availability | VoID file availability check for Pali English Lexicon took 0.0003666877746582031s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.25597119331359863s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.02033686637878418s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 3.337860107421875e-05s
Believability | Calculation of trust value for Pali English Lexicon took 6.9141387939453125e-06s
INFO | --- Analysis for pali-english-lexicon took 6.906791687011719s
Availability | SPARQL endpoint availability check for PanLex took 0.4730801582336426s
Availability | VoID file availability check for PanLex took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for PanLex took 0.2798748016357422s
Reputation | Calculation of the PageRank for PanLex took 0.02053689956665039s
Interlinking | Calculation of Degree of Connection for PanLex took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.62939453125e-05s
Believability | Calculation of trust value for PanLex took 8.821487426757812e-06s
INFO | --- Analysis for panlex took 2.8953232765197754s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.08788180351257324s
Availability | VoID file availability check for patents.data.gov.uk took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.26437950134277344s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.020879745483398438s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 5.507469177246094e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 5.245208740234375e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.541353464126587s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 4.291534423828125e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0006520748138427734s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.28187036514282227s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.02067255973815918s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 3.814697265625e-05s
Believability | Calculation of trust value for PDEV-Lemon took 9.5367431640625e-06s
INFO | --- Analysis for pdev-lemon took 3.8863415718078613s
Availability | SPARQL endpoint availability check for pdevlemon took 4.363059997558594e-05s
Availability | VoID file availability check for pdevlemon took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.2686612606048584s
Reputation | Calculation of the PageRank for pdevlemon took 0.020923614501953125s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.0517578125e-05s
Believability | Calculation of trust value for pdevlemon took 1.2636184692382812e-05s
INFO | --- Analysis for pdevlemon took 3.1659812927246094s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 4.291534423828125e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0008373260498046875s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.2721107006072998s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.020308971405029297s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 7.915496826171875e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 8.58306884765625e-06s
INFO | --- Analysis for periodo took 18.825806379318237s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.291534423828125e-05s
Availability | VoID file availability check for Personal_Homepages took 0.0003085136413574219s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.2654554843902588s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020632266998291016s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.00039267539978027344s
Believability | Calculation of trust value for Personal_Homepages took 8.58306884765625e-06s
INFO | --- Analysis for personal-homepages took 2.363346815109253s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 1.1281626224517822s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007419586181640625s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.27452850341796875s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.02066326141357422s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 9.298324584960938e-06s
INFO | --- Analysis for phoible took 4.991434097290039s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.363059997558594e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.2658534049987793s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.02064061164855957s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.392333984375e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 8.344650268554688e-06s
INFO | --- Analysis for planetdata-project-wiki took 2.419624090194702s
Availability | SPARQL endpoint availability check for Pleiades took 4.267692565917969e-05s
Availability | VoID file availability check for Pleiades took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for Pleiades took 0.2629210948944092s
Reputation | Calculation of the PageRank for Pleiades took 0.020328044891357422s
Interlinking | Calculation of Degree of Connection for Pleiades took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Pleiades took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Pleiades took 7.963180541992188e-05s
Believability | Calculation of trust value for Pleiades took 6.9141387939453125e-06s
INFO | --- Analysis for pleiades took 13.304232358932495s
Availability | SPARQL endpoint availability check for Poképédia took 4.482269287109375e-05s
Availability | VoID file availability check for Poképédia took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Poképédia took 0.2532472610473633s
Reputation | Calculation of the PageRank for Poképédia took 0.020483732223510742s
Interlinking | Calculation of Degree of Connection for Poképédia took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Poképédia took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Poképédia took 7.200241088867188e-05s
Believability | Calculation of trust value for Poképédia took 1.1444091796875e-05s
INFO | --- Analysis for pokepedia-fr took 2.673959970474243s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 5.412101745605469e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.2804899215698242s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.700920104980469e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.152557373046875e-06s
INFO | --- Analysis for polymath-virtual-library took 5.854538679122925s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 4.1961669921875e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.25078916549682617s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.020627498626708984s
Interlinking | Calculation of Degree of Connection for Barley trading volume and wholesale prices took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Barley trading volume and wholesale prices took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 4.267692565917969e-05s
Believability | Calculation of trust value for Barley trading volume and wholesale prices took 7.62939453125e-06s
INFO | --- Analysis for predicting-barley-volume-and-wholesale-prices took 2.885848045349121s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 4.172325134277344e-05s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.2682769298553467s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.020525693893432617s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Corn trading volume and wholesale prices took 2.9325485229492188e-05s
Believability | Calculation of trust value for Corn trading volume and wholesale prices took 7.62939453125e-06s
INFO | --- Analysis for predicting-corn-trading-volume-and-wholesale-prices took 2.905886173248291s
Availability | SPARQL endpoint availability check for Onion trading volume and wholesale prices took 4.076957702636719e-05s
Availability | VoID file availability check for Onion trading volume and wholesale prices took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.27713847160339355s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.020401954650878906s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 2.86102294921875e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 9.298324584960938e-06s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 2.8279714584350586s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 5.1021575927734375e-05s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.000225067138671875s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.2562081813812256s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.020353078842163086s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Potato trading volume and wholesale price took 3.123283386230469e-05s
Believability | Calculation of trust value for Potato trading volume and wholesale price took 8.58306884765625e-06s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 2.941377878189087s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 5.245208740234375e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.27770328521728516s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of apples took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of apples took 0.0008139610290527344s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 3.218650817871094e-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.9221696853637695s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 4.076957702636719e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.2688868045806885s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.020687341690063477s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of barley took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of barley took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of barley took 3.123283386230469e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of barley took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 2.8920443058013916s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of bean took 4.172325134277344e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of bean took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.2568325996398926s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.020581960678100586s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of bean took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of bean took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of bean took 3.0994415283203125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of bean took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 2.8797388076782227s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 4.076957702636719e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.2650146484375s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.020566463470458984s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 3.0517578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 2.9371795654296875s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of corn took 4.0531158447265625e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of corn took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.2585134506225586s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.020540952682495117s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 2.9087066650390625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of corn took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-corn took 2.9547646045684814s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of crab took 4.1484832763671875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of crab took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.2685885429382324s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.020353317260742188s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of crab took 3.075599670410156e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of crab took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 2.883488178253174s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cucumber took 4.1484832763671875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cucumber took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.2613239288330078s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 2.9802322387695312e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 2.815520763397217s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 4.1961669921875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.2685248851776123s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.02055525779724121s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of lettuce took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of lettuce took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 3.266334533691406e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 8.344650268554688e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 2.8273322582244873s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 4.1961669921875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 0.26184844970703125s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.02039647102355957s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 2.9802322387695312e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of onion took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-onion took 2.8164284229278564s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of oyster mushroom took 7.867813110351562e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of oyster mushroom took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.26341962814331055s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.02059483528137207s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 2.9325485229492188e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of oyster mushroom took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-oyster-mushroom took 2.8841052055358887s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 4.982948303222656e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.00022864341735839844s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.26602649688720703s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of potato took 3.0517578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of potato took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-potato took 2.936082601547241s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of radish took 4.267692565917969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of radish took 0.000244140625s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.2446281909942627s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.020455121994018555s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of radish took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of radish took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 2.956390380859375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 2.8741872310638428s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 4.220008850097656e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.25338053703308105s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.02055191993713379s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of rice plant took 3.0517578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of rice plant took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 2.9548821449279785s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 8.845329284667969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.258075475692749s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.02034449577331543s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 3.0040740966796875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of watermelon took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-watermelon took 2.9107158184051514s
Availability | SPARQL endpoint availability check for prefix.cc took 4.363059997558594e-05s
Availability | VoID file availability check for prefix.cc took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.2554924488067627s
Reputation | Calculation of the PageRank for prefix.cc took 0.02059316635131836s
Interlinking | Calculation of Degree of Connection for prefix.cc took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 3.719329833984375e-05s
Believability | Calculation of trust value for prefix.cc took 7.152557373046875e-06s
INFO | --- Analysis for prefix-cc took 3.1381618976593018s
Availability | SPARQL endpoint availability check for PreLex took 0.15225577354431152s
Availability | VoID file availability check for PreLex took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for PreLex took 0.2626371383666992s
Reputation | Calculation of the PageRank for PreLex took 0.020844697952270508s
Interlinking | Calculation of Degree of Connection for PreLex took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for PreLex took 0.00021386146545410156s
Believability | Calculation of trust value for PreLex took 7.3909759521484375e-06s
INFO | --- Analysis for prelex took 2.75791335105896s
Availability | SPARQL endpoint availability check for Prelinger Archives took 2.5988612174987793s
Availability | VoID file availability check for Prelinger Archives took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.28429269790649414s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.0994415283203125e-05s
Believability | Calculation of trust value for Prelinger Archives took 7.3909759521484375e-06s
INFO | --- Analysis for prelinger_archives took 11.027349948883057s
Availability | SPARQL endpoint availability check for PreMOn (Predicate Model for Ontologies) took 0.5755562782287598s
Availability | VoID file availability check for PreMOn (Predicate Model for Ontologies) took 0.0006923675537109375s
Extra | Recovery of all triples for PreMOn (Predicate Model for Ontologies) took 4.545704364776611s
Performance | Total latancy measurement for PreMOn (Predicate Model for Ontologies) took 0.939462423324585s
Amount of data | Number of triples check for PreMOn (Predicate Model for Ontologies) took 0.09196877479553223s
Interoperability | New terms check for PreMOn (Predicate Model for Ontologies) took 2.1792261600494385s
Versatility | Languages check for PreMOn (Predicate Model for Ontologies) took 59.1708550453186s
Interpretability | Number of blank nodes check for PreMOn (Predicate Model for Ontologies) took 0.4030275344848633s
Security | Check HTTPS for PreMOn (Predicate Model for Ontologies) took 0.09769964218139648s
Interpretability | RDF structures check for PreMOn (Predicate Model for Ontologies) took 0.18942523002624512s
Versatility | Serialization formats check for PreMOn (Predicate Model for Ontologies) took 0.3691287040710449s
Availability | RDF dump link check for PreMOn (Predicate Model for Ontologies) took 0.21810412406921387s
License | MR license check for PreMOn (Predicate Model for Ontologies) took 0.37235093116760254s
License | HR license check for PreMOn (Predicate Model for Ontologies) took 0.9278347492218018s
Amount of data | Number of property check for PreMOn (Predicate Model for Ontologies) took 0.208665132522583s
Understandability | Number of label check for PreMOn (Predicate Model for Ontologies) took 0.09160065650939941s
Understandability | URI regex check for PreMOn (Predicate Model for Ontologies) took 0.4233849048614502s
Understandability | Vocabs check for PreMOn (Predicate Model for Ontologies) took 0.4730055332183838s
Verifiability | Authors check for PreMOn (Predicate Model for Ontologies) took 0.3828098773956299s
Verifiability | Publishers check for PreMOn (Predicate Model for Ontologies) took 0.38147735595703125s
Performance | Throughput check for PreMOn (Predicate Model for Ontologies) took 10.783796310424805s
Amount of data | Check the number of entities for PreMOn (Predicate Model for Ontologies) took 7.128715515136719e-05s
Verifiability | Contribs. check for PreMOn (Predicate Model for Ontologies) took 0.21217083930969238s
Interlinking | sameAs chians check for PreMOn (Predicate Model for Ontologies) took 0.08846426010131836s
Interlinking | skos check for PreMOn (Predicate Model for Ontologies) took 0.09318256378173828s
Interlinking | skos check for PreMOn (Predicate Model for Ontologies) took 0.10369229316711426s
Timeliness | dataset update frequency check for PreMOn (Predicate Model for Ontologies) took 0.27895498275756836s
Currency | Creation date check for PreMOn (Predicate Model for Ontologies) took 0.4281175136566162s
Currency | Modification date check for PreMOn (Predicate Model for Ontologies) took 0.42075681686401367s
Rep.Conc. | URIs length for PreMOn (Predicate Model for Ontologies) took 3.9569990634918213s
Interoperability | New vocabularies check for PreMOn (Predicate Model for Ontologies) took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for PreMOn (Predicate Model for Ontologies) took 0.21152734756469727s
Accuracy | Check Empty annotation labels for PreMOn (Predicate Model for Ontologies) took 1.8340167999267578s
Accuracy | Check White space in annotation for PreMOn (Predicate Model for Ontologies) took 0.08216500282287598s
Accuracy | Check Datatype consistency for PreMOn (Predicate Model for Ontologies) took 0.08016729354858398s
Consistency | Disjoint class check for PreMOn (Predicate Model for Ontologies) took 0.20006823539733887s
Consistency | Check Misplaced properties for PreMOn (Predicate Model for Ontologies) took 2.004833459854126s
Consistency | Misplaced classes for PreMOn (Predicate Model for Ontologies) took 0.4490029811859131s
Consistency | Check Ontology hijacking for PreMOn (Predicate Model for Ontologies) took 2.562971353530884s
Consistency | Check Invalid usage of undefined classes for PreMOn (Predicate Model for Ontologies) took 1.3368887901306152s
Consistency | Check Invalid usage of undefined properties for PreMOn (Predicate Model for Ontologies) took 3.1442949771881104s
Conciseness | Check Extensional conciseness for PreMOn (Predicate Model for Ontologies) took 0.0881948471069336s
Conciseness | Check Intensional conciseness for PreMOn (Predicate Model for Ontologies) took 0.2210240364074707s
Security | Sign check for PreMOn (Predicate Model for Ontologies) took 0.2135758399963379s
Availability | Check URIs Dereferenciability for PreMOn (Predicate Model for Ontologies) took 1157.3125281333923s
Completeness | Calculation of interlinking completeness for PreMOn (Predicate Model for Ontologies) took 0.9534506797790527s
Reputation | Calculation of the PageRank for PreMOn (Predicate Model for Ontologies) took 0.021456241607666016s
Interlinking | Calculation of Degree of Connection for PreMOn (Predicate Model for Ontologies) took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for PreMOn (Predicate Model for Ontologies) took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for PreMOn (Predicate Model for Ontologies) took 6.67572021484375e-05s
Interoperability | Check the re-using of existing vocabs for PreMOn (Predicate Model for Ontologies) took 2.1457672119140625e-06s
Believability | Calculation of trust value for PreMOn (Predicate Model for Ontologies) took 7.867813110351562e-06s
INFO | --- Analysis for premon took 1282.2175796031952s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 4.38690185546875e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0007054805755615234s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.29364633560180664s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.021123409271240234s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.91278076171875e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 7.3909759521484375e-06s
INFO | --- Analysis for princeton-library-findingaids took 7.140471935272217s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.5506575107574463s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.3006250858306885s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.320808410644531e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 6.9141387939453125e-06s
INFO | --- Analysis for printed-book-auction-catalogues took 3.4278931617736816s
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.0002620220184326172s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.2678954601287842s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.020316362380981445s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 3.0279159545898438e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 7.867813110351562e-06s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 3.4800944328308105s
Availability | SPARQL endpoint availability check for Procomún SPARQL took 4.4345855712890625e-05s
Availability | VoID file availability check for Procomún SPARQL took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for Procomún SPARQL took 0.2636737823486328s
Reputation | Calculation of the PageRank for Procomún SPARQL took 0.02060389518737793s
Interlinking | Calculation of Degree of Connection for Procomún SPARQL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Procomún SPARQL took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Procomún SPARQL took 3.457069396972656e-05s
Believability | Calculation of trust value for Procomún SPARQL took 9.5367431640625e-06s
INFO | --- Analysis for procomun-sparql took 3.3736796379089355s
Availability | SPARQL endpoint availability check for PROD - JISC Project Directory in RDF took 5.4836273193359375e-05s
Availability | VoID file availability check for PROD - JISC Project Directory in RDF took 0.000274658203125s
Completeness | Calculation of interlinking completeness for PROD - JISC Project Directory in RDF took 0.2535233497619629s
Reputation | Calculation of the PageRank for PROD - JISC Project Directory in RDF took 0.020625591278076172s
Interlinking | Calculation of Degree of Connection for PROD - JISC Project Directory in RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PROD - JISC Project Directory in RDF took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for PROD - JISC Project Directory in RDF took 3.0994415283203125e-05s
Believability | Calculation of trust value for PROD - JISC Project Directory in RDF took 7.867813110351562e-06s
INFO | --- Analysis for prod-jisc-project-directory-in-rdf took 2.9007277488708496s
Availability | SPARQL endpoint availability check for ProductDB took 2.9884119033813477s
Availability | VoID file availability check for ProductDB took 0.0007383823394775391s
Completeness | Calculation of interlinking completeness for ProductDB took 0.251558780670166s
Reputation | Calculation of the PageRank for ProductDB took 0.023232221603393555s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.486343383789062e-05s
Believability | Calculation of trust value for ProductDB took 8.58306884765625e-06s
INFO | --- Analysis for productdb took 7.519028663635254s
Availability | SPARQL endpoint availability check for Product Types Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.2501647472381592s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.020490169525146484s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 9.274482727050781e-05s
Believability | Calculation of trust value for Product Types Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for productontology took 3.3143715858459473s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 4.315376281738281e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.2667720317840576s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.020352840423583984s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.00010418891906738281s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 1.3828277587890625e-05s
INFO | --- Analysis for prospects-and-trends-gnoss took 7.0249786376953125s
Availability | SPARQL endpoint availability check for provenanceweb took 0.0555875301361084s
Availability | VoID file availability check for provenanceweb took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.28566884994506836s
Reputation | Calculation of the PageRank for provenanceweb took 0.020613670349121094s
Interlinking | Calculation of Degree of Connection for provenanceweb took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 7.2479248046875e-05s
Believability | Calculation of trust value for provenanceweb took 7.3909759521484375e-06s
INFO | --- Analysis for provenanceweb took 50.53452134132385s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 5.7697296142578125e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.2557675838470459s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.020140886306762695s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.0001049041748046875s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 1.3113021850585938e-05s
INFO | --- Analysis for proyectoapadrina took 7.4353814125061035s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 25.480937242507935s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0008397102355957031s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.26191282272338867s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.02057194709777832s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 3.886222839355469e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 5.245208740234375e-06s
INFO | --- Analysis for pscs-catalogue took 126.32063484191895s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 4.673004150390625e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0006425380706787109s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.2664377689361572s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.020251989364624023s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.081031799316406e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 7.152557373046875e-06s
INFO | --- Analysis for psh-subject-headings took 2.979217767715454s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 4.38690185546875e-05s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.26577210426330566s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.020497798919677734s
Interlinking | Calculation of Degree of Connection for Public Record Office Victoria Semantic Wiki took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Public Record Office Victoria Semantic Wiki took 0.0008554458618164062s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 3.314018249511719e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 7.62939453125e-06s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 3.395526647567749s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 0.7565577030181885s
Availability | VoID file availability check for Public Spending in Greece took 0.0006499290466308594s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.2631187438964844s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.02005481719970703s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 8.034706115722656e-05s
Believability | Calculation of trust value for Public Spending in Greece took 7.152557373046875e-06s
INFO | --- Analysis for public-spending-in-greece took 8.276470184326172s
Availability | SPARQL endpoint availability check for Publications of Charles University in Prague took 4.1961669921875e-05s
Availability | VoID file availability check for Publications of Charles University in Prague took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.2709159851074219s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.020450353622436523s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 2.86102294921875e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 8.106231689453125e-06s
INFO | --- Analysis for publications-of-charles-university-in-prague took 2.8958215713500977s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 4.0531158447265625e-05s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.24637150764465332s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.0201568603515625s
Interlinking | Calculation of Degree of Connection for Publikace Univerzity Karlovy v Praze took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Publikace Univerzity Karlovy v Praze took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 2.8371810913085938e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 8.344650268554688e-06s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 2.885918617248535s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 7.43865966796875e-05s
Availability | VoID file availability check for qualitywebdata.org took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 0.2564725875854492s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.020432233810424805s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 3.075599670410156e-05s
Believability | Calculation of trust value for qualitywebdata.org took 7.152557373046875e-06s
INFO | --- Analysis for qualitywebdata-org took 2.886486053466797s
Availability | SPARQL endpoint availability check for Quotations Book took 4.220008850097656e-05s
Availability | VoID file availability check for Quotations Book took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Quotations Book took 0.24869871139526367s
Reputation | Calculation of the PageRank for Quotations Book took 0.020215511322021484s
Interlinking | Calculation of Degree of Connection for Quotations Book took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Quotations Book took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 2.8371810913085938e-05s
Believability | Calculation of trust value for Quotations Book took 7.3909759521484375e-06s
INFO | --- Analysis for quotations_book took 2.8360390663146973s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.27086544036865234s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020348310470581055s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 2.7894973754882812e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 6.67572021484375e-06s
INFO | --- Analysis for r4r took 2.8667595386505127s
Availability | SPARQL endpoint availability check for Rådata nå! took 16.6129150390625s
Availability | VoID file availability check for Rådata nå! took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.25408291816711426s
Reputation | Calculation of the PageRank for Rådata nå! took 0.02065253257751465s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 8.678436279296875e-05s
Believability | Calculation of trust value for Rådata nå! took 8.58306884765625e-06s
INFO | --- Analysis for radatana took 20.90251636505127s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 4.315376281738281e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0007238388061523438s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.35068249702453613s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.020651817321777344s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 4.076957702636719e-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 17.543086290359497s
Availability | SPARQL endpoint availability check for Raphael Research Resource took 4.1484832763671875e-05s
Availability | VoID file availability check for Raphael Research Resource took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Raphael Research Resource took 0.27839016914367676s
Reputation | Calculation of the PageRank for Raphael Research Resource took 0.0205686092376709s
Interlinking | Calculation of Degree of Connection for Raphael Research Resource took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Raphael Research Resource took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Raphael Research Resource took 3.0279159545898438e-05s
Believability | Calculation of trust value for Raphael Research Resource took 8.106231689453125e-06s
INFO | --- Analysis for raphaelresearchresource took 3.0203683376312256s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 12.132737636566162s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0006048679351806641s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.2740607261657715s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.02065730094909668s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.24249267578125e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 9.059906005859375e-06s
INFO | --- Analysis for ravensburg-local-shopping-graph took 27.134131908416748s
Availability | SPARQL endpoint availability check for RCAHMS Archaeological Objects Thesaurus took 8.630752563476562e-05s
Availability | VoID file availability check for RCAHMS Archaeological Objects Thesaurus took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for RCAHMS Archaeological Objects Thesaurus took 0.2628285884857178s
Reputation | Calculation of the PageRank for RCAHMS Archaeological Objects Thesaurus took 0.02040553092956543s
Interlinking | Calculation of Degree of Connection for RCAHMS Archaeological Objects Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RCAHMS Archaeological Objects Thesaurus took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for RCAHMS Archaeological Objects Thesaurus took 3.147125244140625e-05s
Believability | Calculation of trust value for RCAHMS Archaeological Objects Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for rcahms-archaeological-objects-thesaurus took 2.931274890899658s
Availability | SPARQL endpoint availability check for RCAHMS Maritime Craft Thesaurus took 4.2438507080078125e-05s
Availability | VoID file availability check for RCAHMS Maritime Craft Thesaurus took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for RCAHMS Maritime Craft Thesaurus took 0.2906229496002197s
Reputation | Calculation of the PageRank for RCAHMS Maritime Craft Thesaurus took 0.02043294906616211s
Interlinking | Calculation of Degree of Connection for RCAHMS Maritime Craft Thesaurus took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for RCAHMS Maritime Craft Thesaurus took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for RCAHMS Maritime Craft Thesaurus took 3.147125244140625e-05s
Believability | Calculation of trust value for RCAHMS Maritime Craft Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for rcahms-maritime-craft-thesaurus took 2.819554328918457s
Availability | SPARQL endpoint availability check for RCAHMS Monument Types Thesaurus took 4.3392181396484375e-05s
Availability | VoID file availability check for RCAHMS Monument Types Thesaurus took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for RCAHMS Monument Types Thesaurus took 0.25441646575927734s
Reputation | Calculation of the PageRank for RCAHMS Monument Types Thesaurus took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for RCAHMS Monument Types Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RCAHMS Monument Types Thesaurus took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for RCAHMS Monument Types Thesaurus took 2.956390380859375e-05s
Believability | Calculation of trust value for RCAHMS Monument Types Thesaurus took 9.298324584960938e-06s
INFO | --- Analysis for rcahms-monument-types-thesaurus took 2.8597500324249268s
Availability | SPARQL endpoint availability check for RCAHMW Monument Types Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for RCAHMW Monument Types Thesaurus took 0.0002913475036621094s
Completeness | Calculation of interlinking completeness for RCAHMW Monument Types Thesaurus took 0.26822876930236816s
Reputation | Calculation of the PageRank for RCAHMW Monument Types Thesaurus took 0.020363330841064453s
Interlinking | Calculation of Degree of Connection for RCAHMW Monument Types Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RCAHMW Monument Types Thesaurus took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for RCAHMW Monument Types Thesaurus took 2.956390380859375e-05s
Believability | Calculation of trust value for RCAHMW Monument Types Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for rcahmw-monument-types-thesaurus took 2.9683260917663574s
Availability | SPARQL endpoint availability check for RCAHMW Periods List took 4.172325134277344e-05s
Availability | VoID file availability check for RCAHMW Periods List took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for RCAHMW Periods List took 0.25580787658691406s
Reputation | Calculation of the PageRank for RCAHMW Periods List took 0.020830392837524414s
Interlinking | Calculation of Degree of Connection for RCAHMW Periods List took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RCAHMW Periods List took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for RCAHMW Periods List took 4.792213439941406e-05s
Believability | Calculation of trust value for RCAHMW Periods List took 7.152557373046875e-06s
INFO | --- Analysis for rcahmw-periods-list took 2.892669200897217s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 4.38690185546875e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.2511162757873535s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.020725488662719727s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.7738037109375e-05s
Believability | Calculation of trust value for RDF Book Mashup took 8.58306884765625e-06s
INFO | --- Analysis for rdf-book-mashup took 3.053891181945801s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 4.363059997558594e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.24405312538146973s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.020328044891357422s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 0.00010275840759277344s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 7.62939453125e-06s
INFO | --- Analysis for rdfize-lastfm took 2.397947072982788s
Availability | SPARQL endpoint availability check for RDFLicense took 260.5713486671448s
Availability | VoID file availability check for RDFLicense took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.31359410285949707s
Reputation | Calculation of the PageRank for RDFLicense took 0.020630359649658203s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 3.886222839355469e-05s
Believability | Calculation of trust value for RDFLicense took 8.344650268554688e-06s
INFO | --- Analysis for rdflicense took 535.4995772838593s
Availability | SPARQL endpoint availability check for RDFohloh took 5.078315734863281e-05s
Availability | VoID file availability check for RDFohloh took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.2879753112792969s
Reputation | Calculation of the PageRank for RDFohloh took 0.02091836929321289s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 9.1552734375e-05s
Believability | Calculation of trust value for RDFohloh took 6.4373016357421875e-06s
INFO | --- Analysis for rdfohloh took 7.562190055847168s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.6021356582641602s
Availability | VoID file availability check for Reactome RDF took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.24657583236694336s
Reputation | Calculation of the PageRank for Reactome RDF took 0.020534276962280273s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.790855407714844e-05s
Believability | Calculation of trust value for Reactome RDF took 8.106231689453125e-06s
INFO | --- Analysis for reactome-rdf took 4.561553955078125s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 0.10010480880737305s
Availability | VoID file availability check for Rechtspraak.nl took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.259169340133667s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.02042412757873535s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 0.00010609626770019531s
Believability | Calculation of trust value for Rechtspraak.nl took 6.4373016357421875e-06s
INFO | --- Analysis for rechtspraak took 3.012868642807007s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 6.890296936035156e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0007135868072509766s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.2378861904144287s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.020668745040893555s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0008528232574462891s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 9.703636169433594e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 8.58306884765625e-06s
INFO | --- Analysis for red-uno-internacional-santillana took 6.977981328964233s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.05049419403076172s
Availability | VoID file availability check for reference.data.gov.uk took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.26229023933410645s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.020369529724121094s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.00015282630920410156s
Believability | Calculation of trust value for reference.data.gov.uk took 5.9604644775390625e-06s
INFO | --- Analysis for reference-data-gov-uk took 2.5027313232421875s
Availability | SPARQL endpoint availability check for Regiony took 4.267692565917969e-05s
Availability | VoID file availability check for Regiony took 0.0002989768981933594s
Completeness | Calculation of interlinking completeness for Regiony took 0.2644309997558594s
Reputation | Calculation of the PageRank for Regiony took 0.020465373992919922s
Interlinking | Calculation of Degree of Connection for Regiony took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Regiony took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Regiony took 3.0040740966796875e-05s
Believability | Calculation of trust value for Regiony took 6.67572021484375e-06s
INFO | --- Analysis for regiony took 2.9714162349700928s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.48734617233276367s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0006105899810791016s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 1.1758568286895752s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 0.8792726993560791s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.5438578128814697s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.7870025634765625s
Versatility | Languages check for Repository for Linked Open Archival Data took 18.604928016662598s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 2.4655981063842773s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.5434830188751221s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.5716185569763184s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.3911585807800293s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.19376921653747559s
License | MR license check for Repository for Linked Open Archival Data took 0.921008825302124s
License | HR license check for Repository for Linked Open Archival Data took 9.058876037597656s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.13840532302856445s
Understandability | Number of label check for Repository for Linked Open Archival Data took 1.961099624633789s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.7885730266571045s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.15091753005981445s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.23054003715515137s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.2598538398742676s
Performance | Throughput check for Repository for Linked Open Archival Data took 10.709777593612671s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 0.000110626220703125s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.16640067100524902s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.1822528839111328s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.6452786922454834s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.2802155017852783s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.22815752029418945s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.620814323425293s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.27289700508117676s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 2.9249536991119385s
Interoperability | New vocabularies check for Repository for Linked Open Archival Data took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Repository for Linked Open Archival Data took 0.19538426399230957s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.18878984451293945s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.09955286979675293s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 1.4113693237304688s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.028769969940185547s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.028229236602783203s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.2988393306732178s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 1.9965126514434814s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.18130850791931152s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.7421064376831055s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.2962243556976318s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 3.080317735671997s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.03042888641357422s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.3009321689605713s
Security | Sign check for Repository for Linked Open Archival Data took 0.49577784538269043s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 1260.4505968093872s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 1.1528911590576172s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.020922183990478516s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 4.4345855712890625e-05s
Interoperability | Check the re-using of existing vocabs for Repository for Linked Open Archival Data took 1.430511474609375e-06s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 8.106231689453125e-06s
INFO | --- Analysis for reload took 1399.47177195549s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 1.8785712718963623s
Availability | VoID file availability check for Renewable Energy Generators took 0.0004265308380126953s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.29355883598327637s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.020639419555664062s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.57763671875e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 5.9604644775390625e-06s
INFO | --- Analysis for renewable_energy_generators took 11.80612826347351s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.05890297889709473s
Availability | VoID file availability check for research.data.gov.uk took 0.0002086162567138672s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.26731276512145996s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.021550416946411133s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 0.00010561943054199219s
Believability | Calculation of trust value for research.data.gov.uk took 6.4373016357421875e-06s
INFO | --- Analysis for research-data-gov-uk took 3.7750096321105957s
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.00023746490478515625s
Completeness | Calculation of interlinking completeness for Research object in Agricolture and Food of the University of Naples took 0.26020193099975586s
Reputation | Calculation of the PageRank for Research object in Agricolture and Food of the University of Naples took 0.02049875259399414s
Interlinking | Calculation of Degree of Connection for Research object in Agricolture and Food of the University of Naples took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Research object in Agricolture and Food of the University of Naples took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Research object in Agricolture and Food of the University of Naples took 3.0279159545898438e-05s
Believability | Calculation of trust value for Research object in Agricolture and Food of the University of Naples took 7.3909759521484375e-06s
INFO | --- Analysis for research-object-in-agricolture-and-food-of-the-university-of-naples took 3.298248291015625s
Availability | SPARQL endpoint availability check for Restaurantes took 4.172325134277344e-05s
Availability | VoID file availability check for Restaurantes took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Restaurantes took 0.2555665969848633s
Reputation | Calculation of the PageRank for Restaurantes took 0.020778656005859375s
Interlinking | Calculation of Degree of Connection for Restaurantes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Restaurantes took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Restaurantes took 3.075599670410156e-05s
Believability | Calculation of trust value for Restaurantes took 7.3909759521484375e-06s
INFO | --- Analysis for restaurantes-zaragoza took 2.8561627864837646s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 4.363059997558594e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.25734519958496094s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.020928382873535156s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 6.556510925292969e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 7.62939453125e-06s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 5.463316917419434s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.27275943756103516s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.00021958351135253906s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.2659139633178711s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.021093368530273438s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00012230873107910156s
Believability | Calculation of trust value for Revyu.com - Review Anything took 6.67572021484375e-06s
INFO | --- Analysis for revyu took 2.687021493911743s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 4.291534423828125e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0004291534423828125s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.2680020332336426s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.020435810089111328s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 4.601478576660156e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 5.9604644775390625e-06s
INFO | --- Analysis for riese took 2.3870999813079834s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection Data took 4.00543212890625e-05s
Availability | VoID file availability check for Rijksmuseum Collection Data took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection Data took 0.25618481636047363s
Reputation | Calculation of the PageRank for Rijksmuseum Collection Data took 0.020603418350219727s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection Data took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection Data took 3.0040740966796875e-05s
Believability | Calculation of trust value for Rijksmuseum Collection Data took 7.3909759521484375e-06s
INFO | --- Analysis for rijksmuseum took 2.8696529865264893s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 1.065972089767456s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0007243156433105469s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.27109837532043457s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.020502090454101562s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 4.291534423828125e-05s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 9.298324584960938e-06s
INFO | --- Analysis for rism took 4.041978120803833s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.18630456924438477s
Availability | VoID file availability check for RISM Authority data took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.282055139541626s
Reputation | Calculation of the PageRank for RISM Authority data took 0.020668506622314453s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 4.792213439941406e-05s
Believability | Calculation of trust value for RISM Authority data took 7.152557373046875e-06s
INFO | --- Analysis for rism-authorities took 3.213047981262207s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.053246259689331055s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00042319297790527344s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.2664151191711426s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.02033686637878418s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0002372264862060547s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-acm took 2.427412509918213s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.03575944900512695s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.00034308433532714844s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.2541310787200928s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.02056097984313965s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.00013756752014160156s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-budapest took 2.4569172859191895s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.04588747024536133s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.28325605392456055s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.020596742630004883s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.00019741058349609375s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-citeseer took 2.506791353225708s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.03181338310241699s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.270618200302124s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.021112442016601562s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00017070770263671875s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-cordis took 2.4453797340393066s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.05403399467468262s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.2615635395050049s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.020670652389526367s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.0001595020294189453s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-courseware took 2.54699969291687s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.03888821601867676s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.24498581886291504s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.02105545997619629s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 5.1021575927734375e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-crime took 2.4334824085235596s
Availability | SPARQL endpoint availability check for crm took 4.124641418457031e-05s
Availability | VoID file availability check for crm took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for crm took 0.27453041076660156s
Reputation | Calculation of the PageRank for crm took 0.02052140235900879s
Interlinking | Calculation of Degree of Connection for crm took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for crm took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for crm took 3.266334533691406e-05s
Believability | Calculation of trust value for crm took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-crm took 2.925191640853882s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.04286932945251465s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.2644786834716797s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.02078533172607422s
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.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00012731552124023438s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-curriculum took 2.4779183864593506s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.04588937759399414s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.27518558502197266s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.020801782608032227s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 6.031990051269531e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.4635486602783203s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.05488228797912598s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0004172325134277344s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.2665987014770508s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.02060413360595703s
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.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.00024890899658203125s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-dblp took 2.497069835662842s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.04026937484741211s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.0004267692565917969s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.25587916374206543s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.020498037338256836s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.891654968261719e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-deepblue took 2.428027629852295s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.04566001892089844s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0002200603485107422s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.2726402282714844s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.02051687240600586s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.822845458984375e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-deploy took 2.5416486263275146s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.041321754455566406s
Availability | VoID file availability check for digitaleconomy took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.27215147018432617s
Reputation | Calculation of the PageRank for digitaleconomy took 0.020697832107543945s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 3.24249267578125e-05s
Believability | Calculation of trust value for digitaleconomy took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.5527408123016357s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.041886329650878906s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.2709653377532959s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.02077007293701172s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.00014638900756835938s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 1.33514404296875e-05s
INFO | --- Analysis for rkb-explorer-dotac took 2.4479966163635254s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.051046133041381836s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.3245532512664795s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020410537719726562s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.76837158203125e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-ecs took 2.9817633628845215s
Availability | SPARQL endpoint availability check for enaktingpsi took 4.2438507080078125e-05s
Availability | VoID file availability check for enaktingpsi took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for enaktingpsi took 0.25984930992126465s
Reputation | Calculation of the PageRank for enaktingpsi took 0.021060466766357422s
Interlinking | Calculation of Degree of Connection for enaktingpsi took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for enaktingpsi took 0.0008327960968017578s
Interlinking | Calculation of Clustering coefficient for enaktingpsi took 3.3855438232421875e-05s
Believability | Calculation of trust value for enaktingpsi took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-enaktingpsi took 2.886497735977173s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.03883504867553711s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.2658061981201172s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.020572423934936523s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00020623207092285156s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-eprints took 2.4403789043426514s
Availability | SPARQL endpoint availability check for epsrc took 0.037317752838134766s
Availability | VoID file availability check for epsrc took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for epsrc took 0.26125550270080566s
Reputation | Calculation of the PageRank for epsrc took 0.020833969116210938s
Interlinking | Calculation of Degree of Connection for epsrc took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for epsrc took 7.128715515136719e-05s
Believability | Calculation of trust value for epsrc took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-epsrc took 2.455132246017456s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.04160499572753906s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.26921629905700684s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.020965099334716797s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 8.273124694824219e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-era took 2.502525806427002s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.04800605773925781s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.2674260139465332s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.027674198150634766s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0014116764068603516s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00014328956604003906s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-eurecom took 2.543081283569336s
Availability | SPARQL endpoint availability check for rkb-explorer-foreign took 4.172325134277344e-05s
Availability | VoID file availability check for rkb-explorer-foreign took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for rkb-explorer-foreign took 0.29606008529663086s
Reputation | Calculation of the PageRank for rkb-explorer-foreign took 0.021119117736816406s
Interlinking | Calculation of Degree of Connection for rkb-explorer-foreign took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for rkb-explorer-foreign took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for rkb-explorer-foreign took 3.24249267578125e-05s
Believability | Calculation of trust value for rkb-explorer-foreign took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-foreign took 3.147977590560913s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.04808616638183594s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.2554664611816406s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.020415782928466797s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 9.34600830078125e-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.4809532165527344s
Availability | SPARQL endpoint availability check for fun took 0.04270339012145996s
Availability | VoID file availability check for fun took 0.0004153251647949219s
Completeness | Calculation of interlinking completeness for fun took 0.270432710647583s
Reputation | Calculation of the PageRank for fun took 0.020332813262939453s
Interlinking | Calculation of Degree of Connection for fun took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for fun took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for fun took 7.796287536621094e-05s
Believability | Calculation of trust value for fun took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-fun took 2.499159097671509s
Availability | SPARQL endpoint availability check for gdlc took 0.04955005645751953s
Availability | VoID file availability check for gdlc took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for gdlc took 0.2904655933380127s
Reputation | Calculation of the PageRank for gdlc took 0.02027297019958496s
Interlinking | Calculation of Degree of Connection for gdlc took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for gdlc took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for gdlc took 7.128715515136719e-05s
Believability | Calculation of trust value for gdlc took 9.059906005859375e-06s
INFO | --- Analysis for rkb-explorer-gdlc took 2.4845523834228516s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.03898811340332031s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.26289892196655273s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.02042078971862793s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.0001366138458251953s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-ibm took 2.503288507461548s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.05760312080383301s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.2799806594848633s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.020296335220336914s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.0001366138458251953s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 9.059906005859375e-06s
INFO | --- Analysis for rkb-explorer-ieee took 2.473879337310791s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.04163336753845215s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.2593677043914795s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0206143856048584s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00014162063598632812s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-irit took 2.4898412227630615s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.052269697189331055s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.25446319580078125s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.02111077308654785s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.67572021484375e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-italy took 7.496011972427368s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.047994136810302734s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.3528318405151367s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.020731687545776367s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.724761962890625e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-jisc took 2.650925397872925s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.043314456939697266s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.2739534378051758s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.5299530029296875e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-kaunas took 2.5266358852386475s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.052085161209106445s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.2727200984954834s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.020595550537109375s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00016546249389648438s
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.617063045501709s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.04300260543823242s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.268343448638916s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.02032017707824707s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.0001518726348876953s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 9.059906005859375e-06s
INFO | --- Analysis for rkb-explorer-laas took 2.4938483238220215s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.04389524459838867s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.26520729064941406s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.02019953727722168s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.198883056640625e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-lisbon took 2.465932607650757s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.05050945281982422s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.26172447204589844s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.0001697540283203125s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 2.444218158721924s
Availability | SPARQL endpoint availability check for notube took 0.0428621768951416s
Availability | VoID file availability check for notube took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for notube took 0.275709867477417s
Reputation | Calculation of the PageRank for notube took 0.02036762237548828s
Interlinking | Calculation of Degree of Connection for notube took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for notube took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for notube took 4.100799560546875e-05s
Believability | Calculation of trust value for notube took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-notube took 2.416046380996704s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.040708303451538086s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.26674962043762207s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.02063751220703125s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.0001404285430908203s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-nsf took 2.4534547328948975s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.049401044845581055s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00048828125s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.25823116302490234s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.020251035690307617s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0001652240753173828s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-oai took 2.454223155975342s
Availability | SPARQL endpoint availability check for OpenCyc (RKBExplorer) took 4.3392181396484375e-05s
Availability | VoID file availability check for OpenCyc (RKBExplorer) took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for OpenCyc (RKBExplorer) took 0.26474547386169434s
Reputation | Calculation of the PageRank for OpenCyc (RKBExplorer) took 0.020444154739379883s
Interlinking | Calculation of Degree of Connection for OpenCyc (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenCyc (RKBExplorer) took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for OpenCyc (RKBExplorer) took 2.7894973754882812e-05s
Believability | Calculation of trust value for OpenCyc (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-opencyc took 2.8428027629852295s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.046143531799316406s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.2671236991882324s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.020210981369018555s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0008542537689208984s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 9.584426879882812e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 9.059906005859375e-06s
INFO | --- Analysis for rkb-explorer-os took 2.4724886417388916s
Availability | SPARQL endpoint availability check for photos took 0.050627708435058594s
Availability | VoID file availability check for photos took 0.00034165382385253906s
Completeness | Calculation of interlinking completeness for photos took 0.26389002799987793s
Reputation | Calculation of the PageRank for photos took 0.02059650421142578s
Interlinking | Calculation of Degree of Connection for photos took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for photos took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for photos took 8.153915405273438e-05s
Believability | Calculation of trust value for photos took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-photos took 2.489105701446533s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.047063350677490234s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.0006773471832275391s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.2542262077331543s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.020535707473754883s
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.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00011420249938964844s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 1.3113021850585938e-05s
INFO | --- Analysis for rkb-explorer-pisa took 2.451674699783325s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0516810417175293s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.2545020580291748s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.020566463470458984s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00019097328186035156s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.4875731468200684s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.05197763442993164s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0004210472106933594s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.2683708667755127s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.020787477493286133s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00016045570373535156s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 6.198883056640625e-06s
INFO | --- Analysis for rkb-explorer-resex took 2.5727226734161377s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.04533815383911133s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0004246234893798828s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.27099084854125977s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020566940307617188s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.369850158691406e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-risks took 2.5286967754364014s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.05485081672668457s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.277240514755249s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.02050018310546875s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00012254714965820312s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-roma took 2.4688079357147217s
Availability | SPARQL endpoint availability check for roni took 0.05141496658325195s
Availability | VoID file availability check for roni took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for roni took 0.2522463798522949s
Reputation | Calculation of the PageRank for roni took 0.02066349983215332s
Interlinking | Calculation of Degree of Connection for roni took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for roni took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for roni took 3.147125244140625e-05s
Believability | Calculation of trust value for roni took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-roni took 2.4903995990753174s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.07097959518432617s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.25629711151123047s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.020702362060546875s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0002319812774658203s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-southampton took 2.5219991207122803s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.05300164222717285s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.0003674030303955078s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.26776623725891113s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.020732879638671875s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0008220672607421875s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00013113021850585938s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 9.5367431640625e-06s
INFO | --- Analysis for rkb-explorer-ulm took 2.4626269340515137s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.047379255294799805s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.0004248619079589844s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.29323434829711914s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.020580768585205078s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 9.942054748535156e-05s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 6.198883056640625e-06s
INFO | --- Analysis for rkb-explorer-unlocode took 2.4996612071990967s
Availability | SPARQL endpoint availability check for webconf took 0.06203031539916992s
Availability | VoID file availability check for webconf took 0.001071929931640625s
Completeness | Calculation of interlinking completeness for webconf took 0.3037700653076172s
Reputation | Calculation of the PageRank for webconf took 0.020473957061767578s
Interlinking | Calculation of Degree of Connection for webconf took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00010657310485839844s
Believability | Calculation of trust value for webconf took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-webconf took 12.796623229980469s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.03620791435241699s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.0004353523254394531s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.26277613639831543s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.020662307739257812s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 7.414817810058594e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-webscience took 2.546546459197998s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.03881406784057617s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.0006346702575683594s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.2530405521392822s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.02047443389892578s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.00020837783813476562s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-wiki took 2.4867939949035645s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.03748345375061035s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.25120115280151367s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.020389080047607422s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.179115295410156e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-wordnet took 2.4465675354003906s
Availability | SPARQL endpoint availability check for RKB Explorer Data took 4.172325134277344e-05s
Availability | VoID file availability check for RKB Explorer Data took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for RKB Explorer Data took 0.24544787406921387s
Reputation | Calculation of the PageRank for RKB Explorer Data took 0.02056145668029785s
Interlinking | Calculation of Degree of Connection for RKB Explorer Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for RKB Explorer Data took 0.0008683204650878906s
Interlinking | Calculation of Clustering coefficient for RKB Explorer Data took 3.933906555175781e-05s
Believability | Calculation of trust value for RKB Explorer Data took 8.344650268554688e-06s
INFO | --- Analysis for rkb_explorer_data took 2.943742275238037s
Availability | SPARQL endpoint availability check for The Rosetta Project took 4.267692565917969e-05s
Availability | VoID file availability check for The Rosetta Project took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for The Rosetta Project took 0.26421451568603516s
Reputation | Calculation of the PageRank for The Rosetta Project took 0.020618677139282227s
Interlinking | Calculation of Degree of Connection for The Rosetta Project took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Rosetta Project took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for The Rosetta Project took 3.0994415283203125e-05s
Believability | Calculation of trust value for The Rosetta Project took 8.106231689453125e-06s
INFO | --- Analysis for rosetta-project took 2.8818557262420654s
Availability | SPARQL endpoint availability check for Rpm Find took 4.2438507080078125e-05s
Availability | VoID file availability check for Rpm Find took 0.0002956390380859375s
Completeness | Calculation of interlinking completeness for Rpm Find took 0.2718513011932373s
Reputation | Calculation of the PageRank for Rpm Find took 0.02048468589782715s
Interlinking | Calculation of Degree of Connection for Rpm Find took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Rpm Find took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Rpm Find took 3.147125244140625e-05s
Believability | Calculation of trust value for Rpm Find took 8.821487426757812e-06s
INFO | --- Analysis for rpm_find took 3.0814223289489746s
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.0005621910095214844s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.27057576179504395s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.02075672149658203s
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.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 6.890296936035156e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 8.58306884765625e-06s
INFO | --- Analysis for rss-500-nif-ner-corpus took 4.040063858032227s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 4.2438507080078125e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0006132125854492188s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.2658202648162842s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.020720243453979492s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 7.581710815429688e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 5.7220458984375e-06s
INFO | --- Analysis for rubentaelman took 4.021368503570557s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 4.4345855712890625e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.2915492057800293s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.0205838680267334s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.225440979003906e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 7.3909759521484375e-06s
INFO | --- Analysis for rubenverborgh took 3.269040107727051s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 392.2860019207001s
Availability | VoID file availability check for Russian Universities Specialities took 0.0006160736083984375s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.30248570442199707s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.020828723907470703s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 5.245208740234375e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 8.106231689453125e-06s
INFO | --- Analysis for russian-universities-specialities took 677.4442591667175s
Availability | SPARQL endpoint availability check for RuThes Cloud took 4.1961669921875e-05s
Availability | VoID file availability check for RuThes Cloud took 0.00033593177795410156s
Completeness | Calculation of interlinking completeness for RuThes Cloud took 0.7138564586639404s
Reputation | Calculation of the PageRank for RuThes Cloud took 0.021057844161987305s
Interlinking | Calculation of Degree of Connection for RuThes Cloud took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for RuThes Cloud took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for RuThes Cloud took 3.314018249511719e-05s
Believability | Calculation of trust value for RuThes Cloud took 1.33514404296875e-05s
INFO | --- Analysis for ruthes took 5.081118822097778s
Availability | SPARQL endpoint availability check for RxNorm took 5.650520324707031e-05s
Availability | VoID file availability check for RxNorm took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for RxNorm took 0.28110623359680176s
Reputation | Calculation of the PageRank for RxNorm took 0.020874500274658203s
Interlinking | Calculation of Degree of Connection for RxNorm took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RxNorm took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for RxNorm took 3.457069396972656e-05s
Believability | Calculation of trust value for RxNorm took 1.430511474609375e-05s
INFO | --- Analysis for rxnorm took 3.808504581451416s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 3.6144332885742188s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.27335190773010254s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.020801544189453125s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 3.218650817871094e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 7.3909759521484375e-06s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 8.08149790763855s
Availability | SPARQL endpoint availability check for SALDO took 4.220008850097656e-05s
Availability | VoID file availability check for SALDO took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for SALDO took 0.28733110427856445s
Reputation | Calculation of the PageRank for SALDO took 0.02088618278503418s
Interlinking | Calculation of Degree of Connection for SALDO took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for SALDO took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for SALDO took 3.266334533691406e-05s
Believability | Calculation of trust value for SALDO took 8.106231689453125e-06s
INFO | --- Analysis for saldo took 2.8383796215057373s
Availability | SPARQL endpoint availability check for SALDO-RDF took 2.31428599357605s
Availability | VoID file availability check for SALDO-RDF took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.2505378723144531s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.020714282989501953s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.528594970703125e-05s
Believability | Calculation of trust value for SALDO-RDF took 8.344650268554688e-06s
INFO | --- Analysis for saldo-rdf took 6.760969877243042s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.6447391510009766s
Availability | VoID file availability check for SALDOM-RDF took 0.00037217140197753906s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.28101682662963867s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.02069854736328125s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.457069396972656e-05s
Believability | Calculation of trust value for SALDOM-RDF took 9.059906005859375e-06s
INFO | --- Analysis for saldom-rdf took 4.778605699539185s
Availability | SPARQL endpoint availability check for sameAs.org took 5.125999450683594e-05s
Availability | VoID file availability check for sameAs.org took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for sameAs.org took 0.2604942321777344s
Reputation | Calculation of the PageRank for sameAs.org took 0.020720481872558594s
Interlinking | Calculation of Degree of Connection for sameAs.org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for sameAs.org took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for sameAs.org took 3.0517578125e-05s
Believability | Calculation of trust value for sameAs.org took 7.867813110351562e-06s
INFO | --- Analysis for sameas-org took 2.8374359607696533s
Availability | SPARQL endpoint availability check for sandrart.net took 5.221366882324219e-05s
Availability | VoID file availability check for sandrart.net took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.26329612731933594s
Reputation | Calculation of the PageRank for sandrart.net took 0.020616769790649414s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 7.200241088867188e-05s
Believability | Calculation of trust value for sandrart.net took 7.62939453125e-06s
INFO | --- Analysis for sandrart-net took 3.553316831588745s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 1.84084153175354s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0007281303405761719s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.2675442695617676s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.02038741111755371s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 3.123283386230469e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 8.344650268554688e-06s
INFO | --- Analysis for sanskrit-english-lexicon took 6.71366286277771s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 263.91113352775574s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0008287429809570312s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.322620153427124s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.021209001541137695s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 4.172325134277344e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 8.106231689453125e-06s
INFO | --- Analysis for santillana_guide_dataset took 670.6929194927216s
Availability | SPARQL endpoint availability check for schema.org took 4.220008850097656e-05s
Availability | VoID file availability check for schema.org took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for schema.org took 0.6888153553009033s
Reputation | Calculation of the PageRank for schema.org took 0.02105093002319336s
Interlinking | Calculation of Degree of Connection for schema.org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for schema.org took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for schema.org took 3.4809112548828125e-05s
Believability | Calculation of trust value for schema.org took 8.106231689453125e-06s
INFO | --- Analysis for schema-org took 4.697753667831421s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 2.1432037353515625s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.2582104206085205s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.020727157592773438s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.528594970703125e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 8.344650268554688e-06s
INFO | --- Analysis for schemapedia took 6.576104164123535s
Availability | SPARQL endpoint availability check for scholarlydata took 4.220008850097656e-05s
Availability | VoID file availability check for scholarlydata took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for scholarlydata took 0.28369736671447754s
Reputation | Calculation of the PageRank for scholarlydata took 0.02046990394592285s
Interlinking | Calculation of Degree of Connection for scholarlydata took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for scholarlydata took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for scholarlydata took 2.9325485229492188e-05s
Believability | Calculation of trust value for scholarlydata took 7.3909759521484375e-06s
INFO | --- Analysis for scholarlydata took 2.9678878784179688s
Availability | SPARQL endpoint availability check for Scholarometer took 6.914138793945312e-05s
Availability | VoID file availability check for Scholarometer took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.2633540630340576s
Reputation | Calculation of the PageRank for Scholarometer took 0.020460128784179688s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 8.96453857421875e-05s
Believability | Calculation of trust value for Scholarometer took 8.821487426757812e-06s
INFO | --- Analysis for scholarometer took 7.031456470489502s
Availability | SPARQL endpoint availability check for Science Commons took 4.172325134277344e-05s
Availability | VoID file availability check for Science Commons took 0.00031447410583496094s
Completeness | Calculation of interlinking completeness for Science Commons took 0.7316513061523438s
Reputation | Calculation of the PageRank for Science Commons took 0.020320892333984375s
Interlinking | Calculation of Degree of Connection for Science Commons took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Science Commons took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Science Commons took 2.9325485229492188e-05s
Believability | Calculation of trust value for Science Commons took 7.62939453125e-06s
INFO | --- Analysis for science_commons took 3.8609819412231445s
Availability | SPARQL endpoint availability check for ScienceWise took 4.1484832763671875e-05s
Availability | VoID file availability check for ScienceWise took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for ScienceWise took 0.24280905723571777s
Reputation | Calculation of the PageRank for ScienceWise took 0.02034926414489746s
Interlinking | Calculation of Degree of Connection for ScienceWise took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ScienceWise took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for ScienceWise took 2.8371810913085938e-05s
Believability | Calculation of trust value for ScienceWise took 7.152557373046875e-06s
INFO | --- Analysis for sciencewise took 2.9433276653289795s
Availability | SPARQL endpoint availability check for sears.com took 4.172325134277344e-05s
Availability | VoID file availability check for sears.com took 0.0006723403930664062s
Completeness | Calculation of interlinking completeness for sears.com took 0.266704797744751s
Reputation | Calculation of the PageRank for sears.com took 0.020884990692138672s
Interlinking | Calculation of Degree of Connection for sears.com took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for sears.com took 0.001108407974243164s
Interlinking | Calculation of Clustering coefficient for sears.com took 8.463859558105469e-05s
Believability | Calculation of trust value for sears.com took 7.62939453125e-06s
INFO | --- Analysis for sears took 4.348524570465088s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.08109831809997559s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.28070521354675293s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.020282745361328125s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.058547973632812e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 6.4373016357421875e-06s
INFO | --- Analysis for sec-rdfabout took 6.158896207809448s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.952547073364258s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.3780028820037842s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.020645618438720703s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 8.535385131835938e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 6.9141387939453125e-06s
INFO | --- Analysis for secold took 168.08222913742065s
Availability | SPARQL endpoint availability check for SEEK-AT-WD ICT tools for education - Web-Share took 4.6253204345703125e-05s
Availability | VoID file availability check for SEEK-AT-WD ICT tools for education - Web-Share took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for SEEK-AT-WD ICT tools for education - Web-Share took 0.267148494720459s
Reputation | Calculation of the PageRank for SEEK-AT-WD ICT tools for education - Web-Share took 0.020635604858398438s
Interlinking | Calculation of Degree of Connection for SEEK-AT-WD ICT tools for education - Web-Share took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SEEK-AT-WD ICT tools for education - Web-Share took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for SEEK-AT-WD ICT tools for education - Web-Share took 2.9325485229492188e-05s
Believability | Calculation of trust value for SEEK-AT-WD ICT tools for education - Web-Share took 6.4373016357421875e-06s
INFO | --- Analysis for seek-at-wd-ict-tools-for-education-web-share took 3.317354440689087s
Availability | SPARQL endpoint availability check for semanlink took 4.482269287109375e-05s
Availability | VoID file availability check for semanlink took 0.0006680488586425781s
Completeness | Calculation of interlinking completeness for semanlink took 0.36278748512268066s
Reputation | Calculation of the PageRank for semanlink took 0.027271747589111328s
Interlinking | Calculation of Degree of Connection for semanlink took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for semanlink took 0.001477956771850586s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.0001537799835205078s
Believability | Calculation of trust value for semanlink took 1.0967254638671875e-05s
INFO | --- Analysis for semanlink took 125.65355610847473s
Availability | SPARQL endpoint availability check for Semantic Library took 4.220008850097656e-05s
Availability | VoID file availability check for Semantic Library took 0.0002846717834472656s
Completeness | Calculation of interlinking completeness for Semantic Library took 0.2799105644226074s
Reputation | Calculation of the PageRank for Semantic Library took 0.020575284957885742s
Interlinking | Calculation of Degree of Connection for Semantic Library took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Semantic Library took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Semantic Library took 2.9325485229492188e-05s
Believability | Calculation of trust value for Semantic Library took 6.67572021484375e-06s
INFO | --- Analysis for semantic-library took 3.7423691749572754s
Availability | SPARQL endpoint availability check for Semantic Profiling Network took 5.5789947509765625e-05s
Availability | VoID file availability check for Semantic Profiling Network took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for Semantic Profiling Network took 0.25310492515563965s
Reputation | Calculation of the PageRank for Semantic Profiling Network took 0.020542621612548828s
Interlinking | Calculation of Degree of Connection for Semantic Profiling Network took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Semantic Profiling Network took 0.0007970333099365234s
Interlinking | Calculation of Clustering coefficient for Semantic Profiling Network took 3.170967102050781e-05s
Believability | Calculation of trust value for Semantic Profiling Network took 8.344650268554688e-06s
INFO | --- Analysis for semantic-profiling-network took 3.7014124393463135s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.05888795852661133s
Availability | VoID file availability check for Semantic Universe Data took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.25920796394348145s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.020700454711914062s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 3.266334533691406e-05s
Believability | Calculation of trust value for Semantic Universe Data took 7.867813110351562e-06s
INFO | --- Analysis for semantic-universe took 2.4367308616638184s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.166199684143066s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0006532669067382812s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.27187061309814453s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.020697832107543945s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00011849403381347656s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 7.152557373046875e-06s
INFO | --- Analysis for semantic-web-dog-food took 83.17839169502258s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 4.673004150390625e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.27192115783691406s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.020416736602783203s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.57763671875e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 7.867813110351562e-06s
INFO | --- Analysis for semantic-web-grundlagen took 3.376537561416626s
Availability | SPARQL endpoint availability check for semantic-web-journal took 4.4345855712890625e-05s
Availability | VoID file availability check for semantic-web-journal took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for semantic-web-journal took 0.2515099048614502s
Reputation | Calculation of the PageRank for semantic-web-journal took 0.020708322525024414s
Interlinking | Calculation of Degree of Connection for semantic-web-journal took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for semantic-web-journal took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for semantic-web-journal took 3.719329833984375e-05s
Believability | Calculation of trust value for semantic-web-journal took 8.821487426757812e-06s
INFO | --- Analysis for semantic-web-journal took 2.85024356842041s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 4.506111145019531e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0006146430969238281s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.6900765895843506s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.020705223083496094s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 9.036064147949219e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 6.67572021484375e-06s
INFO | --- Analysis for semantic-xbrl took 4.383390188217163s
Availability | SPARQL endpoint availability check for Semantic Bible took 5.435943603515625e-05s
Availability | VoID file availability check for Semantic Bible took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for Semantic Bible took 0.2711458206176758s
Reputation | Calculation of the PageRank for Semantic Bible took 0.020764589309692383s
Interlinking | Calculation of Degree of Connection for Semantic Bible took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Semantic Bible took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Semantic Bible took 3.218650817871094e-05s
Believability | Calculation of trust value for Semantic Bible took 8.58306884765625e-06s
INFO | --- Analysis for semantic_bible took 2.924712896347046s
Availability | SPARQL endpoint availability check for SemanticQuran took 6.129537582397461s
Availability | VoID file availability check for SemanticQuran took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for SemanticQuran took 0.2409954071044922s
Reputation | Calculation of the PageRank for SemanticQuran took 0.02072000503540039s
Interlinking | Calculation of Degree of Connection for SemanticQuran took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SemanticQuran took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for SemanticQuran took 7.295608520507812e-05s
Believability | Calculation of trust value for SemanticQuran took 6.9141387939453125e-06s
INFO | --- Analysis for semanticquran took 15.219595909118652s
Availability | SPARQL endpoint availability check for SemanticTweet took 4.38690185546875e-05s
Availability | VoID file availability check for SemanticTweet took 0.00033545494079589844s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.26068925857543945s
Reputation | Calculation of the PageRank for SemanticTweet took 0.020253658294677734s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.698204040527344e-05s
Believability | Calculation of trust value for SemanticTweet took 7.867813110351562e-06s
INFO | --- Analysis for semantictweet took 2.4517078399658203s
Availability | SPARQL endpoint availability check for semanticweb.org took 4.363059997558594e-05s
Availability | VoID file availability check for semanticweb.org took 0.0008733272552490234s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.2548344135284424s
Reputation | Calculation of the PageRank for semanticweb.org took 0.020366668701171875s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 7.796287536621094e-05s
Believability | Calculation of trust value for semanticweb.org took 8.106231689453125e-06s
INFO | --- Analysis for semanticweb-org took 22.616894960403442s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.0872189998626709s
Availability | VoID file availability check for Semantic CrunchBase took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.25409460067749023s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.020305871963500977s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0010008811950683594s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 8.606910705566406e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 7.3909759521484375e-06s
INFO | --- Analysis for semsol-crunchbase took 2.4314723014831543s
Availability | SPARQL endpoint availability check for Sensores de IntelliDomo took 4.076957702636719e-05s
Availability | VoID file availability check for Sensores de IntelliDomo took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Sensores de IntelliDomo took 0.2735588550567627s
Reputation | Calculation of the PageRank for Sensores de IntelliDomo took 0.02079010009765625s
Interlinking | Calculation of Degree of Connection for Sensores de IntelliDomo took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sensores de IntelliDomo took 0.0008654594421386719s
Interlinking | Calculation of Clustering coefficient for Sensores de IntelliDomo took 3.123283386230469e-05s
Believability | Calculation of trust value for Sensores de IntelliDomo took 8.106231689453125e-06s
INFO | --- Analysis for sensores-de-intellidomo took 2.864142656326294s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.28336000442504883s
Availability | VoID file availability check for SentimentWortschatz took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.2703380584716797s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.020435571670532227s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.649162292480469e-05s
Believability | Calculation of trust value for SentimentWortschatz took 7.3909759521484375e-06s
INFO | --- Analysis for sentiws took 3.5481326580047607s
Availability | SPARQL endpoint availability check for Serendipity took 10.825648784637451s
Availability | VoID file availability check for Serendipity took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for Serendipity took 0.27480006217956543s
Reputation | Calculation of the PageRank for Serendipity took 0.02026510238647461s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0009260177612304688s
Interlinking | Calculation of Clustering coefficient for Serendipity took 8.273124694824219e-05s
Believability | Calculation of trust value for Serendipity took 8.344650268554688e-06s
INFO | --- Analysis for serendipity took 18.644136905670166s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.17631793022155762s
Availability | VoID file availability check for Shoah victims? names took 0.049306392669677734s
Extra | Recovery of all triples for Shoah victims? names took 1.5965337753295898s
Performance | Total latancy measurement for Shoah victims? names took 0.8261733055114746s
Amount of data | Number of triples check for Shoah victims? names took 1.4728202819824219s
Interoperability | New terms check for Shoah victims? names took 1.7295167446136475s
Versatility | Languages check for Shoah victims? names took 36.04443717002869s
Interpretability | Number of blank nodes check for Shoah victims? names took 2.5223500728607178s
Security | Check HTTPS for Shoah victims? names took 0.5746235847473145s
Interpretability | RDF structures check for Shoah victims? names took 0.4816417694091797s
Versatility | Serialization formats check for Shoah victims? names took 0.31802940368652344s
Availability | RDF dump link check for Shoah victims? names took 0.21778059005737305s
License | MR license check for Shoah victims? names took 0.5073840618133545s
License | HR license check for Shoah victims? names took 10.781058073043823s
Amount of data | Number of property check for Shoah victims? names took 0.13800859451293945s
Understandability | Number of label check for Shoah victims? names took 1.7914350032806396s
Understandability | URI regex check for Shoah victims? names took 0.737830638885498s
Understandability | Vocabs check for Shoah victims? names took 0.2176656723022461s
Verifiability | Authors check for Shoah victims? names took 0.2639453411102295s
Verifiability | Publishers check for Shoah victims? names took 0.31717848777770996s
Performance | Throughput check for Shoah victims? names took 10.912153720855713s
Amount of data | Check the number of entities for Shoah victims? names took 9.512901306152344e-05s
Verifiability | Contribs. check for Shoah victims? names took 0.08115601539611816s
Interlinking | sameAs chians check for Shoah victims? names took 0.38551855087280273s
Interlinking | skos check for Shoah victims? names took 0.3959801197052002s
Interlinking | skos check for Shoah victims? names took 0.08753156661987305s
Timeliness | dataset update frequency check for Shoah victims? names took 0.4555509090423584s
Currency | Creation date check for Shoah victims? names took 0.16881322860717773s
Currency | Modification date check for Shoah victims? names took 0.22468161582946777s
Rep.Conc. | URIs length for Shoah victims? names took 2.9485223293304443s
Interoperability | New vocabularies check for Shoah victims? names took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.1909329891204834s
Accuracy | Check Functional Property for Shoah victims? names took 0.15720319747924805s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.17298102378845215s
Accuracy | Check Empty annotation labels for Shoah victims? names took 0.7792394161224365s
Accuracy | Check White space in annotation for Shoah victims? names took 0.028870820999145508s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.027770042419433594s
Consistency | Disjoint class check for Shoah victims? names took 0.2683703899383545s
Consistency | Check Misplaced properties for Shoah victims? names took 2.12308931350708s
Consistency | Misplaced classes for Shoah victims? names took 0.19524216651916504s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.7623107433319092s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.2799484729766846s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.14009428024292s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.02964186668395996s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.17881155014038086s
Security | Sign check for Shoah victims? names took 0.5516073703765869s
Availability | Check URIs Dereferenciability for Shoah victims? names took 1241.5848925113678s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.8864274024963379s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.020839691162109375s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 4.863739013671875e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 1.6689300537109375e-06s
Believability | Calculation of trust value for Shoah victims? names took 8.106231689453125e-06s
INFO | --- Analysis for shoah-victims-names took 1385.8705513477325s
Availability | SPARQL endpoint availability check for SIMILE Data Collection took 4.792213439941406e-05s
Availability | VoID file availability check for SIMILE Data Collection took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for SIMILE Data Collection took 0.6887388229370117s
Reputation | Calculation of the PageRank for SIMILE Data Collection took 0.020554304122924805s
Interlinking | Calculation of Degree of Connection for SIMILE Data Collection took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SIMILE Data Collection took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for SIMILE Data Collection took 3.1948089599609375e-05s
Believability | Calculation of trust value for SIMILE Data Collection took 7.3909759521484375e-06s
INFO | --- Analysis for simile_data_collection took 5.661328554153442s
Availability | SPARQL endpoint availability check for SIMPLE took 8.440017700195312e-05s
Availability | VoID file availability check for SIMPLE took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.27103614807128906s
Reputation | Calculation of the PageRank for SIMPLE took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0008485317230224609s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 4.0531158447265625e-05s
Believability | Calculation of trust value for SIMPLE took 6.67572021484375e-06s
INFO | --- Analysis for simple took 7.722932577133179s
Availability | SPARQL endpoint availability check for SITC-V4 took 25.80396008491516s
Availability | VoID file availability check for SITC-V4 took 0.0009202957153320312s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.821298360824585s
Reputation | Calculation of the PageRank for SITC-V4 took 0.020933866500854492s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 4.482269287109375e-05s
Believability | Calculation of trust value for SITC-V4 took 5.245208740234375e-06s
INFO | --- Analysis for sitc-v4 took 126.8951907157898s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.172325134277344e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.2416067123413086s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.020639657974243164s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.0517578125e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 6.67572021484375e-06s
INFO | --- Analysis for slideshare2rdf took 2.806631088256836s
Availability | SPARQL endpoint availability check for Slidewiki (RDF/SPARQL) took 4.1484832763671875e-05s
Availability | VoID file availability check for Slidewiki (RDF/SPARQL) took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for Slidewiki (RDF/SPARQL) took 0.28348493576049805s
Reputation | Calculation of the PageRank for Slidewiki (RDF/SPARQL) took 0.020513057708740234s
Interlinking | Calculation of Degree of Connection for Slidewiki (RDF/SPARQL) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Slidewiki (RDF/SPARQL) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Slidewiki (RDF/SPARQL) took 2.86102294921875e-05s
Believability | Calculation of trust value for Slidewiki (RDF/SPARQL) took 8.106231689453125e-06s
INFO | --- Analysis for slidewiki-rdf-sparql took 3.4013116359710693s
Availability | SPARQL endpoint availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 4.220008850097656e-05s
Availability | VoID file availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.27162790298461914s
Reputation | Calculation of the PageRank for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.02077484130859375s
Interlinking | Calculation of Degree of Connection for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0008661746978759766s
Interlinking | Calculation of Clustering coefficient for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 3.3855438232421875e-05s
Believability | Calculation of trust value for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 6.9141387939453125e-06s
INFO | --- Analysis for slovn-k-cpv-2008---common-procurement-vocabulary-2008 took 3.3300058841705322s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 5.423807382583618s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0007407665252685547s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.27113842964172363s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.020508527755737305s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.647804260253906e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 1.9311904907226562e-05s
INFO | --- Analysis for smartlink took 14.011337041854858s
Availability | SPARQL endpoint availability check for Social Networks and Archival Context Fall 2011 took 4.124641418457031e-05s
Availability | VoID file availability check for Social Networks and Archival Context Fall 2011 took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for Social Networks and Archival Context Fall 2011 took 0.27170777320861816s
Reputation | Calculation of the PageRank for Social Networks and Archival Context Fall 2011 took 0.02044510841369629s
Interlinking | Calculation of Degree of Connection for Social Networks and Archival Context Fall 2011 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Social Networks and Archival Context Fall 2011 took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Social Networks and Archival Context Fall 2011 took 2.8371810913085938e-05s
Believability | Calculation of trust value for Social Networks and Archival Context Fall 2011 took 7.62939453125e-06s
INFO | --- Analysis for social-networks-and-archival-context-fall-2011 took 3.3871591091156006s
Availability | SPARQL endpoint availability check for SocialLink took 4.1484832763671875e-05s
Availability | VoID file availability check for SocialLink took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for SocialLink took 0.27072954177856445s
Reputation | Calculation of the PageRank for SocialLink took 0.020368337631225586s
Interlinking | Calculation of Degree of Connection for SocialLink took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SocialLink took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for SocialLink took 2.8371810913085938e-05s
Believability | Calculation of trust value for SocialLink took 6.67572021484375e-06s
INFO | --- Analysis for sociallink took 2.8885011672973633s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.2298598289489746s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0006725788116455078s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 15.698541164398193s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.4914536476135254s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.2105998992919922s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.4702410697937012s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.36664891242980957s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.19308686256408691s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.3530912399291992s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.1509079933166504s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.12061905860900879s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.7815196514129639s
License | MR license check for Social Semantic Web Thesaurus took 0.13300514221191406s
License | HR license check for Social Semantic Web Thesaurus took 0.12989449501037598s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.1335442066192627s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.12193012237548828s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.2030184268951416s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.13147282600402832s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.12633228302001953s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.11032485961914062s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.647791385650635s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 6.937980651855469e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.12849664688110352s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.1311631202697754s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.11830902099609375s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.09421944618225098s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.10873150825500488s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.22385764122009277s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.2823171615600586s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 1.5289661884307861s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.11414051055908203s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.0936136245727539s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.09937644004821777s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.4491896629333496s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.012149572372436523s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.10031938552856445s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.3219025135040283s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.09994864463806152s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.094273567199707s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.5120136737823486s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.0005521774291992188s
Security | Sign check for Social Semantic Web Thesaurus took 0.08570456504821777s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 105.57206058502197s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.38214612007141113s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.020407915115356445s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 0.00010895729064941406s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for socialsemweb-thesaurus took 215.52859091758728s
Availability | SPARQL endpoint availability check for SORS took 4.6253204345703125e-05s
Availability | VoID file availability check for SORS took 0.0007283687591552734s
Completeness | Calculation of interlinking completeness for SORS took 0.2731907367706299s
Reputation | Calculation of the PageRank for SORS took 0.020699024200439453s
Interlinking | Calculation of Degree of Connection for SORS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SORS took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for SORS took 5.0067901611328125e-05s
Believability | Calculation of trust value for SORS took 5.9604644775390625e-06s
INFO | --- Analysis for sors took 13.118375539779663s
Availability | SPARQL endpoint availability check for Soudy České republiky took 4.291534423828125e-05s
Availability | VoID file availability check for Soudy České republiky took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Soudy České republiky took 0.27916884422302246s
Reputation | Calculation of the PageRank for Soudy České republiky took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for Soudy České republiky took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Soudy České republiky took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Soudy České republiky took 3.075599670410156e-05s
Believability | Calculation of trust value for Soudy České republiky took 7.152557373046875e-06s
INFO | --- Analysis for soudy--esk--republiky took 3.376227617263794s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 4.3392181396484375e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.28318047523498535s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.020581483840942383s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 9.322166442871094e-05s
Believability | Calculation of trust value for southampton-ac-uk took 7.152557373046875e-06s
INFO | --- Analysis for southampton-ac-uk took 3.7438063621520996s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 3.24782657623291s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0006680488586425781s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.2851998805999756s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.020968914031982422s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 3.504753112792969e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 7.867813110351562e-06s
INFO | --- Analysis for southampton-ac-uk-apps took 10.677955150604248s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 4.410743713378906e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0007002353668212891s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.27041006088256836s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.02067279815673828s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.131431579589844e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 7.152557373046875e-06s
INFO | --- Analysis for southampton-ecs-eprints took 4.973536729812622s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.5989603996276855s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.00025916099548339844s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 165.62282347679138s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.2067902088165283s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 2.2534737586975098s
Interoperability | New terms check for Spanish Linguistic Datasets took 2.965970754623413s
Versatility | Languages check for Spanish Linguistic Datasets took 42.412129163742065s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 5.674248695373535s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.13005805015563965s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.38277292251586914s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.3111553192138672s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.28183436393737793s
License | MR license check for Spanish Linguistic Datasets took 0.3260467052459717s
License | HR license check for Spanish Linguistic Datasets took 0.4135932922363281s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.31125736236572266s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.3885838985443115s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.5751423835754395s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.27698349952697754s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.32968878746032715s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.28720808029174805s
Performance | Throughput check for Spanish Linguistic Datasets took 11.403557777404785s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 7.343292236328125e-05s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.2754192352294922s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.27907824516296387s
Interlinking | skos check for Spanish Linguistic Datasets took 0.2888202667236328s
Interlinking | skos check for Spanish Linguistic Datasets took 0.2330787181854248s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.2819831371307373s
Currency | Creation date check for Spanish Linguistic Datasets took 0.5913002490997314s
Currency | Modification date check for Spanish Linguistic Datasets took 0.5630307197570801s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 61.45638036727905s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.28314638137817383s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.2822427749633789s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 0.27306604385375977s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 0.9478039741516113s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.010142087936401367s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.6136727333068848s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.29498767852783203s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.657033205032349s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.444358110427856s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 47.46120834350586s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.507704496383667s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 5.831338405609131s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 2.900169610977173s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.40852832794189453s
Security | Sign check for Spanish Linguistic Datasets took 0.29932665824890137s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 16.205055236816406s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.3789825439453125s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.026178359985351562s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.409385681152344e-05s
Interoperability | Check the re-using of existing vocabs for Spanish Linguistic Datasets took 2.1457672119140625e-06s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 7.3909759521484375e-06s
INFO | --- Analysis for spanish-linguistic-datasets took 430.7337455749512s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.07224607467651367s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.28388500213623047s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.020355939865112305s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 6.461143493652344e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 8.106231689453125e-06s
INFO | --- Analysis for sparql-endpoint-status took 3.8548455238342285s
Availability | SPARQL endpoint availability check for SPC publikovaná SÚKL took 4.291534423828125e-05s
Availability | VoID file availability check for SPC publikovaná SÚKL took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for SPC publikovaná SÚKL took 0.24175190925598145s
Reputation | Calculation of the PageRank for SPC publikovaná SÚKL took 0.02054882049560547s
Interlinking | Calculation of Degree of Connection for SPC publikovaná SÚKL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SPC publikovaná SÚKL took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for SPC publikovaná SÚKL took 2.8371810913085938e-05s
Believability | Calculation of trust value for SPC publikovaná SÚKL took 7.152557373046875e-06s
INFO | --- Analysis for spc-publikovan--s-kl took 2.9196033477783203s
Availability | SPARQL endpoint availability check for SPQR took 4.076957702636719e-05s
Availability | VoID file availability check for SPQR took 0.00037288665771484375s
Completeness | Calculation of interlinking completeness for SPQR took 0.2546043395996094s
Reputation | Calculation of the PageRank for SPQR took 0.020573854446411133s
Interlinking | Calculation of Degree of Connection for SPQR took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SPQR took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for SPQR took 2.9802322387695312e-05s
Believability | Calculation of trust value for SPQR took 8.821487426757812e-06s
INFO | --- Analysis for spqr took 3.038938283920288s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.410743713378906e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.27100634574890137s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.020685672760009766s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 3.123283386230469e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 7.867813110351562e-06s
INFO | --- Analysis for srcmf took 2.4713826179504395s
Availability | SPARQL endpoint availability check for SSF took 4.1961669921875e-05s
Availability | VoID file availability check for SSF took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for SSF took 0.28232550621032715s
Reputation | Calculation of the PageRank for SSF took 0.0207061767578125s
Interlinking | Calculation of Degree of Connection for SSF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SSF took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for SSF took 3.123283386230469e-05s
Believability | Calculation of trust value for SSF took 8.58306884765625e-06s
INFO | --- Analysis for ssf-lexicon took 2.9358069896698s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 4.315376281738281e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.2649345397949219s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.021086454391479492s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.4809112548828125e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 8.344650268554688e-06s
INFO | --- Analysis for st-andrews-resource-lists took 2.753880500793457s
Availability | SPARQL endpoint availability check for STAC took 4.1961669921875e-05s
Availability | VoID file availability check for STAC took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for STAC took 0.2457566261291504s
Reputation | Calculation of the PageRank for STAC took 0.020426273345947266s
Interlinking | Calculation of Degree of Connection for STAC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for STAC took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for STAC took 2.9802322387695312e-05s
Believability | Calculation of trust value for STAC took 7.867813110351562e-06s
INFO | --- Analysis for stac took 3.404801607131958s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for The Scottish Government took 4.1961669921875e-05s
Availability | VoID file availability check for Organogram and staff pay data for The Scottish Government took 0.0003066062927246094s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for The Scottish Government took 0.24010825157165527s
Reputation | Calculation of the PageRank for Organogram and staff pay data for The Scottish Government took 0.0205538272857666s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for The Scottish Government took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Organogram and staff pay data for The Scottish Government took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for The Scottish Government took 3.3855438232421875e-05s
Believability | Calculation of trust value for Organogram and staff pay data for The Scottish Government took 8.344650268554688e-06s
INFO | --- Analysis for staff-organograms-and-pay-scottish-government took 3.364682912826538s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.267692565917969e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.2476820945739746s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.020675182342529297s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.266334533691406e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 5.0067901611328125e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 4.050930023193359s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.2291271686553955s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.2736687660217285s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.02078986167907715s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00010895729064941406s
Believability | Calculation of trust value for statistics.data.gov.uk took 7.152557373046875e-06s
INFO | --- Analysis for statistics-data-gov-uk took 3.893979549407959s
Availability | SPARQL endpoint availability check for Statistics on Fatal Traffic Accidents in greek roads took 4.100799560546875e-05s
Availability | VoID file availability check for Statistics on Fatal Traffic Accidents in greek roads took 0.0002892017364501953s
Completeness | Calculation of interlinking completeness for Statistics on Fatal Traffic Accidents in greek roads took 0.25798463821411133s
Reputation | Calculation of the PageRank for Statistics on Fatal Traffic Accidents in greek roads took 0.021114110946655273s
Interlinking | Calculation of Degree of Connection for Statistics on Fatal Traffic Accidents in greek roads took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Statistics on Fatal Traffic Accidents in greek roads took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Statistics on Fatal Traffic Accidents in greek roads took 3.409385681152344e-05s
Believability | Calculation of trust value for Statistics on Fatal Traffic Accidents in greek roads took 7.3909759521484375e-06s
INFO | --- Analysis for statistics-on-fatal-traffic-accidents-in-greek-roads took 2.9053640365600586s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 4.76837158203125e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.2572314739227295s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.020174264907836914s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00010752677917480469s
Believability | Calculation of trust value for statusnet-1w6-org took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-1w6-org took 3.068655490875244s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.2784862518310547s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.020374298095703125s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.222724914550781e-05s
Believability | Calculation of trust value for statusnet-20100-org took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-20100-org took 2.994438648223877s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.27996325492858887s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.020557880401611328s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 7.200241088867188e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-alexandrefranke-com took 2.789538860321045s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.27167606353759766s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.020412206649780273s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 8.130073547363281e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.4652795791625977s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.2514524459838867s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.020278215408325195s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 8.96453857421875e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-belfalas-org took 2.5731871128082275s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.23860645294189453s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.020268678665161133s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00011420249938964844s
Believability | Calculation of trust value for statusnet-bka-li took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-bka-li took 2.853379011154175s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.6253204345703125e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.27102112770080566s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.02031230926513672s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 4.0531158447265625e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.467209815979004s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0005660057067871094s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.2505948543548584s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.020379304885864258s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 4.9114227294921875e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-ced117-net took 3.852451801300049s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.26144933700561523s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0008854866027832031s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 5.793571472167969e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.541292428970337s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 5.0067901611328125e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0007300376892089844s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.25817251205444336s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.02054762840270996s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00011682510375976562s
Believability | Calculation of trust value for statusnet-chromic-org took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-chromic-org took 3.132889747619629s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.27355432510375977s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.02043914794921875s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 8.106231689453125e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-cooleysekula-net took 5.928474187850952s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.276503324508667s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.020402193069458008s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.745887756347656e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-coreyavis-com took 2.4707939624786377s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 5.984306335449219e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.2699575424194336s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.02074122428894043s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 7.367134094238281e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.210305690765381s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.2598087787628174s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.02037811279296875s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.000110626220703125s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.5668208599090576s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.2810072898864746s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.020737886428833008s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.508827209472656e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.430176019668579s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0007336139678955078s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.2681875228881836s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.020840883255004883s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 6.008148193359375e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-doomicile-de took 3.2542543411254883s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.2587919235229492s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.020631790161132812s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 6.008148193359375e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-dtdns-net took 2.5198285579681396s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.27602219581604004s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.020613908767700195s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.528594970703125e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-equestriarp-net took 2.4398937225341797s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.289736270904541s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.02029705047607422s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.700920104980469e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-exdc-net took 12.489696502685547s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0007393360137939453s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.2526588439941406s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.02030324935913086s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.679794311523438e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-fcac-com took 22.345821142196655s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.27955007553100586s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.020307064056396484s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.412101745605469e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 5.4836273193359375e-06s
INFO | --- Analysis for statusnet-fcestrada-com took 3.131464958190918s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 5.245208740234375e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.2738678455352783s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.02020883560180664s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.0001838207244873047s
Believability | Calculation of trust value for statusnet-fragdev-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-fragdev-com took 3.2573740482330322s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.27518463134765625s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.020482540130615234s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.653236389160156e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-freelish-us took 2.4662837982177734s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.2649712562561035s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.020298242568969727s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00011277198791503906s
Believability | Calculation of trust value for statusnet-gegeweb-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-gegeweb-org took 2.5911459922790527s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.2612597942352295s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.02014613151550293s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 6.747245788574219e-05s
Believability | Calculation of trust value for statusnet-glou-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-glou-org took 2.5237221717834473s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.2616133689880371s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00012135505676269531s
Believability | Calculation of trust value for statusnet-gomertronic-com took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-gomertronic-com took 2.4735991954803467s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 8.344650268554688e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.27013349533081055s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.020261287689208984s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00010800361633300781s
Believability | Calculation of trust value for statusnet-hackerposse-com took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-hackerposse-com took 2.9603002071380615s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 6.67572021484375e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.2562897205352783s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.02047109603881836s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 4.9591064453125e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-hii-co-il took 3.5723109245300293s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.26330137252807617s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.0204927921295166s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 9.179115295410156e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 3.458819627761841s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 4.649162292480469e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.26683616638183594s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.020853519439697266s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 6.413459777832031e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-imirhil-fr took 2.5053305625915527s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.2532970905303955s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.02069091796875s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 4.172325134277344e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-integralblue-com took 2.5885376930236816s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 4.696846008300781e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.25972461700439453s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.020862817764282227s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 5.555152893066406e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.375375747680664s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.2849090099334717s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.02087712287902832s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00012230873107910156s
Believability | Calculation of trust value for statusnet-jonkman-ca took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-jonkman-ca took 3.377248525619507s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 5.412101745605469e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.2705988883972168s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.020659446716308594s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.942054748535156e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-kaimi-cc took 2.453585147857666s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 5.6743621826171875e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.23945879936218262s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.020720481872558594s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0008554458618164062s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 5.1975250244140625e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 1.811981201171875e-05s
INFO | --- Analysis for statusnet-kathryl-fr took 2.3788177967071533s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.25481438636779785s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.020514726638793945s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 4.00543212890625e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-kenzoid-com took 3.2316224575042725s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.2758753299713135s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.020580053329467773s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 7.581710815429688e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-keuser-fr took 2.396785020828247s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.27054548263549805s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.02090907096862793s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 4.839897155761719e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.535820484161377s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 8.344650268554688e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0005779266357421875s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.2583494186401367s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.021261215209960938s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0008873939514160156s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 7.295608520507812e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-lebsanft-org took 2.5594637393951416s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.29265666007995605s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.020827054977416992s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 0.00010347366333007812s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.6385996341705322s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.2804441452026367s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.020331144332885742s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0008592605590820312s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00012087821960449219s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.4391801357269287s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0006682872772216797s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.2543466091156006s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.02024984359741211s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.412101745605469e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-ludost-net took 16.31504988670349s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.26340198516845703s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.020709991455078125s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 0.000102996826171875s
Believability | Calculation of trust value for statusnet-lydiastench-com took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-lydiastench-com took 2.3437187671661377s
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.0005290508270263672s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.2538745403289795s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.02052474021911621s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.316734313964844e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.417738199234009s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.26375842094421387s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.020242929458618164s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.00015783309936523438s
Believability | Calculation of trust value for statusnet-macno-org took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-macno-org took 2.4324119091033936s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 5.054473876953125e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.26148486137390137s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.020749807357788086s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.508827209472656e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.388864278793335s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.32354164123535156s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.020551681518554688s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 8.678436279296875e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-maymay-net took 42.015013694763184s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.25806760787963867s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.020363569259643555s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.0001595020294189453s
Believability | Calculation of trust value for statusnet-morphtown-de took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-morphtown-de took 2.4546427726745605s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.25926756858825684s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.020238876342773438s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 9.584426879882812e-05s
Believability | Calculation of trust value for statusnet-mrblog-nl took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-mrblog-nl took 2.4265055656433105s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.25495386123657227s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.020450115203857422s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.364418029785156e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-mulestable-net took 2.377326726913452s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 4.6253204345703125e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.28003811836242676s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.1975250244140625e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-my-status-tk took 2.6631648540496826s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.2792677879333496s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.02039194107055664s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.0001163482666015625s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.4161572456359863s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.2756984233856201s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.02035689353942871s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 5.5789947509765625e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.630768060684204s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.24143695831298828s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.020288467407226562s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.175041198730469e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-otbm-fr took 2.4450008869171143s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 9.608268737792969e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.28215503692626953s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.020280122756958008s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.869171142578125e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.5026209354400635s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.263275146484375s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.020425796508789062s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 4.76837158203125e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-panda-id-au took 2.824704647064209s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.255723237991333s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.02032184600830078s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.799003601074219e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-piana-eu took 2.4435720443725586s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.863739013671875e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.2770085334777832s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.020755529403686523s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.510185241699219e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-planet-libre-org took 2.4670286178588867s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 4.76837158203125e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.26522183418273926s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.020382404327392578s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.00023484230041503906s
Believability | Calculation of trust value for statusnet-postblue-info took 7.62939453125e-06s
INFO | --- Analysis for statusnet-postblue-info took 2.4267709255218506s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 8.940696716308594e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.2724153995513916s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.020354509353637695s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 7.009506225585938e-05s
Believability | Calculation of trust value for statusnet-progval-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-progval-net took 2.472731113433838s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 4.863739013671875e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.2659485340118408s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.020270586013793945s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00012946128845214844s
Believability | Calculation of trust value for statusnet-qdnx-org took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-qdnx-org took 2.925588369369507s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 6.985664367675781e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.2624638080596924s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.020284414291381836s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 7.05718994140625e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-qth-fr took 3.2413299083709717s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0007555484771728516s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.24045157432556152s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.02057170867919922s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.00022482872009277344s
Believability | Calculation of trust value for statusnet-quitter-se took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-quitter-se took 2.9091145992279053s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.25102996826171875s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.020540475845336914s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00010561943054199219s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.5042171478271484s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0003018379211425781s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.26658201217651367s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.0208432674407959s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 6.151199340820312e-05s
Believability | Calculation of trust value for statusnet-recit-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-recit-org took 4.251003742218018s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.2823312282562256s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.020198583602905273s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.0001456737518310547s
Believability | Calculation of trust value for statusnet-russwurm-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-russwurm-org took 3.2049882411956787s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0006937980651855469s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.2664148807525635s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.020267724990844727s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 7.796287536621094e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-samnoble-org took 4.839596748352051s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.280925989151001s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.020804405212402344s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0010230541229248047s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 9.274482727050781e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-schiessle-org took 2.572404146194458s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 5.054473876953125e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.2583026885986328s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.020438671112060547s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 9.822845458984375e-05s
Believability | Calculation of trust value for statusnet-scoffoni-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-scoffoni-net took 2.4698925018310547s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.27987074851989746s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.02072882652282715s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.365776062011719e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-sebseb01-net took 2.439272403717041s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 5.14984130859375e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.28212666511535645s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.02041029930114746s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.128715515136719e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-shnoulle-net took 3.231405019760132s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.263228178024292s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.020152807235717773s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00022268295288085938s
Believability | Calculation of trust value for statusnet-skilledtests-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-skilledtests-com took 3.0225117206573486s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 0.0001285076141357422s
Availability | VoID file availability check for statusnet-somsants-net took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.2690768241882324s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.020741701126098633s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00012350082397460938s
Believability | Calculation of trust value for statusnet-somsants-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-somsants-net took 2.4882688522338867s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.28136253356933594s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.02166914939880371s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.00015664100646972656s
Believability | Calculation of trust value for statusnet-soucy-cc took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-soucy-cc took 2.4699058532714844s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.2577707767486572s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.020414352416992188s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 7.390975952148438e-05s
Believability | Calculation of trust value for statusnet-spip-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-spip-org took 3.3741559982299805s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 7.343292236328125e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.23965954780578613s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.020690441131591797s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 7.2479248046875e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-spraci-org took 2.4921393394470215s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.982948303222656e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0012750625610351562s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.25616455078125s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.020520448684692383s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.0001232624053955078s
Believability | Calculation of trust value for statusnet-ssweeny-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-ssweeny-net took 6.008458614349365s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.2644984722137451s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.020261764526367188s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00022721290588378906s
Believability | Calculation of trust value for statusnet-status-net took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-status-net took 3.3667123317718506s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.25396728515625s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.020525455474853516s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.5789947509765625e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.4137260913848877s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 5.626678466796875e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.2603793144226074s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.020534515380859375s
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.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 9.870529174804688e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 5.4836273193359375e-06s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.448167324066162s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 5.054473876953125e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.25055932998657227s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.02049565315246582s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0008211135864257812s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.00012755393981933594s
Believability | Calculation of trust value for statusnet-thelovebug-org took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-thelovebug-org took 2.5797646045684814s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0007393360137939453s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.26422572135925293s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.020882844924926758s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.605552673339844e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-thornton2-com took 5.036396265029907s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.2613387107849121s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.020527124404907227s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00010967254638671875s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.6609890460968018s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.2919909954071045s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.020389795303344727s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 3.9577484130859375e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-tl1n-com took 3.5855534076690674s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.2723064422607422s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.02019953727722168s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.699562072753906e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.6064045429229736s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.2610344886779785s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.020589113235473633s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 3.743171691894531e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-uni-siegen-de took 2.529447078704834s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 5.698204040527344e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.2800178527832031s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.02057504653930664s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 3.0994415283203125e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 7.152557373046875e-06s
INFO | --- Analysis for steak took 2.691365957260132s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 4.267692565917969e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.24133539199829102s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.020254135131835938s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.3882598876953125e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 7.3909759521484375e-06s
INFO | --- Analysis for stitch-rameau took 3.8989133834838867s
Availability | SPARQL endpoint availability check for Strukturované popisy z FDA took 4.458427429199219e-05s
Availability | VoID file availability check for Strukturované popisy z FDA took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Strukturované popisy z FDA took 0.26166248321533203s
Reputation | Calculation of the PageRank for Strukturované popisy z FDA took 0.020444869995117188s
Interlinking | Calculation of Degree of Connection for Strukturované popisy z FDA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Strukturované popisy z FDA took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Strukturované popisy z FDA took 2.86102294921875e-05s
Believability | Calculation of trust value for Strukturované popisy z FDA took 1.1920928955078125e-05s
INFO | --- Analysis for strukturovan--popisy-z-fda took 2.935807466506958s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.4055306911468506s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0007731914520263672s
Extra | Recovery of all triples for STW Thesaurus for Economics took 11.388355255126953s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.1633360385894775s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.5559258460998535s
Interoperability | New terms check for STW Thesaurus for Economics took 1.6148715019226074s
Versatility | Languages check for STW Thesaurus for Economics took 1.4247419834136963s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.44790124893188477s
Security | Check HTTPS for STW Thesaurus for Economics took 0.12322711944580078s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.2630314826965332s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.25429821014404297s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.2517681121826172s
License | MR license check for STW Thesaurus for Economics took 0.2527279853820801s
License | HR license check for STW Thesaurus for Economics took 2.2644224166870117s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.24193477630615234s
Understandability | Number of label check for STW Thesaurus for Economics took 0.5931541919708252s
Understandability | URI regex check for STW Thesaurus for Economics took 0.4714338779449463s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.2320702075958252s
Verifiability | Authors check for STW Thesaurus for Economics took 0.2569749355316162s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.25909423828125s
Performance | Throughput check for STW Thesaurus for Economics took 11.009743213653564s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.7222912311553955s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.24078607559204102s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.24123764038085938s
Interlinking | skos check for STW Thesaurus for Economics took 0.3187549114227295s
Interlinking | skos check for STW Thesaurus for Economics took 0.300462007522583s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.2722454071044922s
Currency | Creation date check for STW Thesaurus for Economics took 0.5231459140777588s
Currency | Modification date check for STW Thesaurus for Economics took 0.5198936462402344s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 7.244537353515625s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.2900063991546631s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.24852371215820312s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.2778749465942383s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 7.84831166267395s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.049952507019043s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.3148605823516846s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.27851009368896484s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.8565082550048828s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 2.4147279262542725s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.2991139888763428s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.9132883548736572s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.6522066593170166s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.23538637161254883s
Security | Sign check for STW Thesaurus for Economics took 0.2515530586242676s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 2554.24529671669s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 1.260716199874878s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.021018028259277344s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 2.6702880859375e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00013566017150878906s
Believability | Calculation of trust value for STW Thesaurus for Economics took 7.62939453125e-06s
INFO | --- Analysis for stw-thesaurus-for-economics took 2646.282646417618s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.9330992698669434s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0006020069122314453s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.9568986892700195s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.020392179489135742s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 4.7206878662109375e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 8.821487426757812e-06s
INFO | --- Analysis for sudocfr took 9.064408779144287s
Availability | SPARQL endpoint availability check for Surge Radio took 5.888938903808594e-05s
Availability | VoID file availability check for Surge Radio took 0.0006544589996337891s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.28375911712646484s
Reputation | Calculation of the PageRank for Surge Radio took 0.02065896987915039s
Interlinking | Calculation of Degree of Connection for Surge Radio took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.320808410644531e-05s
Believability | Calculation of trust value for Surge Radio took 8.58306884765625e-06s
INFO | --- Analysis for surge-radio took 4.816915273666382s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 4.4345855712890625e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.41459131240844727s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.27298736572265625s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.020556211471557617s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0010361671447753906s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 8.344650268554688e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 8.58306884765625e-06s
INFO | --- Analysis for swedish-open-cultural-heritage took 6.596918821334839s
Availability | SPARQL endpoint availability check for SweFN-RDF took 0.9599590301513672s
Availability | VoID file availability check for SweFN-RDF took 0.0006649494171142578s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.26453328132629395s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.031865835189819336s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0012857913970947266s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 5.340576171875e-05s
Believability | Calculation of trust value for SweFN-RDF took 8.58306884765625e-06s
INFO | --- Analysis for swefn-rdf took 5.500976800918579s
Availability | SPARQL endpoint availability check for SwetoDblp took 4.410743713378906e-05s
Availability | VoID file availability check for SwetoDblp took 0.0007848739624023438s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.2639439105987549s
Reputation | Calculation of the PageRank for SwetoDblp took 0.02078533172607422s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.719329833984375e-05s
Believability | Calculation of trust value for SwetoDblp took 9.298324584960938e-06s
INFO | --- Analysis for sweto-dblp took 22.7919819355011s
Availability | SPARQL endpoint availability check for SymbolicData took 6.67572021484375e-05s
Availability | VoID file availability check for SymbolicData took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for SymbolicData took 0.25849461555480957s
Reputation | Calculation of the PageRank for SymbolicData took 0.0207977294921875s
Interlinking | Calculation of Degree of Connection for SymbolicData took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SymbolicData took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for SymbolicData took 3.0994415283203125e-05s
Believability | Calculation of trust value for SymbolicData took 8.58306884765625e-06s
INFO | --- Analysis for symbolicdata took 3.388209342956543s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.4917750358581543s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0008511543273925781s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.7147364616394043s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 1.4245927333831787s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 8.988346099853516s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 23.289780855178833s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.2561485767364502s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 3.6681299209594727s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.13913178443908691s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.7742149829864502s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 2.6410367488861084s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.2717413902282715s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.5943212509155273s
License | HR license check for National Digital Data Archive of Hungary (partial) took 54.40580487251282s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.5386810302734375s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 39.88835859298706s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.42745089530944824s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.2787137031555176s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.21101737022399902s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.2548940181732178s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.759740114212036s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 7.104873657226562e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.7429687976837158s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 1.7769851684570312s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.549755334854126s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.5678269863128662s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.522514820098877s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 2.9531328678131104s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 2.8222439289093018s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 65.66074776649475s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.29810476303100586s
Accuracy | Check Functional Property for National Digital Data Archive of Hungary (partial) took 0.28850769996643066s
Accuracy | Check Inverse Functional Property for National Digital Data Archive of Hungary (partial) took 0.28476738929748535s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.3503403663635254s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0012028217315673828s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.0015952587127685547s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.2862727642059326s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 47.01319718360901s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.3987898826599121s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.7220449447631836s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.3089799880981445s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 48.783705949783325s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.001961231231689453s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.46349048614501953s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.2701685428619385s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 22.41382384300232s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 1.3677423000335693s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.020810365676879883s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 0.00012135505676269531s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.430511474609375e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 8.821487426757812e-06s
INFO | --- Analysis for sztaki-lod took 459.07735109329224s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 4.410743713378906e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.2545626163482666s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.020719528198242188s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.817413330078125e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 8.58306884765625e-06s
INFO | --- Analysis for t4gm-info took 5.899567127227783s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.458427429199219e-05s
Availability | VoID file availability check for tags2con delicious took 0.0007731914520263672s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.25434160232543945s
Reputation | Calculation of the PageRank for tags2con delicious took 0.020563840866088867s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 4.57763671875e-05s
Believability | Calculation of trust value for tags2con delicious took 7.152557373046875e-06s
INFO | --- Analysis for tags2con-delicious took 45.459161043167114s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 262.4864149093628s
Availability | VoID file availability check for Taiwan geographic names took 0.0008692741394042969s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 1.2283048629760742s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.02108597755432129s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 4.9591064453125e-05s
Believability | Calculation of trust value for Taiwan geographic names took 9.298324584960938e-06s
INFO | --- Analysis for taiwan-geographic-names took 668.4837779998779s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 4.887580871582031e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0005707740783691406s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.275437593460083s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.021904706954956055s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 0.00010657310485839844s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 7.62939453125e-06s
INFO | --- Analysis for talis-openlibrary took 5.292780160903931s
Availability | SPARQL endpoint availability check for TalkBank took 4.100799560546875e-05s
Availability | VoID file availability check for TalkBank took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for TalkBank took 0.7320029735565186s
Reputation | Calculation of the PageRank for TalkBank took 0.02062702178955078s
Interlinking | Calculation of Degree of Connection for TalkBank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TalkBank took 0.0009377002716064453s
Interlinking | Calculation of Clustering coefficient for TalkBank took 3.4809112548828125e-05s
Believability | Calculation of trust value for TalkBank took 1.6689300537109375e-05s
INFO | --- Analysis for talkbank took 3.8510117530822754s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 0.9422705173492432s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.26173925399780273s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.020549535751342773s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00011396408081054688s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 7.3909759521484375e-06s
INFO | --- Analysis for taxonconcept took 25.554565906524658s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 4.506111145019531e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.26657891273498535s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.020203590393066406s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 7.510185241699219e-05s
Believability | Calculation of trust value for taxonconcept-assets took 7.152557373046875e-06s
INFO | --- Analysis for taxonconcept-assets took 3.685647964477539s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 4.363059997558594e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0005946159362792969s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.24689269065856934s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.020292043685913086s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 5.054473876953125e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 8.106231689453125e-06s
INFO | --- Analysis for taxonconcept-occurences took 3.1915807723999023s
Availability | SPARQL endpoint availability check for TAXREF-LD: Linked Data French Taxonomic Register took 1.2983379364013672s
Availability | VoID file availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Linked Data French Taxonomic Register took 0.26783108711242676s
Reputation | Calculation of the PageRank for TAXREF-LD: Linked Data French Taxonomic Register took 0.02034139633178711s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Linked Data French Taxonomic Register took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Linked Data French Taxonomic Register took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Linked Data French Taxonomic Register took 4.744529724121094e-05s
Believability | Calculation of trust value for TAXREF-LD: Linked Data French Taxonomic Register took 7.3909759521484375e-06s
INFO | --- Analysis for taxref-ld took 7.652712345123291s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 261.2575933933258s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0006949901580810547s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.25921058654785156s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.020891427993774414s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 4.029273986816406e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 8.58306884765625e-06s
INFO | --- Analysis for tcga took 539.6666615009308s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.3601710796356201s
Availability | VoID file availability check for TCGA Roadmap took 0.0007500648498535156s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.28289175033569336s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.020675182342529297s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 8.153915405273438e-05s
Believability | Calculation of trust value for TCGA Roadmap took 9.059906005859375e-06s
INFO | --- Analysis for tcga-roadmap took 7.255689382553101s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 1.6968331336975098s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.9104440212249756s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.020517826080322266s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00010609626770019531s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 8.106231689453125e-06s
INFO | --- Analysis for tcmgenedit_dataset took 141.8456175327301s
Availability | SPARQL endpoint availability check for TDS took 4.38690185546875e-05s
Availability | VoID file availability check for TDS took 0.0007691383361816406s
Completeness | Calculation of interlinking completeness for TDS took 0.2589545249938965s
Reputation | Calculation of the PageRank for TDS took 0.020389556884765625s
Interlinking | Calculation of Degree of Connection for TDS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TDS took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for TDS took 3.62396240234375e-05s
Believability | Calculation of trust value for TDS took 7.62939453125e-06s
INFO | --- Analysis for tds took 5.017461776733398s
Availability | SPARQL endpoint availability check for TED Talks took 4.1961669921875e-05s
Availability | VoID file availability check for TED Talks took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for TED Talks took 0.2735002040863037s
Reputation | Calculation of the PageRank for TED Talks took 0.020310163497924805s
Interlinking | Calculation of Degree of Connection for TED Talks took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TED Talks took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for TED Talks took 2.9325485229492188e-05s
Believability | Calculation of trust value for TED Talks took 7.62939453125e-06s
INFO | --- Analysis for ted-talks took 3.298124313354492s
Availability | SPARQL endpoint availability check for TEKORD took 4.291534423828125e-05s
Availability | VoID file availability check for TEKORD took 0.0003552436828613281s
Completeness | Calculation of interlinking completeness for TEKORD took 0.2834334373474121s
Reputation | Calculation of the PageRank for TEKORD took 0.020371675491333008s
Interlinking | Calculation of Degree of Connection for TEKORD took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for TEKORD took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.649162292480469e-05s
Believability | Calculation of trust value for TEKORD took 6.67572021484375e-06s
INFO | --- Analysis for tekord took 5.48189377784729s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 2.535271644592285s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0004239082336425781s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.2783184051513672s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.022133350372314453s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0011491775512695312s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.0001461505889892578s
Believability | Calculation of trust value for Telegraphis Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for telegraphis took 9.350022077560425s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 4.363059997558594e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0004291534423828125s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.6957287788391113s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.020859718322753906s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0008194446563720703s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 8.130073547363281e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 8.344650268554688e-06s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 14.167119026184082s
Availability | SPARQL endpoint availability check for TERENCE Reading Comprehension Dataset took 4.100799560546875e-05s
Availability | VoID file availability check for TERENCE Reading Comprehension Dataset took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for TERENCE Reading Comprehension Dataset took 0.2514371871948242s
Reputation | Calculation of the PageRank for TERENCE Reading Comprehension Dataset took 0.02040553092956543s
Interlinking | Calculation of Degree of Connection for TERENCE Reading Comprehension Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for TERENCE Reading Comprehension Dataset took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for TERENCE Reading Comprehension Dataset took 2.8133392333984375e-05s
Believability | Calculation of trust value for TERENCE Reading Comprehension Dataset took 8.344650268554688e-06s
INFO | --- Analysis for terence-reading-comprehension-dataset took 2.892191171646118s
Availability | SPARQL endpoint availability check for Terminesp Linked Data took 7.700920104980469e-05s
Availability | VoID file availability check for Terminesp Linked Data took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Terminesp Linked Data took 0.2854468822479248s
Reputation | Calculation of the PageRank for Terminesp Linked Data took 0.020386457443237305s
Interlinking | Calculation of Degree of Connection for Terminesp Linked Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Terminesp Linked Data took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Terminesp Linked Data took 2.8848648071289062e-05s
Believability | Calculation of trust value for Terminesp Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for terminesp took 2.9757578372955322s
Availability | SPARQL endpoint availability check for Tesauro materias BUPM took 4.0531158447265625e-05s
Availability | VoID file availability check for Tesauro materias BUPM took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Tesauro materias BUPM took 0.261096715927124s
Reputation | Calculation of the PageRank for Tesauro materias BUPM took 0.020276784896850586s
Interlinking | Calculation of Degree of Connection for Tesauro materias BUPM took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Tesauro materias BUPM took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Tesauro materias BUPM took 2.7894973754882812e-05s
Believability | Calculation of trust value for Tesauro materias BUPM took 9.775161743164062e-06s
INFO | --- Analysis for tesauro-materias-bupm took 2.8861334323883057s
Availability | SPARQL endpoint availability check for Teseo took 4.935264587402344e-05s
Availability | VoID file availability check for Teseo took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for Teseo took 0.2504386901855469s
Reputation | Calculation of the PageRank for Teseo took 0.02062511444091797s
Interlinking | Calculation of Degree of Connection for Teseo took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Teseo took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Teseo took 3.147125244140625e-05s
Believability | Calculation of trust value for Teseo took 8.344650268554688e-06s
INFO | --- Analysis for teseo took 2.879481554031372s
Availability | SPARQL endpoint availability check for xxxxx took 260.5729582309723s
Availability | VoID file availability check for xxxxx took 0.0008289813995361328s
Completeness | Calculation of interlinking completeness for xxxxx took 0.27027368545532227s
Reputation | Calculation of the PageRank for xxxxx took 0.020853519439697266s
Interlinking | Calculation of Degree of Connection for xxxxx took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for xxxxx took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for xxxxx took 5.5789947509765625e-05s
Believability | Calculation of trust value for xxxxx took 7.62939453125e-06s
INFO | --- Analysis for testee took 797.6989240646362s
Availability | SPARQL endpoint availability check for Texai Lexicon took 5.888938903808594e-05s
Availability | VoID file availability check for Texai Lexicon took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for Texai Lexicon took 0.2687540054321289s
Reputation | Calculation of the PageRank for Texai Lexicon took 0.021002531051635742s
Interlinking | Calculation of Degree of Connection for Texai Lexicon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Texai Lexicon took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Texai Lexicon took 3.0040740966796875e-05s
Believability | Calculation of trust value for Texai Lexicon took 9.298324584960938e-06s
INFO | --- Analysis for texai_lexicon took 5.1936023235321045s
Availability | SPARQL endpoint availability check for The CIARD RING took 4.172325134277344e-05s
Availability | VoID file availability check for The CIARD RING took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for The CIARD RING took 0.7647926807403564s
Reputation | Calculation of the PageRank for The CIARD RING took 0.020715951919555664s
Interlinking | Calculation of Degree of Connection for The CIARD RING took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The CIARD RING took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for The CIARD RING took 3.0994415283203125e-05s
Believability | Calculation of trust value for The CIARD RING took 9.059906005859375e-06s
INFO | --- Analysis for the-ciard-ring took 4.788252115249634s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 0.1535327434539795s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.26894474029541016s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.020944595336914062s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 3.528594970703125e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 1.0251998901367188e-05s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 2.6405482292175293s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 0.8940627574920654s
Availability | VoID file availability check for The European Library Open Dataset took 0.0007531642913818359s
Extra | Recovery of all triples for The European Library Open Dataset took 1.2462456226348877s
Performance | Total latancy measurement for The European Library Open Dataset took 1.377861499786377s
Amount of data | Number of triples check for The European Library Open Dataset took 30.202130794525146s
Versatility | Languages check for The European Library Open Dataset took 0.24963712692260742s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 30.226588487625122s
Interpretability | RDF structures check for The European Library Open Dataset took 0.24721908569335938s
Versatility | Serialization formats check for The European Library Open Dataset took 0.24802613258361816s
Availability | RDF dump link check for The European Library Open Dataset took 0.22785067558288574s
License | MR license check for The European Library Open Dataset took 0.3582940101623535s
License | HR license check for The European Library Open Dataset took 0.23894143104553223s
Amount of data | Number of property check for The European Library Open Dataset took 0.25035905838012695s
Understandability | Number of label check for The European Library Open Dataset took 3.094569444656372s
Understandability | URI regex check for The European Library Open Dataset took 0.5942621231079102s
Understandability | Vocabs check for The European Library Open Dataset took 0.24024295806884766s
Verifiability | Authors check for The European Library Open Dataset took 0.21877241134643555s
Verifiability | Publishers check for The European Library Open Dataset took 0.26189661026000977s
Performance | Throughput check for The European Library Open Dataset took 11.811248779296875s
Amount of data | Check the number of entities for The European Library Open Dataset took 7.200241088867188e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 0.257185697555542s
Interlinking | sameAs chians check for The European Library Open Dataset took 0.4684457778930664s
Interlinking | skos check for The European Library Open Dataset took 0.40390968322753906s
Interlinking | skos check for The European Library Open Dataset took 0.534447193145752s
Timeliness | dataset update frequency check for The European Library Open Dataset took 0.2241504192352295s
Currency | Creation date check for The European Library Open Dataset took 0.4902670383453369s
Currency | Modification date check for The European Library Open Dataset took 0.4956929683685303s
Rep.Conc. | URIs length for The European Library Open Dataset took 60.48973774909973s
Interoperability | New vocabularies check for The European Library Open Dataset took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 0.3231337070465088s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 0.7513768672943115s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.027626752853393555s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.02833104133605957s
Consistency | Disjoint class check for The European Library Open Dataset took 0.3785860538482666s
Consistency | Check Misplaced properties for The European Library Open Dataset took 30.432411909103394s
Consistency | Misplaced classes for The European Library Open Dataset took 0.37166333198547363s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 1.793504238128662s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.3258233070373535s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 31.570886373519897s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.03241300582885742s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 0.30993127822875977s
Security | Sign check for The European Library Open Dataset took 0.22832226753234863s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 17.96576738357544s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.3553924560546875s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.020340919494628906s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 5.984306335449219e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 8.58306884765625e-06s
INFO | --- Analysis for the-european-library-open-dataset took 409.8173372745514s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 60.05189085006714s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0007166862487792969s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.6958160400390625s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.020636320114135742s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00010538101196289062s
Believability | Calculation of trust value for The Eurostat Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for the-eurostat-linked-data took 244.41228866577148s
Availability | SPARQL endpoint availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 4.100799560546875e-05s
Availability | VoID file availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0002846717834472656s
Completeness | Calculation of interlinking completeness for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.6864142417907715s
Reputation | Calculation of the PageRank for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.02044963836669922s
Interlinking | Calculation of Degree of Connection for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 2.7894973754882812e-05s
Believability | Calculation of trust value for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.2159347534179688e-05s
INFO | --- Analysis for the-kazan-university-museum-as-linked-open-data-in-the-europeana-data-model took 5.658369779586792s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 4.363059997558594e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.24723100662231445s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.02042245864868164s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 7.2479248046875e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 7.867813110351562e-06s
INFO | --- Analysis for the-living-lod-cloud took 44.75086545944214s
Availability | SPARQL endpoint availability check for The MIDI Linked Data Cloud took 4.839897155761719e-05s
Availability | VoID file availability check for The MIDI Linked Data Cloud took 0.0003161430358886719s
Completeness | Calculation of interlinking completeness for The MIDI Linked Data Cloud took 0.27518320083618164s
Reputation | Calculation of the PageRank for The MIDI Linked Data Cloud took 0.020902156829833984s
Interlinking | Calculation of Degree of Connection for The MIDI Linked Data Cloud took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The MIDI Linked Data Cloud took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for The MIDI Linked Data Cloud took 3.504753112792969e-05s
Believability | Calculation of trust value for The MIDI Linked Data Cloud took 8.344650268554688e-06s
INFO | --- Analysis for the-midi-linked-data-cloud took 3.396627187728882s
Availability | SPARQL endpoint availability check for The View From took 0.10192584991455078s
Availability | VoID file availability check for The View From took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for The View From took 0.25283098220825195s
Reputation | Calculation of the PageRank for The View From took 0.020307540893554688s
Interlinking | Calculation of Degree of Connection for The View From took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The View From took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for The View From took 9.226799011230469e-05s
Believability | Calculation of trust value for The View From took 7.62939453125e-06s
INFO | --- Analysis for the-view-from took 2.9630849361419678s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 4.220008850097656e-05s
Availability | VoID file availability check for Thesaurus BNCF took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.27651262283325195s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.02181696891784668s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0009856224060058594s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 3.504753112792969e-05s
Believability | Calculation of trust value for Thesaurus BNCF took 7.867813110351562e-06s
INFO | --- Analysis for thesaurus-bncf took 3.346501588821411s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.267692565917969e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.25731921195983887s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.020246267318725586s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 2.8848648071289062e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 8.58306884765625e-06s
INFO | --- Analysis for thesaurus-datenwissen took 2.523627281188965s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.4789271354675293s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.27335500717163086s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.02079939842224121s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 8.606910705566406e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 8.106231689453125e-06s
INFO | --- Analysis for thesaurus-w took 4.150598049163818s
Availability | SPARQL endpoint availability check for theses.fr took 4.267692565917969e-05s
Availability | VoID file availability check for theses.fr took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for theses.fr took 0.27742695808410645s
Reputation | Calculation of the PageRank for theses.fr took 0.02076435089111328s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for theses.fr took 4.601478576660156e-05s
Believability | Calculation of trust value for theses.fr took 8.106231689453125e-06s
INFO | --- Analysis for thesesfr took 3.946110725402832s
Availability | SPARQL endpoint availability check for ThIST took 265.7962245941162s
Availability | VoID file availability check for ThIST took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for ThIST took 0.2566947937011719s
Reputation | Calculation of the PageRank for ThIST took 0.020926237106323242s
Interlinking | Calculation of Degree of Connection for ThIST took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for ThIST took 0.00010037422180175781s
Believability | Calculation of trust value for ThIST took 1.0728836059570312e-05s
INFO | --- Analysis for thist took 564.8185472488403s
Availability | SPARQL endpoint availability check for TIP took 40.041120529174805s
Availability | VoID file availability check for TIP took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for TIP took 0.7883398532867432s
Reputation | Calculation of the PageRank for TIP took 0.0214080810546875s
Interlinking | Calculation of Degree of Connection for TIP took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for TIP took 0.0009055137634277344s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00012731552124023438s
Believability | Calculation of trust value for TIP took 8.106231689453125e-06s
INFO | --- Analysis for tip took 104.13991093635559s
Availability | SPARQL endpoint availability check for Tourpedia took 4.076957702636719e-05s
Availability | VoID file availability check for Tourpedia took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for Tourpedia took 0.2757883071899414s
Reputation | Calculation of the PageRank for Tourpedia took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for Tourpedia took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Tourpedia took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Tourpedia took 2.7894973754882812e-05s
Believability | Calculation of trust value for Tourpedia took 7.152557373046875e-06s
INFO | --- Analysis for tourpedia took 3.3851943016052246s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 0.8997128009796143s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.7035355567932129s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.02079463005065918s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.458427429199219e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 9.298324584960938e-06s
INFO | --- Analysis for traditional-korean-medicine took 5.239060163497925s
Availability | SPARQL endpoint availability check for Traffic Scotland took 0.21036338806152344s
Availability | VoID file availability check for Traffic Scotland took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.26360034942626953s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.02048468589782715s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.409385681152344e-05s
Believability | Calculation of trust value for Traffic Scotland took 1.1205673217773438e-05s
INFO | --- Analysis for traffic-scotland took 3.1366994380950928s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 0.4302794933319092s
Availability | VoID file availability check for Transparency International Linked Data took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.24660563468933105s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.020592451095581055s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00010561943054199219s
Believability | Calculation of trust value for Transparency International Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for transparency-linked-data took 2.857757091522217s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 0.6493310928344727s
Availability | VoID file availability check for transport.data.gov.uk took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.717292308807373s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 9.012222290039062e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 5.0067901611328125e-06s
INFO | --- Analysis for transport-data-gov-uk took 4.271188259124756s
Availability | SPARQL endpoint availability check for OpenUpLabs Transport took 4.172325134277344e-05s
Availability | VoID file availability check for OpenUpLabs Transport took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for OpenUpLabs Transport took 0.2620565891265869s
Reputation | Calculation of the PageRank for OpenUpLabs Transport took 0.02061176300048828s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Transport took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Transport took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Transport took 3.3855438232421875e-05s
Believability | Calculation of trust value for OpenUpLabs Transport took 7.62939453125e-06s
INFO | --- Analysis for transport-openuplabs took 2.918527126312256s
Availability | SPARQL endpoint availability check for Twarql took 11.153229236602783s
Availability | VoID file availability check for Twarql took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for Twarql took 0.26765942573547363s
Reputation | Calculation of the PageRank for Twarql took 0.020108938217163086s
Interlinking | Calculation of Degree of Connection for Twarql took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Twarql took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Twarql took 6.914138793945312e-05s
Believability | Calculation of trust value for Twarql took 1.1205673217773438e-05s
INFO | --- Analysis for twarql took 13.557410717010498s
Availability | SPARQL endpoint availability check for TWC Data-gov took 4.291534423828125e-05s
Availability | VoID file availability check for TWC Data-gov took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.25728774070739746s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.020378589630126953s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 2.9325485229492188e-05s
Believability | Calculation of trust value for TWC Data-gov took 6.198883056640625e-06s
INFO | --- Analysis for twc-data-gov took 2.460451602935791s
Availability | SPARQL endpoint availability check for Tetherless World Constellation Demonstrations took 4.1484832763671875e-05s
Availability | VoID file availability check for Tetherless World Constellation Demonstrations took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Tetherless World Constellation Demonstrations took 0.26885366439819336s
Reputation | Calculation of the PageRank for Tetherless World Constellation Demonstrations took 0.020186901092529297s
Interlinking | Calculation of Degree of Connection for Tetherless World Constellation Demonstrations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Tetherless World Constellation Demonstrations took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Tetherless World Constellation Demonstrations took 2.86102294921875e-05s
Believability | Calculation of trust value for Tetherless World Constellation Demonstrations took 7.3909759521484375e-06s
INFO | --- Analysis for twc-demos took 2.9173314571380615s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.14272570610046387s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.25873446464538574s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 3.7670135498046875e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 1.811981201171875e-05s
INFO | --- Analysis for twc-healthdata took 15.837109327316284s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 4.295367956161499s
Availability | VoID file availability check for Instance Hub (all) took 0.00035381317138671875s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.28980565071105957s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.020494461059570312s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 7.534027099609375e-05s
Believability | Calculation of trust value for Instance Hub (all) took 8.106231689453125e-06s
INFO | --- Analysis for twc-hub took 66.08600234985352s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 0.14627552032470703s
Availability | VoID file availability check for IEEE VIS Source Data took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.3980093002319336s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.020792007446289062s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.00011467933654785156s
Believability | Calculation of trust value for IEEE VIS Source Data took 9.059906005859375e-06s
INFO | --- Analysis for twc-ieeevis took 116.83701777458191s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 4.458427429199219e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.24206876754760742s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.02066969871520996s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 9.131431579589844e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 5.7220458984375e-06s
INFO | --- Analysis for twc-logd took 2.4619359970092773s
Availability | SPARQL endpoint availability check for twc-opendap took 0.12893009185791016s
Availability | VoID file availability check for twc-opendap took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.28504085540771484s
Reputation | Calculation of the PageRank for twc-opendap took 0.020603418350219727s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 8.130073547363281e-05s
Believability | Calculation of trust value for twc-opendap took 8.821487426757812e-06s
INFO | --- Analysis for twc-opendap took 50.665788650512695s
Availability | SPARQL endpoint availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 4.267692565917969e-05s
Availability | VoID file availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.25986599922180176s
Reputation | Calculation of the PageRank for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 3.0279159545898438e-05s
Believability | Calculation of trust value for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 9.5367431640625e-06s
INFO | --- Analysis for tweetskb took 2.9006805419921875s
Availability | SPARQL endpoint availability check for Twitter Linked Data Service took 7.557868957519531e-05s
Availability | VoID file availability check for Twitter Linked Data Service took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for Twitter Linked Data Service took 0.2785613536834717s
Reputation | Calculation of the PageRank for Twitter Linked Data Service took 0.02068638801574707s
Interlinking | Calculation of Degree of Connection for Twitter Linked Data Service took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Twitter Linked Data Service took 0.0010428428649902344s
Interlinking | Calculation of Clustering coefficient for Twitter Linked Data Service took 3.695487976074219e-05s
Believability | Calculation of trust value for Twitter Linked Data Service took 7.867813110351562e-06s
INFO | --- Analysis for twitter-lids took 2.92618727684021s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.9102110862731934s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.0010409355163574219s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.26111865043640137s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.020519495010375977s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 3.7670135498046875e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 8.106231689453125e-06s
INFO | --- Analysis for ub-mannheim-linked-data took 4.690598964691162s
Availability | SPARQL endpoint availability check for Uberblic.org took 3.0253713130950928s
Availability | VoID file availability check for Uberblic.org took 0.0008141994476318359s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.27191781997680664s
Reputation | Calculation of the PageRank for Uberblic.org took 0.020643234252929688s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00011968612670898438s
Believability | Calculation of trust value for Uberblic.org took 1.4066696166992188e-05s
INFO | --- Analysis for uberblic took 10.060088872909546s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.14519238471984863s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.2665531635284424s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.02028369903564453s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 9.965896606445312e-05s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for uis-linked-data took 2.5717663764953613s
Availability | SPARQL endpoint availability check for UK Legislation took 4.220008850097656e-05s
Availability | VoID file availability check for UK Legislation took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.2519536018371582s
Reputation | Calculation of the PageRank for UK Legislation took 0.020680904388427734s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 9.036064147949219e-05s
Believability | Calculation of trust value for UK Legislation took 6.67572021484375e-06s
INFO | --- Analysis for uk-legislation-api took 3.423403024673462s
Availability | SPARQL endpoint availability check for UK Postcodes took 4.601478576660156e-05s
Availability | VoID file availability check for UK Postcodes took 0.0007216930389404297s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.2574138641357422s
Reputation | Calculation of the PageRank for UK Postcodes took 0.020546913146972656s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 5.841255187988281e-05s
Believability | Calculation of trust value for UK Postcodes took 8.344650268554688e-06s
INFO | --- Analysis for uk-postcodes took 22.36293601989746s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 7.891654968261719e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.2577550411224365s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.02041029930114746s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00013017654418945312s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 9.775161743164062e-06s
INFO | --- Analysis for umbel took 4.723043441772461s
Availability | SPARQL endpoint availability check for UMTHES took 4.38690185546875e-05s
Availability | VoID file availability check for UMTHES took 0.0007431507110595703s
Completeness | Calculation of interlinking completeness for UMTHES took 0.2781486511230469s
Reputation | Calculation of the PageRank for UMTHES took 0.02079629898071289s
Interlinking | Calculation of Degree of Connection for UMTHES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UMTHES took 0.0008165836334228516s
Interlinking | Calculation of Clustering coefficient for UMTHES took 4.76837158203125e-05s
Believability | Calculation of trust value for UMTHES took 5.7220458984375e-06s
INFO | --- Analysis for umthes took 6.275912284851074s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 1.6748003959655762s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.29410576820373535s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.02080845832824707s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 3.409385681152344e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 6.4373016357421875e-06s
INFO | --- Analysis for un-hazardous-numbers took 8.820396661758423s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 4.124641418457031e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.2634873390197754s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.020758390426635742s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 3.1948089599609375e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for unesco-thesaurus took 2.899322748184204s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 4.00543212890625e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.23942112922668457s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.020456790924072266s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 2.9325485229492188e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for unescothes took 2.883286476135254s
Availability | SPARQL endpoint availability check for UniProt took 1.8866534233093262s
Availability | VoID file availability check for UniProt took 0.0006039142608642578s
Extra | Recovery of all triples for UniProt took 22.128081798553467s
Performance | Total latancy measurement for UniProt took 3.909583568572998s
Amount of data | Number of triples check for UniProt took 0.3321826457977295s
Versatility | Languages check for UniProt took 1.498833179473877s
Interpretability | Number of blank nodes check for UniProt took 0.8172721862792969s
Security | Check HTTPS for UniProt took 0.17162513732910156s
Interpretability | RDF structures check for UniProt took 0.18208765983581543s
Versatility | Serialization formats check for UniProt took 0.16577434539794922s
Availability | RDF dump link check for UniProt took 0.16980862617492676s
License | MR license check for UniProt took 0.18567132949829102s
License | HR license check for UniProt took 0.19019031524658203s
Amount of data | Number of property check for UniProt took 0.18485713005065918s
Understandability | Number of label check for UniProt took 0.1919384002685547s
Understandability | URI regex check for UniProt took 0.3364090919494629s
Understandability | Vocabs check for UniProt took 0.17480754852294922s
Verifiability | Authors check for UniProt took 0.18172502517700195s
Verifiability | Publishers check for UniProt took 0.17206907272338867s
Performance | Throughput check for UniProt took 18.823798894882202s
Amount of data | Check the number of entities for UniProt took 0.0007045269012451172s
Verifiability | Contribs. check for UniProt took 0.22146201133728027s
Interlinking | sameAs chians check for UniProt took 0.16002225875854492s
Interlinking | skos check for UniProt took 0.1782970428466797s
Interlinking | skos check for UniProt took 0.1474447250366211s
Timeliness | dataset update frequency check for UniProt took 0.17453551292419434s
Currency | Creation date check for UniProt took 0.34337687492370605s
Currency | Modification date check for UniProt took 0.32607269287109375s
Rep.Conc. | URIs length for UniProt took 114.23842263221741s
Interoperability | New vocabularies check for UniProt took 2.384185791015625e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.15821313858032227s
Accuracy | Check Datatype consistency for UniProt took 7.461832761764526s
Consistency | Disjoint class check for UniProt took 0.18543553352355957s
Consistency | Check Ontology hijacking for UniProt took 0.15923023223876953s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.7600514888763428s
Conciseness | Check Extensional conciseness for UniProt took 2.690075159072876s
Security | Sign check for UniProt took 0.17391514778137207s
Availability | Check URIs Dereferenciability for UniProt took 4.3856422901153564s
Completeness | Calculation of interlinking completeness for UniProt took 1.3099536895751953s
Reputation | Calculation of the PageRank for UniProt took 0.020912647247314453s
Interlinking | Calculation of Degree of Connection for UniProt took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for UniProt took 5.1021575927734375e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 9.5367431640625e-07s
Believability | Calculation of trust value for UniProt took 9.059906005859375e-06s
INFO | --- Analysis for uniprot took 718.3309233188629s
Availability | SPARQL endpoint availability check for UniProt citations took 4.1484832763671875e-05s
Availability | VoID file availability check for UniProt citations took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for UniProt citations took 0.7199757099151611s
Reputation | Calculation of the PageRank for UniProt citations took 0.02031874656677246s
Interlinking | Calculation of Degree of Connection for UniProt citations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UniProt citations took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for UniProt citations took 2.7894973754882812e-05s
Believability | Calculation of trust value for UniProt citations took 7.62939453125e-06s
INFO | --- Analysis for uniprot-citations took 5.163041114807129s
Availability | SPARQL endpoint availability check for UniProt databases took 7.653236389160156e-05s
Availability | VoID file availability check for UniProt databases took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for UniProt databases took 0.2616302967071533s
Reputation | Calculation of the PageRank for UniProt databases took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for UniProt databases took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UniProt databases took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for UniProt databases took 3.218650817871094e-05s
Believability | Calculation of trust value for UniProt databases took 6.67572021484375e-06s
INFO | --- Analysis for uniprot-databases took 3.3043389320373535s
Availability | SPARQL endpoint availability check for uniprot-metadata took 5.650520324707031e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.2569601535797119s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.0201871395111084s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 5.91278076171875e-05s
Believability | Calculation of trust value for uniprot-metadata took 7.152557373046875e-06s
INFO | --- Analysis for uniprot-metadata took 3.777811050415039s
Availability | SPARQL endpoint availability check for UniProtKB Taxonomy took 4.076957702636719e-05s
Availability | VoID file availability check for UniProtKB Taxonomy took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for UniProtKB Taxonomy took 0.24539780616760254s
Reputation | Calculation of the PageRank for UniProtKB Taxonomy took 0.020296573638916016s
Interlinking | Calculation of Degree of Connection for UniProtKB Taxonomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UniProtKB Taxonomy took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for UniProtKB Taxonomy took 2.9087066650390625e-05s
Believability | Calculation of trust value for UniProtKB Taxonomy took 8.821487426757812e-06s
INFO | --- Analysis for uniprot-taxonomy took 3.7106268405914307s
Availability | SPARQL endpoint availability check for UniProt UniParc took 4.100799560546875e-05s
Availability | VoID file availability check for UniProt UniParc took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for UniProt UniParc took 0.244093656539917s
Reputation | Calculation of the PageRank for UniProt UniParc took 0.020330190658569336s
Interlinking | Calculation of Degree of Connection for UniProt UniParc took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UniProt UniParc took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for UniProt UniParc took 3.0040740966796875e-05s
Believability | Calculation of trust value for UniProt UniParc took 6.9141387939453125e-06s
INFO | --- Analysis for uniprot-uniparc took 2.757465362548828s
Availability | SPARQL endpoint availability check for UniProt UniPathway took 4.172325134277344e-05s
Availability | VoID file availability check for UniProt UniPathway took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for UniProt UniPathway took 0.27176547050476074s
Reputation | Calculation of the PageRank for UniProt UniPathway took 0.020742416381835938s
Interlinking | Calculation of Degree of Connection for UniProt UniPathway took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UniProt UniPathway took 0.0008494853973388672s
Interlinking | Calculation of Clustering coefficient for UniProt UniPathway took 3.337860107421875e-05s
Believability | Calculation of trust value for UniProt UniPathway took 6.9141387939453125e-06s
INFO | --- Analysis for uniprot-unipathway took 2.832207441329956s
Availability | SPARQL endpoint availability check for UniProtKB took 1.493006944656372s
Availability | VoID file availability check for UniProtKB took 0.0002846717834472656s
Extra | Recovery of all triples for UniProtKB took 13.245208740234375s
Performance | Total latancy measurement for UniProtKB took 3.754401445388794s
Amount of data | Number of triples check for UniProtKB took 0.15793943405151367s
Interoperability | New terms check for UniProtKB took 1.5154173374176025s
Versatility | Languages check for UniProtKB took 1.1510212421417236s
Interpretability | Number of blank nodes check for UniProtKB took 0.575070858001709s
Interpretability | RDF structures check for UniProtKB took 0.1852247714996338s
Versatility | Serialization formats check for UniProtKB took 0.1054985523223877s
Availability | RDF dump link check for UniProtKB took 0.1037435531616211s
License | MR license check for UniProtKB took 0.0985260009765625s
License | HR license check for UniProtKB took 300.102618932724s
Amount of data | Number of property check for UniProtKB took 0.09198904037475586s
Understandability | Number of label check for UniProtKB took 33.66506886482239s
Understandability | URI regex check for UniProtKB took 0.20052146911621094s
Understandability | Vocabs check for UniProtKB took 0.11132049560546875s
Verifiability | Authors check for UniProtKB took 0.09678435325622559s
Verifiability | Publishers check for UniProtKB took 0.11644315719604492s
Performance | Throughput check for UniProtKB took 15.360842227935791s
Amount of data | Check the number of entities for UniProtKB took 7.319450378417969e-05s
Verifiability | Contribs. check for UniProtKB took 0.12105536460876465s
Interlinking | sameAs chians check for UniProtKB took 2.6965160369873047s
Interlinking | skos check for UniProtKB took 0.1559772491455078s
Interlinking | skos check for UniProtKB took 0.16514825820922852s
Timeliness | dataset update frequency check for UniProtKB took 0.0824272632598877s
Currency | Creation date check for UniProtKB took 0.21387338638305664s
Currency | Modification date check for UniProtKB took 0.27089977264404297s
Rep.Conc. | URIs length for UniProtKB took 116.46734976768494s
Interoperability | New vocabularies check for UniProtKB took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for UniProtKB took 0.09204912185668945s
Accuracy | Check Functional Property for UniProtKB took 0.09113192558288574s
Accuracy | Check Inverse Functional Property for UniProtKB took 0.08036422729492188s
Accuracy | Check Empty annotation labels for UniProtKB took 14.917232036590576s
Accuracy | Check White space in annotation for UniProtKB took 2.5449180603027344s
Accuracy | Check Datatype consistency for UniProtKB took 7.402083158493042s
Consistency | Disjoint class check for UniProtKB took 0.10299158096313477s
Consistency | Check Misplaced properties for UniProtKB took 3.992659091949463s
Consistency | Check Ontology hijacking for UniProtKB took 8.194787979125977s
Consistency | Check Invalid usage of undefined classes for UniProtKB took 19950.539180517197s
Consistency | Check Invalid usage of undefined properties for UniProtKB took 1.7026519775390625s
Conciseness | Check Extensional conciseness for UniProtKB took 2.6727378368377686s
Conciseness | Check Intensional conciseness for UniProtKB took 0.12520503997802734s
Security | Sign check for UniProtKB took 0.09918498992919922s
Availability | Check URIs Dereferenciability for UniProtKB took 4.720808267593384s
Completeness | Calculation of interlinking completeness for UniProtKB took 1.2309372425079346s
Reputation | Calculation of the PageRank for UniProtKB took 0.020806550979614258s
Interlinking | Calculation of Degree of Connection for UniProtKB took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 6.461143493652344e-05s
Interoperability | Check the re-using of existing vocabs for UniProtKB took 2.1457672119140625e-06s
Believability | Calculation of trust value for UniProtKB took 7.62939453125e-06s
INFO | --- Analysis for uniprotkb took 20976.020042419434s
Availability | SPARQL endpoint availability check for UniProt UniRef took 4.1484832763671875e-05s
Availability | VoID file availability check for UniProt UniRef took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for UniProt UniRef took 0.6993229389190674s
Reputation | Calculation of the PageRank for UniProt UniRef took 0.020497798919677734s
Interlinking | Calculation of Degree of Connection for UniProt UniRef took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UniProt UniRef took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for UniProt UniRef took 2.8133392333984375e-05s
Believability | Calculation of trust value for UniProt UniRef took 8.344650268554688e-06s
INFO | --- Analysis for uniref took 5.191000938415527s
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.00024628639221191406s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.2731597423553467s
Reputation | Calculation of the PageRank for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.02021503448486328s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 2.765655517578125e-05s
Believability | Calculation of trust value for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 7.867813110351562e-06s
INFO | --- Analysis for unistat-kis-2011-2012-in-rdf-key-information-set-uk-universities took 4.416579484939575s
Availability | SPARQL endpoint availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 7.677078247070312e-05s
Availability | VoID file availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.00041604042053222656s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.26110100746154785s
Reputation | Calculation of the PageRank for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 3.075599670410156e-05s
Believability | Calculation of trust value for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 7.3909759521484375e-06s
INFO | --- Analysis for unistat-kis-in-rdf-key-information-set-uk-universities took 3.838862419128418s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 5.5789947509765625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.2740020751953125s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.020531654357910156s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 13.370733737945557s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.28185415267944336s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.02025914192199707s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 4.323217153549194s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.28721165657043457s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.02031111717224121s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 18.127941370010376s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.0006742477416992188s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.2654125690460205s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.02065110206604004s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-basque took 13.248986721038818s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.0008392333984375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.27520084381103516s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.02042555809020996s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 6.508827209472656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 13.301275491714478s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0007066726684570312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.24948573112487793s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.020393848419189453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 13.393796682357788s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.27582263946533203s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.020425796508789062s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 9.72747802734375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 4.564312934875488s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 5.054473876953125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0006864070892333984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.2669222354888916s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.020275592803955078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 13.159583330154419s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.2801079750061035s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.020382165908813477s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0008556842803955078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 6.4373016357421875e-06s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 13.255472421646118s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 4.9114227294921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.0007076263427734375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.2692911624908447s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.020467042922973633s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech took 13.35202407836914s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.268186092376709s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.02046823501586914s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 5.245208740234375e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 13.022096872329712s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.2516820430755615s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.020380735397338867s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 8.821487426757812e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 13.060058832168579s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.2546374797821045s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.020401477813720703s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 5.245208740234375e-06s
INFO | --- Analysis for universal-dependencies-treebank-danish took 4.0041115283966064s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.2724623680114746s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.02027153968811035s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 13.24505615234375s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.0007746219635009766s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.27689218521118164s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.02100539207458496s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 4.2438507080078125e-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 13.101630687713623s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 5.054473876953125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.27750682830810547s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.020729780197143555s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-english took 13.23134708404541s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.0007331371307373047s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.2738316059112549s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.020717144012451172s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 13.04415249824524s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.27393102645874023s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.020795583724975586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0008575916290283203s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 4.267692565917969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 12.959697484970093s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.0007171630859375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.2535557746887207s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.020730257034301758s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 13.131948471069336s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.25306153297424316s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.0208132266998291s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 4.673004150390625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 4.032741069793701s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 8.273124694824219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.2684485912322998s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.020284652709960938s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 4.3392181396484375e-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 13.198498010635376s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.27292633056640625s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.020274877548217773s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-french took 13.248533964157104s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 6.461143493652344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0007450580596923828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.2717442512512207s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.02082991600036621s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician took 13.218003988265991s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.2676055431365967s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 4.00543212890625e-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 3.8888869285583496s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.28644847869873047s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 4.4345855712890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 9.059906005859375e-06s
INFO | --- Analysis for universal-dependencies-treebank-german took 3.999049663543701s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.0007038116455078125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.25560951232910156s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.020691871643066406s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 4.031490802764893s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.0005807876586914062s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.28208017349243164s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.020663976669311523s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-greek took 3.9711925983428955s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0007188320159912109s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.2534639835357666s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.02057957649230957s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 13.138706684112549s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0007145404815673828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.2894272804260254s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.021025419235229492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 8.821487426757812e-06s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 13.327040195465088s
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.0005943775177001953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.26485705375671387s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.02046680450439453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 3.9536213874816895s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.2808811664581299s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.020383358001708984s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 13.258216857910156s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.2827768325805664s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.020374536514282227s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-irish took 4.026153087615967s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0006835460662841797s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.26187586784362793s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.0207059383392334s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0009481906890869141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-italian took 13.335942029953003s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.0007367134094238281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.25869274139404297s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.020526647567749023s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 5.9604644775390625e-06s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 13.295811891555786s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.25706958770751953s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.020279645919799805s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 4.029273986816406e-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 3.800779104232788s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 4.6253204345703125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.2691624164581299s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.020328760147094727s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 3.6716461181640625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 13.299165487289429s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0006728172302246094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.2755005359649658s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.02053689956665039s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0009596347808837891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 4.38690185546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin took 6.667674541473389s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.0006940364837646484s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.29221224784851074s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 13.162699937820435s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0008232593536376953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.3893849849700928s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.020507097244262695s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 4.887580871582031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 1.8596649169921875e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 13.312675714492798s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.2790045738220215s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.020399093627929688s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 13.296571969985962s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 5.745887756347656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.253695011138916s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.020416259765625s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 13.044251918792725s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 4.839897155761719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.31800222396850586s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.02041459083557129s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 3.6716461181640625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 13.227648258209229s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.2701406478881836s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.02050304412841797s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-persian took 5.4330830574035645s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.0006763935089111328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.28392529487609863s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.02098393440246582s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007925033569335938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 5.030632019042969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-polish took 13.285759449005127s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.0007164478302001953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.25867152214050293s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.020652294158935547s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 12.786466598510742s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.2863445281982422s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.02043437957763672s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 13.064367771148682s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0006606578826904297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.28336548805236816s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.02028489112854004s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 3.910064697265625e-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 13.366127729415894s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.57763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0007307529449462891s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.24454975128173828s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.02184128761291504s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 13.150602579116821s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 5.698204040527344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.0007941722869873047s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.2903251647949219s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.021721363067626953s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 4.76837158203125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian took 13.28945779800415s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.2524852752685547s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.020757198333740234s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 4.506111145019531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 3.907641649246216s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 4.601478576660156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.0006799697875976562s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.27175235748291016s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.020847320556640625s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 13.271753072738647s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 7.081031799316406e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.27275824546813965s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.020165205001831055s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 13.275987386703491s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.0006821155548095703s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.25271010398864746s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.0204925537109375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 6.198883056640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 13.252217054367065s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.000713348388671875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.29762768745422363s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.020724773406982422s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 6.198883056640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 13.037453413009644s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.2652590274810791s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.020415782928466797s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 6.4373016357421875e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 13.092567443847656s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.27526426315307617s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.020241260528564453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 5.7220458984375e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 13.062994480133057s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.2707078456878662s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.020409345626831055s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 4.314911603927612s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.00039267539978027344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.26230621337890625s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.020287752151489258s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 5.4836273193359375e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 4.064432621002197s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.2749137878417969s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.02029585838317871s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 5.7220458984375e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 13.386532068252563s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.00074005126953125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.2688624858856201s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.020308256149291992s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 4.506111145019531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 5.7220458984375e-06s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 16.296037912368774s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.27445054054260254s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.020364761352539062s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 3.6716461181640625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 6.198883056640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 13.26047658920288s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.000579833984375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.2767620086669922s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.020624160766601562s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 13.314816236495972s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.26993584632873535s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.02019810676574707s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 13.362138986587524s
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.000766754150390625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.32191944122314453s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.020450115203857422s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 4.792213439941406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 13.300357103347778s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 4.553794860839844e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.2956118583679199s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.020247936248779297s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 6.723403930664062e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 7.3909759521484375e-06s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 6.4900665283203125s
Availability | SPARQL endpoint availability check for Universitat Pompeu Fabra - linked data took 5.316734313964844e-05s
Availability | VoID file availability check for Universitat Pompeu Fabra - linked data took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for Universitat Pompeu Fabra - linked data took 0.28254270553588867s
Reputation | Calculation of the PageRank for Universitat Pompeu Fabra - linked data took 0.021112918853759766s
Interlinking | Calculation of Degree of Connection for Universitat Pompeu Fabra - linked data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universitat Pompeu Fabra - linked data took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Universitat Pompeu Fabra - linked data took 3.314018249511719e-05s
Believability | Calculation of trust value for Universitat Pompeu Fabra - linked data took 8.58306884765625e-06s
INFO | --- Analysis for universitat-pompeu-fabra-linked-data took 2.96454119682312s
Availability | SPARQL endpoint availability check for University of Bristol took 4.172325134277344e-05s
Availability | VoID file availability check for University of Bristol took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for University of Bristol took 0.24947857856750488s
Reputation | Calculation of the PageRank for University of Bristol took 0.020510435104370117s
Interlinking | Calculation of Degree of Connection for University of Bristol took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for University of Bristol took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for University of Bristol took 3.1948089599609375e-05s
Believability | Calculation of trust value for University of Bristol took 7.3909759521484375e-06s
INFO | --- Analysis for university-of-bristol took 2.8847198486328125s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 4.3392181396484375e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.2822287082672119s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.02057480812072754s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 5.030632019042969e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 8.344650268554688e-06s
INFO | --- Analysis for university-plymouth-reading-lists took 3.0214884281158447s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 4.506111145019531e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.27726244926452637s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.021008729934692383s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 3.9577484130859375e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 6.4373016357421875e-06s
INFO | --- Analysis for university-sussex-reading-lists took 2.83506178855896s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 0.14322638511657715s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.2668299674987793s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.02084660530090332s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 7.843971252441406e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 6.67572021484375e-06s
INFO | --- Analysis for unodc took 2.726560592651367s
Availability | SPARQL endpoint availability check for URIBurner took 0.7714810371398926s
Availability | VoID file availability check for URIBurner took 0.0006461143493652344s
Extra | Recovery of all triples for URIBurner took 121.03749918937683s
Performance | Total latancy measurement for URIBurner took 1.2490923404693604s
Amount of data | Number of triples check for URIBurner took 3.2908174991607666s
Interoperability | New terms check for URIBurner took 55.561238288879395s
Versatility | Languages check for URIBurner took 120.68386173248291s
Interpretability | Number of blank nodes check for URIBurner took 3.757719039916992s
Security | Check HTTPS for URIBurner took 0.43158960342407227s
Interpretability | RDF structures check for URIBurner took 3.0038902759552s
Versatility | Serialization formats check for URIBurner took 24.903850317001343s
Availability | RDF dump link check for URIBurner took 48.584816217422485s
License | MR license check for URIBurner took 1.7113163471221924s
License | HR license check for URIBurner took 120.90880608558655s
Amount of data | Number of property check for URIBurner took 0.4631218910217285s
Understandability | Number of label check for URIBurner took 3.2929039001464844s
Understandability | URI regex check for URIBurner took 0.9300203323364258s
Understandability | Vocabs check for URIBurner took 0.4874091148376465s
Verifiability | Authors check for URIBurner took 0.6389045715332031s
Verifiability | Publishers check for URIBurner took 0.5076849460601807s
Performance | Throughput check for URIBurner took 11.598937749862671s
Amount of data | Check the number of entities for URIBurner took 8.893013000488281e-05s
Verifiability | Contribs. check for URIBurner took 0.5046236515045166s
Interlinking | sameAs chians check for URIBurner took 1.7686824798583984s
Interlinking | skos check for URIBurner took 1.0356385707855225s
Interlinking | skos check for URIBurner took 0.2829115390777588s
Timeliness | dataset update frequency check for URIBurner took 2.3903820514678955s
Currency | Creation date check for URIBurner took 14.920810222625732s
Currency | Modification date check for URIBurner took 1.1804709434509277s
Rep.Conc. | URIs length for URIBurner took 245.67636370658875s
Consistency | Deprecated classes/propertiers check for URIBurner took 0.3834874629974365s
Accuracy | Check Functional Property for URIBurner took 0.36169862747192383s
Accuracy | Check Inverse Functional Property for URIBurner took 0.3416781425476074s
Accuracy | Check Empty annotation labels for URIBurner took 74.95190262794495s
Accuracy | Check White space in annotation for URIBurner took 0.18273019790649414s
Consistency | Disjoint class check for URIBurner took 0.3857228755950928s
Consistency | Check Misplaced properties for URIBurner took 335.5791425704956s
Consistency | Check Ontology hijacking for URIBurner took 122.04093527793884s
Consistency | Check Invalid usage of undefined properties for URIBurner took 122.22709965705872s
Conciseness | Check Extensional conciseness for URIBurner took 0.0001666545867919922s
Security | Sign check for URIBurner took 0.49109315872192383s
Completeness | Calculation of interlinking completeness for URIBurner took 1.4480395317077637s
Reputation | Calculation of the PageRank for URIBurner took 0.020976781845092773s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for URIBurner took 0.0001049041748046875s
Believability | Calculation of trust value for URIBurner took 1.4066696166992188e-05s
INFO | --- Analysis for uriburner took 6778.167158842087s
Availability | SPARQL endpoint availability check for US Political Violence took 4.1484832763671875e-05s
Availability | VoID file availability check for US Political Violence took 0.00033092498779296875s
Completeness | Calculation of interlinking completeness for US Political Violence took 0.288104772567749s
Reputation | Calculation of the PageRank for US Political Violence took 0.021323442459106445s
Interlinking | Calculation of Degree of Connection for US Political Violence took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for US Political Violence took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for US Political Violence took 3.075599670410156e-05s
Believability | Calculation of trust value for US Political Violence took 8.821487426757812e-06s
INFO | --- Analysis for us-political-violence took 5.231438159942627s
Availability | SPARQL endpoint availability check for USAGE review corpus took 0.6487782001495361s
Availability | VoID file availability check for USAGE review corpus took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.26818013191223145s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.020408153533935547s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 3.0994415283203125e-05s
Believability | Calculation of trust value for USAGE review corpus took 8.58306884765625e-06s
INFO | --- Analysis for usage-review-corpus took 4.661413908004761s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 5.6725873947143555s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.7231106758117676s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.020521163940429688s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 7.414817810058594e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 8.58306884765625e-06s
INFO | --- Analysis for utpl-lod took 12.122386693954468s
Availability | SPARQL endpoint availability check for Výkazy zisku a ztrát obcí ČR took 4.1961669921875e-05s
Availability | VoID file availability check for Výkazy zisku a ztrát obcí ČR took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Výkazy zisku a ztrát obcí ČR took 0.2823803424835205s
Reputation | Calculation of the PageRank for Výkazy zisku a ztrát obcí ČR took 0.02087688446044922s
Interlinking | Calculation of Degree of Connection for Výkazy zisku a ztrát obcí ČR took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Výkazy zisku a ztrát obcí ČR took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Výkazy zisku a ztrát obcí ČR took 3.075599670410156e-05s
Believability | Calculation of trust value for Výkazy zisku a ztrát obcí ČR took 9.059906005859375e-06s
INFO | --- Analysis for v-kazy-zisku-a-ztr-t-obc---r took 3.4639577865600586s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 6.351113319396973s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.0007328987121582031s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.2658400535583496s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.02027106285095215s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 0.00010514259338378906s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 8.58306884765625e-06s
INFO | --- Analysis for verrijktkoninkrijk took 14.923938274383545s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 4.38690185546875e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0007669925689697266s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.24790358543395996s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.02086162567138672s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0009808540344238281s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.00020623207092285156s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 8.344650268554688e-06s
INFO | --- Analysis for viaf took 19.299647569656372s
Availability | SPARQL endpoint availability check for Vías Públicas de Zaragoza (Localización) took 4.172325134277344e-05s
Availability | VoID file availability check for Vías Públicas de Zaragoza (Localización) took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Vías Públicas de Zaragoza (Localización) took 0.24298715591430664s
Reputation | Calculation of the PageRank for Vías Públicas de Zaragoza (Localización) took 0.020720243453979492s
Interlinking | Calculation of Degree of Connection for Vías Públicas de Zaragoza (Localización) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Vías Públicas de Zaragoza (Localización) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Vías Públicas de Zaragoza (Localización) took 3.123283386230469e-05s
Believability | Calculation of trust value for Vías Públicas de Zaragoza (Localización) took 8.821487426757812e-06s
INFO | --- Analysis for vias-publicas-zaragoza took 2.9177541732788086s
Availability | SPARQL endpoint availability check for vimeo.videoobject took 4.363059997558594e-05s
Availability | VoID file availability check for vimeo.videoobject took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for vimeo.videoobject took 0.24971723556518555s
Reputation | Calculation of the PageRank for vimeo.videoobject took 0.020780086517333984s
Interlinking | Calculation of Degree of Connection for vimeo.videoobject took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for vimeo.videoobject took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for vimeo.videoobject took 3.24249267578125e-05s
Believability | Calculation of trust value for vimeo.videoobject took 8.344650268554688e-06s
INFO | --- Analysis for vimeo_videoobject took 3.4550704956054688s
Availability | SPARQL endpoint availability check for VIVO took 4.2438507080078125e-05s
Availability | VoID file availability check for VIVO took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for VIVO took 0.2664153575897217s
Reputation | Calculation of the PageRank for VIVO took 0.02048945426940918s
Interlinking | Calculation of Degree of Connection for VIVO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for VIVO took 6.794929504394531e-05s
Believability | Calculation of trust value for VIVO took 7.62939453125e-06s
INFO | --- Analysis for vivo took 5.564897537231445s
Availability | SPARQL endpoint availability check for VIVO Cornell took 4.1961669921875e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.27193379402160645s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.020537137985229492s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 8.535385131835938e-05s
Believability | Calculation of trust value for VIVO Cornell took 6.9141387939453125e-06s
INFO | --- Analysis for vivo-cornell-university took 6.044100284576416s
Availability | SPARQL endpoint availability check for VIVO CU-Boulder took 4.553794860839844e-05s
Availability | VoID file availability check for VIVO CU-Boulder took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for VIVO CU-Boulder took 0.25817131996154785s
Reputation | Calculation of the PageRank for VIVO CU-Boulder took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for VIVO CU-Boulder took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VIVO CU-Boulder took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for VIVO CU-Boulder took 3.0279159545898438e-05s
Believability | Calculation of trust value for VIVO CU-Boulder took 7.152557373046875e-06s
INFO | --- Analysis for vivo-cu-boulder took 3.0579991340637207s
Availability | SPARQL endpoint availability check for VIVO Indiana took 4.220008850097656e-05s
Availability | VoID file availability check for VIVO Indiana took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.2528223991394043s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 8.20159912109375e-05s
Believability | Calculation of trust value for VIVO Indiana took 7.62939453125e-06s
INFO | --- Analysis for vivo-indiana-university took 3.033480167388916s
Availability | SPARQL endpoint availability check for VIVO Ponce took 4.1961669921875e-05s
Availability | VoID file availability check for VIVO Ponce took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.27581262588500977s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.02071666717529297s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.552436828613281e-05s
Believability | Calculation of trust value for VIVO Ponce took 1.1682510375976562e-05s
INFO | --- Analysis for vivo-ponce took 2.9540696144104004s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 4.315376281738281e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.0010714530944824219s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.29223060607910156s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.02062392234802246s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 4.220008850097656e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 7.867813110351562e-06s
INFO | --- Analysis for vivo-scripps-research-institute took 3.398714542388916s
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.00048041343688964844s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.2556304931640625s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.02061629295349121s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 9.870529174804688e-05s
Believability | Calculation of trust value for VIVO University of Florida took 8.106231689453125e-06s
INFO | --- Analysis for vivo-university-of-florida took 2.624436140060425s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 5.698204040527344e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.00039768218994140625s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.26918983459472656s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.02052760124206543s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 3.600120544433594e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 2.002716064453125e-05s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 2.856076240539551s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 4.1961669921875e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.2726473808288574s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.02053356170654297s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 3.5762786865234375e-05s
Believability | Calculation of trust value for VIVO WUSTL took 7.3909759521484375e-06s
INFO | --- Analysis for vivo-wustl took 2.939772605895996s
Availability | SPARQL endpoint availability check for vivo2doi took 5.054473876953125e-05s
Availability | VoID file availability check for vivo2doi took 0.0005943775177001953s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.25540614128112793s
Reputation | Calculation of the PageRank for vivo2doi took 0.02057480812072754s
Interlinking | Calculation of Degree of Connection for vivo2doi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 4.029273986816406e-05s
Believability | Calculation of trust value for vivo2doi took 7.152557373046875e-06s
INFO | --- Analysis for vivo2doi took 24.304882526397705s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 9.775161743164062e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.282634973526001s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.020451068878173828s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 6.628036499023438e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 8.821487426757812e-06s
INFO | --- Analysis for vu-wordnet took 14.563266038894653s
Availability | SPARQL endpoint availability check for vulnerapedia took 0.11076712608337402s
Availability | VoID file availability check for vulnerapedia took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.27994418144226074s
Reputation | Calculation of the PageRank for vulnerapedia took 0.020420074462890625s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 6.961822509765625e-05s
Believability | Calculation of trust value for vulnerapedia took 7.3909759521484375e-06s
INFO | --- Analysis for vulnerapedia took 3.0615792274475098s
Availability | SPARQL endpoint availability check for W3C took 4.363059997558594e-05s
Availability | VoID file availability check for W3C took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for W3C took 0.2759065628051758s
Reputation | Calculation of the PageRank for W3C took 0.020476579666137695s
Interlinking | Calculation of Degree of Connection for W3C took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for W3C took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for W3C took 0.00014138221740722656s
Believability | Calculation of trust value for W3C took 1.1682510375976562e-05s
INFO | --- Analysis for w3c took 2.575153112411499s
Availability | SPARQL endpoint availability check for W3C Provenance Incubator Group Vocabulary Mappings took 6.318092346191406e-05s
Availability | VoID file availability check for W3C Provenance Incubator Group Vocabulary Mappings took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for W3C Provenance Incubator Group Vocabulary Mappings took 0.2451035976409912s
Reputation | Calculation of the PageRank for W3C Provenance Incubator Group Vocabulary Mappings took 0.02041482925415039s
Interlinking | Calculation of Degree of Connection for W3C Provenance Incubator Group Vocabulary Mappings took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for W3C Provenance Incubator Group Vocabulary Mappings took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for W3C Provenance Incubator Group Vocabulary Mappings took 2.8371810913085938e-05s
Believability | Calculation of trust value for W3C Provenance Incubator Group Vocabulary Mappings took 8.106231689453125e-06s
INFO | --- Analysis for w3c-provenance-incubator-group-vocabulary-mappings took 2.919588804244995s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 6.747245788574219e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.2924306392669678s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.020351886749267578s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00010991096496582031s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 8.106231689453125e-06s
INFO | --- Analysis for w3c-wordnet took 3.2193145751953125s
Availability | SPARQL endpoint availability check for WarSampo took 0.3669555187225342s
Availability | VoID file availability check for WarSampo took 0.0007796287536621094s
Extra | Recovery of all triples for WarSampo took 170.18205666542053s
Performance | Total latancy measurement for WarSampo took 0.8449671268463135s
Amount of data | Number of triples check for WarSampo took 18.147128582000732s
Interoperability | New terms check for WarSampo took 3.7363674640655518s
Versatility | Languages check for WarSampo took 50.78544354438782s
Interpretability | Number of blank nodes check for WarSampo took 17.092841148376465s
Security | Check HTTPS for WarSampo took 0.4048445224761963s
Interpretability | RDF structures check for WarSampo took 0.19339561462402344s
Versatility | Serialization formats check for WarSampo took 0.19294047355651855s
Availability | RDF dump link check for WarSampo took 1.0637338161468506s
License | MR license check for WarSampo took 0.19414544105529785s
License | HR license check for WarSampo took 45.39260220527649s
Amount of data | Number of property check for WarSampo took 0.20920634269714355s
Understandability | Number of label check for WarSampo took 10.731175661087036s
Understandability | URI regex check for WarSampo took 0.38979578018188477s
Understandability | Vocabs check for WarSampo took 0.16759037971496582s
Verifiability | Authors check for WarSampo took 0.19387149810791016s
Verifiability | Publishers check for WarSampo took 0.19032931327819824s
Performance | Throughput check for WarSampo took 11.105936288833618s
Amount of data | Check the number of entities for WarSampo took 15.869844198226929s
Verifiability | Contribs. check for WarSampo took 0.19910407066345215s
Interlinking | sameAs chians check for WarSampo took 0.2220299243927002s
Interlinking | skos check for WarSampo took 0.20642590522766113s
Interlinking | skos check for WarSampo took 0.17019939422607422s
Timeliness | dataset update frequency check for WarSampo took 0.17570924758911133s
Currency | Creation date check for WarSampo took 0.40004467964172363s
Currency | Modification date check for WarSampo took 0.38857054710388184s
Rep.Conc. | URIs length for WarSampo took 94.25535869598389s
Interoperability | New vocabularies check for WarSampo took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.20681309700012207s
Accuracy | Check Functional Property for WarSampo took 0.1913008689880371s
Accuracy | Check Inverse Functional Property for WarSampo took 0.15980219841003418s
Accuracy | Check Empty annotation labels for WarSampo took 56.83159947395325s
Accuracy | Check White space in annotation for WarSampo took 2.255781650543213s
Accuracy | Check Datatype consistency for WarSampo took 5.392000436782837s
Consistency | Disjoint class check for WarSampo took 0.20606160163879395s
Consistency | Check Misplaced properties for WarSampo took 20.174774885177612s
Consistency | Check Ontology hijacking for WarSampo took 60.719050884246826s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.4361965656280518s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.6951613426208496s
Conciseness | Check Extensional conciseness for WarSampo took 2.834444284439087s
Conciseness | Check Intensional conciseness for WarSampo took 0.30276989936828613s
Security | Sign check for WarSampo took 0.17645955085754395s
Availability | Check URIs Dereferenciability for WarSampo took 2.639564275741577s
Completeness | Calculation of interlinking completeness for WarSampo took 0.46736860275268555s
Reputation | Calculation of the PageRank for WarSampo took 0.02109074592590332s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for WarSampo took 8.630752563476562e-05s
Interoperability | Check the re-using of existing vocabs for WarSampo took 1.9073486328125e-06s
Believability | Calculation of trust value for WarSampo took 8.821487426757812e-06s
INFO | --- Analysis for warsampo took 1187.6591370105743s
Availability | SPARQL endpoint availability check for WebIsALOD took 0.40781307220458984s
Availability | VoID file availability check for WebIsALOD took 0.0005939006805419922s
Extra | Recovery of all triples for WebIsALOD took 2.191890239715576s
Performance | Total latancy measurement for WebIsALOD took 1.091008186340332s
Amount of data | Number of triples check for WebIsALOD took 26.316829204559326s
Interoperability | New terms check for WebIsALOD took 20.96194314956665s
Versatility | Languages check for WebIsALOD took 60.69365048408508s
Interpretability | Number of blank nodes check for WebIsALOD took 0.4526853561401367s
Security | Check HTTPS for WebIsALOD took 0.13497543334960938s
Interpretability | RDF structures check for WebIsALOD took 0.4344007968902588s
Versatility | Serialization formats check for WebIsALOD took 0.2718667984008789s
Availability | RDF dump link check for WebIsALOD took 18.01779580116272s
License | MR license check for WebIsALOD took 15.180956602096558s
License | HR license check for WebIsALOD took 27.911439418792725s
Amount of data | Number of property check for WebIsALOD took 0.2507951259613037s
Understandability | Number of label check for WebIsALOD took 0.6629691123962402s
Understandability | URI regex check for WebIsALOD took 0.5164356231689453s
Understandability | Vocabs check for WebIsALOD took 0.289874792098999s
Verifiability | Authors check for WebIsALOD took 0.3407900333404541s
Verifiability | Publishers check for WebIsALOD took 0.2703588008880615s
Performance | Throughput check for WebIsALOD took 10.437212944030762s
Amount of data | Check the number of entities for WebIsALOD took 8.416175842285156e-05s
Verifiability | Contribs. check for WebIsALOD took 0.2703113555908203s
Interlinking | sameAs chians check for WebIsALOD took 0.3030688762664795s
Interlinking | skos check for WebIsALOD took 0.29410409927368164s
Interlinking | skos check for WebIsALOD took 0.21390032768249512s
Timeliness | dataset update frequency check for WebIsALOD took 0.26915502548217773s
Currency | Creation date check for WebIsALOD took 0.5324666500091553s
Currency | Modification date check for WebIsALOD took 0.4923410415649414s
Rep.Conc. | URIs length for WebIsALOD took 105.19303512573242s
Consistency | Deprecated classes/propertiers check for WebIsALOD took 0.24664783477783203s
Accuracy | Check Functional Property for WebIsALOD took 0.2558729648590088s
Accuracy | Check Inverse Functional Property for WebIsALOD took 0.26250267028808594s
Accuracy | Check Empty annotation labels for WebIsALOD took 0.6776056289672852s
Accuracy | Check White space in annotation for WebIsALOD took 0.030419349670410156s
Accuracy | Check Datatype consistency for WebIsALOD took 0.028077363967895508s
Consistency | Disjoint class check for WebIsALOD took 0.29767322540283203s
Consistency | Check Misplaced properties for WebIsALOD took 60.905832052230835s
Consistency | Misplaced classes for WebIsALOD took 1.380713939666748s
Consistency | Check Ontology hijacking for WebIsALOD took 2.746460437774658s
Consistency | Check Invalid usage of undefined classes for WebIsALOD took 1.7166295051574707s
Consistency | Check Invalid usage of undefined properties for WebIsALOD took 63.073742151260376s
Conciseness | Check Extensional conciseness for WebIsALOD took 0.03094482421875s
Conciseness | Check Intensional conciseness for WebIsALOD took 0.2809021472930908s
Security | Sign check for WebIsALOD took 0.2566375732421875s
Availability | Check URIs Dereferenciability for WebIsALOD took 12.37627387046814s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.4752340316772461s
Reputation | Calculation of the PageRank for WebIsALOD took 0.0210723876953125s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 8.988380432128906e-05s
Believability | Calculation of trust value for WebIsALOD took 8.58306884765625e-06s
INFO | --- Analysis for webisalod took 597.3073887825012s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 4.410743713378906e-05s
Availability | VoID file availability check for webnmasunotraveler took 0.0003502368927001953s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.28178954124450684s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.020318984985351562s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 3.695487976074219e-05s
Believability | Calculation of trust value for webnmasunotraveler took 7.867813110351562e-06s
INFO | --- Analysis for webnmasunotraveler took 9.631597518920898s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 6.699562072753906e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.2588498592376709s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.02053213119506836s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 7.104873657226562e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 8.344650268554688e-06s
INFO | --- Analysis for wikilinks-rdf-nif took 4.29932165145874s
Availability | SPARQL endpoint availability check for WikiPathways took 4.00543212890625e-05s
Availability | VoID file availability check for WikiPathways took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.27605748176574707s
Reputation | Calculation of the PageRank for WikiPathways took 0.021860837936401367s
Interlinking | Calculation of Degree of Connection for WikiPathways took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for WikiPathways took 0.0010383129119873047s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 3.552436828613281e-05s
Believability | Calculation of trust value for WikiPathways took 9.059906005859375e-06s
INFO | --- Analysis for wikipathways took 3.974802255630493s
Availability | SPARQL endpoint availability check for WikiWord Thesaurus Data took 4.124641418457031e-05s
Availability | VoID file availability check for WikiWord Thesaurus Data took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for WikiWord Thesaurus Data took 0.2570822238922119s
Reputation | Calculation of the PageRank for WikiWord Thesaurus Data took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for WikiWord Thesaurus Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for WikiWord Thesaurus Data took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for WikiWord Thesaurus Data took 2.9325485229492188e-05s
Believability | Calculation of trust value for WikiWord Thesaurus Data took 1.3828277587890625e-05s
INFO | --- Analysis for wikiword_thesaurus took 2.9233713150024414s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 0.2800626754760742s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.0006821155548095703s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.24221348762512207s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 9.608268737792969e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 8.58306884765625e-06s
INFO | --- Analysis for wiktionary-dbpedia-org took 4.544182300567627s
Availability | SPARQL endpoint availability check for Wings workflow provenance dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for Wings workflow provenance dataset took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Wings workflow provenance dataset took 0.31378889083862305s
Reputation | Calculation of the PageRank for Wings workflow provenance dataset took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for Wings workflow provenance dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Wings workflow provenance dataset took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Wings workflow provenance dataset took 3.0517578125e-05s
Believability | Calculation of trust value for Wings workflow provenance dataset took 7.867813110351562e-06s
INFO | --- Analysis for wings-workflow-provenance-dataset took 2.9434854984283447s
Availability | SPARQL endpoint availability check for World Loanword Database took 0.12449979782104492s
Availability | VoID file availability check for World Loanword Database took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.25241851806640625s
Reputation | Calculation of the PageRank for World Loanword Database took 0.02040719985961914s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0008869171142578125s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 8.320808410644531e-05s
Believability | Calculation of trust value for World Loanword Database took 8.58306884765625e-06s
INFO | --- Analysis for wold took 2.5043909549713135s
Availability | SPARQL endpoint availability check for Wordnet took 4.00543212890625e-05s
Availability | VoID file availability check for Wordnet took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Wordnet took 0.26700735092163086s
Reputation | Calculation of the PageRank for Wordnet took 0.020369529724121094s
Interlinking | Calculation of Degree of Connection for Wordnet took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Wordnet took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Wordnet took 3.9577484130859375e-05s
Believability | Calculation of trust value for Wordnet took 7.3909759521484375e-06s
INFO | --- Analysis for wordnet took 3.3653831481933594s
Availability | SPARQL endpoint availability check for WordNet-RDF took 4.267692565917969e-05s
Availability | VoID file availability check for WordNet-RDF took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.2619750499725342s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.020650863647460938s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 9.131431579589844e-05s
Believability | Calculation of trust value for WordNet-RDF took 8.821487426757812e-06s
INFO | --- Analysis for wordnet-rdf took 2.4528331756591797s
Availability | SPARQL endpoint availability check for wordpress took 4.7206878662109375e-05s
Availability | VoID file availability check for wordpress took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for wordpress took 0.26955533027648926s
Reputation | Calculation of the PageRank for wordpress took 0.02048492431640625s
Interlinking | Calculation of Degree of Connection for wordpress took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for wordpress took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for wordpress took 8.368492126464844e-05s
Believability | Calculation of trust value for wordpress took 7.3909759521484375e-06s
INFO | --- Analysis for wordpress took 2.7130019664764404s
Availability | SPARQL endpoint availability check for wordpress.post took 4.100799560546875e-05s
Availability | VoID file availability check for wordpress.post took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for wordpress.post took 0.32327890396118164s
Reputation | Calculation of the PageRank for wordpress.post took 0.020325660705566406s
Interlinking | Calculation of Degree of Connection for wordpress.post took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for wordpress.post took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for wordpress.post took 2.765655517578125e-05s
Believability | Calculation of trust value for wordpress.post took 7.867813110351562e-06s
INFO | --- Analysis for wordpress_post took 3.167375087738037s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 0.5546953678131104s
Availability | VoID file availability check for World Bank Linked Data took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.24791669845581055s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.020631074905395508s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.00012135505676269531s
Believability | Calculation of trust value for World Bank Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for world-bank-linked-data took 3.2120420932769775s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 0.9386122226715088s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.2865304946899414s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.02035975456237793s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 8.416175842285156e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 1.0013580322265625e-05s
INFO | --- Analysis for world-factbook-fu-berlin took 5.355178594589233s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 4.410743713378906e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.000640869140625s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.2503011226654053s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.020722627639770508s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 8.845329284667969e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 4.5299530029296875e-06s
INFO | --- Analysis for world-wide-web-foundation took 5.583894491195679s
Availability | SPARQL endpoint availability check for WikiPathways took 4.076957702636719e-05s
Availability | VoID file availability check for WikiPathways took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.2495710849761963s
Reputation | Calculation of the PageRank for WikiPathways took 0.0202181339263916s
Interlinking | Calculation of Degree of Connection for WikiPathways took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for WikiPathways took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 2.9325485229492188e-05s
Believability | Calculation of trust value for WikiPathways took 7.62939453125e-06s
INFO | --- Analysis for wp took 3.0393078327178955s
Availability | SPARQL endpoint availability check for wunderground.weatherreport took 4.267692565917969e-05s
Availability | VoID file availability check for wunderground.weatherreport took 0.000244140625s
Completeness | Calculation of interlinking completeness for wunderground.weatherreport took 0.29971837997436523s
Reputation | Calculation of the PageRank for wunderground.weatherreport took 0.020308732986450195s
Interlinking | Calculation of Degree of Connection for wunderground.weatherreport took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for wunderground.weatherreport took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for wunderground.weatherreport took 2.9325485229492188e-05s
Believability | Calculation of trust value for wunderground.weatherreport took 7.3909759521484375e-06s
INFO | --- Analysis for wunderground_weatherreport took 2.965463399887085s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.2066657543182373s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0005085468292236328s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 16.38534140586853s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.8593010902404785s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.2449357509613037s
Interoperability | New terms check for World War 1 as Linked Open Data took 1.9902198314666748s
Versatility | Languages check for World War 1 as Linked Open Data took 0.5121033191680908s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.23644208908081055s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.25272083282470703s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.46411895751953125s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.35445380210876465s
Availability | RDF dump link check for World War 1 as Linked Open Data took 7.220493316650391s
License | MR license check for World War 1 as Linked Open Data took 0.1951456069946289s
License | HR license check for World War 1 as Linked Open Data took 1.6035816669464111s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.1882178783416748s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.27291321754455566s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.36107468605041504s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.22594952583312988s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.18506312370300293s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.19390106201171875s
Performance | Throughput check for World War 1 as Linked Open Data took 10.596046447753906s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.07119393348693848s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.18958258628845215s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.22816944122314453s
Interlinking | skos check for World War 1 as Linked Open Data took 0.1959695816040039s
Interlinking | skos check for World War 1 as Linked Open Data took 0.19546771049499512s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.16921234130859375s
Currency | Creation date check for World War 1 as Linked Open Data took 0.3965182304382324s
Currency | Modification date check for World War 1 as Linked Open Data took 0.20054960250854492s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 3.5059661865234375s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.19487571716308594s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 1.2437186241149902s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.18374085426330566s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.7426722049713135s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.05082416534423828s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.31566429138183594s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.20079803466796875s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.6106023788452148s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 2.361400604248047s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.3073859214782715s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.5465385913848877s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.1859738826751709s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 0.585608959197998s
Security | Sign check for World War 1 as Linked Open Data took 0.23875927925109863s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 1613.3866260051727s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 1.1212921142578125s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.021019935607910156s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 2.86102294921875e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 0.0001666545867919922s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 8.58306884765625e-06s
INFO | --- Analysis for ww1lod took 1707.988846063614s
Availability | SPARQL endpoint availability check for XlendiAmphorae took 8.58306884765625e-05s
Availability | VoID file availability check for XlendiAmphorae took 0.00022649765014648438s
Completeness | Calculation of interlinking completeness for XlendiAmphorae took 0.2689805030822754s
Reputation | Calculation of the PageRank for XlendiAmphorae took 0.020638465881347656s
Interlinking | Calculation of Degree of Connection for XlendiAmphorae took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for XlendiAmphorae took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for XlendiAmphorae took 3.314018249511719e-05s
Believability | Calculation of trust value for XlendiAmphorae took 8.106231689453125e-06s
INFO | --- Analysis for xlendiamphorae took 4.316147804260254s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 0.31759166717529297s
Availability | VoID file availability check for xLiD-Lexica took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.7283632755279541s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.020533323287963867s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 7.295608520507812e-05s
Believability | Calculation of trust value for xLiD-Lexica took 7.3909759521484375e-06s
INFO | --- Analysis for xlid-lexica took 5.856714963912964s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 4.458427429199219e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.27919721603393555s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.020452022552490234s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 3.743171691894531e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 1.1444091796875e-05s
INFO | --- Analysis for xwn took 3.6181702613830566s
Availability | SPARQL endpoint availability check for YAGO took 4.267692565917969e-05s
Availability | VoID file availability check for YAGO took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for YAGO took 0.27563977241516113s
Reputation | Calculation of the PageRank for YAGO took 0.020491361618041992s
Interlinking | Calculation of Degree of Connection for YAGO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for YAGO took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.00013208389282226562s
Believability | Calculation of trust value for YAGO took 7.867813110351562e-06s
INFO | --- Analysis for yago took 4.400853395462036s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 1.7840981483459473s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.0004222393035888672s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.25660204887390137s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.020449161529541016s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0008685588836669922s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 8.821487426757812e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 7.867813110351562e-06s
INFO | --- Analysis for yahoo_geoplanet took 13.804502010345459s
Availability | SPARQL endpoint availability check for Yale Senselab took 0.13740229606628418s
Availability | VoID file availability check for Yale Senselab took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.2953507900238037s
Reputation | Calculation of the PageRank for Yale Senselab took 0.023284912109375s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Yale Senselab took 0.001207590103149414s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 4.100799560546875e-05s
Believability | Calculation of trust value for Yale Senselab took 1.4543533325195312e-05s
INFO | --- Analysis for yale_senselab took 14.794840097427368s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 1.3132538795471191s
Availability | VoID file availability check for Yovisto - academic video search took 0.0007596015930175781s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.2674400806427002s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.020875215530395508s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 7.319450378417969e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 6.198883056640625e-06s
INFO | --- Analysis for yovisto took 30.685149908065796s
Availability | SPARQL endpoint availability check for Yleinen suomalainen asiasanasto - YSA took 4.315376281738281e-05s
Availability | VoID file availability check for Yleinen suomalainen asiasanasto - YSA took 0.0007781982421875s
Completeness | Calculation of interlinking completeness for Yleinen suomalainen asiasanasto - YSA took 0.2795445919036865s
Reputation | Calculation of the PageRank for Yleinen suomalainen asiasanasto - YSA took 0.020369768142700195s
Interlinking | Calculation of Degree of Connection for Yleinen suomalainen asiasanasto - YSA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Yleinen suomalainen asiasanasto - YSA took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Yleinen suomalainen asiasanasto - YSA took 3.266334533691406e-05s
Believability | Calculation of trust value for Yleinen suomalainen asiasanasto - YSA took 9.059906005859375e-06s
INFO | --- Analysis for ysa took 4.469796419143677s
Availability | SPARQL endpoint availability check for yso-fi-allars took 4.220008850097656e-05s
Availability | VoID file availability check for yso-fi-allars took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.2611057758331299s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.123283386230469e-05s
Believability | Calculation of trust value for yso-fi-allars took 7.62939453125e-06s
INFO | --- Analysis for yso-fi-allars took 4.168139696121216s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 4.363059997558594e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.0003514289855957031s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.24375581741333008s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.020389556884765625s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 3.361701965332031e-05s
Believability | Calculation of trust value for yso-fi-ysa took 7.62939453125e-06s
INFO | --- Analysis for yso-fi-ysa took 3.099299907684326s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 4.458427429199219e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.0007359981536865234s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.28386354446411133s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.020239591598510742s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 3.170967102050781e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 5.9604644775390625e-06s
INFO | --- Analysis for zaragoza-datosabiertos took 7.64739465713501s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 5.745887756347656e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.0003542900085449219s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.25700974464416504s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.02051520347595215s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.1948089599609375e-05s
Believability | Calculation of trust value for zaragoza_turruta took 1.3589859008789062e-05s
INFO | --- Analysis for zaragoza_turruta took 2.6752495765686035s
Availability | SPARQL endpoint availability check for ZBW Labs took 4.458427429199219e-05s
Availability | VoID file availability check for ZBW Labs took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.26633119583129883s
Reputation | Calculation of the PageRank for ZBW Labs took 0.020367145538330078s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 7.104873657226562e-05s
Believability | Calculation of trust value for ZBW Labs took 7.867813110351562e-06s
INFO | --- Analysis for zbw-labs took 3.98962664604187s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.17401862144470215s
Availability | VoID file availability check for 20th Century Press Archives took 0.0005950927734375s
Extra | Recovery of all triples for 20th Century Press Archives took 76.90102076530457s
Performance | Total latancy measurement for 20th Century Press Archives took 0.796907901763916s
Amount of data | Number of triples check for 20th Century Press Archives took 0.97607421875s
Interoperability | New terms check for 20th Century Press Archives took 1.7763252258300781s
Versatility | Languages check for 20th Century Press Archives took 2.9235692024230957s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 0.7164583206176758s
Interpretability | RDF structures check for 20th Century Press Archives took 0.20464444160461426s
Versatility | Serialization formats check for 20th Century Press Archives took 0.17896485328674316s
Availability | RDF dump link check for 20th Century Press Archives took 0.15085077285766602s
License | MR license check for 20th Century Press Archives took 0.154984712600708s
License | HR license check for 20th Century Press Archives took 4.910597324371338s
Amount of data | Number of property check for 20th Century Press Archives took 0.16764140129089355s
Understandability | Number of label check for 20th Century Press Archives took 0.47647976875305176s
Understandability | URI regex check for 20th Century Press Archives took 0.32390451431274414s
Understandability | Vocabs check for 20th Century Press Archives took 0.1321392059326172s
Verifiability | Authors check for 20th Century Press Archives took 0.13121390342712402s
Verifiability | Publishers check for 20th Century Press Archives took 0.15578055381774902s
Performance | Throughput check for 20th Century Press Archives took 10.738425254821777s
Amount of data | Check the number of entities for 20th Century Press Archives took 8.511543273925781e-05s
Verifiability | Contribs. check for 20th Century Press Archives took 0.1636977195739746s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.1414024829864502s
Interlinking | skos check for 20th Century Press Archives took 0.18967366218566895s
Interlinking | skos check for 20th Century Press Archives took 0.16473746299743652s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.14808368682861328s
Currency | Creation date check for 20th Century Press Archives took 0.2997865676879883s
Currency | Modification date check for 20th Century Press Archives took 0.3147397041320801s
Rep.Conc. | URIs length for 20th Century Press Archives took 22.31484889984131s
Interoperability | New vocabularies check for 20th Century Press Archives took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.1522514820098877s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.15629935264587402s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.14600443840026855s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 8.57718300819397s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.8901612758636475s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.110404968261719s
Consistency | Disjoint class check for 20th Century Press Archives took 0.17901110649108887s
Consistency | Check Misplaced properties for 20th Century Press Archives took 2.4894802570343018s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 3.922006368637085s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 7.619352340698242s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 3.269974946975708s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.761134147644043s
Security | Sign check for 20th Century Press Archives took 0.14947056770324707s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 992.8051040172577s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 1.3520233631134033s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.021013259887695312s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.00011277198791503906s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 1.430511474609375e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 9.775161743164062e-06s
INFO | --- Analysis for zbw-pressemappe20 took 1176.3767673969269s
Availability | SPARQL endpoint availability check for zhishi.lemon took 4.887580871582031e-05s
Availability | VoID file availability check for zhishi.lemon took 0.0007152557373046875s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.7132449150085449s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 4.4345855712890625e-05s
Believability | Calculation of trust value for zhishi.lemon took 7.62939453125e-06s
INFO | --- Analysis for zhishi-lemon took 25.340784549713135s
Availability | SPARQL endpoint availability check for Zhishi.me took 3.9585039615631104s
Availability | VoID file availability check for Zhishi.me took 0.0003440380096435547s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.2630627155303955s
Reputation | Calculation of the PageRank for Zhishi.me took 0.020904064178466797s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 7.319450378417969e-05s
Believability | Calculation of trust value for Zhishi.me took 7.62939453125e-06s
INFO | --- Analysis for zhishi-me took 8.475564002990723s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 4.3392181396484375e-05s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0006706714630126953s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.2577197551727295s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.020343542098999023s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 5.888938903808594e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 9.059906005859375e-06s
INFO | --- Analysis for zitgist-musicbrainz took 3.5620813369750977s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.4010658264160156s
Availability | VoID file availability check for performing-arts.ch took 0.00026154518127441406s
Extra | Recovery of all triples for performing-arts.ch took 81.91528105735779s
Performance | Total latancy measurement for performing-arts.ch took 0.8164811134338379s
Amount of data | Number of triples check for performing-arts.ch took 37.0440468788147s
Interoperability | New terms check for performing-arts.ch took 1.5809190273284912s
Versatility | Languages check for performing-arts.ch took 60.137206077575684s
Interpretability | Number of blank nodes check for performing-arts.ch took 60.14780378341675s
Interpretability | RDF structures check for performing-arts.ch took 0.2350614070892334s
Versatility | Serialization formats check for performing-arts.ch took 0.18599915504455566s
Availability | RDF dump link check for performing-arts.ch took 0.15109467506408691s
License | MR license check for performing-arts.ch took 0.2055816650390625s
License | HR license check for performing-arts.ch took 60.14902687072754s
Amount of data | Number of property check for performing-arts.ch took 0.29261279106140137s
Understandability | Number of label check for performing-arts.ch took 23.122579336166382s
Understandability | URI regex check for performing-arts.ch took 0.316988468170166s
Understandability | Vocabs check for performing-arts.ch took 0.14536070823669434s
Verifiability | Authors check for performing-arts.ch took 0.13817548751831055s
Verifiability | Publishers check for performing-arts.ch took 0.15847039222717285s
Performance | Throughput check for performing-arts.ch took 10.936298608779907s
Amount of data | Check the number of entities for performing-arts.ch took 7.081031799316406e-05s
Verifiability | Contribs. check for performing-arts.ch took 0.17464804649353027s
Interlinking | sameAs chians check for performing-arts.ch took 0.6079099178314209s
Interlinking | skos check for performing-arts.ch took 0.18905997276306152s
Interlinking | skos check for performing-arts.ch took 0.1785132884979248s
Timeliness | dataset update frequency check for performing-arts.ch took 0.17614507675170898s
Currency | Creation date check for performing-arts.ch took 0.3453502655029297s
Currency | Modification date check for performing-arts.ch took 0.36554408073425293s
Rep.Conc. | URIs length for performing-arts.ch took 41.765191316604614s
Interoperability | New vocabularies check for performing-arts.ch took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.1684272289276123s
Accuracy | Check Functional Property for performing-arts.ch took 0.13715624809265137s
Accuracy | Check Inverse Functional Property for performing-arts.ch took 0.15762567520141602s
Accuracy | Check Empty annotation labels for performing-arts.ch took 42.31541872024536s
Accuracy | Check White space in annotation for performing-arts.ch took 2.538351535797119s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.777621030807495s
Consistency | Disjoint class check for performing-arts.ch took 0.2654266357421875s
Consistency | Check Misplaced properties for performing-arts.ch took 0.42478013038635254s
Consistency | Misplaced classes for performing-arts.ch took 8.469825983047485s
Consistency | Check Ontology hijacking for performing-arts.ch took 48.5915789604187s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 17778.111968517303s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 1.944626808166504s
Conciseness | Check Extensional conciseness for performing-arts.ch took 2.9413199424743652s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.3263852596282959s
Security | Sign check for performing-arts.ch took 0.14039158821105957s
Availability | Check URIs Dereferenciability for performing-arts.ch took 3.462344169616699s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 0.7986319065093994s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.021021604537963867s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 1.7881393432617188e-05s
Interoperability | Check the re-using of existing vocabs for performing-arts.ch took 1.9073486328125e-06s
Believability | Calculation of trust value for performing-arts.ch took 7.62939453125e-06s
INFO | --- Analysis for performing-arts.ch took 18671.742206335068s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 2.2615766525268555s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.2681856155395508s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.02042555809020996s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.52587890625e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.2159347534179688e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for The-AA-Thesaurus took 9.273006439208984s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.4995789527893066s
Availability | VoID file availability check for MiMoTextBase took 0.0007441043853759766s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.27799439430236816s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.020252227783203125s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.0728836059570312e-05s
Believability | Calculation of trust value for MiMoTextBase took 8.344650268554688e-06s
INFO | --- Analysis for MiMoTextBase took 6.579418659210205s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.5048863887786865s
Availability | VoID file availability check for National Library of Sweden took 0.0003604888916015625s
Extra | Recovery of all triples for National Library of Sweden took 14.725906133651733s
Performance | Total latancy measurement for National Library of Sweden took 1.0794010162353516s
Amount of data | Number of triples check for National Library of Sweden took 21.97575569152832s
Interoperability | New terms check for National Library of Sweden took 15.02876353263855s
Versatility | Languages check for National Library of Sweden took 0.20154714584350586s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.1995277404785s
Interpretability | RDF structures check for National Library of Sweden took 0.28203797340393066s
Versatility | Serialization formats check for National Library of Sweden took 0.20725059509277344s
Availability | RDF dump link check for National Library of Sweden took 0.22188258171081543s
License | MR license check for National Library of Sweden took 0.3284571170806885s
License | HR license check for National Library of Sweden took 0.2438950538635254s
Amount of data | Number of property check for National Library of Sweden took 0.2166140079498291s
Understandability | Number of label check for National Library of Sweden took 0.43721556663513184s
Understandability | URI regex check for National Library of Sweden took 0.44564032554626465s
Understandability | Vocabs check for National Library of Sweden took 0.22278642654418945s
Verifiability | Authors check for National Library of Sweden took 0.28252077102661133s
Verifiability | Publishers check for National Library of Sweden took 0.2537684440612793s
Performance | Throughput check for National Library of Sweden took 10.661311626434326s
Amount of data | Check the number of entities for National Library of Sweden took 7.295608520507812e-05s
Verifiability | Contribs. check for National Library of Sweden took 0.27529430389404297s
Interlinking | sameAs chians check for National Library of Sweden took 0.2829563617706299s
Interlinking | skos check for National Library of Sweden took 0.2624523639678955s
Interlinking | skos check for National Library of Sweden took 0.2135331630706787s
Timeliness | dataset update frequency check for National Library of Sweden took 0.2482445240020752s
Currency | Creation date check for National Library of Sweden took 0.47005772590637207s
Currency | Modification date check for National Library of Sweden took 0.4341435432434082s
Rep.Conc. | URIs length for National Library of Sweden took 81.8192925453186s
Interoperability | New vocabularies check for National Library of Sweden took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.20207905769348145s
Accuracy | Check Functional Property for National Library of Sweden took 0.22987818717956543s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.22283411026000977s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.28142333030700684s
Consistency | Disjoint class check for National Library of Sweden took 0.21025776863098145s
Consistency | Check Misplaced properties for National Library of Sweden took 59.997562885284424s
Consistency | Misplaced classes for National Library of Sweden took 1.171069860458374s
Consistency | Check Ontology hijacking for National Library of Sweden took 6.774225950241089s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.39200758934021s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 61.08267045021057s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.2862257957458496s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.36333513259887695s
Security | Sign check for National Library of Sweden took 0.4341564178466797s
Availability | Check URIs Dereferenciability for National Library of Sweden took 18.370702743530273s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 1.3228583335876465s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.021155595779418945s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 2.0503997802734375e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 1.430511474609375e-06s
Believability | Calculation of trust value for National Library of Sweden took 8.106231689453125e-06s
INFO | --- Analysis for NLS took 1393.8415603637695s
Availability | SPARQL endpoint availability check for Japan Search took 0.9553229808807373s
Availability | VoID file availability check for Japan Search took 0.0002665519714355469s
Extra | Recovery of all triples for Japan Search took 3.42877459526062s
Performance | Total latancy measurement for Japan Search took 1.410353183746338s
Amount of data | Number of triples check for Japan Search took 5.742089509963989s
Interoperability | New terms check for Japan Search took 3.3403093814849854s
Versatility | Languages check for Japan Search took 0.2836644649505615s
Interpretability | Number of blank nodes check for Japan Search took 13.152734518051147s
Interpretability | RDF structures check for Japan Search took 0.7949719429016113s
Versatility | Serialization formats check for Japan Search took 0.8458085060119629s
Availability | RDF dump link check for Japan Search took 0.46663761138916016s
License | MR license check for Japan Search took 1.6263773441314697s
License | HR license check for Japan Search took 11.901918411254883s
Amount of data | Number of property check for Japan Search took 0.28653502464294434s
Understandability | Number of label check for Japan Search took 3.0966808795928955s
Understandability | URI regex check for Japan Search took 0.5928101539611816s
Understandability | Vocabs check for Japan Search took 0.29603075981140137s
Verifiability | Authors check for Japan Search took 0.7276718616485596s
Verifiability | Publishers check for Japan Search took 0.5202875137329102s
Performance | Throughput check for Japan Search took 11.55120849609375s
Amount of data | Check the number of entities for Japan Search took 8.320808410644531e-05s
Verifiability | Contribs. check for Japan Search took 0.49155139923095703s
Interlinking | sameAs chians check for Japan Search took 0.28359413146972656s
Interlinking | skos check for Japan Search took 0.6472020149230957s
Interlinking | skos check for Japan Search took 0.3051414489746094s
Timeliness | dataset update frequency check for Japan Search took 0.6888489723205566s
Currency | Creation date check for Japan Search took 1.2514314651489258s
Currency | Modification date check for Japan Search took 1.1492867469787598s
Rep.Conc. | URIs length for Japan Search took 14.817225933074951s
Interoperability | New vocabularies check for Japan Search took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.2803976535797119s
Accuracy | Check Functional Property for Japan Search took 0.6601853370666504s
Accuracy | Check Inverse Functional Property for Japan Search took 0.6592392921447754s
Accuracy | Check Empty annotation labels for Japan Search took 0.5614578723907471s
Accuracy | Check White space in annotation for Japan Search took 0.031212329864501953s
Accuracy | Check Datatype consistency for Japan Search took 0.02907085418701172s
Consistency | Disjoint class check for Japan Search took 0.5360763072967529s
Consistency | Check Misplaced properties for Japan Search took 10.886158466339111s
Consistency | Misplaced classes for Japan Search took 0.4389677047729492s
Consistency | Check Ontology hijacking for Japan Search took 1.8886380195617676s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.395622968673706s
Consistency | Check Invalid usage of undefined properties for Japan Search took 13.811359882354736s
Conciseness | Check Extensional conciseness for Japan Search took 0.03784608840942383s
Conciseness | Check Intensional conciseness for Japan Search took 0.27046656608581543s
Security | Sign check for Japan Search took 0.31910204887390137s
Availability | Check URIs Dereferenciability for Japan Search took 11.939332485198975s
Completeness | Calculation of interlinking completeness for Japan Search took 0.3993680477142334s
Reputation | Calculation of the PageRank for Japan Search took 0.020855426788330078s
Interlinking | Calculation of Degree of Connection for Japan Search took 2.9325485229492188e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Japan Search took 1.239776611328125e-05s
Interoperability | Check the re-using of existing vocabs for Japan Search took 1.1920928955078125e-06s
Believability | Calculation of trust value for Japan Search took 8.106231689453125e-06s
INFO | --- Analysis for Japan-Search took 390.89494037628174s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 1.2733154296875s
Availability | VoID file availability check for Rijksmuseum Collection took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.7040798664093018s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.020417213439941406s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.1920928955078125e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 8.344650268554688e-06s
INFO | --- Analysis for Rijksmuseum took 6.720173358917236s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 0.6349937915802002s
Availability | VoID file availability check for Finnish Public Libraries took 0.0007627010345458984s
Extra | Recovery of all triples for Finnish Public Libraries took 40.08779335021973s
Performance | Total latancy measurement for Finnish Public Libraries took 1.2837636470794678s
Amount of data | Number of triples check for Finnish Public Libraries took 60.286558389663696s
Interoperability | New terms check for Finnish Public Libraries took 18.153894901275635s
Versatility | Languages check for Finnish Public Libraries took 60.28290557861328s
Interpretability | Number of blank nodes check for Finnish Public Libraries took 60.314566135406494s
Interpretability | RDF structures check for Finnish Public Libraries took 0.37759876251220703s
Versatility | Serialization formats check for Finnish Public Libraries took 0.2901773452758789s
Availability | RDF dump link check for Finnish Public Libraries took 0.23976540565490723s
License | MR license check for Finnish Public Libraries took 0.42298078536987305s
License | HR license check for Finnish Public Libraries took 50.87649416923523s
Amount of data | Number of property check for Finnish Public Libraries took 0.365614652633667s
Understandability | Number of label check for Finnish Public Libraries took 15.042049884796143s
Understandability | URI regex check for Finnish Public Libraries took 0.7851815223693848s
Understandability | Vocabs check for Finnish Public Libraries took 0.30759763717651367s
Verifiability | Authors check for Finnish Public Libraries took 0.2878134250640869s
Verifiability | Publishers check for Finnish Public Libraries took 0.12341499328613281s
Performance | Throughput check for Finnish Public Libraries took 11.43451189994812s
Amount of data | Check the number of entities for Finnish Public Libraries took 7.462501525878906e-05s
Verifiability | Contribs. check for Finnish Public Libraries took 0.12346959114074707s
Interlinking | sameAs chians check for Finnish Public Libraries took 0.47058939933776855s
Interlinking | skos check for Finnish Public Libraries took 0.2934906482696533s
Interlinking | skos check for Finnish Public Libraries took 0.2684361934661865s
Timeliness | dataset update frequency check for Finnish Public Libraries took 0.30719971656799316s
Currency | Creation date check for Finnish Public Libraries took 0.5730698108673096s
Currency | Modification date check for Finnish Public Libraries took 0.44106149673461914s
Rep.Conc. | URIs length for Finnish Public Libraries took 85.49747896194458s
Interoperability | New vocabularies check for Finnish Public Libraries took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Finnish Public Libraries took 0.2138063907623291s
Accuracy | Check Empty annotation labels for Finnish Public Libraries took 12.74463176727295s
Accuracy | Check White space in annotation for Finnish Public Libraries took 2.2043397426605225s
Accuracy | Check Datatype consistency for Finnish Public Libraries took 4.390049934387207s
Consistency | Disjoint class check for Finnish Public Libraries took 0.36174511909484863s
Consistency | Check Misplaced properties for Finnish Public Libraries took 60.4148063659668s
Consistency | Check Ontology hijacking for Finnish Public Libraries took 15.206679582595825s
Consistency | Check Invalid usage of undefined classes for Finnish Public Libraries took 1.5997998714447021s
Consistency | Check Invalid usage of undefined properties for Finnish Public Libraries took 61.71693253517151s
Conciseness | Check Extensional conciseness for Finnish Public Libraries took 2.7453560829162598s
Security | Sign check for Finnish Public Libraries took 0.29560375213623047s
Availability | Check URIs Dereferenciability for Finnish Public Libraries took 1.7861008644104004s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 0.9445655345916748s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.02087259292602539s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 1.6927719116210938e-05s
Interoperability | Check the re-using of existing vocabs for Finnish Public Libraries took 1.6689300537109375e-06s
Believability | Calculation of trust value for Finnish Public Libraries took 8.344650268554688e-06s
INFO | --- Analysis for FI-Library took 715.5394196510315s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 3.9161312580108643s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.00034499168395996094s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.7169489860534668s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.022602558135986328s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.0010197162628173828s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 1.5974044799804688e-05s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 9.298324584960938e-06s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 10.225838661193848s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.7267041206359863s
Availability | VoID file availability check for National Library Netherlands took 0.0005936622619628906s
Extra | Recovery of all triples for National Library Netherlands took 1.1616284847259521s
Performance | Total latancy measurement for National Library Netherlands took 0.6824092864990234s
Amount of data | Number of triples check for National Library Netherlands took 0.15223288536071777s
Interoperability | New terms check for National Library Netherlands took 1.4203987121582031s
Versatility | Languages check for National Library Netherlands took 58.12309288978577s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.13518905639648438s
Interpretability | RDF structures check for National Library Netherlands took 0.16112446784973145s
Versatility | Serialization formats check for National Library Netherlands took 0.15802454948425293s
Availability | RDF dump link check for National Library Netherlands took 0.15816473960876465s
License | MR license check for National Library Netherlands took 0.15524601936340332s
License | HR license check for National Library Netherlands took 0.21088266372680664s
Amount of data | Number of property check for National Library Netherlands took 0.1376938819885254s
Understandability | Number of label check for National Library Netherlands took 0.14673209190368652s
Understandability | URI regex check for National Library Netherlands took 0.31015801429748535s
Understandability | Vocabs check for National Library Netherlands took 0.15323424339294434s
Verifiability | Authors check for National Library Netherlands took 0.13600826263427734s
Verifiability | Publishers check for National Library Netherlands took 0.14584922790527344s
Performance | Throughput check for National Library Netherlands took 10.754528284072876s
Amount of data | Check the number of entities for National Library Netherlands took 8.916854858398438e-05s
Verifiability | Contribs. check for National Library Netherlands took 0.1467139720916748s
Interlinking | sameAs chians check for National Library Netherlands took 0.1823275089263916s
Interlinking | skos check for National Library Netherlands took 0.16094303131103516s
Interlinking | skos check for National Library Netherlands took 0.1666412353515625s
Timeliness | dataset update frequency check for National Library Netherlands took 0.16274619102478027s
Currency | Creation date check for National Library Netherlands took 0.304351806640625s
Currency | Modification date check for National Library Netherlands took 0.2975273132324219s
Rep.Conc. | URIs length for National Library Netherlands took 0.6616923809051514s
Interoperability | New vocabularies check for National Library Netherlands took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 0.16433334350585938s
Accuracy | Check Functional Property for National Library Netherlands took 0.16961407661437988s
Accuracy | Check Inverse Functional Property for National Library Netherlands took 0.1508922576904297s
Accuracy | Check Empty annotation labels for National Library Netherlands took 0.5095739364624023s
Accuracy | Check White space in annotation for National Library Netherlands took 0.02488398551940918s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.02768540382385254s
Consistency | Disjoint class check for National Library Netherlands took 0.13545775413513184s
Consistency | Check Misplaced properties for National Library Netherlands took 0.32174015045166016s
Consistency | Check Ontology hijacking for National Library Netherlands took 1.882944107055664s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 2.2373619079589844s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.5478839874267578s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.036714792251586914s
Security | Sign check for National Library Netherlands took 0.15193796157836914s
Availability | Check URIs Dereferenciability for National Library Netherlands took 1761.2904212474823s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 1.636286973953247s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.02050924301147461s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 3.266334533691406e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 2.1457672119140625e-05s
Interoperability | Check the re-using of existing vocabs for National Library Netherlands took 1.9073486328125e-06s
Believability | Calculation of trust value for National Library Netherlands took 3.409385681152344e-05s
INFO | --- Analysis for National-Library-Netherlands took 1871.56920170784s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.6085095405578613s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007159709930419922s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.26348328590393066s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.02092432975769043s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.33514404296875e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 8.821487426757812e-06s
INFO | --- Analysis for Antique-Renaissance took 8.00757360458374s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 7.544057369232178s
Availability | VoID file availability check for ARTSDATA.CA took 0.0007109642028808594s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.24417638778686523s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.0207369327545166s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.3113021850585938e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 7.152557373046875e-06s
INFO | --- Analysis for ARTSDATA-CA took 12.784274578094482s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.22155427932739258s
Availability | VoID file availability check for Architecture of Knowledge took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.2574613094329834s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.02046036720275879s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.2159347534179688e-05s
Believability | Calculation of trust value for Architecture of Knowledge took 6.4373016357421875e-06s
INFO | --- Analysis for ArCo took 3.8633463382720947s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.38640546798706055s
Availability | VoID file availability check for ConfermentSampo took 0.0004010200500488281s
Extra | Recovery of all triples for ConfermentSampo took 177.0259461402893s
Performance | Total latancy measurement for ConfermentSampo took 0.8498303890228271s
Amount of data | Number of triples check for ConfermentSampo took 10.31142282485962s
Interoperability | New terms check for ConfermentSampo took 2.7774503231048584s
Versatility | Languages check for ConfermentSampo took 39.77166819572449s
Interpretability | Number of blank nodes check for ConfermentSampo took 8.772144079208374s
Security | Check HTTPS for ConfermentSampo took 0.41867518424987793s
Interpretability | RDF structures check for ConfermentSampo took 0.2136390209197998s
Versatility | Serialization formats check for ConfermentSampo took 0.2165825366973877s
Availability | RDF dump link check for ConfermentSampo took 3.2181732654571533s
License | MR license check for ConfermentSampo took 0.20128083229064941s
License | HR license check for ConfermentSampo took 0.2578890323638916s
Amount of data | Number of property check for ConfermentSampo took 0.19251060485839844s
Understandability | Number of label check for ConfermentSampo took 6.239382982254028s
Understandability | URI regex check for ConfermentSampo took 0.3793971538543701s
Understandability | Vocabs check for ConfermentSampo took 0.17430925369262695s
Verifiability | Authors check for ConfermentSampo took 0.20490670204162598s
Verifiability | Publishers check for ConfermentSampo took 0.20156550407409668s
Performance | Throughput check for ConfermentSampo took 10.953680038452148s
Amount of data | Check the number of entities for ConfermentSampo took 3.974761724472046s
Verifiability | Contribs. check for ConfermentSampo took 0.17859268188476562s
Interlinking | sameAs chians check for ConfermentSampo took 0.4658384323120117s
Interlinking | skos check for ConfermentSampo took 0.1708812713623047s
Interlinking | skos check for ConfermentSampo took 0.1684584617614746s
Timeliness | dataset update frequency check for ConfermentSampo took 0.1760110855102539s
Currency | Creation date check for ConfermentSampo took 0.36654114723205566s
Currency | Modification date check for ConfermentSampo took 0.3857998847961426s
Rep.Conc. | URIs length for ConfermentSampo took 86.52553677558899s
Interoperability | New vocabularies check for ConfermentSampo took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.20147395133972168s
Accuracy | Check Functional Property for ConfermentSampo took 0.20708370208740234s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.18770670890808105s
Accuracy | Check Empty annotation labels for ConfermentSampo took 57.762449741363525s
Accuracy | Check White space in annotation for ConfermentSampo took 3.0182621479034424s
Accuracy | Check Datatype consistency for ConfermentSampo took 5.22493052482605s
Consistency | Disjoint class check for ConfermentSampo took 0.18959617614746094s
Consistency | Check Misplaced properties for ConfermentSampo took 6.740639925003052s
Consistency | Check Ontology hijacking for ConfermentSampo took 58.015862703323364s
Consistency | Check Invalid usage of undefined classes for ConfermentSampo took 1.4670569896697998s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.574281930923462s
Conciseness | Check Extensional conciseness for ConfermentSampo took 2.8557140827178955s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.20453119277954102s
Security | Sign check for ConfermentSampo took 0.17772912979125977s
Availability | Check URIs Dereferenciability for ConfermentSampo took 1456.4424543380737s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 1.4909203052520752s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.022305965423583984s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 2.6941299438476562e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.001191854476928711s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 2.3126602172851562e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 2.1457672119140625e-06s
Believability | Calculation of trust value for ConfermentSampo took 8.344650268554688e-06s
INFO | --- Analysis for ConfermentSampo took 2080.3172421455383s
Availability | SPARQL endpoint availability check for Museum Finland took 0.37113475799560547s
Availability | VoID file availability check for Museum Finland took 0.00027632713317871094s
Extra | Recovery of all triples for Museum Finland took 47.66736340522766s
Performance | Total latancy measurement for Museum Finland took 0.8400347232818604s
Amount of data | Number of triples check for Museum Finland took 0.34247350692749023s
Interoperability | New terms check for Museum Finland took 2.048682689666748s
Versatility | Languages check for Museum Finland took 0.6488401889801025s
Interpretability | Number of blank nodes check for Museum Finland took 0.3281407356262207s
Security | Check HTTPS for Museum Finland took 0.41103100776672363s
Interpretability | RDF structures check for Museum Finland took 0.9548802375793457s
Versatility | Serialization formats check for Museum Finland took 0.18909573554992676s
Availability | RDF dump link check for Museum Finland took 0.1791396141052246s
License | MR license check for Museum Finland took 0.17033791542053223s
License | HR license check for Museum Finland took 0.34523725509643555s
Amount of data | Number of property check for Museum Finland took 0.19022345542907715s
Understandability | Number of label check for Museum Finland took 0.31527280807495117s
Understandability | URI regex check for Museum Finland took 0.3376307487487793s
Understandability | Vocabs check for Museum Finland took 0.16965651512145996s
Verifiability | Authors check for Museum Finland took 0.17216825485229492s
Verifiability | Publishers check for Museum Finland took 0.16995477676391602s
Performance | Throughput check for Museum Finland took 11.004411935806274s
Amount of data | Check the number of entities for Museum Finland took 7.987022399902344e-05s
Verifiability | Contribs. check for Museum Finland took 0.15648508071899414s
Interlinking | sameAs chians check for Museum Finland took 0.16897916793823242s
Interlinking | skos check for Museum Finland took 0.16713285446166992s
Interlinking | skos check for Museum Finland took 0.17483282089233398s
Timeliness | dataset update frequency check for Museum Finland took 0.1712024211883545s
Currency | Creation date check for Museum Finland took 0.3599538803100586s
Currency | Modification date check for Museum Finland took 0.3596820831298828s
Rep.Conc. | URIs length for Museum Finland took 7.491159200668335s
Interoperability | New vocabularies check for Museum Finland took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.18076038360595703s
Accuracy | Check Functional Property for Museum Finland took 0.16109418869018555s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.16404390335083008s
Accuracy | Check Empty annotation labels for Museum Finland took 1.63871431350708s
Accuracy | Check White space in annotation for Museum Finland took 0.062168121337890625s
Accuracy | Check Datatype consistency for Museum Finland took 1.0040924549102783s
Consistency | Disjoint class check for Museum Finland took 0.16990232467651367s
Consistency | Check Misplaced properties for Museum Finland took 0.6401305198669434s
Consistency | Check Ontology hijacking for Museum Finland took 3.0400710105895996s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.770824909210205s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 1.9319360256195068s
Conciseness | Check Extensional conciseness for Museum Finland took 0.6941649913787842s
Conciseness | Check Intensional conciseness for Museum Finland took 0.4231863021850586s
Security | Sign check for Museum Finland took 0.16404938697814941s
Availability | Check URIs Dereferenciability for Museum Finland took 3160.4335260391235s
Completeness | Calculation of interlinking completeness for Museum Finland took 1.6820714473724365s
Reputation | Calculation of the PageRank for Museum Finland took 0.022173404693603516s
Interlinking | Calculation of Degree of Connection for Museum Finland took 3.9577484130859375e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0010797977447509766s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 1.3113021850585938e-05s
Interoperability | Check the re-using of existing vocabs for Museum Finland took 2.384185791015625e-06s
Believability | Calculation of trust value for Museum Finland took 9.059906005859375e-06s
INFO | --- Analysis for FI-Museum took 3269.6513493061066s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.20252394676208496s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0006422996520996094s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 162.67491245269775s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.8472528457641602s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 42.95997405052185s
Interoperability | New terms check for Mapping Manuscript Migrations took 6.107710361480713s
Versatility | Languages check for Mapping Manuscript Migrations took 102.56801223754883s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 32.58744239807129s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.41258740425109863s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.18301033973693848s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.18968844413757324s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.16971659660339355s
License | MR license check for Mapping Manuscript Migrations took 0.18168115615844727s
License | HR license check for Mapping Manuscript Migrations took 1.6877436637878418s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.18125343322753906s
Understandability | Number of label check for Mapping Manuscript Migrations took 10.74191164970398s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.3727562427520752s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.16706395149230957s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.19595003128051758s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.1893761157989502s
Performance | Throughput check for Mapping Manuscript Migrations took 10.814861536026001s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 1.059483289718628s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.16388463973999023s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 0.5782406330108643s
Interlinking | skos check for Mapping Manuscript Migrations took 0.16525721549987793s
Interlinking | skos check for Mapping Manuscript Migrations took 0.16317296028137207s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.1621847152709961s
Currency | Creation date check for Mapping Manuscript Migrations took 0.3673868179321289s
Currency | Modification date check for Mapping Manuscript Migrations took 0.1950516700744629s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 88.85009169578552s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.19454169273376465s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.1769421100616455s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.17316985130310059s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 63.22888541221619s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.4511027336120605s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.812361717224121s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.2019822597503662s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 24.35604476928711s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 67.20858216285706s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.6061856746673584s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.6112091541290283s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.889418840408325s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.19840049743652344s
Security | Sign check for Mapping Manuscript Migrations took 0.18672442436218262s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 1641.836298942566s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 0.9687972068786621s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.02134418487548828s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 1.7404556274414062e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 2.1457672119140625e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 9.059906005859375e-06s
INFO | --- Analysis for MMM took 2395.678904056549s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.4983096122741699s
Availability | VoID file availability check for Semantic Kalevala took 0.0002930164337158203s
Extra | Recovery of all triples for Semantic Kalevala took 59.729429721832275s
Performance | Total latancy measurement for Semantic Kalevala took 0.8477392196655273s
Amount of data | Number of triples check for Semantic Kalevala took 0.4271533489227295s
Interoperability | New terms check for Semantic Kalevala took 2.3899879455566406s
Versatility | Languages check for Semantic Kalevala took 0.8859059810638428s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.3892526626586914s
Security | Check HTTPS for Semantic Kalevala took 0.4151155948638916s
Interpretability | RDF structures check for Semantic Kalevala took 0.23169922828674316s
Versatility | Serialization formats check for Semantic Kalevala took 0.19904208183288574s
Availability | RDF dump link check for Semantic Kalevala took 0.1634678840637207s
License | MR license check for Semantic Kalevala took 0.1658649444580078s
License | HR license check for Semantic Kalevala took 1.1444718837738037s
Amount of data | Number of property check for Semantic Kalevala took 0.20714521408081055s
Understandability | Number of label check for Semantic Kalevala took 0.39902830123901367s
Understandability | URI regex check for Semantic Kalevala took 0.3406689167022705s
Understandability | Vocabs check for Semantic Kalevala took 0.16428732872009277s
Verifiability | Authors check for Semantic Kalevala took 0.17897558212280273s
Verifiability | Publishers check for Semantic Kalevala took 0.19681859016418457s
Performance | Throughput check for Semantic Kalevala took 11.096900463104248s
Amount of data | Check the number of entities for Semantic Kalevala took 0.00010991096496582031s
Verifiability | Contribs. check for Semantic Kalevala took 0.17723655700683594s
Interlinking | sameAs chians check for Semantic Kalevala took 0.19410014152526855s
Interlinking | skos check for Semantic Kalevala took 0.29390668869018555s
Interlinking | skos check for Semantic Kalevala took 0.1756126880645752s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.15711712837219238s
Currency | Creation date check for Semantic Kalevala took 0.3703885078430176s
Currency | Modification date check for Semantic Kalevala took 0.36476874351501465s
Rep.Conc. | URIs length for Semantic Kalevala took 13.618234395980835s
Interoperability | New vocabularies check for Semantic Kalevala took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.20327472686767578s
Accuracy | Check Functional Property for Semantic Kalevala took 0.19481682777404785s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.17096614837646484s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 6.432842493057251s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.29538917541503906s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.4516685009002686s
Consistency | Disjoint class check for Semantic Kalevala took 0.16180920600891113s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.8024795055389404s
Consistency | Check Ontology hijacking for Semantic Kalevala took 3.5007948875427246s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.5266914367675781s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.7326581478118896s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.9247128963470459s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.2855668067932129s
Security | Sign check for Semantic Kalevala took 0.16989421844482422s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 3277.4744510650635s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 1.2492687702178955s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.5083582401275635s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.2159347534179688e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 1.9073486328125e-06s
Believability | Calculation of trust value for Semantic Kalevala took 8.344650268554688e-06s
INFO | --- Analysis for Semantic-Kalevala took 3411.8372399806976s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 0.9176125526428223s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.0003657341003417969s
Extra | Recovery of all triples for Smithsonian American Art Museum took 282.5131368637085s
Performance | Total latancy measurement for Smithsonian American Art Museum took 3.2072548866271973s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.6075541973114014s
Interoperability | New terms check for Smithsonian American Art Museum took 3.157780170440674s
Versatility | Languages check for Smithsonian American Art Museum took 39.35680794715881s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.5879733562469482s
Security | Check HTTPS for Smithsonian American Art Museum took 0.3579113483428955s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.611020565032959s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.6280221939086914s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.634392261505127s
License | MR license check for Smithsonian American Art Museum took 0.6450974941253662s
License | HR license check for Smithsonian American Art Museum took 20.24204182624817s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.6126139163970947s
Understandability | Number of label check for Smithsonian American Art Museum took 0.630650520324707s
Understandability | URI regex check for Smithsonian American Art Museum took 1.212327480316162s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.6171908378601074s
Verifiability | Authors check for Smithsonian American Art Museum took 0.6000382900238037s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.6152215003967285s
Performance | Throughput check for Smithsonian American Art Museum took 11.950339555740356s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 7.200241088867188e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.6198925971984863s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.617438554763794s
Interlinking | skos check for Smithsonian American Art Museum took 0.5799350738525391s
Interlinking | skos check for Smithsonian American Art Museum took 0.5894515514373779s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.5919573307037354s
Currency | Creation date check for Smithsonian American Art Museum took 1.217442512512207s
Currency | Modification date check for Smithsonian American Art Museum took 1.3235316276550293s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 106.78230905532837s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.5993442535400391s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 21.9459068775177s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.5017819404602051s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.288495302200317s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.5869655609130859s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 4.390176296234131s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 103.85480332374573s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.6783463954925537s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 7.2454352378845215s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.9076881408691406s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.6483221054077148s
Security | Sign check for Smithsonian American Art Museum took 0.6101324558258057s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.4335668087005615s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 1.3570003509521484s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.020478487014770508s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.239776611328125e-05s
Interoperability | Check the re-using of existing vocabs for Smithsonian American Art Museum took 2.384185791015625e-06s
Believability | Calculation of trust value for Smithsonian American Art Museum took 8.344650268554688e-06s
INFO | --- Analysis for Smithsonian took 733.1045446395874s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.19666814804077148s
Availability | VoID file availability check for Zeri Photo Archive took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.2711808681488037s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.02101731300354004s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.3113021850585938e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 8.58306884765625e-06s
INFO | --- Analysis for Zeri-Photo-Archive took 7.007456541061401s
Availability | SPARQL endpoint availability check for Archives Hub took 21.33738613128662s
Availability | VoID file availability check for Archives Hub took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.2590830326080322s
Reputation | Calculation of the PageRank for Archives Hub took 0.02090907096862793s
Interlinking | Calculation of Degree of Connection for Archives Hub took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.3828277587890625e-05s
Believability | Calculation of trust value for Archives Hub took 7.152557373046875e-06s
INFO | --- Analysis for Archives-Hub took 54.80839467048645s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.6059894561767578s
Availability | VoID file availability check for Yale centre of British Art took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.27944254875183105s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.02053999900817871s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.239776611328125e-05s
Believability | Calculation of trust value for Yale centre of British Art took 8.106231689453125e-06s
INFO | --- Analysis for Yale took 5.491461992263794s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 260.9021713733673s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.29694414138793945s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.020960092544555664s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 1.3828277587890625e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 8.344650268554688e-06s
INFO | --- Analysis for ADL took 538.3609228134155s
Availability | SPARQL endpoint availability check for MusicKG took 3.470027446746826s
Availability | VoID file availability check for MusicKG took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for MusicKG took 0.28006982803344727s
Reputation | Calculation of the PageRank for MusicKG took 0.021175146102905273s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.239776611328125e-05s
Believability | Calculation of trust value for MusicKG took 6.9141387939453125e-06s
INFO | --- Analysis for MusicKG took 9.086261749267578s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 0.8658177852630615s
Availability | VoID file availability check for CIDOC-CRM took 0.00034046173095703125s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.2796924114227295s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.02135014533996582s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.1920928955078125e-05s
Believability | Calculation of trust value for CIDOC-CRM took 7.62939453125e-06s
INFO | --- Analysis for CIDOC-CRM took 4.998895168304443s
Availability | SPARQL endpoint availability check for Mondis took 0.4504239559173584s
Availability | VoID file availability check for Mondis took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Mondis took 0.25562334060668945s
Reputation | Calculation of the PageRank for Mondis took 0.021451950073242188s
Interlinking | Calculation of Degree of Connection for Mondis took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Mondis took 0.001308441162109375s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.71661376953125e-05s
Believability | Calculation of trust value for Mondis took 8.344650268554688e-06s
INFO | --- Analysis for Mondis took 3.896120309829712s
Availability | SPARQL endpoint availability check for DigitalNZ took 3.4392824172973633s
Availability | VoID file availability check for DigitalNZ took 0.000606536865234375s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.7294924259185791s
Reputation | Calculation of the PageRank for DigitalNZ took 0.02047872543334961s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.2636184692382812e-05s
Believability | Calculation of trust value for DigitalNZ took 7.152557373046875e-06s
INFO | --- Analysis for DigitalNZ took 7.595820903778076s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.2156226634979248s
Availability | VoID file availability check for Fondazione Zeri took 0.0014176368713378906s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.25682640075683594s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.020788908004760742s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.239776611328125e-05s
Believability | Calculation of trust value for Fondazione Zeri took 7.152557373046875e-06s
INFO | --- Analysis for Fondazione-Zeri took 3.965582847595215s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 1.0406806468963623s
Availability | VoID file availability check for Digital Public Library of America took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.2646822929382324s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.02087235450744629s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.0010111331939697266s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.2874603271484375e-05s
Believability | Calculation of trust value for Digital Public Library of America took 7.62939453125e-06s
INFO | --- Analysis for Library-of-America took 4.634562969207764s
Availability | SPARQL endpoint availability check for Auckland Museum took 2.0585455894470215s
Availability | VoID file availability check for Auckland Museum took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.24978256225585938s
Reputation | Calculation of the PageRank for Auckland Museum took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.239776611328125e-05s
Believability | Calculation of trust value for Auckland Museum took 8.106231689453125e-06s
INFO | --- Analysis for Auckland-Museum took 7.414573431015015s
Availability | SPARQL endpoint availability check for National Library of Spain took 3.368746042251587s
Availability | VoID file availability check for National Library of Spain took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.26578307151794434s
Reputation | Calculation of the PageRank for National Library of Spain took 0.020642995834350586s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 1.2159347534179688e-05s
Believability | Calculation of trust value for National Library of Spain took 8.821487426757812e-06s
INFO | --- Analysis for BNE took 6.346019744873047s
Availability | SPARQL endpoint availability check for National Library of Korea took 2.4925262928009033s
Availability | VoID file availability check for National Library of Korea took 0.00028777122497558594s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.27496910095214844s
Reputation | Calculation of the PageRank for National Library of Korea took 0.020975351333618164s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.2874603271484375e-05s
Believability | Calculation of trust value for National Library of Korea took 9.298324584960938e-06s
INFO | --- Analysis for Korea-Library took 5.38371729850769s
Availability | SPARQL endpoint availability check for The State Russian Museum took 2.541141986846924s
Availability | VoID file availability check for The State Russian Museum took 0.0003056526184082031s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.2720332145690918s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.02185344696044922s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0008940696716308594s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 1.33514404296875e-05s
Believability | Calculation of trust value for The State Russian Museum took 9.5367431640625e-06s
INFO | --- Analysis for Russian-Museum took 5.442891836166382s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.7186079025268555s
Availability | VoID file availability check for National Library of Scotland took 0.0012698173522949219s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.28063416481018066s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.022476911544799805s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for National Library of Scotland took 1.3113021850585938e-05s
Believability | Calculation of trust value for National Library of Scotland took 8.106231689453125e-06s
INFO | --- Analysis for National-Library-of-Scotland took 7.075200080871582s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 0.34421300888061523s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.0004115104675292969s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.27329444885253906s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.021628379821777344s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.000957489013671875s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.4781951904296875e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 7.867813110351562e-06s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 3.9486076831817627s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.21164870262145996s
Availability | VoID file availability check for OntoComedySources took 0.0006923675537109375s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.24648785591125488s
Reputation | Calculation of the PageRank for OntoComedySources took 0.020745277404785156s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.33514404296875e-05s
Believability | Calculation of trust value for OntoComedySources took 9.5367431640625e-06s
INFO | --- Analysis for OntoComedySources took 4.454386472702026s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.21631193161010742s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0007555484771728516s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.2848489284515381s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.021095991134643555s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.2159347534179688e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 8.344650268554688e-06s
INFO | --- Analysis for OntoCeramic-2.0 took 4.454319477081299s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.1443319320678711s
Availability | VoID file availability check for SaintGall Ontology took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.27557873725891113s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.020715951919555664s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 1.52587890625e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.6927719116210938e-05s
Believability | Calculation of trust value for SaintGall Ontology took 9.298324584960938e-06s
INFO | --- Analysis for SaintGall-Ontology took 3.024792432785034s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.7356314659118652s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.000751495361328125s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.266772985458374s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.020776987075805664s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.3113021850585938e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 9.298324584960938e-06s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 3.78454852104187s
Availability | SPARQL endpoint availability check for ICON took 0.26120758056640625s
Availability | VoID file availability check for ICON took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for ICON took 0.2807118892669678s
Reputation | Calculation of the PageRank for ICON took 0.020860671997070312s
Interlinking | Calculation of Degree of Connection for ICON took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ICON took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for ICON took 1.1920928955078125e-05s
Believability | Calculation of trust value for ICON took 9.059906005859375e-06s
INFO | --- Analysis for ICON took 4.019506454467773s
Availability | SPARQL endpoint availability check for Polifonia took 0.2576789855957031s
Availability | VoID file availability check for Polifonia took 0.0003714561462402344s
Completeness | Calculation of interlinking completeness for Polifonia took 0.2727651596069336s
Reputation | Calculation of the PageRank for Polifonia took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.1444091796875e-05s
Believability | Calculation of trust value for Polifonia took 6.67572021484375e-06s
INFO | --- Analysis for Polifonia took 4.311863422393799s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 0.23553895950317383s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0007753372192382812s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.27441954612731934s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.02086043357849121s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.0008325576782226562s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.3113021850585938e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 8.58306884765625e-06s
INFO | --- Analysis for Atlas-of-Paths took 3.8043816089630127s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.19929909706115723s
Availability | VoID file availability check for Music Note Ontology took 0.0007343292236328125s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.2741875648498535s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.0210268497467041s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.2874603271484375e-05s
Believability | Calculation of trust value for Music Note Ontology took 8.344650268554688e-06s
INFO | --- Analysis for Music-Note-Ontology took 9.172698974609375s
Availability | SPARQL endpoint availability check for HaMSE took 0.1947016716003418s
Availability | VoID file availability check for HaMSE took 0.0007321834564208984s
Completeness | Calculation of interlinking completeness for HaMSE took 0.28318095207214355s
Reputation | Calculation of the PageRank for HaMSE took 0.02066969871520996s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.0967254638671875e-05s
Believability | Calculation of trust value for HaMSE took 8.58306884765625e-06s
INFO | --- Analysis for HaMSE took 4.722330570220947s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.10573887825012207s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0006916522979736328s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.2699902057647705s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.02141547203063965s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.2874603271484375e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 1.0013580322265625e-05s
INFO | --- Analysis for FOod took 3.346815347671509s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 0.7152132987976074s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.0006668567657470703s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.2667548656463623s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.021335363388061523s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for The ATLAS of Italian Digital Cultural Heritage took 1.2874603271484375e-05s
Believability | Calculation of trust value for The ATLAS of Italian Digital Cultural Heritage took 8.58306884765625e-06s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 5.098308086395264s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 1.5407638549804688s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.0007414817810058594s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.2818760871887207s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.02074575424194336s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.1682510375976562e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 9.5367431640625e-06s
INFO | --- Analysis for ARIADNE took 5.646044731140137s
Availability | SPARQL endpoint availability check for Nomisma.org  took 3.5598320960998535s
Availability | VoID file availability check for Nomisma.org  took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 0.27097558975219727s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.020487546920776367s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 0.00013065338134765625s
Believability | Calculation of trust value for Nomisma.org  took 8.344650268554688e-06s
INFO | --- Analysis for nomisma_org took 25.443432569503784s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.267692565917969e-05s
Availability | VoID file availability check for Discogs in RDF took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.2669491767883301s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.512901306152344e-05s
Believability | Calculation of trust value for Discogs in RDF took 9.059906005859375e-06s
INFO | --- Analysis for data-incubator-discogs took 6.72472882270813s
Availability | SPARQL endpoint availability check for Enslaved.org took 4.267692565917969e-05s
Availability | VoID file availability check for Enslaved.org took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.2760181427001953s
Reputation | Calculation of the PageRank for Enslaved.org took 0.02077198028564453s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.0279159545898438e-05s
Believability | Calculation of trust value for Enslaved.org took 8.344650268554688e-06s
INFO | --- Analysis for enslaved.org took 4.830732822418213s
Availability | SPARQL endpoint availability check for EventKG took 5.459785461425781e-05s
Availability | VoID file availability check for EventKG took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for EventKG took 0.26966094970703125s
Reputation | Calculation of the PageRank for EventKG took 0.020664215087890625s
Interlinking | Calculation of Degree of Connection for EventKG took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.511543273925781e-05s
Believability | Calculation of trust value for EventKG took 8.344650268554688e-06s
INFO | --- Analysis for eventkg took 5.42076563835144s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.7483937740325928s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0007274150848388672s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.2708625793457031s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.02070450782775879s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 7.772445678710938e-05s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 5.7220458984375e-06s
INFO | --- Analysis for roceeh-road took 3.9774017333984375s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.27921128273010254s
Availability | VoID file availability check for Thesaurus BNCF took 0.0006155967712402344s
Extra | Recovery of all triples for Thesaurus BNCF took 58.50984597206116s
Performance | Total latancy measurement for Thesaurus BNCF took 0.47284412384033203s
Amount of data | Number of triples check for Thesaurus BNCF took 0.7529606819152832s
Interoperability | New terms check for Thesaurus BNCF took 1.4868338108062744s
Versatility | Languages check for Thesaurus BNCF took 8.89637017250061s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 1.1587855815887451s
Interpretability | RDF structures check for Thesaurus BNCF took 0.06774163246154785s
Versatility | Serialization formats check for Thesaurus BNCF took 0.05396413803100586s
Availability | RDF dump link check for Thesaurus BNCF took 0.06005358695983887s
License | MR license check for Thesaurus BNCF took 0.049471139907836914s
License | HR license check for Thesaurus BNCF took 0.17647457122802734s
Amount of data | Number of property check for Thesaurus BNCF took 0.057698726654052734s
Understandability | Number of label check for Thesaurus BNCF took 0.23624777793884277s
Understandability | URI regex check for Thesaurus BNCF took 0.10964322090148926s
Understandability | Vocabs check for Thesaurus BNCF took 0.05657958984375s
Verifiability | Authors check for Thesaurus BNCF took 0.05484747886657715s
Verifiability | Publishers check for Thesaurus BNCF took 0.06052422523498535s
Performance | Throughput check for Thesaurus BNCF took 10.333091974258423s
Amount of data | Check the number of entities for Thesaurus BNCF took 7.867813110351562e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.06304717063903809s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.06028866767883301s
Interlinking | skos check for Thesaurus BNCF took 0.15672087669372559s
Interlinking | skos check for Thesaurus BNCF took 0.15997838973999023s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.05926227569580078s
Currency | Creation date check for Thesaurus BNCF took 0.12654948234558105s
Currency | Modification date check for Thesaurus BNCF took 0.12362051010131836s
Rep.Conc. | URIs length for Thesaurus BNCF took 27.640785932540894s
Interoperability | New vocabularies check for Thesaurus BNCF took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.05495595932006836s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.052608489990234375s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.051955461502075195s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 13.71430516242981s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.5058631896972656s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 4.022359371185303s
Consistency | Disjoint class check for Thesaurus BNCF took 0.05745077133178711s
Consistency | Check Misplaced properties for Thesaurus BNCF took 1.1989719867706299s
Consistency | Misplaced classes for Thesaurus BNCF took 6.750003099441528s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 8.048250675201416s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.504650592803955s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.439974069595337s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.4093525409698486s
Security | Sign check for Thesaurus BNCF took 0.0682377815246582s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 21.36256194114685s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.31928038597106934s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020842790603637695s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 8.20159912109375e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 2.384185791015625e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 6.67572021484375e-06s
INFO | --- Analysis for bncf-ns took 207.02544569969177s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.6312642097473145s
Availability | VoID file availability check for COURAGE Dataset took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.26106929779052734s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.020148038864135742s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 2.956390380859375e-05s
Believability | Calculation of trust value for COURAGE Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for http:cultural-opposition.eu took 5.2895989418029785s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.410743713378906e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.2846982479095459s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.020221233367919922s
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.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.00543212890625e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 6.67572021484375e-06s
INFO | --- Analysis for bll-thesaurus took 3.6474151611328125s
Availability | SPARQL endpoint availability check for Inztrow took 4.315376281738281e-05s
Availability | VoID file availability check for Inztrow took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for Inztrow took 0.26746153831481934s
Reputation | Calculation of the PageRank for Inztrow took 0.0205533504486084s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Inztrow took 3.266334533691406e-05s
Believability | Calculation of trust value for Inztrow took 8.58306884765625e-06s
INFO | --- Analysis for Inztrow took 4.030146598815918s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 30.10061502456665s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0007786750793457031s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.3928353786468506s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.020957469940185547s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 5.984306335449219e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 9.059906005859375e-06s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 183.032732963562s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.1961669921875e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.2938528060913086s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.021155834197998047s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.218650817871094e-05s
Believability | Calculation of trust value for Temples of the Classical World took 7.152557373046875e-06s
INFO | --- Analysis for classical_temples took 3.6476638317108154s
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 4.041769981384277s
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.000530242919921875s
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.25272488594055176s
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.020462989807128906s
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.6927719116210938e-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.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 8.535385131835938e-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 8.106231689453125e-06s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 12.761238098144531s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.389195203781128s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.2751619815826416s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.020858049392700195s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.441375732421875e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 8.821487426757812e-06s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 12.770312309265137s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.4166078567504883s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.3095362186431885s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.020711183547973633s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.410743713378906e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-CRB took 14.793041229248047s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.383283853530884s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.2532846927642822s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.020653247833251953s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.202957153320312e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 11.61790919303894s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.382232904434204s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0010666847229003906s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.26928114891052246s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.020651817321777344s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.7670135498046875e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 1.1682510375976562e-05s
INFO | --- Analysis for ASCDC-DQOT took 12.733826637268066s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.38274884223938s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0006365776062011719s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.2796468734741211s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.02046799659729004s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 9.083747863769531e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-IHP-WCD took 12.72508192062378s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 3.449037551879883s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0006616115570068359s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.3808424472808838s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.440017700195312e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.2874603271484375e-05s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 15.487478017807007s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.392064094543457s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006728172302246094s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.25391268730163574s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.021051645278930664s
Interlinking | Calculation of Degree of Connection for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.5789947509765625e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.1205673217773438e-05s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 11.72900938987732s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.413522720336914s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0003490447998046875s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.23157572746276855s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.02036452293395996s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.364418029785156e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 8.106231689453125e-06s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 11.571962118148804s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 5.936622619628906e-05s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.2571909427642822s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.020447731018066406s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.744529724121094e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 6.198883056640625e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 12.107630252838135s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.3954126834869385s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.2776923179626465s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.02075815200805664s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 8.225440979003906e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 11.174630403518677s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 2.381082534790039s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.2694864273071289s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.021462678909301758s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.678436279296875e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.821487426757812e-06s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 11.753887414932251s
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.407970666885376s
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.0006756782531738281s
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.2696113586425781s
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.020799875259399414s
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.239776611328125e-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.0007872581481933594s
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.630752563476562e-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.821487426757812e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 12.706934928894043s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.395232915878296s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.27039456367492676s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.020729780197143555s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.649162292480469e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC_-_DNB took 11.159982442855835s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 2.5640125274658203s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0007135868072509766s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 4.365065574645996s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 4.018925666809082s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.4738166332244873s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.8685920238494873s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 47.41382694244385s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 1.0491714477539062s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.5292994976043701s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.6007978916168213s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.4230024814605713s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 1.427476167678833s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 1.833326816558838s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 21.365601778030396s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 1.086679220199585s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.9690039157867432s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 1.3573386669158936s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.7197258472442627s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 1.6367175579071045s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.8543729782104492s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 18.898821353912354s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 7.390975952148438e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.6926474571228027s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 2.57086181640625s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.5700569152832031s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.39876317977905273s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.4255869388580322s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 4.04361367225647s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 1.4597105979919434s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 3.792492389678955s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.9510924816131592s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.6390385627746582s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.793860912322998s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 6.401082754135132s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.03343820571899414s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.02814793586730957s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.49225425720214844s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.7969083786010742s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 1.9606306552886963s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 3.2017130851745605s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.3395581245422363s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 3.1860108375549316s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.03494572639465332s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 2.129751443862915s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 1.4953405857086182s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 3104.3091027736664s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 1.3328535556793213s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.02088141441345215s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.14984130859375e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.430511474609375e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 7.62939453125e-06s
INFO | --- Analysis for BVMC took 3299.6656708717346s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 393.08161520957947s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.26818227767944336s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.021036386489868164s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 3.910064697265625e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 8.58306884765625e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 801.5956196784973s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.742070198059082s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.26569199562072754s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.020908594131469727s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0009944438934326172s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 4.76837158203125e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 7.62939453125e-06s
INFO | --- Analysis for LucaniPharsalia took 5.913487911224365s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.5919816493988037s
Availability | VoID file availability check for Querolus in LiLa took 0.00035119056701660156s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.2247905731201172s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.02030348777770996s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 4.00543212890625e-05s
Believability | Calculation of trust value for Querolus in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for Querolus took 4.362370014190674s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.536501407623291s
Availability | VoID file availability check for UDante in LiLa took 0.0006814002990722656s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.2765657901763916s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.02058553695678711s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 3.600120544433594e-05s
Believability | Calculation of trust value for UDante in LiLa took 1.8596649169921875e-05s
INFO | --- Analysis for UDante took 4.923975706100464s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4047985076904297s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0005326271057128906s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.5995097160339355s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.6947846412658691s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.25179147720336914s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6763880252838135s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.14070653915405s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1418755054473877s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3776211738586426s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15168094635009766s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16460013389587402s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.23867225646972656s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.35134148597717285s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16396665573120117s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.34110188484191895s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.31895995140075684s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.19992876052856445s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.20319294929504395s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.183058500289917s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.77549695968628s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.510185241699219e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.24728822708129883s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.36403703689575195s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.39573025703430176s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14071011543273926s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15697431564331055s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5822582244873047s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.19516301155090332s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.153996229171753s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16028761863708496s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.2620580196380615s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.2373361587524414s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 1.1484136581420898s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.029540061950683594s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.02808237075805664s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.35666775703430176s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.1809179782867432s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 2.0298843383789062s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.3053491115570068s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.4355976581573486s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.030633926391601562s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.18898820877075195s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2508695125579834s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 1943.694087266922s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.542039155960083s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.020296573638916016s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.553794860839844e-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.867813110351562e-06s
INFO | --- Analysis for ceo took 2068.9948432445526s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.5548727512359619s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0006873607635498047s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 114.88387060165405s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.6164181232452393s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.6985528469085693s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.1870968341827393s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.6762323379516602s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.6058416366577148s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.3284785747528076s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.2968597412109375s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 12.611135244369507s
License | MR license check for Cultural Heritage Thesaurus took 0.33446478843688965s
License | HR license check for Cultural Heritage Thesaurus took 0.37358903884887695s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.2933797836303711s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.30453038215637207s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.6609373092651367s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.2862968444824219s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.32120847702026367s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.34375429153442383s
Performance | Throughput check for Cultural Heritage Thesaurus took 12.296939849853516s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 8.273124694824219e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.3164081573486328s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.322070837020874s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.3461282253265381s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.349973201751709s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.31428027153015137s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.5958020687103271s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.5979671478271484s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 33.47015357017517s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.28734350204467773s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.3572869300842285s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.3704812526702881s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 6.583388805389404s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.22179532051086426s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.2976813316345215s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.0114436149597168s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.31130385398864746s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 7.740257024765015s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.295767068862915s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00014925003051757812s
Security | Sign check for Cultural Heritage Thesaurus took 0.3298497200012207s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 263.23873805999756s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.9348156452178955s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 1.079078197479248s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.0001289844512939453s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 1.0013580322265625e-05s
INFO | --- Analysis for cht took 497.9478166103363s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 1.0725023746490479s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0006291866302490234s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.3015141487121582s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020335674285888672s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 8.440017700195312e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 8.344650268554688e-06s
INFO | --- Analysis for greekchildrensartmuseum took 6.097582101821899s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 4.506111145019531e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.000713348388671875s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.2681095600128174s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020781993865966797s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.891654968261719e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 8.106231689453125e-06s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 2.500059127807617s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.666965961456299s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.26714611053466797s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.020357608795166016s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.482269287109375e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 7.867813110351562e-06s
INFO | --- Analysis for ldt@library took 36.887760639190674s
Availability | SPARQL endpoint availability check for Muziekweb took 0.698859691619873s
Availability | VoID file availability check for Muziekweb took 0.0006794929504394531s
Extra | Recovery of all triples for Muziekweb took 1.8541662693023682s
Performance | Total latancy measurement for Muziekweb took 1.4253878593444824s
Amount of data | Number of triples check for Muziekweb took 0.38588428497314453s
Interoperability | New terms check for Muziekweb took 1.6739811897277832s
Versatility | Languages check for Muziekweb took 54.99208402633667s
Interpretability | Number of blank nodes check for Muziekweb took 0.30005812644958496s
Interpretability | RDF structures check for Muziekweb took 0.7148494720458984s
Versatility | Serialization formats check for Muziekweb took 0.2925412654876709s
Availability | RDF dump link check for Muziekweb took 0.3043205738067627s
License | MR license check for Muziekweb took 0.33551836013793945s
License | HR license check for Muziekweb took 11.496371269226074s
Amount of data | Number of property check for Muziekweb took 0.31149864196777344s
Understandability | Number of label check for Muziekweb took 0.6945714950561523s
Understandability | URI regex check for Muziekweb took 0.5933828353881836s
Understandability | Vocabs check for Muziekweb took 0.28745126724243164s
Verifiability | Authors check for Muziekweb took 0.3125309944152832s
Verifiability | Publishers check for Muziekweb took 0.3125121593475342s
Performance | Throughput check for Muziekweb took 11.239663124084473s
Amount of data | Check the number of entities for Muziekweb took 7.081031799316406e-05s
Verifiability | Contribs. check for Muziekweb took 0.32308101654052734s
Interlinking | sameAs chians check for Muziekweb took 0.272824764251709s
Interlinking | skos check for Muziekweb took 0.32066893577575684s
Interlinking | skos check for Muziekweb took 0.27829694747924805s
Timeliness | dataset update frequency check for Muziekweb took 0.25674939155578613s
Currency | Creation date check for Muziekweb took 0.8257596492767334s
Currency | Modification date check for Muziekweb took 0.7810385227203369s
Rep.Conc. | URIs length for Muziekweb took 1.8381714820861816s
Interoperability | New vocabularies check for Muziekweb took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.3102569580078125s
Accuracy | Check Functional Property for Muziekweb took 0.49002885818481445s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.5173499584197998s
Accuracy | Check Empty annotation labels for Muziekweb took 0.9490077495574951s
Accuracy | Check White space in annotation for Muziekweb took 0.027992963790893555s
Accuracy | Check Datatype consistency for Muziekweb took 0.0290071964263916s
Consistency | Disjoint class check for Muziekweb took 0.44664573669433594s
Consistency | Check Misplaced properties for Muziekweb took 1.122335433959961s
Consistency | Check Ontology hijacking for Muziekweb took 2.2660441398620605s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.3442482948303223s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.6451749801635742s
Conciseness | Check Extensional conciseness for Muziekweb took 0.0431056022644043s
Conciseness | Check Intensional conciseness for Muziekweb took 0.301196813583374s
Security | Sign check for Muziekweb took 0.2957029342651367s
Availability | Check URIs Dereferenciability for Muziekweb took 1722.919715642929s
Completeness | Calculation of interlinking completeness for Muziekweb took 1.7062032222747803s
Reputation | Calculation of the PageRank for Muziekweb took 0.020852088928222656s
Interlinking | Calculation of Degree of Connection for Muziekweb took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Muziekweb took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 6.031990051269531e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.1920928955078125e-06s
Believability | Calculation of trust value for Muziekweb took 9.298324584960938e-06s
INFO | --- Analysis for muziekweb took 1851.75692152977s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 5.889324426651001s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0007107257843017578s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.27948474884033203s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.020592451095581055s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 9.679794311523438e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 7.867813110351562e-06s
INFO | --- Analysis for nom took 22.81596851348877s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.8126068115234375s
Availability | VoID file availability check for Linked Stage Graph took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.2522761821746826s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.020596981048583984s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 4.982948303222656e-05s
Believability | Calculation of trust value for Linked Stage Graph took 7.62939453125e-06s
INFO | --- Analysis for slod took 4.646398305892944s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 0.5877232551574707s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.25591111183166504s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.020812511444091797s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 8.130073547363281e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 9.059906005859375e-06s
INFO | --- Analysis for wasabi took 5.629233360290527s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.220055103302002s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.2590789794921875s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 3.0279159545898438e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 8.344650268554688e-06s
INFO | --- Analysis for wl-kg took 3.840651512145996s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.0008885860443115234s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.26685500144958496s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 5.507469177246094e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for yso took 5.6167943477630615s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.4345855712890625e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0003066062927246094s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2711772918701172s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020662546157836914s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.8623809814453125e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 8.106231689453125e-06s
INFO | --- Analysis for ISSN:0080-3626 took 2.3471152782440186s
Availability | SPARQL endpoint availability check for Copyright Free Music took 4.172325134277344e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0007092952728271484s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.26740026473999023s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.020276308059692383s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 3.0517578125e-05s
Believability | Calculation of trust value for Copyright Free Music took 6.4373016357421875e-06s
INFO | --- Analysis for Copyright_Free_Music took 3.6917712688446045s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 6.031990051269531e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.6780102252960205s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 3.1948089599609375e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.1920928955078125e-05s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.724757194519043s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 5.173683166503906e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.25093531608581543s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.02042365074157715s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 2.9087066650390625e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 8.106231689453125e-06s
INFO | --- Analysis for Sherry_Wine took 2.59222674369812s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.315376281738281e-05s
Availability | VoID file availability check for Sherry Wine took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.25974273681640625s
Reputation | Calculation of the PageRank for Sherry Wine took 0.020354509353637695s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 2.9325485229492188e-05s
Believability | Calculation of trust value for Sherry Wine took 6.198883056640625e-06s
INFO | --- Analysis for Sherry_Wine_ took 2.3635783195495605s
Availability | SPARQL endpoint availability check for Freeyork took 4.458427429199219e-05s
Availability | VoID file availability check for Freeyork took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Freeyork took 0.27167630195617676s
Reputation | Calculation of the PageRank for Freeyork took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.0001049041748046875s
Believability | Calculation of trust value for Freeyork took 8.58306884765625e-06s
INFO | --- Analysis for freeyork-org took 3.020824432373047s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.38690185546875e-05s
Availability | VoID file availability check for Informatics Studies took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.2781243324279785s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020404338836669922s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 2.8848648071289062e-05s
Believability | Calculation of trust value for Informatics Studies took 6.4373016357421875e-06s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 2.8869330883026123s
Availability | SPARQL endpoint availability check for MappingChange took 4.100799560546875e-05s
Availability | VoID file availability check for MappingChange took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for MappingChange took 0.2397749423980713s
Reputation | Calculation of the PageRank for MappingChange took 0.020394325256347656s
Interlinking | Calculation of Degree of Connection for MappingChange took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for MappingChange took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for MappingChange took 1.1444091796875e-05s
Believability | Calculation of trust value for MappingChange took 9.059906005859375e-06s
INFO | --- Analysis for mappingch took 2.895372152328491s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Odeuropa Ontology took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.26661133766174316s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.1444091796875e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 7.867813110351562e-06s
INFO | --- Analysis for Odeuropa took 2.9136409759521484s

--- Total time for analysis:257958.86990761757s ---
--- Total time for analysis:71.65524164100488 hours ---