Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.06634926795959473s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.6821267604827881s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.5447566509246826s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 0.0003981590270996094s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 7.152557373046875e-06s
INFO | --- Analysis for 2000-us-census-rdf took 5.15224027633667s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 2.666679620742798s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.26972341537475586s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.01987934112548828s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 4.0531158447265625e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 5.4836273193359375e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 8.139567375183105s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.1484832763671875e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.260272741317749s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.02015209197998047s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 3.4809112548828125e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 6.4373016357421875e-06s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 3.547680139541626s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.38188958168029785s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.29470205307006836s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.019942045211791992s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00010275840759277344s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 7.62939453125e-06s
INFO | --- Analysis for abs-linked-data took 3.189821481704712s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 4.267692565917969e-05s
Availability | VoID file availability check for Academic Offer of UNL took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.2645440101623535s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.020316362380981445s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 3.24249267578125e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 7.3909759521484375e-06s
INFO | --- Analysis for academic-offer-of-unl took 2.9308056831359863s
Availability | SPARQL endpoint availability check for AcadOnto took 4.506111145019531e-05s
Availability | VoID file availability check for AcadOnto took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.2737421989440918s
Reputation | Calculation of the PageRank for AcadOnto took 0.02023005485534668s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 3.24249267578125e-05s
Believability | Calculation of trust value for AcadOnto took 3.4809112548828125e-05s
INFO | --- Analysis for acadonto took 2.9362637996673584s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.288676977157593s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007166862487792969s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.2936382293701172s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.019864797592163086s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.814697265625e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.4543533325195312e-05s
INFO | --- Analysis for acorn-sat took 36.41527771949768s
Availability | SPARQL endpoint availability check for Addgene took 4.1961669921875e-05s
Availability | VoID file availability check for Addgene took 0.0007674694061279297s
Completeness | Calculation of interlinking completeness for Addgene took 0.6951999664306641s
Reputation | Calculation of the PageRank for Addgene took 0.019984960556030273s
Interlinking | Calculation of Degree of Connection for Addgene took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.361701965332031e-05s
Believability | Calculation of trust value for Addgene took 6.9141387939453125e-06s
INFO | --- Analysis for addgene took 16.288276195526123s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.267692565917969e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0006847381591796875s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.24165058135986328s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.020408153533935547s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0008261203765869141s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.894371032714844e-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.688475370407104s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.6172568798065186s
Availability | VoID file availability check for AEMET metereological dataset took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.26662588119506836s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.020194530487060547s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.7670135498046875e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 7.152557373046875e-06s
INFO | --- Analysis for aemet took 5.331063985824585s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 4.00543212890625e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0004203319549560547s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.2653186321258545s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.02044081687927246s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 4.792213439941406e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 6.198883056640625e-06s
INFO | --- Analysis for agenda-de-zaragoza took 3.4389538764953613s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.040349721908569336s
Availability | VoID file availability check for AgriNepalData took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.2702634334564209s
Reputation | Calculation of the PageRank for AgriNepalData took 0.02043628692626953s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 7.271766662597656e-05s
Believability | Calculation of trust value for AgriNepalData took 9.775161743164062e-06s
INFO | --- Analysis for agrinepaldata took 2.4382150173187256s
Availability | SPARQL endpoint availability check for AGRIS took 262.04614543914795s
Availability | VoID file availability check for AGRIS took 0.0007565021514892578s
Completeness | Calculation of interlinking completeness for AGRIS took 0.3016397953033447s
Reputation | Calculation of the PageRank for AGRIS took 0.020395994186401367s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for AGRIS took 0.00014591217041015625s
Believability | Calculation of trust value for AGRIS took 7.867813110351562e-06s
INFO | --- Analysis for agris took 555.2275528907776s
Availability | SPARQL endpoint availability check for AGROVOC took 4.3392181396484375e-05s
Availability | VoID file availability check for AGROVOC took 0.0002949237823486328s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.2842247486114502s
Reputation | Calculation of the PageRank for AGROVOC took 0.022190332412719727s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0008533000946044922s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 7.486343383789062e-05s
Believability | Calculation of trust value for AGROVOC took 9.059906005859375e-06s
INFO | --- Analysis for agrovoc-skos took 4.303518533706665s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 4.363059997558594e-05s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.713320255279541s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.02026963233947754s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 3.528594970703125e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 7.867813110351562e-06s
INFO | --- Analysis for aksworg took 3.4438135623931885s
Availability | SPARQL endpoint availability check for AlchemyAPI took 4.172325134277344e-05s
Availability | VoID file availability check for AlchemyAPI took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.2623882293701172s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.02024531364440918s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 3.2901763916015625e-05s
Believability | Calculation of trust value for AlchemyAPI took 7.867813110351562e-06s
INFO | --- Analysis for alchemyapi took 3.3674046993255615s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 4.38690185546875e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.2578904628753662s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.02127385139465332s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0009562969207763672s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 4.124641418457031e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 8.58306884765625e-06s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 2.959718942642212s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.1655421257019043s
Availability | VoID file availability check for aliada-scanbit-net took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.26647067070007324s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.021641254425048828s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00011515617370605469s
Believability | Calculation of trust value for aliada-scanbit-net took 8.344650268554688e-06s
INFO | --- Analysis for aliada-scanbit-net took 4.790477991104126s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 5.53131103515625e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.00039196014404296875s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.2655494213104248s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.02040243148803711s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 3.314018249511719e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 9.059906005859375e-06s
INFO | --- Analysis for allen-brain-atlas took 2.975767135620117s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 0.9436807632446289s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0007622241973876953s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 137.98223400115967s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.7545695304870605s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.453535556793213s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.6762354373931885s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.0071351528168s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 3.341172933578491s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8791074752807617s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.8973495960235596s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.7199044227600098s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.6216847896575928s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.644437313079834s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 32.87313175201416s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.5654919147491455s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.7573091983795166s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.1013052463531494s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.6106119155883789s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.6677460670471191s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.6114060878753662s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.784290552139282s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 7.390975952148438e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5351991653442383s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.5687122344970703s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6567738056182861s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6623270511627197s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.6268808841705322s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.1938631534576416s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.1269900798797607s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 55.451998233795166s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 4.613864898681641s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.571162223815918s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6154735088348389s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6224958896636963s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 35.77418327331543s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.0961215496063232s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.653437614440918s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.6441712379455566s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 11.087069034576416s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.91989541053772s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 33.48283386230469s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.4583923816680908s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.863768339157104s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.7670366764068604s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8393566608428955s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.5633895397186279s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 12513.853022098541s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 1.5852315425872803s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.023244619369506836s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 0.00012350082397460938s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 5.5093700885772705s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 9.298324584960938e-06s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 13272.997816085815s
Availability | SPARQL endpoint availability check for Alojamientos took 4.1961669921875e-05s
Availability | VoID file availability check for Alojamientos took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.719836950302124s
Reputation | Calculation of the PageRank for Alojamientos took 0.020630359649658203s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 3.1948089599609375e-05s
Believability | Calculation of trust value for Alojamientos took 1.1444091796875e-05s
INFO | --- Analysis for alojamientos-zaragoza took 4.244676351547241s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.28493452072143555s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.2644803524017334s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.020563125610351562s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 4.0531158447265625e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 6.4373016357421875e-06s
INFO | --- Analysis for alpino-rdf took 4.082330226898193s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 4.1484832763671875e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.00028777122497558594s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.24263334274291992s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 3.170967102050781e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 6.4373016357421875e-06s
INFO | --- Analysis for am-collections-online took 2.9712655544281006s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0003974437713623047s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.2644801139831543s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0204617977142334s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.24249267578125e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for amon took 3.3233723640441895s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.7642505168914795s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.2711629867553711s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.020294904708862305s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.179115295410156e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.1205673217773438e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 3.8233401775360107s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 5.4836273193359375e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.00022292137145996094s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.27677106857299805s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.020529747009277344s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 3.147125244140625e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 8.106231689453125e-06s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 3.3817648887634277s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 4.172325134277344e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.26732516288757324s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.020670413970947266s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 3.24249267578125e-05s
Believability | Calculation of trust value for Animal Diversity Web took 6.4373016357421875e-06s
INFO | --- Analysis for animal-diversity-web took 2.974203586578369s
Availability | SPARQL endpoint availability check for apache took 4.363059997558594e-05s
Availability | VoID file availability check for apache took 0.001135110855102539s
Completeness | Calculation of interlinking completeness for apache took 0.2844204902648926s
Reputation | Calculation of the PageRank for apache took 0.020409822463989258s
Interlinking | Calculation of Degree of Connection for apache took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for apache took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for apache took 5.984306335449219e-05s
Believability | Calculation of trust value for apache took 5.9604644775390625e-06s
INFO | --- Analysis for apache took 3.3766167163848877s
Availability | SPARQL endpoint availability check for Apertium RDF took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF took 0.0006108283996582031s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.25330162048339844s
Reputation | Calculation of the PageRank for Apertium RDF took 0.020557165145874023s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.649162292480469e-05s
Believability | Calculation of trust value for Apertium RDF took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf took 8.073127031326294s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.2883305549621582s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.020601987838745117s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 6.318092346191406e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-ca-it took 5.753910064697266s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 5.936622619628906e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.2687349319458008s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.020702362060546875s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.6253204345703125e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-en-ca took 5.606152534484863s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.26582884788513184s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.020360708236694336s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-en-es took 6.89749550819397s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0006833076477050781s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.2795069217681885s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.020436763763427734s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.649162292480469e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-en-gl took 5.685519456863403s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 4.267692565917969e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.277310848236084s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.0202484130859375s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.267692565917969e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.6144936084747314s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 7.796287536621094e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.24945878982543945s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.649162292480469e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-eo-en took 5.516491413116455s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 4.267692565917969e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.2521822452545166s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.021017074584960938s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.696846008300781e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 8.58306884765625e-06s
INFO | --- Analysis for apertium-rdf-eo-es took 5.545809745788574s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0006990432739257812s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.27118682861328125s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.02057623863220215s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 7.176399230957031e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.502596139907837s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.2797508239746094s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.020462989807128906s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-es-an took 5.605693817138672s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 5.1021575927734375e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.27138733863830566s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.02033209800720215s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 5.521891355514526s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0007734298706054688s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.2691795825958252s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020543813705444336s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 6.198883056640625e-06s
INFO | --- Analysis for apertium-rdf-es-ca took 25.264398097991943s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 0.00011157989501953125s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0007765293121337891s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.2936398983001709s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-es-gl took 5.514553546905518s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 4.458427429199219e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.27327871322631836s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 5.574633598327637s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.2621495723724365s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.02024388313293457s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-es-ro took 5.598776340484619s
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.0005865097045898438s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.26221442222595215s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.020999431610107422s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.3392181396484375e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-eu-en took 5.720895290374756s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 4.506111145019531e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0007231235504150391s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.2846052646636963s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.02074432373046875s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0010564327239990234s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.887580871582031e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-eu-es took 5.603407144546509s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.291534423828125e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.24669790267944336s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.020273447036743164s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.541961908340454s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 7.486343383789062e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.00040650367736816406s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.2548069953918457s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020297527313232422s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-fr-es took 5.5364909172058105s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0010051727294921875s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.2554922103881836s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.02044057846069336s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 5.030632019042969e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 8.344650268554688e-06s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.582473278045654s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 4.458427429199219e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.2783079147338867s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.020715713500976562s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 5.054473876953125e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.33514404296875e-05s
INFO | --- Analysis for apertium-rdf-oc-es took 5.5491392612457275s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.00041556358337402344s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.26589417457580566s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.02124762535095215s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0008158683776855469s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.8160552978515625e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-pt-ca took 5.625482797622681s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 4.4345855712890625e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.26914501190185547s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.020282506942749023s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.3247740268707275s
Availability | SPARQL endpoint availability check for AragoDBPedia took 0.7819130420684814s
Availability | VoID file availability check for AragoDBPedia took 0.0005779266357421875s
Extra | Recovery of all triples for AragoDBPedia took 3.6263365745544434s
Performance | Total latancy measurement for AragoDBPedia took 1.889176607131958s
Amount of data | Number of triples check for AragoDBPedia took 1.2288787364959717s
Interoperability | New terms check for AragoDBPedia took 2.2005815505981445s
Versatility | Languages check for AragoDBPedia took 60.545920848846436s
Interpretability | Number of blank nodes check for AragoDBPedia took 5.021130084991455s
Security | Check HTTPS for AragoDBPedia took 0.237335205078125s
Interpretability | RDF structures check for AragoDBPedia took 2.25307035446167s
Versatility | Serialization formats check for AragoDBPedia took 1.7436845302581787s
Availability | RDF dump link check for AragoDBPedia took 0.4178946018218994s
License | MR license check for AragoDBPedia took 1.182037353515625s
License | HR license check for AragoDBPedia took 8.000348329544067s
Amount of data | Number of property check for AragoDBPedia took 0.41259145736694336s
Understandability | Number of label check for AragoDBPedia took 0.9396507740020752s
Understandability | URI regex check for AragoDBPedia took 1.0129523277282715s
Understandability | Vocabs check for AragoDBPedia took 0.4577641487121582s
Verifiability | Authors check for AragoDBPedia took 0.7709898948669434s
Verifiability | Publishers check for AragoDBPedia took 0.4391968250274658s
Performance | Throughput check for AragoDBPedia took 11.612236738204956s
Amount of data | Check the number of entities for AragoDBPedia took 7.295608520507812e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.6455028057098389s
Interlinking | sameAs chians check for AragoDBPedia took 0.49088454246520996s
Interlinking | skos check for AragoDBPedia took 1.214202880859375s
Interlinking | skos check for AragoDBPedia took 0.3838777542114258s
Timeliness | dataset update frequency check for AragoDBPedia took 1.097212553024292s
Currency | Creation date check for AragoDBPedia took 2.0047693252563477s
Currency | Modification date check for AragoDBPedia took 0.9950675964355469s
Rep.Conc. | URIs length for AragoDBPedia took 6.131403923034668s
Interoperability | New vocabularies check for AragoDBPedia took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.38490843772888184s
Accuracy | Check Functional Property for AragoDBPedia took 0.5488190650939941s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.6280474662780762s
Accuracy | Check Empty annotation labels for AragoDBPedia took 1.4753403663635254s
Accuracy | Check White space in annotation for AragoDBPedia took 0.030722618103027344s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.026999235153198242s
Consistency | Disjoint class check for AragoDBPedia took 0.6950819492340088s
Consistency | Check Misplaced properties for AragoDBPedia took 4.852322340011597s
Consistency | Misplaced classes for AragoDBPedia took 0.67283034324646s
Consistency | Check Ontology hijacking for AragoDBPedia took 2.9024243354797363s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.3515219688415527s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 5.597384214401245s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.03188443183898926s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.5469717979431152s
Security | Sign check for AragoDBPedia took 0.864396333694458s
Availability | Check URIs Dereferenciability for AragoDBPedia took 3348.0807688236237s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 1.5163581371307373s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.02106642723083496s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 5.459785461425781e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.430511474609375e-06s
Believability | Calculation of trust value for AragoDBPedia took 4.76837158203125e-06s
INFO | --- Analysis for aragodbpedia took 13904.963364839554s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.18926763534546s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0006775856018066406s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.2891204357147217s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.02077794075012207s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.078315734863281e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for archiveshub-linkeddata took 83.6747694015503s
Availability | SPARQL endpoint availability check for Archivi ISMA took 4.315376281738281e-05s
Availability | VoID file availability check for Archivi ISMA took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.2736632823944092s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.020374774932861328s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 3.337860107421875e-05s
Believability | Calculation of trust value for Archivi ISMA took 7.152557373046875e-06s
INFO | --- Analysis for archivio-isma took 3.4010801315307617s
Availability | SPARQL endpoint availability check for ARIADNE took 6.961822509765625e-05s
Availability | VoID file availability check for ARIADNE took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.24954891204833984s
Reputation | Calculation of the PageRank for ARIADNE took 0.020485639572143555s
Interlinking | Calculation of Degree of Connection for ARIADNE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ARIADNE took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 3.0994415283203125e-05s
Believability | Calculation of trust value for ARIADNE took 7.152557373046875e-06s
INFO | --- Analysis for ariadne took 2.9777891635894775s
Availability | SPARQL endpoint availability check for Aristotle University took 4.3392181396484375e-05s
Availability | VoID file availability check for Aristotle University took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.7579760551452637s
Reputation | Calculation of the PageRank for Aristotle University took 0.020496129989624023s
Interlinking | Calculation of Degree of Connection for Aristotle University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Aristotle University took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 3.0994415283203125e-05s
Believability | Calculation of trust value for Aristotle University took 7.3909759521484375e-06s
INFO | --- Analysis for aristotle-university took 4.750658988952637s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 4.911155462265015s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.279829740524292s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.019850730895996094s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 2.8371810913085938e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 6.9141387939453125e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 19.892996072769165s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 5.2928924560546875e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.2500185966491699s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.020142793655395508s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0007238388061523438s
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 6.67572021484375e-06s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 3.353583812713623s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.907682418823242s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0006945133209228516s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.270277738571167s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.02037501335144043s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.790855407714844e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 7.62939453125e-06s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 17.01741909980774s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.3392181396484375e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0003631114959716797s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.25123095512390137s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.02100229263305664s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00010776519775390625s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 7.62939453125e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 10.27314043045044s
Availability | SPARQL endpoint availability check for Arthroscopy community took 5.602836608886719e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0005433559417724609s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.28440141677856445s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.020733118057250977s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0008509159088134766s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00011205673217773438s
Believability | Calculation of trust value for Arthroscopy community took 1.239776611328125e-05s
INFO | --- Analysis for arthroscopy took 13.613211870193481s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.744529724121094e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0003256797790527344s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.2627699375152588s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.02038741111755371s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.842613220214844e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 7.867813110351562e-06s
INFO | --- Analysis for asit took 7.592392206192017s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.410743713378906e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0003428459167480469s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.2707197666168213s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.020211219787597656s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 3.647804260253906e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 7.62939453125e-06s
INFO | --- Analysis for asjp took 4.675045967102051s
Availability | SPARQL endpoint availability check for ASN:US took 2.2151670455932617s
Availability | VoID file availability check for ASN:US took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for ASN:US took 0.2735707759857178s
Reputation | Calculation of the PageRank for ASN:US took 0.025109529495239258s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0011630058288574219s
Interlinking | Calculation of Clustering coefficient for ASN:US took 8.392333984375e-05s
Believability | Calculation of trust value for ASN:US took 5.4836273193359375e-06s
INFO | --- Analysis for asn-us took 12.23858118057251s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.315376281738281e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.24383974075317383s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.020461559295654297s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.409385681152344e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 5.9604644775390625e-06s
INFO | --- Analysis for aspire-mmu took 4.4062581062316895s
Availability | SPARQL endpoint availability check for associations took 4.315376281738281e-05s
Availability | VoID file availability check for associations took 0.0006690025329589844s
Completeness | Calculation of interlinking completeness for associations took 0.2621638774871826s
Reputation | Calculation of the PageRank for associations took 0.02038884162902832s
Interlinking | Calculation of Degree of Connection for associations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for associations took 0.00086212158203125s
Interlinking | Calculation of Clustering coefficient for associations took 6.794929504394531e-05s
Believability | Calculation of trust value for associations took 7.3909759521484375e-06s
INFO | --- Analysis for associations took 7.59153151512146s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 4.2438507080078125e-05s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.25818347930908203s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.020101308822631836s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 3.0040740966796875e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 7.3909759521484375e-06s
INFO | --- Analysis for atc-publikovan--s-kl took 2.9164655208587646s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 8.702278137207031e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.24828338623046875s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.02024984359741211s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 0.00011181831359863281s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 6.9141387939453125e-06s
INFO | --- Analysis for athelia-rfid took 5.173419952392578s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 4.267692565917969e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.2677292823791504s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.020440340042114258s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 2.9325485229492188e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for aueb-linked-open-data took 2.9392054080963135s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.6106688976287842s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.2632791996002197s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.020142078399658203s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 8.893013000488281e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 5.9604644775390625e-06s
INFO | --- Analysis for austrian_ski_racers took 3.8296358585357666s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.30710363388061523s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0005633831024169922s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 169.3589324951172s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.49944519996643066s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0326602458954s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 190.75739765167236s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.07391381263733s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0601544380188s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2606229782104492s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14525794982910156s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1438288688659668s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11682295799255371s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 50.03460168838501s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.01200580596924s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13248991966247559s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 206.35953187942505s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.3691232204437256s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09458708763122559s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11688065528869629s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10852503776550293s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.516496658325195s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.390975952148438e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10991096496582031s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0912055969238s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13873004913330078s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16389870643615723s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12584400177001953s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24378156661987305s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24715399742126465s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 398.0323314666748s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12746739387512207s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 11.469438791275024s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.237239122390747s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.819782018661499s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14157533645629883s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.15256810188293s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 146.90350818634033s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.39485239982605s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.49865555763245s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.816344976425171s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2010176181793213s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.101198434829712s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.6218595504760742s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.02088189125061035s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007321834564208984s
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.430511474609375e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 5.9604644775390625e-06s
INFO | --- Analysis for b3kat took 3931.61221575737s
Availability | SPARQL endpoint availability check for BabelNet took 0.5794451236724854s
Availability | VoID file availability check for BabelNet took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for BabelNet took 0.2732410430908203s
Reputation | Calculation of the PageRank for BabelNet took 0.020650148391723633s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.00016307830810546875s
Believability | Calculation of trust value for BabelNet took 7.3909759521484375e-06s
INFO | --- Analysis for babelnet took 5.947800874710083s
Availability | SPARQL endpoint availability check for BAMS took 4.220008850097656e-05s
Availability | VoID file availability check for BAMS took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for BAMS took 0.2804238796234131s
Reputation | Calculation of the PageRank for BAMS took 0.020464658737182617s
Interlinking | Calculation of Degree of Connection for BAMS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for BAMS took 3.24249267578125e-05s
Believability | Calculation of trust value for BAMS took 8.106231689453125e-06s
INFO | --- Analysis for bams took 2.948394536972046s
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.0006494522094726562s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.2717404365539551s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.020355224609375s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 7.62939453125e-06s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 3.414994955062866s
Availability | SPARQL endpoint availability check for BBC Music took 0.30884265899658203s
Availability | VoID file availability check for BBC Music took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for BBC Music took 0.7300822734832764s
Reputation | Calculation of the PageRank for BBC Music took 0.020071983337402344s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00013446807861328125s
Believability | Calculation of trust value for BBC Music took 7.3909759521484375e-06s
INFO | --- Analysis for bbc-music took 3.809032678604126s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.2708747386932373s
Availability | VoID file availability check for BBC Programmes took 0.0006988048553466797s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.2672727108001709s
Reputation | Calculation of the PageRank for BBC Programmes took 0.019976139068603516s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010037422180175781s
Believability | Calculation of trust value for BBC Programmes took 7.3909759521484375e-06s
INFO | --- Analysis for bbc-programmes took 10.693920850753784s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.22922396659851074s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0007445812225341797s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.2908918857574463s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.02005314826965332s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010061264038085938s
Believability | Calculation of trust value for BBC Wildlife Finder took 8.106231689453125e-06s
INFO | --- Analysis for bbc-wildlife-finder took 9.768141746520996s
Availability | SPARQL endpoint availability check for BBOP took 4.220008850097656e-05s
Availability | VoID file availability check for BBOP took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for BBOP took 0.2848789691925049s
Reputation | Calculation of the PageRank for BBOP took 0.020215272903442383s
Interlinking | Calculation of Degree of Connection for BBOP took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for BBOP took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for BBOP took 2.8848648071289062e-05s
Believability | Calculation of trust value for BBOP took 7.3909759521484375e-06s
INFO | --- Analysis for bbop took 2.989372491836548s
Availability | SPARQL endpoint availability check for BBOP took 0.00010251998901367188s
Availability | VoID file availability check for BBOP took 0.0007960796356201172s
Completeness | Calculation of interlinking completeness for BBOP took 0.27214932441711426s
Reputation | Calculation of the PageRank for BBOP took 0.020087003707885742s
Interlinking | Calculation of Degree of Connection for BBOP took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.0040740966796875e-05s
Believability | Calculation of trust value for BBOP took 7.152557373046875e-06s
INFO | --- Analysis for bbop-selected took 20.46788215637207s
Availability | SPARQL endpoint availability check for Bdgp took 1.8747012615203857s
Availability | VoID file availability check for Bdgp took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for Bdgp took 0.25757670402526855s
Reputation | Calculation of the PageRank for Bdgp took 0.02036905288696289s
Interlinking | Calculation of Degree of Connection for Bdgp took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bdgp took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.62396240234375e-05s
Believability | Calculation of trust value for Bdgp took 7.867813110351562e-06s
INFO | --- Analysis for bdgp took 8.613063097000122s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 0.14365363121032715s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.28699254989624023s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.020164966583251953s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.914138793945312e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 6.198883056640625e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 2.727266311645508s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 4.2438507080078125e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.29326367378234863s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.020270586013793945s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 3.123283386230469e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 8.344650268554688e-06s
INFO | --- Analysis for berlin-offener-haushalt took 2.922750949859619s
Availability | SPARQL endpoint availability check for berlios took 4.315376281738281e-05s
Availability | VoID file availability check for berlios took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for berlios took 0.2477264404296875s
Reputation | Calculation of the PageRank for berlios took 0.02014780044555664s
Interlinking | Calculation of Degree of Connection for berlios took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for berlios took 9.250640869140625e-05s
Believability | Calculation of trust value for berlios took 6.4373016357421875e-06s
INFO | --- Analysis for berlios took 2.919517993927002s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.5150322914123535s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.29130029678344727s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.020228147506713867s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 8.821487426757812e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for bfs-linked-data took 3.0128655433654785s
Availability | SPARQL endpoint availability check for BibBase took 0.05910682678222656s
Availability | VoID file availability check for BibBase took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for BibBase took 0.2787182331085205s
Reputation | Calculation of the PageRank for BibBase took 0.020251750946044922s
Interlinking | Calculation of Degree of Connection for BibBase took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BibBase took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.441375732421875e-05s
Believability | Calculation of trust value for BibBase took 6.9141387939453125e-06s
INFO | --- Analysis for bibbase took 2.533216953277588s
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.0006701946258544922s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.27130556106567383s
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.5367431640625e-06s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.00010061264038085938s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 7.3909759521484375e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 7.539139747619629s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 5.5789947509765625e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.2687695026397705s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.02037835121154785s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 9.584426879882812e-05s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 7.62939453125e-06s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 9.101901054382324s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 4.076957702636719e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.2668492794036865s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.020204544067382812s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.3855438232421875e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 6.9141387939453125e-06s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 2.9648289680480957s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 4.220008850097656e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.24372172355651855s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.020525217056274414s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 2.956390380859375e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 7.867813110351562e-06s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 4.8799474239349365s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 4.291534423828125e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.27185726165771484s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.020242929458618164s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 2.9325485229492188e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 7.62939453125e-06s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.640011787414551s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 4.839897155761719e-05s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.26294589042663574s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.020174264907836914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 2.8371810913085938e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-acfsid took 2.933912515640259s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 1.2881672382354736s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0006799697875976562s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 20.22527527809143s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.518890380859375s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 44.2001519203186s
Interoperability | New terms check for Bio2RDF::Affymetrix took 41.34645891189575s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.13224196434021s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.14189934730529785s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.8766193389892578s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.1934511661529541s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 0.1833937168121338s
License | MR license check for Bio2RDF::Affymetrix took 0.41528940200805664s
License | HR license check for Bio2RDF::Affymetrix took 60.09904909133911s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.1370530128479004s
Understandability | Number of label check for Bio2RDF::Affymetrix took 9.665098428726196s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.3636159896850586s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.14120960235595703s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.13822340965270996s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.13783860206604004s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.781127452850342s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 71.64865207672119s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.29450273513793945s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.2250678539276123s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.7944540977478027s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.18820929527282715s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.1088254451751709s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.2699010372161865s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.2321939468383789s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 108.60527014732361s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 10.831416130065918s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.3029041290283203s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.1464078426361084s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.12880229949951172s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 7.267688989639282s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.9079480171203613s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6870391368865967s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.5942423343658447s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 64.83250117301941s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.2908198833465576s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.059776306152344s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.2838096618652344s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.38742804527283s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.7020320892333984s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.29931068420410156s
Security | Sign check for Bio2RDF::Affymetrix took 0.13559937477111816s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 11.692249774932861s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.8174715042114258s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.021445274353027344s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.00010085105895996094s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 13.396080255508423s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-affymetrix took 1013.809700012207s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.48810482025146484s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0005810260772705078s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 18.98979926109314s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.2559678554534912s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 44.87828731536865s
Interoperability | New terms check for Bio2RDF::Biomodels took 40.87655019760132s
Versatility | Languages check for Bio2RDF::Biomodels took 60.26025581359863s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.2721395492553711s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.18960046768188477s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.5574569702148438s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.3304443359375s
Availability | RDF dump link check for Bio2RDF::Biomodels took 0.3224203586578369s
License | MR license check for Bio2RDF::Biomodels took 0.5784673690795898s
License | HR license check for Bio2RDF::Biomodels took 60.26612377166748s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.27926039695739746s
Understandability | Number of label check for Bio2RDF::Biomodels took 9.461947679519653s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5851821899414062s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.26751232147216797s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.26909780502319336s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.2597079277038574s
Performance | Throughput check for Bio2RDF::Biomodels took 11.452471256256104s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 76.51541638374329s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 0.5538580417633057s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.36660170555114746s
Interlinking | skos check for Bio2RDF::Biomodels took 0.8267679214477539s
Interlinking | skos check for Bio2RDF::Biomodels took 0.4036703109741211s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.2617068290710449s
Currency | Creation date check for Bio2RDF::Biomodels took 0.531055212020874s
Currency | Modification date check for Bio2RDF::Biomodels took 0.5262820720672607s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 107.06895899772644s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 15.009822845458984s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.39676594734191895s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.24852991104125977s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.2714674472808838s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 7.2010393142700195s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.9122586250305176s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6656591892242432s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.4469454288482666s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.14867329597473s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.3814384937286377s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 5.776960134506226s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.2976746559143066s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.56599736213684s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.7039446830749512s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.4602515697479248s
Security | Sign check for Bio2RDF::Biomodels took 0.2694685459136963s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 11.385568141937256s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 1.4054226875305176s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.0206606388092041s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0008139610290527344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00012946128845214844s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 35.025505781173706s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-biomodels took 1051.499397277832s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.29442930221557617s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.02065587043762207s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 4.450455188751221s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.46277451515197754s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0005619525909423828s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 18.8194522857666s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.2470927238464355s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 43.43271994590759s
Interoperability | New terms check for Bio2RDF::Bioportal took 40.430826902389526s
Versatility | Languages check for Bio2RDF::Bioportal took 60.254244804382324s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.2538950443267822s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.1546921730041504s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.6085958480834961s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.3093125820159912s
Availability | RDF dump link check for Bio2RDF::Bioportal took 0.30429625511169434s
License | MR license check for Bio2RDF::Bioportal took 0.4863767623901367s
License | HR license check for Bio2RDF::Bioportal took 60.24365210533142s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.25359225273132324s
Understandability | Number of label check for Bio2RDF::Bioportal took 9.635303497314453s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.5617485046386719s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.24603009223937988s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.2596931457519531s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.26566052436828613s
Performance | Throughput check for Bio2RDF::Bioportal took 11.29223918914795s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 75.88485479354858s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.5938136577606201s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.2744104862213135s
Interlinking | skos check for Bio2RDF::Bioportal took 0.7304327487945557s
Interlinking | skos check for Bio2RDF::Bioportal took 0.39557456970214844s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.26006484031677246s
Currency | Creation date check for Bio2RDF::Bioportal took 0.5189595222473145s
Currency | Modification date check for Bio2RDF::Bioportal took 0.5146181583404541s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 107.78082847595215s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 74.38814330101013s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.4419095516204834s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.26419997215270996s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.27648353576660156s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 7.304184913635254s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.9103994369506836s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6629433631896973s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.2811429500579834s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 64.83208107948303s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.4024596214294434s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.34371542930603s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.2982971668243408s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.581071853637695s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7205357551574707s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.7089269161224365s
Security | Sign check for Bio2RDF::Bioportal took 0.27649712562561035s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 11.668722152709961s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.856950044631958s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.02090287208557129s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004181861877441406s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 69.04196095466614s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-bioportal took 1149.9860796928406s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.1383957862854004s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.29604029655456543s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.02001357078552246s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.245208740234375e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-chembl took 16.90295910835266s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.47328615188598633s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0006535053253173828s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 20.597551107406616s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.271019458770752s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 44.75075340270996s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 42.69253969192505s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.25653624534607s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.2607998847961426s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.15199542045593262s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.3282747268676758s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.3118398189544678s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 0.2839527130126953s
License | MR license check for Bio2RDF::Clinicaltrials took 0.4632840156555176s
License | HR license check for Bio2RDF::Clinicaltrials took 60.23108124732971s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.3006014823913574s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 9.538188695907593s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.5682127475738525s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.24665331840515137s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.2692880630493164s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.24601411819458008s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 11.264564514160156s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 71.69135570526123s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.5895848274230957s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.26746559143066406s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 1.0050303936004639s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.3780100345611572s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.24256110191345215s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.532224178314209s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.4894223213195801s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 107.64185881614685s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 51.84637475013733s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.44837260246276855s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.23391127586364746s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.2644779682159424s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 6.664143800735474s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.8939404487609863s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.7092752456665039s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.37113332748413086s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 65.28074669837952s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.4465529918670654s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 6.901920318603516s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.3509609699249268s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.59651017189026s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.7124817371368408s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.5939867496490479s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.26967883110046387s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 11.196135997772217s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.9113547801971436s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.020211458206176758s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 4.887580871582031e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 64.94601249694824s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1129.1613912582397s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.48859453201293945s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0005633831024169922s
Extra | Recovery of all triples for Bio2RDF::Ctd took 19.91076374053955s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.2149066925048828s
Amount of data | Number of triples check for Bio2RDF::Ctd took 44.283941984176636s
Interoperability | New terms check for Bio2RDF::Ctd took 41.39572286605835s
Versatility | Languages check for Bio2RDF::Ctd took 60.23776364326477s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.27107787132263184s
Security | Check HTTPS for Bio2RDF::Ctd took 0.1567835807800293s
Interpretability | RDF structures check for Bio2RDF::Ctd took 1.029829740524292s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.3878777027130127s
Availability | RDF dump link check for Bio2RDF::Ctd took 0.32888245582580566s
License | MR license check for Bio2RDF::Ctd took 0.4439704418182373s
License | HR license check for Bio2RDF::Ctd took 60.2547070980072s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.2527453899383545s
Understandability | Number of label check for Bio2RDF::Ctd took 10.114745378494263s
Understandability | URI regex check for Bio2RDF::Ctd took 0.5999970436096191s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.2578704357147217s
Verifiability | Authors check for Bio2RDF::Ctd took 0.2727174758911133s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.26065969467163086s
Performance | Throughput check for Bio2RDF::Ctd took 11.664833784103394s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 76.20041394233704s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.6146321296691895s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.4914436340332031s
Interlinking | skos check for Bio2RDF::Ctd took 1.3690862655639648s
Interlinking | skos check for Bio2RDF::Ctd took 0.34146714210510254s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.28917551040649414s
Currency | Creation date check for Bio2RDF::Ctd took 0.5371997356414795s
Currency | Modification date check for Bio2RDF::Ctd took 0.5453343391418457s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 111.54670906066895s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 74.3807783126831s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.43212151527404785s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.26514172554016113s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.2762258052825928s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 7.190110445022583s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.9156427383422852s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6653656959533691s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.5522215366363525s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.19518399238586s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.429128646850586s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.972530126571655s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.3425657749176025s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.577747106552124s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.7031769752502441s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.6540749073028564s
Security | Sign check for Bio2RDF::Ctd took 0.27558159828186035s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 11.678185224533081s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.43058061599731445s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.020658493041992188s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.699562072753906e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 71.66235423088074s
Believability | Calculation of trust value for Bio2RDF::Ctd took 9.298324584960938e-06s
INFO | --- Analysis for bio2rdf-ctd took 1168.9402704238892s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.410743713378906e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0006628036499023438s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.2809314727783203s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 4.9114227294921875e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-dataset took 4.4495861530303955s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.47136592864990234s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0005593299865722656s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 19.079195499420166s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.2101633548736572s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 45.12647032737732s
Interoperability | New terms check for Bio2RDF::Dbsnp took 41.80476999282837s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.24658274650574s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.28349876403808594s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.1680591106414795s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.6509435176849365s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.35976147651672363s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 0.29080843925476074s
License | MR license check for Bio2RDF::Dbsnp took 0.47136592864990234s
License | HR license check for Bio2RDF::Dbsnp took 60.25885534286499s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.289578914642334s
Understandability | Number of label check for Bio2RDF::Dbsnp took 9.695697784423828s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.5881640911102295s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.2669546604156494s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.3119988441467285s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.24954652786254883s
Performance | Throughput check for Bio2RDF::Dbsnp took 11.68549394607544s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 74.71385025978088s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.5564019680023193s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.4054546356201172s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.8892898559570312s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.3483431339263916s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.2748544216156006s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.5074939727783203s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.5130012035369873s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 107.82534885406494s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 62.36133861541748s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.4517338275909424s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.28681135177612305s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.26407933235168457s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 7.084484338760376s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.8960933685302734s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6724061965942383s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.38529276847839355s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 65.38829255104065s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.3956046104431152s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.469146490097046s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.3253746032714844s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.52665138244629s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.6972134113311768s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 1.3699977397918701s
Security | Sign check for Bio2RDF::Dbsnp took 0.27069997787475586s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 11.390525579452515s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 1.3522863388061523s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.020694732666015625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 7.557868957519531e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 70.4691789150238s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 1138.997350692749s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.48265981674194336s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0006439685821533203s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 18.743694305419922s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.2436375617980957s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 44.430636167526245s
Interoperability | New terms check for Bio2RDF::Drugbank took 39.88454031944275s
Versatility | Languages check for Bio2RDF::Drugbank took 60.275458097457886s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.274538516998291s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.14505696296691895s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.8082184791564941s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.3155386447906494s
Availability | RDF dump link check for Bio2RDF::Drugbank took 0.30519556999206543s
License | MR license check for Bio2RDF::Drugbank took 0.49162745475769043s
License | HR license check for Bio2RDF::Drugbank took 60.251094579696655s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.27422332763671875s
Understandability | Number of label check for Bio2RDF::Drugbank took 9.359600305557251s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.5927944183349609s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.25606656074523926s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.27162718772888184s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.2525796890258789s
Performance | Throughput check for Bio2RDF::Drugbank took 11.033832550048828s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 75.82096672058105s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.5776114463806152s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.26815366744995117s
Interlinking | skos check for Bio2RDF::Drugbank took 0.7445826530456543s
Interlinking | skos check for Bio2RDF::Drugbank took 0.347609281539917s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.25693655014038086s
Currency | Creation date check for Bio2RDF::Drugbank took 0.5020046234130859s
Currency | Modification date check for Bio2RDF::Drugbank took 0.510793924331665s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 109.98789596557617s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 72.81087183952332s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.41394662857055664s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.2774074077606201s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.2548067569732666s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 6.993139266967773s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.9028451442718506s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.6690161228179932s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.4062225818634033s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 65.69386887550354s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.4290506839752197s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 6.080426931381226s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.2984402179718018s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.570366859436035s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.7005984783172607s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.579470157623291s
Security | Sign check for Bio2RDF::Drugbank took 0.2686769962310791s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 11.549951076507568s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 1.3838741779327393s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020314693450927734s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 9.870529174804688e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 17.80404806137085s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-drugbank took 1092.6655185222626s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.475830078125s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0006644725799560547s
Extra | Recovery of all triples for Bio2RDF::Genage took 18.368990898132324s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.2215547561645508s
Amount of data | Number of triples check for Bio2RDF::Genage took 43.86531186103821s
Interoperability | New terms check for Bio2RDF::Genage took 39.76435828208923s
Versatility | Languages check for Bio2RDF::Genage took 60.24841809272766s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.25559234619140625s
Security | Check HTTPS for Bio2RDF::Genage took 0.1586904525756836s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.6008450984954834s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.3196983337402344s
Availability | RDF dump link check for Bio2RDF::Genage took 0.2803328037261963s
License | MR license check for Bio2RDF::Genage took 0.746485710144043s
License | HR license check for Bio2RDF::Genage took 60.244901180267334s
Amount of data | Number of property check for Bio2RDF::Genage took 0.257826566696167s
Understandability | Number of label check for Bio2RDF::Genage took 9.359242677688599s
Understandability | URI regex check for Bio2RDF::Genage took 0.5488898754119873s
Understandability | Vocabs check for Bio2RDF::Genage took 0.26679325103759766s
Verifiability | Authors check for Bio2RDF::Genage took 0.25685548782348633s
Verifiability | Publishers check for Bio2RDF::Genage took 0.2514355182647705s
Performance | Throughput check for Bio2RDF::Genage took 11.225014448165894s
Amount of data | Check the number of entities for Bio2RDF::Genage took 76.0910222530365s
Verifiability | Contribs. check for Bio2RDF::Genage took 2.03320050239563s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.357790470123291s
Interlinking | skos check for Bio2RDF::Genage took 0.6774773597717285s
Interlinking | skos check for Bio2RDF::Genage took 0.3681826591491699s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.28714895248413086s
Currency | Creation date check for Bio2RDF::Genage took 0.5131187438964844s
Currency | Modification date check for Bio2RDF::Genage took 0.5235540866851807s
Rep.Conc. | URIs length for Bio2RDF::Genage took 107.51080751419067s
Interoperability | New vocabularies check for Bio2RDF::Genage took 68.26947927474976s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.4562196731567383s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.2903938293457031s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.29742431640625s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 7.245755195617676s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.9018573760986328s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6952073574066162s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.4803595542907715s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 65.5730607509613s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.3981456756591797s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.415832281112671s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.2984998226165771s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.566612005233765s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7084803581237793s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.5830011367797852s
Security | Sign check for Bio2RDF::Genage took 0.27018022537231445s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 11.507258653640747s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.5719542503356934s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.02051544189453125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 5.745887756347656e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 73.25226712226868s
Believability | Calculation of trust value for Bio2RDF::Genage took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-genage took 1144.3436243534088s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.00031185150146484375s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.6916792392730713s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.020389318466186523s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0009086132049560547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 6.4849853515625e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-genbank took 3.8411147594451904s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.46996307373046875s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0003464221954345703s
Extra | Recovery of all triples for Bio2RDF::Gendr took 19.83988618850708s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.2977402210235596s
Amount of data | Number of triples check for Bio2RDF::Gendr took 59.37527060508728s
Interoperability | New terms check for Bio2RDF::Gendr took 41.17413926124573s
Versatility | Languages check for Bio2RDF::Gendr took 60.242722272872925s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.26236629486083984s
Security | Check HTTPS for Bio2RDF::Gendr took 0.1606731414794922s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.7966189384460449s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.3778867721557617s
Availability | RDF dump link check for Bio2RDF::Gendr took 0.2978239059448242s
License | MR license check for Bio2RDF::Gendr took 0.5480082035064697s
License | HR license check for Bio2RDF::Gendr took 60.25966262817383s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.3033301830291748s
Understandability | Number of label check for Bio2RDF::Gendr took 10.744319200515747s
Understandability | URI regex check for Bio2RDF::Gendr took 0.5830240249633789s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.2695329189300537s
Verifiability | Authors check for Bio2RDF::Gendr took 0.35950303077697754s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.24231529235839844s
Performance | Throughput check for Bio2RDF::Gendr took 11.002711296081543s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 74.81983661651611s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.5676300525665283s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.40016961097717285s
Interlinking | skos check for Bio2RDF::Gendr took 1.1663463115692139s
Interlinking | skos check for Bio2RDF::Gendr took 0.6226596832275391s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.2543215751647949s
Currency | Creation date check for Bio2RDF::Gendr took 0.5375041961669922s
Currency | Modification date check for Bio2RDF::Gendr took 0.5323271751403809s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 114.15052032470703s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 69.96031665802002s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.4437124729156494s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.2704439163208008s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.27767014503479004s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 7.129872798919678s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.8914813995361328s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6542356014251709s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.3924562931060791s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 65.93382358551025s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.4005000591278076s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.367645263671875s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.3313136100769043s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.56299543380737s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.7063665390014648s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.6267247200012207s
Security | Sign check for Bio2RDF::Gendr took 0.268247127532959s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 11.57423186302185s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.3634970188140869s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.020620107650756836s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.53131103515625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 64.25702476501465s
Believability | Calculation of trust value for Bio2RDF::Gendr took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-gendr took 1177.9320614337921s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.46169090270996094s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0006310939788818359s
Extra | Recovery of all triples for Bio2RDF::Goa took 22.617332935333252s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.2320315837860107s
Amount of data | Number of triples check for Bio2RDF::Goa took 55.463518381118774s
Interoperability | New terms check for Bio2RDF::Goa took 45.14473509788513s
Versatility | Languages check for Bio2RDF::Goa took 60.24684143066406s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.27486538887023926s
Security | Check HTTPS for Bio2RDF::Goa took 0.1563405990600586s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.40065813064575195s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.46030712127685547s
Availability | RDF dump link check for Bio2RDF::Goa took 0.30739498138427734s
License | MR license check for Bio2RDF::Goa took 0.5799429416656494s
License | HR license check for Bio2RDF::Goa took 60.24686002731323s
Amount of data | Number of property check for Bio2RDF::Goa took 0.265810489654541s
Understandability | Number of label check for Bio2RDF::Goa took 10.337098360061646s
Understandability | URI regex check for Bio2RDF::Goa took 0.5898263454437256s
Understandability | Vocabs check for Bio2RDF::Goa took 0.28232669830322266s
Verifiability | Authors check for Bio2RDF::Goa took 0.31444597244262695s
Verifiability | Publishers check for Bio2RDF::Goa took 0.2695882320404053s
Performance | Throughput check for Bio2RDF::Goa took 11.441969633102417s
Amount of data | Check the number of entities for Bio2RDF::Goa took 72.40872311592102s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.7463533878326416s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.42559027671813965s
Interlinking | skos check for Bio2RDF::Goa took 0.8949172496795654s
Interlinking | skos check for Bio2RDF::Goa took 0.3394641876220703s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.2510519027709961s
Currency | Creation date check for Bio2RDF::Goa took 0.5021367073059082s
Currency | Modification date check for Bio2RDF::Goa took 0.48094606399536133s
Rep.Conc. | URIs length for Bio2RDF::Goa took 110.93092608451843s
Interoperability | New vocabularies check for Bio2RDF::Goa took 56.30567693710327s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.4447059631347656s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.29780030250549316s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.28270840644836426s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 8.122090816497803s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.9072959423065186s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6558830738067627s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.4832019805908203s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 65.5544822216034s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.434335947036743s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 7.445721626281738s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.3564229011535645s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.607436418533325s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.7049355506896973s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.5975935459136963s
Security | Sign check for Bio2RDF::Goa took 0.27541637420654297s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 11.195901155471802s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 1.402482509613037s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.020256757736206055s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.437301635742188e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 56.60228133201599s
Believability | Calculation of trust value for Bio2RDF::Goa took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-goa took 1161.899057149887s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.4495115280151367s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0008301734924316406s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 20.55478572845459s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.2443101406097412s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 44.41927218437195s
Interoperability | New terms check for Bio2RDF::Hgnc took 43.18166708946228s
Versatility | Languages check for Bio2RDF::Hgnc took 60.24480128288269s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.2781345844268799s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.15899324417114258s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.4500601291656494s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.34873390197753906s
Availability | RDF dump link check for Bio2RDF::Hgnc took 0.28783512115478516s
License | MR license check for Bio2RDF::Hgnc took 0.4629504680633545s
License | HR license check for Bio2RDF::Hgnc took 60.268393993377686s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.27891087532043457s
Understandability | Number of label check for Bio2RDF::Hgnc took 9.967490196228027s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.618391752243042s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.2773399353027344s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.33919262886047363s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.2711465358734131s
Performance | Throughput check for Bio2RDF::Hgnc took 11.041776657104492s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 74.5279586315155s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.574012279510498s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.3677377700805664s
Interlinking | skos check for Bio2RDF::Hgnc took 0.8013391494750977s
Interlinking | skos check for Bio2RDF::Hgnc took 0.3515937328338623s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.27657532691955566s
Currency | Creation date check for Bio2RDF::Hgnc took 0.5420188903808594s
Currency | Modification date check for Bio2RDF::Hgnc took 0.5171329975128174s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 112.26937556266785s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 55.28020143508911s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.4220118522644043s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.28543663024902344s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.29564881324768066s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 7.4704906940460205s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.9031116962432861s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6705031394958496s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.4377171993255615s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.14160203933716s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.4212398529052734s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 7.488916635513306s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.3063421249389648s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.60949444770813s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7229759693145752s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 1.4021048545837402s
Security | Sign check for Bio2RDF::Hgnc took 0.26354146003723145s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 11.533907413482666s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.3664977550506592s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.020464181900024414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00011777877807617188s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 61.74439311027527s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-hgnc took 1127.971847295761s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 1.2693688869476318s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0005974769592285156s
Extra | Recovery of all triples for Bio2RDF::Homologene took 19.757601261138916s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.2667605876922607s
Amount of data | Number of triples check for Bio2RDF::Homologene took 43.418272733688354s
Interoperability | New terms check for Bio2RDF::Homologene took 41.92149829864502s
Versatility | Languages check for Bio2RDF::Homologene took 60.2523455619812s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.29224371910095215s
Security | Check HTTPS for Bio2RDF::Homologene took 0.15570592880249023s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.6969428062438965s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.351381778717041s
Availability | RDF dump link check for Bio2RDF::Homologene took 0.3130519390106201s
License | MR license check for Bio2RDF::Homologene took 0.5628645420074463s
License | HR license check for Bio2RDF::Homologene took 60.25279688835144s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.2678389549255371s
Understandability | Number of label check for Bio2RDF::Homologene took 10.634337663650513s
Understandability | URI regex check for Bio2RDF::Homologene took 0.5606896877288818s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.24203252792358398s
Verifiability | Authors check for Bio2RDF::Homologene took 0.27454423904418945s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.25748753547668457s
Performance | Throughput check for Bio2RDF::Homologene took 10.600529432296753s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 74.1382188796997s
Verifiability | Contribs. check for Bio2RDF::Homologene took 2.03444504737854s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.36533522605895996s
Interlinking | skos check for Bio2RDF::Homologene took 0.7763388156890869s
Interlinking | skos check for Bio2RDF::Homologene took 0.3835780620574951s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.26628923416137695s
Currency | Creation date check for Bio2RDF::Homologene took 0.5134789943695068s
Currency | Modification date check for Bio2RDF::Homologene took 0.5294308662414551s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 111.83708214759827s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 54.17867064476013s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.4237556457519531s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.27579808235168457s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.2689659595489502s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 7.9565589427948s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8993215560913086s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6624269485473633s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.4509909152984619s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.23436212539673s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.367277145385742s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.867209434509277s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.3114798069000244s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.53959822654724s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7050421237945557s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.5229663848876953s
Security | Sign check for Bio2RDF::Homologene took 0.26526927947998047s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 10.644583702087402s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.5381662845611572s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.02105569839477539s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 6.079673767089844e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 57.79080152511597s
Believability | Calculation of trust value for Bio2RDF::Homologene took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-homologene took 1121.6604821681976s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 4.291534423828125e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.26890110969543457s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.020787477493286133s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 3.337860107421875e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-inoh took 4.3031299114227295s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.4888138771057129s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0005776882171630859s
Extra | Recovery of all triples for Bio2RDF::Interpro took 19.791901350021362s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.3015830516815186s
Amount of data | Number of triples check for Bio2RDF::Interpro took 45.98867917060852s
Interoperability | New terms check for Bio2RDF::Interpro took 42.69926738739014s
Versatility | Languages check for Bio2RDF::Interpro took 60.24219369888306s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.2619504928588867s
Security | Check HTTPS for Bio2RDF::Interpro took 0.14269614219665527s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.8959424495697021s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.3506491184234619s
Availability | RDF dump link check for Bio2RDF::Interpro took 0.2980611324310303s
License | MR license check for Bio2RDF::Interpro took 0.4338867664337158s
License | HR license check for Bio2RDF::Interpro took 60.25055766105652s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.2644846439361572s
Understandability | Number of label check for Bio2RDF::Interpro took 10.375800132751465s
Understandability | URI regex check for Bio2RDF::Interpro took 0.5955779552459717s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.2808821201324463s
Verifiability | Authors check for Bio2RDF::Interpro took 0.35242557525634766s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.2622811794281006s
Performance | Throughput check for Bio2RDF::Interpro took 11.550573587417603s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 77.4189784526825s
Verifiability | Contribs. check for Bio2RDF::Interpro took 2.04142427444458s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.3891935348510742s
Interlinking | skos check for Bio2RDF::Interpro took 0.818321943283081s
Interlinking | skos check for Bio2RDF::Interpro took 0.3937253952026367s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.27353930473327637s
Currency | Creation date check for Bio2RDF::Interpro took 0.5178635120391846s
Currency | Modification date check for Bio2RDF::Interpro took 0.5278229713439941s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 110.80239343643188s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 55.68559765815735s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.45751309394836426s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.27886176109313965s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.2822587490081787s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 7.347509384155273s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.9035725593566895s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6613118648529053s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.5160048007965088s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.40732383728027s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.4133288860321045s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.435842275619507s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.305473804473877s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.555569648742676s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.7206721305847168s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.5672037601470947s
Security | Sign check for Bio2RDF::Interpro took 0.2834184169769287s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 10.805384635925293s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.8321330547332764s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.02088475227355957s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00010251998901367188s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 59.893723011016846s
Believability | Calculation of trust value for Bio2RDF::Interpro took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-interpro took 1147.2689430713654s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.13913559913635254s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0006234645843505859s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.2698671817779541s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.020514488220214844s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.677078247070312e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-iproclass took 17.08442234992981s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.455704927444458s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.000568389892578125s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 20.502683401107788s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.2360081672668457s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 44.48638558387756s
Interoperability | New terms check for Bio2RDF::Irefindex took 45.13515663146973s
Versatility | Languages check for Bio2RDF::Irefindex took 60.236616373062134s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.2684657573699951s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.1456623077392578s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.5452799797058105s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.3745706081390381s
Availability | RDF dump link check for Bio2RDF::Irefindex took 0.3003065586090088s
License | MR license check for Bio2RDF::Irefindex took 0.47823143005371094s
License | HR license check for Bio2RDF::Irefindex took 60.25656199455261s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.2860097885131836s
Understandability | Number of label check for Bio2RDF::Irefindex took 17.67813467979431s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.6088929176330566s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.27417492866516113s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.3011922836303711s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.270205020904541s
Performance | Throughput check for Bio2RDF::Irefindex took 11.187550783157349s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 77.26048016548157s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.534013032913208s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.3662106990814209s
Interlinking | skos check for Bio2RDF::Irefindex took 0.9581425189971924s
Interlinking | skos check for Bio2RDF::Irefindex took 0.3462200164794922s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.2605295181274414s
Currency | Creation date check for Bio2RDF::Irefindex took 0.4858283996582031s
Currency | Modification date check for Bio2RDF::Irefindex took 0.492328405380249s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 112.68527579307556s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 57.29448461532593s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.4657599925994873s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.2768568992614746s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.26338720321655273s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 7.539945602416992s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.9058127403259277s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6676158905029297s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.5063331127166748s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 65.70471501350403s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.3865182399749756s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.930254697799683s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.3418552875518799s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.58345866203308s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7164871692657471s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.6266512870788574s
Security | Sign check for Bio2RDF::Irefindex took 0.27664780616760254s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 10.735853910446167s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 1.091256856918335s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.020760059356689453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 9.1552734375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 58.594303131103516s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-irefindex took 1153.7999918460846s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 4.291534423828125e-05s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.2600719928741455s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.020299673080444336s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.341934204101562e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-kegg took 2.9453868865966797s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 4.1961669921875e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.0008425712585449219s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.28173089027404785s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.0205690860748291s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 3.24249267578125e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-kegg-biopax took 3.8006138801574707s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.1415412425994873s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.2588686943054199s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020714521408081055s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.314018249511719e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 9.409454345703125s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.46799278259277344s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0006859302520751953s
Extra | Recovery of all triples for Bio2RDF::Lsr took 19.61320662498474s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.2571384906768799s
Amount of data | Number of triples check for Bio2RDF::Lsr took 44.33829116821289s
Interoperability | New terms check for Bio2RDF::Lsr took 47.75468826293945s
Versatility | Languages check for Bio2RDF::Lsr took 60.24686145782471s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.2902357578277588s
Security | Check HTTPS for Bio2RDF::Lsr took 0.1572399139404297s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.850614070892334s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.3771209716796875s
Availability | RDF dump link check for Bio2RDF::Lsr took 0.29445791244506836s
License | MR license check for Bio2RDF::Lsr took 0.5595812797546387s
License | HR license check for Bio2RDF::Lsr took 60.25108551979065s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.2504444122314453s
Understandability | Number of label check for Bio2RDF::Lsr took 10.798229932785034s
Understandability | URI regex check for Bio2RDF::Lsr took 0.5763823986053467s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.24559760093688965s
Verifiability | Authors check for Bio2RDF::Lsr took 0.3296506404876709s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.27378129959106445s
Performance | Throughput check for Bio2RDF::Lsr took 11.271979808807373s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 74.82702422142029s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.5846965312957764s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.3996109962463379s
Interlinking | skos check for Bio2RDF::Lsr took 1.1602425575256348s
Interlinking | skos check for Bio2RDF::Lsr took 0.3483302593231201s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.28713464736938477s
Currency | Creation date check for Bio2RDF::Lsr took 0.5231986045837402s
Currency | Modification date check for Bio2RDF::Lsr took 0.4912097454071045s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 112.58828830718994s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 61.63639974594116s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.4274101257324219s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.2965238094329834s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.29544973373413086s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 8.030269145965576s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.90142822265625s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.663001298904419s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.511399507522583s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 65.35444521903992s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.428276777267456s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 7.398848295211792s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.327547311782837s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.58619165420532s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.711613655090332s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.6149170398712158s
Security | Sign check for Bio2RDF::Lsr took 0.27576422691345215s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 11.054112434387207s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.9021704196929932s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.021077394485473633s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 6.031990051269531e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 56.65449070930481s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-lsr took 1135.428513765335s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.46901988983154297s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0006556510925292969s
Extra | Recovery of all triples for Bio2RDF::Mesh took 21.58367896080017s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.2899348735809326s
Amount of data | Number of triples check for Bio2RDF::Mesh took 45.014439821243286s
Interoperability | New terms check for Bio2RDF::Mesh took 41.3731644153595s
Versatility | Languages check for Bio2RDF::Mesh took 60.25262141227722s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.27532339096069336s
Security | Check HTTPS for Bio2RDF::Mesh took 0.15712213516235352s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.6961231231689453s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.40401315689086914s
Availability | RDF dump link check for Bio2RDF::Mesh took 0.33973002433776855s
License | MR license check for Bio2RDF::Mesh took 0.6420650482177734s
License | HR license check for Bio2RDF::Mesh took 60.2516827583313s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.27277493476867676s
Understandability | Number of label check for Bio2RDF::Mesh took 10.05291748046875s
Understandability | URI regex check for Bio2RDF::Mesh took 0.6339483261108398s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.28405261039733887s
Verifiability | Authors check for Bio2RDF::Mesh took 0.3377561569213867s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.25951504707336426s
Performance | Throughput check for Bio2RDF::Mesh took 11.017857789993286s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 72.18525171279907s
Verifiability | Contribs. check for Bio2RDF::Mesh took 1.100548505783081s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.436373233795166s
Interlinking | skos check for Bio2RDF::Mesh took 1.021118402481079s
Interlinking | skos check for Bio2RDF::Mesh took 0.352677583694458s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.28777074813842773s
Currency | Creation date check for Bio2RDF::Mesh took 0.5083723068237305s
Currency | Modification date check for Bio2RDF::Mesh took 0.5214648246765137s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 115.18726778030396s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 57.16297745704651s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.42830801010131836s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.2790505886077881s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.30338335037231445s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 8.305877685546875s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.907799482345581s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6773257255554199s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.4840695858001709s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 66.7025671005249s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.4614388942718506s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.99942684173584s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.314594030380249s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.573805809020996s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.706876277923584s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.5904345512390137s
Security | Sign check for Bio2RDF::Mesh took 0.2862553596496582s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 11.421283483505249s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.9573068618774414s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.020458698272705078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 8.821487426757812e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 47.694379806518555s
Believability | Calculation of trust value for Bio2RDF::Mesh took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-mesh took 1132.5354001522064s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 1.2700247764587402s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0006742477416992188s
Extra | Recovery of all triples for Bio2RDF::Mgi took 19.711148262023926s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.2671189308166504s
Amount of data | Number of triples check for Bio2RDF::Mgi took 46.04821181297302s
Interoperability | New terms check for Bio2RDF::Mgi took 44.53696966171265s
Versatility | Languages check for Bio2RDF::Mgi took 60.252729415893555s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.26459765434265137s
Security | Check HTTPS for Bio2RDF::Mgi took 0.15879535675048828s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.7818307876586914s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.38285303115844727s
Availability | RDF dump link check for Bio2RDF::Mgi took 0.29460573196411133s
License | MR license check for Bio2RDF::Mgi took 0.5896508693695068s
License | HR license check for Bio2RDF::Mgi took 60.23805832862854s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.27367258071899414s
Understandability | Number of label check for Bio2RDF::Mgi took 33.12771439552307s
Understandability | URI regex check for Bio2RDF::Mgi took 0.5812485218048096s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.26377201080322266s
Verifiability | Authors check for Bio2RDF::Mgi took 0.36324238777160645s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.24684429168701172s
Performance | Throughput check for Bio2RDF::Mgi took 11.161309957504272s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 74.66174626350403s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.27273988723754883s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.4330780506134033s
Interlinking | skos check for Bio2RDF::Mgi took 1.5917212963104248s
Interlinking | skos check for Bio2RDF::Mgi took 0.6438326835632324s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.2929809093475342s
Currency | Creation date check for Bio2RDF::Mgi took 0.5046980381011963s
Currency | Modification date check for Bio2RDF::Mgi took 0.5108332633972168s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 108.26071834564209s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 57.20799779891968s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.6126306056976318s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.29639124870300293s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.2540767192840576s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 7.630500793457031s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.8958380222320557s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6650073528289795s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.5136928558349609s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.55453944206238s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.4195706844329834s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 6.464591026306152s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.311211109161377s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.55338931083679s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7125661373138428s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.4389042854309082s
Security | Sign check for Bio2RDF::Mgi took 0.26659607887268066s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 10.829658508300781s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 1.3458361625671387s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.02037644386291504s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 0.00011777877807617188s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 61.28444766998291s
Believability | Calculation of trust value for Bio2RDF::Mgi took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-mgi took 1156.6261868476868s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.46610379219055176s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0006952285766601562s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 20.508440732955933s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.2196824550628662s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 44.928324937820435s
Interoperability | New terms check for Bio2RDF::Ncbigene took 43.382047176361084s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.25739765167236s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.27947044372558594s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.1446514129638672s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 1.0226106643676758s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.37334561347961426s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 5.325504779815674s
License | MR license check for Bio2RDF::Ncbigene took 0.5721890926361084s
License | HR license check for Bio2RDF::Ncbigene took 60.256163358688354s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.3214409351348877s
Understandability | Number of label check for Bio2RDF::Ncbigene took 9.815310001373291s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.6249034404754639s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.26642537117004395s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.2943301200866699s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.2727839946746826s
Performance | Throughput check for Bio2RDF::Ncbigene took 10.860067129135132s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 74.13731694221497s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.7277276515960693s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.42296671867370605s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.9384365081787109s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.39641451835632324s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.2802603244781494s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.5431320667266846s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.5255584716796875s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 111.95398211479187s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 58.06005001068115s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.4777092933654785s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2689850330352783s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.2923011779785156s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 8.450068950653076s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.8937051296234131s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6654365062713623s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.46610021591186523s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 66.40806078910828s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.4060757160186768s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.313157320022583s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.3493189811706543s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.5876362323761s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.7286727428436279s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.6765713691711426s
Security | Sign check for Bio2RDF::Ncbigene took 0.26928257942199707s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 10.721587419509888s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.5549719333648682s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.02034592628479004s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012111663818359375s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 61.41386961936951s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-ncbigene took 1148.1808984279633s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.5929009914398193s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0006449222564697266s
Extra | Recovery of all triples for Bio2RDF::Ndc took 20.343897581100464s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.2602035999298096s
Amount of data | Number of triples check for Bio2RDF::Ndc took 44.381712436676025s
Interoperability | New terms check for Bio2RDF::Ndc took 42.88932824134827s
Versatility | Languages check for Bio2RDF::Ndc took 60.2646267414093s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.2895772457122803s
Security | Check HTTPS for Bio2RDF::Ndc took 0.1576693058013916s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.6096274852752686s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.389965295791626s
Availability | RDF dump link check for Bio2RDF::Ndc took 0.34029078483581543s
License | MR license check for Bio2RDF::Ndc took 0.5238997936248779s
License | HR license check for Bio2RDF::Ndc took 60.27419114112854s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.27861595153808594s
Understandability | Number of label check for Bio2RDF::Ndc took 10.492570638656616s
Understandability | URI regex check for Bio2RDF::Ndc took 0.556652307510376s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.2561531066894531s
Verifiability | Authors check for Bio2RDF::Ndc took 0.37105870246887207s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.2609536647796631s
Performance | Throughput check for Bio2RDF::Ndc took 10.827080249786377s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 75.76813220977783s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.8973608016967773s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.40240955352783203s
Interlinking | skos check for Bio2RDF::Ndc took 1.028822898864746s
Interlinking | skos check for Bio2RDF::Ndc took 0.3380463123321533s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.27312660217285156s
Currency | Creation date check for Bio2RDF::Ndc took 0.5356853008270264s
Currency | Modification date check for Bio2RDF::Ndc took 0.5130338668823242s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 112.6005699634552s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 55.716262340545654s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.42265915870666504s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.29465794563293457s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.2851681709289551s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 7.909400939941406s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.8983321189880371s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6625974178314209s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.48703718185424805s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 66.17701077461243s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.418113946914673s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 7.140142202377319s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.302457332611084s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.52644968032837s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7249572277069092s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.676154613494873s
Security | Sign check for Bio2RDF::Ndc took 0.27179694175720215s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 11.015018224716187s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 1.0293240547180176s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.0203704833984375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 4.363059997558594e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 62.46631598472595s
Believability | Calculation of trust value for Bio2RDF::Ndc took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-ndc took 1109.4243676662445s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 4.1484832763671875e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.7294139862060547s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.0205535888671875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 3.170967102050781e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-netpath took 4.1592137813568115s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.13097047805786133s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.7122745513916016s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.020386695861816406s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.314018249511719e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 9.298324584960938e-06s
INFO | --- Analysis for bio2rdf-nextprot took 4.148071527481079s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.5707640647888184s
Availability | VoID file availability check for Bio2RDF::Omim took 0.00033354759216308594s
Extra | Recovery of all triples for Bio2RDF::Omim took 21.68256115913391s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.2718055248260498s
Amount of data | Number of triples check for Bio2RDF::Omim took 45.058945655822754s
Interoperability | New terms check for Bio2RDF::Omim took 40.92459535598755s
Versatility | Languages check for Bio2RDF::Omim took 60.251951694488525s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.2936258316040039s
Security | Check HTTPS for Bio2RDF::Omim took 0.16869664192199707s
Interpretability | RDF structures check for Bio2RDF::Omim took 1.1642169952392578s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.4102318286895752s
Availability | RDF dump link check for Bio2RDF::Omim took 0.3168313503265381s
License | MR license check for Bio2RDF::Omim took 0.41481852531433105s
License | HR license check for Bio2RDF::Omim took 60.260236501693726s
Amount of data | Number of property check for Bio2RDF::Omim took 0.26503682136535645s
Understandability | Number of label check for Bio2RDF::Omim took 9.852576494216919s
Understandability | URI regex check for Bio2RDF::Omim took 0.6074535846710205s
Understandability | Vocabs check for Bio2RDF::Omim took 0.2712442874908447s
Verifiability | Authors check for Bio2RDF::Omim took 0.3184971809387207s
Verifiability | Publishers check for Bio2RDF::Omim took 0.25931334495544434s
Performance | Throughput check for Bio2RDF::Omim took 11.208419799804688s
Amount of data | Check the number of entities for Bio2RDF::Omim took 74.04985547065735s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.6926357746124268s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.3656010627746582s
Interlinking | skos check for Bio2RDF::Omim took 0.9186136722564697s
Interlinking | skos check for Bio2RDF::Omim took 0.34700632095336914s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.25003933906555176s
Currency | Creation date check for Bio2RDF::Omim took 0.517341136932373s
Currency | Modification date check for Bio2RDF::Omim took 0.5063295364379883s
Rep.Conc. | URIs length for Bio2RDF::Omim took 108.53756046295166s
Interoperability | New vocabularies check for Bio2RDF::Omim took 62.230650663375854s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.4189152717590332s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.2763378620147705s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.2743527889251709s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 7.504913330078125s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.893153190612793s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6766672134399414s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.48629117012023926s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 65.07676863670349s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.423038959503174s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 7.03652811050415s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.3069498538970947s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.53352189064026s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.704857349395752s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 1.5525219440460205s
Security | Sign check for Bio2RDF::Omim took 0.2912771701812744s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 10.548627614974976s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.5560770034790039s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.020267724990844727s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.0001327991485595703s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 57.193095684051514s
Believability | Calculation of trust value for Bio2RDF::Omim took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-omim took 1126.015985250473s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 4.458427429199219e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0006191730499267578s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.27835679054260254s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.019982099533081055s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.62396240234375e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 4.091388702392578s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.5896942615509033s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0006513595581054688s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 19.14333200454712s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.2389283180236816s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 44.75027942657471s
Interoperability | New terms check for Bio2RDF::Orphanet took 39.960432052612305s
Versatility | Languages check for Bio2RDF::Orphanet took 60.25230693817139s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.24850845336914062s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.15439295768737793s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 1.0925891399383545s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.3994712829589844s
Availability | RDF dump link check for Bio2RDF::Orphanet took 0.3282511234283447s
License | MR license check for Bio2RDF::Orphanet took 0.5337810516357422s
License | HR license check for Bio2RDF::Orphanet took 60.26096796989441s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.28144383430480957s
Understandability | Number of label check for Bio2RDF::Orphanet took 10.060856342315674s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.5883059501647949s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.25881528854370117s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.3086278438568115s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.2786722183227539s
Performance | Throughput check for Bio2RDF::Orphanet took 11.483883380889893s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 77.49184060096741s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.8519589900970459s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.34122204780578613s
Interlinking | skos check for Bio2RDF::Orphanet took 0.7987658977508545s
Interlinking | skos check for Bio2RDF::Orphanet took 0.3433046340942383s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.27723169326782227s
Currency | Creation date check for Bio2RDF::Orphanet took 0.5291800498962402s
Currency | Modification date check for Bio2RDF::Orphanet took 0.4977855682373047s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 110.89485359191895s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 51.871960163116455s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.4722716808319092s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.2828516960144043s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.28835058212280273s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 10.552700281143188s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.9065971374511719s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6679842472076416s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.5335354804992676s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 65.96727228164673s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.408027172088623s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 7.313185214996338s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.327638864517212s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.569586753845215s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7081220149993896s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.675769567489624s
Security | Sign check for Bio2RDF::Orphanet took 0.2910604476928711s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 10.701554536819458s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.5919981002807617s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.020878076553344727s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 8.082389831542969e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 46.74267387390137s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-orphanet took 1131.7833042144775s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.1481306552886963s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.2665238380432129s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020140409469604492s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.361701965332031e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 9.902775287628174s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.58431077003479s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0006113052368164062s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 22.63448977470398s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.2561533451080322s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 60.23468565940857s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 41.695046186447144s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.239763021469116s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.2818796634674072s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.16799569129943848s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.7742505073547363s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.3893013000488281s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 0.33014702796936035s
License | MR license check for Bio2RDF::Pharmgkb took 0.5920982360839844s
License | HR license check for Bio2RDF::Pharmgkb took 60.243316411972046s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.2641620635986328s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 10.162299156188965s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5609416961669922s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.2900230884552002s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.27126646041870117s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.2495899200439453s
Performance | Throughput check for Bio2RDF::Pharmgkb took 10.416510820388794s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 78.41391229629517s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 2.9490444660186768s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.4018533229827881s
Interlinking | skos check for Bio2RDF::Pharmgkb took 1.0715630054473877s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.34493136405944824s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.2435002326965332s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.5491223335266113s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.5320932865142822s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 114.68502116203308s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 43.43420195579529s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.4095649719238281s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 8.353704929351807s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.9115803241729736s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.7014980316162109s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.5311262607574463s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 65.71305012702942s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.412233591079712s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 8.297136306762695s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.3213927745819092s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.58180236816406s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7178523540496826s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.7072141170501709s
Security | Sign check for Bio2RDF::Pharmgkb took 0.28327059745788574s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 10.89829683303833s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 1.4145326614379883s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.024245023727416992s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 3.528594970703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0011496543884277344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 8.7738037109375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 52.3017692565918s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-pharmgkb took 1141.809986591339s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 4.220008850097656e-05s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.26711249351501465s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.021198272705078125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0009756088256835938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 3.838539123535156e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 4.28795051574707s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 4.00543212890625e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.2674729824066162s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.020555973052978516s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.218650817871094e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-pid took 3.7905023097991943s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 4.076957702636719e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.25876450538635254s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.020255088806152344s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 2.86102294921875e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-pubchem-2 took 3.3811984062194824s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.5994782447814941s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0006160736083984375s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 21.1729793548584s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2772574424743652s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 44.977020025253296s
Interoperability | New terms check for Bio2RDF::Pubmed took 41.6121461391449s
Versatility | Languages check for Bio2RDF::Pubmed took 60.24827027320862s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.3030412197113037s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.15825843811035156s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.8196632862091064s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.3704376220703125s
Availability | RDF dump link check for Bio2RDF::Pubmed took 0.35250139236450195s
License | MR license check for Bio2RDF::Pubmed took 0.7280356884002686s
License | HR license check for Bio2RDF::Pubmed took 60.242958307266235s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.28687572479248047s
Understandability | Number of label check for Bio2RDF::Pubmed took 9.906886339187622s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.5846517086029053s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.25911855697631836s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.32251405715942383s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.2606220245361328s
Performance | Throughput check for Bio2RDF::Pubmed took 11.083982229232788s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 76.75084519386292s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.6771805286407471s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.3896162509918213s
Interlinking | skos check for Bio2RDF::Pubmed took 1.0103967189788818s
Interlinking | skos check for Bio2RDF::Pubmed took 0.33507752418518066s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.2624015808105469s
Currency | Creation date check for Bio2RDF::Pubmed took 0.4969649314880371s
Currency | Modification date check for Bio2RDF::Pubmed took 0.5028078556060791s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 111.68613743782043s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 59.50977063179016s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.4404425621032715s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.26985883712768555s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.29339122772216797s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 7.6518213748931885s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.899451494216919s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6598930358886719s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.4987502098083496s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.42662048339844s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.371413230895996s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.5461015701293945s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.2965054512023926s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.52949118614197s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.7056496143341064s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.6913042068481445s
Security | Sign check for Bio2RDF::Pubmed took 0.26626086235046387s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 10.821728944778442s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.8822324275970459s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.0001385211944580078s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 61.04966998100281s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-pubmed took 1142.828054189682s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 4.38690185546875e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.24630355834960938s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.020162105560302734s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 7.104873657226562e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-reactome took 4.723285913467407s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 4.1484832763671875e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.00038743019104003906s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.2823643684387207s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.020058870315551758s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 5.125999450683594e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-rhea took 3.8682072162628174s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.13840270042419434s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.6872713565826416s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.020375490188598633s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.510185241699219e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-sabiork took 10.100878715515137s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.5783979892730713s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0005650520324707031s
Extra | Recovery of all triples for Bio2RDF::Sgd took 20.8696768283844s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.2365524768829346s
Amount of data | Number of triples check for Bio2RDF::Sgd took 45.096108198165894s
Interoperability | New terms check for Bio2RDF::Sgd took 43.94315719604492s
Versatility | Languages check for Bio2RDF::Sgd took 60.23521137237549s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.284731388092041s
Security | Check HTTPS for Bio2RDF::Sgd took 0.16988062858581543s
Interpretability | RDF structures check for Bio2RDF::Sgd took 1.0009000301361084s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.3865985870361328s
Availability | RDF dump link check for Bio2RDF::Sgd took 0.32208251953125s
License | MR license check for Bio2RDF::Sgd took 0.6187248229980469s
License | HR license check for Bio2RDF::Sgd took 60.24296045303345s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.2533421516418457s
Understandability | Number of label check for Bio2RDF::Sgd took 10.757499694824219s
Understandability | URI regex check for Bio2RDF::Sgd took 0.5990464687347412s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.2912559509277344s
Verifiability | Authors check for Bio2RDF::Sgd took 0.3181121349334717s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.2651488780975342s
Performance | Throughput check for Bio2RDF::Sgd took 10.605093240737915s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 73.69227337837219s
Verifiability | Contribs. check for Bio2RDF::Sgd took 2.1518213748931885s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.40052294731140137s
Interlinking | skos check for Bio2RDF::Sgd took 1.252162218093872s
Interlinking | skos check for Bio2RDF::Sgd took 0.4103083610534668s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.2852199077606201s
Currency | Creation date check for Bio2RDF::Sgd took 0.4986996650695801s
Currency | Modification date check for Bio2RDF::Sgd took 0.5350310802459717s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 113.14781641960144s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 54.2108473777771s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.44389772415161133s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.2812988758087158s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.29253339767456055s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 8.00015926361084s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.8908848762512207s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.7058143615722656s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.44584226608276367s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 65.5328722000122s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.4237663745880127s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 7.230130434036255s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.3204209804534912s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.5690975189209s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.7118360996246338s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.6876311302185059s
Security | Sign check for Bio2RDF::Sgd took 0.2832789421081543s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 10.692647695541382s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.9854123592376709s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.02034473419189453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00010275840759277344s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 51.527859687805176s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-sgd took 1143.922721862793s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.57763671875e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0003666877746582031s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.6981644630432129s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.020285606384277344s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007190704345703125s
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 4.481541156768799s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.60691237449646s
Availability | VoID file availability check for Bio2RDF::Sider took 0.00035500526428222656s
Extra | Recovery of all triples for Bio2RDF::Sider took 21.8460214138031s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.224827766418457s
Amount of data | Number of triples check for Bio2RDF::Sider took 46.16173481941223s
Interoperability | New terms check for Bio2RDF::Sider took 43.92055416107178s
Versatility | Languages check for Bio2RDF::Sider took 60.24040150642395s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.2853724956512451s
Security | Check HTTPS for Bio2RDF::Sider took 0.14564251899719238s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.5652592182159424s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.4273197650909424s
Availability | RDF dump link check for Bio2RDF::Sider took 0.30597901344299316s
License | MR license check for Bio2RDF::Sider took 0.5331640243530273s
License | HR license check for Bio2RDF::Sider took 60.23809480667114s
Amount of data | Number of property check for Bio2RDF::Sider took 0.28031277656555176s
Understandability | Number of label check for Bio2RDF::Sider took 9.987419128417969s
Understandability | URI regex check for Bio2RDF::Sider took 0.5448956489562988s
Understandability | Vocabs check for Bio2RDF::Sider took 0.26622796058654785s
Verifiability | Authors check for Bio2RDF::Sider took 0.2843775749206543s
Verifiability | Publishers check for Bio2RDF::Sider took 0.26444458961486816s
Performance | Throughput check for Bio2RDF::Sider took 11.014292478561401s
Amount of data | Check the number of entities for Bio2RDF::Sider took 76.99248886108398s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.7085392475128174s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.3931729793548584s
Interlinking | skos check for Bio2RDF::Sider took 0.93082594871521s
Interlinking | skos check for Bio2RDF::Sider took 0.3672475814819336s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.25366902351379395s
Currency | Creation date check for Bio2RDF::Sider took 0.535667896270752s
Currency | Modification date check for Bio2RDF::Sider took 0.5210154056549072s
Rep.Conc. | URIs length for Bio2RDF::Sider took 111.52026271820068s
Interoperability | New vocabularies check for Bio2RDF::Sider took 50.67669606208801s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.45233654975891113s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.29404401779174805s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.2980499267578125s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 8.121646642684937s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.9009742736816406s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6582238674163818s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.5159702301025391s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 65.85096907615662s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.395612955093384s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 6.896290302276611s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.2847392559051514s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.551745891571045s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7185823917388916s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.6920299530029297s
Security | Sign check for Bio2RDF::Sider took 0.271620512008667s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 11.006119012832642s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.8402738571166992s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.02003026008605957s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.00543212890625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 49.5899600982666s
Believability | Calculation of trust value for Bio2RDF::Sider took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-sider took 1128.2184479236603s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.2725861072540283s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.020792722702026367s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 3.4332275390625e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-spike took 4.817749977111816s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.458427429199219e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.2697582244873047s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.020985126495361328s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 5.1975250244140625e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-taxon took 2.7541775703430176s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.5845057964324951s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0006361007690429688s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 20.40584945678711s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.2327640056610107s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 44.93963837623596s
Interoperability | New terms check for Bio2RDF::Taxonomy took 44.98605990409851s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.247493743896484s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.2623300552368164s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.15838861465454102s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.7221605777740479s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.3787078857421875s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 0.3823268413543701s
License | MR license check for Bio2RDF::Taxonomy took 0.5506563186645508s
License | HR license check for Bio2RDF::Taxonomy took 60.25939440727234s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.25037598609924316s
Understandability | Number of label check for Bio2RDF::Taxonomy took 10.116928100585938s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.5968453884124756s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.26932191848754883s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.32717275619506836s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.2806828022003174s
Performance | Throughput check for Bio2RDF::Taxonomy took 11.426028966903687s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 75.12025570869446s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 2.9613351821899414s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.424785852432251s
Interlinking | skos check for Bio2RDF::Taxonomy took 1.1553139686584473s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.39914751052856445s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.26145243644714355s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.5239870548248291s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.5107276439666748s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 113.27742433547974s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 56.14051651954651s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.43786120414733887s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.29323554039001465s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.2860691547393799s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 8.683857202529907s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.9104392528533936s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.7133021354675293s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.46799564361572266s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 65.35834431648254s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.3860747814178467s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 7.299746513366699s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.3041555881500244s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.54268193244934s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7087981700897217s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.6886191368103027s
Security | Sign check for Bio2RDF::Taxonomy took 0.272136926651001s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 10.756994009017944s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 1.3877778053283691s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.02079010009765625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.0001010894775390625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 52.75227451324463s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-taxonomy took 1172.6701254844666s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.1429436206817627s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.2691195011138916s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.020179033279418945s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0008208751678466797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.4332275390625e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 16.769548654556274s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.6047685146331787s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0006258487701416016s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 19.58334231376648s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.220571756362915s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 44.720213651657104s
Interoperability | New terms check for Bio2RDF::Wormbase took 45.6884868144989s
Versatility | Languages check for Bio2RDF::Wormbase took 60.242141008377075s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.26320576667785645s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.15801715850830078s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.9390983581542969s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.37415242195129395s
Availability | RDF dump link check for Bio2RDF::Wormbase took 0.3434591293334961s
License | MR license check for Bio2RDF::Wormbase took 0.46502685546875s
License | HR license check for Bio2RDF::Wormbase took 60.25842070579529s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.29288625717163086s
Understandability | Number of label check for Bio2RDF::Wormbase took 10.482532501220703s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.594069242477417s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.28914546966552734s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.2939183712005615s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.26035165786743164s
Performance | Throughput check for Bio2RDF::Wormbase took 11.036242961883545s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 78.18470978736877s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.7724626064300537s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.4086496829986572s
Interlinking | skos check for Bio2RDF::Wormbase took 1.0273950099945068s
Interlinking | skos check for Bio2RDF::Wormbase took 0.5684597492218018s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.25340867042541504s
Currency | Creation date check for Bio2RDF::Wormbase took 0.5127456188201904s
Currency | Modification date check for Bio2RDF::Wormbase took 0.5168414115905762s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 112.73781824111938s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 56.98245811462402s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.4243762493133545s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.28821659088134766s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.2782602310180664s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 7.600021123886108s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.9050576686859131s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6579265594482422s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.48516011238098145s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 65.94349074363708s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.399421453475952s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 7.159132957458496s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.2885539531707764s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.54464530944824s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7065019607543945s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.7101569175720215s
Security | Sign check for Bio2RDF::Wormbase took 0.2684612274169922s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 10.96367859840393s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.8782522678375244s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.02058553695678711s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 7.987022399902344e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 65.45364212989807s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-wormbase took 1171.282357931137s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.29340577125549316s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.29061269760131836s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020278215408325195s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.320808410644531e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 6.198883056640625e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 4.536560773849487s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 4.124641418457031e-05s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0003094673156738281s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.2887606620788574s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.02026200294494629s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 5.245208740234375e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 9.059906005859375e-06s
INFO | --- Analysis for biolit took 3.503572940826416s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.5916085243225098s
Availability | VoID file availability check for BioModels RDF took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.2833089828491211s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020409584045410156s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.981590270996094e-05s
Believability | Calculation of trust value for BioModels RDF took 8.106231689453125e-06s
INFO | --- Analysis for biomodels-rdf took 3.689511299133301s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 5.173683166503906e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.2986569404602051s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.020354270935058594s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006306171417236328s
Believability | Calculation of trust value for Amphibian gross anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-aao took 3.288726806640625s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.2438507080078125e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0012383460998535156s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.24972200393676758s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.020266056060791016s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.00030112266540527344s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-aba took 2.6770200729370117s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.25127363204956055s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.020866870880126953s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015172958374023438s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-acgt took 2.7011871337890625s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 9.012222290039062e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.2889516353607178s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.020357131958007812s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003368854522705078s
Believability | Calculation of trust value for Animal natural history and life history took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-adw took 2.7003486156463623s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.26733922958374023s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.020487546920776367s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0005257129669189453s
Believability | Calculation of trust value for Anatomical Entity Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-aeo took 2.706531524658203s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.27065277099609375s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.020297527313232422s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0010325908660888672s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-aero took 2.6696434020996094s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.220008850097656e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.2602393627166748s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.0207364559173584s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0004200935363769531s
Believability | Calculation of trust value for AI/RHEUM took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-air took 2.6495535373687744s
Availability | SPARQL endpoint availability check for Amino Acid took 4.3392181396484375e-05s
Availability | VoID file availability check for Amino Acid took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.29433345794677734s
Reputation | Calculation of the PageRank for Amino Acid took 0.020646333694458008s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0008270740509033203s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.00027632713317871094s
Believability | Calculation of trust value for Amino Acid took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-amino-acid took 2.6837058067321777s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.2583804130554199s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020441770553588867s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.00029158592224121094s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-apo took 2.64228892326355s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 4.38690185546875e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.258211612701416s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.02070450782775879s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00026345252990722656s
Believability | Calculation of trust value for African Traditional Medicine took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-atmo took 2.7141528129577637s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.4345855712890625e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.27962756156921387s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.020545244216918945s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 9.1552734375e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-ato took 2.6526710987091064s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.271470308303833s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.02049422264099121s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013363361358642578s
Believability | Calculation of trust value for BioAssay Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-bao took 2.646005868911743s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 4.506111145019531e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.2873690128326416s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020330429077148438s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.00038504600524902344s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 2.7236578464508057s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.2692861557006836s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.02071404457092285s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.00031638145446777344s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-bcgo took 2.7057242393493652s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.27701520919799805s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020887374877929688s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0014100074768066406s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-bdo took 2.6585474014282227s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.28928709030151367s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.020844459533691406s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0005118846893310547s
Believability | Calculation of trust value for Basic Formal Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bfo took 2.6464877128601074s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.315376281738281e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.2661454677581787s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.020691394805908203s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007641315460205078s
Believability | Calculation of trust value for Bleeding History Phenotype took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bho took 2.640850067138672s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 7.081031799316406e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.25495314598083496s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.02082228660583496s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.00045180320739746094s
Believability | Calculation of trust value for Bilateria anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bila took 2.6311066150665283s
Availability | SPARQL endpoint availability check for BIRNLex took 4.363059997558594e-05s
Availability | VoID file availability check for BIRNLex took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.2499101161956787s
Reputation | Calculation of the PageRank for BIRNLex took 0.021119117736816406s
Interlinking | Calculation of Degree of Connection for BIRNLex took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014946460723876953s
Believability | Calculation of trust value for BIRNLex took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-birnlex took 2.663106918334961s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.27954673767089844s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020511388778686523s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007698535919189453s
Believability | Calculation of trust value for Gene Regulation Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-bootstrep took 2.598813056945801s
Availability | SPARQL endpoint availability check for BioPAX took 4.2438507080078125e-05s
Availability | VoID file availability check for BioPAX took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for BioPAX took 0.2404623031616211s
Reputation | Calculation of the PageRank for BioPAX took 0.020632028579711914s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for BioPAX took 0.00010013580322265625s
Believability | Calculation of trust value for BioPAX took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bp took 2.562809944152832s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.2677936553955078s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.02072763442993164s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003409385681152344s
Believability | Calculation of trust value for Biomedical Resource Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-bro_x1 took 2.622805595397949s
Availability | SPARQL endpoint availability check for Spatial Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.24480485916137695s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.020668745040893555s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.0002319812774658203s
Believability | Calculation of trust value for Spatial Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bspo took 2.637763023376465s
Availability | SPARQL endpoint availability check for BioTop took 4.2438507080078125e-05s
Availability | VoID file availability check for BioTop took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for BioTop took 0.2838592529296875s
Reputation | Calculation of the PageRank for BioTop took 0.020566463470458984s
Interlinking | Calculation of Degree of Connection for BioTop took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006415843963623047s
Believability | Calculation of trust value for BioTop took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bt took 2.6922881603240967s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.38690185546875e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.26294469833374023s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.0207669734954834s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008766651153564453s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-bto took 2.6765644550323486s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3098597526550293s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.020630359649658203s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018286705017089844s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-canco took 3.112706422805786s
Availability | SPARQL endpoint availability check for CAO took 4.3392181396484375e-05s
Availability | VoID file availability check for CAO took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for CAO took 0.27389097213745117s
Reputation | Calculation of the PageRank for CAO took 0.02036571502685547s
Interlinking | Calculation of Degree of Connection for CAO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CAO took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0006158351898193359s
Believability | Calculation of trust value for CAO took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cao took 2.678021192550659s
Availability | SPARQL endpoint availability check for CareLex took 4.220008850097656e-05s
Availability | VoID file availability check for CareLex took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for CareLex took 0.2403864860534668s
Reputation | Calculation of the PageRank for CareLex took 0.02059316635131836s
Interlinking | Calculation of Degree of Connection for CareLex took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.269050598144531e-05s
Believability | Calculation of trust value for CareLex took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-carelex took 2.6262824535369873s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.2716844081878662s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.02104806900024414s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0008256435394287109s
Believability | Calculation of trust value for Cell Cycle Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-cco took 2.8521246910095215s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.2681260108947754s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020673036575317383s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.0002720355987548828s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-cdao took 2.705596923828125s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 6.961822509765625e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.28377342224121094s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.020720720291137695s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0007960796356201172s
Believability | Calculation of trust value for Chemical entities of biological interest took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-chebi took 2.733185052871704s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 7.319450378417969e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.2533142566680908s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.021071672439575195s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002715587615966797s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 2.5907504558563232s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.2747001647949219s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.020355224609375s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007870197296142578s
Believability | Calculation of trust value for Chemical Information Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cheminf took 2.615893602371216s
Availability | SPARQL endpoint availability check for Cell type took 4.291534423828125e-05s
Availability | VoID file availability check for Cell type took 0.001047372817993164s
Completeness | Calculation of interlinking completeness for Cell type took 0.27270078659057617s
Reputation | Calculation of the PageRank for Cell type took 0.020360231399536133s
Interlinking | Calculation of Degree of Connection for Cell type took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cell type took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003941059112548828s
Believability | Calculation of trust value for Cell type took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cl took 2.6539905071258545s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 5.53131103515625e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.2834630012512207s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.020069122314453125s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008461475372314453s
Believability | Calculation of trust value for Cell Line Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-clo took 2.6920204162597656s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 4.839897155761719e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.28565096855163574s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.0001709461212158203s
Believability | Calculation of trust value for Clinical Measurement Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cmo took 2.653735399246216s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.601478576660156e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.29918861389160156s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.020472288131713867s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.00020313262939453125s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-cno took 2.6719911098480225s
Availability | SPARQL endpoint availability check for Wheat trait took 4.553794860839844e-05s
Availability | VoID file availability check for Wheat trait took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.26500487327575684s
Reputation | Calculation of the PageRank for Wheat trait took 0.020623207092285156s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.555152893066406e-05s
Believability | Calculation of trust value for Wheat trait took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-co_wheat took 2.625699996948242s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.4345855712890625e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.24048423767089844s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.02059173583984375s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.00034236907958984375s
Believability | Calculation of trust value for Cognitive Atlas took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-cogat took 2.716472625732422s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.2389695644378662s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.0205233097076416s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007457733154296875s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-cogpo took 2.6465485095977783s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 4.291534423828125e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.26578831672668457s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.02065730094909668s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004279613494873047s
Believability | Calculation of trust value for Current Procedural Terminology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-cpt took 2.5728402137756348s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 4.4345855712890625e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.3200509548187256s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020926475524902344s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0018281936645507812s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-csp took 3.0479390621185303s
Availability | SPARQL endpoint availability check for COSTART took 4.363059997558594e-05s
Availability | VoID file availability check for COSTART took 0.00054931640625s
Completeness | Calculation of interlinking completeness for COSTART took 0.2639336585998535s
Reputation | Calculation of the PageRank for COSTART took 0.020629405975341797s
Interlinking | Calculation of Degree of Connection for COSTART took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009794235229492188s
Believability | Calculation of trust value for COSTART took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-cst took 2.607361316680908s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.5299530029296875e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0011789798736572266s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.29149556159973145s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020752668380737305s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0009644031524658203s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0006155967712402344s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-ctcae took 2.6633195877075195s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 4.315376281738281e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0003504753112792969s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.26488184928894043s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.020737886428833008s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0005123615264892578s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-ctx took 2.691056966781616s
Availability | SPARQL endpoint availability check for Dendritic cell took 7.939338684082031e-05s
Availability | VoID file availability check for Dendritic cell took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.26526474952697754s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020685195922851562s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.0003178119659423828s
Believability | Calculation of trust value for Dendritic cell took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-dc_cl took 2.5459511280059814s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 8.177757263183594e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.2758033275604248s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.02064371109008789s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 0.00010132789611816406s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-ddanat took 2.618983268737793s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.410743713378906e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.284757137298584s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.020600080490112305s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009877681732177734s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-ddi took 2.7319884300231934s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 6.890296936035156e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0006492137908935547s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.25530362129211426s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007927417755126953s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 9.679794311523438e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-diagnosticont took 2.6355605125427246s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.2580587863922119s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.020252466201782227s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.0001647472381591797s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 2.7060434818267822s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Human disease ontology took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2525460720062256s
Reputation | Calculation of the PageRank for Human disease ontology took 0.020150423049926758s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006237030029296875s
Believability | Calculation of trust value for Human disease ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-doid took 2.6601126194000244s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.2438516616821289s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.02036118507385254s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008299350738525391s
Believability | Calculation of trust value for Electrocardiography Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ecg took 2.5662782192230225s
Availability | SPARQL endpoint availability check for Evidence codes took 4.220008850097656e-05s
Availability | VoID file availability check for Evidence codes took 0.0003914833068847656s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.25531911849975586s
Reputation | Calculation of the PageRank for Evidence codes took 0.020273923873901367s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.0517578125e-05s
Believability | Calculation of trust value for Evidence codes took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-eco took 2.5703177452087402s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.3032505512237549s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020182371139526367s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017323493957519531s
Believability | Calculation of trust value for Experimental Factor Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-efo took 3.0516483783721924s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 5.245208740234375e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0004343986511230469s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.26871728897094727s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.02036428451538086s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011730194091796875s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ehda took 2.4994890689849854s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.124641418457031e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.00040078163146972656s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.2613508701324463s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.020019054412841797s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007028579711914062s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-ehdaa took 2.5739128589630127s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.2438507080078125e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.2741532325744629s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.02008962631225586s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005285739898681641s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 2.6306164264678955s
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.0005326271057128906s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.26053714752197266s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.02036428451538086s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007243156433105469s
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.245208740234375e-06s
INFO | --- Analysis for bioportal-emap took 2.5422873497009277s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Environment Ontology took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.253887414932251s
Reputation | Calculation of the PageRank for Environment Ontology took 0.02050614356994629s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.00038814544677734375s
Believability | Calculation of trust value for Environment Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-envo took 2.6442482471466064s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 5.7220458984375e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.0003752708435058594s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.24862337112426758s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.020405054092407227s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.0003161430358886719s
Believability | Calculation of trust value for Plant environmental conditions took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-eo took 2.514752149581909s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 4.839897155761719e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.269364595413208s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.020291805267333984s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012285709381103516s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ep took 2.6009738445281982s
Availability | SPARQL endpoint availability check for Epilepsy took 4.2438507080078125e-05s
Availability | VoID file availability check for Epilepsy took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.26874780654907227s
Reputation | Calculation of the PageRank for Epilepsy took 0.0202486515045166s
Interlinking | Calculation of Degree of Connection for Epilepsy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.00013780593872070312s
Believability | Calculation of trust value for Epilepsy took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-epileponto took 2.7151706218719482s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.267692565917969e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.2563745975494385s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020108461380004883s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011553764343261719s
Believability | Calculation of trust value for eagle-i research resource ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ero took 2.6346354484558105s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.5299530029296875e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.27091383934020996s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020373821258544922s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011246204376220703s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ev took 2.6220505237579346s
Availability | SPARQL endpoint availability check for ExO took 7.390975952148438e-05s
Availability | VoID file availability check for ExO took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for ExO took 0.25209903717041016s
Reputation | Calculation of the PageRank for ExO took 0.02038884162902832s
Interlinking | Calculation of Degree of Connection for ExO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ExO took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00026106834411621094s
Believability | Calculation of trust value for ExO took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-exo took 2.6153483390808105s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 4.4345855712890625e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.2652456760406494s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020234107971191406s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00014019012451171875s
Believability | Calculation of trust value for Fungal gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-fao took 2.723837375640869s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.4345855712890625e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.2595365047454834s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.02022695541381836s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00022530555725097656s
Believability | Calculation of trust value for Biological imaging methods took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-fbbi took 2.6308341026306152s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 4.410743713378906e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.2633061408996582s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.02020573616027832s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006670951843261719s
Believability | Calculation of trust value for Drosophila gross anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-fbbt took 2.6527254581451416s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 5.507469177246094e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0006425380706787109s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.2713618278503418s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.02039813995361328s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004277229309082031s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-fbcv took 2.653693199157715s
Availability | SPARQL endpoint availability check for Drosophila development took 5.936622619628906e-05s
Availability | VoID file availability check for Drosophila development took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.2600722312927246s
Reputation | Calculation of the PageRank for Drosophila development took 0.02009892463684082s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 5.078315734863281e-05s
Believability | Calculation of trust value for Drosophila development took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fbdv took 2.65002179145813s
Availability | SPARQL endpoint availability check for Fly taxonomy took 5.626678466796875e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.281862735748291s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.020267724990844727s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003638267517089844s
Believability | Calculation of trust value for Fly taxonomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-fbsp took 2.60657000541687s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.363059997558594e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.2667098045349121s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020258665084838867s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00021696090698242188s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 2.6860897541046143s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.2409961223602295s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020653247833251953s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.00040793418884277344s
Believability | Calculation of trust value for Family Health History Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-fhho took 2.473768472671509s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.26218724250793457s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.020277976989746094s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.001088857650756836s
Believability | Calculation of trust value for Influenza Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-flu took 2.5649466514587402s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 4.3392181396484375e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.26491689682006836s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.02061772346496582s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.866455078125e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fma took 2.639404296875s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.2761101722717285s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.020458221435546875s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00012993812561035156s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fypo took 2.647822856903076s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 4.57763671875e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.2940950393676758s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 9.72747802734375e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-geospecies took 2.6725969314575195s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for General Formal Ontology took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.27765512466430664s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.025871753692626953s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.0001819133758544922s
Believability | Calculation of trust value for General Formal Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-gfo took 2.696092128753662s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.3392181396484375e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.00042438507080078125s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.27395153045654297s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.02044820785522461s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0006167888641357422s
Believability | Calculation of trust value for General Formal Ontology: Biology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-gfo-bio took 2.634291410446167s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.267692565917969e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.2672119140625s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.020414113998413086s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.000881195068359375s
Believability | Calculation of trust value for Gene Ontology Extension took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-go_x1 took 2.7031333446502686s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Gene Ontology took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.2540888786315918s
Reputation | Calculation of the PageRank for Gene Ontology took 0.020679712295532227s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008726119995117188s
Believability | Calculation of trust value for Gene Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-go_x2 took 2.642683744430542s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.38690185546875e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.29495763778686523s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.020709753036499023s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.1948089599609375e-05s
Believability | Calculation of trust value for Cereal Plant Development took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-gro took 2.6347973346710205s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.291534423828125e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.28130197525024414s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.02054429054260254s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004279613494873047s
Believability | Calculation of trust value for Cereal plant gross anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-gro_x1 took 2.669731855392456s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.26740312576293945s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020760774612426758s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007457733154296875s
Believability | Calculation of trust value for Gene Regulation Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-gro_x2 took 2.63088059425354s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.2516450881958008s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005533695220947266s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hao took 2.6773576736450195s
Availability | SPARQL endpoint availability check for HCPCS took 4.1961669921875e-05s
Availability | VoID file availability check for HCPCS took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for HCPCS took 0.2702155113220215s
Reputation | Calculation of the PageRank for HCPCS took 0.020534276962280273s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00022459030151367188s
Believability | Calculation of trust value for HCPCS took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hcpcs took 2.5805504322052s
Availability | SPARQL endpoint availability check for Health Level Seven took 4.291534423828125e-05s
Availability | VoID file availability check for Health Level Seven took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.25839877128601074s
Reputation | Calculation of the PageRank for Health Level Seven took 0.02055644989013672s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012810230255126953s
Believability | Calculation of trust value for Health Level Seven took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-hl7 took 2.618422269821167s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 4.220008850097656e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.2667882442474365s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.000347137451171875s
Believability | Calculation of trust value for HEALTH_INDICATORS took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hlth_indics took 2.6859419345855713s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 4.982948303222656e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.29166746139526367s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.02069234848022461s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.457069396972656e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hom took 2.674006700515747s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.839897155761719e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.2949223518371582s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.020559072494506836s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.337860107421875e-05s
Believability | Calculation of trust value for HOM-HARVARD took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hom_harvard took 2.598341226577759s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.26880884170532227s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.020570755004882812s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006647109985351562s
Believability | Calculation of trust value for Human Phenotype Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hp_x1 took 2.6832613945007324s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 5.435943603515625e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.26113295555114746s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.020686864852905273s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010814666748046875s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hpio took 2.6133997440338135s
Availability | SPARQL endpoint availability check for HUGO took 4.6253204345703125e-05s
Availability | VoID file availability check for HUGO took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for HUGO took 0.2648317813873291s
Reputation | Calculation of the PageRank for HUGO took 0.020686864852905273s
Interlinking | Calculation of Degree of Connection for HUGO took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for HUGO took 8.177757263183594e-05s
Believability | Calculation of trust value for HUGO took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hugo took 2.668299436569214s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.24300551414489746s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.02088761329650879s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0007021427154541016s
Believability | Calculation of trust value for Information Artifact Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-iao took 2.4989659786224365s
Availability | SPARQL endpoint availability check for ICD10 took 4.482269287109375e-05s
Availability | VoID file availability check for ICD10 took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for ICD10 took 0.2650768756866455s
Reputation | Calculation of the PageRank for ICD10 took 0.02089715003967285s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0008213520050048828s
Believability | Calculation of trust value for ICD10 took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-icd10 took 2.6468923091888428s
Availability | SPARQL endpoint availability check for ICD10CM took 4.4345855712890625e-05s
Availability | VoID file availability check for ICD10CM took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.25183629989624023s
Reputation | Calculation of the PageRank for ICD10CM took 0.02057194709777832s
Interlinking | Calculation of Degree of Connection for ICD10CM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006110668182373047s
Believability | Calculation of trust value for ICD10CM took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-icd10cm took 2.657118558883667s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.3392181396484375e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.25824785232543945s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.020618200302124023s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00016379356384277344s
Believability | Calculation of trust value for ICD-10-PCS took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icd10pcs took 2.613171339035034s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 5.793571472167969e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.2937657833099365s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020341157913208008s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006463527679443359s
Believability | Calculation of trust value for International Classification of Diseases took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-icd9cm took 2.6719584465026855s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 6.365776062011719e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.2692544460296631s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.020694494247436523s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.00045752525329589844s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-icf_x1 took 2.894158363342285s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 0.00010156631469726562s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.2667684555053711s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.02045130729675293s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012497901916503906s
Believability | Calculation of trust value for International Classification for Nursing Practice took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-icnp took 2.6611287593841553s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 4.3392181396484375e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.26964592933654785s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.020342111587524414s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0005173683166503906s
Believability | Calculation of trust value for International Classification of Primary Care took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-icpc took 2.8065900802612305s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 4.4345855712890625e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.25862669944763184s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020108699798583984s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008726119995117188s
Believability | Calculation of trust value for ICPC-2 PLUS took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-icpc2p took 2.6446964740753174s
Availability | SPARQL endpoint availability check for ICPS Network took 4.291534423828125e-05s
Availability | VoID file availability check for ICPS Network took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.2823209762573242s
Reputation | Calculation of the PageRank for ICPS Network took 0.020463943481445312s
Interlinking | Calculation of Degree of Connection for ICPS Network took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.000213623046875s
Believability | Calculation of trust value for ICPS Network took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icps took 2.6283321380615234s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 5.793571472167969e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.26035404205322266s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.0203092098236084s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008692741394042969s
Believability | Calculation of trust value for Infectious Disease Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-ido took 2.6693620681762695s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.251934289932251s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.020178556442260742s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011649131774902344s
Believability | Calculation of trust value for Brucellosis Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-idobru took 2.6713273525238037s
Availability | SPARQL endpoint availability check for Malaria Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.2924213409423828s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.020539522171020508s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0013043880462646484s
Believability | Calculation of trust value for Malaria Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-idomal took 2.6198999881744385s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 4.3392181396484375e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.267017126083374s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.02023625373840332s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0003223419189453125s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-iev took 2.6916911602020264s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.363059997558594e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.26494503021240234s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.02051544189453125s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00015687942504882812s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-imgt took 2.8625760078430176s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.506111145019531e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.00029778480529785156s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.2522542476654053s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020621299743652344s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005311965942382812s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-imr took 2.6160876750946045s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.25958752632141113s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.02025127410888672s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0008013248443603516s
Believability | Calculation of trust value for Interaction Network Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-ino took 2.642881393432617s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.38690185546875e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.29361414909362793s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.0202329158782959s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0008981227874755859s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.6716461181640625e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-invertebrata took 2.664992332458496s
Availability | SPARQL endpoint availability check for IxnO took 5.269050598144531e-05s
Availability | VoID file availability check for IxnO took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for IxnO took 0.25449204444885254s
Reputation | Calculation of the PageRank for IxnO took 0.020481109619140625s
Interlinking | Calculation of Degree of Connection for IxnO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00019741058349609375s
Believability | Calculation of trust value for IxnO took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-ixno took 2.5635578632354736s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.2438507080078125e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.28137755393981934s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0003764629364013672s
Believability | Calculation of trust value for SysMO-JERM took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-jerm took 2.7047808170318604s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.2780165672302246s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.02056288719177246s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.147125244140625e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-kisao took 2.6356844902038574s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.482269287109375e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.27628302574157715s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.02338886260986328s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.0002377033233642578s
Believability | Calculation of trust value for Loggerhead nesting took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-lhn took 2.635321617126465s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.2766244411468506s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020401477813720703s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.0002167224884033203s
Believability | Calculation of trust value for Lipid Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-lipro took 2.60721492767334s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.458427429199219e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.33228516578674316s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.02054762840270996s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0019078254699707031s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-lnc took 3.126711130142212s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.6253204345703125e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.28803133964538574s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020682334899902344s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006456375122070312s
Believability | Calculation of trust value for Mouse adult gross anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ma took 2.702040195465088s
Availability | SPARQL endpoint availability check for Multiple alignment took 4.4345855712890625e-05s
Availability | VoID file availability check for Multiple alignment took 0.00031280517578125s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.2599220275878906s
Reputation | Calculation of the PageRank for Multiple alignment took 0.020331621170043945s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.0002028942108154297s
Believability | Calculation of trust value for Multiple alignment took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-mao took 2.622025728225708s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.4345855712890625e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.2822990417480469s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.020257234573364258s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0007104873657226562s
Believability | Calculation of trust value for Minimal anatomical terminology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mat took 2.6297199726104736s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 5.0067901611328125e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.2726106643676758s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020395994186401367s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0008745193481445312s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0005209445953369141s
Believability | Calculation of trust value for Breast tissue cell lines took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mcbcc took 2.6374120712280273s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Cell line ontology took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2861800193786621s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020206689834594727s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007457733154296875s
Believability | Calculation of trust value for Cell line ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mccl took 2.6358745098114014s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Cell line ontology took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.26497840881347656s
Reputation | Calculation of the PageRank for Cell line ontology took 0.022142887115478516s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0008528232574462891s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0015003681182861328s
Believability | Calculation of trust value for Cell line ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 2.6278274059295654s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 4.291534423828125e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.29441308975219727s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.020534038543701172s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.000240325927734375s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mcv took 2.6093802452087402s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.363059997558594e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.2903568744659424s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.020334482192993164s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00017523765563964844s
Believability | Calculation of trust value for Master Drug Data Base took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mddb took 2.608755350112915s
Availability | SPARQL endpoint availability check for MedDRA took 4.458427429199219e-05s
Availability | VoID file availability check for MedDRA took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for MedDRA took 0.2575969696044922s
Reputation | Calculation of the PageRank for MedDRA took 0.02026844024658203s
Interlinking | Calculation of Degree of Connection for MedDRA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MedDRA took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011532306671142578s
Believability | Calculation of trust value for MedDRA took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mdr took 2.615961790084839s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 4.315376281738281e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.2661092281341553s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.02179098129272461s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0008158683776855469s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0009405612945556641s
Believability | Calculation of trust value for MedlinePlus Health Topics took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-medlineplus took 2.6670761108398438s
Availability | SPARQL endpoint availability check for MeGO took 7.557868957519531e-05s
Availability | VoID file availability check for MeGO took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for MeGO took 0.25104522705078125s
Reputation | Calculation of the PageRank for MeGO took 0.020200252532958984s
Interlinking | Calculation of Degree of Connection for MeGO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00014853477478027344s
Believability | Calculation of trust value for MeGO took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mego took 2.619232177734375s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.291534423828125e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.3415818214416504s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.02026963233947754s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0018341541290283203s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-mesh-owl took 3.1396484375s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.26541662216186523s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.02015542984008789s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006186962127685547s
Believability | Calculation of trust value for Mental Functioning Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mf took 2.607271432876587s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.696846008300781e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.27339911460876465s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.02024531364440918s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005476474761962891s
Believability | Calculation of trust value for Medaka fish anatomy and development took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mfo took 2.6420533657073975s
Availability | SPARQL endpoint availability check for Emotion Ontology took 6.031990051269531e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.2677493095397949s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.02040696144104004s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007619857788085938s
Believability | Calculation of trust value for Emotion Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mfoem took 2.6563432216644287s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 7.343292236328125e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.2880289554595947s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.02024555206298828s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00010228157043457031s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mhc took 2.6604981422424316s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.3392181396484375e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.24118757247924805s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.02024984359741211s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0007412433624267578s
Believability | Calculation of trust value for Protein-protein interaction took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mi took 2.600393056869507s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.744529724121094e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.28763675689697266s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020133018493652344s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007302761077880859s
Believability | Calculation of trust value for Mosquito insecticide resistance took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-miro took 2.6884710788726807s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0003905296325683594s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.24670863151550293s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.020236968994140625s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00013446807861328125s
Believability | Calculation of trust value for Measurement Method Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mmo took 2.6356983184814453s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for MGED Ontology took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.28333044052124023s
Reputation | Calculation of the PageRank for MGED Ontology took 0.020732879638671875s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0003826618194580078s
Believability | Calculation of trust value for MGED Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mo took 2.615225076675415s
Availability | SPARQL endpoint availability check for Protein modification took 4.601478576660156e-05s
Availability | VoID file availability check for Protein modification took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Protein modification took 0.28139162063598633s
Reputation | Calculation of the PageRank for Protein modification took 0.02020263671875s
Interlinking | Calculation of Degree of Connection for Protein modification took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Protein modification took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00021505355834960938s
Believability | Calculation of trust value for Protein modification took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mod took 2.649970769882202s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.315376281738281e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.2667970657348633s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.0202639102935791s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006568431854248047s
Believability | Calculation of trust value for Mammalian phenotype took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mp took 2.62929630279541s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.267692565917969e-05s
Availability | VoID file availability check for Mouse pathology took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.25276994705200195s
Reputation | Calculation of the PageRank for Mouse pathology took 0.021297216415405273s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0004754066467285156s
Believability | Calculation of trust value for Mouse pathology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mpath took 2.552568197250366s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.220008850097656e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.2524406909942627s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0003573894500732422s
Believability | Calculation of trust value for Mass spectrometry took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ms took 2.65336275100708s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 4.673004150390625e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.00030040740966796875s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.3039588928222656s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020434856414794922s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018889904022216797s
Believability | Calculation of trust value for Medical Subject Headings took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-msh took 3.0976905822753906s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.2438507080078125e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.2538759708404541s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.02040410041809082s
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.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00016999244689941406s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mthch took 2.590111017227173s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 5.412101745605469e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.25266599655151367s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020323991775512695s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0007791519165039062s
Believability | Calculation of trust value for Natural Products Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-natpro took 2.7151496410369873s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 5.793571472167969e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.2652125358581543s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.020160436630249023s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008182525634765625s
Believability | Calculation of trust value for NCBI organismal classification took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 2.536017417907715s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.267692565917969e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.30190229415893555s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020188093185424805s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0020034313201904297s
Believability | Calculation of trust value for NCI Thesaurus took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ncit took 3.027479410171509s
Availability | SPARQL endpoint availability check for National Drug Data File took 4.4345855712890625e-05s
Availability | VoID file availability check for National Drug Data File took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.2829110622406006s
Reputation | Calculation of the PageRank for National Drug Data File took 0.020714521408081055s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006206035614013672s
Believability | Calculation of trust value for National Drug Data File took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-nddf took 2.6653175354003906s
Availability | SPARQL endpoint availability check for National Drug File took 4.291534423828125e-05s
Availability | VoID file availability check for National Drug File took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for National Drug File took 0.2594928741455078s
Reputation | Calculation of the PageRank for National Drug File took 0.020857572555541992s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012447834014892578s
Believability | Calculation of trust value for National Drug File took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ndfrt took 2.4939587116241455s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.8160552978515625e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.2668769359588623s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0012099742889404297s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 2.6706390380859375s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.2428133487701416s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.02080535888671875s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006992816925048828s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-neomark took 2.6651558876037598s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0003170967102050781s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.271747350692749s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.02064800262451172s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00013256072998046875s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-neomarkontology took 2.591074228286743s
Availability | SPARQL endpoint availability check for NIFSTD took 4.3392181396484375e-05s
Availability | VoID file availability check for NIFSTD took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.3080780506134033s
Reputation | Calculation of the PageRank for NIFSTD took 0.020499229431152344s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0018944740295410156s
Believability | Calculation of trust value for NIFSTD took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nif took 2.980499267578125s
Availability | SPARQL endpoint availability check for NIF Cell took 4.220008850097656e-05s
Availability | VoID file availability check for NIF Cell took 0.0003898143768310547s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.25491762161254883s
Reputation | Calculation of the PageRank for NIF Cell took 0.020735979080200195s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013713836669921875s
Believability | Calculation of trust value for NIF Cell took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-nif_cell took 2.644822359085083s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.601478576660156e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.2765316963195801s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020598411560058594s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0014073848724365234s
Believability | Calculation of trust value for NIF Dysfunction took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 2.7032527923583984s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.2830932140350342s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.020709991455078125s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005578994750976562s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nigo took 2.697087287902832s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 5.435943603515625e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.25713133811950684s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.020366668701171875s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005712509155273438s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nmr took 2.5816328525543213s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 7.677078247070312e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.2462456226348877s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.021198511123657227s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00011277198791503906s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-nonrctontology took 2.6303458213806152s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 5.4836273193359375e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0004124641418457031s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.2617340087890625s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0011959075927734375s
Believability | Calculation of trust value for NanoParticle Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-npo took 2.5364830493927s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.38690185546875e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.2675435543060303s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.0205233097076416s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007307529449462891s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-oae took 2.6111574172973633s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.25786924362182617s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.0205233097076416s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0014576911926269531s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-obi took 2.5968024730682373s
Availability | SPARQL endpoint availability check for OBOE took 4.291534423828125e-05s
Availability | VoID file availability check for OBOE took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for OBOE took 0.26328611373901367s
Reputation | Calculation of the PageRank for OBOE took 0.0206756591796875s
Interlinking | Calculation of Degree of Connection for OBOE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.0001163482666015625s
Believability | Calculation of trust value for OBOE took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-oboe took 2.6828458309173584s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.410743713378906e-05s
Availability | VoID file availability check for OBOE SBC took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.2443854808807373s
Reputation | Calculation of the PageRank for OBOE SBC took 0.02020120620727539s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007739067077636719s
Believability | Calculation of trust value for OBOE SBC took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 2.570220947265625s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.24201583862304688s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020645618438720703s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0009665489196777344s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0006778240203857422s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ocre took 2.606719970703125s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 4.315376281738281e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.2715451717376709s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.020148515701293945s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008530616760253906s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-odgi took 2.6156063079833984s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.26407814025878906s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.0202639102935791s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008916854858398438s
Believability | Calculation of trust value for Ontology for Genetic Interval took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ogi took 2.586223602294922s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 4.291534423828125e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.2512021064758301s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0008721351623535156s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.000324249267578125s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ogmd took 2.7113287448883057s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.291534423828125e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.26941633224487305s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.020439863204956055s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006964206695556641s
Believability | Calculation of trust value for Ontology for General Medical Science took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ogms took 2.605053186416626s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.4345855712890625e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.2722439765930176s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020417213439941406s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011217594146728516s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-omim took 2.580333948135376s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.291534423828125e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.280487060546875s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020388364791870117s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003712177276611328s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-omit took 2.6663336753845215s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.291534423828125e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0003504753112792969s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.26544976234436035s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.020111560821533203s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0006275177001953125s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-omrse took 2.353092670440674s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.291534423828125e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.2831573486328125s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.02028512954711914s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0008509159088134766s
Believability | Calculation of trust value for Ontology of Data Mining took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ontodm took 2.739750862121582s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.26662445068359375s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.020114898681640625s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.00026226043701171875s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ontodt took 2.623213768005371s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.267692565917969e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.2758445739746094s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.0207211971282959s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 3.075599670410156e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006129741668701172s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ontoorpha took 2.698425531387329s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.2613973617553711s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.02014780044555664s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009262561798095703s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-opl took 2.6445701122283936s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.315376281738281e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.2667875289916992s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.02019667625427246s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0009558200836181641s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0009701251983642578s
Believability | Calculation of trust value for Phenotypic quality took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-pato took 2.622659683227539s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.291534423828125e-05s
Availability | VoID file availability check for Physician Data Query took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.26474595069885254s
Reputation | Calculation of the PageRank for Physician Data Query took 0.02016162872314453s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0009613037109375s
Believability | Calculation of trust value for Physician Data Query took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pdq took 2.6706721782684326s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 8.559226989746094e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.27436065673828125s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.0202791690826416s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0008566379547119141s
Believability | Calculation of trust value for Pediatric Terminology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-pedterm took 2.682203769683838s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.26347923278808594s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0009722709655761719s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.0002372264862060547s
Believability | Calculation of trust value for Parasite Experiment Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-peo took 2.6182851791381836s
Availability | SPARQL endpoint availability check for PHARE took 4.291534423828125e-05s
Availability | VoID file availability check for PHARE took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for PHARE took 0.26885390281677246s
Reputation | Calculation of the PageRank for PHARE took 0.020633697509765625s
Interlinking | Calculation of Degree of Connection for PHARE took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0008060932159423828s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0007119178771972656s
Believability | Calculation of trust value for PHARE took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-phare took 2.6432156562805176s
Availability | SPARQL endpoint availability check for PKO_Re took 4.291534423828125e-05s
Availability | VoID file availability check for PKO_Re took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.2563350200653076s
Reputation | Calculation of the PageRank for PKO_Re took 0.020175933837890625s
Interlinking | Calculation of Degree of Connection for PKO_Re took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PKO_Re took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.0001678466796875s
Believability | Calculation of trust value for PKO_Re took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pko took 2.6093525886535645s
Availability | SPARQL endpoint availability check for PMA 2010 took 5.91278076171875e-05s
Availability | VoID file availability check for PMA 2010 took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.2825486660003662s
Reputation | Calculation of the PageRank for PMA 2010 took 0.020668983459472656s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0009098052978515625s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0009725093841552734s
Believability | Calculation of trust value for PMA 2010 took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pma took 2.5844578742980957s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 4.38690185546875e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.27243542671203613s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.0204312801361084s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.0001659393310546875s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pmr took 2.623258590698242s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.172325134277344e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.2675635814666748s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.02041482925415039s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.00038504600524902344s
Believability | Calculation of trust value for Plant Anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-po took 2.5868968963623047s
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.0005571842193603516s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.2914597988128662s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.02014470100402832s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 6.699562072753906e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-po_x1 took 2.612719774246216s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Plant Ontology took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.26604533195495605s
Reputation | Calculation of the PageRank for Plant Ontology took 0.020247220993041992s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.00043702125549316406s
Believability | Calculation of trust value for Plant Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-po_x2 took 2.6723735332489014s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 4.315376281738281e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.2674529552459717s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.0200192928314209s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006732940673828125s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pr took 2.6748416423797607s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.38690185546875e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.265622615814209s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.020499229431152344s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.00026679039001464844s
Believability | Calculation of trust value for Proteomics data and process provenance took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-propreo took 2.5803353786468506s
Availability | SPARQL endpoint availability check for Pathway ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Pathway ontology took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.28455114364624023s
Reputation | Calculation of the PageRank for Pathway ontology took 0.020361661911010742s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Pathway ontology took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00013375282287597656s
Believability | Calculation of trust value for Pathway ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-pw took 2.603342294692993s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.2815558910369873s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.020637035369873047s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 3.123283386230469e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.24249267578125e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-qibo took 2.603452444076538s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.363059997558594e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.3314790725708008s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.020795583724975586s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017881393432617188s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-rcd took 3.092461585998535s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.24973297119140625s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.020429372787475586s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00012564659118652344s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-rctontology took 2.656754970550537s
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.0006387233734130859s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.2651660442352295s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.02190375328063965s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 0.00010204315185546875s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-repo took 2.610375165939331s
Availability | SPARQL endpoint availability check for Physico-chemical process took 4.482269287109375e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.27169370651245117s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020671606063842773s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.0001990795135498047s
Believability | Calculation of trust value for Physico-chemical process took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-rex took 2.658573627471924s
Availability | SPARQL endpoint availability check for RadLex took 5.459785461425781e-05s
Availability | VoID file availability check for RadLex took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for RadLex took 0.27190232276916504s
Reputation | Calculation of the PageRank for RadLex took 0.02092266082763672s
Interlinking | Calculation of Degree of Connection for RadLex took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.001535654067993164s
Believability | Calculation of trust value for RadLex took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-rid took 2.6465070247650146s
Availability | SPARQL endpoint availability check for RNA ontology took 4.410743713378906e-05s
Availability | VoID file availability check for RNA ontology took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.25458264350891113s
Reputation | Calculation of the PageRank for RNA ontology took 0.021833181381225586s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0006039142608642578s
Believability | Calculation of trust value for RNA ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rnao took 2.5951662063598633s
Availability | SPARQL endpoint availability check for Role Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Role Ontology took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.2794034481048584s
Reputation | Calculation of the PageRank for Role Ontology took 0.021036386489868164s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00019931793212890625s
Believability | Calculation of trust value for Role Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-roleo took 2.7370266914367676s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 7.534027099609375e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.26793527603149414s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.02039813995361328s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00018143653869628906s
Believability | Calculation of trust value for Rat Strain Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-rs took 2.5955522060394287s
Availability | SPARQL endpoint availability check for RxNORM took 4.315376281738281e-05s
Availability | VoID file availability check for RxNORM took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for RxNORM took 0.2793154716491699s
Reputation | Calculation of the PageRank for RxNORM took 0.02021503448486328s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006139278411865234s
Believability | Calculation of trust value for RxNORM took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-rxnorm took 2.6578261852264404s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.315376281738281e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.2537977695465088s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.020658493041992188s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0008687973022460938s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.001108407974243164s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-sao took 2.648650884628296s
Availability | SPARQL endpoint availability check for Systems Biology took 4.4345855712890625e-05s
Availability | VoID file availability check for Systems Biology took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.25623273849487305s
Reputation | Calculation of the PageRank for Systems Biology took 0.020259857177734375s
Interlinking | Calculation of Degree of Connection for Systems Biology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.000457763671875s
Believability | Calculation of trust value for Systems Biology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sbo took 2.6256911754608154s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.2631974220275879s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.02033066749572754s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.0001239776611328125s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sbro took 2.5872561931610107s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.2704775333404541s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.02041912078857422s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013663768768310547s
Believability | Calculation of trust value for Sleep Domain Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sdo took 2.6408565044403076s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.267692565917969e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.26335978507995605s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.020215511322021484s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003440380096435547s
Believability | Calculation of trust value for Sample processing and separation techniques took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sep took 2.603973865509033s
Availability | SPARQL endpoint availability check for Student Health Record took 4.315376281738281e-05s
Availability | VoID file availability check for Student Health Record took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.2924368381500244s
Reputation | Calculation of the PageRank for Student Health Record took 0.020376205444335938s
Interlinking | Calculation of Degree of Connection for Student Health Record took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004394054412841797s
Believability | Calculation of trust value for Student Health Record took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-shr took 2.6286869049072266s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0006852149963378906s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.2689666748046875s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012655258178710938s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-sio took 3.320250988006592s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 4.363059997558594e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.26839327812194824s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.020307064056396484s
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.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.0002002716064453125s
Believability | Calculation of trust value for Situation-Based Access Control took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-sitbac took 2.615454912185669s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.4345855712890625e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.3003871440887451s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.020235776901245117s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019435882568359375s
Believability | Calculation of trust value for SNOMED Clinical Terms took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-snomedct took 3.121978759765625s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.30800318717956543s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.020096778869628906s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0007522106170654297s
Believability | Calculation of trust value for SNP-Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-snpo took 2.6071531772613525s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.220008850097656e-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.25325751304626465s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020139217376708984s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005824565887451172s
Believability | Calculation of trust value for Sequence types and features took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-so_x1 took 2.6234138011932373s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 4.3392181396484375e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.2980523109436035s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.020857572555541992s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015878677368164062s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-sopharm took 3.0362353324890137s
Availability | SPARQL endpoint availability check for SoyOntology took 4.458427429199219e-05s
Availability | VoID file availability check for SoyOntology took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.26674914360046387s
Reputation | Calculation of the PageRank for SoyOntology took 0.020770549774169922s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.0001323223114013672s
Believability | Calculation of trust value for SoyOntology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-soy took 2.636561393737793s
Availability | SPARQL endpoint availability check for Spider Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Spider Ontology took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.27840375900268555s
Reputation | Calculation of the PageRank for Spider Ontology took 0.02062082290649414s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00032591819763183594s
Believability | Calculation of trust value for Spider Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-spd took 2.6382856369018555s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.27782297134399414s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.021389007568359375s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00028061866760253906s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-spto took 2.638605833053589s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 5.245208740234375e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.2552216053009033s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.02086615562438965s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004794597625732422s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-sso took 2.703774929046631s
Availability | SPARQL endpoint availability check for Software Ontology took 5.340576171875e-05s
Availability | VoID file availability check for Software Ontology took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.2553558349609375s
Reputation | Calculation of the PageRank for Software Ontology took 0.020305633544921875s
Interlinking | Calculation of Degree of Connection for Software Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00040411949157714844s
Believability | Calculation of trust value for Software Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-swo took 2.6716835498809814s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.172325134277344e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.2790236473083496s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.0206301212310791s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.0002377033233642578s
Believability | Calculation of trust value for Tick gross anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tads took 2.696753978729248s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.2693214416503906s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.020675182342529297s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008766651153564453s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tao took 2.650397539138794s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.76837158203125e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0003573894500732422s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.24547910690307617s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.020824193954467773s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 9.369850158691406e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-taxrank took 2.6745986938476562s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 4.267692565917969e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.264315128326416s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.020588159561157227s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 9.059906005859375e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-teddy took 2.7217257022857666s
Availability | SPARQL endpoint availability check for Time Event Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.2757105827331543s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.02044224739074707s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007915496826171875s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008485317230224609s
Believability | Calculation of trust value for Time Event Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-teo took 2.6735551357269287s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 4.363059997558594e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.2641115188598633s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.02064204216003418s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0004019737243652344s
Believability | Calculation of trust value for Mosquito gross anatomy took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-tgma took 2.6384165287017822s
Availability | SPARQL endpoint availability check for thesaurus took 4.267692565917969e-05s
Availability | VoID file availability check for thesaurus took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for thesaurus took 0.2740652561187744s
Reputation | Calculation of the PageRank for thesaurus took 0.020710229873657227s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.818771362304688e-05s
Believability | Calculation of trust value for thesaurus took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-thesaurus took 2.6342873573303223s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.315376281738281e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0005476474761962891s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.29012513160705566s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.020442485809326172s
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.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.00036787986755371094s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 2.657047748565674s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.26937079429626465s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.020444869995117188s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008447170257568359s
Believability | Calculation of trust value for Translational Medicine Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-tmo took 2.7126519680023193s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 5.4836273193359375e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.002504587173461914s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.28042078018188477s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.020538330078125s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.0001575946807861328s
Believability | Calculation of trust value for Plant Trait Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-to took 2.5769646167755127s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.27866077423095703s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.020119428634643555s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.0001766681671142578s
Believability | Calculation of trust value for TOK_Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-tok took 2.694431781768799s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.3392181396484375e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.2661123275756836s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.02078843116760254s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00022220611572265625s
Believability | Calculation of trust value for Teleost taxonomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-tto took 2.6585659980773926s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.2558462619781494s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.02002739906311035s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010306835174560547s
Believability | Calculation of trust value for Uber anatomy ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-uberon took 2.603581190109253s
Availability | SPARQL endpoint availability check for Units Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Units Ontology took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.259080171585083s
Reputation | Calculation of the PageRank for Units Ontology took 0.020204544067382812s
Interlinking | Calculation of Degree of Connection for Units Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.00021600723266601562s
Believability | Calculation of trust value for Units Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-unitsontology took 2.6900203227996826s
Availability | SPARQL endpoint availability check for Units of measurement took 4.172325134277344e-05s
Availability | VoID file availability check for Units of measurement took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.280167818069458s
Reputation | Calculation of the PageRank for Units of measurement took 0.02023005485534668s
Interlinking | Calculation of Degree of Connection for Units of measurement took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.00027823448181152344s
Believability | Calculation of trust value for Units of measurement took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-uo took 2.6425857543945312s
Availability | SPARQL endpoint availability check for VANDF took 4.291534423828125e-05s
Availability | VoID file availability check for VANDF took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for VANDF took 0.26085972785949707s
Reputation | Calculation of the PageRank for VANDF took 0.02013254165649414s
Interlinking | Calculation of Degree of Connection for VANDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for VANDF took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0006916522979736328s
Believability | Calculation of trust value for VANDF took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-vandf took 2.6296234130859375s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 4.696846008300781e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.2680072784423828s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.02038884162902832s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0004134178161621094s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-vao took 2.6011974811553955s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 4.315376281738281e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.27169013023376465s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020639896392822266s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006666183471679688s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-vhog took 2.5802555084228516s
Availability | SPARQL endpoint availability check for VIVO took 4.220008850097656e-05s
Availability | VoID file availability check for VIVO took 0.0005354881286621094s
Completeness | Calculation of interlinking completeness for VIVO took 0.25821781158447266s
Reputation | Calculation of the PageRank for VIVO took 0.020295143127441406s
Interlinking | Calculation of Degree of Connection for VIVO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003514289855957031s
Believability | Calculation of trust value for VIVO took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-vivo took 2.644848108291626s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.2668619155883789s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.020165681838989258s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012578964233398438s
Believability | Calculation of trust value for Vaccine Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-vo took 2.6676318645477295s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.25334668159484863s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.020694971084594727s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00020885467529296875s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-vt took 2.6617612838745117s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.315376281738281e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.27245593070983887s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020731449127197266s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.000492095947265625s
Believability | Calculation of trust value for C. elegans gross anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-wbbt took 2.6589863300323486s
Availability | SPARQL endpoint availability check for C. elegans development took 4.363059997558594e-05s
Availability | VoID file availability check for C. elegans development took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.28029727935791016s
Reputation | Calculation of the PageRank for C. elegans development took 0.0203859806060791s
Interlinking | Calculation of Degree of Connection for C. elegans development took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.458427429199219e-05s
Believability | Calculation of trust value for C. elegans development took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-wbls took 2.664989471435547s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 7.081031799316406e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.2627980709075928s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.020789384841918945s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007379055023193359s
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.6455936431884766s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 0.0014982223510742188s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.2554025650024414s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0006096363067626953s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-who took 2.672971487045288s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 4.601478576660156e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.26500391960144043s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.021037817001342773s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0009946823120117188s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.00080108642578125s
Believability | Calculation of trust value for Xenopus anatomy and development took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-xao took 2.686025619506836s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.27885866165161133s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.020202159881591797s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00023412704467773438s
Believability | Calculation of trust value for Experimental Conditions Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-xco took 2.6895999908447266s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 4.172325134277344e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.26746058464050293s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.02121591567993164s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0008435249328613281s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0003190040588378906s
Believability | Calculation of trust value for Yeast phenotypes took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ypo took 2.5807993412017822s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 4.4345855712890625e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.2707972526550293s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.020555496215820312s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.000774383544921875s
Believability | Calculation of trust value for Zebrafish anatomy and development took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-zfa took 2.602860927581787s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.4170074462890625s
Availability | VoID file availability check for BioSamples RDF took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.28278541564941406s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.020462751388549805s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.3855438232421875e-05s
Believability | Calculation of trust value for BioSamples RDF took 6.67572021484375e-06s
INFO | --- Analysis for biosamples-rdf took 3.5193636417388916s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.9371743202209473s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.27080869674682617s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.020416259765625s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011801719665527344s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for bis-linked-data took 3.3962697982788086s
Availability | SPARQL endpoint availability check for Bitzi took 4.076957702636719e-05s
Availability | VoID file availability check for Bitzi took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for Bitzi took 0.25238561630249023s
Reputation | Calculation of the PageRank for Bitzi took 0.020502328872680664s
Interlinking | Calculation of Degree of Connection for Bitzi took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bitzi took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Bitzi took 3.361701965332031e-05s
Believability | Calculation of trust value for Bitzi took 8.344650268554688e-06s
INFO | --- Analysis for bitzi took 2.972398281097412s
Availability | SPARQL endpoint availability check for BizkaiSense took 4.291534423828125e-05s
Availability | VoID file availability check for BizkaiSense took 0.00031948089599609375s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.2693781852722168s
Reputation | Calculation of the PageRank for BizkaiSense took 0.020689725875854492s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 3.266334533691406e-05s
Believability | Calculation of trust value for BizkaiSense took 3.457069396972656e-05s
INFO | --- Analysis for bizkaisense took 2.922558546066284s
Availability | SPARQL endpoint availability check for blabla.itemlist took 5.555152893066406e-05s
Availability | VoID file availability check for blabla.itemlist took 0.00031065940856933594s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.2756531238555908s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020638704299926758s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.123283386230469e-05s
Believability | Calculation of trust value for blabla.itemlist took 8.58306884765625e-06s
INFO | --- Analysis for blabla-itemlist took 3.01713490486145s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.00543212890625e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0003399848937988281s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.2759828567504883s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.02091836929321289s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.409385681152344e-05s
Believability | Calculation of trust value for blabla.itemlist took 1.3589859008789062e-05s
INFO | --- Analysis for blabla_itemlist took 2.943984031677246s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.6876304149627686s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0004162788391113281s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.24619221687316895s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.02006077766418457s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.532669067382812e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for bluk-bnb took 12.021031141281128s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6895532608032227s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.00031495094299316406s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.3143622875213623s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 29.23461413383484s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 28.103978633880615s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 6.385818004608154s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 80.02741885185242s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 30.435295343399048s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3209059238433838s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0934150218963623s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.015677452087402s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 30.15877056121826s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 30.9210422039032s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 74.00088429450989s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.667126178741455s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.2060766220092773s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 31.22097659111023s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.696432113647461s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.105518341064453s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 30.477030754089355s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 28.77704644203186s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0002143383026123047s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6697051525115967s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.650667667388916s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6101810932159424s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.328670024871826s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.4834179878234863s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.2664556503295898s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.9800562858581543s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 22.02939248085022s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.4615602493286133s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4711637496948242s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.5350770950317383s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.9462428092956543s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.023862600326538086s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.028177499771118164s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5067653656005859s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 15.280121326446533s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5148186683654785s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.2078044414520264s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.2776787281036377s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 16.5094256401062s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03156471252441406s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0050015449523926s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.47609758377075195s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 10.936553955078125s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.3684914112091064s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02052617073059082s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.935264587402344e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1920928955078125e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.3909759521484375e-06s
INFO | --- Analysis for bpr took 1333.7484154701233s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 7.152557373046875e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.2695317268371582s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 7.939338684082031e-05s
Believability | Calculation of trust value for Brazilian Politicians took 5.245208740234375e-06s
INFO | --- Analysis for brazilian-politicians took 3.835376501083374s
Availability | SPARQL endpoint availability check for BrazilianCities took 4.076957702636719e-05s
Availability | VoID file availability check for BrazilianCities took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.2824540138244629s
Reputation | Calculation of the PageRank for BrazilianCities took 0.020158052444458008s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 3.0040740966796875e-05s
Believability | Calculation of trust value for BrazilianCities took 8.106231689453125e-06s
INFO | --- Analysis for braziliancities took 4.4113850593566895s
Availability | SPARQL endpoint availability check for Bricklink took 1.7567720413208008s
Availability | VoID file availability check for Bricklink took 0.0007219314575195312s
Completeness | Calculation of interlinking completeness for Bricklink took 0.2791740894317627s
Reputation | Calculation of the PageRank for Bricklink took 0.02030205726623535s
Interlinking | Calculation of Degree of Connection for Bricklink took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bricklink took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.532669067382812e-05s
Believability | Calculation of trust value for Bricklink took 6.9141387939453125e-06s
INFO | --- Analysis for bricklink took 10.294424772262573s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.248024702072144s
Availability | VoID file availability check for British Museum Collection took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.2702157497406006s
Reputation | Calculation of the PageRank for British Museum Collection took 0.020407676696777344s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.4332275390625e-05s
Believability | Calculation of trust value for British Museum Collection took 1.239776611328125e-05s
INFO | --- Analysis for british-museum-collection took 73.21842288970947s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 4.315376281738281e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.25646042823791504s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.020023107528686523s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007171630859375s
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 7.152557373046875e-06s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.4584014415740967s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 4.100799560546875e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.24020791053771973s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.02019190788269043s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 2.9802322387695312e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 6.9141387939453125e-06s
INFO | --- Analysis for bsv took 2.8534812927246094s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 4.076957702636719e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.2810540199279785s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.020324230194091797s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 2.9087066650390625e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 6.9141387939453125e-06s
INFO | --- Analysis for bund-offener-haushalt took 2.8886265754699707s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 5.459785461425781e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.000244140625s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.27358126640319824s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.02021050453186035s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 2.7894973754882812e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 6.4373016357421875e-06s
INFO | --- Analysis for bundestagnebeneinkuenfte took 3.2982561588287354s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.42823076248168945s
Availability | VoID file availability check for business.data.gov.uk took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.2723541259765625s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.020128965377807617s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 4.792213439941406e-05s
Believability | Calculation of trust value for business.data.gov.uk took 9.5367431640625e-06s
INFO | --- Analysis for business-data-gov-uk took 2.9077095985412598s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 4.0531158447265625e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.26207756996154785s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.020154953002929688s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 2.8848648071289062e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 7.3909759521484375e-06s
INFO | --- Analysis for cabbage took 2.8176114559173584s
Availability | SPARQL endpoint availability check for cablegate took 1.751596212387085s
Availability | VoID file availability check for cablegate took 0.00037217140197753906s
Completeness | Calculation of interlinking completeness for cablegate took 0.24692988395690918s
Reputation | Calculation of the PageRank for cablegate took 0.020444154739379883s
Interlinking | Calculation of Degree of Connection for cablegate took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for cablegate took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.67572021484375e-05s
Believability | Calculation of trust value for cablegate took 6.4373016357421875e-06s
INFO | --- Analysis for cablegate took 16.442930221557617s
Availability | SPARQL endpoint availability check for Calames took 4.291534423828125e-05s
Availability | VoID file availability check for Calames took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for Calames took 0.2612452507019043s
Reputation | Calculation of the PageRank for Calames took 0.020136594772338867s
Interlinking | Calculation of Degree of Connection for Calames took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Calames took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Calames took 3.4809112548828125e-05s
Believability | Calculation of trust value for Calames took 6.9141387939453125e-06s
INFO | --- Analysis for calames took 4.887670040130615s
Availability | SPARQL endpoint availability check for can-link took 4.267692565917969e-05s
Availability | VoID file availability check for can-link took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for can-link took 0.284257173538208s
Reputation | Calculation of the PageRank for can-link took 0.020277023315429688s
Interlinking | Calculation of Degree of Connection for can-link took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for can-link took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for can-link took 3.0040740966796875e-05s
Believability | Calculation of trust value for can-link took 6.9141387939453125e-06s
INFO | --- Analysis for can-link took 2.9457857608795166s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.07651853561401367s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.2555673122406006s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.020442962646484375s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007307529449462891s
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.3909759521484375e-06s
INFO | --- Analysis for cap-italy-rdf took 2.483165979385376s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 7.05718994140625e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0003948211669921875s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.2521045207977295s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020311594009399414s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 3.7670135498046875e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 6.9141387939453125e-06s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 2.9092302322387695s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 4.100799560546875e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.278552770614624s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.02019667625427246s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 2.7894973754882812e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 1.5497207641601562e-05s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 2.8851869106292725s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.363059997558594e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.28485631942749023s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 9.965896606445312e-05s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 7.3909759521484375e-06s
INFO | --- Analysis for ce4r took 18.638431072235107s
Availability | SPARQL endpoint availability check for Charging Stations took 4.076957702636719e-05s
Availability | VoID file availability check for Charging Stations took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.28673791885375977s
Reputation | Calculation of the PageRank for Charging Stations took 0.020436525344848633s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 2.956390380859375e-05s
Believability | Calculation of trust value for Charging Stations took 7.3909759521484375e-06s
INFO | --- Analysis for charging-stations took 2.9291083812713623s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.315376281738281e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0007021427154541016s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.25188398361206055s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.020248889923095703s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.62396240234375e-05s
Believability | Calculation of trust value for Chat Game corpus took 7.62939453125e-06s
INFO | --- Analysis for chat-game-corpus took 12.523823738098145s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 4.00543212890625e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.00031256675720214844s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.2639787197113037s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.020189523696899414s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.3855438232421875e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 7.62939453125e-06s
INFO | --- Analysis for chebi took 2.859102964401245s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.982948303222656e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0007433891296386719s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.31673765182495117s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.02067422866821289s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 6.556510925292969e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 6.67572021484375e-06s
INFO | --- Analysis for chem2bio2rdf took 135.07407069206238s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.5747697353363037s
Availability | VoID file availability check for ChEMBL RDF took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.2752547264099121s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.020505189895629883s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.1021575927734375e-05s
Believability | Calculation of trust value for ChEMBL RDF took 7.867813110351562e-06s
INFO | --- Analysis for chembl-rdf took 4.0562825202941895s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 4.291534423828125e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.25209689140319824s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.02051401138305664s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.075599670410156e-05s
Believability | Calculation of trust value for ChemPedia RDF took 7.152557373046875e-06s
INFO | --- Analysis for chempedia-rdf took 9.23601245880127s
Availability | SPARQL endpoint availability check for Chronicling America took 4.291534423828125e-05s
Availability | VoID file availability check for Chronicling America took 0.000606536865234375s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.25932860374450684s
Reputation | Calculation of the PageRank for Chronicling America took 0.020189762115478516s
Interlinking | Calculation of Degree of Connection for Chronicling America took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 9.989738464355469e-05s
Believability | Calculation of trust value for Chronicling America took 6.9141387939453125e-06s
INFO | --- Analysis for chronicling-america took 6.735901832580566s
Availability | SPARQL endpoint availability check for ciard-ring took 4.2438507080078125e-05s
Availability | VoID file availability check for ciard-ring took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.27048563957214355s
Reputation | Calculation of the PageRank for ciard-ring took 0.020763397216796875s
Interlinking | Calculation of Degree of Connection for ciard-ring took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.57763671875e-05s
Believability | Calculation of trust value for ciard-ring took 7.152557373046875e-06s
INFO | --- Analysis for ciard-ring took 4.738501787185669s
Availability | SPARQL endpoint availability check for CIPFA took 4.410743713378906e-05s
Availability | VoID file availability check for CIPFA took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for CIPFA took 0.2681875228881836s
Reputation | Calculation of the PageRank for CIPFA took 0.020318031311035156s
Interlinking | Calculation of Degree of Connection for CIPFA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CIPFA took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for CIPFA took 5.7697296142578125e-05s
Believability | Calculation of trust value for CIPFA took 5.7220458984375e-06s
INFO | --- Analysis for cipfa took 2.6909775733947754s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.040722131729126s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0007233619689941406s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.2566094398498535s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.02049851417541504s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.0003924369812011719s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 7.62939453125e-06s
INFO | --- Analysis for ckan took 262.5932722091675s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 2.3476388454437256s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.3111755847930908s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.020153284072875977s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.106231689453125e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 4.76837158203125e-06s
INFO | --- Analysis for clean-energy-data-reegle took 12.400279760360718s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.2438507080078125e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.264601469039917s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.020411252975463867s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.581710815429688e-05s
Believability | Calculation of trust value for CLLD-afbo took 7.62939453125e-06s
INFO | --- Analysis for clld-afbo took 3.9609034061431885s
Availability | SPARQL endpoint availability check for CLLD-APICS took 4.291534423828125e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.27629995346069336s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.020328998565673828s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.82012939453125e-05s
Believability | Calculation of trust value for CLLD-APICS took 6.198883056640625e-06s
INFO | --- Analysis for clld-apics took 4.499772548675537s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.363059997558594e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.27641987800598145s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.02034306526184082s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.7670135498046875e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 7.152557373046875e-06s
INFO | --- Analysis for clld-ewave took 3.5551373958587646s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 4.363059997558594e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.29378819465637207s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.020571231842041016s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00010037422180175781s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 7.3909759521484375e-06s
INFO | --- Analysis for clld-glottolog took 3.4568800926208496s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 6.008148193359375e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.26857805252075195s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.02033066749572754s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 8.273124694824219e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 7.3909759521484375e-06s
INFO | --- Analysis for clld-phoible took 3.4832847118377686s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 4.2438507080078125e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.28104138374328613s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.020439624786376953s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 7.891654968261719e-05s
Believability | Calculation of trust value for CLLD-SAILS took 7.152557373046875e-06s
INFO | --- Analysis for clld-sails took 3.7014052867889404s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.3392181396484375e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.2513241767883301s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.02035832405090332s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.249282836914062e-05s
Believability | Calculation of trust value for CLLD-WALS took 7.152557373046875e-06s
INFO | --- Analysis for clld-wals took 3.5541296005249023s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.315376281738281e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.2569875717163086s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.0203249454498291s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.939338684082031e-05s
Believability | Calculation of trust value for CLLD-WOLD took 6.67572021484375e-06s
INFO | --- Analysis for clld-wold took 3.575608730316162s
Availability | SPARQL endpoint availability check for COD inventory took 5.0067901611328125e-05s
Availability | VoID file availability check for COD inventory took 0.00029730796813964844s
Completeness | Calculation of interlinking completeness for COD inventory took 0.26148176193237305s
Reputation | Calculation of the PageRank for COD inventory took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for COD inventory took 3.170967102050781e-05s
Believability | Calculation of trust value for COD inventory took 8.344650268554688e-06s
INFO | --- Analysis for cod-inventory took 2.8757693767547607s
Availability | SPARQL endpoint availability check for CODE Endpoint took 4.172325134277344e-05s
Availability | VoID file availability check for CODE Endpoint took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.253554105758667s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.020329713821411133s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 3.266334533691406e-05s
Believability | Calculation of trust value for CODE Endpoint took 7.3909759521484375e-06s
INFO | --- Analysis for code-endpoint took 2.9310386180877686s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 1.5792202949523926s
Availability | VoID file availability check for OpenUpLabs COINS took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.27715373039245605s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.020274877548217773s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.0517578125e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 5.0067901611328125e-06s
INFO | --- Analysis for coins-openuplabs took 4.066281795501709s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.06782793998718262s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.24411296844482422s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.0203399658203125s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.933906555175781e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for colinda took 2.58854603767395s
Availability | SPARQL endpoint availability check for CN  2012 took 25.242241144180298s
Availability | VoID file availability check for CN  2012 took 0.0009005069732666016s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.7141904830932617s
Reputation | Calculation of the PageRank for CN  2012 took 0.020270586013793945s
Interlinking | Calculation of Degree of Connection for CN  2012 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 3.552436828613281e-05s
Believability | Calculation of trust value for CN  2012 took 5.0067901611328125e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 124.59506845474243s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 4.1961669921875e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.00031185150146484375s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.2590157985687256s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.021392107009887695s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.0008058547973632812s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 3.170967102050781e-05s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 7.867813110351562e-06s
INFO | --- Analysis for comments-on-literature-in-literature took 3.332801342010498s
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.0002605915069580078s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.26370978355407715s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.02008366584777832s
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.0007421970367431641s
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 6.9141387939453125e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 2.939291000366211s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 4.2438507080078125e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.2648634910583496s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.020656824111938477s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 3.3855438232421875e-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.9660186767578125s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 4.0531158447265625e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.2542450428009033s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.020512104034423828s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 3.0994415283203125e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 7.152557373046875e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 2.991009473800659s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 4.076957702636719e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.24257946014404297s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.020188570022583008s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 3.0279159545898438e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 7.152557373046875e-06s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 2.8536508083343506s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 1.8172740936279297s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0007152557373046875s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.27579522132873535s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.02007603645324707s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.528594970703125e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 7.3909759521484375e-06s
INFO | --- Analysis for comsode-d3-2 took 7.051693677902222s
Availability | SPARQL endpoint availability check for ConceptNet took 4.0531158447265625e-05s
Availability | VoID file availability check for ConceptNet took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.25864601135253906s
Reputation | Calculation of the PageRank for ConceptNet took 0.020314693450927734s
Interlinking | Calculation of Degree of Connection for ConceptNet took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ConceptNet took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 2.9325485229492188e-05s
Believability | Calculation of trust value for ConceptNet took 6.9141387939453125e-06s
INFO | --- Analysis for conceptnet took 2.9190618991851807s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 4.220008850097656e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.24965190887451172s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.020200252532958984s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 2.8848648071289062e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 8.106231689453125e-06s
INFO | --- Analysis for connectivity-of-lod-datasets took 2.9066598415374756s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 5.2928924560546875e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.26833343505859375s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.020070552825927734s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 2.8371810913085938e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 6.9141387939453125e-06s
INFO | --- Analysis for copac-library-catalogue took 2.877789258956909s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 4.38690185546875e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.3053014278411865s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.02021312713623047s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 6.794929504394531e-05s
Believability | Calculation of trust value for CopyrightTermBank took 5.9604644775390625e-06s
INFO | --- Analysis for copyrighttermbank took 34.19409775733948s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 2.3089966773986816s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.2832362651824951s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020301342010498047s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.838539123535156e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 6.4373016357421875e-06s
INFO | --- Analysis for core took 7.054123640060425s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 4.124641418457031e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.2640509605407715s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.020207643508911133s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 3.0517578125e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 7.867813110351562e-06s
INFO | --- Analysis for corn took 2.8689000606536865s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 4.267692565917969e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.000308990478515625s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.24941110610961914s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.020827770233154297s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 3.314018249511719e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 6.9141387939453125e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 2.8839919567108154s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 4.1961669921875e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.26117444038391113s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.020244359970092773s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 4.887580871582031e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 3.361701965332031e-05s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 2.8388123512268066s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 4.291534423828125e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.29404234886169434s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.020202159881591797s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.7697296142578125e-05s
Believability | Calculation of trust value for Cornetto1.2 took 7.867813110351562e-06s
INFO | --- Analysis for cornetto took 12.664506673812866s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 4.1961669921875e-05s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.23961544036865234s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.020266294479370117s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 3.123283386230469e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 6.9141387939453125e-06s
INFO | --- Analysis for corscheck took 2.908336639404297s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.0779106616973877s
Availability | VoID file availability check for Courts thesaurus took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.2832951545715332s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.020613431930541992s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 7.009506225585938e-05s
Believability | Calculation of trust value for Courts thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for courts-thesaurus took 2.4576773643493652s
Availability | SPARQL endpoint availability check for CPA 2008 took 24.000471830368042s
Availability | VoID file availability check for CPA 2008 took 0.0007596015930175781s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.3882462978363037s
Reputation | Calculation of the PageRank for CPA 2008 took 0.020441293716430664s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 3.62396240234375e-05s
Believability | Calculation of trust value for CPA 2008 took 9.775161743164062e-06s
INFO | --- Analysis for cpa-2008 took 123.28744173049927s
Availability | SPARQL endpoint availability check for CPC 2008 took 24.19925570487976s
Availability | VoID file availability check for CPC 2008 took 0.0008063316345214844s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.26528334617614746s
Reputation | Calculation of the PageRank for CPC 2008 took 0.027016162872314453s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.52587890625e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 4.863739013671875e-05s
Believability | Calculation of trust value for CPC 2008 took 5.0067901611328125e-06s
INFO | --- Analysis for cpc-2008 took 123.14339685440063s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.150150060653687s
Availability | VoID file availability check for CPV  2003 took 0.0007860660552978516s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.6944561004638672s
Reputation | Calculation of the PageRank for CPV  2003 took 0.02031111717224121s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 4.315376281738281e-05s
Believability | Calculation of trust value for CPV  2003 took 9.775161743164062e-06s
INFO | --- Analysis for cpv-2003 took 114.14549398422241s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.098310470581055s
Availability | VoID file availability check for CPV 2008 took 0.000896453857421875s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.7038769721984863s
Reputation | Calculation of the PageRank for CPV 2008 took 0.020573854446411133s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 4.8160552978515625e-05s
Believability | Calculation of trust value for CPV 2008 took 5.9604644775390625e-06s
INFO | --- Analysis for cpv-2008 took 125.04722619056702s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 261.22685289382935s
Availability | VoID file availability check for crowdsourcing-fb took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.26999926567077637s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.020682573318481445s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.3392181396484375e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 8.58306884765625e-06s
INFO | --- Analysis for crowdsourcing-fb took 536.1867389678955s
Availability | SPARQL endpoint availability check for CRTM took 4.673004150390625e-05s
Availability | VoID file availability check for CRTM took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for CRTM took 0.6999876499176025s
Reputation | Calculation of the PageRank for CRTM took 0.02078080177307129s
Interlinking | Calculation of Degree of Connection for CRTM took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for CRTM took 3.24249267578125e-05s
Believability | Calculation of trust value for CRTM took 8.821487426757812e-06s
INFO | --- Analysis for crtm took 5.874891757965088s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 4.1961669921875e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.2940499782562256s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.020512819290161133s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 3.1948089599609375e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 9.059906005859375e-06s
INFO | --- Analysis for crystal-eye took 3.0071351528167725s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.853857517242432s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.31233859062194824s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.02021956443786621s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 4.7206878662109375e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 5.245208740234375e-06s
INFO | --- Analysis for ctic-public-dataset took 44.53641200065613s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 4.2438507080078125e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.25428009033203125s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.020225048065185547s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 2.8848648071289062e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 7.3909759521484375e-06s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 3.4537081718444824s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.5660707950592041s
Availability | VoID file availability check for CulturaLinkedData took 0.0004956722259521484s
Extra | Recovery of all triples for CulturaLinkedData took 139.09205222129822s
Performance | Total latancy measurement for CulturaLinkedData took 6.306097745895386s
Amount of data | Number of triples check for CulturaLinkedData took 4.963809967041016s
Interoperability | New terms check for CulturaLinkedData took 2.221158981323242s
Versatility | Languages check for CulturaLinkedData took 61.470128536224365s
Interpretability | Number of blank nodes check for CulturaLinkedData took 0.1681818962097168s
Interpretability | RDF structures check for CulturaLinkedData took 0.5165848731994629s
Versatility | Serialization formats check for CulturaLinkedData took 0.5364842414855957s
Availability | RDF dump link check for CulturaLinkedData took 0.25840115547180176s
License | MR license check for CulturaLinkedData took 0.7759857177734375s
License | HR license check for CulturaLinkedData took 64.16742134094238s
Amount of data | Number of property check for CulturaLinkedData took 1.9233040809631348s
Understandability | Number of label check for CulturaLinkedData took 2.8822500705718994s
Understandability | URI regex check for CulturaLinkedData took 0.5964891910552979s
Understandability | Vocabs check for CulturaLinkedData took 0.28043437004089355s
Verifiability | Authors check for CulturaLinkedData took 0.3280913829803467s
Verifiability | Publishers check for CulturaLinkedData took 0.27179813385009766s
Performance | Throughput check for CulturaLinkedData took 21.009780406951904s
Amount of data | Check the number of entities for CulturaLinkedData took 9.489059448242188e-05s
Verifiability | Contribs. check for CulturaLinkedData took 0.24194955825805664s
Interlinking | sameAs chians check for CulturaLinkedData took 0.36521148681640625s
Interlinking | skos check for CulturaLinkedData took 2.345031261444092s
Interlinking | skos check for CulturaLinkedData took 1.9130151271820068s
Timeliness | dataset update frequency check for CulturaLinkedData took 2.142817974090576s
Currency | Creation date check for CulturaLinkedData took 2.2578299045562744s
Currency | Modification date check for CulturaLinkedData took 2.120673656463623s
Rep.Conc. | URIs length for CulturaLinkedData took 64.80545139312744s
Interoperability | New vocabularies check for CulturaLinkedData took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 0.18052339553833008s
Accuracy | Check Functional Property for CulturaLinkedData took 2.023831844329834s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 0.18541336059570312s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 42.68330097198486s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.6282455921173096s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.3275768756866455s
Consistency | Disjoint class check for CulturaLinkedData took 0.20246171951293945s
Consistency | Check Misplaced properties for CulturaLinkedData took 10.670944213867188s
Consistency | Misplaced classes for CulturaLinkedData took 6.0845558643341064s
Consistency | Check Ontology hijacking for CulturaLinkedData took 44.42099738121033s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.3392915725708008s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 9.499483108520508s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.3845531940460205s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 0.17079973220825195s
Security | Sign check for CulturaLinkedData took 2.7346184253692627s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 11.081098794937134s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.4117729663848877s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.021229982376098633s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 3.409385681152344e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 4.0531158447265625e-06s
Believability | Calculation of trust value for CulturaLinkedData took 7.867813110351562e-06s
INFO | --- Analysis for culturalinkeddata took 665.8837037086487s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.1360914707183838s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007932186126708984s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.6860871315002441s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.02083134651184082s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 4.220008850097656e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 5.7220458984375e-06s
INFO | --- Analysis for cz-ares-or took 4.506361484527588s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.10561871528625488s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.2700679302215576s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.020794391632080078s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.9577484130859375e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ares-rzp took 2.7885043621063232s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.10140466690063477s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.2750051021575928s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.020874738693237305s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.528594970703125e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 6.67572021484375e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 3.3135979175567627s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.10592293739318848s
Availability | VoID file availability check for Integrated pollution registry took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.2951018810272217s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 4.029273986816406e-05s
Believability | Calculation of trust value for Integrated pollution registry took 6.198883056640625e-06s
INFO | --- Analysis for cz-cenia-pollution took 2.903216600418091s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.10500025749206543s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0011515617370605469s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.3113250732421875s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.02069568634033203s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.7670135498046875e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 1.0251998901367188e-05s
INFO | --- Analysis for cz-contracts took 2.84917950630188s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 4.172325134277344e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.26677989959716797s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.021099328994750977s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 3.647804260253906e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 1.0013580322265625e-05s
INFO | --- Analysis for cz-courts took 2.868013381958008s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.1128997802734375s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.25588130950927734s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.020546674728393555s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.504753112792969e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 6.198883056640625e-06s
INFO | --- Analysis for cz-ctia-bans took 5.485114812850952s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.10203838348388672s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0009255409240722656s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.2701897621154785s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020751953125s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.695487976074219e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 1.0013580322265625e-05s
INFO | --- Analysis for cz-ctia-confiscations took 2.781235694885254s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.11676645278930664s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.26739931106567383s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.020249366760253906s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.361701965332031e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ctia-focus took 2.737131118774414s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.10896492004394531s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.2674887180328369s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020357131958007812s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.029273986816406e-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.787501573562622s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.09858489036560059s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.27088236808776855s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.790855407714844e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 5.245208740234375e-06s
INFO | --- Analysis for cz-ctia-sanctions took 4.888255596160889s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.19467663764953613s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.00070953369140625s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.2692265510559082s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007979869842529297s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 3.814697265625e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 5.4836273193359375e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 2.775569438934326s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.10868406295776367s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.2735269069671631s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.020089149475097656s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.4809112548828125e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 5.9604644775390625e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 2.854731321334839s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.9066243171691895s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.23816990852355957s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.020823240280151367s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.838539123535156e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-czso-average-salaries took 3.793684720993042s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.4176192283630371s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.2837963104248047s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.02060103416442871s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 3.647804260253906e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.38512921333313s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.3587605953216553s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.2622101306915283s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.020529985427856445s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.7670135498046875e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.260064125061035s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.3717987537384033s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.25520801544189453s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.020457983016967773s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 4.124641418457031e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-job-applicants took 3.2677764892578125s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.4316112995147705s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.25121212005615234s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.981590270996094e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.3085975646972656s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.4336893558502197s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.27802610397338867s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.02036452293395996s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.647804260253906e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-regions took 3.111131191253662s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.3990485668182373s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.26001405715942383s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.020673036575317383s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.000873565673828125s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 4.410743713378906e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.2563326358795166s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.3721301555633545s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0010876655578613281s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.2753279209136963s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.01999807357788086s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 3.695487976074219e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.2943382263183594s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.3990309238433838s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.26348400115966797s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.02019476890563965s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.6716461181640625e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 3.356168270111084s
Availability | SPARQL endpoint availability check for ATC groups took 0.11292839050292969s
Availability | VoID file availability check for ATC groups took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for ATC groups took 0.25708794593811035s
Reputation | Calculation of the PageRank for ATC groups took 0.020220518112182617s
Interlinking | Calculation of Degree of Connection for ATC groups took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ATC groups took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for ATC groups took 6.771087646484375e-05s
Believability | Calculation of trust value for ATC groups took 9.059906005859375e-06s
INFO | --- Analysis for cz-eh-1-atc took 2.758147954940796s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.10535693168640137s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.2541079521179199s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.020008325576782227s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.266334533691406e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 5.7220458984375e-06s
INFO | --- Analysis for cz-fulfillments took 2.6684765815734863s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.04477262496948242s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.26581335067749023s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.02008533477783203s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.482269287109375e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 4.76837158203125e-06s
INFO | --- Analysis for cz-ic took 3.442328929901123s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.2202777862548828s
Availability | VoID file availability check for List of Czech data boxes took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.23644328117370605s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 2.9325485229492188e-05s
Believability | Calculation of trust value for List of Czech data boxes took 5.245208740234375e-06s
INFO | --- Analysis for cz-list-of-databoxes took 4.2130560874938965s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.24129748344421387s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2809128761291504s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.218650817871094e-05s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 4.76837158203125e-06s
INFO | --- Analysis for cz-nace took 4.330038785934448s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.32204771041870117s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0005362033843994141s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 44.47587442398071s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8707919120788574s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2551126480102539s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.588555097579956s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 15.757934808731079s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.55401611328125s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.24238204956054688s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.2058508396148682s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3186194896697998s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.38450145721435547s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5987677574157715s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16508150100708008s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5428981781005859s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3528311252593994s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17218589782714844s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.23259735107421875s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.27988147735595703s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.2 took 10.634469747543335s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.106231689453125e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16469264030456543s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.20580291748046875s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.332439661026001s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16507244110107422s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.8967349529266357s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.37867021560668945s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.32801270484924316s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.2 took 68.20024394989014s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16135740280151367s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.18167853355407715s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17472410202026367s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.2 took 49.757243633270264s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.466888189315796s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.741581678390503s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.18816375732421875s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.694974422454834s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.705893516540527s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.2 took 88.20752263069153s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.6296501159667969s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.9382905960083008s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.0847744941711426s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.21860361099243164s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.44734811782836914s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.2 took 1116.3662827014923s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.567439317703247s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8057911396026611s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.814697265625e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.430511474609375e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 5.9604644775390625e-06s
INFO | --- Analysis for cz-nkod took 64724.348217725754s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.2251729965209961s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.2838149070739746s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.020088911056518555s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.719329833984375e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 5.9604644775390625e-06s
INFO | --- Analysis for cz-orders took 3.860414981842041s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.3082101345062256s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0007131099700927734s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.29388928413391113s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.020806312561035156s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007269382476806641s
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 5.7220458984375e-06s
INFO | --- Analysis for cz-ovm took 4.535123825073242s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.10885858535766602s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.2866849899291992s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.020701169967651367s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 4.291534423828125e-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.732738733291626s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.26703357696533203s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.00054931640625s
Extra | Recovery of all triples for Registry of territorial identification, addresses and real estate of the Czech Republic took 121.15181970596313s
Performance | Total latancy measurement for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.5751092433929443s
Amount of data | Number of triples check for Registry of territorial identification, addresses and real estate of the Czech Republic took 125.59589672088623s
Interoperability | New terms check for Registry of territorial identification, addresses and real estate of the Czech Republic took 23.956555366516113s
Versatility | Languages check for Registry of territorial identification, addresses and real estate of the Czech Republic took 300.1101989746094s
Interpretability | Number of blank nodes check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.24903488159179688s
Interpretability | RDF structures check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.39475202560424805s
Versatility | Serialization formats check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.23765349388122559s
Availability | RDF dump link check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.791466474533081s
License | MR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.14819049835205078s
License | HR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.16141247749328613s
Amount of data | Number of property check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1244659423828125s
Understandability | Number of label check for Registry of territorial identification, addresses and real estate of the Czech Republic took 4.913213729858398s
Understandability | URI regex check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.23357629776000977s
Understandability | Vocabs check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13098502159118652s
Verifiability | Authors check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1978468894958496s
Verifiability | Publishers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.19561266899108887s
Performance | Throughput check for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.522550821304321s
Amount of data | Check the number of entities for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.00013327598571777344s
Verifiability | Contribs. check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13264679908752441s
Interlinking | sameAs chians check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11163544654846191s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13332104682922363s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10809564590454102s
Timeliness | dataset update frequency check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11974716186523438s
Currency | Creation date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.24626493453979492s
Currency | Modification date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1235811710357666s
Rep.Conc. | URIs length for Registry of territorial identification, addresses and real estate of the Czech Republic took 174.61713814735413s
Interoperability | New vocabularies check for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12169265747070312s
Accuracy | Check Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12084674835205078s
Accuracy | Check Inverse Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11347293853759766s
Accuracy | Check Empty annotation labels for Registry of territorial identification, addresses and real estate of the Czech Republic took 23.047757863998413s
Accuracy | Check White space in annotation for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.223581552505493s
Accuracy | Check Datatype consistency for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.800816535949707s
Consistency | Disjoint class check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13204431533813477s
Consistency | Check Misplaced properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 110.24444937705994s
Consistency | Misplaced classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.499881982803345s
Consistency | Check Ontology hijacking for Registry of territorial identification, addresses and real estate of the Czech Republic took 43.73773121833801s
Consistency | Check Invalid usage of undefined classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.4581654071807861s
Consistency | Check Invalid usage of undefined properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 109.41756129264832s
Conciseness | Check Extensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.905099630355835s
Conciseness | Check Intensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.28436708450317383s
Security | Sign check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10317635536193848s
Availability | Check URIs Dereferenciability for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.152985334396362s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.3757121562957764s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.021243572235107422s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.915496826171875e-05s
Interoperability | Check the re-using of existing vocabs for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.6689300537109375e-06s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-ruian took 1635.9967198371887s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.9972233772277832s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.28055238723754883s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.020638704299926758s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.796287536621094e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 5.9604644775390625e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 4.569117784500122s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.4673762321472168s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007317066192626953s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.7162144184112549s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.020384788513183594s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 4.029273986816406e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-sao-check-actions took 4.834141492843628s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.45775580406188965s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.2784078121185303s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020285367965698242s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.0279159545898438e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 5.4836273193359375e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 4.800270080566406s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.10831212997436523s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.2742598056793213s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.020307540893554688s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.361701965332031e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 1.3113021850585938e-05s
INFO | --- Analysis for cz-sidc-drug-ingredients took 2.832066774368286s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.11515450477600098s
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.26068925857543945s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.020120859146118164s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.3855438232421875e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 2.808145046234131s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.11008834838867188s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.26498937606811523s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.020131587982177734s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.409385681152344e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 7.867813110351562e-06s
INFO | --- Analysis for cz-sidc-drugs took 3.7482032775878906s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.2680823802947998s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.2683827877044678s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.02049851417541504s
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.0008337497711181641s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 3.4332275390625e-05s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 5.4836273193359375e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 4.958688735961914s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.10883378982543945s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.29287004470825195s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.020192623138427734s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.266334533691406e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 2.8146166801452637s
Availability | SPARQL endpoint availability check for State funding providers took 0.10734176635742188s
Availability | VoID file availability check for State funding providers took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for State funding providers took 0.29156017303466797s
Reputation | Calculation of the PageRank for State funding providers took 0.02029561996459961s
Interlinking | Calculation of Degree of Connection for State funding providers took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for State funding providers took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for State funding providers took 3.647804260253906e-05s
Believability | Calculation of trust value for State funding providers took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 2.7954177856445312s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.10348963737487793s
Availability | VoID file availability check for Organizations active in R&D took 0.0007388591766357422s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.2595038414001465s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.020559310913085938s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0009553432464599609s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 5.054473876953125e-05s
Believability | Calculation of trust value for Organizations active in R&D took 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-organizations took 2.9717109203338623s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.1056828498840332s
Availability | VoID file availability check for R&D Programmes took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.2706024646759033s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020726680755615234s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.291534423828125e-05s
Believability | Calculation of trust value for R&D Programmes took 5.7220458984375e-06s
INFO | --- Analysis for cz-vavai-programmes took 2.8259975910186768s
Availability | SPARQL endpoint availability check for R&D Projects took 0.1131889820098877s
Availability | VoID file availability check for R&D Projects took 0.0007534027099609375s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.2715139389038086s
Reputation | Calculation of the PageRank for R&D Projects took 0.020720243453979492s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.291534423828125e-05s
Believability | Calculation of trust value for R&D Projects took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-projects took 2.8120720386505127s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.11396408081054688s
Availability | VoID file availability check for Institutional research plans took 0.0005698204040527344s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.25701212882995605s
Reputation | Calculation of the PageRank for Institutional research plans took 0.02027153968811035s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.00543212890625e-05s
Believability | Calculation of trust value for Institutional research plans took 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-research-plans took 2.7979753017425537s
Availability | SPARQL endpoint availability check for Results of R&D took 0.11156797409057617s
Availability | VoID file availability check for Results of R&D took 0.0008161067962646484s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.29192066192626953s
Reputation | Calculation of the PageRank for Results of R&D took 0.020322084426879883s
Interlinking | Calculation of Degree of Connection for Results of R&D took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.076957702636719e-05s
Believability | Calculation of trust value for Results of R&D took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-results took 2.8244292736053467s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.10942959785461426s
Availability | VoID file availability check for Tenders in R&D took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.2681424617767334s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.02021050453186035s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 3.8623809814453125e-05s
Believability | Calculation of trust value for Tenders in R&D took 4.76837158203125e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.736006498336792s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.6421892642974854s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0006494522094726562s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 157.2440745830536s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.2578151226043701s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 11.814297676086426s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 3.159487247467041s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.32359385490417s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.2905302047729492s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.12116026878356934s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.35716867446899414s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.40254950523376465s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.2770566940307617s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.6974985599517822s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 89.71872067451477s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.2020714282989502s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 0.9004795551300049s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.6529662609100342s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.2667043209075928s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.28673362731933594s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.24459457397460938s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.750741481781006s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 9.083747863769531e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.22694993019104004s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.40816569328308105s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.6779758930206299s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.24544119834899902s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.49146056175231934s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 0.6980931758880615s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 0.8175625801086426s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 79.83363819122314s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.2262578010559082s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.5998444557189941s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.6403181552886963s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 45.55377388000488s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.2499258518218994s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.627890110015869s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.8355176448822021s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 20.101486682891846s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.536464929580688s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 49.515079975128174s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.5539844036102295s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 13.759693145751953s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.844528913497925s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.22921013832092285s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 1.1701316833496094s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 8.495961427688599s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 1.5922822952270508s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.021346569061279297s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00014662742614746094s
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 8.344650268554688e-06s
INFO | --- Analysis for data-bnf-fr took 835.6969196796417s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.13089466094970703s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0006449222564697266s
Extra | Recovery of all triples for Open Data from the Italian National Research Council took 0.7462234497070312s
Performance | Total latancy measurement for Open Data from the Italian National Research Council took 0.35064244270324707s
Amount of data | Number of triples check for Open Data from the Italian National Research Council took 4.505307197570801s
Interoperability | New terms check for Open Data from the Italian National Research Council took 2.409686326980591s
Versatility | Languages check for Open Data from the Italian National Research Council took 0.07908058166503906s
Interpretability | Number of blank nodes check for Open Data from the Italian National Research Council took 0.583228349685669s
Security | Check HTTPS for Open Data from the Italian National Research Council took 0.04072690010070801s
Interpretability | RDF structures check for Open Data from the Italian National Research Council took 0.10523438453674316s
Versatility | Serialization formats check for Open Data from the Italian National Research Council took 0.1000361442565918s
Availability | RDF dump link check for Open Data from the Italian National Research Council took 0.08513092994689941s
License | MR license check for Open Data from the Italian National Research Council took 0.10145306587219238s
License | HR license check for Open Data from the Italian National Research Council took 12.030177354812622s
Amount of data | Number of property check for Open Data from the Italian National Research Council took 0.09257030487060547s
Understandability | Number of label check for Open Data from the Italian National Research Council took 3.8392698764801025s
Understandability | URI regex check for Open Data from the Italian National Research Council took 0.1741940975189209s
Understandability | Vocabs check for Open Data from the Italian National Research Council took 0.10585165023803711s
Verifiability | Authors check for Open Data from the Italian National Research Council took 0.09832930564880371s
Verifiability | Publishers check for Open Data from the Italian National Research Council took 0.09221339225769043s
Performance | Throughput check for Open Data from the Italian National Research Council took 12.030731678009033s
Amount of data | Check the number of entities for Open Data from the Italian National Research Council took 8.344650268554688e-05s
Verifiability | Contribs. check for Open Data from the Italian National Research Council took 0.08435964584350586s
Interlinking | sameAs chians check for Open Data from the Italian National Research Council took 0.08341431617736816s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.08702230453491211s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.06799769401550293s
Timeliness | dataset update frequency check for Open Data from the Italian National Research Council took 0.09027218818664551s
Currency | Creation date check for Open Data from the Italian National Research Council took 0.18494367599487305s
Currency | Modification date check for Open Data from the Italian National Research Council took 0.19812726974487305s
Rep.Conc. | URIs length for Open Data from the Italian National Research Council took 11.929595947265625s
Interoperability | New vocabularies check for Open Data from the Italian National Research Council took 2.474820375442505s
Consistency | Deprecated classes/propertiers check for Open Data from the Italian National Research Council took 0.1035456657409668s
Accuracy | Check Functional Property for Open Data from the Italian National Research Council took 0.08287215232849121s
Accuracy | Check Inverse Functional Property for Open Data from the Italian National Research Council took 0.08355069160461426s
Accuracy | Check Empty annotation labels for Open Data from the Italian National Research Council took 0.4416615962982178s
Accuracy | Check White space in annotation for Open Data from the Italian National Research Council took 0.03236699104309082s
Accuracy | Check Datatype consistency for Open Data from the Italian National Research Council took 0.027933120727539062s
Consistency | Disjoint class check for Open Data from the Italian National Research Council took 0.09666919708251953s
Consistency | Check Misplaced properties for Open Data from the Italian National Research Council took 10.697667121887207s
Consistency | Misplaced classes for Open Data from the Italian National Research Council took 0.19082379341125488s
Consistency | Check Ontology hijacking for Open Data from the Italian National Research Council took 1.7140977382659912s
Consistency | Check Invalid usage of undefined classes for Open Data from the Italian National Research Council took 1.4532725811004639s
Consistency | Check Invalid usage of undefined properties for Open Data from the Italian National Research Council took 12.327990055084229s
Conciseness | Check Extensional conciseness for Open Data from the Italian National Research Council took 0.034551382064819336s
Conciseness | Check Intensional conciseness for Open Data from the Italian National Research Council took 0.10330963134765625s
Security | Sign check for Open Data from the Italian National Research Council took 0.08664274215698242s
Availability | Check URIs Dereferenciability for Open Data from the Italian National Research Council took 651.5433325767517s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.848517894744873s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.02119135856628418s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 8.559226989746094e-05s
Interoperability | Check the re-using of existing vocabs for Open Data from the Italian National Research Council took 3.171055555343628s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 5.9604644775390625e-06s
INFO | --- Analysis for data-cnr-it took 761.8435702323914s
Availability | SPARQL endpoint availability check for Data.gov took 1.446385383605957s
Availability | VoID file availability check for Data.gov took 0.0007205009460449219s
Completeness | Calculation of interlinking completeness for Data.gov took 0.7154738903045654s
Reputation | Calculation of the PageRank for Data.gov took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for Data.gov took 2.9802322387695312e-05s
Believability | Calculation of trust value for Data.gov took 6.198883056640625e-06s
INFO | --- Analysis for data-gov took 20.5382981300354s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.1851367950439453s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.2892589569091797s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.020324230194091797s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 6.771087646484375e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 5.4836273193359375e-06s
INFO | --- Analysis for data-gov-ie took 2.7557613849639893s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 4.315376281738281e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.2753722667694092s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.033348083496094e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 3.7670135498046875e-05s
INFO | --- Analysis for data-gov-uk-time-intervals took 3.5316243171691895s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 21.996923446655273s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0007596015930175781s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.7198092937469482s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.020730972290039062s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 7.343292236328125e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 7.3909759521484375e-06s
INFO | --- Analysis for data-hnm-hu took 168.18327450752258s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.10455751419067383s
Availability | VoID file availability check for Climb Dataincubator took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.6770915985107422s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.020779132843017578s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.605552673339844e-05s
Believability | Calculation of trust value for Climb Dataincubator took 7.62939453125e-06s
INFO | --- Analysis for data-incubator-climb took 2.9037551879882812s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.05515599250793457s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.29538798332214355s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.020153045654296875s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.0067901611328125e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 5.0067901611328125e-06s
INFO | --- Analysis for data-incubator-metoffice took 5.69191575050354s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.060343265533447266s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.28397560119628906s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.020378828048706055s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.96453857421875e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 9.059906005859375e-06s
INFO | --- Analysis for data-incubator-moseley took 10.047898530960083s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.05220174789428711s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0003008842468261719s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.25040411949157715s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.020333290100097656s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 0.0001049041748046875s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 8.106231689453125e-06s
INFO | --- Analysis for data-incubator-musicbrainz took 2.914574146270752s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.7572557926177979s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0008230209350585938s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.26799607276916504s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.020221233367919922s
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.0007290840148925781s
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 5.245208740234375e-06s
INFO | --- Analysis for data-incubator-nasa took 9.768401622772217s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.05520820617675781s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.2719259262084961s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.020204544067382812s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.343292236328125e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 7.62939453125e-06s
INFO | --- Analysis for data-incubator-our-airports took 2.560157299041748s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.06816482543945312s
Availability | VoID file availability check for Pokedex data in RDF took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.2603886127471924s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.021303653717041016s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.846687316894531e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 6.198883056640625e-06s
INFO | --- Analysis for data-incubator-pokedex took 4.25189995765686s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.05155777931213379s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.28328680992126465s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.020233869552612305s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 8.678436279296875e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 8.106231689453125e-06s
INFO | --- Analysis for data-incubator-smcjournals took 2.531766653060913s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.497389554977417s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0006399154663085938s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 106.63279223442078s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 1.319946527481079s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 17.113048315048218s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.6824891567230225s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.307743787765503s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.309746503829956s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.3320026397705078s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.34098339080810547s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.3694601058959961s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.3503744602203369s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.3717963695526123s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.319084644317627s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 1.3163976669311523s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 30.342984914779663s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 0.7857804298400879s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.3645799160003662s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.3907163143157959s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.47414088249206543s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 12.478445768356323s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 0.00010752677917480469s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.3843047618865967s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.6141853332519531s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.41361021995544434s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.3693993091583252s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.4239692687988281s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.8291120529174805s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.769599437713623s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 54.29416084289551s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.35392236709594727s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.3007664680480957s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.37529683113098145s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 48.323986530303955s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 3.005686044692993s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.079611301422119s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.8230226039886475s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 0.8378450870513916s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 7.9379472732543945s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 31.01874327659607s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.4943656921386719s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.8248469829559326s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 2.8427023887634277s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.5205798149108887s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.4303610324859619s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 0.12208318710327148s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.39290642738342285s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.020290374755859375s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 6.318092346191406e-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.867813110351562e-06s
INFO | --- Analysis for data-open-ac-uk took 692.0224297046661s
Availability | SPARQL endpoint availability check for Persée in RDF took 1.0611662864685059s
Availability | VoID file availability check for Persée in RDF took 0.00067138671875s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.7012579441070557s
Reputation | Calculation of the PageRank for Persée in RDF took 0.020353317260742188s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00010037422180175781s
Believability | Calculation of trust value for Persée in RDF took 7.867813110351562e-06s
INFO | --- Analysis for data-persee-fr took 8.699630498886108s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 0.00010561943054199219s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.28212428092956543s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.02027106285095215s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 3.147125244140625e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 6.9141387939453125e-06s
INFO | --- Analysis for data-southampton-ac-uk took 3.90810489654541s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.5309860706329346s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0006647109985351562s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.26922059059143066s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.020513534545898438s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011420249938964844s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 7.3909759521484375e-06s
INFO | --- Analysis for data-szepmuveszeti-hu took 9.660639762878418s
Availability | SPARQL endpoint availability check for DataFAQs took 6.747245788574219e-05s
Availability | VoID file availability check for DataFAQs took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.7043654918670654s
Reputation | Calculation of the PageRank for DataFAQs took 0.020446300506591797s
Interlinking | Calculation of Degree of Connection for DataFAQs took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DataFAQs took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 3.075599670410156e-05s
Believability | Calculation of trust value for DataFAQs took 6.67572021484375e-06s
INFO | --- Analysis for datafaqs took 4.738476991653442s
Availability | SPARQL endpoint availability check for datahub took 4.267692565917969e-05s
Availability | VoID file availability check for datahub took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for datahub took 0.27539753913879395s
Reputation | Calculation of the PageRank for datahub took 0.02034592628479004s
Interlinking | Calculation of Degree of Connection for datahub took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for datahub took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for datahub took 5.2928924560546875e-05s
Believability | Calculation of trust value for datahub took 7.3909759521484375e-06s
INFO | --- Analysis for datahub took 7.011337757110596s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.36042165756225586s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0012371540069580078s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.2674863338470459s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.020263671875s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.033348083496094e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 8.344650268554688e-06s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 5.1224141120910645s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.42242193222046s
Availability | VoID file availability check for datos-artium-org took 0.0007698535919189453s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.42168641090393066s
Reputation | Calculation of the PageRank for datos-artium-org took 0.020600557327270508s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00011610984802246094s
Believability | Calculation of trust value for datos-artium-org took 7.62939453125e-06s
INFO | --- Analysis for datos-artium-org took 165.51610946655273s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.8648250102996826s
Availability | VoID file availability check for Datos.bcn.cl took 0.0007214546203613281s
Extra | Recovery of all triples for Datos.bcn.cl took 68.3779046535492s
Performance | Total latancy measurement for Datos.bcn.cl took 6.024965763092041s
Amount of data | Number of triples check for Datos.bcn.cl took 5.871673822402954s
Interoperability | New terms check for Datos.bcn.cl took 3.8858461380004883s
Versatility | Languages check for Datos.bcn.cl took 301.0230984687805s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.3298265933990479s
Security | Check HTTPS for Datos.bcn.cl took 0.7159008979797363s
Interpretability | RDF structures check for Datos.bcn.cl took 1.326249599456787s
Versatility | Serialization formats check for Datos.bcn.cl took 1.2806153297424316s
Availability | RDF dump link check for Datos.bcn.cl took 1.1905887126922607s
License | MR license check for Datos.bcn.cl took 1.2011871337890625s
License | HR license check for Datos.bcn.cl took 31.65594744682312s
Amount of data | Number of property check for Datos.bcn.cl took 4.241765022277832s
Understandability | Number of label check for Datos.bcn.cl took 1.721869707107544s
Understandability | URI regex check for Datos.bcn.cl took 2.409364938735962s
Understandability | Vocabs check for Datos.bcn.cl took 1.2146575450897217s
Verifiability | Authors check for Datos.bcn.cl took 1.2164766788482666s
Verifiability | Publishers check for Datos.bcn.cl took 1.2092819213867188s
Performance | Throughput check for Datos.bcn.cl took 12.04304838180542s
Amount of data | Check the number of entities for Datos.bcn.cl took 3.170967102050781e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.2147152423858643s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.2051920890808105s
Interlinking | skos check for Datos.bcn.cl took 1.2334990501403809s
Interlinking | skos check for Datos.bcn.cl took 1.1963934898376465s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.241502285003662s
Currency | Creation date check for Datos.bcn.cl took 2.4566030502319336s
Currency | Modification date check for Datos.bcn.cl took 1.2285635471343994s
Rep.Conc. | URIs length for Datos.bcn.cl took 55.84192490577698s
Interoperability | New vocabularies check for Datos.bcn.cl took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.2912249565124512s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.204735517501831s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.2148380279541016s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 25.75901460647583s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.23985743522644043s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.2676255702972412s
Consistency | Disjoint class check for Datos.bcn.cl took 1.2125332355499268s
Consistency | Check Misplaced properties for Datos.bcn.cl took 7.1542441844940186s
Consistency | Misplaced classes for Datos.bcn.cl took 2.0506269931793213s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 23.672173023223877s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.3860349655151367s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 7.856589317321777s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.3033623695373535s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.45078444480896s
Security | Sign check for Datos.bcn.cl took 1.2058501243591309s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 10.20345687866211s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 1.296220302581787s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.02052140235900879s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 7.319450378417969e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.6689300537109375e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 5.245208740234375e-06s
INFO | --- Analysis for datos-bcn-cl took 1237.4358625411987s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.32073140144348145s
Availability | VoID file availability check for datos.bne.es took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.7017245292663574s
Reputation | Calculation of the PageRank for datos.bne.es took 0.020444869995117188s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011038780212402344s
Believability | Calculation of trust value for datos.bne.es took 1.3113021850585938e-05s
INFO | --- Analysis for datos-bne-es took 6.284371614456177s
Availability | SPARQL endpoint availability check for DBkWik took 0.40956926345825195s
Availability | VoID file availability check for DBkWik took 0.0006611347198486328s
Extra | Recovery of all triples for DBkWik took 2.77839732170105s
Performance | Total latancy measurement for DBkWik took 0.44464588165283203s
Amount of data | Number of triples check for DBkWik took 3.798063039779663s
Interoperability | New terms check for DBkWik took 2.260883331298828s
Versatility | Languages check for DBkWik took 62.819828510284424s
Interpretability | Number of blank nodes check for DBkWik took 0.17325949668884277s
Interpretability | RDF structures check for DBkWik took 0.44583868980407715s
Versatility | Serialization formats check for DBkWik took 0.267136812210083s
Availability | RDF dump link check for DBkWik took 3.3288516998291016s
License | MR license check for DBkWik took 2.4232349395751953s
License | HR license check for DBkWik took 61.28815841674805s
Amount of data | Number of property check for DBkWik took 0.6170370578765869s
Understandability | Number of label check for DBkWik took 67.62554216384888s
Understandability | URI regex check for DBkWik took 0.7485735416412354s
Understandability | Vocabs check for DBkWik took 0.13063263893127441s
Verifiability | Authors check for DBkWik took 0.16750097274780273s
Verifiability | Publishers check for DBkWik took 0.0875542163848877s
Performance | Throughput check for DBkWik took 10.393650770187378s
Amount of data | Check the number of entities for DBkWik took 7.2479248046875e-05s
Verifiability | Contribs. check for DBkWik took 0.7740061283111572s
Interlinking | sameAs chians check for DBkWik took 0.42190051078796387s
Interlinking | skos check for DBkWik took 0.5229828357696533s
Interlinking | skos check for DBkWik took 0.0760958194732666s
Timeliness | dataset update frequency check for DBkWik took 0.21878767013549805s
Currency | Creation date check for DBkWik took 0.5017602443695068s
Currency | Modification date check for DBkWik took 0.24009418487548828s
Rep.Conc. | URIs length for DBkWik took 12.235140800476074s
Interoperability | New vocabularies check for DBkWik took 2.4155945777893066s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.10656332969665527s
Accuracy | Check Functional Property for DBkWik took 0.2450265884399414s
Accuracy | Check Inverse Functional Property for DBkWik took 0.22141551971435547s
Accuracy | Check Empty annotation labels for DBkWik took 0.6326742172241211s
Accuracy | Check White space in annotation for DBkWik took 0.02333855628967285s
Accuracy | Check Datatype consistency for DBkWik took 0.0379488468170166s
Consistency | Disjoint class check for DBkWik took 0.10914087295532227s
Consistency | Check Misplaced properties for DBkWik took 11.88362741470337s
Consistency | Misplaced classes for DBkWik took 0.7210359573364258s
Consistency | Check Ontology hijacking for DBkWik took 1.9809114933013916s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.361999273300171s
Consistency | Check Invalid usage of undefined properties for DBkWik took 11.845225095748901s
Conciseness | Check Extensional conciseness for DBkWik took 0.032842397689819336s
Conciseness | Check Intensional conciseness for DBkWik took 0.962796688079834s
Security | Sign check for DBkWik took 0.21113920211791992s
Availability | Check URIs Dereferenciability for DBkWik took 10.817945718765259s
Completeness | Calculation of interlinking completeness for DBkWik took 0.3305392265319824s
Reputation | Calculation of the PageRank for DBkWik took 0.02098560333251953s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for DBkWik took 7.104873657226562e-05s
Interoperability | Check the re-using of existing vocabs for DBkWik took 3.245586633682251s
Believability | Calculation of trust value for DBkWik took 9.059906005859375e-06s
INFO | --- Analysis for dbkwik took 1409.7851004600525s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 7.510185241699219e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.2710592746734619s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.020714759826660156s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00011754035949707031s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 7.3909759521484375e-06s
INFO | --- Analysis for dblp-deusto-gnoss took 6.611110210418701s
Availability | SPARQL endpoint availability check for dbnary took 0.2550053596496582s
Availability | VoID file availability check for dbnary took 0.0005390644073486328s
Extra | Recovery of all triples for dbnary took 2.505955457687378s
Performance | Total latancy measurement for dbnary took 0.40413498878479004s
Amount of data | Number of triples check for dbnary took 1.2046542167663574s
Interoperability | New terms check for dbnary took 3.7168354988098145s
Versatility | Languages check for dbnary took 60.702593088150024s
Interpretability | Number of blank nodes check for dbnary took 3.488779306411743s
Security | Check HTTPS for dbnary took 0.1607666015625s
Interpretability | RDF structures check for dbnary took 0.15366506576538086s
Versatility | Serialization formats check for dbnary took 0.7391774654388428s
Availability | RDF dump link check for dbnary took 0.07316255569458008s
License | MR license check for dbnary took 0.10440254211425781s
License | HR license check for dbnary took 61.73983430862427s
Amount of data | Number of property check for dbnary took 0.13847017288208008s
Understandability | Number of label check for dbnary took 1.3983402252197266s
Understandability | URI regex check for dbnary took 0.13982057571411133s
Understandability | Vocabs check for dbnary took 0.6774942874908447s
Verifiability | Authors check for dbnary took 0.10673379898071289s
Verifiability | Publishers check for dbnary took 0.0741875171661377s
Performance | Throughput check for dbnary took 10.390240669250488s
Amount of data | Check the number of entities for dbnary took 7.081031799316406e-05s
Verifiability | Contribs. check for dbnary took 0.08047699928283691s
Interlinking | sameAs chians check for dbnary took 0.10334944725036621s
Interlinking | skos check for dbnary took 0.6824073791503906s
Interlinking | skos check for dbnary took 0.08165168762207031s
Timeliness | dataset update frequency check for dbnary took 0.4087200164794922s
Currency | Creation date check for dbnary took 0.1843128204345703s
Currency | Modification date check for dbnary took 0.16218304634094238s
Rep.Conc. | URIs length for dbnary took 11.38010573387146s
Interoperability | New vocabularies check for dbnary took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for dbnary took 0.09425067901611328s
Accuracy | Check Functional Property for dbnary took 0.16910481452941895s
Accuracy | Check Inverse Functional Property for dbnary took 0.14379024505615234s
Accuracy | Check Empty annotation labels for dbnary took 1.2799062728881836s
Accuracy | Check White space in annotation for dbnary took 0.025238990783691406s
Accuracy | Check Datatype consistency for dbnary took 0.031453609466552734s
Consistency | Disjoint class check for dbnary took 0.09867095947265625s
Consistency | Check Misplaced properties for dbnary took 8.808080434799194s
Consistency | Misplaced classes for dbnary took 0.22116303443908691s
Consistency | Check Ontology hijacking for dbnary took 1.9570567607879639s
Consistency | Check Invalid usage of undefined classes for dbnary took 1.2970011234283447s
Consistency | Check Invalid usage of undefined properties for dbnary took 9.943628787994385s
Conciseness | Check Extensional conciseness for dbnary took 0.037012577056884766s
Conciseness | Check Intensional conciseness for dbnary took 0.23208951950073242s
Security | Sign check for dbnary took 0.39238762855529785s
Availability | Check URIs Dereferenciability for dbnary took 4694.6406672000885s
Completeness | Calculation of interlinking completeness for dbnary took 1.7474441528320312s
Reputation | Calculation of the PageRank for dbnary took 0.020958423614501953s
Interlinking | Calculation of Degree of Connection for dbnary took 2.8848648071289062e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for dbnary took 5.316734313964844e-05s
Interoperability | Check the re-using of existing vocabs for dbnary took 1.6689300537109375e-06s
Believability | Calculation of trust value for dbnary took 7.3909759521484375e-06s
INFO | --- Analysis for dbnary took 4913.300642967224s
Availability | SPARQL endpoint availability check for DBpedia took 2.7065792083740234s
Availability | VoID file availability check for DBpedia took 0.0005385875701904297s
Extra | Recovery of all triples for DBpedia took 6.5440592765808105s
Performance | Total latancy measurement for DBpedia took 0.911196231842041s
Amount of data | Number of triples check for DBpedia took 1.495671272277832s
Interoperability | New terms check for DBpedia took 5.68099045753479s
Versatility | Languages check for DBpedia took 31.989521026611328s
Interpretability | Number of blank nodes check for DBpedia took 0.20239925384521484s
Security | Check HTTPS for DBpedia took 0.12294673919677734s
Interpretability | RDF structures check for DBpedia took 0.9209778308868408s
Versatility | Serialization formats check for DBpedia took 0.2626528739929199s
Availability | RDF dump link check for DBpedia took 0.46872925758361816s
License | MR license check for DBpedia took 0.2108595371246338s
License | HR license check for DBpedia took 37.46385622024536s
Amount of data | Number of property check for DBpedia took 5.589430570602417s
Understandability | Number of label check for DBpedia took 9.712670803070068s
Understandability | URI regex check for DBpedia took 3.8731460571289062s
Understandability | Vocabs check for DBpedia took 0.6060516834259033s
Verifiability | Authors check for DBpedia took 0.2756175994873047s
Verifiability | Publishers check for DBpedia took 0.2763831615447998s
Performance | Throughput check for DBpedia took 10.952400207519531s
Amount of data | Check the number of entities for DBpedia took 7.271766662597656e-05s
Verifiability | Contribs. check for DBpedia took 0.231736421585083s
Interlinking | sameAs chians check for DBpedia took 5.000890493392944s
Interlinking | skos check for DBpedia took 0.21960234642028809s
Interlinking | skos check for DBpedia took 0.16249990463256836s
Timeliness | dataset update frequency check for DBpedia took 0.2054140567779541s
Currency | Creation date check for DBpedia took 0.44619083404541016s
Currency | Modification date check for DBpedia took 0.4662289619445801s
Rep.Conc. | URIs length for DBpedia took 38.010183572769165s
Interoperability | New vocabularies check for DBpedia took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.20406317710876465s
Accuracy | Check Functional Property for DBpedia took 0.3013641834259033s
Accuracy | Check Inverse Functional Property for DBpedia took 0.2824137210845947s
Accuracy | Check Empty annotation labels for DBpedia took 11.39595627784729s
Accuracy | Check White space in annotation for DBpedia took 0.03075718879699707s
Accuracy | Check Datatype consistency for DBpedia took 0.028440475463867188s
Consistency | Disjoint class check for DBpedia took 0.18591904640197754s
Consistency | Check Misplaced properties for DBpedia took 38.09076380729675s
Consistency | Misplaced classes for DBpedia took 2.1163766384124756s
Consistency | Check Ontology hijacking for DBpedia took 2.3757665157318115s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.3468570709228516s
Consistency | Check Invalid usage of undefined properties for DBpedia took 1.903482437133789s
Conciseness | Check Extensional conciseness for DBpedia took 0.03396344184875488s
Conciseness | Check Intensional conciseness for DBpedia took 1.1004540920257568s
Security | Sign check for DBpedia took 0.2230520248413086s
Availability | Check URIs Dereferenciability for DBpedia took 5688.195467948914s
Completeness | Calculation of interlinking completeness for DBpedia took 0.6540272235870361s
Reputation | Calculation of the PageRank for DBpedia took 0.020822763442993164s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0009019374847412109s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBpedia took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia took 6098.863946437836s
Availability | SPARQL endpoint availability check for DBpedia Commons took 6.1901469230651855s
Availability | VoID file availability check for DBpedia Commons took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.6913163661956787s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.0205533504486084s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 6.818771362304688e-05s
Believability | Calculation of trust value for DBpedia Commons took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-commons took 16.449522018432617s
Availability | SPARQL endpoint availability check for DBpedia in German took 5.269050598144531e-05s
Availability | VoID file availability check for DBpedia in German took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.27568507194519043s
Reputation | Calculation of the PageRank for DBpedia in German took 0.020867109298706055s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 7.176399230957031e-05s
Believability | Calculation of trust value for DBpedia in German took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-de took 3.8779001235961914s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 10.972819566726685s
Availability | VoID file availability check for DBpedia in Greek took 0.0007114410400390625s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.26976728439331055s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.02071380615234375s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00021076202392578125s
Believability | Calculation of trust value for DBpedia in Greek took 6.198883056640625e-06s
INFO | --- Analysis for dbpedia-el took 47.714306116104126s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 30.38621997833252s
Availability | VoID file availability check for DBpedia in Spanish took 0.0007383823394775391s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.2713446617126465s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.02058553695678711s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00010347366333007812s
Believability | Calculation of trust value for DBpedia in Spanish took 4.5299530029296875e-06s
INFO | --- Analysis for dbpedia-es took 84.71481394767761s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.2748751640319824s
Availability | VoID file availability check for DBpedia in Basque took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.2501041889190674s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.020743370056152344s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.218650817871094e-05s
Believability | Calculation of trust value for DBpedia in Basque took 5.245208740234375e-06s
INFO | --- Analysis for dbpedia-eu took 8.339596033096313s
Availability | SPARQL endpoint availability check for DBpedia in French took 0.16505718231201172s
Availability | VoID file availability check for DBpedia in French took 0.0006513595581054688s
Extra | Recovery of all triples for DBpedia in French took 91.48494696617126s
Performance | Total latancy measurement for DBpedia in French took 0.416980504989624s
Amount of data | Number of triples check for DBpedia in French took 1.5032410621643066s
Interoperability | New terms check for DBpedia in French took 2.2436439990997314s
Versatility | Languages check for DBpedia in French took 300.082941532135s
Interpretability | Number of blank nodes check for DBpedia in French took 0.15508222579956055s
Security | Check HTTPS for DBpedia in French took 0.1690826416015625s
Interpretability | RDF structures check for DBpedia in French took 0.5309090614318848s
Versatility | Serialization formats check for DBpedia in French took 0.284837007522583s
Availability | RDF dump link check for DBpedia in French took 6.605470180511475s
License | MR license check for DBpedia in French took 0.9499690532684326s
License | HR license check for DBpedia in French took 87.41007423400879s
Amount of data | Number of property check for DBpedia in French took 0.10248994827270508s
Understandability | Number of label check for DBpedia in French took 3.2725512981414795s
Understandability | URI regex check for DBpedia in French took 0.36641669273376465s
Understandability | Vocabs check for DBpedia in French took 0.13306570053100586s
Verifiability | Authors check for DBpedia in French took 0.416731595993042s
Verifiability | Publishers check for DBpedia in French took 0.16007375717163086s
Performance | Throughput check for DBpedia in French took 10.406151056289673s
Amount of data | Check the number of entities for DBpedia in French took 2.124866485595703s
Verifiability | Contribs. check for DBpedia in French took 0.14045166969299316s
Interlinking | sameAs chians check for DBpedia in French took 0.46077394485473633s
Interlinking | skos check for DBpedia in French took 0.19927501678466797s
Interlinking | skos check for DBpedia in French took 0.06958436965942383s
Timeliness | dataset update frequency check for DBpedia in French took 0.5543475151062012s
Currency | Creation date check for DBpedia in French took 0.2631070613861084s
Currency | Modification date check for DBpedia in French took 0.20733356475830078s
Rep.Conc. | URIs length for DBpedia in French took 40.404772996902466s
Interoperability | New vocabularies check for DBpedia in French took 8.409907579421997s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 0.09877252578735352s
Accuracy | Check Functional Property for DBpedia in French took 0.1258101463317871s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.12766218185424805s
Accuracy | Check Empty annotation labels for DBpedia in French took 29.342339992523193s
Accuracy | Check White space in annotation for DBpedia in French took 3.0877625942230225s
Accuracy | Check Datatype consistency for DBpedia in French took 2.6168923377990723s
Consistency | Disjoint class check for DBpedia in French took 0.2621135711669922s
Consistency | Check Misplaced properties for DBpedia in French took 7.4675304889678955s
Consistency | Misplaced classes for DBpedia in French took 9.22074294090271s
Consistency | Check Ontology hijacking for DBpedia in French took 23.930440425872803s
Consistency | Check Invalid usage of undefined classes for DBpedia in French took 1.4188528060913086s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 10.138618230819702s
Conciseness | Check Extensional conciseness for DBpedia in French took 3.038863182067871s
Conciseness | Check Intensional conciseness for DBpedia in French took 1.148442029953003s
Security | Sign check for DBpedia in French took 0.1147928237915039s
Availability | Check URIs Dereferenciability for DBpedia in French took 1053.0803990364075s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.5664477348327637s
Reputation | Calculation of the PageRank for DBpedia in French took 0.021503210067749023s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.00014781951904296875s
Interoperability | Check the re-using of existing vocabs for DBpedia in French took 8.457908630371094s
Believability | Calculation of trust value for DBpedia in French took 6.4373016357421875e-06s
INFO | --- Analysis for dbpedia-fr took 1838.4782478809357s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.9496214389801025s
Availability | VoID file availability check for DBpedia in Japanese took 4.056589841842651s
Extra | Recovery of all triples for DBpedia in Japanese took 5.506218433380127s
Performance | Total latancy measurement for DBpedia in Japanese took 6.658735036849976s
Amount of data | Number of triples check for DBpedia in Japanese took 35.91473150253296s
Interoperability | New terms check for DBpedia in Japanese took 18.605997562408447s
Versatility | Languages check for DBpedia in Japanese took 1.3280105590820312s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.3354792594909668s
Security | Check HTTPS for DBpedia in Japanese took 0.799013614654541s
Interpretability | RDF structures check for DBpedia in Japanese took 1.3801724910736084s
Versatility | Serialization formats check for DBpedia in Japanese took 1.3375742435455322s
Availability | RDF dump link check for DBpedia in Japanese took 1.342585802078247s
License | MR license check for DBpedia in Japanese took 1.3512227535247803s
License | HR license check for DBpedia in Japanese took 61.318822145462036s
Amount of data | Number of property check for DBpedia in Japanese took 1.3459722995758057s
Understandability | Number of label check for DBpedia in Japanese took 39.77216339111328s
Understandability | URI regex check for DBpedia in Japanese took 2.6812918186187744s
Understandability | Vocabs check for DBpedia in Japanese took 1.3346507549285889s
Verifiability | Authors check for DBpedia in Japanese took 1.3462333679199219s
Verifiability | Publishers check for DBpedia in Japanese took 1.3404221534729004s
Performance | Throughput check for DBpedia in Japanese took 13.248111724853516s
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.3495895862579346s
Interlinking | sameAs chians check for DBpedia in Japanese took 3.0196645259857178s
Interlinking | skos check for DBpedia in Japanese took 1.3898768424987793s
Interlinking | skos check for DBpedia in Japanese took 1.3416411876678467s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.3529918193817139s
Currency | Creation date check for DBpedia in Japanese took 2.6649563312530518s
Currency | Modification date check for DBpedia in Japanese took 2.685727596282959s
Rep.Conc. | URIs length for DBpedia in Japanese took 80.0943694114685s
Interoperability | New vocabularies check for DBpedia in Japanese took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.3389110565185547s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.03207039833068848s
Consistency | Disjoint class check for DBpedia in Japanese took 1.3256168365478516s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 4.328096389770508s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.3621454238891602s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 94.17387962341309s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.0337984561920166s
Conciseness | Check Intensional conciseness for DBpedia in Japanese took 3.2501397132873535s
Security | Sign check for DBpedia in Japanese took 1.3654284477233887s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 14.752567529678345s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 1.2236998081207275s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.020827770233154297s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00010991096496582031s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 1.6689300537109375e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia-ja took 924.677383184433s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.4345855712890625e-05s
Availability | VoID file availability check for dbpedia lite took 0.0006327629089355469s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.2756962776184082s
Reputation | Calculation of the PageRank for dbpedia lite took 0.020418405532836914s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.00010061264038085938s
Believability | Calculation of trust value for dbpedia lite took 5.0067901611328125e-06s
INFO | --- Analysis for dbpedia-lite took 24.686143398284912s
Availability | SPARQL endpoint availability check for DBpedia-Live took 3.981590270996094e-05s
Availability | VoID file availability check for DBpedia-Live took 0.0003097057342529297s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.29266905784606934s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.020122289657592773s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 2.9087066650390625e-05s
Believability | Calculation of trust value for DBpedia-Live took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-live took 3.8038177490234375s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.26574182510375977s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.2711496353149414s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.02044534683227539s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.000202178955078125s
Believability | Calculation of trust value for DBpedia in Dutch took 5.9604644775390625e-06s
INFO | --- Analysis for dbpedia-nl took 3.6244571208953857s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 11.697946548461914s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0006327629089355469s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.2789499759674072s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.020300865173339844s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.678436279296875e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 7.867813110351562e-06s
INFO | --- Analysis for dbpedia-pt took 43.75298833847046s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 4.0531158447265625e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.2613377571105957s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.020298004150390625s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 2.8848648071289062e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 3.0517578125e-05s
INFO | --- Analysis for dbpedia-spotlight took 2.9565961360931396s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.3392181396484375e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.279557466506958s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.020395755767822266s
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.0007436275482177734s
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.3909759521484375e-06s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 14.390967845916748s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 4.172325134277344e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.27596449851989746s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.020474672317504883s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 3.0994415283203125e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 7.867813110351562e-06s
INFO | --- Analysis for dbpedia-wikidata took 3.279247760772705s
Availability | SPARQL endpoint availability check for DBpedia took 4.267692565917969e-05s
Availability | VoID file availability check for DBpedia took 0.0002951622009277344s
Completeness | Calculation of interlinking completeness for DBpedia took 0.2918055057525635s
Reputation | Calculation of the PageRank for DBpedia took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for DBpedia took 3.170967102050781e-05s
Believability | Calculation of trust value for DBpedia took 7.62939453125e-06s
INFO | --- Analysis for dbpedia_ took 2.9540324211120605s
Availability | SPARQL endpoint availability check for DBTropes took 4.3392181396484375e-05s
Availability | VoID file availability check for DBTropes took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for DBTropes took 0.2708728313446045s
Reputation | Calculation of the PageRank for DBTropes took 0.020522117614746094s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.369850158691406e-05s
Believability | Calculation of trust value for DBTropes took 1.2636184692382812e-05s
INFO | --- Analysis for dbtropes took 3.575474977493286s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 4.291534423828125e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.2731895446777344s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.020483732223510742s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 3.814697265625e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 7.867813110351562e-06s
INFO | --- Analysis for dbtune took 2.9136197566986084s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 4.291534423828125e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.27005767822265625s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.020354032516479492s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.4836273193359375e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 6.67572021484375e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 8.561375141143799s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 4.363059997558594e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.2616403102874756s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.020183324813842773s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.361701965332031e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 8.106231689453125e-06s
INFO | --- Analysis for dbtune-audioscrobbler took 6.003614187240601s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 6.879491567611694s
Availability | VoID file availability check for DBTune.org/classical took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.26884913444519043s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.020241975784301758s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.414817810058594e-05s
Believability | Calculation of trust value for DBTune.org/classical took 7.867813110351562e-06s
INFO | --- Analysis for dbtune-classical took 22.44618320465088s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 8.383564710617065s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.27263784408569336s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.02066183090209961s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 8.344650268554688e-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.922681093215942s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 8.350177526473999s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.2591586112976074s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.020725488662719727s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.866455078125e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 7.62939453125e-06s
INFO | --- Analysis for dbtune-magnatune took 24.526833057403564s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 8.324911832809448s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.287703275680542s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.020280122756958008s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00010800361633300781s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-musicbrainz took 23.955393314361572s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 8.286930799484253s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.28473353385925293s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.020776987075805664s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.3882598876953125e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 6.4373016357421875e-06s
INFO | --- Analysis for dbtune-myspace took 17.855807065963745s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 4.076957702636719e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.27134060859680176s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.020494937896728516s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 3.123283386230469e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 1.6927719116210938e-05s
INFO | --- Analysis for dclg-openuplabs took 2.9261765480041504s
Availability | SPARQL endpoint availability check for data.dcs took 4.291534423828125e-05s
Availability | VoID file availability check for data.dcs took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for data.dcs took 0.27451062202453613s
Reputation | Calculation of the PageRank for data.dcs took 0.020513057708740234s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.818771362304688e-05s
Believability | Calculation of trust value for data.dcs took 7.3909759521484375e-06s
INFO | --- Analysis for dcs-sheffield took 2.608198404312134s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 4.363059997558594e-05s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.27559471130371094s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.020276546478271484s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 3.0994415283203125e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 7.152557373046875e-06s
INFO | --- Analysis for de-budget took 2.853538990020752s
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.0004971027374267578s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.2544376850128174s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.0203249454498291s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.981590270996094e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 7.867813110351562e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.4306480884552s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 4.410743713378906e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0008208751678466797s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.27062225341796875s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.020664215087890625s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 5.1021575927734375e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 7.3909759521484375e-06s
INFO | --- Analysis for debian-package-tracking-system took 4.651824474334717s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 4.2438507080078125e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.00033092498779296875s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.2498633861541748s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.020749807357788086s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 3.314018249511719e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 6.198883056640625e-06s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 2.9286322593688965s
Availability | SPARQL endpoint availability check for Demografie took 4.291534423828125e-05s
Availability | VoID file availability check for Demografie took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for Demografie took 0.2550978660583496s
Reputation | Calculation of the PageRank for Demografie took 0.020666837692260742s
Interlinking | Calculation of Degree of Connection for Demografie took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Demografie took 3.457069396972656e-05s
Believability | Calculation of trust value for Demografie took 7.3909759521484375e-06s
INFO | --- Analysis for demografie took 2.921329975128174s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.4345855712890625e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.2657148838043213s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.020856618881225586s
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.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 0.00010085105895996094s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 6.9141387939453125e-06s
INFO | --- Analysis for deustoentrepreneurship took 5.060702800750732s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 8.749961853027344e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.2533302307128906s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.02060723304748535s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00010514259338378906s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 9.298324584960938e-06s
INFO | --- Analysis for deustotech took 4.796116352081299s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.5343577861785889s
Availability | VoID file availability check for Deutsche Biographie took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.2610645294189453s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.02063918113708496s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 3.8623809814453125e-05s
Believability | Calculation of trust value for Deutsche Biographie took 7.152557373046875e-06s
INFO | --- Analysis for deutsche-biographie took 4.2226386070251465s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 4.458427429199219e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0007059574127197266s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.26973533630371094s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.020877838134765625s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.793571472167969e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 7.3909759521484375e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 7.271413087844849s
Availability | SPARQL endpoint availability check for dev8d took 4.696846008300781e-05s
Availability | VoID file availability check for dev8d took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for dev8d took 0.27744531631469727s
Reputation | Calculation of the PageRank for dev8d took 0.02055644989013672s
Interlinking | Calculation of Degree of Connection for dev8d took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.842613220214844e-05s
Believability | Calculation of trust value for dev8d took 7.152557373046875e-06s
INFO | --- Analysis for dev8d took 2.9655754566192627s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.170190811157227s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0007762908935546875s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.28139662742614746s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.0207211971282959s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 5.7220458984375e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 6.4373016357421875e-06s
INFO | --- Analysis for dewey_decimal_classification took 92.78189468383789s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 4.124641418457031e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.283977746963501s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.020433902740478516s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 3.123283386230469e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 6.9141387939453125e-06s
INFO | --- Analysis for diachronic-ontologies-peoples-daily took 2.868589162826538s
Availability | SPARQL endpoint availability check for Diavgeia took 4.363059997558594e-05s
Availability | VoID file availability check for Diavgeia took 0.0007274150848388672s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.25584912300109863s
Reputation | Calculation of the PageRank for Diavgeia took 0.020548343658447266s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.654594421386719e-05s
Believability | Calculation of trust value for Diavgeia took 4.76837158203125e-06s
INFO | --- Analysis for diavgeia took 5.544925212860107s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.410743713378906e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.25552988052368164s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.02209949493408203s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0010640621185302734s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0001583099365234375s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 7.62939453125e-06s
INFO | --- Analysis for didactalia took 16.207845211029053s
Availability | SPARQL endpoint availability check for diigo.feed took 4.076957702636719e-05s
Availability | VoID file availability check for diigo.feed took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.25168895721435547s
Reputation | Calculation of the PageRank for diigo.feed took 0.020627498626708984s
Interlinking | Calculation of Degree of Connection for diigo.feed took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 3.075599670410156e-05s
Believability | Calculation of trust value for diigo.feed took 7.62939453125e-06s
INFO | --- Analysis for diigo-feed took 2.8655941486358643s
Availability | SPARQL endpoint availability check for DisGeNET took 0.4032731056213379s
Availability | VoID file availability check for DisGeNET took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.27762770652770996s
Reputation | Calculation of the PageRank for DisGeNET took 0.02038097381591797s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.0001518726348876953s
Believability | Calculation of trust value for DisGeNET took 7.152557373046875e-06s
INFO | --- Analysis for disgenet took 3.4913973808288574s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 4.1961669921875e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.28227710723876953s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.020151376724243164s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 3.123283386230469e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 7.62939453125e-06s
INFO | --- Analysis for disk took 2.909926176071167s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 4.267692565917969e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.2797994613647461s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.020397424697875977s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 2.956390380859375e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 6.9141387939453125e-06s
INFO | --- Analysis for distritos-zaragoza took 2.9759795665740967s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.267692565917969e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0008051395416259766s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.2594583034515381s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.020453453063964844s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0008935928344726562s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.409385681152344e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 7.62939453125e-06s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 9.00734806060791s
Availability | SPARQL endpoint availability check for DM2E took 6.079673767089844e-05s
Availability | VoID file availability check for DM2E took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for DM2E took 0.2580087184906006s
Reputation | Calculation of the PageRank for DM2E took 0.02033233642578125s
Interlinking | Calculation of Degree of Connection for DM2E took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00010752677917480469s
Believability | Calculation of trust value for DM2E took 5.9604644775390625e-06s
INFO | --- Analysis for dm2e took 3.088588237762451s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 4.1961669921875e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.28111863136291504s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.02040696144104004s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 3.123283386230469e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 8.344650268554688e-06s
INFO | --- Analysis for dmoz_rdf_dump took 2.968230724334717s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 1.684208869934082s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0006549358367919922s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.32294678688049316s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.020714282989501953s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00015497207641601562s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 7.152557373046875e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 10.598678588867188s
Availability | SPARQL endpoint availability check for DOAP Store took 8.845329284667969e-05s
Availability | VoID file availability check for DOAP Store took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.2904837131500244s
Reputation | Calculation of the PageRank for DOAP Store took 0.020539522171020508s
Interlinking | Calculation of Degree of Connection for DOAP Store took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DOAP Store took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 3.075599670410156e-05s
Believability | Calculation of trust value for DOAP Store took 8.821487426757812e-06s
INFO | --- Analysis for doap_store took 2.9970178604125977s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 4.363059997558594e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.29675936698913574s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.020391225814819336s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.341934204101562e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 5.4836273193359375e-06s
INFO | --- Analysis for doi took 7.880572557449341s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 6.277415752410889s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0007212162017822266s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.25432753562927246s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.021849393844604492s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.838539123535156e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 6.9141387939453125e-06s
INFO | --- Analysis for drug-data-hifm took 32.553147315979004s
Availability | SPARQL endpoint availability check for dspace took 4.220008850097656e-05s
Availability | VoID file availability check for dspace took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for dspace took 0.24137353897094727s
Reputation | Calculation of the PageRank for dspace took 0.020188093185424805s
Interlinking | Calculation of Degree of Connection for dspace took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for dspace took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for dspace took 2.8848648071289062e-05s
Believability | Calculation of trust value for dspace took 7.867813110351562e-06s
INFO | --- Analysis for dspace took 2.865190029144287s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 4.1961669921875e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.2660844326019287s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.02030491828918457s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 2.8133392333984375e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 7.867813110351562e-06s
INFO | --- Analysis for duraark-linked-building-data took 2.9025144577026367s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 272.16811990737915s
Availability | VoID file availability check for MetaLex Document Server took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.45032358169555664s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.020740747451782227s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0009746551513671875s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 9.703636169433594e-05s
Believability | Calculation of trust value for MetaLex Document Server took 7.867813110351562e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 555.517528295517s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.5835392475128174s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.00033354759216308594s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.26921892166137695s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 4.00543212890625e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 6.4373016357421875e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 12.736281633377075s
Availability | SPARQL endpoint availability check for DWS-Group took 4.38690185546875e-05s
Availability | VoID file availability check for DWS-Group took 0.0007669925689697266s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.2657191753387451s
Reputation | Calculation of the PageRank for DWS-Group took 0.020395994186401367s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.0001068115234375s
Believability | Calculation of trust value for DWS-Group took 8.106231689453125e-06s
INFO | --- Analysis for dws-group took 4.2910239696502686s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.06636953353881836s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0003693103790283203s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.23834013938903809s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.02051568031311035s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0009410381317138672s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.0001373291015625s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-alaska took 2.894714117050171s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.042620182037353516s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0003635883331298828s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.25620222091674805s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020259618759155273s
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.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.459785461425781e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-cau took 3.004488706588745s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.033640384674072266s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.2607567310333252s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.020269155502319336s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.461143493652344e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.972963571548462s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.045290470123291016s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.2716827392578125s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.02016615867614746s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.822845458984375e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 8.58306884765625e-06s
INFO | --- Analysis for eagle-i-cdrewu took 2.89359974861145s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.04703402519226074s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.2634854316711426s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.020369291305541992s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0010228157043457031s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00016164779663085938s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-dartmouth took 2.491971492767334s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.04669904708862305s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0003688335418701172s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.2571690082550049s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.02021050453186035s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.392333984375e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-famu took 2.485417604446411s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.04676938056945801s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.2522454261779785s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.020641326904296875s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00013446807861328125s
Believability | Calculation of trust value for eagle-i @ Harvard University took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-harvard took 2.507009267807007s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.047330379486083984s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.00040435791015625s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.26259398460388184s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.020543336868286133s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00012731552124023438s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-hawaii took 2.4784531593322754s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.03923988342285156s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0011169910430908203s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.2943692207336426s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.02053356170654297s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.389617919921875e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-howard took 2.5122628211975098s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.03511857986450195s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.30916357040405273s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.0203249454498291s
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.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.389617919921875e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.5498878955841064s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.04471945762634277s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.2575991153717041s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.020512104034423828s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.0001251697540283203s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-jsu took 2.486701011657715s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.046133995056152344s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.2544238567352295s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.020088911056518555s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.838539123535156e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-meharry took 2.4600777626037598s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.04305863380432129s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0004229545593261719s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.25321292877197266s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.020607471466064453s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 9.775161743164062e-05s
Believability | Calculation of trust value for eagle-i @ Montana State University took 5.245208740234375e-06s
INFO | --- Analysis for eagle-i-montana took 2.445338249206543s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.04580807685852051s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0003790855407714844s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.24831199645996094s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.020948171615600586s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.846687316894531e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-msm took 2.4681460857391357s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.04592418670654297s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0003781318664550781s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.27038145065307617s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.02038288116455078s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00012946128845214844s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-ohsu took 2.4399735927581787s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.03642702102661133s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0004010200500488281s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.2643449306488037s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.02015399932861328s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.556510925292969e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-psm took 2.414931058883667s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.045606136322021484s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.25430870056152344s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020252227783203125s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.103515625e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 9.059906005859375e-06s
INFO | --- Analysis for eagle-i-tsu took 2.48587703704834s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.04250001907348633s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.2646963596343994s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.02013111114501953s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.341934204101562e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 1.4781951904296875e-05s
INFO | --- Analysis for eagle-i-tuskegee took 2.4952635765075684s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.04786419868469238s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.2380237579345703s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.02033257484436035s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.00010633468627929688s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-uccaribe took 2.398850440979004s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.04059720039367676s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.2684895992279053s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.019940614700317383s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00012159347534179688s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-upr took 2.4775402545928955s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.03933382034301758s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.26877856254577637s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.020142793655395508s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.0558319091796875e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-utep took 2.469562292098999s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.041745662689208984s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.2646622657775879s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.020149946212768555s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 6.580352783203125e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-utsa took 2.437455177307129s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.16605305671691895s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.0003910064697265625s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.26004672050476074s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.02005290985107422s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 8.749961853027344e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-vanderbilt took 2.645373821258545s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.03973054885864258s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.2762894630432129s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.02049398422241211s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.343292236328125e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-xula took 2.4988553524017334s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.3588869571685791s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.2530810832977295s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.02028203010559082s
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.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010204315185546875s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for ecb-linked-data took 2.850170850753784s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 0.16280341148376465s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0005698204040527344s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.2671232223510742s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.02021312713623047s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.4332275390625e-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.6269936561584473s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.8685095310211182s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.2662234306335449s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.020570755004882812s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.937980651855469e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 7.62939453125e-06s
INFO | --- Analysis for ecco-tcp-linked-data took 6.191651344299316s
Availability | SPARQL endpoint availability check for ECLAP took 20.627561569213867s
Availability | VoID file availability check for ECLAP took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for ECLAP took 0.2523040771484375s
Reputation | Calculation of the PageRank for ECLAP took 0.020113706588745117s
Interlinking | Calculation of Degree of Connection for ECLAP took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ECLAP took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for ECLAP took 3.695487976074219e-05s
Believability | Calculation of trust value for ECLAP took 7.152557373046875e-06s
INFO | --- Analysis for eclap took 53.16803240776062s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 7.43865966796875e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.243973970413208s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020342350006103516s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.793571472167969e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 7.3909759521484375e-06s
INFO | --- Analysis for ecs took 3.0093791484832764s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 0.00011754035949707031s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.28356170654296875s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.020700454711914062s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 3.24249267578125e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 7.3909759521484375e-06s
INFO | --- Analysis for edificios-historicos-zaragoza took 2.9978580474853516s
Availability | SPARQL endpoint availability check for Edublogs took 4.363059997558594e-05s
Availability | VoID file availability check for Edublogs took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for Edublogs took 0.26255011558532715s
Reputation | Calculation of the PageRank for Edublogs took 0.020326852798461914s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.00010013580322265625s
Believability | Calculation of trust value for Edublogs took 7.62939453125e-06s
INFO | --- Analysis for edublogs took 3.311415195465088s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.41414904594421387s
Availability | VoID file availability check for education.data.gov.uk took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.27619147300720215s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.02014470100402832s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 8.869171142578125e-05s
Believability | Calculation of trust value for education.data.gov.uk took 5.7220458984375e-06s
INFO | --- Analysis for education-data-gov-uk took 4.3707594871521s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 4.029273986816406e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.2650117874145508s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.02003622055053711s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 2.86102294921875e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 1.1205673217773438e-05s
INFO | --- Analysis for education-openuplabs took 2.9608852863311768s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 393.7388186454773s
Availability | VoID file availability check for Educational programs - SISVU took 0.0008959770202636719s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 1.340193271636963s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.02107977867126465s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 6.866455078125e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 7.62939453125e-06s
INFO | --- Analysis for educationalprograms_sisvu took 1324.075811624527s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 0.8025281429290771s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0006742477416992188s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.2807161808013916s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.020654678344726562s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 4.744529724121094e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 5.4836273193359375e-06s
INFO | --- Analysis for eea took 12.23388385772705s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.5161190032958984s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.26168179512023926s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020299434661865234s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.3882598876953125e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 5.7220458984375e-06s
INFO | --- Analysis for eea-rod took 5.909325838088989s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.19517779350280762s
Availability | VoID file availability check for EEA Vocabularies took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.26699185371398926s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.02078390121459961s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 9.202957153320312e-05s
Believability | Calculation of trust value for EEA Vocabularies took 1.0013580322265625e-05s
INFO | --- Analysis for eea-vocabularies took 6.263020277023315s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 4.482269287109375e-05s
Availability | VoID file availability check for Ege University Linked Open Data took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.3253951072692871s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.0204010009765625s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 3.314018249511719e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 8.821487426757812e-06s
INFO | --- Analysis for ege-university-linked-open-data took 3.9701318740844727s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 4.220008850097656e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.3015265464782715s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.020476818084716797s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010728836059570312s
Believability | Calculation of trust value for EIONET RDF Data took 5.7220458984375e-06s
INFO | --- Analysis for eionet-rdf took 2.8339931964874268s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 4.172325134277344e-05s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.27804040908813477s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.02037811279296875s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 3.0994415283203125e-05s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 1.3589859008789062e-05s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 2.96895432472229s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 2.6826720237731934s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.38336825370788574s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.02047109603881836s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 7.510185241699219e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 1.1682510375976562e-05s
INFO | --- Analysis for elviajero took 12.826278924942017s
Availability | SPARQL endpoint availability check for EMN took 4.458427429199219e-05s
Availability | VoID file availability check for EMN took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for EMN took 0.2825305461883545s
Reputation | Calculation of the PageRank for EMN took 0.02065896987915039s
Interlinking | Calculation of Degree of Connection for EMN took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for EMN took 4.8160552978515625e-05s
Believability | Calculation of trust value for EMN took 6.4373016357421875e-06s
INFO | --- Analysis for emn took 3.2729544639587402s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 4.410743713378906e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.2589261531829834s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.022093534469604492s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0010306835174560547s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 6.508827209472656e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 5.9604644775390625e-06s
INFO | --- Analysis for enakting-co2emission took 2.4432661533355713s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 4.363059997558594e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.00044035911560058594s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.2821376323699951s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.020802021026611328s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 4.267692565917969e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 5.4836273193359375e-06s
INFO | --- Analysis for enakting-crime took 2.4414172172546387s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.315376281738281e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.0006940364837646484s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.27602362632751465s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.02068352699279785s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 4.410743713378906e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 5.7220458984375e-06s
INFO | --- Analysis for enakting-energy took 2.390916109085083s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.26920223236083984s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.02068638801574707s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 9.655952453613281e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 5.9604644775390625e-06s
INFO | --- Analysis for enakting-mortality took 2.3722620010375977s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.649162292480469e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.2759706974029541s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.02045583724975586s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 4.863739013671875e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 5.4836273193359375e-06s
INFO | --- Analysis for enakting-nhs took 2.494917631149292s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 4.38690185546875e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.2549419403076172s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.020415544509887695s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.555152893066406e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 5.7220458984375e-06s
INFO | --- Analysis for enakting-population took 2.3914413452148438s
Availability | SPARQL endpoint availability check for Enel Shops took 4.172325134277344e-05s
Availability | VoID file availability check for Enel Shops took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.2734100818634033s
Reputation | Calculation of the PageRank for Enel Shops took 0.020513296127319336s
Interlinking | Calculation of Degree of Connection for Enel Shops took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Enel Shops took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 3.123283386230469e-05s
Believability | Calculation of trust value for Enel Shops took 7.867813110351562e-06s
INFO | --- Analysis for enel-shops took 2.9335153102874756s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 5.245208740234375e-05s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.23627138137817383s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.0203857421875s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 3.266334533691406e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 8.821487426757812e-06s
INFO | --- Analysis for energy-efficiency took 2.9223976135253906s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.0002846717834472656s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.26447415351867676s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.02063918113708496s
Interlinking | Calculation of Degree of Connection for English Heritage Archaeological Sciences Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Heritage Archaeological Sciences Thesaurus took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 3.218650817871094e-05s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for english-heritage-archaeological-sciences-thesaurus took 2.914088487625122s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 4.1484832763671875e-05s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 0.00028705596923828125s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.264005184173584s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.02023458480834961s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 3.361701965332031e-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.9519553184509277s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 4.2438507080078125e-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.27922987937927246s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.020458698272705078s
Interlinking | Calculation of Degree of Connection for English Heritage Components Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Heritage Components Thesaurus took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 3.719329833984375e-05s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for english-heritage-components-thesaurus took 2.956122398376465s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 4.9114227294921875e-05s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.25079989433288574s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.02056741714477539s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 3.147125244140625e-05s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 2.892620801925659s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 5.412101745605469e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 0.28672313690185547s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.020600557327270508s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 3.4809112548828125e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 2.942845582962036s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.25939369201660156s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for English Heritage Maritime Craft Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for English Heritage Maritime Craft Thesaurus took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 3.0517578125e-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.902218818664551s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 4.1961669921875e-05s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.2536928653717041s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.020575761795043945s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 3.123283386230469e-05s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for english-heritage-monument-types-thesaurus took 2.944204330444336s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 1.0868737697601318s
Availability | VoID file availability check for English Heritage Periods List took 0.0006794929504394531s
Extra | Recovery of all triples for English Heritage Periods List took 0.4196481704711914s
Performance | Total latancy measurement for English Heritage Periods List took 2.0218818187713623s
Amount of data | Number of triples check for English Heritage Periods List took 0.6049258708953857s
Versatility | Languages check for English Heritage Periods List took 0.3495361804962158s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.5592236518859863s
Security | Check HTTPS for English Heritage Periods List took 0.272960901260376s
Interpretability | RDF structures check for English Heritage Periods List took 0.35353875160217285s
Versatility | Serialization formats check for English Heritage Periods List took 0.5708169937133789s
Availability | RDF dump link check for English Heritage Periods List took 0.41104650497436523s
License | MR license check for English Heritage Periods List took 0.47109436988830566s
License | HR license check for English Heritage Periods List took 0.4170525074005127s
Amount of data | Number of property check for English Heritage Periods List took 0.44812822341918945s
Understandability | Number of label check for English Heritage Periods List took 0.5324485301971436s
Understandability | URI regex check for English Heritage Periods List took 0.8333022594451904s
Understandability | Vocabs check for English Heritage Periods List took 0.4343860149383545s
Verifiability | Authors check for English Heritage Periods List took 0.46477484703063965s
Verifiability | Publishers check for English Heritage Periods List took 0.43192529678344727s
Performance | Throughput check for English Heritage Periods List took 11.965530395507812s
Amount of data | Check the number of entities for English Heritage Periods List took 7.081031799316406e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.40497350692749023s
Interlinking | sameAs chians check for English Heritage Periods List took 0.38608765602111816s
Interlinking | skos check for English Heritage Periods List took 0.42456793785095215s
Interlinking | skos check for English Heritage Periods List took 0.4029555320739746s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.4780113697052002s
Currency | Creation date check for English Heritage Periods List took 0.7885169982910156s
Currency | Modification date check for English Heritage Periods List took 0.8499305248260498s
Rep.Conc. | URIs length for English Heritage Periods List took 0.8105542659759521s
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.40981125831604004s
Accuracy | Check Functional Property for English Heritage Periods List took 0.3672757148742676s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.40558409690856934s
Consistency | Disjoint class check for English Heritage Periods List took 0.4014403820037842s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.42458248138427734s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.7440719604492188s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.00014138221740722656s
Security | Sign check for English Heritage Periods List took 0.42740917205810547s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.37644004821777344s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.552436828613281e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Heritage Periods List took 6.9141387939453125e-06s
INFO | --- Analysis for english-heritage-periods-list took 61.39158797264099s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.40203094482421875s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0008444786071777344s
Extra | Recovery of all triples for English Index of Multiple Deprivation Ranking 2010 took 0.329758882522583s
Performance | Total latancy measurement for English Index of Multiple Deprivation Ranking 2010 took 1.0641729831695557s
Amount of data | Number of triples check for English Index of Multiple Deprivation Ranking 2010 took 0.25699496269226074s
Interoperability | New terms check for English Index of Multiple Deprivation Ranking 2010 took 2.091797351837158s
Versatility | Languages check for English Index of Multiple Deprivation Ranking 2010 took 0.3290400505065918s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Ranking 2010 took 0.2827296257019043s
Security | Check HTTPS for English Index of Multiple Deprivation Ranking 2010 took 0.10641074180603027s
Interpretability | RDF structures check for English Index of Multiple Deprivation Ranking 2010 took 0.26847124099731445s
Versatility | Serialization formats check for English Index of Multiple Deprivation Ranking 2010 took 0.13410377502441406s
Availability | RDF dump link check for English Index of Multiple Deprivation Ranking 2010 took 47.84786248207092s
License | MR license check for English Index of Multiple Deprivation Ranking 2010 took 0.25113630294799805s
License | HR license check for English Index of Multiple Deprivation Ranking 2010 took 0.21727418899536133s
Amount of data | Number of property check for English Index of Multiple Deprivation Ranking 2010 took 0.1296520233154297s
Understandability | Number of label check for English Index of Multiple Deprivation Ranking 2010 took 0.2389976978302002s
Understandability | URI regex check for English Index of Multiple Deprivation Ranking 2010 took 0.33247900009155273s
Understandability | Vocabs check for English Index of Multiple Deprivation Ranking 2010 took 0.20287609100341797s
Verifiability | Authors check for English Index of Multiple Deprivation Ranking 2010 took 0.1327989101409912s
Verifiability | Publishers check for English Index of Multiple Deprivation Ranking 2010 took 0.29698967933654785s
Performance | Throughput check for English Index of Multiple Deprivation Ranking 2010 took 11.895451545715332s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Ranking 2010 took 7.033348083496094e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Ranking 2010 took 0.15289568901062012s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Ranking 2010 took 0.3115518093109131s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.29118871688842773s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.15230584144592285s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Ranking 2010 took 0.20360827445983887s
Currency | Creation date check for English Index of Multiple Deprivation Ranking 2010 took 0.5471680164337158s
Currency | Modification date check for English Index of Multiple Deprivation Ranking 2010 took 0.23495841026306152s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Ranking 2010 took 0.6881136894226074s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Ranking 2010 took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Ranking 2010 took 0.13464021682739258s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.12979578971862793s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.1379251480102539s
Consistency | Disjoint class check for English Index of Multiple Deprivation Ranking 2010 took 0.30313730239868164s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Ranking 2010 took 0.5746877193450928s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Ranking 2010 took 0.2788846492767334s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Ranking 2010 took 1.552259922027588s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.00017261505126953125s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.3392148017883301s
Security | Sign check for English Index of Multiple Deprivation Ranking 2010 took 0.14575695991516113s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.2720510959625244s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.020259857177734375s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.2901763916015625e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Ranking 2010 took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 6.198883056640625e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 176.14726090431213s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.4347257614135742s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0006821155548095703s
Extra | Recovery of all triples for English Index of Multiple Deprivation Score 2010 took 0.2327582836151123s
Performance | Total latancy measurement for English Index of Multiple Deprivation Score 2010 took 1.1185829639434814s
Amount of data | Number of triples check for English Index of Multiple Deprivation Score 2010 took 0.1476128101348877s
Interoperability | New terms check for English Index of Multiple Deprivation Score 2010 took 1.5337791442871094s
Versatility | Languages check for English Index of Multiple Deprivation Score 2010 took 0.2895781993865967s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Score 2010 took 0.22211098670959473s
Security | Check HTTPS for English Index of Multiple Deprivation Score 2010 took 0.11627054214477539s
Interpretability | RDF structures check for English Index of Multiple Deprivation Score 2010 took 0.13646888732910156s
Versatility | Serialization formats check for English Index of Multiple Deprivation Score 2010 took 0.13343524932861328s
Availability | RDF dump link check for English Index of Multiple Deprivation Score 2010 took 45.416565895080566s
License | MR license check for English Index of Multiple Deprivation Score 2010 took 0.24375057220458984s
License | HR license check for English Index of Multiple Deprivation Score 2010 took 0.44771718978881836s
Amount of data | Number of property check for English Index of Multiple Deprivation Score 2010 took 0.1858205795288086s
Understandability | Number of label check for English Index of Multiple Deprivation Score 2010 took 0.21858954429626465s
Understandability | URI regex check for English Index of Multiple Deprivation Score 2010 took 0.36412978172302246s
Understandability | Vocabs check for English Index of Multiple Deprivation Score 2010 took 0.14210247993469238s
Verifiability | Authors check for English Index of Multiple Deprivation Score 2010 took 0.1480720043182373s
Verifiability | Publishers check for English Index of Multiple Deprivation Score 2010 took 0.13158488273620605s
Performance | Throughput check for English Index of Multiple Deprivation Score 2010 took 11.281272888183594s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Score 2010 took 7.510185241699219e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Score 2010 took 0.2825343608856201s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Score 2010 took 0.2312335968017578s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.14583730697631836s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.1423046588897705s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Score 2010 took 0.18915033340454102s
Currency | Creation date check for English Index of Multiple Deprivation Score 2010 took 0.442852258682251s
Currency | Modification date check for English Index of Multiple Deprivation Score 2010 took 0.15072131156921387s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Score 2010 took 0.419330358505249s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Score 2010 took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Score 2010 took 0.20455074310302734s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Score 2010 took 0.4123542308807373s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Score 2010 took 0.13296985626220703s
Consistency | Disjoint class check for English Index of Multiple Deprivation Score 2010 took 0.14306902885437012s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Score 2010 took 0.3645932674407959s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Score 2010 took 0.2271411418914795s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Score 2010 took 1.510099172592163s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.0001380443572998047s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.22251009941101074s
Security | Sign check for English Index of Multiple Deprivation Score 2010 took 0.13938355445861816s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.2644531726837158s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.020580291748046875s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.886222839355469e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Score 2010 took 9.5367431640625e-07s
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 163.96974968910217s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 4.220008850097656e-05s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 0.2630300521850586s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.020373821258544922s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 2.9087066650390625e-05s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 7.62939453125e-06s
INFO | --- Analysis for english-indices-of-multiple-deprivation took 2.9052748680114746s
Availability | SPARQL endpoint availability check for English Heritage Places took 5.078315734863281e-05s
Availability | VoID file availability check for English Heritage Places took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for English Heritage Places took 0.2630929946899414s
Reputation | Calculation of the PageRank for English Heritage Places took 0.020303010940551758s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 2.8848648071289062e-05s
Believability | Calculation of trust value for English Heritage Places took 7.152557373046875e-06s
INFO | --- Analysis for englishheritage_places took 2.9072000980377197s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.17981672286987305s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.28054356575012207s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.019986867904663086s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 8.678436279296875e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 7.152557373046875e-06s
INFO | --- Analysis for enipedia took 2.649590015411377s
Availability | SPARQL endpoint availability check for Entrez Gene took 4.291534423828125e-05s
Availability | VoID file availability check for Entrez Gene took 0.0007069110870361328s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.2814457416534424s
Reputation | Calculation of the PageRank for Entrez Gene took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.8623809814453125e-05s
Believability | Calculation of trust value for Entrez Gene took 7.152557373046875e-06s
INFO | --- Analysis for entrez_gene took 27.12904453277588s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 4.2438507080078125e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 0.28090333938598633s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.02069878578186035s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 3.170967102050781e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 7.152557373046875e-06s
INFO | --- Analysis for entrez_gene_extract took 2.9047250747680664s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.0965797901153564s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.285952091217041s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.02146172523498535s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0009455680847167969s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.817413330078125e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 5.7220458984375e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 12.155659437179565s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.31248021125793457s
Availability | VoID file availability check for environment.data.gov.uk took 0.00042891502380371094s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.2655673027038574s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.020689964294433594s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.76837158203125e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 5.9604644775390625e-06s
INFO | --- Analysis for environment-data-gov-uk took 9.610944986343384s
Availability | SPARQL endpoint availability check for EARTh took 270.46860909461975s
Availability | VoID file availability check for EARTh took 0.0007073879241943359s
Completeness | Calculation of interlinking completeness for EARTh took 0.29328131675720215s
Reputation | Calculation of the PageRank for EARTh took 0.020608901977539062s
Interlinking | Calculation of Degree of Connection for EARTh took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00010395050048828125s
Believability | Calculation of trust value for EARTh took 8.344650268554688e-06s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 561.9713518619537s
Availability | SPARQL endpoint availability check for EPA-CDR took 4.744529724121094e-05s
Availability | VoID file availability check for EPA-CDR took 0.0006837844848632812s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.282090425491333s
Reputation | Calculation of the PageRank for EPA-CDR took 0.020621538162231445s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0008020401000976562s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.910064697265625e-05s
Believability | Calculation of trust value for EPA-CDR took 5.7220458984375e-06s
INFO | --- Analysis for epa-cdr took 8.333001613616943s
Availability | SPARQL endpoint availability check for EPA-FRS took 4.267692565917969e-05s
Availability | VoID file availability check for EPA-FRS took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.33628153800964355s
Reputation | Calculation of the PageRank for EPA-FRS took 0.02046346664428711s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.390975952148438e-05s
Believability | Calculation of trust value for EPA-FRS took 5.245208740234375e-06s
INFO | --- Analysis for epa-frs took 7.301721572875977s
Availability | SPARQL endpoint availability check for EPA-RCRA took 6.175041198730469e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.24504756927490234s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.023210763931274414s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0013365745544433594s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 4.76837158203125e-05s
Believability | Calculation of trust value for EPA-RCRA took 5.0067901611328125e-06s
INFO | --- Analysis for epa-rcra took 6.603576898574829s
Availability | SPARQL endpoint availability check for EPA-SRS took 4.267692565917969e-05s
Availability | VoID file availability check for EPA-SRS took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.2819063663482666s
Reputation | Calculation of the PageRank for EPA-SRS took 0.020288467407226562s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.82012939453125e-05s
Believability | Calculation of trust value for EPA-SRS took 4.76837158203125e-06s
INFO | --- Analysis for epa-srs took 6.291244029998779s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.1484832763671875e-05s
Availability | VoID file availability check for EPA-TRI took 0.0011739730834960938s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.2659423351287842s
Reputation | Calculation of the PageRank for EPA-TRI took 0.02057671546936035s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0010044574737548828s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 4.172325134277344e-05s
Believability | Calculation of trust value for EPA-TRI took 9.5367431640625e-06s
INFO | --- Analysis for epa-tri took 6.425081014633179s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 4.172325134277344e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 0.24181604385375977s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.020433425903320312s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 7.843971252441406e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 1.2159347534179688e-05s
INFO | --- Analysis for epo took 2.881040096282959s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.04308366775512695s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.00036907196044921875s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.29168176651000977s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.020405054092407227s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00012993812561035156s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.5207226276397705s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.5134382247924805s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.25255751609802246s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.020637035369873047s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.368492126464844e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 7.62939453125e-06s
INFO | --- Analysis for eprtr took 3.5220870971679688s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.16369009017944336s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.2657287120819092s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.020722389221191406s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0011005401611328125s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.933906555175781e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 6.198883056640625e-06s
INFO | --- Analysis for es-msssi-drug-prices took 2.7415237426757812s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 4.410743713378906e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0007202625274658203s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.28841638565063477s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.02000904083251953s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 8.559226989746094e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 5.7220458984375e-06s
INFO | --- Analysis for esd-standards took 3.8563854694366455s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 4.291534423828125e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.2662477493286133s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.020272254943847656s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.081031799316406e-05s
Believability | Calculation of trust value for ESD-Toolkit took 6.67572021484375e-06s
INFO | --- Analysis for esd-toolkit took 3.6737051010131836s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 0.1512913703918457s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.2518789768218994s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.020495891571044922s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.796287536621094e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 8.106231689453125e-06s
INFO | --- Analysis for eu-agencies-bodies took 2.6452112197875977s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 5.340576171875e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.2696821689605713s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.01999640464782715s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 2.7418136596679688e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 7.867813110351562e-06s
INFO | --- Analysis for eu-dgt-tm took 2.8856256008148193s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 4.482269287109375e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.2772188186645508s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.020164966583251953s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.104873657226562e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 5.0067901611328125e-06s
INFO | --- Analysis for eu-institutions took 2.58457350730896s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 0.12132382392883301s
Availability | VoID file availability check for EU Parliament Media Library took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.2634139060974121s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.02020549774169922s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.1948089599609375e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 5.245208740234375e-06s
INFO | --- Analysis for eu-parliament-media took 2.5756542682647705s
Availability | SPARQL endpoint availability check for EU Who Is Who took 0.08996272087097168s
Availability | VoID file availability check for EU Who Is Who took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.2687196731567383s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.504753112792969e-05s
Believability | Calculation of trust value for EU Who Is Who took 1.5497207641601562e-05s
INFO | --- Analysis for eu-who-is-who took 2.5542352199554443s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 0.09234189987182617s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.2622199058532715s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.02039957046508789s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 3.933906555175781e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for eumida-linked-data took 2.6048872470855713s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.28273987770080566s
Availability | VoID file availability check for European Nature Information System took 0.0006978511810302734s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.2844381332397461s
Reputation | Calculation of the PageRank for European Nature Information System took 0.021170377731323242s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0010986328125s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.0001304149627685547s
Believability | Calculation of trust value for European Nature Information System took 6.67572021484375e-06s
INFO | --- Analysis for eunis took 4.178583860397339s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 0.13857340812683105s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.2818577289581299s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.020355701446533203s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.104873657226562e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for eur-lex-rdf took 2.669483184814453s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 0.09020471572875977s
Availability | VoID file availability check for Standard Eurobarometer took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.24915647506713867s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.020216703414916992s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 3.886222839355469e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 6.9141387939453125e-06s
INFO | --- Analysis for eurobarometer-standard took 2.623293399810791s
Availability | SPARQL endpoint availability check for European Election Results took 0.09652328491210938s
Availability | VoID file availability check for European Election Results took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for European Election Results took 0.2935359477996826s
Reputation | Calculation of the PageRank for European Election Results took 0.022242307662963867s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0008029937744140625s
Interlinking | Calculation of Clustering coefficient for European Election Results took 4.076957702636719e-05s
Believability | Calculation of trust value for European Election Results took 4.5299530029296875e-06s
INFO | --- Analysis for european-election-results took 2.71174693107605s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 4.1484832763671875e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.24619579315185547s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 3.1948089599609375e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 6.4373016357421875e-06s
INFO | --- Analysis for europeana-lod took 2.899812936782837s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 0.0005376338958740234s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.3167288303375244s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.02037525177001953s
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.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.584426879882812e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 7.62939453125e-06s
INFO | --- Analysis for europeana-lod-v1 took 7.436032295227051s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.039440155029296875s
Availability | VoID file availability check for Europeana SPARQL took 0.0006530284881591797s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.23959994316101074s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.020070552825927734s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 4.506111145019531e-05s
Believability | Calculation of trust value for Europeana SPARQL took 1.1682510375976562e-05s
INFO | --- Analysis for europeana-sparql took 2.6688473224639893s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.07739996910095215s
Availability | VoID file availability check for EuroSentiment took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.31235194206237793s
Reputation | Calculation of the PageRank for EuroSentiment took 0.020612001419067383s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.910064697265625e-05s
Believability | Calculation of trust value for EuroSentiment took 7.62939453125e-06s
INFO | --- Analysis for eurosentiment took 3.20654559135437s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 4.291534423828125e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.24076247215270996s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.020617008209228516s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 8.034706115722656e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 5.7220458984375e-06s
INFO | --- Analysis for eurostat-rdf took 12.09074091911316s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 4.076957702636719e-05s
Availability | VoID file availability check for EUROVOC in SKOS took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 0.26853513717651367s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.020668983459472656s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 4.220008850097656e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 7.867813110351562e-06s
INFO | --- Analysis for eurovoc-in-skos took 2.9518985748291016s
Availability | SPARQL endpoint availability check for European Television Heritage took 4.1961669921875e-05s
Availability | VoID file availability check for European Television Heritage took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.27915239334106445s
Reputation | Calculation of the PageRank for European Television Heritage took 0.020557641983032227s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 3.075599670410156e-05s
Believability | Calculation of trust value for European Television Heritage took 7.152557373046875e-06s
INFO | --- Analysis for euscreen took 2.9606480598449707s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 4.6253204345703125e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0007355213165283203s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.2706258296966553s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.020817995071411133s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.6253204345703125e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 5.245208740234375e-06s
INFO | --- Analysis for euskadi-farmacias took 5.390578269958496s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.349545955657959s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0009326934814453125s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.2663290500640869s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.510185241699219e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 1.3828277587890625e-05s
INFO | --- Analysis for eutc-productions took 6.940016508102417s
Availability | SPARQL endpoint availability check for EventMedia took 0.3840780258178711s
Availability | VoID file availability check for EventMedia took 0.00035309791564941406s
Completeness | Calculation of interlinking completeness for EventMedia took 0.27045726776123047s
Reputation | Calculation of the PageRank for EventMedia took 0.020619869232177734s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0007965564727783203s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00011515617370605469s
Believability | Calculation of trust value for EventMedia took 8.106231689453125e-06s
INFO | --- Analysis for event-media took 14.657038450241089s
Availability | SPARQL endpoint availability check for Eventseer took 1.0696730613708496s
Availability | VoID file availability check for Eventseer took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Eventseer took 0.26743531227111816s
Reputation | Calculation of the PageRank for Eventseer took 0.02040386199951172s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.887580871582031e-05s
Believability | Calculation of trust value for Eventseer took 7.62939453125e-06s
INFO | --- Analysis for eventseer took 3.432677984237671s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 8.96453857421875e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.2724173069000244s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.020288705825805664s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 2.9802322387695312e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 7.3909759521484375e-06s
INFO | --- Analysis for facebook-lids took 2.904196262359619s
Availability | SPARQL endpoint availability check for Fact Forge took 4.2438507080078125e-05s
Availability | VoID file availability check for Fact Forge took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.23023176193237305s
Reputation | Calculation of the PageRank for Fact Forge took 0.020256519317626953s
Interlinking | Calculation of Degree of Connection for Fact Forge took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fact Forge took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 2.8848648071289062e-05s
Believability | Calculation of trust value for Fact Forge took 7.3909759521484375e-06s
INFO | --- Analysis for fact-forge took 2.7828149795532227s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 4.8160552978515625e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.00070953369140625s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.26706790924072266s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.02095651626586914s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 9.655952453613281e-05s
Believability | Calculation of trust value for FAO geopolitical ontology took 9.298324584960938e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 10.516694784164429s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.15404176712036133s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.28177547454833984s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.02052760124206543s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.965896606445312e-05s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for fao-linked-data took 2.5750350952148438s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.553736686706543s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0005919933319091797s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.28171396255493164s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.0205686092376709s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.696846008300781e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 6.9141387939453125e-06s
INFO | --- Analysis for farmbio-chembl took 65.02624988555908s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 5.078315734863281e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.000274658203125s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.2523000240325928s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.020715951919555664s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 3.123283386230469e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 7.152557373046875e-06s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 2.9363420009613037s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 6.532669067382812e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.2778608798980713s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.020296096801757812s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 3.123283386230469e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for farolapp-dataset took 2.8974013328552246s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 4.982948303222656e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.0003962516784667969s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.2595536708831787s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.020334720611572266s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Fatal Traffic Accidents in greek roads took 3.314018249511719e-05s
Believability | Calculation of trust value for Fatal Traffic Accidents in greek roads took 8.58306884765625e-06s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 2.9466118812561035s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 4.220008850097656e-05s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 0.29079365730285645s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.02052593231201172s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 3.123283386230469e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 8.344650268554688e-06s
INFO | --- Analysis for federal-economic-rdf took 2.983241081237793s
Availability | SPARQL endpoint availability check for Feed Wrapper took 5.91278076171875e-05s
Availability | VoID file availability check for Feed Wrapper took 0.00022292137145996094s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 0.2736022472381592s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.020704269409179688s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 3.1948089599609375e-05s
Believability | Calculation of trust value for Feed Wrapper took 1.3113021850585938e-05s
INFO | --- Analysis for feedwrapper-lids took 2.8803136348724365s
Availability | SPARQL endpoint availability check for FiESTA took 4.291534423828125e-05s
Availability | VoID file availability check for FiESTA took 0.0007560253143310547s
Completeness | Calculation of interlinking completeness for FiESTA took 0.24184846878051758s
Reputation | Calculation of the PageRank for FiESTA took 0.020412445068359375s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for FiESTA took 4.00543212890625e-05s
Believability | Calculation of trust value for FiESTA took 3.0517578125e-05s
INFO | --- Analysis for fiesta took 12.531695365905762s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 5.841255187988281e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0006201267242431641s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.3602735996246338s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.0207822322845459s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 8.392333984375e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 5.9604644775390625e-06s
INFO | --- Analysis for finnish-municipalities took 185.0244710445404s
Availability | SPARQL endpoint availability check for firmao took 4.124641418457031e-05s
Availability | VoID file availability check for firmao took 0.0002932548522949219s
Completeness | Calculation of interlinking completeness for firmao took 0.24810171127319336s
Reputation | Calculation of the PageRank for firmao took 0.020544052124023438s
Interlinking | Calculation of Degree of Connection for firmao took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for firmao took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for firmao took 3.504753112792969e-05s
Believability | Calculation of trust value for firmao took 7.62939453125e-06s
INFO | --- Analysis for firmao took 2.9118213653564453s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 4.315376281738281e-05s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.2785007953643799s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.020544052124023438s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 3.123283386230469e-05s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 2.978811025619507s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.363059997558594e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.2762565612792969s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.020264148712158203s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 9.274482727050781e-05s
Believability | Calculation of trust value for Fishes of Texas took 1.1920928955078125e-05s
INFO | --- Analysis for fishes-of-texas took 4.13422155380249s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.267692565917969e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.27288365364074707s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.021543502807617188s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.608268737792969e-05s
Believability | Calculation of trust value for flickr? wrappr took 9.775161743164062e-06s
INFO | --- Analysis for flickr-wrappr took 3.423163890838623s
Availability | SPARQL endpoint availability check for flickr.person took 4.124641418457031e-05s
Availability | VoID file availability check for flickr.person took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for flickr.person took 0.2704625129699707s
Reputation | Calculation of the PageRank for flickr.person took 0.020676612854003906s
Interlinking | Calculation of Degree of Connection for flickr.person took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for flickr.person took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for flickr.person took 3.218650817871094e-05s
Believability | Calculation of trust value for flickr.person took 8.344650268554688e-06s
INFO | --- Analysis for flickr_person took 2.8983402252197266s
Availability | SPARQL endpoint availability check for flickr.videoobject took 6.29425048828125e-05s
Availability | VoID file availability check for flickr.videoobject took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 0.2685084342956543s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.021060943603515625s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.0010268688201904297s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 4.029273986816406e-05s
Believability | Calculation of trust value for flickr.videoobject took 8.344650268554688e-06s
INFO | --- Analysis for flickr_videoobject took 2.8692233562469482s
Availability | SPARQL endpoint availability check for Fly-TED took 4.0531158447265625e-05s
Availability | VoID file availability check for Fly-TED took 0.0002963542938232422s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.25379300117492676s
Reputation | Calculation of the PageRank for Fly-TED took 0.021007776260375977s
Interlinking | Calculation of Degree of Connection for Fly-TED took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Fly-TED took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 3.361701965332031e-05s
Believability | Calculation of trust value for Fly-TED took 8.58306884765625e-06s
INFO | --- Analysis for fly-ted took 2.869837522506714s
Availability | SPARQL endpoint availability check for FlyAtlas took 4.0531158447265625e-05s
Availability | VoID file availability check for FlyAtlas took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.2454373836517334s
Reputation | Calculation of the PageRank for FlyAtlas took 0.020088911056518555s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 2.7894973754882812e-05s
Believability | Calculation of trust value for FlyAtlas took 7.867813110351562e-06s
INFO | --- Analysis for flyatlas took 2.8081092834472656s
Availability | SPARQL endpoint availability check for Flybase took 1.7541885375976562s
Availability | VoID file availability check for Flybase took 0.0003695487976074219s
Completeness | Calculation of interlinking completeness for Flybase took 0.25437259674072266s
Reputation | Calculation of the PageRank for Flybase took 0.021519899368286133s
Interlinking | Calculation of Degree of Connection for Flybase took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.886222839355469e-05s
Believability | Calculation of trust value for Flybase took 1.239776611328125e-05s
INFO | --- Analysis for flybase took 9.88904881477356s
Availability | SPARQL endpoint availability check for Flyted took 1.5132598876953125s
Availability | VoID file availability check for Flyted took 0.0006430149078369141s
Completeness | Calculation of interlinking completeness for Flyted took 0.27562856674194336s
Reputation | Calculation of the PageRank for Flyted took 0.02038884162902832s
Interlinking | Calculation of Degree of Connection for Flyted took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.170967102050781e-05s
Believability | Calculation of trust value for Flyted took 6.9141387939453125e-06s
INFO | --- Analysis for flyted took 11.211086511611938s
Availability | SPARQL endpoint availability check for Foodista took 0.9610943794250488s
Availability | VoID file availability check for Foodista took 0.0006690025329589844s
Completeness | Calculation of interlinking completeness for Foodista took 0.2692561149597168s
Reputation | Calculation of the PageRank for Foodista took 0.0204312801361084s
Interlinking | Calculation of Degree of Connection for Foodista took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Foodista took 5.221366882324219e-05s
Believability | Calculation of trust value for Foodista took 7.867813110351562e-06s
INFO | --- Analysis for foodista took 10.298595428466797s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.27651500701904297s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.28045082092285156s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.020503997802734375s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.534027099609375e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 6.4373016357421875e-06s
INFO | --- Analysis for foodpedia took 2.7488174438476562s
Availability | SPARQL endpoint availability check for FORGE Course information took 4.172325134277344e-05s
Availability | VoID file availability check for FORGE Course information took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.2517213821411133s
Reputation | Calculation of the PageRank for FORGE Course information took 0.020498275756835938s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 3.170967102050781e-05s
Believability | Calculation of trust value for FORGE Course information took 1.33514404296875e-05s
INFO | --- Analysis for forge-course-information took 2.9180350303649902s
Availability | SPARQL endpoint availability check for FrameNet took 4.220008850097656e-05s
Availability | VoID file availability check for FrameNet took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for FrameNet took 0.25240612030029297s
Reputation | Calculation of the PageRank for FrameNet took 0.021711111068725586s
Interlinking | Calculation of Degree of Connection for FrameNet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for FrameNet took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for FrameNet took 3.457069396972656e-05s
Believability | Calculation of trust value for FrameNet took 7.152557373046875e-06s
INFO | --- Analysis for framenet took 2.902318239212036s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.18276071548461914s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.2598423957824707s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.02030181884765625s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.916854858398438e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for frb-linked-data took 2.5720412731170654s
Availability | SPARQL endpoint availability check for Freebase took 4.2438507080078125e-05s
Availability | VoID file availability check for Freebase took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for Freebase took 0.25000810623168945s
Reputation | Calculation of the PageRank for Freebase took 0.020342111587524414s
Interlinking | Calculation of Degree of Connection for Freebase took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Freebase took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.0003094673156738281s
Believability | Calculation of trust value for Freebase took 6.9141387939453125e-06s
INFO | --- Analysis for freebase took 3.867969274520874s
Availability | SPARQL endpoint availability check for French School Program took 4.124641418457031e-05s
Availability | VoID file availability check for French School Program took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for French School Program took 0.2636129856109619s
Reputation | Calculation of the PageRank for French School Program took 0.020128250122070312s
Interlinking | Calculation of Degree of Connection for French School Program took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for French School Program took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for French School Program took 2.86102294921875e-05s
Believability | Calculation of trust value for French School Program took 7.62939453125e-06s
INFO | --- Analysis for french-school-program took 2.8999063968658447s
Availability | SPARQL endpoint availability check for French School System took 4.1484832763671875e-05s
Availability | VoID file availability check for French School System took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for French School System took 0.26387906074523926s
Reputation | Calculation of the PageRank for French School System took 0.02067852020263672s
Interlinking | Calculation of Degree of Connection for French School System took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for French School System took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for French School System took 3.218650817871094e-05s
Believability | Calculation of trust value for French School System took 7.152557373046875e-06s
INFO | --- Analysis for french-school-system took 2.9277710914611816s
Availability | SPARQL endpoint availability check for French TimeBank took 4.3392181396484375e-05s
Availability | VoID file availability check for French TimeBank took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for French TimeBank took 0.2585632801055908s
Reputation | Calculation of the PageRank for French TimeBank took 0.020536184310913086s
Interlinking | Calculation of Degree of Connection for French TimeBank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for French TimeBank took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 3.170967102050781e-05s
Believability | Calculation of trust value for French TimeBank took 7.867813110351562e-06s
INFO | --- Analysis for french-timebank took 2.884807586669922s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.7503318786621094s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.25214648246765137s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 8.416175842285156e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 9.298324584960938e-06s
INFO | --- Analysis for fu-berlin-cordis took 4.3901026248931885s
Availability | SPARQL endpoint availability check for DailyMed took 0.7065615653991699s
Availability | VoID file availability check for DailyMed took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for DailyMed took 0.26350998878479004s
Reputation | Calculation of the PageRank for DailyMed took 0.020308494567871094s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.5367431640625e-05s
Believability | Calculation of trust value for DailyMed took 1.1920928955078125e-05s
INFO | --- Analysis for fu-berlin-dailymed took 5.660249710083008s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.7016525268554688s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.2682769298553467s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.020657062530517578s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.845329284667969e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 1.5020370483398438e-05s
INFO | --- Analysis for fu-berlin-dblp took 4.296282768249512s
Availability | SPARQL endpoint availability check for Diseasome took 0.7187416553497314s
Availability | VoID file availability check for Diseasome took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Diseasome took 0.256274938583374s
Reputation | Calculation of the PageRank for Diseasome took 0.02046966552734375s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.0001068115234375s
Believability | Calculation of trust value for Diseasome took 6.67572021484375e-06s
INFO | --- Analysis for fu-berlin-diseasome took 5.6657819747924805s
Availability | SPARQL endpoint availability check for DrugBank took 0.7182986736297607s
Availability | VoID file availability check for DrugBank took 0.0007069110870361328s
Completeness | Calculation of interlinking completeness for DrugBank took 0.2569003105163574s
Reputation | Calculation of the PageRank for DrugBank took 0.020567893981933594s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011515617370605469s
Believability | Calculation of trust value for DrugBank took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-drugbank took 5.655418157577515s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.7164335250854492s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0006189346313476562s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.2787153720855713s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.02013707160949707s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 2.86102294921875e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 8.58306884765625e-06s
INFO | --- Analysis for fu-berlin-ec-competition took 4.390209436416626s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.7491974830627441s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.2710559368133545s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.02056097984313965s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.43865966796875e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 4.5299530029296875e-06s
INFO | --- Analysis for fu-berlin-euraxess took 4.530797958374023s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.764521598815918s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.25383520126342773s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.020696163177490234s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0008742809295654297s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.677078247070312e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 4.76837158203125e-06s
INFO | --- Analysis for fu-berlin-eures took 4.56110143661499s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.7159051895141602s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.2667858600616455s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.020639419555664062s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.632110595703125e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 5.4836273193359375e-06s
INFO | --- Analysis for fu-berlin-eurostat took 5.125184059143066s
Availability | SPARQL endpoint availability check for MediCare took 0.7723736763000488s
Availability | VoID file availability check for MediCare took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for MediCare took 0.2773549556732178s
Reputation | Calculation of the PageRank for MediCare took 0.020556926727294922s
Interlinking | Calculation of Degree of Connection for MediCare took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.9114227294921875e-05s
Believability | Calculation of trust value for MediCare took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-medicare took 5.141790866851807s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.7122933864593506s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.24886035919189453s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.020678281784057617s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.724761962890625e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 7.152557373046875e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 4.370232105255127s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.7476849555969238s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.24789190292358398s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.020484447479248047s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.393692016601562e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 8.58306884765625e-06s
INFO | --- Analysis for fu-berlin-sider took 5.138787031173706s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.7699985504150391s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.2656087875366211s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.02064347267150879s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.581710815429688e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 1.3113021850585938e-05s
INFO | --- Analysis for fu-berlin-stitch took 4.448307991027832s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 4.124641418457031e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.2650444507598877s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.020772457122802734s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 3.409385681152344e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 7.62939453125e-06s
INFO | --- Analysis for galen_from_co-odeorg took 2.872366428375244s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 4.57763671875e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0006945133209228516s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.2688014507293701s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.020686626434326172s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.267692565917969e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 1.430511474609375e-05s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 5.408298492431641s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 4.315376281738281e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.24387884140014648s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.020559072494506836s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.00010275840759277344s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 8.106231689453125e-06s
INFO | --- Analysis for garnicaplywood took 3.1867246627807617s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 4.4345855712890625e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.24087858200073242s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.020404815673828125s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.00010371208190917969s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.2874603271484375e-05s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 7.3080878257751465s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.2908360958099365s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.000640869140625s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.28061580657958984s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 9.34600830078125e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for gemet took 4.772321701049805s
Availability | SPARQL endpoint availability check for gemet-annotated took 4.1961669921875e-05s
Availability | VoID file availability check for gemet-annotated took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.280261754989624s
Reputation | Calculation of the PageRank for gemet-annotated took 0.020803451538085938s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.838539123535156e-05s
Believability | Calculation of trust value for gemet-annotated took 1.239776611328125e-05s
INFO | --- Analysis for gemet-annotated took 3.012634515762329s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.7641987800598145s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.0003190040588378906s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.2652242183685303s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.020641803741455078s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 4.00543212890625e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 7.152557373046875e-06s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.109912395477295s
Availability | SPARQL endpoint availability check for geo.place took 4.1484832763671875e-05s
Availability | VoID file availability check for geo.place took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for geo.place took 0.24152231216430664s
Reputation | Calculation of the PageRank for geo.place took 0.02038097381591797s
Interlinking | Calculation of Degree of Connection for geo.place took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for geo.place took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for geo.place took 3.170967102050781e-05s
Believability | Calculation of trust value for geo.place took 9.298324584960938e-06s
INFO | --- Analysis for geo_place took 2.9518165588378906s
Availability | SPARQL endpoint availability check for geodomainwn took 4.267692565917969e-05s
Availability | VoID file availability check for geodomainwn took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.2654109001159668s
Reputation | Calculation of the PageRank for geodomainwn took 0.020766258239746094s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0008084774017333984s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 5.507469177246094e-05s
Believability | Calculation of trust value for geodomainwn took 7.62939453125e-06s
INFO | --- Analysis for geodomainwn took 3.7440903186798096s
Availability | SPARQL endpoint availability check for GeoEcuador took 8.988380432128906e-05s
Availability | VoID file availability check for GeoEcuador took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.2502408027648926s
Reputation | Calculation of the PageRank for GeoEcuador took 0.02090620994567871s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 7.534027099609375e-05s
Believability | Calculation of trust value for GeoEcuador took 7.3909759521484375e-06s
INFO | --- Analysis for geoecuador took 12.496481657028198s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.2409703731536865s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.2919278144836426s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.020662784576416016s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 6.985664367675781e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 6.67572021484375e-06s
INFO | --- Analysis for geographic-names-information-system-gnis took 47.67928886413574s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 4.601478576660156e-05s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.2792806625366211s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.020810842514038086s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 3.314018249511719e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 7.867813110351562e-06s
INFO | --- Analysis for geographic-openuplabs took 2.8307504653930664s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.5496327877044678s
Availability | VoID file availability check for GeoLinkedData took 0.0012731552124023438s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.24927353858947754s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.021404266357421875s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0010933876037597656s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 0.00011897087097167969s
Believability | Calculation of trust value for GeoLinkedData took 5.4836273193359375e-06s
INFO | --- Analysis for geolinkeddata took 3.9823246002197266s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.24307703971862793s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.001138448715209961s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 8.933732271194458s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.3691830635070801s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.16205549240112305s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.4619739055633545s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.20937204360961914s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.15889954566955566s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.1929771900177002s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.1014852523803711s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.09433126449584961s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.0832362174987793s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.09610557556152344s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 1.9831368923187256s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.10244226455688477s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.10052752494812012s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.14443564414978027s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.08586001396179199s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.07025527954101562s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.08673286437988281s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.405462265014648s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 7.176399230957031e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.06960153579711914s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.06929397583007812s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.08586406707763672s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.07652497291564941s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.06972718238830566s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.15759015083312988s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.16563129425048828s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.323951244354248s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 1.2492809295654297s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.0997471809387207s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06847286224365234s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.07525348663330078s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.28865599632263184s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.007401704788208008s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.23367881774902344s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.07647085189819336s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.20405983924865723s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5248332023620605s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 3.2591702938079834s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.547034740447998s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.7188780307769775s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.1786057949066162s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.07532835006713867s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 1.0792615413665771s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.60595703125s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.02737736701965332s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.654594421386719e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 0.7472212314605713s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 9.059906005859375e-06s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 113.98489189147949s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 4.3392181396484375e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.24232912063598633s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.020101547241210938s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0004839897155761719s
Believability | Calculation of trust value for GeoNames Semantic Web took 1.5497207641601562e-05s
INFO | --- Analysis for geonames-semantic-web took 3.1709930896759033s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.5582232475280762s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0007216930389404297s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.2807633876800537s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.023270368576049805s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0013251304626464844s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00019216537475585938s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 7.867813110351562e-06s
INFO | --- Analysis for geospecies took 5.8416852951049805s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.458427429199219e-05s
Availability | VoID file availability check for GeoWordNet took 0.0008244514465332031s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.27295756340026855s
Reputation | Calculation of the PageRank for GeoWordNet took 0.020587682723999023s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 5.054473876953125e-05s
Believability | Calculation of trust value for GeoWordNet took 8.106231689453125e-06s
INFO | --- Analysis for geowordnet took 7.320674419403076s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.16050148010253906s
Availability | VoID file availability check for German labor law thesaurus took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.2598733901977539s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.0205690860748291s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 8.082389831542969e-05s
Believability | Calculation of trust value for German labor law thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for german-labor-law-thesaurus took 2.598153829574585s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.482269287109375e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.26401448249816895s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.1961669921875e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 8.106231689453125e-06s
INFO | --- Analysis for germlex took 2.759732246398926s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.929220199584961s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.2568073272705078s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020617246627807617s
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.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.274482727050781e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 8.58306884765625e-06s
INFO | --- Analysis for gesis-thesoz took 11.78145980834961s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.3842854499816895s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.26074862480163574s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.02079629898071289s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.82012939453125e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for getty-aat took 15.90145754814148s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.283315896987915s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0005841255187988281s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.2634589672088623s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020453929901123047s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.245208740234375e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 6.67572021484375e-06s
INFO | --- Analysis for getty-tgn took 12.767586946487427s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 0.3916473388671875s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.2838461399078369s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.02058720588684082s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.0994415283203125e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 4.76837158203125e-06s
INFO | --- Analysis for gipuzkoademografia took 2.9677088260650635s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 4.5299530029296875e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.26602888107299805s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.02070760726928711s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.0994415283203125e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 7.152557373046875e-06s
INFO | --- Analysis for glastonbury-2011 took 5.6556236743927s
Availability | SPARQL endpoint availability check for Global Change Information System took 4.2438507080078125e-05s
Availability | VoID file availability check for Global Change Information System took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.25287866592407227s
Reputation | Calculation of the PageRank for Global Change Information System took 0.020416975021362305s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 2.8371810913085938e-05s
Believability | Calculation of trust value for Global Change Information System took 7.152557373046875e-06s
INFO | --- Analysis for global-change-information-system took 2.8939762115478516s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 4.291534423828125e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.2714071273803711s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.02036309242248535s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007970333099365234s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 4.839897155761719e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 6.9141387939453125e-06s
INFO | --- Analysis for global-hunger-index-2011 took 3.065112352371216s
Availability | SPARQL endpoint availability check for Glottolog took 4.3392181396484375e-05s
Availability | VoID file availability check for Glottolog took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for Glottolog took 0.24634408950805664s
Reputation | Calculation of the PageRank for Glottolog took 0.020690202713012695s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Glottolog took 5.1975250244140625e-05s
Believability | Calculation of trust value for Glottolog took 7.867813110351562e-06s
INFO | --- Analysis for glottolog took 6.391141414642334s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 4.506111145019531e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.2597367763519287s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00010514259338378906s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 1.2636184692382812e-05s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 9.759997844696045s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 4.172325134277344e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.2644352912902832s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.020757436752319336s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 2.8133392333984375e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 7.3909759521484375e-06s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 2.909275531768799s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 4.2438507080078125e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.26773548126220703s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.02054762840270996s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 3.0994415283203125e-05s
Believability | Calculation of trust value for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 8.58306884765625e-06s
INFO | --- Analysis for go_annotations_from_ncbi_and_ebi took 2.9420254230499268s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 4.363059997558594e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.2418668270111084s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020406484603881836s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.0067901611328125e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 7.867813110351562e-06s
INFO | --- Analysis for gold took 13.125787258148193s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 4.863739013671875e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.24655914306640625s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.02066826820373535s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.937980651855469e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 7.867813110351562e-06s
INFO | --- Analysis for googleart-wrapper took 2.6552014350891113s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.12604355812072754s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0003132820129394531s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.27664947509765625s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.02095317840576172s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0008521080017089844s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 4.267692565917969e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 7.152557373046875e-06s
INFO | --- Analysis for govagribus-denmark took 34.628204584121704s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.4355809688568115s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.2868385314941406s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 8.296966552734375e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 23.925391912460327s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.7925975322723389s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.26978516578674316s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.02031683921813965s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0008015632629394531s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 8.940696716308594e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 5.245208740234375e-06s
INFO | --- Analysis for govtrack took 10.303200721740723s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 4.4345855712890625e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0003044605255126953s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.2638981342315674s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.020415544509887695s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 5.745887756347656e-05s
Believability | Calculation of trust value for greek-administrative-geography took 8.344650268554688e-06s
INFO | --- Analysis for greek-administrative-geography took 2.578479528427124s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.15656757354736328s
Availability | VoID file availability check for Greek Wordnet took 0.00039124488830566406s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.2578084468841553s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.020257949829101562s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 3.790855407714844e-05s
Believability | Calculation of trust value for Greek Wordnet took 7.62939453125e-06s
INFO | --- Analysis for greek-wordnet took 2.539168119430542s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 4.267692565917969e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.24904417991638184s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.020718097686767578s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0008065700531005859s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.00011205673217773438s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 9.059906005859375e-06s
INFO | --- Analysis for green-competitiveness-gnoss took 8.147082805633545s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 1.2855403423309326s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.29570794105529785s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.02019953727722168s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.696846008300781e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 7.152557373046875e-06s
INFO | --- Analysis for grrp took 3.788280725479126s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.903033971786499s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.2768256664276123s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.020237207412719727s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 7.104873657226562e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 6.4373016357421875e-06s
INFO | --- Analysis for grrt took 4.426917791366577s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.8160552978515625e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0003466606140136719s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.2589411735534668s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.020387887954711914s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 6.699562072753906e-05s
Believability | Calculation of trust value for Project Gutenberg took 6.9141387939453125e-06s
INFO | --- Analysis for gutenberg took 10.846487760543823s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 4.172325134277344e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.25126075744628906s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.02053999900817871s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 2.9802322387695312e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 8.106231689453125e-06s
INFO | --- Analysis for hcls-knowledge-base took 2.873798370361328s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 6.175041198730469e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0003528594970703125s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.27625346183776855s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.020377635955810547s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 6.461143493652344e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 8.58306884765625e-06s
INFO | --- Analysis for heartfailure took 39.46390986442566s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 22.008214473724365s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.000720977783203125s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.30194759368896484s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.020345449447631836s
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.0728836059570312e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 3.647804260253906e-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.867813110351562e-06s
INFO | --- Analysis for hebis-bibliographic-resources took 121.35723519325256s
Availability | SPARQL endpoint availability check for Hedatuz took 0.25988197326660156s
Availability | VoID file availability check for Hedatuz took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.2697408199310303s
Reputation | Calculation of the PageRank for Hedatuz took 0.02042245864868164s
Interlinking | Calculation of Degree of Connection for Hedatuz took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 3.719329833984375e-05s
Believability | Calculation of trust value for Hedatuz took 7.152557373046875e-06s
INFO | --- Analysis for hedatuz took 2.984407901763916s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.12198066711425781s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.2582221031188965s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.020707368850708008s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00013828277587890625s
Believability | Calculation of trust value for Hellenic Fire Brigade took 5.9604644775390625e-06s
INFO | --- Analysis for hellenic-fire-brigade took 2.5857861042022705s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.02288198471069336s
Availability | VoID file availability check for Hellenic Police took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.28661322593688965s
Reputation | Calculation of the PageRank for Hellenic Police took 0.02031421661376953s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.0001266002655029297s
Believability | Calculation of trust value for Hellenic Police took 5.4836273193359375e-06s
INFO | --- Analysis for hellenic-police took 2.5749032497406006s
Availability | SPARQL endpoint availability check for Homologene took 4.363059997558594e-05s
Availability | VoID file availability check for Homologene took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for Homologene took 0.26943492889404297s
Reputation | Calculation of the PageRank for Homologene took 0.02138543128967285s
Interlinking | Calculation of Degree of Connection for Homologene took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Homologene took 0.0008771419525146484s
Interlinking | Calculation of Clustering coefficient for Homologene took 3.790855407714844e-05s
Believability | Calculation of trust value for Homologene took 8.821487426757812e-06s
INFO | --- Analysis for homologene took 3.0433266162872314s
Availability | SPARQL endpoint availability check for Noticias Universia took 4.1961669921875e-05s
Availability | VoID file availability check for Noticias Universia took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.25539731979370117s
Reputation | Calculation of the PageRank for Noticias Universia took 0.022059202194213867s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0008108615875244141s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 3.528594970703125e-05s
Believability | Calculation of trust value for Noticias Universia took 8.58306884765625e-06s
INFO | --- Analysis for http-data-noticias-universia-net took 2.923436164855957s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 4.172325134277344e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.00028777122497558594s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.2589445114135742s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.02057623863220215s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0009145736694335938s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 3.790855407714844e-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.8711130619049072s
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.0003552436828613281s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.2697181701660156s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.020369529724121094s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0007941722869873047s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 4.0531158447265625e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 8.344650268554688e-06s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 2.925123453140259s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 8.940696716308594e-05s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.00031948089599609375s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.26868247985839844s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.020368576049804688s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 2.86102294921875e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 8.58306884765625e-06s
INFO | --- Analysis for hud-library-usagedata took 2.873957872390747s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.4012775421142578s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.2785830497741699s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.020870447158813477s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0008485317230224609s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00011491775512695312s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 7.867813110351562e-06s
INFO | --- Analysis for hungarian-national-library-catalog took 4.07004714012146s
Availability | SPARQL endpoint availability check for IATE RDF took 4.76837158203125e-05s
Availability | VoID file availability check for IATE RDF took 0.0006742477416992188s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.2902858257293701s
Reputation | Calculation of the PageRank for IATE RDF took 0.020773887634277344s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 4.3392181396484375e-05s
Believability | Calculation of trust value for IATE RDF took 8.58306884765625e-06s
INFO | --- Analysis for iate-rdf took 2.8445167541503906s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.117417573928833s
Availability | VoID file availability check for IATI as Linked Data took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.278583288192749s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.02050042152404785s
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.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 9.012222290039062e-05s
Believability | Calculation of trust value for IATI as Linked Data took 7.62939453125e-06s
INFO | --- Analysis for iati-as-linked-data took 13.123271942138672s
Availability | SPARQL endpoint availability check for ICANE took 0.450042724609375s
Availability | VoID file availability check for ICANE took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for ICANE took 0.28383517265319824s
Reputation | Calculation of the PageRank for ICANE took 0.02569270133972168s
Interlinking | Calculation of Degree of Connection for ICANE took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for ICANE took 0.000978231430053711s
Interlinking | Calculation of Clustering coefficient for ICANE took 9.965896606445312e-05s
Believability | Calculation of trust value for ICANE took 5.245208740234375e-06s
INFO | --- Analysis for icane took 3.759631633758545s
Availability | SPARQL endpoint availability check for ichoose took 0.1285238265991211s
Availability | VoID file availability check for ichoose took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for ichoose took 0.2556130886077881s
Reputation | Calculation of the PageRank for ichoose took 0.020540714263916016s
Interlinking | Calculation of Degree of Connection for ichoose took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for ichoose took 6.818771362304688e-05s
Believability | Calculation of trust value for ichoose took 7.62939453125e-06s
INFO | --- Analysis for ichoose took 41.9479124546051s
Availability | SPARQL endpoint availability check for Identifiers.org took 5.14984130859375e-05s
Availability | VoID file availability check for Identifiers.org took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Identifiers.org took 0.2793853282928467s
Reputation | Calculation of the PageRank for Identifiers.org took 0.02065896987915039s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 4.1484832763671875e-05s
Believability | Calculation of trust value for Identifiers.org took 9.059906005859375e-06s
INFO | --- Analysis for identifiers-org took 2.8796274662017822s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 4.57763671875e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.268963098526001s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.020515918731689453s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007600784301757812s
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 7.3909759521484375e-06s
INFO | --- Analysis for idreffr took 4.148601055145264s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.926821231842041s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.2723958492279053s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.02158045768737793s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 5.173683166503906e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 7.152557373046875e-06s
INFO | --- Analysis for ids took 3.913177967071533s
Availability | SPARQL endpoint availability check for ietflang took 4.4345855712890625e-05s
Availability | VoID file availability check for ietflang took 0.000640869140625s
Completeness | Calculation of interlinking completeness for ietflang took 0.25340843200683594s
Reputation | Calculation of the PageRank for ietflang took 0.020263195037841797s
Interlinking | Calculation of Degree of Connection for ietflang took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ietflang took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.506111145019531e-05s
Believability | Calculation of trust value for ietflang took 7.152557373046875e-06s
INFO | --- Analysis for ietflang took 12.671271324157715s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 0.7216649055480957s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.2712724208831787s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.02046513557434082s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 3.1948089599609375e-05s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 6.67572021484375e-06s
INFO | --- Analysis for iislod-test took 3.146275043487549s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.0784459114074707s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0007040500640869141s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 22.07797861099243s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.474771022796631s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 9.723211765289307s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.3666093349456787s
Versatility | Languages check for Imagesnippets Image Descriptions took 19.446250915527344s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.181118726730347s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.6903555393218994s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7086656093597412s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.7097721099853516s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7158722877502441s
License | MR license check for Imagesnippets Image Descriptions took 0.7267577648162842s
License | HR license check for Imagesnippets Image Descriptions took 30.742162942886353s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.6923549175262451s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.9471449851989746s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.4107906818389893s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.6986515522003174s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.7238080501556396s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.6907422542572021s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.713863849639893s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 7.510185241699219e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.6890425682067871s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.7046895027160645s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7094411849975586s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6982765197753906s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.7309365272521973s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.3872110843658447s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.3969519138336182s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 32.73204970359802s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.7186946868896484s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.708005428314209s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.6868271827697754s
Accuracy | Check Empty annotation labels for Imagesnippets Image Descriptions took 12.27440881729126s
Accuracy | Check White space in annotation for Imagesnippets Image Descriptions took 2.270357370376587s
Accuracy | Check Datatype consistency for Imagesnippets Image Descriptions took 4.505730628967285s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.6948111057281494s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.592373609542847s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 5.138273239135742s
Consistency | Check Invalid usage of undefined classes for Imagesnippets Image Descriptions took 1.4906644821166992s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.350272417068481s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 2.8857409954071045s
Security | Sign check for Imagesnippets Image Descriptions took 0.703394889831543s
Availability | Check URIs Dereferenciability for Imagesnippets Image Descriptions took 24.737054586410522s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.35268688201904297s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.0211179256439209s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 8.559226989746094e-05s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 1.430511474609375e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 8.344650268554688e-06s
INFO | --- Analysis for imagesnippets took 376.01913189888s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.4837820529937744s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.7073428630828857s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.02033519744873047s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 8.869171142578125e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for imf-linked-data took 3.8585681915283203s
Availability | SPARQL endpoint availability check for IMGpedia took 4.029273986816406e-05s
Availability | VoID file availability check for IMGpedia took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.28092241287231445s
Reputation | Calculation of the PageRank for IMGpedia took 0.020840167999267578s
Interlinking | Calculation of Degree of Connection for IMGpedia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IMGpedia took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 3.0279159545898438e-05s
Believability | Calculation of trust value for IMGpedia took 3.218650817871094e-05s
INFO | --- Analysis for imgpedia took 3.0174062252044678s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 4.267692565917969e-05s
Availability | VoID file availability check for Import Status of GMO Crops took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 0.27240467071533203s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.020763158798217773s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.0008103847503662109s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 3.457069396972656e-05s
Believability | Calculation of trust value for Import Status of GMO Crops took 7.62939453125e-06s
INFO | --- Analysis for import-status-of-gmo-crops took 2.9878532886505127s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 4.220008850097656e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 0.2829155921936035s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.021047592163085938s
Interlinking | Calculation of Degree of Connection for Income and production cost of grape by year took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Income and production cost of grape by year took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 3.0279159545898438e-05s
Believability | Calculation of trust value for Income and production cost of grape by year took 7.867813110351562e-06s
INFO | --- Analysis for income-and-production-cost-of-grape-by-year took 2.9336981773376465s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 4.1484832763671875e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.2508697509765625s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.02078413963317871s
Interlinking | Calculation of Degree of Connection for Income and production cost of pear by year took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Income and production cost of pear by year took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Income and production cost of pear by year took 2.956390380859375e-05s
Believability | Calculation of trust value for Income and production cost of pear by year took 8.344650268554688e-06s
INFO | --- Analysis for income-and-production-cost-of-pear-by-year took 2.9289166927337646s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 4.315376281738281e-05s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.26554298400878906s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.020457983016967773s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 3.075599670410156e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.2636184692382812e-05s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 2.961639165878296s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 4.553794860839844e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0006377696990966797s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.2669992446899414s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.020524024963378906s
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.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00011491775512695312s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 1.1920928955078125e-05s
INFO | --- Analysis for ineverycrea took 16.998432159423828s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 4.5299530029296875e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0010042190551757812s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.28035902976989746s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.020518064498901367s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.512901306152344e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.3113021850585938e-05s
INFO | --- Analysis for ineverycrea-argentina took 10.62892460823059s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 0.04620552062988281s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0006871223449707031s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.28727221488952637s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.02028179168701172s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 7.081031799316406e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for influence-tracker-dataset took 13.034680843353271s
Availability | SPARQL endpoint availability check for INSEMTIVES took 4.363059997558594e-05s
Availability | VoID file availability check for INSEMTIVES took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.28647565841674805s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.020940303802490234s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 3.314018249511719e-05s
Believability | Calculation of trust value for INSEMTIVES took 8.58306884765625e-06s
INFO | --- Analysis for insemtives took 2.9626576900482178s
Availability | SPARQL endpoint availability check for instagram.person took 6.532669067382812e-05s
Availability | VoID file availability check for instagram.person took 0.0002238750457763672s
Completeness | Calculation of interlinking completeness for instagram.person took 0.25639867782592773s
Reputation | Calculation of the PageRank for instagram.person took 0.020195960998535156s
Interlinking | Calculation of Degree of Connection for instagram.person took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for instagram.person took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for instagram.person took 3.0279159545898438e-05s
Believability | Calculation of trust value for instagram.person took 8.106231689453125e-06s
INFO | --- Analysis for instagram_person took 2.914797782897949s
Availability | SPARQL endpoint availability check for instagram.videoobject took 4.124641418457031e-05s
Availability | VoID file availability check for instagram.videoobject took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 0.27701473236083984s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.020395994186401367s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 2.8848648071289062e-05s
Believability | Calculation of trust value for instagram.videoobject took 7.867813110351562e-06s
INFO | --- Analysis for instagram_videoobject took 2.9762661457061768s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 4.172325134277344e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.00022721290588378906s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.2808492183685303s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.020348072052001953s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 2.9087066650390625e-05s
Believability | Calculation of trust value for Instance Hub Countries took 6.67572021484375e-06s
INFO | --- Analysis for instance-hub-countries took 2.926877975463867s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.291534423828125e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.2722954750061035s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.020375490188598633s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 2.765655517578125e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 2.285907745361328s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 4.124641418457031e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.2753922939300537s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.0202486515045166s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 2.86102294921875e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 6.9141387939453125e-06s
INFO | --- Analysis for instance-hub-organizations took 2.8756825923919678s
Availability | SPARQL endpoint availability check for Instance Hub People took 4.124641418457031e-05s
Availability | VoID file availability check for Instance Hub People took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.2691643238067627s
Reputation | Calculation of the PageRank for Instance Hub People took 0.020390748977661133s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 2.8371810913085938e-05s
Believability | Calculation of trust value for Instance Hub People took 6.4373016357421875e-06s
INFO | --- Analysis for instance-hub-people took 2.886715888977051s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 8.130073547363281e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.000244140625s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.24471664428710938s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.020358562469482422s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 2.8848648071289062e-05s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-us-civil-servants took 2.9403774738311768s
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.00028061866760253906s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.2655947208404541s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.02042102813720703s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 2.9802322387695312e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 7.867813110351562e-06s
INFO | --- Analysis for instance-hub-us-congressional-committees took 2.957066059112549s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 8.821487426757812e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.28150486946105957s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.020665407180786133s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 3.0994415283203125e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-us-congressional-districts took 2.903277635574341s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 4.124641418457031e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.00036025047302246094s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.2535717487335205s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.022200822830200195s
Interlinking | Calculation of Degree of Connection for Instance Hub US Crops took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Crops took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 3.457069396972656e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 7.62939453125e-06s
INFO | --- Analysis for instance-hub-us-crops took 2.9669671058654785s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 4.172325134277344e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.2776005268096924s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.020582914352416992s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 3.123283386230469e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 1.3113021850585938e-05s
INFO | --- Analysis for instance-hub-us-federal-agencies took 3.0159811973571777s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 4.220008850097656e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.2499711513519287s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.020404338836669922s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 3.147125244140625e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-us-states-and-territories took 3.0058982372283936s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 4.220008850097656e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.27909183502197266s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.020496129989624023s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 3.170967102050781e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 1.2874603271484375e-05s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 2.9825406074523926s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 7.05718994140625e-05s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.2850453853607178s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.02048945426940918s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 3.0994415283203125e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 8.58306884765625e-06s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 3.014835834503174s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.744529724121094e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0003299713134765625s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.2561628818511963s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.020496368408203125s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0001049041748046875s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 8.58306884765625e-06s
INFO | --- Analysis for interactivemaps-gnoss took 9.185125827789307s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 4.291534423828125e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.3038163185119629s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.02034735679626465s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 3.0517578125e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 7.62939453125e-06s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 2.9662857055664062s
Availability | SPARQL endpoint availability check for intervalue took 0.29439783096313477s
Availability | VoID file availability check for intervalue took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for intervalue took 0.25385165214538574s
Reputation | Calculation of the PageRank for intervalue took 0.020280122756958008s
Interlinking | Calculation of Degree of Connection for intervalue took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.794929504394531e-05s
Believability | Calculation of trust value for intervalue took 7.152557373046875e-06s
INFO | --- Analysis for intervalue took 2.6743998527526855s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.4345855712890625e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0007605552673339844s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.25859832763671875s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.020858049392700195s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.458427429199219e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 8.106231689453125e-06s
INFO | --- Analysis for iptc-newscodes took 3.415066957473755s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 4.363059997558594e-05s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.2808833122253418s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.02035832405090332s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 2.86102294921875e-05s
Believability | Calculation of trust value for Irstea Weather Dataset of the Montoldre Experimental Farm took 7.867813110351562e-06s
INFO | --- Analysis for irstea-weather-dataset-of-the-montoldre-experimental-farm took 2.924180746078491s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 2.663996458053589s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0007274150848388672s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.25380873680114746s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020410537719726562s
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.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.703636169433594e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 8.106231689453125e-06s
INFO | --- Analysis for iserve took 9.218963623046875s
Availability | SPARQL endpoint availability check for ISIC V4 took 20.808252334594727s
Availability | VoID file availability check for ISIC V4 took 0.0009272098541259766s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.28055644035339355s
Reputation | Calculation of the PageRank for ISIC V4 took 0.02067255973815918s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 4.2438507080078125e-05s
Believability | Calculation of trust value for ISIC V4 took 5.245208740234375e-06s
INFO | --- Analysis for isic-v4 took 114.35283207893372s
Availability | SPARQL endpoint availability check for Isidore took 4.0531158447265625e-05s
Availability | VoID file availability check for Isidore took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Isidore took 0.2693593502044678s
Reputation | Calculation of the PageRank for Isidore took 0.020165443420410156s
Interlinking | Calculation of Degree of Connection for Isidore took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Isidore took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Isidore took 2.9325485229492188e-05s
Believability | Calculation of trust value for Isidore took 9.775161743164062e-06s
INFO | --- Analysis for isidore took 2.8742661476135254s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 4.1484832763671875e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.0002846717834472656s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.27993178367614746s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.020316362380981445s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 2.9087066650390625e-05s
Believability | Calculation of trust value for Linked ISO 3166-2 Data took 8.106231689453125e-06s
INFO | --- Analysis for iso-3166-2-data took 2.963756799697876s
Availability | SPARQL endpoint availability check for ISOcat took 4.291534423828125e-05s
Availability | VoID file availability check for ISOcat took 0.0004024505615234375s
Completeness | Calculation of interlinking completeness for ISOcat took 0.3574850559234619s
Reputation | Calculation of the PageRank for ISOcat took 0.020521879196166992s
Interlinking | Calculation of Degree of Connection for ISOcat took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for ISOcat took 5.936622619628906e-05s
Believability | Calculation of trust value for ISOcat took 7.62939453125e-06s
INFO | --- Analysis for isocat took 34.05999231338501s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 4.291534423828125e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.28823280334472656s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.02026081085205078s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.314018249511719e-05s
Believability | Calculation of trust value for ISOcat-metadata took 7.62939453125e-06s
INFO | --- Analysis for isocat-metadata took 4.818743944168091s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 4.172325134277344e-05s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 0.27694201469421387s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.0009281635284423828s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 3.314018249511719e-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.922765016555786s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3488650321960449s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0006103515625s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 6.272781610488892s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.7955703735351562s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20015811920166016s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 3.0699877738952637s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 90.70845317840576s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2750527858734131s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.12071514129638672s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20122981071472168s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15014052391052246s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.17062687873840332s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.23202967643737793s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.96912860870361s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.22350287437438965s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.3075103759765625s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.40619754791259766s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.19853854179382324s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1813046932220459s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15078425407409668s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.75640344619751s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.104873657226562e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.22050070762634277s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2681899070739746s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.4550936222076416s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.47749996185302734s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20353984832763672s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3369636535644531s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1467435359954834s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 13.82959794998169s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 6.198883056640625e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14177393913269043s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.17283058166503906s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15322256088256836s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.8882203102111816s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.31737208366394043s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.26937007904052734s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.13657164573669434s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.669166088104248s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9892134666442871s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 3.25644850730896s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.3232548236846924s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.82363748550415s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2892277240753174s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.22741436958312988s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1744072437286377s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 14.617968320846558s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.7554116249084473s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.020868539810180664s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.0013580322265625e-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.00012159347534179688s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.430511474609375e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.821487426757812e-06s
INFO | --- Analysis for ispra-lod-place took 459.0743396282196s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 4.172325134277344e-05s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.2933385372161865s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.021204710006713867s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 3.838539123535156e-05s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 8.344650268554688e-06s
INFO | --- Analysis for ispra-lod-rmn took 4.317739725112915s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.18318748474121094s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0005800724029541016s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 6.150483846664429s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.7293810844421387s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.22780156135559082s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 3.1100034713745117s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 92.01171445846558s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.17059683799743652s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.12154245376586914s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.18181610107421875s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.18276762962341309s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.15119719505310059s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.2074143886566162s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 91.08971309661865s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.23075270652770996s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.4261205196380615s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.45975565910339355s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.19762110710144043s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.21248459815979004s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.14499211311340332s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.609868288040161s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 0.0002334117889404297s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.20141148567199707s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.3093681335449219s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.536768913269043s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.5368227958679199s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.20852231979370117s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.3183128833770752s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.16977405548095703s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 13.990586996078491s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 6.198883056640625e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.14167428016662598s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.16368818283081055s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.16289877891540527s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 3.333498477935791s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.3151891231536865s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.27359604835510254s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.18939709663391113s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 9.66751480102539s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.9616224765777588s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 3.1946966648101807s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.37233567237854s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.96970796585083s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.294511079788208s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.19257426261901855s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.17595458030700684s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 10.90688443183899s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 1.3793134689331055s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.020797014236450195s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007245540618896484s
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.9073486328125e-06s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 8.106231689453125e-06s
INFO | --- Analysis for ispra-lod-ron took 456.82365226745605s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 4.5299530029296875e-05s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 0.25403809547424316s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 2.9802322387695312e-05s
Believability | Calculation of trust value for ISPRA - Soil Consumption Indicators in Italy took 6.67572021484375e-06s
INFO | --- Analysis for ispra-lod-sc took 4.306554079055786s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 1.7416126728057861s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.2575109004974365s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.020560741424560547s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.606910705566406e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 5.245208740234375e-06s
INFO | --- Analysis for istat-immigration took 4.082388639450073s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 5.221366882324219e-05s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 0.7377545833587646s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.020390033721923828s
Interlinking | Calculation of Degree of Connection for ISTAT Immigrazione (Linkedopendata.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISTAT Immigrazione (Linkedopendata.it) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 3.0517578125e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 7.62939453125e-06s
INFO | --- Analysis for istat-immigrazione took 3.436431884765625s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.13338685035705566s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.28249692916870117s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.020406246185302734s
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.00072479248046875s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 2.956390380859375e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 4.76837158203125e-06s
INFO | --- Analysis for it-aifa-drug-prices took 3.2480411529541016s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.4051759243011475s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.2693140506744385s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.020354032516479492s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007977485656738281s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.295608520507812e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 6.67572021484375e-06s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 4.2639970779418945s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 4.100799560546875e-05s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.2615342140197754s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.020506620407104492s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 3.0994415283203125e-05s
Believability | Calculation of trust value for Academic Bibliography data available from Acta Cryst E took 8.58306884765625e-06s
INFO | --- Analysis for iucr-acta-cryst-e took 2.937532901763916s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 8.916854858398438e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.2727367877960205s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.020369768142700195s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 2.7894973754882812e-05s
Believability | Calculation of trust value for IWMI Research Reports took 7.152557373046875e-06s
INFO | --- Analysis for iwmi-research-reports took 2.9839766025543213s
Availability | SPARQL endpoint availability check for IWN took 4.410743713378906e-05s
Availability | VoID file availability check for IWN took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for IWN took 0.2728872299194336s
Reputation | Calculation of the PageRank for IWN took 0.020346641540527344s
Interlinking | Calculation of Degree of Connection for IWN took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IWN took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for IWN took 3.647804260253906e-05s
Believability | Calculation of trust value for IWN took 7.867813110351562e-06s
INFO | --- Analysis for iwn took 5.869004011154175s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 4.220008850097656e-05s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.0002982616424560547s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.26897144317626953s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.021135330200195312s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.000997304916381836s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 3.528594970703125e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 8.106231689453125e-06s
INFO | --- Analysis for j-global-knowledge took 2.9219696521759033s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 4.792213439941406e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.25335264205932617s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.021106958389282227s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 3.218650817871094e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 7.867813110351562e-06s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 2.9002768993377686s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 9.103125095367432s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.00037407875061035156s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.24725604057312012s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.02022266387939453s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 5.9604644775390625e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 8.106231689453125e-06s
INFO | --- Analysis for jamendo-dbtune took 25.253544569015503s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 7.700920104980469e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.2784430980682373s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.0206906795501709s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 5.269050598144531e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for japan-radioactivity-stat took 4.34323263168335s
Availability | SPARQL endpoint availability check for JEL Classification took 4.696846008300781e-05s
Availability | VoID file availability check for JEL Classification took 0.00038433074951171875s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.2752816677093506s
Reputation | Calculation of the PageRank for JEL Classification took 0.020152568817138672s
Interlinking | Calculation of Degree of Connection for JEL Classification took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 2.8371810913085938e-05s
Believability | Calculation of trust value for JEL Classification took 7.152557373046875e-06s
INFO | --- Analysis for jel-classification took 4.6952009201049805s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.0915164947509766s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0006916522979736328s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.25592875480651855s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.02043008804321289s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.0040740966796875e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 5.9604644775390625e-06s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 6.844374895095825s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.7793743610382s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.2550656795501709s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.020695209503173828s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 7.581710815429688e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 6.9141387939453125e-06s
INFO | --- Analysis for jita took 540.6108748912811s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 4.363059997558594e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.00029659271240234375s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.2640552520751953s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.020549774169921875s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 3.170967102050781e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 7.867813110351562e-06s
INFO | --- Analysis for jmdict took 4.862047433853149s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.073899030685425s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0007519721984863281s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.27527952194213867s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.020684242248535156s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 9.393692016601562e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 7.62939453125e-06s
INFO | --- Analysis for john-goodwins-family-tree took 63.9916934967041s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 1.0595502853393555s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.26618337631225586s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.020595550537109375s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.794929504394531e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 7.152557373046875e-06s
INFO | --- Analysis for jrc-names-mlode took 3.93980073928833s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.363059997558594e-05s
Availability | VoID file availability check for JudaicaLink took 0.0006742477416992188s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.27982378005981445s
Reputation | Calculation of the PageRank for JudaicaLink took 0.02058243751525879s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 9.965896606445312e-05s
Believability | Calculation of trust value for JudaicaLink took 7.62939453125e-06s
INFO | --- Analysis for judaicalink took 22.977262496948242s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 4.1961669921875e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.00038623809814453125s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.2628345489501953s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.022769927978515625s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.0008382797241210938s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 3.719329833984375e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 8.106231689453125e-06s
INFO | --- Analysis for kaist-silver-standard-corpus took 3.2330963611602783s
Availability | SPARQL endpoint availability check for KAKEN took 4.1484832763671875e-05s
Availability | VoID file availability check for KAKEN took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for KAKEN took 0.6648585796356201s
Reputation | Calculation of the PageRank for KAKEN took 0.02051377296447754s
Interlinking | Calculation of Degree of Connection for KAKEN took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for KAKEN took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for KAKEN took 3.218650817871094e-05s
Believability | Calculation of trust value for KAKEN took 7.3909759521484375e-06s
INFO | --- Analysis for kaken took 3.2574455738067627s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.06653666496276855s
Availability | VoID file availability check for Kallikratis municipalities took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.24999260902404785s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.0204160213470459s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.1552734375e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 5.4836273193359375e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.3784170150756836s
Availability | SPARQL endpoint availability check for Openflights Routes took 4.172325134277344e-05s
Availability | VoID file availability check for Openflights Routes took 0.0002932548522949219s
Completeness | Calculation of interlinking completeness for Openflights Routes took 0.25513362884521484s
Reputation | Calculation of the PageRank for Openflights Routes took 0.020784616470336914s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 3.0040740966796875e-05s
Believability | Calculation of trust value for Openflights Routes took 9.059906005859375e-06s
INFO | --- Analysis for kasabi-openflights-routes took 2.8046703338623047s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 4.458427429199219e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.2897031307220459s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.020940065383911133s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 7.009506225585938e-05s
Believability | Calculation of trust value for Klappstuhlclub took 4.76837158203125e-06s
INFO | --- Analysis for klappstuhlclub took 12.575414657592773s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.896386861801147s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.2846977710723877s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.0202329158782959s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 6.008148193359375e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 7.152557373046875e-06s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.393057346343994s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.315376281738281e-05s
Availability | VoID file availability check for Knowledge Forest took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.26032018661499023s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020631074905395508s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.0994415283203125e-05s
Believability | Calculation of trust value for Knowledge Forest took 7.867813110351562e-06s
INFO | --- Analysis for knowledge-map took 2.919616460800171s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 4.38690185546875e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0005991458892822266s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.2677009105682373s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.02042102813720703s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.985664367675781e-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.378035306930542s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 4.124641418457031e-05s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.000408172607421875s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.2816803455352783s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.020627498626708984s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 6.9141387939453125e-06s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 2.918044328689575s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 4.076957702636719e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.27825164794921875s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.0205686092376709s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 2.9087066650390625e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 7.152557373046875e-06s
INFO | --- Analysis for ktr took 2.971956253051758s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.08834481239318848s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.0012273788452148438s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.2551305294036865s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.020101547241210938s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.528594970703125e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 7.62939453125e-06s
INFO | --- Analysis for kupkb took 10.341451168060303s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 4.291534423828125e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.2552788257598877s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.020538330078125s
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.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 2.8848648071289062e-05s
Believability | Calculation of trust value for Léčivé přípravky ze SÚKL took 7.867813110351562e-06s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 2.9037973880767822s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 10.332855939865112s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.26976752281188965s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.020307302474975586s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 7.224082946777344e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 7.3909759521484375e-06s
INFO | --- Analysis for l3s-dblp took 48.76844382286072s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 23.35138440132141s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.25714111328125s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.02067422866821289s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 6.890296936035156e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for lak-dataset took 66.87788319587708s
Availability | SPARQL endpoint availability check for LATC Linksets took 4.100799560546875e-05s
Availability | VoID file availability check for LATC Linksets took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for LATC Linksets took 0.25304317474365234s
Reputation | Calculation of the PageRank for LATC Linksets took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 3.0517578125e-05s
Believability | Calculation of trust value for LATC Linksets took 8.106231689453125e-06s
INFO | --- Analysis for latc-linksets took 2.8850436210632324s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 4.267692565917969e-05s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 0.28386831283569336s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for Leipzig Corpora Collection (LCC) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Leipzig Corpora Collection (LCC) took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 7.867813110351562e-06s
INFO | --- Analysis for lcc took 2.968691110610962s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 4.57763671875e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0013301372528076172s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.26745152473449707s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.020781278610229492s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00011777877807617188s
Believability | Calculation of trust value for Library of Congress Subject Headings took 8.58306884765625e-06s
INFO | --- Analysis for lcsh took 5.743110418319702s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 4.291534423828125e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.295363187789917s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.020723342895507812s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.153915405273438e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 7.3909759521484375e-06s
INFO | --- Analysis for lcsubjects took 2.6255598068237305s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 8.535385131835938e-05s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 0.2379441261291504s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.02045583724975586s
Interlinking | Calculation of Degree of Connection for LDQM - Accessibility of DBpedia resources took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LDQM - Accessibility of DBpedia resources took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 2.86102294921875e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 7.3909759521484375e-06s
INFO | --- Analysis for ldqm-dbpedia-2016 took 2.88211989402771s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 4.506111145019531e-05s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 0.2669408321380615s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.02031993865966797s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Eng took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Eng took 0.0008573532104492188s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Eng took 3.2901763916015625e-05s
Believability | Calculation of trust value for Learned Genre Ontology Eng took 9.059906005859375e-06s
INFO | --- Analysis for learned-genre-ontology-eng took 2.8768298625946045s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 4.291534423828125e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.2375168800354004s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.020706653594970703s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Intl took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Intl took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 2.9802322387695312e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 7.3909759521484375e-06s
INFO | --- Analysis for learned-genre-ontology-intl took 2.8589344024658203s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 4.100799560546875e-05s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.2500145435333252s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.020547151565551758s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 2.86102294921875e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 6.9141387939453125e-06s
INFO | --- Analysis for legislation-openuplabs took 2.8510634899139404s
Availability | SPARQL endpoint availability check for lemonUby took 4.3392181396484375e-05s
Availability | VoID file availability check for lemonUby took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for lemonUby took 0.2724940776824951s
Reputation | Calculation of the PageRank for lemonUby took 0.020226478576660156s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.461143493652344e-05s
Believability | Calculation of trust value for lemonUby took 7.152557373046875e-06s
INFO | --- Analysis for lemonuby took 3.351918935775757s
Availability | SPARQL endpoint availability check for LemonWiktionary took 4.2438507080078125e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.2914137840270996s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.02034616470336914s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.4332275390625e-05s
Believability | Calculation of trust value for LemonWiktionary took 7.867813110351562e-06s
INFO | --- Analysis for lemonwiktionary took 4.443734884262085s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.2491862773895264s
Availability | VoID file availability check for LEXIN-RDF took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.2590057849884033s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.02046656608581543s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007197856903076172s
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 5.705382823944092s
Availability | SPARQL endpoint availability check for lexinfo took 4.9591064453125e-05s
Availability | VoID file availability check for lexinfo took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for lexinfo took 0.26004600524902344s
Reputation | Calculation of the PageRank for lexinfo took 0.02034163475036621s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for lexinfo took 8.797645568847656e-05s
Believability | Calculation of trust value for lexinfo took 7.152557373046875e-06s
INFO | --- Analysis for lexinfo took 2.759129524230957s
Availability | SPARQL endpoint availability check for Lexvo took 4.3392181396484375e-05s
Availability | VoID file availability check for Lexvo took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for Lexvo took 0.2477095127105713s
Reputation | Calculation of the PageRank for Lexvo took 0.02067255973815918s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00017595291137695312s
Believability | Calculation of trust value for Lexvo took 7.62939453125e-06s
INFO | --- Analysis for lexvo took 43.06365942955017s
Availability | SPARQL endpoint availability check for LIBRIS took 0.36075472831726074s
Availability | VoID file availability check for LIBRIS took 0.0003714561462402344s
Extra | Recovery of all triples for LIBRIS took 6.349425792694092s
Performance | Total latancy measurement for LIBRIS took 0.7490739822387695s
Amount of data | Number of triples check for LIBRIS took 21.363987684249878s
Interoperability | New terms check for LIBRIS took 15.650009393692017s
Versatility | Languages check for LIBRIS took 0.1875770092010498s
Interpretability | Number of blank nodes check for LIBRIS took 300.09073209762573s
Security | Check HTTPS for LIBRIS took 0.37165188789367676s
Interpretability | RDF structures check for LIBRIS took 0.5316922664642334s
Versatility | Serialization formats check for LIBRIS took 0.34929466247558594s
Availability | RDF dump link check for LIBRIS took 0.15446043014526367s
License | MR license check for LIBRIS took 0.4545328617095947s
License | HR license check for LIBRIS took 0.35398006439208984s
Amount of data | Number of property check for LIBRIS took 0.18709444999694824s
Understandability | Number of label check for LIBRIS took 1.0092480182647705s
Understandability | URI regex check for LIBRIS took 0.5090467929840088s
Understandability | Vocabs check for LIBRIS took 0.16395783424377441s
Verifiability | Authors check for LIBRIS took 0.26182007789611816s
Verifiability | Publishers check for LIBRIS took 0.24883246421813965s
Performance | Throughput check for LIBRIS took 11.222365617752075s
Amount of data | Check the number of entities for LIBRIS took 7.319450378417969e-05s
Verifiability | Contribs. check for LIBRIS took 0.24787211418151855s
Interlinking | sameAs chians check for LIBRIS took 0.35610437393188477s
Interlinking | skos check for LIBRIS took 0.528569221496582s
Interlinking | skos check for LIBRIS took 0.14663410186767578s
Timeliness | dataset update frequency check for LIBRIS took 0.18976378440856934s
Currency | Creation date check for LIBRIS took 0.4410672187805176s
Currency | Modification date check for LIBRIS took 0.6394703388214111s
Rep.Conc. | URIs length for LIBRIS took 80.23139595985413s
Interoperability | New vocabularies check for LIBRIS took 6.4373016357421875e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.17941641807556152s
Accuracy | Check Functional Property for LIBRIS took 0.18724536895751953s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.1416182518005371s
Accuracy | Check Datatype consistency for LIBRIS took 0.27331066131591797s
Consistency | Disjoint class check for LIBRIS took 0.1944432258605957s
Consistency | Check Misplaced properties for LIBRIS took 60.92288827896118s
Consistency | Misplaced classes for LIBRIS took 1.12825345993042s
Consistency | Check Ontology hijacking for LIBRIS took 3.697082281112671s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.318739891052246s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 61.70794653892517s
Conciseness | Check Extensional conciseness for LIBRIS took 0.28415989875793457s
Conciseness | Check Intensional conciseness for LIBRIS took 0.4065706729888916s
Security | Sign check for LIBRIS took 0.5797519683837891s
Availability | Check URIs Dereferenciability for LIBRIS took 9.107110738754272s
Completeness | Calculation of interlinking completeness for LIBRIS took 1.5168187618255615s
Reputation | Calculation of the PageRank for LIBRIS took 0.02046823501586914s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 0.00010228157043457031s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.1920928955078125e-06s
Believability | Calculation of trust value for LIBRIS took 9.059906005859375e-06s
INFO | --- Analysis for libris took 1070.567393541336s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.07013225555419922s
Availability | VoID file availability check for Public Library of Veroia took 0.0007150173187255859s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.24827837944030762s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.020140886306762695s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.128715515136719e-05s
Believability | Calculation of trust value for Public Library of Veroia took 6.198883056640625e-06s
INFO | --- Analysis for libver took 4.497685670852661s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.2170553207397461s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.2513282299041748s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.02037835121154785s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 7.987022399902344e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 5.0067901611328125e-06s
INFO | --- Analysis for lichfield-spending took 3.4867584705352783s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 4.363059997558594e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0007107257843017578s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.2713758945465088s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.02015376091003418s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.337860107421875e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 8.106231689453125e-06s
INFO | --- Analysis for lime took 6.9310712814331055s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 4.410743713378906e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0003516674041748047s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.2924978733062744s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.020444393157958984s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00010800361633300781s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 7.152557373046875e-06s
INFO | --- Analysis for lingvoj took 6.264874219894409s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 4.4345855712890625e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.28980278968811035s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.02043461799621582s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0008177757263183594s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 8.249282836914062e-05s
Believability | Calculation of trust value for Linked Crunchbase took 7.3909759521484375e-06s
INFO | --- Analysis for linked-crunchbase took 3.2886083126068115s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 6.252164125442505s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.25693559646606445s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.020400285720825195s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.987022399902344e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.2874603271484375e-05s
INFO | --- Analysis for linked-drugs took 19.97376799583435s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.4345855712890625e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.24352097511291504s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.02043890953063965s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.632110595703125e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 5.9604644775390625e-06s
INFO | --- Analysis for linked-edgar took 4.371670722961426s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 4.363059997558594e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0007290840148925781s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.26435208320617676s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.02062368392944336s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.560585021972656e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 6.67572021484375e-06s
INFO | --- Analysis for linked-eurostat took 4.221181392669678s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.291534423828125e-05s
Availability | VoID file availability check for linked hypernyms took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.279965877532959s
Reputation | Calculation of the PageRank for linked hypernyms took 0.0207366943359375s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0009694099426269531s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 9.012222290039062e-05s
Believability | Calculation of trust value for linked hypernyms took 9.775161743164062e-06s
INFO | --- Analysis for linked-hypernyms took 3.5413548946380615s
Availability | SPARQL endpoint availability check for Linked Life Data took 228.72916960716248s
Availability | VoID file availability check for Linked Life Data took 0.0007398128509521484s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.7447223663330078s
Reputation | Calculation of the PageRank for Linked Life Data took 0.020900964736938477s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 2.956390380859375e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 5.698204040527344e-05s
Believability | Calculation of trust value for Linked Life Data took 6.9141387939453125e-06s
INFO | --- Analysis for linked-life-data took 705.71937084198s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.35830140113830566s
Availability | VoID file availability check for Linked Logainm took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.7090132236480713s
Reputation | Calculation of the PageRank for Linked Logainm took 0.020640850067138672s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 7.987022399902344e-05s
Believability | Calculation of trust value for Linked Logainm took 8.58306884765625e-06s
INFO | --- Analysis for linked-logainm took 5.472326040267944s
Availability | SPARQL endpoint availability check for Linked NUTS took 4.458427429199219e-05s
Availability | VoID file availability check for Linked NUTS took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.2568700313568115s
Reputation | Calculation of the PageRank for Linked NUTS took 0.02041316032409668s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.0067901611328125e-05s
Believability | Calculation of trust value for Linked NUTS took 5.4836273193359375e-06s
INFO | --- Analysis for linked-nuts took 3.7490062713623047s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 4.0531158447265625e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.2670254707336426s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.020177125930786133s
Interlinking | Calculation of Degree of Connection for Linked Open Aalto Data Service took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Aalto Data Service took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Linked Open Aalto Data Service took 2.9802322387695312e-05s
Believability | Calculation of trust value for Linked Open Aalto Data Service took 8.106231689453125e-06s
INFO | --- Analysis for linked-open-aalto-data-service took 3.3549787998199463s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 1.3270127773284912s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.2823526859283447s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020539045333862305s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0008075237274169922s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.719329833984375e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 6.67572021484375e-06s
INFO | --- Analysis for linked-open-camera took 3.7684237957000732s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 3.463416576385498s
Availability | VoID file availability check for Linked Open Commerce took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.2525954246520996s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.02018117904663086s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 2.8133392333984375e-05s
Believability | Calculation of trust value for Linked Open Commerce took 6.67572021484375e-06s
INFO | --- Analysis for linked-open-commerce took 13.457412958145142s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 2.0821564197540283s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.00021886825561523438s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.2677299976348877s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.02019953727722168s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 9.751319885253906e-05s
Believability | Calculation of trust value for Linked Open Data of Ecology took 6.9141387939453125e-06s
INFO | --- Analysis for linked-open-data-of-ecology took 4.551699876785278s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 4.315376281738281e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.25824880599975586s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.02025127410888672s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 8.7738037109375e-05s
Believability | Calculation of trust value for Linked Open Numbers took 7.62939453125e-06s
INFO | --- Analysis for linked-open-numbers took 2.5763649940490723s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 4.267692565917969e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.26848459243774414s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.020284414291381836s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 3.2901763916015625e-05s
Believability | Calculation of trust value for Linked Open Piracy took 5.245208740234375e-06s
INFO | --- Analysis for linked-open-piracy took 7.09465479850769s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 3.9577484130859375e-05s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 0.24445152282714844s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.020435094833374023s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 6.9141387939453125e-06s
INFO | --- Analysis for linked-open-senate took 2.8668477535247803s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 1.682821273803711s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0007741451263427734s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.2539379596710205s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.020245790481567383s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 4.410743713378906e-05s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 7.3909759521484375e-06s
INFO | --- Analysis for linked-open-vocabularies-lov took 9.547480821609497s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.315376281738281e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.2926633358001709s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.02037954330444336s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.504753112792969e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 5.0067901611328125e-06s
INFO | --- Analysis for linked-periodicals took 2.539397954940796s
Availability | SPARQL endpoint availability check for Linked Index took 4.2438507080078125e-05s
Availability | VoID file availability check for Linked Index took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for Linked Index took 0.2682979106903076s
Reputation | Calculation of the PageRank for Linked Index took 0.020396709442138672s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.320808410644531e-05s
Believability | Calculation of trust value for Linked Index took 6.198883056640625e-06s
INFO | --- Analysis for linked-stockindex took 2.383443593978882s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 4.701797008514404s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.269913911819458s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.020380496978759766s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 3.528594970703125e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 7.3909759521484375e-06s
INFO | --- Analysis for linked-structured-product-labels took 13.507768154144287s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.971980094909668s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.2670094966888428s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.02022385597229004s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.218650817871094e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 6.9141387939453125e-06s
INFO | --- Analysis for linked-taiwan-geo-names took 3.9921867847442627s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.487619400024414s
Availability | VoID file availability check for Linked TCGA took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.24182510375976562s
Reputation | Calculation of the PageRank for Linked TCGA took 0.020494699478149414s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 9.775161743164062e-05s
Believability | Calculation of trust value for Linked TCGA took 1.0013580322265625e-05s
INFO | --- Analysis for linked-tcga took 63.01438093185425s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.10116910934448242s
Availability | VoID file availability check for Linked User Feedback took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.27186059951782227s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.02031683921813965s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.838539123535156e-05s
Believability | Calculation of trust value for Linked User Feedback took 1.1920928955078125e-05s
INFO | --- Analysis for linked-user-feedback took 2.8391451835632324s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.601478576660156e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0013267993927001953s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.26042962074279785s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.020316362380981445s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 8.749961853027344e-05s
Believability | Calculation of trust value for USPTO Patent data took 7.3909759521484375e-06s
INFO | --- Analysis for linked-uspto-patent-data took 53.27754282951355s
Availability | SPARQL endpoint availability check for Linked Web APIs dataset took 5.435943603515625e-05s
Availability | VoID file availability check for Linked Web APIs dataset took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.2790391445159912s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.020464420318603516s
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.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Linked Web APIs dataset took 2.9325485229492188e-05s
Believability | Calculation of trust value for Linked Web APIs dataset took 7.867813110351562e-06s
INFO | --- Analysis for linked-web-apis took 3.2812752723693848s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 8.940696716308594e-05s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.281144380569458s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.020391464233398438s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 3.218650817871094e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 6.9141387939453125e-06s
INFO | --- Analysis for linkedarc took 3.495002269744873s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.0868678092956543s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.2699751853942871s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.020449161529541016s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0009784698486328125s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 4.100799560546875e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 7.62939453125e-06s
INFO | --- Analysis for linkedcrowdsourceddata took 2.7107431888580322s
Availability | SPARQL endpoint availability check for LinkedCT took 1.5406250953674316s
Availability | VoID file availability check for LinkedCT took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.25785017013549805s
Reputation | Calculation of the PageRank for LinkedCT took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 9.918212890625e-05s
Believability | Calculation of trust value for LinkedCT took 7.867813110351562e-06s
INFO | --- Analysis for linkedct took 5.020650148391724s
Availability | SPARQL endpoint availability check for LinkedGeoData took 391.5300991535187s
Availability | VoID file availability check for LinkedGeoData took 0.0004153251647949219s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.6708106994628906s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.020659208297729492s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00017118453979492188s
Believability | Calculation of trust value for LinkedGeoData took 8.106231689453125e-06s
INFO | --- Analysis for linkedgeodata took 928.6295323371887s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 4.673004150390625e-05s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.273090124130249s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.020671844482421875s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 2.9087066650390625e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 6.67572021484375e-06s
INFO | --- Analysis for linkedgeodata-aerodromes took 5.392412185668945s
Availability | SPARQL endpoint availability check for LinkedLCCN took 1.0424399375915527s
Availability | VoID file availability check for LinkedLCCN took 0.00072479248046875s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.25466060638427734s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.020456552505493164s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00010347366333007812s
Believability | Calculation of trust value for LinkedLCCN took 1.049041748046875e-05s
INFO | --- Analysis for linkedlccn took 11.722264766693115s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 4.220008850097656e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.2796328067779541s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.020648717880249023s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.600120544433594e-05s
Believability | Calculation of trust value for LinkedMarkMail took 7.152557373046875e-06s
INFO | --- Analysis for linkedmarkmail took 3.0397391319274902s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.63052463531494s
Availability | VoID file availability check for Linked Movie DataBase took 0.00072479248046875s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.2808864116668701s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.031255245208740234s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 2.7894973754882812e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.001214742660522461s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.0002117156982421875s
Believability | Calculation of trust value for Linked Movie DataBase took 8.58306884765625e-06s
INFO | --- Analysis for linkedmdb took 134.34804964065552s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.4661712646484375s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0005967617034912109s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 0.2671959400177002s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.020348072052001953s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 8.058547973632812e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 8.58306884765625e-06s
INFO | --- Analysis for linkedspending took 4.448807239532471s
Availability | SPARQL endpoint availability check for LinkedStats took 4.172325134277344e-05s
Availability | VoID file availability check for LinkedStats took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for LinkedStats took 0.2651181221008301s
Reputation | Calculation of the PageRank for LinkedStats took 0.02065896987915039s
Interlinking | Calculation of Degree of Connection for LinkedStats took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LinkedStats took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 3.147125244140625e-05s
Believability | Calculation of trust value for LinkedStats took 6.67572021484375e-06s
INFO | --- Analysis for linkedstats took 3.731182813644409s
Availability | SPARQL endpoint availability check for LinkedUp Catalogue of Educational Datasets took 4.076957702636719e-05s
Availability | VoID file availability check for LinkedUp Catalogue of Educational Datasets took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 0.24387168884277344s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.020275592803955078s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for LinkedUp Catalogue of Educational Datasets took 2.8133392333984375e-05s
Believability | Calculation of trust value for LinkedUp Catalogue of Educational Datasets took 6.9141387939453125e-06s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 2.8865365982055664s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 4.172325134277344e-05s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 0.2674891948699951s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for Linking Open Drug Data (LODD) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linking Open Drug Data (LODD) took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for Linking Open Drug Data (LODD) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Linking Open Drug Data (LODD) took 6.9141387939453125e-06s
INFO | --- Analysis for linking-open-drug-data took 2.976870059967041s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.5534250736236572s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.00040411949157714844s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.28986120223999023s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.020526647567749023s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00010991096496582031s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 1.1444091796875e-05s
INFO | --- Analysis for linklion took 2.9355838298797607s
Availability | SPARQL endpoint availability check for Lion's Den took 4.3392181396484375e-05s
Availability | VoID file availability check for Lion's Den took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.2568507194519043s
Reputation | Calculation of the PageRank for Lion's Den took 0.02041912078857422s
Interlinking | Calculation of Degree of Connection for Lion's Den took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lion's Den took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 2.956390380859375e-05s
Believability | Calculation of trust value for Lion's Den took 7.152557373046875e-06s
INFO | --- Analysis for lionsden took 2.8871238231658936s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 36.987544298172s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.25766754150390625s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.020349502563476562s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 5.435943603515625e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for lista-encabezamientos-materia took 42.38474917411804s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 4.124641418457031e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 0.26838231086730957s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.02037644386291504s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 7.867813110351562e-06s
INFO | --- Analysis for livtdm took 2.8685073852539062s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 4.124641418457031e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.2583444118499756s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.02016162872314453s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 2.7894973754882812e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 7.3909759521484375e-06s
INFO | --- Analysis for livtdm2017 took 2.923220634460449s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 5.2928924560546875e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.2477724552154541s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.0201261043548584s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.0008044242858886719s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 2.7894973754882812e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 7.3909759521484375e-06s
INFO | --- Analysis for lobi took 2.8349106311798096s
Availability | SPARQL endpoint availability check for lobid-organisations took 1.5962798595428467s
Availability | VoID file availability check for lobid-organisations took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.28473496437072754s
Reputation | Calculation of the PageRank for lobid-organisations took 0.02061176300048828s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.632110595703125e-05s
Believability | Calculation of trust value for lobid-organisations took 7.152557373046875e-06s
INFO | --- Analysis for lobid-organisations took 6.127983093261719s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.8480582237243652s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.000682830810546875s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.28291869163513184s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.020366191864013672s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 9.918212890625e-05s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 7.152557373046875e-06s
INFO | --- Analysis for lobid-resources took 8.131560325622559s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.363059997558594e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.2670297622680664s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.020196914672851562s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 6.985664367675781e-05s
Believability | Calculation of trust value for Linked Open Colors took 8.821487426757812e-06s
INFO | --- Analysis for loc took 7.1530303955078125s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 4.935264587402344e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.26018452644348145s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.020416736602783203s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 2.7418136596679688e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 6.67572021484375e-06s
INFO | --- Analysis for locv took 36.05599236488342s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.7315394878387451s
Availability | VoID file availability check for LOD-a-lot took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.25217127799987793s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.020427227020263672s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 2.9087066650390625e-05s
Believability | Calculation of trust value for LOD-a-lot took 6.67572021484375e-06s
INFO | --- Analysis for lod-a-lot took 14.327166318893433s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 4.124641418457031e-05s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.29214954376220703s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.02052450180053711s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 2.7418136596679688e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 6.9141387939453125e-06s
INFO | --- Analysis for lod-it_scuole-italiane took 3.095074415206909s
Availability | SPARQL endpoint availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 4.649162292480469e-05s
Availability | VoID file availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.25273776054382324s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.020159482955932617s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Open Data Web - a CKAN based linked open data repository in Taiwan took 2.8133392333984375e-05s
Believability | Calculation of trust value for Open Data Web - a CKAN based linked open data repository in Taiwan took 7.3909759521484375e-06s
INFO | --- Analysis for lod-taiwan took 2.889108896255493s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.315376281738281e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.28587889671325684s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.020360946655273438s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.559226989746094e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 1.0013580322265625e-05s
INFO | --- Analysis for lod2-project-wiki took 3.7638168334960938s
Availability | SPARQL endpoint availability check for LODAC BDLS took 4.0177083015441895s
Availability | VoID file availability check for LODAC BDLS took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.2659163475036621s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.020107269287109375s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 6.985664367675781e-05s
Believability | Calculation of trust value for LODAC BDLS took 9.5367431640625e-06s
INFO | --- Analysis for lodac-bdls took 15.096893787384033s
Availability | SPARQL endpoint availability check for LODRussia Math took 4.00543212890625e-05s
Availability | VoID file availability check for LODRussia Math took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for LODRussia Math took 0.2904524803161621s
Reputation | Calculation of the PageRank for LODRussia Math took 0.02025437355041504s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LODRussia Math took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 2.765655517578125e-05s
Believability | Calculation of trust value for LODRussia Math took 7.152557373046875e-06s
INFO | --- Analysis for lodrussia-math took 2.941659688949585s
Availability | SPARQL endpoint availability check for LODRussia Nano took 4.506111145019531e-05s
Availability | VoID file availability check for LODRussia Nano took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 0.2727348804473877s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.02066779136657715s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 2.86102294921875e-05s
Believability | Calculation of trust value for LODRussia Nano took 6.9141387939453125e-06s
INFO | --- Analysis for lodrussia-nano took 2.926056146621704s
Availability | SPARQL endpoint availability check for LODStats took 4.100799560546875e-05s
Availability | VoID file availability check for LODStats took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for LODStats took 0.2426455020904541s
Reputation | Calculation of the PageRank for LODStats took 0.02016925811767578s
Interlinking | Calculation of Degree of Connection for LODStats took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LODStats took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for LODStats took 2.7418136596679688e-05s
Believability | Calculation of trust value for LODStats took 7.152557373046875e-06s
INFO | --- Analysis for lodstats took 2.8834500312805176s
Availability | SPARQL endpoint availability check for LODUM took 4.100799560546875e-05s
Availability | VoID file availability check for LODUM took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for LODUM took 0.25452518463134766s
Reputation | Calculation of the PageRank for LODUM took 0.022054672241210938s
Interlinking | Calculation of Degree of Connection for LODUM took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LODUM took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for LODUM took 3.337860107421875e-05s
Believability | Calculation of trust value for LODUM took 8.344650268554688e-06s
INFO | --- Analysis for lodum took 2.933619976043701s
Availability | SPARQL endpoint availability check for lofd took 0.13618683815002441s
Availability | VoID file availability check for lofd took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for lofd took 0.2699251174926758s
Reputation | Calculation of the PageRank for lofd took 0.02046942710876465s
Interlinking | Calculation of Degree of Connection for lofd took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for lofd took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for lofd took 2.8371810913085938e-05s
Believability | Calculation of trust value for lofd took 1.1444091796875e-05s
INFO | --- Analysis for lofd took 2.5651893615722656s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 272.08405661582947s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0011670589447021484s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.2766847610473633s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.02031993865966797s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 4.887580871582031e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 5.0067901611328125e-06s
INFO | --- Analysis for loius took 586.1574289798737s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 4.38690185546875e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.23882174491882324s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.020842313766479492s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 2.765655517578125e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 7.152557373046875e-06s
INFO | --- Analysis for loius-linking-italian-university-statistics took 3.446258068084717s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 0.8004550933837891s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.7413392066955566s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.0203855037689209s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.030632019042969e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 5.7220458984375e-06s
INFO | --- Analysis for london-gazette took 6.105400800704956s
Availability | SPARQL endpoint availability check for Weather Stations took 4.4345855712890625e-05s
Availability | VoID file availability check for Weather Stations took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.2830698490142822s
Reputation | Calculation of the PageRank for Weather Stations took 0.020441770553588867s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 8.058547973632812e-05s
Believability | Calculation of trust value for Weather Stations took 7.3909759521484375e-06s
INFO | --- Analysis for los_metar took 7.807727336883545s
Availability | SPARQL endpoint availability check for Lotico took 0.9886157512664795s
Availability | VoID file availability check for Lotico took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for Lotico took 0.27126169204711914s
Reputation | Calculation of the PageRank for Lotico took 0.020264625549316406s
Interlinking | Calculation of Degree of Connection for Lotico took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Lotico took 8.225440979003906e-05s
Believability | Calculation of trust value for Lotico took 6.67572021484375e-06s
INFO | --- Analysis for lotico took 6.791664123535156s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.27670764923095703s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0006315708160400391s
Extra | Recovery of all triples for Lower Layer Super Output Areas took 0.22349047660827637s
Performance | Total latancy measurement for Lower Layer Super Output Areas took 0.6975045204162598s
Amount of data | Number of triples check for Lower Layer Super Output Areas took 0.15293407440185547s
Interoperability | New terms check for Lower Layer Super Output Areas took 1.532717227935791s
Versatility | Languages check for Lower Layer Super Output Areas took 0.20528411865234375s
Interpretability | Number of blank nodes check for Lower Layer Super Output Areas took 0.3365654945373535s
Security | Check HTTPS for Lower Layer Super Output Areas took 0.4743344783782959s
Interpretability | RDF structures check for Lower Layer Super Output Areas took 0.13039350509643555s
Versatility | Serialization formats check for Lower Layer Super Output Areas took 0.21307039260864258s
Availability | RDF dump link check for Lower Layer Super Output Areas took 47.73393177986145s
License | MR license check for Lower Layer Super Output Areas took 0.16440343856811523s
License | HR license check for Lower Layer Super Output Areas took 0.29065799713134766s
Amount of data | Number of property check for Lower Layer Super Output Areas took 0.21776986122131348s
Understandability | Number of label check for Lower Layer Super Output Areas took 0.130537748336792s
Understandability | URI regex check for Lower Layer Super Output Areas took 0.2768442630767822s
Understandability | Vocabs check for Lower Layer Super Output Areas took 0.1995863914489746s
Verifiability | Authors check for Lower Layer Super Output Areas took 0.19642424583435059s
Verifiability | Publishers check for Lower Layer Super Output Areas took 0.12593841552734375s
Performance | Throughput check for Lower Layer Super Output Areas took 12.059514045715332s
Amount of data | Check the number of entities for Lower Layer Super Output Areas took 8.535385131835938e-05s
Verifiability | Contribs. check for Lower Layer Super Output Areas took 0.13802719116210938s
Interlinking | sameAs chians check for Lower Layer Super Output Areas took 0.15257525444030762s
Interlinking | skos check for Lower Layer Super Output Areas took 0.13464117050170898s
Interlinking | skos check for Lower Layer Super Output Areas took 0.13002490997314453s
Timeliness | dataset update frequency check for Lower Layer Super Output Areas took 0.1555495262145996s
Currency | Creation date check for Lower Layer Super Output Areas took 0.3570411205291748s
Currency | Modification date check for Lower Layer Super Output Areas took 0.16770625114440918s
Rep.Conc. | URIs length for Lower Layer Super Output Areas took 0.5102388858795166s
Interoperability | New vocabularies check for Lower Layer Super Output Areas took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Lower Layer Super Output Areas took 0.12866997718811035s
Accuracy | Check Functional Property for Lower Layer Super Output Areas took 0.20091009140014648s
Accuracy | Check Inverse Functional Property for Lower Layer Super Output Areas took 0.7559521198272705s
Consistency | Disjoint class check for Lower Layer Super Output Areas took 0.15494704246520996s
Consistency | Check Misplaced properties for Lower Layer Super Output Areas took 0.4095287322998047s
Consistency | Check Ontology hijacking for Lower Layer Super Output Areas took 0.28600549697875977s
Consistency | Check Invalid usage of undefined properties for Lower Layer Super Output Areas took 1.540271282196045s
Conciseness | Check Extensional conciseness for Lower Layer Super Output Areas took 0.0001437664031982422s
Conciseness | Check Intensional conciseness for Lower Layer Super Output Areas took 0.4193556308746338s
Security | Sign check for Lower Layer Super Output Areas took 0.1504042148590088s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.24754023551940918s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.020348787307739258s
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.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 2.9325485229492188e-05s
Interoperability | Check the re-using of existing vocabs for Lower Layer Super Output Areas took 1.6689300537109375e-06s
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.74143624305725s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 5.9604644775390625e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.2622246742248535s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.021259546279907227s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0008015632629394531s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.4332275390625e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 8.106231689453125e-06s
INFO | --- Analysis for lremap-auth took 3.1756837368011475s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 7.867813110351562e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.26148414611816406s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.02051711082458496s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.00072479248046875s
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 7.152557373046875e-06s
INFO | --- Analysis for lremap-conf took 3.9669716358184814s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 8.869171142578125e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.2732541561126709s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.020476818084716797s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 2.9325485229492188e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 7.867813110351562e-06s
INFO | --- Analysis for lremap-ri took 2.7825846672058105s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 4.4345855712890625e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.25355982780456543s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.02061152458190918s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 3.0279159545898438e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 1.1444091796875e-05s
INFO | --- Analysis for lremap-sub took 2.6673154830932617s
Availability | SPARQL endpoint availability check for LSQ took 4.3392181396484375e-05s
Availability | VoID file availability check for LSQ took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for LSQ took 0.2641568183898926s
Reputation | Calculation of the PageRank for LSQ took 0.020465373992919922s
Interlinking | Calculation of Degree of Connection for LSQ took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for LSQ took 2.9802322387695312e-05s
Believability | Calculation of trust value for LSQ took 8.58306884765625e-06s
INFO | --- Analysis for lsq took 3.490004301071167s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 4.1961669921875e-05s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.00021648406982421875s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.2703430652618408s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.020638465881347656s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 3.0517578125e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 6.198883056640625e-06s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 2.877939462661743s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 4.5299530029296875e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.2633204460144043s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.020789623260498047s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.504753112792969e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 8.58306884765625e-06s
INFO | --- Analysis for manchester-university-reading-lists took 3.350813865661621s
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.00024819374084472656s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.28185319900512695s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.020693063735961914s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 2.9802322387695312e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 7.62939453125e-06s
INFO | --- Analysis for mapa-referencia-bogota took 2.944779872894287s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá D.C took 5.7697296142578125e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá D.C took 0.00040411949157714844s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.2659313678741455s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.020409822463989258s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 3.314018249511719e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 8.58306884765625e-06s
INFO | --- Analysis for mapa-referencia-bogota-dc took 2.979832887649536s
Availability | SPARQL endpoint availability check for MARC Codes List took 4.267692565917969e-05s
Availability | VoID file availability check for MARC Codes List took 0.0003199577331542969s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.2679581642150879s
Reputation | Calculation of the PageRank for MARC Codes List took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.0001232624053955078s
Believability | Calculation of trust value for MARC Codes List took 8.821487426757812e-06s
INFO | --- Analysis for marc-codes took 12.694360494613647s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.482269287109375e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.29156494140625s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.02060222625732422s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 3.9577484130859375e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 6.9141387939453125e-06s
INFO | --- Analysis for masc took 5.97067928314209s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 4.38690185546875e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.2524831295013428s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.02030777931213379s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.00080108642578125s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.719329833984375e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 7.152557373046875e-06s
INFO | --- Analysis for masc-bn-nif took 2.4025354385375977s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.379892349243164s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.266829252243042s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.020207643508911133s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 2.9087066650390625e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 4.696846008300781e-05s
INFO | --- Analysis for massobservationarchivecatalogue took 3.8532776832580566s
Availability | SPARQL endpoint availability check for medline took 4.410743713378906e-05s
Availability | VoID file availability check for medline took 0.0003440380096435547s
Completeness | Calculation of interlinking completeness for medline took 0.26667165756225586s
Reputation | Calculation of the PageRank for medline took 0.02039337158203125s
Interlinking | Calculation of Degree of Connection for medline took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for medline took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for medline took 5.507469177246094e-05s
Believability | Calculation of trust value for medline took 7.152557373046875e-06s
INFO | --- Analysis for medline took 7.501982927322388s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 1.9598934650421143s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0008623600006103516s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.25619053840637207s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.02065753936767578s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 6.747245788574219e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 7.3909759521484375e-06s
INFO | --- Analysis for meducator took 22.739964962005615s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 4.1484832763671875e-05s
Availability | VoID file availability check for Finnish translation of mesh took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.2670104503631592s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.020273923873901367s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 2.9087066650390625e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 6.67572021484375e-06s
INFO | --- Analysis for mesh-finnish took 2.859004497528076s
Availability | SPARQL endpoint availability check for MeSH headings took 5.53131103515625e-05s
Availability | VoID file availability check for MeSH headings took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for MeSH headings took 0.26804304122924805s
Reputation | Calculation of the PageRank for MeSH headings took 0.02031731605529785s
Interlinking | Calculation of Degree of Connection for MeSH headings took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MeSH headings took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 2.765655517578125e-05s
Believability | Calculation of trust value for MeSH headings took 7.152557373046875e-06s
INFO | --- Analysis for mesh_headings took 2.910210371017456s
Availability | SPARQL endpoint availability check for MeSH, IPSV - SKOS RDF took 5.316734313964844e-05s
Availability | VoID file availability check for MeSH, IPSV - SKOS RDF took 0.00029468536376953125s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 0.2894587516784668s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.02042675018310547s
Interlinking | Calculation of Degree of Connection for MeSH, IPSV - SKOS RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MeSH, IPSV - SKOS RDF took 0.000835418701171875s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 3.266334533691406e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 7.62939453125e-06s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 2.976236581802368s
Availability | SPARQL endpoint availability check for MeSH pairs took 4.076957702636719e-05s
Availability | VoID file availability check for MeSH pairs took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for MeSH pairs took 0.2549915313720703s
Reputation | Calculation of the PageRank for MeSH pairs took 0.02019643783569336s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MeSH pairs took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 2.9325485229492188e-05s
Believability | Calculation of trust value for MeSH pairs took 7.62939453125e-06s
INFO | --- Analysis for mesh_pairs took 2.964827060699463s
Availability | SPARQL endpoint availability check for MeSH titles took 4.1961669921875e-05s
Availability | VoID file availability check for MeSH titles took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.24679064750671387s
Reputation | Calculation of the PageRank for MeSH titles took 0.020592451095581055s
Interlinking | Calculation of Degree of Connection for MeSH titles took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MeSH titles took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 3.0994415283203125e-05s
Believability | Calculation of trust value for MeSH titles took 8.821487426757812e-06s
INFO | --- Analysis for mesh_titles took 2.8952438831329346s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 5.14984130859375e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.282454252243042s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.020560264587402344s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 2.9325485229492188e-05s
Believability | Calculation of trust value for Metadata k zákonům z psp.cz took 8.58306884765625e-06s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 2.9785571098327637s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 4.482269287109375e-05s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.29024410247802734s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.020595073699951172s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 3.123283386230469e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 8.344650268554688e-06s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 2.956570863723755s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 4.363059997558594e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.3032948970794678s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.021031856536865234s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0008382797241210938s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 8.320808410644531e-05s
Believability | Calculation of trust value for MetaShare metadata model took 9.059906005859375e-06s
INFO | --- Analysis for metashare took 2.771299123764038s
Availability | SPARQL endpoint availability check for MExiCo took 4.363059997558594e-05s
Availability | VoID file availability check for MExiCo took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for MExiCo took 0.2713959217071533s
Reputation | Calculation of the PageRank for MExiCo took 0.020537137985229492s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for MExiCo took 5.7697296142578125e-05s
Believability | Calculation of trust value for MExiCo took 8.58306884765625e-06s
INFO | --- Analysis for mexico took 22.504496574401855s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 5.91278076171875e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.23745107650756836s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.02041459083557129s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00010395050048828125s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 6.9141387939453125e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 5.723012208938599s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 4.553794860839844e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.2871205806732178s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.020261526107788086s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0001239776611328125s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 8.344650268554688e-06s
INFO | --- Analysis for mismuseos-gnoss took 5.63882303237915s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.46891236305236816s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.2585628032684326s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.020210742950439453s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.38690185546875e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 7.152557373046875e-06s
INFO | --- Analysis for mlsa took 3.30442476272583s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 5.078315734863281e-05s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.00022840499877929688s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.2694225311279297s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.020226001739501953s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 2.9325485229492188e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 9.298324584960938e-06s
INFO | --- Analysis for mond took 2.9779601097106934s
Availability | SPARQL endpoint availability check for MONDIS took 4.172325134277344e-05s
Availability | VoID file availability check for MONDIS took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for MONDIS took 0.25914835929870605s
Reputation | Calculation of the PageRank for MONDIS took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for MONDIS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MONDIS took 0.0008330345153808594s
Interlinking | Calculation of Clustering coefficient for MONDIS took 3.170967102050781e-05s
Believability | Calculation of trust value for MONDIS took 8.58306884765625e-06s
INFO | --- Analysis for mondis took 2.929802894592285s
Availability | SPARQL endpoint availability check for Monumentos took 4.172325134277344e-05s
Availability | VoID file availability check for Monumentos took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for Monumentos took 0.25774264335632324s
Reputation | Calculation of the PageRank for Monumentos took 0.02028632164001465s
Interlinking | Calculation of Degree of Connection for Monumentos took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Monumentos took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Monumentos took 3.123283386230469e-05s
Believability | Calculation of trust value for Monumentos took 8.58306884765625e-06s
INFO | --- Analysis for monumentos-zaragoza took 2.987326145172119s
Availability | SPARQL endpoint availability check for MORElab took 0.8571121692657471s
Availability | VoID file availability check for MORElab took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for MORElab took 0.2683134078979492s
Reputation | Calculation of the PageRank for MORElab took 0.020271778106689453s
Interlinking | Calculation of Degree of Connection for MORElab took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for MORElab took 8.606910705566406e-05s
Believability | Calculation of trust value for MORElab took 7.62939453125e-06s
INFO | --- Analysis for morelab took 4.192092180252075s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 1.840193510055542s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.2596251964569092s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.02047109603881836s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.702278137207031e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 7.3909759521484375e-06s
INFO | --- Analysis for msc took 6.13752555847168s
Availability | SPARQL endpoint availability check for Multext-East took 0.0001087188720703125s
Availability | VoID file availability check for Multext-East took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Multext-East took 0.2675204277038574s
Reputation | Calculation of the PageRank for Multext-East took 0.020426273345947266s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.4809112548828125e-05s
Believability | Calculation of trust value for Multext-East took 8.106231689453125e-06s
INFO | --- Analysis for multext-east took 2.40684175491333s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 4.124641418457031e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.25160717964172363s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.02056717872619629s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 3.075599670410156e-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.8292293548583984s
Availability | SPARQL endpoint availability check for Multimedia Lab took 7.677078247070312e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0009286403656005859s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.26788949966430664s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.02038741111755371s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.361701965332031e-05s
Believability | Calculation of trust value for Multimedia Lab took 8.58306884765625e-06s
INFO | --- Analysis for multimedia-lab took 2.435154914855957s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 4.172325134277344e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.28178977966308594s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.020312786102294922s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 3.123283386230469e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 1.4066696166992188e-05s
INFO | --- Analysis for munich-offener-haushalt took 2.933117628097534s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.7792127132415771s
Availability | VoID file availability check for Muninn World War I took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.660161018371582s
Reputation | Calculation of the PageRank for Muninn World War I took 0.020676374435424805s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.082389831542969e-05s
Believability | Calculation of trust value for Muninn World War I took 8.106231689453125e-06s
INFO | --- Analysis for muninn-world-war-i took 11.39892315864563s
Availability | SPARQL endpoint availability check for Musei Italiani took 4.1961669921875e-05s
Availability | VoID file availability check for Musei Italiani took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.2393193244934082s
Reputation | Calculation of the PageRank for Musei Italiani took 0.02051377296447754s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Musei Italiani took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 3.0517578125e-05s
Believability | Calculation of trust value for Musei Italiani took 8.58306884765625e-06s
INFO | --- Analysis for musei-italiani took 2.8829050064086914s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 4.506111145019531e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0005869865417480469s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.28027796745300293s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.020481586456298828s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00010347366333007812s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 6.9141387939453125e-06s
INFO | --- Analysis for museosespania-gnoss took 94.31852579116821s
Availability | SPARQL endpoint availability check for Italian Museums took 1.2682750225067139s
Availability | VoID file availability check for Italian Museums took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.2716207504272461s
Reputation | Calculation of the PageRank for Italian Museums took 0.020652294158935547s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 8.559226989746094e-05s
Believability | Calculation of trust value for Italian Museums took 7.62939453125e-06s
INFO | --- Analysis for museums-in-italy took 3.7591071128845215s
Availability | SPARQL endpoint availability check for MusicBrainz took 4.220008850097656e-05s
Availability | VoID file availability check for MusicBrainz took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.27141427993774414s
Reputation | Calculation of the PageRank for MusicBrainz took 0.02023458480834961s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MusicBrainz took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 3.0040740966796875e-05s
Believability | Calculation of trust value for MusicBrainz took 7.867813110351562e-06s
INFO | --- Analysis for musicbrainz_ took 2.9389779567718506s
Availability | SPARQL endpoint availability check for MusicNet Codex took 4.100799560546875e-05s
Availability | VoID file availability check for MusicNet Codex took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.25478529930114746s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.02052903175354004s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 3.0040740966796875e-05s
Believability | Calculation of trust value for MusicNet Codex took 7.62939453125e-06s
INFO | --- Analysis for musicnet_codex took 2.904048442840576s
Availability | SPARQL endpoint availability check for myExperiment took 0.28494906425476074s
Availability | VoID file availability check for myExperiment took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for myExperiment took 0.2614562511444092s
Reputation | Calculation of the PageRank for myExperiment took 0.0212860107421875s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.00010609626770019531s
Believability | Calculation of trust value for myExperiment took 8.344650268554688e-06s
INFO | --- Analysis for my-experiment took 3.634880781173706s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.06639719009399414s
Availability | VoID file availability check for My Family Lineage took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.27256107330322266s
Reputation | Calculation of the PageRank for My Family Lineage took 0.020348787307739258s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.654594421386719e-05s
Believability | Calculation of trust value for My Family Lineage took 6.4373016357421875e-06s
INFO | --- Analysis for my-family-lineage took 4.067340135574341s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 0.14134979248046875s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.26157069206237793s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.02061629295349121s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 6.580352783203125e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for n-lex-as-linked-data took 2.6914148330688477s
Availability | SPARQL endpoint availability check for NAICS 2007 took 25.22581124305725s
Availability | VoID file availability check for NAICS 2007 took 0.0008463859558105469s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.29498291015625s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.021436452865600586s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 3.5762786865234375e-05s
Believability | Calculation of trust value for NAICS 2007 took 6.198883056640625e-06s
INFO | --- Analysis for naics-2007 took 124.00571632385254s
Availability | SPARQL endpoint availability check for NAICS 2012 took 24.296700477600098s
Availability | VoID file availability check for NAICS 2012 took 0.0008544921875s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.28472375869750977s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.020659685134887695s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 5.626678466796875e-05s
Believability | Calculation of trust value for NAICS 2012 took 5.245208740234375e-06s
INFO | --- Analysis for naics-2012 took 123.26690173149109s
Availability | SPARQL endpoint availability check for National Agricultural Library Thesaurus took 4.124641418457031e-05s
Availability | VoID file availability check for National Agricultural Library Thesaurus took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 0.25304102897644043s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.020673036575317383s
Interlinking | Calculation of Degree of Connection for National Agricultural Library Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for National Agricultural Library Thesaurus took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 5.269050598144531e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for nalt took 2.894704580307007s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 1.8069794178009033s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0007441043853759766s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 1.1065781116485596s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 1.893219232559204s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 13.252422094345093s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 26.15062141418457s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.4289839267730713s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.879939556121826s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.8480262756347656s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.3605673313140869s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.44185829162597656s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.34643101692199707s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.4179806709289551s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.77583408355713s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.9302546977996826s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 5.957346677780151s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 0.7930240631103516s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.3573760986328125s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.39500951766967773s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.43361902236938477s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 11.587542533874512s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 8.559226989746094e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.3393857479095459s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.554889440536499s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.69504976272583s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.3562054634094238s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.43062829971313477s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.1723253726959229s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 0.775820255279541s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 1.0405960083007812s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 4.76837158203125e-07s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.4169802665710449s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.3689713478088379s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.3622758388519287s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.370922327041626s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0003349781036376953s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0005207061767578125s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.37445878982543945s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.7665698528289795s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.3701903820037842s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.8190014362335205s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.374110460281372s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.7711458206176758s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0008313655853271484s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.41298747062683105s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 3.6412627696990967s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.852015495300293s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.020797014236450195s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 6.0558319091796875e-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.7220458984375e-06s
INFO | --- Analysis for national-diet-library-authorities took 241.1579201221466s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.343731164932251s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0005068778991699219s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 1.5417346954345703s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 1.9288508892059326s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.821797609329224s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.8830668926239014s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 13.756841897964478s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.3804314136505127s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.3303389549255371s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.4296078681945801s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.40961599349975586s
License | MR license check for National Diet Library of Japan subject headings took 0.38057661056518555s
License | HR license check for National Diet Library of Japan subject headings took 91.82087397575378s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.8914790153503418s
Understandability | Number of label check for National Diet Library of Japan subject headings took 5.108366966247559s
Understandability | URI regex check for National Diet Library of Japan subject headings took 0.8038034439086914s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.39232373237609863s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.4315311908721924s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.3990640640258789s
Performance | Throughput check for National Diet Library of Japan subject headings took 11.566138744354248s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 8.940696716308594e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.38907408714294434s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.5366675853729248s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.5032451152801514s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.4202806949615479s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.38998866081237793s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.1550896167755127s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.7537734508514404s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 0.9856805801391602s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.39400267601013184s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.35465574264526367s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.35767555236816406s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.378856897354126s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0007450580596923828s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0010080337524414062s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.35424351692199707s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.7618691921234131s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.34589719772338867s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.7941861152648926s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.3909127712249756s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.7692553997039795s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0007309913635253906s
Security | Sign check for National Diet Library of Japan subject headings took 0.35753822326660156s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 3.6554243564605713s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.39753174781799316s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.020481586456298828s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 6.413459777832031e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.1920928955078125e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 7.62939453125e-06s
INFO | --- Analysis for national-diet-library-subject-headings took 300.18645906448364s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 1.1490554809570312s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.6724228858947754s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.020443439483642578s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 5.14984130859375e-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 7.352169513702393s
Availability | SPARQL endpoint availability check for Naturopathy took 5.340576171875e-05s
Availability | VoID file availability check for Naturopathy took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Naturopathy took 0.27126502990722656s
Reputation | Calculation of the PageRank for Naturopathy took 0.02053213119506836s
Interlinking | Calculation of Degree of Connection for Naturopathy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Naturopathy took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 3.0040740966796875e-05s
Believability | Calculation of trust value for Naturopathy took 8.344650268554688e-06s
INFO | --- Analysis for naturopathy2 took 2.9622349739074707s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.2809138298034668s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02087116241455078s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 3.337860107421875e-05s
Believability | Calculation of trust value for NCI Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for nci-thesaurus took 3.013319492340088s
Availability | SPARQL endpoint availability check for NDF-RT took 4.1484832763671875e-05s
Availability | VoID file availability check for NDF-RT took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.2596869468688965s
Reputation | Calculation of the PageRank for NDF-RT took 0.020499467849731445s
Interlinking | Calculation of Degree of Connection for NDF-RT took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NDF-RT took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 3.170967102050781e-05s
Believability | Calculation of trust value for NDF-RT took 6.9141387939453125e-06s
INFO | --- Analysis for ndf-rt took 2.9625799655914307s
Availability | SPARQL endpoint availability check for Near took 4.458427429199219e-05s
Availability | VoID file availability check for Near took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for Near took 0.29241394996643066s
Reputation | Calculation of the PageRank for Near took 0.02046942710876465s
Interlinking | Calculation of Degree of Connection for Near took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Near took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Near took 9.441375732421875e-05s
Believability | Calculation of trust value for Near took 6.67572021484375e-06s
INFO | --- Analysis for near took 10.159279108047485s
Availability | SPARQL endpoint availability check for Neel took 4.291534423828125e-05s
Availability | VoID file availability check for Neel took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Neel took 0.2475290298461914s
Reputation | Calculation of the PageRank for Neel took 0.020289182662963867s
Interlinking | Calculation of Degree of Connection for Neel took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neel took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Neel took 3.0279159545898438e-05s
Believability | Calculation of trust value for Neel took 1.1682510375976562e-05s
INFO | --- Analysis for neel took 3.3891050815582275s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 5.1021575927734375e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.2530350685119629s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 3.0994415283203125e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 7.62939453125e-06s
INFO | --- Analysis for neurocommons_text_mining_pilot took 3.3739631175994873s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 4.291534423828125e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0010373592376708984s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.27588558197021484s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.020846843719482422s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0008187294006347656s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 3.4332275390625e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 1.0728836059570312e-05s
INFO | --- Analysis for neurolex-wiki took 2.4507977962493896s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 4.220008850097656e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.2754182815551758s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.021102428436279297s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0008411407470703125s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 8.96453857421875e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 7.867813110351562e-06s
INFO | --- Analysis for news-100-nif-ner-corpus took 4.228426694869995s
Availability | SPARQL endpoint availability check for Newsweek took 4.220008850097656e-05s
Availability | VoID file availability check for Newsweek took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for Newsweek took 0.26038074493408203s
Reputation | Calculation of the PageRank for Newsweek took 0.020391464233398438s
Interlinking | Calculation of Degree of Connection for Newsweek took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Newsweek took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Newsweek took 2.956390380859375e-05s
Believability | Calculation of trust value for Newsweek took 7.62939453125e-06s
INFO | --- Analysis for newsweek took 2.8815436363220215s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 4.6253204345703125e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.2778794765472412s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.02022719383239746s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0001010894775390625s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 3.314018249511719e-05s
INFO | --- Analysis for nextweb-gnoss took 10.035679817199707s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 5.054473876953125e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0005815029144287109s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.2748715877532959s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.020282745361328125s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 8.0108642578125e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 5.9604644775390625e-06s
INFO | --- Analysis for nhs-jargon took 2.8722951412200928s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 4.124641418457031e-05s
Availability | VoID file availability check for NLM 2007 MeSH took 0.00029397010803222656s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.26468610763549805s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.02035212516784668s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 3.3855438232421875e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 7.152557373046875e-06s
INFO | --- Analysis for nlm_2007_mesh took 2.9384093284606934s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 4.291534423828125e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.2854900360107422s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.020424604415893555s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0008511543273925781s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.814697265625e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 7.62939453125e-06s
INFO | --- Analysis for nlr-dataset-mod took 4.3061301708221436s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.443544387817383s
Availability | VoID file availability check for Nobel Prizes took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.28943419456481934s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.020931720733642578s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0008091926574707031s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 0.0001010894775390625s
Believability | Calculation of trust value for Nobel Prizes took 7.3909759521484375e-06s
INFO | --- Analysis for nobelprizes took 8.365502834320068s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 24.969123363494873s
Availability | VoID file availability check for Nomenclator Asturias took 0.0008893013000488281s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.2758002281188965s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.020463228225708008s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 8.487701416015625e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 5.7220458984375e-06s
INFO | --- Analysis for nomenclator-asturias took 139.08731865882874s
Availability | SPARQL endpoint availability check for nomisma took 4.029273986816406e-05s
Availability | VoID file availability check for nomisma took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for nomisma took 0.2923767566680908s
Reputation | Calculation of the PageRank for nomisma took 0.02046680450439453s
Interlinking | Calculation of Degree of Connection for nomisma took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for nomisma took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for nomisma took 2.9325485229492188e-05s
Believability | Calculation of trust value for nomisma took 7.62939453125e-06s
INFO | --- Analysis for nomisma took 2.993978261947632s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.3688347339630127s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.28778576850891113s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.020345449447631836s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 5.173683166503906e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 6.9141387939453125e-06s
INFO | --- Analysis for norwegian-geo-divisions took 7.457745552062988s
Availability | SPARQL endpoint availability check for NorwegianSoE took 4.172325134277344e-05s
Availability | VoID file availability check for NorwegianSoE took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 0.2831730842590332s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.020128488540649414s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 2.8848648071289062e-05s
Believability | Calculation of trust value for NorwegianSoE took 7.152557373046875e-06s
INFO | --- Analysis for norwegiansoe took 3.367865562438965s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.315376281738281e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0005779266357421875s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.28560829162597656s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.0202181339263916s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.4809112548828125e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 7.3909759521484375e-06s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 2.7770614624023438s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 4.4345855712890625e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.2662649154663086s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.02102351188659668s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 3.266334533691406e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 8.106231689453125e-06s
INFO | --- Analysis for npg took 2.943124771118164s
Availability | SPARQL endpoint availability check for NPM took 4.38690185546875e-05s
Availability | VoID file availability check for NPM took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for NPM took 0.2791872024536133s
Reputation | Calculation of the PageRank for NPM took 0.020943880081176758s
Interlinking | Calculation of Degree of Connection for NPM took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for NPM took 3.695487976074219e-05s
Believability | Calculation of trust value for NPM took 7.3909759521484375e-06s
INFO | --- Analysis for npm took 3.3694281578063965s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.02638387680053711s
Availability | VoID file availability check for NTNU special collections took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.2565727233886719s
Reputation | Calculation of the PageRank for NTNU special collections took 0.02042388916015625s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.650520324707031e-05s
Believability | Calculation of trust value for NTNU special collections took 8.344650268554688e-06s
INFO | --- Analysis for ntnusc took 5.243536472320557s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 4.410743713378906e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.27795910835266113s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.020355224609375s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 9.965896606445312e-05s
Believability | Calculation of trust value for NUTS (GeoVocab) took 5.4836273193359375e-06s
INFO | --- Analysis for nuts-geovocab took 2.5981030464172363s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.41440916061401367s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0003516674041748047s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.25592923164367676s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.020442724227905273s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 6.771087646484375e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 7.152557373046875e-06s
INFO | --- Analysis for nvd took 3.9967637062072754s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.7037534713745117s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.2713155746459961s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.020209550857543945s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 8.20159912109375e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 1.3113021850585938e-05s
INFO | --- Analysis for nvs took 8.638202905654907s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 4.2438507080078125e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.29384875297546387s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.020404577255249023s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.00018072128295898438s
Believability | Calculation of trust value for New York Times - Linked Open Data took 1.2874603271484375e-05s
INFO | --- Analysis for nytimes-linked-open-data took 2.4438695907592773s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 4.1484832763671875e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.2409074306488037s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.020251750946044922s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 2.956390380859375e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 7.867813110351562e-06s
INFO | --- Analysis for o-anc took 2.9173214435577393s
Availability | SPARQL endpoint availability check for OANetzwerk took 4.220008850097656e-05s
Availability | VoID file availability check for OANetzwerk took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for OANetzwerk took 0.2888529300689697s
Reputation | Calculation of the PageRank for OANetzwerk took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OANetzwerk took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 2.9087066650390625e-05s
Believability | Calculation of trust value for OANetzwerk took 7.62939453125e-06s
INFO | --- Analysis for oanetzwerk took 3.0908334255218506s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 4.0531158447265625e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.0002951622009277344s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.29038381576538086s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.020421504974365234s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 1.0251998901367188e-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 2.7418136596679688e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 7.62939453125e-06s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 2.8743083477020264s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.6358323097229004s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0005712509155273438s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 2.500049352645874s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 2.6625256538391113s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 4.059097528457642s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.9480628967285156s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 60.45492625236511s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 2.4706692695617676s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.37229061126708984s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 2.393195390701294s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.6607272624969482s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.5575392246246338s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.8099725246429443s
License | HR license check for Italian Chamber of Deputies - official dataset took 60.49030542373657s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.4545304775238037s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.9412798881530762s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.9298925399780273s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 2.09468674659729s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.4928734302520752s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.42581987380981445s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 14.55793833732605s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 7.557868957519531e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.47751522064208984s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.46747612953186035s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.5785973072052002s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.4346904754638672s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.5752005577087402s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 1.0050323009490967s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.6556146144866943s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 17.529374837875366s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 0.4965343475341797s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 0.44928860664367676s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 2.6433348655700684s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 0.9465913772583008s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.02398991584777832s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.02892923355102539s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.45348095893859863s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 13.349430799484253s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.5465800762176514s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 2.241185426712036s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.3297855854034424s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 14.060617446899414s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.03449606895446777s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.48897480964660645s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.46999335289001465s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 17.0257785320282s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.342557430267334s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.020281076431274414s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 9.894371032714844e-05s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 7.62939453125e-06s
INFO | --- Analysis for ocd took 441.41141176223755s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 4.315376281738281e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0006327629089355469s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.7182092666625977s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.020615339279174805s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 3.719329833984375e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 8.106231689453125e-06s
INFO | --- Analysis for oceandrilling-borehole took 4.9027252197265625s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 1.481398105621338s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0007998943328857422s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.2425527572631836s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.020559072494506836s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 8.130073547363281e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 1.1682510375976562e-05s
INFO | --- Analysis for oceandrilling-codices took 8.101139068603516s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 1.2866992950439453s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.689751386642456s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.021291017532348633s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.528594970703125e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 8.344650268554688e-06s
INFO | --- Analysis for oceandrilling-dbseabed took 6.385160684585571s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 1.222820520401001s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0007450580596923828s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.27507972717285156s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.020640850067138672s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.552436828613281e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 1.33514404296875e-05s
INFO | --- Analysis for oceandrilling-forams took 5.839205265045166s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 1.2053108215332031s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0006690025329589844s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.281233549118042s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.02063918113708496s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.457069396972656e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 7.3909759521484375e-06s
INFO | --- Analysis for oceandrilling-janus took 5.731826305389404s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 11.036871671676636s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0008299350738525391s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.26655030250549316s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020516395568847656s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.3855438232421875e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 8.344650268554688e-06s
INFO | --- Analysis for oceandrilling-janusamp took 15.627565860748291s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.1110589504241943s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007014274597167969s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.2671821117401123s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.02077484130859375s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.647804260253906e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 8.58306884765625e-06s
INFO | --- Analysis for oceandrilling-ldeo took 5.716012477874756s
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.0006680488586425781s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.7118608951568604s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.020788192749023438s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.817413330078125e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 6.67572021484375e-06s
INFO | --- Analysis for oclc-fast took 16.90719985961914s
Availability | SPARQL endpoint availability check for Open Data Communities took 4.3392181396484375e-05s
Availability | VoID file availability check for Open Data Communities took 0.00031256675720214844s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.2621288299560547s
Reputation | Calculation of the PageRank for Open Data Communities took 0.02050495147705078s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data Communities took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 3.147125244140625e-05s
Believability | Calculation of trust value for Open Data Communities took 7.867813110351562e-06s
INFO | --- Analysis for odc took 2.908637285232544s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.315376281738281e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.27010035514831543s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.020160913467407227s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 2.956390380859375e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 5.0067901611328125e-06s
INFO | --- Analysis for odc-imd-environment-score took 5.153602361679077s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 4.100799560546875e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.2685701847076416s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.020359039306640625s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation Ranking, 2007 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation Ranking, 2007 took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 2.8133392333984375e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 7.62939453125e-06s
INFO | --- Analysis for odc-imd-rank-2007 took 2.8879289627075195s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.21516990661621094s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.000560760498046875s
Extra | Recovery of all triples for Open Data Communities - Lower layer Super Output Areas took 0.22226476669311523s
Performance | Total latancy measurement for Open Data Communities - Lower layer Super Output Areas took 0.8755388259887695s
Amount of data | Number of triples check for Open Data Communities - Lower layer Super Output Areas took 0.143143892288208s
Interoperability | New terms check for Open Data Communities - Lower layer Super Output Areas took 1.508777141571045s
Versatility | Languages check for Open Data Communities - Lower layer Super Output Areas took 0.22640728950500488s
Interpretability | Number of blank nodes check for Open Data Communities - Lower layer Super Output Areas took 0.28626012802124023s
Security | Check HTTPS for Open Data Communities - Lower layer Super Output Areas took 0.7118208408355713s
Interpretability | RDF structures check for Open Data Communities - Lower layer Super Output Areas took 0.2051088809967041s
Versatility | Serialization formats check for Open Data Communities - Lower layer Super Output Areas took 0.22696852684020996s
Availability | RDF dump link check for Open Data Communities - Lower layer Super Output Areas took 42.859699726104736s
License | MR license check for Open Data Communities - Lower layer Super Output Areas took 0.1526622772216797s
License | HR license check for Open Data Communities - Lower layer Super Output Areas took 0.22324228286743164s
Amount of data | Number of property check for Open Data Communities - Lower layer Super Output Areas took 0.15537452697753906s
Understandability | Number of label check for Open Data Communities - Lower layer Super Output Areas took 0.14435386657714844s
Understandability | URI regex check for Open Data Communities - Lower layer Super Output Areas took 0.6030285358428955s
Understandability | Vocabs check for Open Data Communities - Lower layer Super Output Areas took 0.1253662109375s
Verifiability | Authors check for Open Data Communities - Lower layer Super Output Areas took 0.19037604331970215s
Verifiability | Publishers check for Open Data Communities - Lower layer Super Output Areas took 0.13918566703796387s
Performance | Throughput check for Open Data Communities - Lower layer Super Output Areas took 11.541728019714355s
Amount of data | Check the number of entities for Open Data Communities - Lower layer Super Output Areas took 7.581710815429688e-05s
Verifiability | Contribs. check for Open Data Communities - Lower layer Super Output Areas took 0.48729944229125977s
Interlinking | sameAs chians check for Open Data Communities - Lower layer Super Output Areas took 0.1479814052581787s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.13544034957885742s
Interlinking | skos check for Open Data Communities - Lower layer Super Output Areas took 0.1515810489654541s
Timeliness | dataset update frequency check for Open Data Communities - Lower layer Super Output Areas took 0.12752556800842285s
Currency | Creation date check for Open Data Communities - Lower layer Super Output Areas took 0.3573923110961914s
Currency | Modification date check for Open Data Communities - Lower layer Super Output Areas took 0.2104501724243164s
Rep.Conc. | URIs length for Open Data Communities - Lower layer Super Output Areas took 1.4369251728057861s
Interoperability | New vocabularies check for Open Data Communities - Lower layer Super Output Areas took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Open Data Communities - Lower layer Super Output Areas took 0.1687779426574707s
Accuracy | Check Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.20980405807495117s
Accuracy | Check Inverse Functional Property for Open Data Communities - Lower layer Super Output Areas took 0.15073871612548828s
Consistency | Disjoint class check for Open Data Communities - Lower layer Super Output Areas took 0.13837766647338867s
Consistency | Check Misplaced properties for Open Data Communities - Lower layer Super Output Areas took 0.4327735900878906s
Consistency | Check Ontology hijacking for Open Data Communities - Lower layer Super Output Areas took 0.21448445320129395s
Consistency | Check Invalid usage of undefined properties for Open Data Communities - Lower layer Super Output Areas took 1.5780398845672607s
Conciseness | Check Extensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.0001442432403564453s
Conciseness | Check Intensional conciseness for Open Data Communities - Lower layer Super Output Areas took 0.2039635181427002s
Security | Sign check for Open Data Communities - Lower layer Super Output Areas took 0.14390277862548828s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.7230744361877441s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.020424604415893555s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 3.790855407714844e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Communities - Lower layer Super Output Areas took 1.430511474609375e-06s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 5.4836273193359375e-06s
INFO | --- Analysis for odc-lsoa took 162.05240869522095s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 5.0067901611328125e-05s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.2640974521636963s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.020304441452026367s
Interlinking | Calculation of Degree of Connection for Estimated mid-year population 2005 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Estimated mid-year population 2005 took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 2.86102294921875e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 6.9141387939453125e-06s
INFO | --- Analysis for odc-population-2005 took 3.0474436283111572s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 4.1484832763671875e-05s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.2965221405029297s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.02033853530883789s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 3.075599670410156e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 7.3909759521484375e-06s
INFO | --- Analysis for ods took 3.0140740871429443s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.5497708320617676s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.2796025276184082s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.020252227783203125s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.369850158691406e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for oecd-linked-data took 3.09852933883667s
Availability | SPARQL endpoint availability check for Offener Haushalt took 0.0005714893341064453s
Availability | VoID file availability check for Offener Haushalt took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 0.2772331237792969s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.020256519317626953s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 2.9325485229492188e-05s
Believability | Calculation of trust value for Offener Haushalt took 8.344650268554688e-06s
INFO | --- Analysis for offener-haushalt took 3.0415396690368652s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.309215307235718s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.26875758171081543s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 3.910064697265625e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 8.106231689453125e-06s
INFO | --- Analysis for ogolod took 102.89656567573547s
Availability | SPARQL endpoint availability check for OLiA took 4.291534423828125e-05s
Availability | VoID file availability check for OLiA took 0.000705718994140625s
Completeness | Calculation of interlinking completeness for OLiA took 0.2741990089416504s
Reputation | Calculation of the PageRank for OLiA took 0.02020120620727539s
Interlinking | Calculation of Degree of Connection for OLiA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OLiA took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.0001266002655029297s
Believability | Calculation of trust value for OLiA took 7.3909759521484375e-06s
INFO | --- Analysis for olia took 12.361344814300537s
Availability | SPARQL endpoint availability check for OLiA Discourse took 4.2438507080078125e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.2767479419708252s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.020529508590698242s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 4.267692565917969e-05s
Believability | Calculation of trust value for OLiA Discourse took 6.67572021484375e-06s
INFO | --- Analysis for olia-discourse took 7.391589879989624s
Availability | SPARQL endpoint availability check for OmegaWiki took 4.124641418457031e-05s
Availability | VoID file availability check for OmegaWiki took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for OmegaWiki took 0.26838135719299316s
Reputation | Calculation of the PageRank for OmegaWiki took 0.020267963409423828s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for OmegaWiki took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 2.8848648071289062e-05s
Believability | Calculation of trust value for OmegaWiki took 7.62939453125e-06s
INFO | --- Analysis for omegawiki took 3.150510311126709s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 6.727357625961304s
Availability | VoID file availability check for OntoBeef Domain took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.28968334197998047s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.020430326461791992s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 5.459785461425781e-05s
Believability | Calculation of trust value for OntoBeef Domain took 7.3909759521484375e-06s
INFO | --- Analysis for ontobeef-domain took 32.60269737243652s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.9591064453125e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.28760385513305664s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.020583391189575195s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 9.274482727050781e-05s
Believability | Calculation of trust value for Ontos News Portal took 6.67572021484375e-06s
INFO | --- Analysis for ontos-news-portal took 3.7894129753112793s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 4.982948303222656e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0006859302520751953s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.288297176361084s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.020728349685668945s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0008740425109863281s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 4.1961669921875e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 6.9141387939453125e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 10.558193445205688s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 4.57763671875e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.2843012809753418s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.020241498947143555s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.000732421875s
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 1.3113021850585938e-05s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 3.0756454467773438s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 4.3392181396484375e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.30882740020751953s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.02070474624633789s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 4.6253204345703125e-05s
Believability | Calculation of trust value for Open Data Euskadi took 4.5299530029296875e-06s
INFO | --- Analysis for open-data-euskadi took 8.623657703399658s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 4.38690185546875e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.2768254280090332s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.02020883560180664s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.0001010894775390625s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 7.62939453125e-06s
INFO | --- Analysis for open-data-risp took 8.044930458068848s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.14310121536254883s
Availability | VoID file availability check for Open Data Thesaurus took 0.0007030963897705078s
Extra | Recovery of all triples for Open Data Thesaurus took 1.21724534034729s
Performance | Total latancy measurement for Open Data Thesaurus took 0.5016319751739502s
Amount of data | Number of triples check for Open Data Thesaurus took 0.11421513557434082s
Interoperability | New terms check for Open Data Thesaurus took 1.4378430843353271s
Versatility | Languages check for Open Data Thesaurus took 0.10984921455383301s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.12999200820922852s
Security | Check HTTPS for Open Data Thesaurus took 0.35796403884887695s
Interpretability | RDF structures check for Open Data Thesaurus took 0.1376054286956787s
Versatility | Serialization formats check for Open Data Thesaurus took 0.12065935134887695s
Availability | RDF dump link check for Open Data Thesaurus took 1.1264827251434326s
License | MR license check for Open Data Thesaurus took 0.1365339756011963s
License | HR license check for Open Data Thesaurus took 0.11131930351257324s
Amount of data | Number of property check for Open Data Thesaurus took 0.10322451591491699s
Understandability | Number of label check for Open Data Thesaurus took 0.1263291835784912s
Understandability | URI regex check for Open Data Thesaurus took 0.15781021118164062s
Understandability | Vocabs check for Open Data Thesaurus took 0.12497496604919434s
Verifiability | Authors check for Open Data Thesaurus took 0.12531375885009766s
Verifiability | Publishers check for Open Data Thesaurus took 0.11826276779174805s
Performance | Throughput check for Open Data Thesaurus took 10.408711671829224s
Amount of data | Check the number of entities for Open Data Thesaurus took 6.222724914550781e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.12548351287841797s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.12510991096496582s
Interlinking | skos check for Open Data Thesaurus took 0.11928510665893555s
Interlinking | skos check for Open Data Thesaurus took 0.08581066131591797s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.09305214881896973s
Currency | Creation date check for Open Data Thesaurus took 0.17862319946289062s
Currency | Modification date check for Open Data Thesaurus took 0.20745635032653809s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.5051534175872803s
Interoperability | New vocabularies check for Open Data Thesaurus took 1.0354630947113037s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.11788201332092285s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.07925200462341309s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.11083388328552246s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.1859593391418457s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011591911315917969s
Consistency | Disjoint class check for Open Data Thesaurus took 0.099395751953125s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.19805192947387695s
Consistency | Misplaced classes for Open Data Thesaurus took 0.07904839515686035s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.4894828796386719s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.3950402736663818s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.00014090538024902344s
Security | Sign check for Open Data Thesaurus took 0.0782928466796875s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.2917153835296631s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.02007460594177246s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 7.939338684082031e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Thesaurus took 0.7090573310852051s
Believability | Calculation of trust value for Open Data Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for open-data-thesaurus took 64.18803071975708s
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.0002589225769042969s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.2933168411254883s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.020200252532958984s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 2.8848648071289062e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 7.62939453125e-06s
INFO | --- Analysis for open-data-tor-vergata took 3.1621031761169434s
Availability | SPARQL endpoint availability check for Open Election Data Project took 9.131431579589844e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0007281303405761719s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.28223466873168945s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.0201108455657959s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.794929504394531e-05s
Believability | Calculation of trust value for Open Election Data Project took 6.198883056640625e-06s
INFO | --- Analysis for open-election-data-project took 3.3650901317596436s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 3.7498292922973633s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.2854897975921631s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.028303861618041992s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0015003681182861328s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 0.00013184547424316406s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 8.106231689453125e-06s
INFO | --- Analysis for open-energy-info-wiki took 10.856566429138184s
Availability | SPARQL endpoint availability check for Open Library took 4.220008850097656e-05s
Availability | VoID file availability check for Open Library took 0.0007214546203613281s
Completeness | Calculation of interlinking completeness for Open Library took 0.29842591285705566s
Reputation | Calculation of the PageRank for Open Library took 0.020115375518798828s
Interlinking | Calculation of Degree of Connection for Open Library took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Library took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Open Library took 8.749961853027344e-05s
Believability | Calculation of trust value for Open Library took 7.62939453125e-06s
INFO | --- Analysis for open-library took 9.824975967407227s
Availability | SPARQL endpoint availability check for Open Directory took 4.267692565917969e-05s
Availability | VoID file availability check for Open Directory took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for Open Directory took 0.2662487030029297s
Reputation | Calculation of the PageRank for Open Directory took 0.02026224136352539s
Interlinking | Calculation of Degree of Connection for Open Directory took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Directory took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Open Directory took 2.9087066650390625e-05s
Believability | Calculation of trust value for Open Directory took 7.3909759521484375e-06s
INFO | --- Analysis for open_directory took 3.0941407680511475s
Availability | SPARQL endpoint availability check for flyatlas took 1.6638004779815674s
Availability | VoID file availability check for flyatlas took 0.0012164115905761719s
Completeness | Calculation of interlinking completeness for flyatlas took 0.2824270725250244s
Reputation | Calculation of the PageRank for flyatlas took 0.020154237747192383s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for flyatlas took 2.7894973754882812e-05s
Believability | Calculation of trust value for flyatlas took 8.106231689453125e-06s
INFO | --- Analysis for openbiomed-flyatlas took 10.401342630386353s
Availability | SPARQL endpoint availability check for OpenCalais took 4.1484832763671875e-05s
Availability | VoID file availability check for OpenCalais took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.28327012062072754s
Reputation | Calculation of the PageRank for OpenCalais took 0.0201265811920166s
Interlinking | Calculation of Degree of Connection for OpenCalais took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.0001232624053955078s
Believability | Calculation of trust value for OpenCalais took 7.3909759521484375e-06s
INFO | --- Analysis for opencalais took 4.8051111698150635s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 4.839897155761719e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.3064596652984619s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.02046966552734375s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007200241088867188s
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 4.76837158203125e-06s
INFO | --- Analysis for opencorporates took 3.1314780712127686s
Availability | SPARQL endpoint availability check for OpenCyc took 4.315376281738281e-05s
Availability | VoID file availability check for OpenCyc took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.28165555000305176s
Reputation | Calculation of the PageRank for OpenCyc took 0.02027750015258789s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00010704994201660156s
Believability | Calculation of trust value for OpenCyc took 6.9141387939453125e-06s
INFO | --- Analysis for opencyc took 2.636741876602173s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 5.4836273193359375e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.001425027847290039s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.28198814392089844s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.0202028751373291s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.314018249511719e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 3.281102180480957s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0005795955657958984s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.3002355098724365s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.020093917846679688s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 3.528594970703125e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 3.398794174194336s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 5.91278076171875e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.2973358631134033s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.020438194274902344s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0010771751403808594s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.6591203212738037s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 8.320808410644531e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.2907135486602783s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.020310163497924805s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0008931159973144531s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 4.673004150390625e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.561159610748291s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.2732830047607422s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.02026081085205078s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0009427070617675781s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 1.71661376953125e-05s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 3.248650550842285s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 5.7697296142578125e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.2884337902069092s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.020775556564331055s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-households-projections-population took 3.8332889080047607s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0007216930389404297s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.2827606201171875s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.02121257781982422s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0009438991546630859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 4.11272931098938s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.26384425163269043s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.020276784896850586s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 5.173683166503906e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.5856924057006836s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.792213439941406e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0006234645843505859s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.308422327041626s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.020428895950317383s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.886222839355469e-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 5.033875942230225s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.26944518089294434s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.020853757858276367s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-housing-market took 4.0178680419921875s
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.0006418228149414062s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.26865172386169434s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 3.89785099029541s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.27144694328308105s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.020461559295654297s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 3.2683725357055664s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 5.626678466796875e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.29711389541625977s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.0205841064453125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 3.5356080532073975s
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.0004742145538330078s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.275038480758667s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.020429134368896484s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.462249279022217s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.839897155761719e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.2689089775085449s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.0203857421875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 6.198883056640625e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 3.2323033809661865s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.29851388931274414s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.02040886878967285s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 3.260248899459839s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.30105161666870117s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.02050471305847168s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 6.198883056640625e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 3.310610771179199s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 4.553794860839844e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.2955622673034668s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.021363258361816406s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.744529724121094e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 3.4026787281036377s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 7.700920104980469e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0003039836883544922s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.2791261672973633s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.024147510528564453s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0009968280792236328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 4.9114227294921875e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.60064959526062s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.2709522247314453s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.02013874053955078s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 3.349801540374756s
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.0005879402160644531s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.30483508110046387s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.019959449768066406s
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.000728607177734375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 3.9327354431152344s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0007252693176269531s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.2989368438720703s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.02066636085510254s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0008273124694824219s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-service-expenditure took 3.0636301040649414s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 5.9604644775390625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0006444454193115234s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.27805638313293457s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020691394805908203s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0008955001831054688s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.9114227294921875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.346637010574341s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.506111145019531e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0006892681121826172s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.30889368057250977s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.02034926414489746s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 3.4084279537200928s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 5.4836273193359375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.2958683967590332s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.020534276962280273s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 5.041537523269653s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 9.679794311523438e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0005502700805664062s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.27358150482177734s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.38690185546875e-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.1910781860351562s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 5.91278076171875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007379055023193359s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.2810356616973877s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.020471572875976562s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 3.356325626373291s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.28075313568115234s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.02057361602783203s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.0728836059570312e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.257570266723633s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0012874603271484375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.2876582145690918s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.02019190788269043s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.696846008300781e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.961293697357178s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.744529724121094e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.28151416778564453s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.020589590072631836s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.3697285652160645s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.5299530029296875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.27101731300354004s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.02035212516784668s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.542262077331543s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.26030468940734863s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.020295381546020508s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 3.7630667686462402s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0006434917449951172s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.3004446029663086s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.020197153091430664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.673004150390625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 3.0495777130126953s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.3026614189147949s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.020555973052978516s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.5514652729034424s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.2926504611968994s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.020462751388549805s
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.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.5739734172821045s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0006062984466552734s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.27169251441955566s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.020387649536132812s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.6253204345703125e-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.330000877380371s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.280534029006958s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.020420074462890625s
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.00072479248046875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.025340557098389s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.26932239532470703s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.02033376693725586s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 4.066788196563721s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0004177093505859375s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.31163859367370605s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.020444154739379883s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.52587890625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 5.1975250244140625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 3.421923875808716s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007205009460449219s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.2757143974304199s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.020465373992919922s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.792213439941406e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 3.881002426147461s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 8.893013000488281e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0008347034454345703s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.29549360275268555s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.020718097686767578s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.053438425064087s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.2928884029388428s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 9.298324584960938e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.14241886138916s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0007314682006835938s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.26000094413757324s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.020603656768798828s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 8.821487426757812e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 4.114465951919556s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 5.834261178970337s
Availability | VoID file availability check for Open Data of Ecuador took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.2942194938659668s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.020483016967773438s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.463859558105469e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 1.3828277587890625e-05s
INFO | --- Analysis for opendataec took 11.291488409042358s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0006427764892578125s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.2853734493255615s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.020577430725097656s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 8.821487426757812e-06s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.972997426986694s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 5.125999450683594e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.2957291603088379s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.020139694213867188s
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.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 7.867813110351562e-06s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 4.658096551895142s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 5.745887756347656e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.3119685649871826s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020546436309814453s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.814697265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 8.344650268554688e-06s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 3.2006845474243164s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 4.291534423828125e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.30982542037963867s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.020837068557739258s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 9.059906005859375e-06s
INFO | --- Analysis for opendatascotland-simd-education-rank took 2.990636110305786s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.2861194610595703s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.020339488983154297s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 2.9643425941467285s
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.0005819797515869141s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.28768062591552734s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.02035832405090332s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 3.0189743041992188s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 4.291534423828125e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0003228187561035156s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.2804849147796631s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.0202634334564209s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 7.867813110351562e-06s
INFO | --- Analysis for opendatascotland-simd-health-rank took 2.945369005203247s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 4.315376281738281e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.00035834312438964844s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.27114295959472656s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.020267009735107422s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 8.58306884765625e-06s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 2.843210220336914s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 5.459785461425781e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.27524328231811523s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.020207643508911133s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 8.821487426757812e-06s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.5667197704315186s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.542620420455933s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.30666041374206543s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.0206906795501709s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.147125244140625e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.33514404296875e-05s
INFO | --- Analysis for openlink-lod-cache took 63.29457235336304s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 4.220008850097656e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0007309913635253906s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.34041619300842285s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.02023911476135254s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.012222290039062e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 4.76837158203125e-06s
INFO | --- Analysis for openlylocal took 22.5535945892334s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 1.338679313659668s
Availability | VoID file availability check for OpenMobileNetwork took 0.0006763935089111328s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.30363965034484863s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.02042841911315918s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.295608520507812e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 7.62939453125e-06s
INFO | --- Analysis for openmobilenetwork took 4.412899494171143s
Availability | SPARQL endpoint availability check for OpenTox took 4.553794860839844e-05s
Availability | VoID file availability check for OpenTox took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for OpenTox took 0.2904369831085205s
Reputation | Calculation of the PageRank for OpenTox took 0.020441293716430664s
Interlinking | Calculation of Degree of Connection for OpenTox took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OpenTox took 0.0009264945983886719s
Interlinking | Calculation of Clustering coefficient for OpenTox took 3.62396240234375e-05s
Believability | Calculation of trust value for OpenTox took 8.58306884765625e-06s
INFO | --- Analysis for opentox took 3.1377296447753906s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 4.363059997558594e-05s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.3099696636199951s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.02024245262145996s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 2.9325485229492188e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 8.58306884765625e-06s
INFO | --- Analysis for openuplabs took 3.3571436405181885s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 4.2438507080078125e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.311413049697876s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.020383596420288086s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 2.86102294921875e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 7.867813110351562e-06s
INFO | --- Analysis for opus took 3.129343032836914s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 4.315376281738281e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.2603569030761719s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.020177841186523438s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 3.3855438232421875e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 1.33514404296875e-05s
INFO | --- Analysis for orcid took 3.164792537689209s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 1.143897294998169s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.27715396881103516s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.02053999900817871s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 9.417533874511719e-05s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for ordnance-survey-linked-data took 6.312266826629639s
Availability | SPARQL endpoint availability check for oreilly took 4.9114227294921875e-05s
Availability | VoID file availability check for oreilly took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for oreilly took 0.2835547924041748s
Reputation | Calculation of the PageRank for oreilly took 0.020800113677978516s
Interlinking | Calculation of Degree of Connection for oreilly took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0010890960693359375s
Interlinking | Calculation of Clustering coefficient for oreilly took 5.793571472167969e-05s
Believability | Calculation of trust value for oreilly took 1.0967254638671875e-05s
INFO | --- Analysis for oreilly took 5.962427377700806s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.14377713203430176s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.27492809295654297s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 8.106231689453125e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for organic-edunet took 10.267100095748901s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 3.0769402980804443s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.27520036697387695s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.0199739933013916s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 7.987022399902344e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 6.9141387939453125e-06s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 29.352247714996338s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.535874366760254s
Availability | VoID file availability check for OSM Semantic Network took 0.000690460205078125s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.2864203453063965s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.020735740661621094s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.886222839355469e-05s
Believability | Calculation of trust value for OSM Semantic Network took 1.3828277587890625e-05s
INFO | --- Analysis for osm-semantic-network took 8.352717876434326s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 4.220008850097656e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.30809807777404785s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.020294189453125s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 2.8133392333984375e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 8.344650268554688e-06s
INFO | --- Analysis for ounl-dspace-in-rdf took 3.187819480895996s
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.0002574920654296875s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.3091416358947754s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020267963409423828s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 1.3589859008789062e-05s
INFO | --- Analysis for ox-ac-uk-catalogue took 3.1222424507141113s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.029273986816406e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.31928229331970215s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020468473434448242s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.956390380859375e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 6.9141387939453125e-06s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 3.185556411743164s
Availability | SPARQL endpoint availability check for OpenMeters (University of Oxford) took 4.1484832763671875e-05s
Availability | VoID file availability check for OpenMeters (University of Oxford) took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.2523505687713623s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 2.9802322387695312e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 7.867813110351562e-06s
INFO | --- Analysis for ox-ac-uk-openmeters took 3.0516068935394287s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 5.412101745605469e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.2959403991699219s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.020784378051757812s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0008866786956787109s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 3.719329833984375e-05s
Believability | Calculation of trust value for Time-series metadata (University of Oxford) took 7.867813110351562e-06s
INFO | --- Analysis for ox-ac-uk-timeseries took 3.117249011993408s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 4.1484832763671875e-05s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.29796385765075684s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.020389556884765625s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 0.00013327598571777344s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 7.152557373046875e-06s
INFO | --- Analysis for ox-ac-uk-vacancies took 3.2330362796783447s
Availability | SPARQL endpoint availability check for Events calendar for the University (University of Oxford) took 4.100799560546875e-05s
Availability | VoID file availability check for Events calendar for the University (University of Oxford) took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.28711986541748047s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.020239830017089844s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0007722377777099609s
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 7.3909759521484375e-06s
INFO | --- Analysis for ox-ac-uk-www-ox-ac-uk-events took 3.1435084342956543s
Availability | SPARQL endpoint availability check for OxPoints (University of Oxford) took 4.601478576660156e-05s
Availability | VoID file availability check for OxPoints (University of Oxford) took 0.00030493736267089844s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.2666952610015869s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.020572185516357422s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 3.1948089599609375e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 8.58306884765625e-06s
INFO | --- Analysis for oxpoints took 3.1849632263183594s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.8420298099517822s
Availability | VoID file availability check for Pali English Lexicon took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.28087806701660156s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.02020573616027832s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 3.0279159545898438e-05s
Believability | Calculation of trust value for Pali English Lexicon took 7.3909759521484375e-06s
INFO | --- Analysis for pali-english-lexicon took 7.476623773574829s
Availability | SPARQL endpoint availability check for PanLex took 1.280259132385254s
Availability | VoID file availability check for PanLex took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for PanLex took 0.298572301864624s
Reputation | Calculation of the PageRank for PanLex took 0.020348787307739258s
Interlinking | Calculation of Degree of Connection for PanLex took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.605552673339844e-05s
Believability | Calculation of trust value for PanLex took 1.621246337890625e-05s
INFO | --- Analysis for panlex took 5.624500036239624s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.055425405502319336s
Availability | VoID file availability check for patents.data.gov.uk took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.3204336166381836s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.020080089569091797s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 4.887580871582031e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 5.7220458984375e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.71113657951355s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 4.5299530029296875e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.28040623664855957s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.020971059799194336s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 4.220008850097656e-05s
Believability | Calculation of trust value for PDEV-Lemon took 9.059906005859375e-06s
INFO | --- Analysis for pdev-lemon took 4.150818586349487s
Availability | SPARQL endpoint availability check for pdevlemon took 5.9604644775390625e-05s
Availability | VoID file availability check for pdevlemon took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.2845644950866699s
Reputation | Calculation of the PageRank for pdevlemon took 0.020360231399536133s
Interlinking | Calculation of Degree of Connection for pdevlemon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.24249267578125e-05s
Believability | Calculation of trust value for pdevlemon took 1.3828277587890625e-05s
INFO | --- Analysis for pdevlemon took 3.4845080375671387s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 4.220008850097656e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0008845329284667969s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.2943599224090576s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.02059769630432129s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007996559143066406s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 8.130073547363281e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 8.344650268554688e-06s
INFO | --- Analysis for periodo took 19.060921907424927s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.315376281738281e-05s
Availability | VoID file availability check for Personal_Homepages took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.29875636100769043s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.02043914794921875s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.0003871917724609375s
Believability | Calculation of trust value for Personal_Homepages took 9.298324584960938e-06s
INFO | --- Analysis for personal-homepages took 2.620251417160034s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 1.324577808380127s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.2674143314361572s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.02079033851623535s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0008299350738525391s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 2.765655517578125e-05s
INFO | --- Analysis for phoible took 5.1301634311676025s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.4345855712890625e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.2861957550048828s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.020457029342651367s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 0.00010561943054199219s
Believability | Calculation of trust value for PlanetData Project Wiki took 8.821487426757812e-06s
INFO | --- Analysis for planetdata-project-wiki took 2.773709774017334s
Availability | SPARQL endpoint availability check for Pleiades took 4.2438507080078125e-05s
Availability | VoID file availability check for Pleiades took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for Pleiades took 0.30805373191833496s
Reputation | Calculation of the PageRank for Pleiades took 0.02057957649230957s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.392333984375e-05s
Believability | Calculation of trust value for Pleiades took 9.775161743164062e-06s
INFO | --- Analysis for pleiades took 14.857646226882935s
Availability | SPARQL endpoint availability check for Poképédia took 4.506111145019531e-05s
Availability | VoID file availability check for Poképédia took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Poképédia took 0.2842066287994385s
Reputation | Calculation of the PageRank for Poképédia took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Poképédia took 7.009506225585938e-05s
Believability | Calculation of trust value for Poképédia took 1.4066696166992188e-05s
INFO | --- Analysis for pokepedia-fr took 2.907057523727417s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.772445678710938e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007073879241943359s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.273360013961792s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.02067732810974121s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.939338684082031e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.1682510375976562e-05s
INFO | --- Analysis for polymath-virtual-library took 5.955775499343872s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 4.267692565917969e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.2824704647064209s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.020554780960083008s
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.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 3.24249267578125e-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 3.12770938873291s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 4.2438507080078125e-05s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.30228519439697266s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.020502090454101562s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Corn trading volume and wholesale prices took 3.147125244140625e-05s
Believability | Calculation of trust value for Corn trading volume and wholesale prices took 8.821487426757812e-06s
INFO | --- Analysis for predicting-corn-trading-volume-and-wholesale-prices took 3.2965149879455566s
Availability | SPARQL endpoint availability check for Onion trading volume and wholesale prices took 4.744529724121094e-05s
Availability | VoID file availability check for Onion trading volume and wholesale prices took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.3203709125518799s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.020496606826782227s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 3.218650817871094e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 8.58306884765625e-06s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 3.2101783752441406s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 4.124641418457031e-05s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.3084678649902344s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.02047276496887207s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Potato trading volume and wholesale price took 3.266334533691406e-05s
Believability | Calculation of trust value for Potato trading volume and wholesale price took 7.867813110351562e-06s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 3.1625406742095947s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 4.1961669921875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.2769322395324707s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.020742416381835938s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of apples took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of apples took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 3.170967102050781e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of apples took 9.059906005859375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-apples took 3.1842904090881348s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 4.2438507080078125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.27811121940612793s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.021148681640625s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of barley took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of barley took 0.0011889934539794922s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of barley took 4.100799560546875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of barley took 7.867813110351562e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 3.177065849304199s
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.0002675056457519531s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.29546618461608887s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.02050638198852539s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of bean took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of bean took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of bean took 2.9802322387695312e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of bean took 8.58306884765625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 3.2884936332702637s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 4.1961669921875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.29233670234680176s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.020595073699951172s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 3.337860107421875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 8.821487426757812e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 3.1300084590911865s
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.0002894401550292969s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.2933685779571533s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 3.24249267578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of corn took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-corn took 3.225206136703491s
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.00042557716369628906s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.2793881893157959s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.02070164680480957s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0007376670837402344s
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 1.2874603271484375e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 3.116672992706299s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cucumber took 4.2438507080078125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cucumber took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.2918398380279541s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.020780086517333984s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 3.123283386230469e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 7.867813110351562e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 3.2014355659484863s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 4.267692565917969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.0003247261047363281s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.29247403144836426s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.020823955535888672s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of lettuce took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of lettuce took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 3.123283386230469e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 7.867813110351562e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 3.1272213459014893s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 4.124641418457031e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 0.2935364246368408s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.020484447479248047s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 3.409385681152344e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of onion took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-onion took 3.2090604305267334s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of oyster mushroom took 4.267692565917969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of oyster mushroom took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.2903146743774414s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.02046680450439453s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 3.170967102050781e-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 3.1789841651916504s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 4.3392181396484375e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.0006020069122314453s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.2939565181732178s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.020620346069335938s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of potato took 3.337860107421875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of potato took 8.58306884765625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-potato took 3.12526535987854s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of radish took 4.696846008300781e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of radish took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.2570478916168213s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.020571470260620117s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of radish took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of radish took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 3.170967102050781e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 3.1171188354492188s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 4.2438507080078125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.29155778884887695s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.02063131332397461s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of rice plant took 3.218650817871094e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of rice plant took 8.344650268554688e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 3.2256414890289307s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 4.2438507080078125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.2968406677246094s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.02069711685180664s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 3.123283386230469e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of watermelon took 9.775161743164062e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-watermelon took 3.283313035964966s
Availability | SPARQL endpoint availability check for prefix.cc took 8.0108642578125e-05s
Availability | VoID file availability check for prefix.cc took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.2631721496582031s
Reputation | Calculation of the PageRank for prefix.cc took 0.020666122436523438s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 4.172325134277344e-05s
Believability | Calculation of trust value for prefix.cc took 8.344650268554688e-06s
INFO | --- Analysis for prefix-cc took 3.6309027671813965s
Availability | SPARQL endpoint availability check for PreLex took 0.15059781074523926s
Availability | VoID file availability check for PreLex took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for PreLex took 0.2629518508911133s
Reputation | Calculation of the PageRank for PreLex took 0.02042365074157715s
Interlinking | Calculation of Degree of Connection for PreLex took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for PreLex took 7.05718994140625e-05s
Believability | Calculation of trust value for PreLex took 8.344650268554688e-06s
INFO | --- Analysis for prelex took 2.8326544761657715s
Availability | SPARQL endpoint availability check for Prelinger Archives took 2.175872802734375s
Availability | VoID file availability check for Prelinger Archives took 0.0008563995361328125s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.2732357978820801s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.020813465118408203s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.314018249511719e-05s
Believability | Calculation of trust value for Prelinger Archives took 5.9604644775390625e-06s
INFO | --- Analysis for prelinger_archives took 10.76463508605957s
Availability | SPARQL endpoint availability check for PreMOn (Predicate Model for Ontologies) took 0.44318509101867676s
Availability | VoID file availability check for PreMOn (Predicate Model for Ontologies) took 0.0005795955657958984s
Extra | Recovery of all triples for PreMOn (Predicate Model for Ontologies) took 4.381032466888428s
Performance | Total latancy measurement for PreMOn (Predicate Model for Ontologies) took 0.8944251537322998s
Amount of data | Number of triples check for PreMOn (Predicate Model for Ontologies) took 0.08285045623779297s
Interoperability | New terms check for PreMOn (Predicate Model for Ontologies) took 2.2610881328582764s
Versatility | Languages check for PreMOn (Predicate Model for Ontologies) took 58.23167824745178s
Interpretability | Number of blank nodes check for PreMOn (Predicate Model for Ontologies) took 0.11423087120056152s
Security | Check HTTPS for PreMOn (Predicate Model for Ontologies) took 0.08515214920043945s
Interpretability | RDF structures check for PreMOn (Predicate Model for Ontologies) took 0.17955923080444336s
Versatility | Serialization formats check for PreMOn (Predicate Model for Ontologies) took 0.28507041931152344s
Availability | RDF dump link check for PreMOn (Predicate Model for Ontologies) took 0.2613213062286377s
License | MR license check for PreMOn (Predicate Model for Ontologies) took 0.3817892074584961s
License | HR license check for PreMOn (Predicate Model for Ontologies) took 1.2464826107025146s
Amount of data | Number of property check for PreMOn (Predicate Model for Ontologies) took 0.23639249801635742s
Understandability | Number of label check for PreMOn (Predicate Model for Ontologies) took 0.09133577346801758s
Understandability | URI regex check for PreMOn (Predicate Model for Ontologies) took 0.4072573184967041s
Understandability | Vocabs check for PreMOn (Predicate Model for Ontologies) took 0.3249955177307129s
Verifiability | Authors check for PreMOn (Predicate Model for Ontologies) took 0.21378040313720703s
Verifiability | Publishers check for PreMOn (Predicate Model for Ontologies) took 0.2796902656555176s
Performance | Throughput check for PreMOn (Predicate Model for Ontologies) took 10.963536977767944s
Amount of data | Check the number of entities for PreMOn (Predicate Model for Ontologies) took 8.511543273925781e-05s
Verifiability | Contribs. check for PreMOn (Predicate Model for Ontologies) took 0.21082234382629395s
Interlinking | sameAs chians check for PreMOn (Predicate Model for Ontologies) took 0.0951838493347168s
Interlinking | skos check for PreMOn (Predicate Model for Ontologies) took 0.09896516799926758s
Interlinking | skos check for PreMOn (Predicate Model for Ontologies) took 0.09014081954956055s
Timeliness | dataset update frequency check for PreMOn (Predicate Model for Ontologies) took 0.21019577980041504s
Currency | Creation date check for PreMOn (Predicate Model for Ontologies) took 0.4136831760406494s
Currency | Modification date check for PreMOn (Predicate Model for Ontologies) took 0.41498279571533203s
Rep.Conc. | URIs length for PreMOn (Predicate Model for Ontologies) took 3.8585643768310547s
Interoperability | New vocabularies check for PreMOn (Predicate Model for Ontologies) took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for PreMOn (Predicate Model for Ontologies) took 0.2024250030517578s
Accuracy | Check Empty annotation labels for PreMOn (Predicate Model for Ontologies) took 1.7996623516082764s
Accuracy | Check White space in annotation for PreMOn (Predicate Model for Ontologies) took 0.08190584182739258s
Accuracy | Check Datatype consistency for PreMOn (Predicate Model for Ontologies) took 0.08783245086669922s
Consistency | Disjoint class check for PreMOn (Predicate Model for Ontologies) took 0.21110105514526367s
Consistency | Check Misplaced properties for PreMOn (Predicate Model for Ontologies) took 2.0480849742889404s
Consistency | Misplaced classes for PreMOn (Predicate Model for Ontologies) took 0.45769739151000977s
Consistency | Check Ontology hijacking for PreMOn (Predicate Model for Ontologies) took 2.566972255706787s
Consistency | Check Invalid usage of undefined classes for PreMOn (Predicate Model for Ontologies) took 1.3486990928649902s
Consistency | Check Invalid usage of undefined properties for PreMOn (Predicate Model for Ontologies) took 3.0109457969665527s
Conciseness | Check Extensional conciseness for PreMOn (Predicate Model for Ontologies) took 0.09036803245544434s
Conciseness | Check Intensional conciseness for PreMOn (Predicate Model for Ontologies) took 0.218858003616333s
Security | Sign check for PreMOn (Predicate Model for Ontologies) took 0.20380806922912598s
Availability | Check URIs Dereferenciability for PreMOn (Predicate Model for Ontologies) took 1136.4773948192596s
Completeness | Calculation of interlinking completeness for PreMOn (Predicate Model for Ontologies) took 0.6666178703308105s
Reputation | Calculation of the PageRank for PreMOn (Predicate Model for Ontologies) took 0.02132129669189453s
Interlinking | Calculation of Degree of Connection for PreMOn (Predicate Model for Ontologies) took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for PreMOn (Predicate Model for Ontologies) took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for PreMOn (Predicate Model for Ontologies) took 6.151199340820312e-05s
Interoperability | Check the re-using of existing vocabs for PreMOn (Predicate Model for Ontologies) took 1.430511474609375e-06s
Believability | Calculation of trust value for PreMOn (Predicate Model for Ontologies) took 8.344650268554688e-06s
INFO | --- Analysis for premon took 1258.7884874343872s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 4.887580871582031e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.27172017097473145s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.555152893066406e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 1.6927719116210938e-05s
INFO | --- Analysis for princeton-library-findingaids took 4.924997568130493s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.608572244644165s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.3123788833618164s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.020369291305541992s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 7.963180541992188e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.821487426757812e-06s
INFO | --- Analysis for printed-book-auction-catalogues took 4.9455156326293945s
Availability | SPARQL endpoint availability check for Procedimientos, trámites y servicios took 4.291534423828125e-05s
Availability | VoID file availability check for Procedimientos, trámites y servicios took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.274432897567749s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.020657777786254883s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 2.9802322387695312e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 8.106231689453125e-06s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 3.6533780097961426s
Availability | SPARQL endpoint availability check for Procomún SPARQL took 4.3392181396484375e-05s
Availability | VoID file availability check for Procomún SPARQL took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Procomún SPARQL took 0.2991349697113037s
Reputation | Calculation of the PageRank for Procomún SPARQL took 0.020282506942749023s
Interlinking | Calculation of Degree of Connection for Procomún SPARQL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Procomún SPARQL took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Procomún SPARQL took 3.0517578125e-05s
Believability | Calculation of trust value for Procomún SPARQL took 7.867813110351562e-06s
INFO | --- Analysis for procomun-sparql took 3.2057278156280518s
Availability | SPARQL endpoint availability check for PROD - JISC Project Directory in RDF took 4.172325134277344e-05s
Availability | VoID file availability check for PROD - JISC Project Directory in RDF took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for PROD - JISC Project Directory in RDF took 0.29979610443115234s
Reputation | Calculation of the PageRank for PROD - JISC Project Directory in RDF took 0.020520687103271484s
Interlinking | Calculation of Degree of Connection for PROD - JISC Project Directory in RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PROD - JISC Project Directory in RDF took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for PROD - JISC Project Directory in RDF took 3.075599670410156e-05s
Believability | Calculation of trust value for PROD - JISC Project Directory in RDF took 8.106231689453125e-06s
INFO | --- Analysis for prod-jisc-project-directory-in-rdf took 3.6745076179504395s
Availability | SPARQL endpoint availability check for ProductDB took 4.252733945846558s
Availability | VoID file availability check for ProductDB took 0.0006539821624755859s
Completeness | Calculation of interlinking completeness for ProductDB took 0.29531002044677734s
Reputation | Calculation of the PageRank for ProductDB took 0.020395278930664062s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.414817810058594e-05s
Believability | Calculation of trust value for ProductDB took 8.821487426757812e-06s
INFO | --- Analysis for productdb took 9.422645330429077s
Availability | SPARQL endpoint availability check for Product Types Ontology took 7.891654968261719e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.2856903076171875s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 7.677078247070312e-05s
Believability | Calculation of trust value for Product Types Ontology took 1.239776611328125e-05s
INFO | --- Analysis for productontology took 3.5385687351226807s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 4.2438507080078125e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.279238224029541s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.020183801651000977s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.00010061264038085938s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 8.106231689453125e-06s
INFO | --- Analysis for prospects-and-trends-gnoss took 7.972144603729248s
Availability | SPARQL endpoint availability check for provenanceweb took 0.04567670822143555s
Availability | VoID file availability check for provenanceweb took 0.0002868175506591797s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.26645755767822266s
Reputation | Calculation of the PageRank for provenanceweb took 0.02075982093811035s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 8.869171142578125e-05s
Believability | Calculation of trust value for provenanceweb took 8.344650268554688e-06s
INFO | --- Analysis for provenanceweb took 47.08744287490845s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 4.3392181396484375e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.2710394859313965s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.020606517791748047s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0009751319885253906s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.00013136863708496094s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 8.106231689453125e-06s
INFO | --- Analysis for proyectoapadrina took 7.854224681854248s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 25.018209218978882s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0008511543273925781s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.4318807125091553s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.020341157913208008s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 3.3855438232421875e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 8.344650268554688e-06s
INFO | --- Analysis for pscs-catalogue took 126.4346055984497s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 4.363059997558594e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.3087613582611084s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.02058577537536621s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.176399230957031e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 9.059906005859375e-06s
INFO | --- Analysis for psh-subject-headings took 3.1391031742095947s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 4.0531158447265625e-05s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.00029754638671875s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.3030686378479004s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.02015066146850586s
Interlinking | Calculation of Degree of Connection for Public Record Office Victoria Semantic Wiki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Public Record Office Victoria Semantic Wiki took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 3.0040740966796875e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 8.344650268554688e-06s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 3.1618354320526123s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 0.6535463333129883s
Availability | VoID file availability check for Public Spending in Greece took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.27234387397766113s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.021073579788208008s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 7.963180541992188e-05s
Believability | Calculation of trust value for Public Spending in Greece took 8.58306884765625e-06s
INFO | --- Analysis for public-spending-in-greece took 8.214815378189087s
Availability | SPARQL endpoint availability check for Publications of Charles University in Prague took 5.53131103515625e-05s
Availability | VoID file availability check for Publications of Charles University in Prague took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.30676960945129395s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.021054506301879883s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.0008172988891601562s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 3.695487976074219e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 8.58306884765625e-06s
INFO | --- Analysis for publications-of-charles-university-in-prague took 3.6422488689422607s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 4.220008850097656e-05s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.00029468536376953125s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.2874603271484375s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.020424842834472656s
Interlinking | Calculation of Degree of Connection for Publikace Univerzity Karlovy v Praze took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Publikace Univerzity Karlovy v Praze took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 3.0279159545898438e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 8.58306884765625e-06s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 3.122981309890747s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 0.00010514259338378906s
Availability | VoID file availability check for qualitywebdata.org took 0.0002956390380859375s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 0.2943136692047119s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.02039813995361328s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 3.0279159545898438e-05s
Believability | Calculation of trust value for qualitywebdata.org took 8.58306884765625e-06s
INFO | --- Analysis for qualitywebdata-org took 3.161752223968506s
Availability | SPARQL endpoint availability check for Quotations Book took 4.00543212890625e-05s
Availability | VoID file availability check for Quotations Book took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for Quotations Book took 0.27051591873168945s
Reputation | Calculation of the PageRank for Quotations Book took 0.02034449577331543s
Interlinking | Calculation of Degree of Connection for Quotations Book took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Quotations Book took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 3.0279159545898438e-05s
Believability | Calculation of trust value for Quotations Book took 9.059906005859375e-06s
INFO | --- Analysis for quotations_book took 3.1361348628997803s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.29687976837158203s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020173072814941406s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.552436828613281e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 8.106231689453125e-06s
INFO | --- Analysis for r4r took 4.180880546569824s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.2922511100769043s
Availability | VoID file availability check for Rådata nå! took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.2980310916900635s
Reputation | Calculation of the PageRank for Rådata nå! took 0.020384788513183594s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 0.00010967254638671875s
Believability | Calculation of trust value for Rådata nå! took 9.059906005859375e-06s
INFO | --- Analysis for radatana took 5.1079511642456055s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 7.295608520507812e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.2894153594970703s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.020138025283813477s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 3.886222839355469e-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 16.734848499298096s
Availability | SPARQL endpoint availability check for Raphael Research Resource took 4.220008850097656e-05s
Availability | VoID file availability check for Raphael Research Resource took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Raphael Research Resource took 0.2972261905670166s
Reputation | Calculation of the PageRank for Raphael Research Resource took 0.020287036895751953s
Interlinking | Calculation of Degree of Connection for Raphael Research Resource took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Raphael Research Resource took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Raphael Research Resource took 2.9087066650390625e-05s
Believability | Calculation of trust value for Raphael Research Resource took 8.344650268554688e-06s
INFO | --- Analysis for raphaelresearchresource took 3.1166024208068848s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 12.255584716796875s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.34415173530578613s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.02039170265197754s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 2.8371810913085938e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 7.152557373046875e-06s
INFO | --- Analysis for ravensburg-local-shopping-graph took 27.097411155700684s
Availability | SPARQL endpoint availability check for RCAHMS Archaeological Objects Thesaurus took 4.315376281738281e-05s
Availability | VoID file availability check for RCAHMS Archaeological Objects Thesaurus took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for RCAHMS Archaeological Objects Thesaurus took 0.29870176315307617s
Reputation | Calculation of the PageRank for RCAHMS Archaeological Objects Thesaurus took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for RCAHMS Archaeological Objects Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RCAHMS Archaeological Objects Thesaurus took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for RCAHMS Archaeological Objects Thesaurus took 2.956390380859375e-05s
Believability | Calculation of trust value for RCAHMS Archaeological Objects Thesaurus took 9.298324584960938e-06s
INFO | --- Analysis for rcahms-archaeological-objects-thesaurus took 3.02677059173584s
Availability | SPARQL endpoint availability check for RCAHMS Maritime Craft Thesaurus took 9.059906005859375e-05s
Availability | VoID file availability check for RCAHMS Maritime Craft Thesaurus took 0.0003001689910888672s
Completeness | Calculation of interlinking completeness for RCAHMS Maritime Craft Thesaurus took 0.2760171890258789s
Reputation | Calculation of the PageRank for RCAHMS Maritime Craft Thesaurus took 0.020426034927368164s
Interlinking | Calculation of Degree of Connection for RCAHMS Maritime Craft Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RCAHMS Maritime Craft Thesaurus took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for RCAHMS Maritime Craft Thesaurus took 3.1948089599609375e-05s
Believability | Calculation of trust value for RCAHMS Maritime Craft Thesaurus took 1.1444091796875e-05s
INFO | --- Analysis for rcahms-maritime-craft-thesaurus took 3.156970500946045s
Availability | SPARQL endpoint availability check for RCAHMS Monument Types Thesaurus took 4.124641418457031e-05s
Availability | VoID file availability check for RCAHMS Monument Types Thesaurus took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for RCAHMS Monument Types Thesaurus took 0.280468225479126s
Reputation | Calculation of the PageRank for RCAHMS Monument Types Thesaurus took 0.02068352699279785s
Interlinking | Calculation of Degree of Connection for RCAHMS Monument Types Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RCAHMS Monument Types Thesaurus took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for RCAHMS Monument Types Thesaurus took 3.24249267578125e-05s
Believability | Calculation of trust value for RCAHMS Monument Types Thesaurus took 1.4543533325195312e-05s
INFO | --- Analysis for rcahms-monument-types-thesaurus took 3.2268948554992676s
Availability | SPARQL endpoint availability check for RCAHMW Monument Types Thesaurus took 4.0531158447265625e-05s
Availability | VoID file availability check for RCAHMW Monument Types Thesaurus took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for RCAHMW Monument Types Thesaurus took 0.2957937717437744s
Reputation | Calculation of the PageRank for RCAHMW Monument Types Thesaurus took 0.02050638198852539s
Interlinking | Calculation of Degree of Connection for RCAHMW Monument Types Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RCAHMW Monument Types Thesaurus took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for RCAHMW Monument Types Thesaurus took 3.0040740966796875e-05s
Believability | Calculation of trust value for RCAHMW Monument Types Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for rcahmw-monument-types-thesaurus took 3.244901657104492s
Availability | SPARQL endpoint availability check for RCAHMW Periods List took 4.1484832763671875e-05s
Availability | VoID file availability check for RCAHMW Periods List took 0.0002956390380859375s
Completeness | Calculation of interlinking completeness for RCAHMW Periods List took 0.29746007919311523s
Reputation | Calculation of the PageRank for RCAHMW Periods List took 0.020707368850708008s
Interlinking | Calculation of Degree of Connection for RCAHMW Periods List took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RCAHMW Periods List took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for RCAHMW Periods List took 3.0279159545898438e-05s
Believability | Calculation of trust value for RCAHMW Periods List took 1.049041748046875e-05s
INFO | --- Analysis for rcahmw-periods-list took 3.138461112976074s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 4.410743713378906e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.28658342361450195s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.020370960235595703s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.535385131835938e-05s
Believability | Calculation of trust value for RDF Book Mashup took 5.7220458984375e-06s
INFO | --- Analysis for rdf-book-mashup took 3.3199198246002197s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 4.6253204345703125e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.2651188373565674s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.020336389541625977s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 9.894371032714844e-05s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 8.58306884765625e-06s
INFO | --- Analysis for rdfize-lastfm took 2.6262013912200928s
Availability | SPARQL endpoint availability check for RDFLicense took 261.16866850852966s
Availability | VoID file availability check for RDFLicense took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.4177846908569336s
Reputation | Calculation of the PageRank for RDFLicense took 0.02082657814025879s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 3.457069396972656e-05s
Believability | Calculation of trust value for RDFLicense took 7.62939453125e-06s
INFO | --- Analysis for rdflicense took 536.1891422271729s
Availability | SPARQL endpoint availability check for RDFohloh took 5.078315734863281e-05s
Availability | VoID file availability check for RDFohloh took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.26508116722106934s
Reputation | Calculation of the PageRank for RDFohloh took 0.020581722259521484s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 9.202957153320312e-05s
Believability | Calculation of trust value for RDFohloh took 9.298324584960938e-06s
INFO | --- Analysis for rdfohloh took 8.597819089889526s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.6372308731079102s
Availability | VoID file availability check for Reactome RDF took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.35349011421203613s
Reputation | Calculation of the PageRank for Reactome RDF took 0.021419048309326172s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0008034706115722656s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 4.982948303222656e-05s
Believability | Calculation of trust value for Reactome RDF took 1.0013580322265625e-05s
INFO | --- Analysis for reactome-rdf took 4.094113111495972s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 0.10474419593811035s
Availability | VoID file availability check for Rechtspraak.nl took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.28252267837524414s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.02010369300842285s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 9.1552734375e-05s
Believability | Calculation of trust value for Rechtspraak.nl took 6.198883056640625e-06s
INFO | --- Analysis for rechtspraak took 3.7018275260925293s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 4.267692565917969e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0007243156433105469s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.3093233108520508s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.021187543869018555s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 8.58306884765625e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 7.62939453125e-06s
INFO | --- Analysis for red-uno-internacional-santillana took 8.079870462417603s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.03278803825378418s
Availability | VoID file availability check for reference.data.gov.uk took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.2627580165863037s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.020175933837890625s
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.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.00015044212341308594s
Believability | Calculation of trust value for reference.data.gov.uk took 5.4836273193359375e-06s
INFO | --- Analysis for reference-data-gov-uk took 2.758051633834839s
Availability | SPARQL endpoint availability check for Regiony took 4.1484832763671875e-05s
Availability | VoID file availability check for Regiony took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Regiony took 0.29048800468444824s
Reputation | Calculation of the PageRank for Regiony took 0.02019524574279785s
Interlinking | Calculation of Degree of Connection for Regiony took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Regiony took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Regiony took 2.7894973754882812e-05s
Believability | Calculation of trust value for Regiony took 6.9141387939453125e-06s
INFO | --- Analysis for regiony took 4.028791666030884s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.19341254234313965s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0006084442138671875s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 1.6321041584014893s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 1.2648158073425293s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.4748249053955078s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.7208836078643799s
Versatility | Languages check for Repository for Linked Open Archival Data took 18.111586809158325s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 1.9943592548370361s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.5268270969390869s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.33614563941955566s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.4008216857910156s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.23953938484191895s
License | MR license check for Repository for Linked Open Archival Data took 0.6547417640686035s
License | HR license check for Repository for Linked Open Archival Data took 7.99506139755249s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.1423661708831787s
Understandability | Number of label check for Repository for Linked Open Archival Data took 1.135239839553833s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.3797271251678467s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.19570159912109375s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.24418139457702637s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.24072599411010742s
Performance | Throughput check for Repository for Linked Open Archival Data took 10.589593410491943s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 6.914138793945312e-05s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.29482603073120117s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.22061419486999512s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.511948823928833s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.14734387397766113s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.3445889949798584s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.40784311294555664s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.29063844680786133s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 2.6655282974243164s
Interoperability | New vocabularies check for Repository for Linked Open Archival Data took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Repository for Linked Open Archival Data took 0.156327486038208s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.1369328498840332s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.17380332946777344s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 0.6797389984130859s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.029407262802124023s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.028702497482299805s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.2530038356781006s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 2.0457193851470947s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.267270565032959s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.6970634460449219s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.3224575519561768s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 3.384418487548828s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.030330419540405273s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.32143163681030273s
Security | Sign check for Repository for Linked Open Archival Data took 0.5910346508026123s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 1237.8921360969543s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.5844542980194092s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.02118539810180664s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 4.458427429199219e-05s
Interoperability | Check the re-using of existing vocabs for Repository for Linked Open Archival Data took 1.9073486328125e-06s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 9.298324584960938e-06s
INFO | --- Analysis for reload took 1370.951147556305s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 1.7297325134277344s
Availability | VoID file availability check for Renewable Energy Generators took 0.0007586479187011719s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.293975830078125s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.696846008300781e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 5.245208740234375e-06s
INFO | --- Analysis for renewable_energy_generators took 12.158302068710327s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.08658647537231445s
Availability | VoID file availability check for research.data.gov.uk took 0.0003619194030761719s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.253798246383667s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.020801782608032227s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0008509159088134766s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 0.00010538101196289062s
Believability | Calculation of trust value for research.data.gov.uk took 5.7220458984375e-06s
INFO | --- Analysis for research-data-gov-uk took 3.031944513320923s
Availability | SPARQL endpoint availability check for Research object in Agricolture and Food of the University of Naples took 4.935264587402344e-05s
Availability | VoID file availability check for Research object in Agricolture and Food of the University of Naples took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Research object in Agricolture and Food of the University of Naples took 0.24083876609802246s
Reputation | Calculation of the PageRank for Research object in Agricolture and Food of the University of Naples took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for Research object in Agricolture and Food of the University of Naples took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Research object in Agricolture and Food of the University of Naples took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Research object in Agricolture and Food of the University of Naples took 3.123283386230469e-05s
Believability | Calculation of trust value for Research object in Agricolture and Food of the University of Naples took 7.867813110351562e-06s
INFO | --- Analysis for research-object-in-agricolture-and-food-of-the-university-of-naples took 3.8656957149505615s
Availability | SPARQL endpoint availability check for Restaurantes took 4.076957702636719e-05s
Availability | VoID file availability check for Restaurantes took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for Restaurantes took 0.2706418037414551s
Reputation | Calculation of the PageRank for Restaurantes took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for Restaurantes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Restaurantes took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Restaurantes took 3.147125244140625e-05s
Believability | Calculation of trust value for Restaurantes took 7.3909759521484375e-06s
INFO | --- Analysis for restaurantes-zaragoza took 3.5619373321533203s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 7.033348083496094e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.2821207046508789s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.020444154739379883s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 6.914138793945312e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 8.344650268554688e-06s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 4.23815131187439s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.2857532501220703s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.27983784675598145s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.020345449447631836s
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.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00011754035949707031s
Believability | Calculation of trust value for Revyu.com - Review Anything took 7.152557373046875e-06s
INFO | --- Analysis for revyu took 2.8209729194641113s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 4.458427429199219e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.27199792861938477s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.024590492248535156s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.001154184341430664s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 6.461143493652344e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 8.106231689453125e-06s
INFO | --- Analysis for riese took 2.6104977130889893s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection Data took 4.38690185546875e-05s
Availability | VoID file availability check for Rijksmuseum Collection Data took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection Data took 0.28316545486450195s
Reputation | Calculation of the PageRank for Rijksmuseum Collection Data took 0.020839929580688477s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection Data took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection Data took 3.4332275390625e-05s
Believability | Calculation of trust value for Rijksmuseum Collection Data took 8.344650268554688e-06s
INFO | --- Analysis for rijksmuseum took 3.0960447788238525s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.5765857696533203s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0006470680236816406s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.2714967727661133s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.020524263381958008s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 4.458427429199219e-05s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 7.152557373046875e-06s
INFO | --- Analysis for rism took 3.5871055126190186s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.20707440376281738s
Availability | VoID file availability check for RISM Authority data took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.2661147117614746s
Reputation | Calculation of the PageRank for RISM Authority data took 0.02044987678527832s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 4.506111145019531e-05s
Believability | Calculation of trust value for RISM Authority data took 7.3909759521484375e-06s
INFO | --- Analysis for rism-authorities took 3.270205497741699s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.04199028015136719s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00022649765014648438s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.24611616134643555s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.02063584327697754s
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.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00022792816162109375s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-acm took 2.484736442565918s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.02925252914428711s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.0002224445343017578s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.25963664054870605s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.020691394805908203s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.0001697540283203125s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-budapest took 2.436889410018921s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.03729844093322754s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.2677783966064453s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.020637989044189453s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.00019788742065429688s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-citeseer took 2.528912305831909s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.044342994689941406s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.26373982429504395s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.020366668701171875s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0008325576782226562s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00017762184143066406s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-cordis took 2.5294437408447266s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.04330301284790039s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.25179004669189453s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.020580530166625977s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.00015997886657714844s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-courseware took 2.4859445095062256s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.03757619857788086s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.26772236824035645s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.020343542098999023s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 3.743171691894531e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 5.7220458984375e-06s
INFO | --- Analysis for rkb-explorer-crime took 2.54293155670166s
Availability | SPARQL endpoint availability check for crm took 4.00543212890625e-05s
Availability | VoID file availability check for crm took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for crm took 0.2503058910369873s
Reputation | Calculation of the PageRank for crm took 0.020222187042236328s
Interlinking | Calculation of Degree of Connection for crm took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for crm took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for crm took 2.9325485229492188e-05s
Believability | Calculation of trust value for crm took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-crm took 2.9915521144866943s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.04445147514343262s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.2907445430755615s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.02032637596130371s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00011920928955078125s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-curriculum took 2.5382754802703857s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.04587149620056152s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.27684664726257324s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.02033376693725586s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 4.863739013671875e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.5987625122070312s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.049254655838012695s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.27393674850463867s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.020395755767822266s
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.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.00024390220642089844s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-dblp took 2.4744162559509277s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.04523587226867676s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.2697489261627197s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.020299673080444336s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.200241088867188e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-deepblue took 2.505948066711426s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.03473043441772461s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.2698037624359131s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.560585021972656e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-deploy took 2.484574317932129s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.04214835166931152s
Availability | VoID file availability check for digitaleconomy took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.27893924713134766s
Reputation | Calculation of the PageRank for digitaleconomy took 0.020308732986450195s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 2.9325485229492188e-05s
Believability | Calculation of trust value for digitaleconomy took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.503650188446045s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.04946494102478027s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.24017095565795898s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.000152587890625s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 1.33514404296875e-05s
INFO | --- Analysis for rkb-explorer-dotac took 2.526095390319824s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.05156564712524414s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2779350280761719s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02047252655029297s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.315376281738281e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-ecs took 2.793518543243408s
Availability | SPARQL endpoint availability check for enaktingpsi took 4.124641418457031e-05s
Availability | VoID file availability check for enaktingpsi took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for enaktingpsi took 0.27849531173706055s
Reputation | Calculation of the PageRank for enaktingpsi took 0.020370960235595703s
Interlinking | Calculation of Degree of Connection for enaktingpsi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for enaktingpsi took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for enaktingpsi took 2.765655517578125e-05s
Believability | Calculation of trust value for enaktingpsi took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-enaktingpsi took 2.981051445007324s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.04217410087585449s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.26513099670410156s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.020520925521850586s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00018334388732910156s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-eprints took 2.5051558017730713s
Availability | SPARQL endpoint availability check for epsrc took 0.04656362533569336s
Availability | VoID file availability check for epsrc took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for epsrc took 0.25684022903442383s
Reputation | Calculation of the PageRank for epsrc took 0.020152807235717773s
Interlinking | Calculation of Degree of Connection for epsrc took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.555152893066406e-05s
Believability | Calculation of trust value for epsrc took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-epsrc took 2.5344078540802s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.04988694190979004s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.24162864685058594s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0208740234375s
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.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 9.584426879882812e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-era took 2.5101051330566406s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.03427290916442871s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.25943470001220703s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.02046823501586914s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00010347366333007812s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-eurecom took 2.582153081893921s
Availability | SPARQL endpoint availability check for rkb-explorer-foreign took 4.1484832763671875e-05s
Availability | VoID file availability check for rkb-explorer-foreign took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for rkb-explorer-foreign took 0.2783992290496826s
Reputation | Calculation of the PageRank for rkb-explorer-foreign took 0.02045416831970215s
Interlinking | Calculation of Degree of Connection for rkb-explorer-foreign took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for rkb-explorer-foreign took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for rkb-explorer-foreign took 3.0517578125e-05s
Believability | Calculation of trust value for rkb-explorer-foreign took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-foreign took 2.970881462097168s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.04791259765625s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.2723205089569092s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.020476818084716797s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 8.916854858398438e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-ft took 2.5502779483795166s
Availability | SPARQL endpoint availability check for fun took 0.0510406494140625s
Availability | VoID file availability check for fun took 0.0007293224334716797s
Completeness | Calculation of interlinking completeness for fun took 0.25566744804382324s
Reputation | Calculation of the PageRank for fun took 0.020856142044067383s
Interlinking | Calculation of Degree of Connection for fun took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for fun took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for fun took 7.700920104980469e-05s
Believability | Calculation of trust value for fun took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-fun took 2.508917808532715s
Availability | SPARQL endpoint availability check for gdlc took 0.03988146781921387s
Availability | VoID file availability check for gdlc took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for gdlc took 0.2975630760192871s
Reputation | Calculation of the PageRank for gdlc took 0.020288944244384766s
Interlinking | Calculation of Degree of Connection for gdlc took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for gdlc took 7.05718994140625e-05s
Believability | Calculation of trust value for gdlc took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-gdlc took 2.5211985111236572s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.051816701889038086s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.00042247772216796875s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.29046177864074707s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.020681142807006836s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00011229515075683594s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-ibm took 2.59189772605896s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.04737257957458496s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.2819674015045166s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.02071380615234375s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.00013709068298339844s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-ieee took 2.613987922668457s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.045664072036743164s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.2932403087615967s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.020546913146972656s
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.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0001373291015625s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-irit took 2.534207344055176s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.04538869857788086s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.2736642360687256s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.020299196243286133s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.270408630371094e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-italy took 2.4962832927703857s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.05197715759277344s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.26569294929504395s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.02023172378540039s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.367134094238281e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 1.3828277587890625e-05s
INFO | --- Analysis for rkb-explorer-jisc took 2.5580809116363525s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.05077719688415527s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.27861785888671875s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.020314455032348633s
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.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.124641418457031e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-kaunas took 2.5612356662750244s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.045124053955078125s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.25305938720703125s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.020422697067260742s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0001652240753173828s
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.4640934467315674s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.044005632400512695s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.26812219619750977s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.02035236358642578s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.0001475811004638672s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-laas took 2.5456979274749756s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.03922414779663086s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.26640844345092773s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.02017068862915039s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.437301635742188e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-lisbon took 2.4798121452331543s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.03854990005493164s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.26664185523986816s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020142793655395508s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.0001537799835205078s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 2.507903814315796s
Availability | SPARQL endpoint availability check for notube took 0.04965329170227051s
Availability | VoID file availability check for notube took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for notube took 0.262908935546875s
Reputation | Calculation of the PageRank for notube took 0.020234107971191406s
Interlinking | Calculation of Degree of Connection for notube took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for notube took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for notube took 4.220008850097656e-05s
Believability | Calculation of trust value for notube took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-notube took 2.5002098083496094s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.04967832565307617s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.3168628215789795s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.02040696144104004s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00013518333435058594s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-nsf took 2.570542097091675s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.043106794357299805s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.31343650817871094s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0204770565032959s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00015687942504882812s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-oai took 2.656526565551758s
Availability | SPARQL endpoint availability check for OpenCyc (RKBExplorer) took 4.100799560546875e-05s
Availability | VoID file availability check for OpenCyc (RKBExplorer) took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for OpenCyc (RKBExplorer) took 0.2855558395385742s
Reputation | Calculation of the PageRank for OpenCyc (RKBExplorer) took 0.020114421844482422s
Interlinking | Calculation of Degree of Connection for OpenCyc (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenCyc (RKBExplorer) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for OpenCyc (RKBExplorer) took 2.86102294921875e-05s
Believability | Calculation of trust value for OpenCyc (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-opencyc took 2.9710636138916016s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.049152374267578125s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.27638912200927734s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.020282268524169922s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.462501525878906e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-os took 2.5313518047332764s
Availability | SPARQL endpoint availability check for photos took 0.04908609390258789s
Availability | VoID file availability check for photos took 0.0003483295440673828s
Completeness | Calculation of interlinking completeness for photos took 0.2652933597564697s
Reputation | Calculation of the PageRank for photos took 0.020168542861938477s
Interlinking | Calculation of Degree of Connection for photos took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for photos took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for photos took 7.033348083496094e-05s
Believability | Calculation of trust value for photos took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-photos took 2.4908108711242676s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.04631304740905762s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.3108510971069336s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.020205020904541016s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00011277198791503906s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 9.298324584960938e-06s
INFO | --- Analysis for rkb-explorer-pisa took 2.6153783798217773s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.052326202392578125s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0010280609130859375s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.28479456901550293s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.02021479606628418s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.0001914501190185547s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.534480094909668s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.04591822624206543s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0004267692565917969s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.28975844383239746s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0001373291015625s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-resex took 2.5217692852020264s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.0352325439453125s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.2778489589691162s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.02003622055053711s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 8.988380432128906e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-risks took 2.517561674118042s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.03715252876281738s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.27947187423706055s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.020177602767944336s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0001251697540283203s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-roma took 2.5218467712402344s
Availability | SPARQL endpoint availability check for roni took 0.049661874771118164s
Availability | VoID file availability check for roni took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for roni took 0.2918682098388672s
Reputation | Calculation of the PageRank for roni took 0.020421266555786133s
Interlinking | Calculation of Degree of Connection for roni took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for roni took 0.0008790493011474609s
Interlinking | Calculation of Clustering coefficient for roni took 3.314018249511719e-05s
Believability | Calculation of trust value for roni took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-roni took 2.5285887718200684s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.041455984115600586s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.26462602615356445s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.020668983459472656s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0002357959747314453s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-southampton took 2.5625786781311035s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.035546302795410156s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.0004322528839111328s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.28287363052368164s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.02067255973815918s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00011730194091796875s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-ulm took 2.5619633197784424s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.0471651554107666s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.2785511016845703s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.020595550537109375s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 0.00010132789611816406s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-unlocode took 2.5695531368255615s
Availability | SPARQL endpoint availability check for webconf took 0.045928001403808594s
Availability | VoID file availability check for webconf took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for webconf took 0.2807025909423828s
Reputation | Calculation of the PageRank for webconf took 0.020528793334960938s
Interlinking | Calculation of Degree of Connection for webconf took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00010609626770019531s
Believability | Calculation of trust value for webconf took 2.4557113647460938e-05s
INFO | --- Analysis for rkb-explorer-webconf took 12.828262090682983s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.04805636405944824s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.26987743377685547s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.020369768142700195s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007965564727783203s
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 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-webscience took 2.5230767726898193s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.0514376163482666s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.2641458511352539s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.020366907119750977s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.00021076202392578125s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-wiki took 2.6199796199798584s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.05193471908569336s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.27314090728759766s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.02034306526184082s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.250640869140625e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-wordnet took 2.5586600303649902s
Availability | SPARQL endpoint availability check for RKB Explorer Data took 5.3882598876953125e-05s
Availability | VoID file availability check for RKB Explorer Data took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for RKB Explorer Data took 0.278231143951416s
Reputation | Calculation of the PageRank for RKB Explorer Data took 0.02066826820373535s
Interlinking | Calculation of Degree of Connection for RKB Explorer Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RKB Explorer Data took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for RKB Explorer Data took 3.0517578125e-05s
Believability | Calculation of trust value for RKB Explorer Data took 1.239776611328125e-05s
INFO | --- Analysis for rkb_explorer_data took 3.02189040184021s
Availability | SPARQL endpoint availability check for The Rosetta Project took 4.315376281738281e-05s
Availability | VoID file availability check for The Rosetta Project took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for The Rosetta Project took 0.2755289077758789s
Reputation | Calculation of the PageRank for The Rosetta Project took 0.020438671112060547s
Interlinking | Calculation of Degree of Connection for The Rosetta Project took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Rosetta Project took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for The Rosetta Project took 3.075599670410156e-05s
Believability | Calculation of trust value for The Rosetta Project took 7.62939453125e-06s
INFO | --- Analysis for rosetta-project took 3.0137827396392822s
Availability | SPARQL endpoint availability check for Rpm Find took 5.14984130859375e-05s
Availability | VoID file availability check for Rpm Find took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Rpm Find took 0.25818562507629395s
Reputation | Calculation of the PageRank for Rpm Find took 0.02033066749572754s
Interlinking | Calculation of Degree of Connection for Rpm Find took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Rpm Find took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Rpm Find took 2.956390380859375e-05s
Believability | Calculation of trust value for Rpm Find took 1.33514404296875e-05s
INFO | --- Analysis for rpm_find took 3.057664155960083s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 4.3392181396484375e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.28450608253479004s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.02057504653930664s
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.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 6.914138793945312e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 7.62939453125e-06s
INFO | --- Analysis for rss-500-nif-ner-corpus took 3.6833276748657227s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 4.4345855712890625e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0007109642028808594s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.25690507888793945s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.020193099975585938s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 7.152557373046875e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 1.2636184692382812e-05s
INFO | --- Analysis for rubentaelman took 2.9456934928894043s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 4.2438507080078125e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.2957029342651367s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.0202333927154541s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.273124694824219e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 7.3909759521484375e-06s
INFO | --- Analysis for rubenverborgh took 3.337637424468994s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 393.2292971611023s
Availability | VoID file availability check for Russian Universities Specialities took 0.0008690357208251953s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.2736990451812744s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.020835399627685547s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 4.220008850097656e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 8.106231689453125e-06s
INFO | --- Analysis for russian-universities-specialities took 678.4446423053741s
Availability | SPARQL endpoint availability check for RuThes Cloud took 4.553794860839844e-05s
Availability | VoID file availability check for RuThes Cloud took 0.0002887248992919922s
Completeness | Calculation of interlinking completeness for RuThes Cloud took 0.6935873031616211s
Reputation | Calculation of the PageRank for RuThes Cloud took 0.0205838680267334s
Interlinking | Calculation of Degree of Connection for RuThes Cloud took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for RuThes Cloud took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for RuThes Cloud took 3.790855407714844e-05s
Believability | Calculation of trust value for RuThes Cloud took 8.106231689453125e-06s
INFO | --- Analysis for ruthes took 5.624376535415649s
Availability | SPARQL endpoint availability check for RxNorm took 4.2438507080078125e-05s
Availability | VoID file availability check for RxNorm took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for RxNorm took 0.7407090663909912s
Reputation | Calculation of the PageRank for RxNorm took 0.020467281341552734s
Interlinking | Calculation of Degree of Connection for RxNorm took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RxNorm took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for RxNorm took 3.528594970703125e-05s
Believability | Calculation of trust value for RxNorm took 8.344650268554688e-06s
INFO | --- Analysis for rxnorm took 4.748600959777832s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 2.0015997886657715s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.2740330696105957s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.020412921905517578s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 3.266334533691406e-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 5.984523296356201s
Availability | SPARQL endpoint availability check for SALDO took 4.315376281738281e-05s
Availability | VoID file availability check for SALDO took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for SALDO took 0.25286388397216797s
Reputation | Calculation of the PageRank for SALDO took 0.020291805267333984s
Interlinking | Calculation of Degree of Connection for SALDO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SALDO took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for SALDO took 3.147125244140625e-05s
Believability | Calculation of trust value for SALDO took 7.62939453125e-06s
INFO | --- Analysis for saldo took 3.0027129650115967s
Availability | SPARQL endpoint availability check for SALDO-RDF took 1.1199686527252197s
Availability | VoID file availability check for SALDO-RDF took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.26261353492736816s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.02017378807067871s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0008208751678466797s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.6716461181640625e-05s
Believability | Calculation of trust value for SALDO-RDF took 7.867813110351562e-06s
INFO | --- Analysis for saldo-rdf took 5.5676209926605225s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.6420609951019287s
Availability | VoID file availability check for SALDOM-RDF took 0.00031256675720214844s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.2592282295227051s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.020772457122802734s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0008223056793212891s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 4.482269287109375e-05s
Believability | Calculation of trust value for SALDOM-RDF took 7.867813110351562e-06s
INFO | --- Analysis for saldom-rdf took 4.910671710968018s
Availability | SPARQL endpoint availability check for sameAs.org took 4.1484832763671875e-05s
Availability | VoID file availability check for sameAs.org took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for sameAs.org took 0.25730109214782715s
Reputation | Calculation of the PageRank for sameAs.org took 0.020229339599609375s
Interlinking | Calculation of Degree of Connection for sameAs.org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for sameAs.org took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for sameAs.org took 3.0279159545898438e-05s
Believability | Calculation of trust value for sameAs.org took 9.059906005859375e-06s
INFO | --- Analysis for sameas-org took 2.8816699981689453s
Availability | SPARQL endpoint availability check for sandrart.net took 4.267692565917969e-05s
Availability | VoID file availability check for sandrart.net took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.24752283096313477s
Reputation | Calculation of the PageRank for sandrart.net took 0.02007126808166504s
Interlinking | Calculation of Degree of Connection for sandrart.net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.508827209472656e-05s
Believability | Calculation of trust value for sandrart.net took 6.4373016357421875e-06s
INFO | --- Analysis for sandrart-net took 3.590604782104492s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 1.6374058723449707s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0003478527069091797s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.274782657623291s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.020046234130859375s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 2.9325485229492188e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 8.58306884765625e-06s
INFO | --- Analysis for sanskrit-english-lexicon took 6.494250297546387s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 263.76877069473267s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0007576942443847656s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.9919703006744385s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.021015644073486328s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 4.5299530029296875e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for santillana_guide_dataset took 670.5052559375763s
Availability | SPARQL endpoint availability check for schema.org took 6.747245788574219e-05s
Availability | VoID file availability check for schema.org took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for schema.org took 0.2686755657196045s
Reputation | Calculation of the PageRank for schema.org took 0.020522356033325195s
Interlinking | Calculation of Degree of Connection for schema.org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for schema.org took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for schema.org took 3.528594970703125e-05s
Believability | Calculation of trust value for schema.org took 7.867813110351562e-06s
INFO | --- Analysis for schema-org took 5.2638161182403564s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 2.0845651626586914s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.7085764408111572s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.020099878311157227s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.2901763916015625e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 7.152557373046875e-06s
INFO | --- Analysis for schemapedia took 6.047755002975464s
Availability | SPARQL endpoint availability check for scholarlydata took 5.412101745605469e-05s
Availability | VoID file availability check for scholarlydata took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for scholarlydata took 0.29286813735961914s
Reputation | Calculation of the PageRank for scholarlydata took 0.020115375518798828s
Interlinking | Calculation of Degree of Connection for scholarlydata took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for scholarlydata took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for scholarlydata took 2.7894973754882812e-05s
Believability | Calculation of trust value for scholarlydata took 7.62939453125e-06s
INFO | --- Analysis for scholarlydata took 3.5034711360931396s
Availability | SPARQL endpoint availability check for Scholarometer took 4.315376281738281e-05s
Availability | VoID file availability check for Scholarometer took 0.0012929439544677734s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.2827920913696289s
Reputation | Calculation of the PageRank for Scholarometer took 0.020494461059570312s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0009348392486572266s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 0.00010061264038085938s
Believability | Calculation of trust value for Scholarometer took 7.152557373046875e-06s
INFO | --- Analysis for scholarometer took 7.146203517913818s
Availability | SPARQL endpoint availability check for Science Commons took 4.124641418457031e-05s
Availability | VoID file availability check for Science Commons took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Science Commons took 0.26505160331726074s
Reputation | Calculation of the PageRank for Science Commons took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for Science Commons took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Science Commons took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Science Commons took 2.8848648071289062e-05s
Believability | Calculation of trust value for Science Commons took 8.106231689453125e-06s
INFO | --- Analysis for science_commons took 3.0244224071502686s
Availability | SPARQL endpoint availability check for ScienceWise took 4.982948303222656e-05s
Availability | VoID file availability check for ScienceWise took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for ScienceWise took 0.2917516231536865s
Reputation | Calculation of the PageRank for ScienceWise took 0.020293712615966797s
Interlinking | Calculation of Degree of Connection for ScienceWise took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ScienceWise took 0.0009303092956542969s
Interlinking | Calculation of Clustering coefficient for ScienceWise took 3.600120544433594e-05s
Believability | Calculation of trust value for ScienceWise took 7.867813110351562e-06s
INFO | --- Analysis for sciencewise took 2.980952262878418s
Availability | SPARQL endpoint availability check for sears.com took 4.291534423828125e-05s
Availability | VoID file availability check for sears.com took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for sears.com took 0.2672746181488037s
Reputation | Calculation of the PageRank for sears.com took 0.0203399658203125s
Interlinking | Calculation of Degree of Connection for sears.com took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for sears.com took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for sears.com took 7.2479248046875e-05s
Believability | Calculation of trust value for sears.com took 7.3909759521484375e-06s
INFO | --- Analysis for sears took 4.5670812129974365s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.10353517532348633s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.2789573669433594s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.020641088485717773s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.702278137207031e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 4.76837158203125e-06s
INFO | --- Analysis for sec-rdfabout took 6.12173867225647s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.94407558441162s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0007283687591552734s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.39320802688598633s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.020341157913208008s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 9.894371032714844e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for secold took 168.4297502040863s
Availability | SPARQL endpoint availability check for SEEK-AT-WD ICT tools for education - Web-Share took 4.172325134277344e-05s
Availability | VoID file availability check for SEEK-AT-WD ICT tools for education - Web-Share took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for SEEK-AT-WD ICT tools for education - Web-Share took 0.2978549003601074s
Reputation | Calculation of the PageRank for SEEK-AT-WD ICT tools for education - Web-Share took 0.020314693450927734s
Interlinking | Calculation of Degree of Connection for SEEK-AT-WD ICT tools for education - Web-Share took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SEEK-AT-WD ICT tools for education - Web-Share took 0.0007269382476806641s
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 1.0728836059570312e-05s
INFO | --- Analysis for seek-at-wd-ict-tools-for-education-web-share took 4.093692064285278s
Availability | SPARQL endpoint availability check for semanlink took 4.220008850097656e-05s
Availability | VoID file availability check for semanlink took 0.0007739067077636719s
Completeness | Calculation of interlinking completeness for semanlink took 0.37471771240234375s
Reputation | Calculation of the PageRank for semanlink took 0.020345449447631836s
Interlinking | Calculation of Degree of Connection for semanlink took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.00016164779663085938s
Believability | Calculation of trust value for semanlink took 7.62939453125e-06s
INFO | --- Analysis for semanlink took 183.48361325263977s
Availability | SPARQL endpoint availability check for Semantic Library took 4.076957702636719e-05s
Availability | VoID file availability check for Semantic Library took 0.0003349781036376953s
Completeness | Calculation of interlinking completeness for Semantic Library took 0.28147101402282715s
Reputation | Calculation of the PageRank for Semantic Library took 0.02157449722290039s
Interlinking | Calculation of Degree of Connection for Semantic Library took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Semantic Library took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Semantic Library took 3.0279159545898438e-05s
Believability | Calculation of trust value for Semantic Library took 7.62939453125e-06s
INFO | --- Analysis for semantic-library took 3.4740123748779297s
Availability | SPARQL endpoint availability check for Semantic Profiling Network took 4.291534423828125e-05s
Availability | VoID file availability check for Semantic Profiling Network took 0.0002994537353515625s
Completeness | Calculation of interlinking completeness for Semantic Profiling Network took 0.2736785411834717s
Reputation | Calculation of the PageRank for Semantic Profiling Network took 0.020228862762451172s
Interlinking | Calculation of Degree of Connection for Semantic Profiling Network took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Semantic Profiling Network took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Semantic Profiling Network took 2.86102294921875e-05s
Believability | Calculation of trust value for Semantic Profiling Network took 8.106231689453125e-06s
INFO | --- Analysis for semantic-profiling-network took 2.918456554412842s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.0706181526184082s
Availability | VoID file availability check for Semantic Universe Data took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.2624940872192383s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.02028512954711914s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 2.9802322387695312e-05s
Believability | Calculation of trust value for Semantic Universe Data took 1.3589859008789062e-05s
INFO | --- Analysis for semantic-universe took 2.539285659790039s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.195274829864502s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0009059906005859375s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.2636115550994873s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.02069687843322754s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00012040138244628906s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 1.6927719116210938e-05s
INFO | --- Analysis for semantic-web-dog-food took 82.95123362541199s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 4.315376281738281e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.27895641326904297s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.020261049270629883s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 6.365776062011719e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 8.106231689453125e-06s
INFO | --- Analysis for semantic-web-grundlagen took 3.5337860584259033s
Availability | SPARQL endpoint availability check for semantic-web-journal took 4.1484832763671875e-05s
Availability | VoID file availability check for semantic-web-journal took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for semantic-web-journal took 0.28015828132629395s
Reputation | Calculation of the PageRank for semantic-web-journal took 0.02022242546081543s
Interlinking | Calculation of Degree of Connection for semantic-web-journal took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for semantic-web-journal took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for semantic-web-journal took 3.0040740966796875e-05s
Believability | Calculation of trust value for semantic-web-journal took 8.106231689453125e-06s
INFO | --- Analysis for semantic-web-journal took 2.9749491214752197s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 4.1961669921875e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.2857856750488281s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.020168304443359375s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 8.225440979003906e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 5.0067901611328125e-06s
INFO | --- Analysis for semantic-xbrl took 3.3780288696289062s
Availability | SPARQL endpoint availability check for Semantic Bible took 4.1484832763671875e-05s
Availability | VoID file availability check for Semantic Bible took 0.000324249267578125s
Completeness | Calculation of interlinking completeness for Semantic Bible took 0.281261682510376s
Reputation | Calculation of the PageRank for Semantic Bible took 0.020251750946044922s
Interlinking | Calculation of Degree of Connection for Semantic Bible took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Semantic Bible took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Semantic Bible took 3.0517578125e-05s
Believability | Calculation of trust value for Semantic Bible took 7.867813110351562e-06s
INFO | --- Analysis for semantic_bible took 3.4166765213012695s
Availability | SPARQL endpoint availability check for SemanticQuran took 5.217737197875977s
Availability | VoID file availability check for SemanticQuran took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for SemanticQuran took 0.26381397247314453s
Reputation | Calculation of the PageRank for SemanticQuran took 0.020228147506713867s
Interlinking | Calculation of Degree of Connection for SemanticQuran took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SemanticQuran took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for SemanticQuran took 7.152557373046875e-05s
Believability | Calculation of trust value for SemanticQuran took 6.9141387939453125e-06s
INFO | --- Analysis for semanticquran took 14.90675401687622s
Availability | SPARQL endpoint availability check for SemanticTweet took 4.291534423828125e-05s
Availability | VoID file availability check for SemanticTweet took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.26994872093200684s
Reputation | Calculation of the PageRank for SemanticTweet took 0.02025294303894043s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 6.937980651855469e-05s
Believability | Calculation of trust value for SemanticTweet took 6.9141387939453125e-06s
INFO | --- Analysis for semantictweet took 3.20459246635437s
Availability | SPARQL endpoint availability check for semanticweb.org took 4.410743713378906e-05s
Availability | VoID file availability check for semanticweb.org took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.24454760551452637s
Reputation | Calculation of the PageRank for semanticweb.org took 0.020313262939453125s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 8.082389831542969e-05s
Believability | Calculation of trust value for semanticweb.org took 6.9141387939453125e-06s
INFO | --- Analysis for semanticweb-org took 27.86719012260437s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.06927013397216797s
Availability | VoID file availability check for Semantic CrunchBase took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.2895166873931885s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.020793914794921875s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 6.961822509765625e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 7.62939453125e-06s
INFO | --- Analysis for semsol-crunchbase took 2.5572450160980225s
Availability | SPARQL endpoint availability check for Sensores de IntelliDomo took 5.269050598144531e-05s
Availability | VoID file availability check for Sensores de IntelliDomo took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Sensores de IntelliDomo took 0.2708170413970947s
Reputation | Calculation of the PageRank for Sensores de IntelliDomo took 0.020749330520629883s
Interlinking | Calculation of Degree of Connection for Sensores de IntelliDomo took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Sensores de IntelliDomo took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Sensores de IntelliDomo took 3.7670135498046875e-05s
Believability | Calculation of trust value for Sensores de IntelliDomo took 9.298324584960938e-06s
INFO | --- Analysis for sensores-de-intellidomo took 2.9875218868255615s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.24868559837341309s
Availability | VoID file availability check for SentimentWortschatz took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.2640261650085449s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.020596981048583984s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.57763671875e-05s
Believability | Calculation of trust value for SentimentWortschatz took 7.3909759521484375e-06s
INFO | --- Analysis for sentiws took 3.595517158508301s
Availability | SPARQL endpoint availability check for Serendipity took 8.07613468170166s
Availability | VoID file availability check for Serendipity took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Serendipity took 0.2820131778717041s
Reputation | Calculation of the PageRank for Serendipity took 0.020380020141601562s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Serendipity took 7.390975952148438e-05s
Believability | Calculation of trust value for Serendipity took 6.9141387939453125e-06s
INFO | --- Analysis for serendipity took 15.830541133880615s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.31265759468078613s
Availability | VoID file availability check for Shoah victims? names took 0.7419416904449463s
Extra | Recovery of all triples for Shoah victims? names took 1.3780875205993652s
Performance | Total latancy measurement for Shoah victims? names took 0.7570784091949463s
Amount of data | Number of triples check for Shoah victims? names took 1.5267894268035889s
Interoperability | New terms check for Shoah victims? names took 1.7611174583435059s
Versatility | Languages check for Shoah victims? names took 19.381816625595093s
Interpretability | Number of blank nodes check for Shoah victims? names took 2.15841007232666s
Security | Check HTTPS for Shoah victims? names took 0.5401997566223145s
Interpretability | RDF structures check for Shoah victims? names took 0.34355711936950684s
Versatility | Serialization formats check for Shoah victims? names took 0.5535814762115479s
Availability | RDF dump link check for Shoah victims? names took 0.28882884979248047s
License | MR license check for Shoah victims? names took 0.430553674697876s
License | HR license check for Shoah victims? names took 8.9570791721344s
Amount of data | Number of property check for Shoah victims? names took 0.1814277172088623s
Understandability | Number of label check for Shoah victims? names took 1.574345350265503s
Understandability | URI regex check for Shoah victims? names took 0.6946191787719727s
Understandability | Vocabs check for Shoah victims? names took 0.19965720176696777s
Verifiability | Authors check for Shoah victims? names took 0.2629215717315674s
Verifiability | Publishers check for Shoah victims? names took 0.23952007293701172s
Performance | Throughput check for Shoah victims? names took 10.641421556472778s
Amount of data | Check the number of entities for Shoah victims? names took 0.0001125335693359375s
Verifiability | Contribs. check for Shoah victims? names took 0.09077072143554688s
Interlinking | sameAs chians check for Shoah victims? names took 0.16276192665100098s
Interlinking | skos check for Shoah victims? names took 0.2856252193450928s
Interlinking | skos check for Shoah victims? names took 0.0736091136932373s
Timeliness | dataset update frequency check for Shoah victims? names took 0.3089323043823242s
Currency | Creation date check for Shoah victims? names took 0.45986104011535645s
Currency | Modification date check for Shoah victims? names took 0.2375044822692871s
Rep.Conc. | URIs length for Shoah victims? names took 3.06367826461792s
Interoperability | New vocabularies check for Shoah victims? names took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.09332585334777832s
Accuracy | Check Functional Property for Shoah victims? names took 0.18681788444519043s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.09853076934814453s
Accuracy | Check Empty annotation labels for Shoah victims? names took 1.0065407752990723s
Accuracy | Check White space in annotation for Shoah victims? names took 0.029369115829467773s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.028318405151367188s
Consistency | Disjoint class check for Shoah victims? names took 0.2837700843811035s
Consistency | Check Misplaced properties for Shoah victims? names took 2.3781449794769287s
Consistency | Misplaced classes for Shoah victims? names took 0.28159332275390625s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.748378038406372s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.300285816192627s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.2347567081451416s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.03006434440612793s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.19973087310791016s
Security | Sign check for Shoah victims? names took 0.5277166366577148s
Availability | Check URIs Dereferenciability for Shoah victims? names took 1218.8939242362976s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.40088558197021484s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.0204775333404541s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 5.555152893066406e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 1.430511474609375e-06s
Believability | Calculation of trust value for Shoah victims? names took 7.3909759521484375e-06s
INFO | --- Analysis for shoah-victims-names took 1342.3459014892578s
Availability | SPARQL endpoint availability check for SIMILE Data Collection took 4.673004150390625e-05s
Availability | VoID file availability check for SIMILE Data Collection took 0.00034880638122558594s
Completeness | Calculation of interlinking completeness for SIMILE Data Collection took 0.7617950439453125s
Reputation | Calculation of the PageRank for SIMILE Data Collection took 0.020692825317382812s
Interlinking | Calculation of Degree of Connection for SIMILE Data Collection took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SIMILE Data Collection took 0.0009245872497558594s
Interlinking | Calculation of Clustering coefficient for SIMILE Data Collection took 3.528594970703125e-05s
Believability | Calculation of trust value for SIMILE Data Collection took 9.059906005859375e-06s
INFO | --- Analysis for simile_data_collection took 4.421560287475586s
Availability | SPARQL endpoint availability check for SIMPLE took 4.291534423828125e-05s
Availability | VoID file availability check for SIMPLE took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.2581148147583008s
Reputation | Calculation of the PageRank for SIMPLE took 0.02024078369140625s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 3.8623809814453125e-05s
Believability | Calculation of trust value for SIMPLE took 7.152557373046875e-06s
INFO | --- Analysis for simple took 8.188472986221313s
Availability | SPARQL endpoint availability check for SITC-V4 took 25.281396865844727s
Availability | VoID file availability check for SITC-V4 took 0.0008027553558349609s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.39228034019470215s
Reputation | Calculation of the PageRank for SITC-V4 took 0.02059650421142578s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 3.3855438232421875e-05s
Believability | Calculation of trust value for SITC-V4 took 5.0067901611328125e-06s
INFO | --- Analysis for sitc-v4 took 125.87331557273865s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.267692565917969e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.2628133296966553s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.020224809646606445s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 2.956390380859375e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 8.106231689453125e-06s
INFO | --- Analysis for slideshare2rdf took 3.8962042331695557s
Availability | SPARQL endpoint availability check for Slidewiki (RDF/SPARQL) took 4.124641418457031e-05s
Availability | VoID file availability check for Slidewiki (RDF/SPARQL) took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Slidewiki (RDF/SPARQL) took 0.2655296325683594s
Reputation | Calculation of the PageRank for Slidewiki (RDF/SPARQL) took 0.02018451690673828s
Interlinking | Calculation of Degree of Connection for Slidewiki (RDF/SPARQL) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Slidewiki (RDF/SPARQL) took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Slidewiki (RDF/SPARQL) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Slidewiki (RDF/SPARQL) took 7.62939453125e-06s
INFO | --- Analysis for slidewiki-rdf-sparql took 3.5071632862091064s
Availability | SPARQL endpoint availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 4.267692565917969e-05s
Availability | VoID file availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.7400803565979004s
Reputation | Calculation of the PageRank for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.020328521728515625s
Interlinking | Calculation of Degree of Connection for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 3.0040740966796875e-05s
Believability | Calculation of trust value for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 7.3909759521484375e-06s
INFO | --- Analysis for slovn-k-cpv-2008---common-procurement-vocabulary-2008 took 3.4273483753204346s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 5.110792875289917s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.2880406379699707s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.02035832405090332s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.2901763916015625e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 7.3909759521484375e-06s
INFO | --- Analysis for smartlink took 13.363704204559326s
Availability | SPARQL endpoint availability check for Social Networks and Archival Context Fall 2011 took 4.0531158447265625e-05s
Availability | VoID file availability check for Social Networks and Archival Context Fall 2011 took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for Social Networks and Archival Context Fall 2011 took 0.23882508277893066s
Reputation | Calculation of the PageRank for Social Networks and Archival Context Fall 2011 took 0.020465850830078125s
Interlinking | Calculation of Degree of Connection for Social Networks and Archival Context Fall 2011 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Social Networks and Archival Context Fall 2011 took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Social Networks and Archival Context Fall 2011 took 2.8848648071289062e-05s
Believability | Calculation of trust value for Social Networks and Archival Context Fall 2011 took 8.106231689453125e-06s
INFO | --- Analysis for social-networks-and-archival-context-fall-2011 took 3.482109785079956s
Availability | SPARQL endpoint availability check for SocialLink took 4.1961669921875e-05s
Availability | VoID file availability check for SocialLink took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for SocialLink took 0.270674467086792s
Reputation | Calculation of the PageRank for SocialLink took 0.020324230194091797s
Interlinking | Calculation of Degree of Connection for SocialLink took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SocialLink took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for SocialLink took 2.8133392333984375e-05s
Believability | Calculation of trust value for SocialLink took 7.867813110351562e-06s
INFO | --- Analysis for sociallink took 3.0443332195281982s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.3175942897796631s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0006425380706787109s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 15.74745774269104s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.5173141956329346s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.23155522346496582s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.5427517890930176s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.4100356101989746s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.18287181854248047s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.33029985427856445s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.10633158683776855s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.13179254531860352s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.7495534420013428s
License | MR license check for Social Semantic Web Thesaurus took 0.12140774726867676s
License | HR license check for Social Semantic Web Thesaurus took 0.10605239868164062s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.1188960075378418s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.1308279037475586s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.1947019100189209s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.12799596786499023s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.11765336990356445s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.11707067489624023s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.468706130981445s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 7.510185241699219e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.11010885238647461s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.12482881546020508s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.11965441703796387s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.10198593139648438s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.0878291130065918s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.20026588439941406s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.20079946517944336s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 1.5050077438354492s
Interoperability | New vocabularies check for Social Semantic Web Thesaurus took 1.23909592628479s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.10998725891113281s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.10091876983642578s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.07873773574829102s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.4471447467803955s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.012740135192871094s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.08699154853820801s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.2747015953063965s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.08880972862243652s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.1333086490631104s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.510350227355957s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.00014543533325195312s
Security | Sign check for Social Semantic Web Thesaurus took 0.09920859336853027s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 115.72042155265808s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.868826150894165s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.020323991775512695s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 9.894371032714844e-05s
Interoperability | Check the re-using of existing vocabs for Social Semantic Web Thesaurus took 0.863257646560669s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 1.1682510375976562e-05s
INFO | --- Analysis for socialsemweb-thesaurus took 229.0252103805542s
Availability | SPARQL endpoint availability check for SORS took 5.793571472167969e-05s
Availability | VoID file availability check for SORS took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for SORS took 0.2970468997955322s
Reputation | Calculation of the PageRank for SORS took 0.020609378814697266s
Interlinking | Calculation of Degree of Connection for SORS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SORS took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for SORS took 5.054473876953125e-05s
Believability | Calculation of trust value for SORS took 5.7220458984375e-06s
INFO | --- Analysis for sors took 12.711535453796387s
Availability | SPARQL endpoint availability check for Soudy České republiky took 4.363059997558594e-05s
Availability | VoID file availability check for Soudy České republiky took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for Soudy České republiky took 0.29012346267700195s
Reputation | Calculation of the PageRank for Soudy České republiky took 0.03267669677734375s
Interlinking | Calculation of Degree of Connection for Soudy České republiky took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Soudy České republiky took 0.0014085769653320312s
Interlinking | Calculation of Clustering coefficient for Soudy České republiky took 4.38690185546875e-05s
Believability | Calculation of trust value for Soudy České republiky took 9.5367431640625e-06s
INFO | --- Analysis for soudy--esk--republiky took 3.101466178894043s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 6.818771362304688e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.24450445175170898s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.020476579666137695s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 9.34600830078125e-05s
Believability | Calculation of trust value for southampton-ac-uk took 6.9141387939453125e-06s
INFO | --- Analysis for southampton-ac-uk took 4.035526275634766s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 3.203322410583496s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0007550716400146484s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.30463218688964844s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.020879268646240234s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 7.62939453125e-06s
INFO | --- Analysis for southampton-ac-uk-apps took 10.521377325057983s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 5.5789947509765625e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0006830692291259766s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.28681063652038574s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.020263671875s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.751319885253906e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 1.33514404296875e-05s
INFO | --- Analysis for southampton-ecs-eprints took 4.4011852741241455s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.6020641326904297s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.0002636909484863281s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 162.8228588104248s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.278458595275879s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 2.2120561599731445s
Interoperability | New terms check for Spanish Linguistic Datasets took 3.111607313156128s
Versatility | Languages check for Spanish Linguistic Datasets took 44.620534896850586s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 1.1619584560394287s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.1252896785736084s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.2705528736114502s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.27899789810180664s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.27573704719543457s
License | MR license check for Spanish Linguistic Datasets took 0.26006102561950684s
License | HR license check for Spanish Linguistic Datasets took 0.3630824089050293s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.2840242385864258s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.3440098762512207s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.549795389175415s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.2989506721496582s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.2833256721496582s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.28098201751708984s
Performance | Throughput check for Spanish Linguistic Datasets took 11.24335765838623s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 7.414817810058594e-05s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.27537107467651367s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.30254578590393066s
Interlinking | skos check for Spanish Linguistic Datasets took 0.2828841209411621s
Interlinking | skos check for Spanish Linguistic Datasets took 0.22780799865722656s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.30248570442199707s
Currency | Creation date check for Spanish Linguistic Datasets took 0.5818562507629395s
Currency | Modification date check for Spanish Linguistic Datasets took 0.5958428382873535s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 58.438236236572266s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.2877535820007324s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.29982495307922363s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 0.32654476165771484s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 0.8864593505859375s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.010064125061035156s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.645993232727051s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.28759026527404785s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.6811511516571045s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.429834365844727s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 44.699761629104614s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.4463930130004883s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 5.70949387550354s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 2.8819007873535156s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.29079151153564453s
Security | Sign check for Spanish Linguistic Datasets took 0.29450511932373047s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 10.680416107177734s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 1.1772348880767822s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.021182537078857422s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007958412170410156s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.457069396972656e-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.62939453125e-06s
INFO | --- Analysis for spanish-linguistic-datasets took 414.2874116897583s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.05980658531188965s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.30647921562194824s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.020647764205932617s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 6.67572021484375e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 8.58306884765625e-06s
INFO | --- Analysis for sparql-endpoint-status took 3.414433717727661s
Availability | SPARQL endpoint availability check for SPC publikovaná SÚKL took 4.3392181396484375e-05s
Availability | VoID file availability check for SPC publikovaná SÚKL took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for SPC publikovaná SÚKL took 0.26749539375305176s
Reputation | Calculation of the PageRank for SPC publikovaná SÚKL took 0.020697355270385742s
Interlinking | Calculation of Degree of Connection for SPC publikovaná SÚKL took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for SPC publikovaná SÚKL took 0.0008709430694580078s
Interlinking | Calculation of Clustering coefficient for SPC publikovaná SÚKL took 3.4332275390625e-05s
Believability | Calculation of trust value for SPC publikovaná SÚKL took 9.298324584960938e-06s
INFO | --- Analysis for spc-publikovan--s-kl took 4.238282680511475s
Availability | SPARQL endpoint availability check for SPQR took 4.100799560546875e-05s
Availability | VoID file availability check for SPQR took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for SPQR took 0.2639644145965576s
Reputation | Calculation of the PageRank for SPQR took 0.020355939865112305s
Interlinking | Calculation of Degree of Connection for SPQR took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SPQR took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for SPQR took 3.0279159545898438e-05s
Believability | Calculation of trust value for SPQR took 1.8358230590820312e-05s
INFO | --- Analysis for spqr took 3.018942356109619s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.172325134277344e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.2863743305206299s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.020384550094604492s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 8.58306884765625e-06s
INFO | --- Analysis for srcmf took 2.591198205947876s
Availability | SPARQL endpoint availability check for SSF took 5.626678466796875e-05s
Availability | VoID file availability check for SSF took 0.0008397102355957031s
Completeness | Calculation of interlinking completeness for SSF took 0.2697713375091553s
Reputation | Calculation of the PageRank for SSF took 0.02039813995361328s
Interlinking | Calculation of Degree of Connection for SSF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SSF took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for SSF took 2.956390380859375e-05s
Believability | Calculation of trust value for SSF took 1.1682510375976562e-05s
INFO | --- Analysis for ssf-lexicon took 3.52046275138855s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 4.458427429199219e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.268765926361084s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.020257234573364258s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.504753112792969e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 8.106231689453125e-06s
INFO | --- Analysis for st-andrews-resource-lists took 2.7846457958221436s
Availability | SPARQL endpoint availability check for STAC took 4.220008850097656e-05s
Availability | VoID file availability check for STAC took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for STAC took 0.24120879173278809s
Reputation | Calculation of the PageRank for STAC took 0.02129960060119629s
Interlinking | Calculation of Degree of Connection for STAC took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for STAC took 0.0009980201721191406s
Interlinking | Calculation of Clustering coefficient for STAC took 3.5762786865234375e-05s
Believability | Calculation of trust value for STAC took 7.62939453125e-06s
INFO | --- Analysis for stac took 3.0032010078430176s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for The Scottish Government took 4.38690185546875e-05s
Availability | VoID file availability check for Organogram and staff pay data for The Scottish Government took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for The Scottish Government took 0.2955639362335205s
Reputation | Calculation of the PageRank for Organogram and staff pay data for The Scottish Government took 0.020639419555664062s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for The Scottish Government took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for The Scottish Government took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for The Scottish Government took 3.0040740966796875e-05s
Believability | Calculation of trust value for Organogram and staff pay data for The Scottish Government took 7.867813110351562e-06s
INFO | --- Analysis for staff-organograms-and-pay-scottish-government took 2.9654295444488525s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.3392181396484375e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0003769397735595703s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.2688298225402832s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.020464658737182617s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007266998291015625s
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.7220458984375e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 4.2385313510894775s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.1734185218811035s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.29692506790161133s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.020281553268432617s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00012254714965820312s
Believability | Calculation of trust value for statistics.data.gov.uk took 3.2901763916015625e-05s
INFO | --- Analysis for statistics-data-gov-uk took 3.9730632305145264s
Availability | SPARQL endpoint availability check for Statistics on Fatal Traffic Accidents in greek roads took 4.076957702636719e-05s
Availability | VoID file availability check for Statistics on Fatal Traffic Accidents in greek roads took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Statistics on Fatal Traffic Accidents in greek roads took 0.27973341941833496s
Reputation | Calculation of the PageRank for Statistics on Fatal Traffic Accidents in greek roads took 0.02065896987915039s
Interlinking | Calculation of Degree of Connection for Statistics on Fatal Traffic Accidents in greek roads took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Statistics on Fatal Traffic Accidents in greek roads took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Statistics on Fatal Traffic Accidents in greek roads took 3.3855438232421875e-05s
Believability | Calculation of trust value for Statistics on Fatal Traffic Accidents in greek roads took 9.298324584960938e-06s
INFO | --- Analysis for statistics-on-fatal-traffic-accidents-in-greek-roads took 3.0431771278381348s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.27283334732055664s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.020438194274902344s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.0001068115234375s
Believability | Calculation of trust value for statusnet-1w6-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-1w6-org took 2.985224723815918s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 4.839897155761719e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.2572939395904541s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.02067708969116211s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.651878356933594e-05s
Believability | Calculation of trust value for statusnet-20100-org took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-20100-org took 2.477471351623535s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 0.00010395050048828125s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.2652099132537842s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.020457744598388672s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 7.390975952148438e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-alexandrefranke-com took 2.834474563598633s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0006315708160400391s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.284698486328125s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.021592378616333008s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0009694099426269531s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 9.751319885253906e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.576291561126709s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.2611067295074463s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.020311355590820312s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 8.678436279296875e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-belfalas-org took 2.5359904766082764s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 4.9591064453125e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0007309913635253906s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.2905092239379883s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.020126819610595703s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00010371208190917969s
Believability | Calculation of trust value for statusnet-bka-li took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-bka-li took 2.8590950965881348s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0007178783416748047s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.2771327495574951s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.02535104751586914s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0021827220916748047s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 6.222724914550781e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.3667654991149902s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0007469654083251953s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.27074503898620605s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.020752429962158203s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 4.887580871582031e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 1.52587890625e-05s
INFO | --- Analysis for statusnet-ced117-net took 3.882594347000122s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0010640621185302734s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.2520885467529297s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.020442962646484375s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 5.054473876953125e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.691321849822998s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.2792625427246094s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.020288705825805664s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00011181831359863281s
Believability | Calculation of trust value for statusnet-chromic-org took 1.5020370483398438e-05s
INFO | --- Analysis for statusnet-chromic-org took 2.622936725616455s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 5.3882598876953125e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.2920088768005371s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.020467519760131836s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 8.0108642578125e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-cooleysekula-net took 6.138505697250366s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.2776930332183838s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.020259380340576172s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.459785461425781e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-coreyavis-com took 2.5894229412078857s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.309370756149292s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.02016901969909668s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 6.747245788574219e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.299081325531006s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 5.91278076171875e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.25333285331726074s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.020300626754760742s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00010323524475097656s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.627784013748169s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.00048828125s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.25321149826049805s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.02037811279296875s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0008223056793212891s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.508827209472656e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.4698996543884277s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.2548866271972656s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.02021193504333496s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 4.9591064453125e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-doomicile-de took 3.340128183364868s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.26433372497558594s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.02057790756225586s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0008137226104736328s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 6.365776062011719e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-dtdns-net took 2.600800037384033s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.26396942138671875s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.02021002769470215s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.504753112792969e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-equestriarp-net took 2.4729342460632324s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0006935596466064453s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.26914405822753906s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.020824193954467773s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.462501525878906e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-exdc-net took 12.542749404907227s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0007071495056152344s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.26541614532470703s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.02025580406188965s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.131431579589844e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-fcac-com took 22.426406383514404s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0005919933319091797s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.2798123359680176s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.02055191993713379s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.364418029785156e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-fcestrada-com took 3.133888006210327s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.30346012115478516s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.020333051681518555s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.0002071857452392578s
Believability | Calculation of trust value for statusnet-fragdev-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-fragdev-com took 3.4555070400238037s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.25304698944091797s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.020325899124145508s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.462501525878906e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 9.5367431640625e-06s
INFO | --- Analysis for statusnet-freelish-us took 2.570929765701294s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.27919626235961914s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.020671606063842773s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00010800361633300781s
Believability | Calculation of trust value for statusnet-gegeweb-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-gegeweb-org took 2.547576665878296s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 8.678436279296875e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.2799248695373535s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.02051687240600586s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 6.890296936035156e-05s
Believability | Calculation of trust value for statusnet-glou-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-glou-org took 2.6509664058685303s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.2671377658843994s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.02074599266052246s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.0001285076141357422s
Believability | Calculation of trust value for statusnet-gomertronic-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-gomertronic-com took 2.481414556503296s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0005898475646972656s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.2546727657318115s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.02026963233947754s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.0001068115234375s
Believability | Calculation of trust value for statusnet-hackerposse-com took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-hackerposse-com took 2.9279911518096924s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.27756285667419434s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.020251989364624023s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 4.506111145019531e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-hii-co-il took 3.403630256652832s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.25208115577697754s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.02052617073059082s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 9.489059448242188e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 3.4830570220947266s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.2676112651824951s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.02040696144104004s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 6.008148193359375e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 7.62939453125e-06s
INFO | --- Analysis for statusnet-imirhil-fr took 2.6575772762298584s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 5.125999450683594e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.27704286575317383s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.02045583724975586s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 3.886222839355469e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-integralblue-com took 2.675231456756592s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.28087902069091797s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.02029561996459961s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 5.316734313964844e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.445807456970215s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.2512505054473877s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.02051520347595215s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00011491775512695312s
Believability | Calculation of trust value for statusnet-jonkman-ca took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-jonkman-ca took 3.6571872234344482s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.29850268363952637s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.02028059959411621s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.369850158691406e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-kaimi-cc took 2.590782403945923s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0009303092956542969s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.2718362808227539s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.02038884162902832s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 4.8160552978515625e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-kathryl-fr took 2.384653329849243s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.2847766876220703s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.020163774490356445s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 3.838539123535156e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-kenzoid-com took 3.316441059112549s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.27733516693115234s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.020485401153564453s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 7.033348083496094e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-keuser-fr took 2.4934864044189453s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.27112269401550293s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.020302772521972656s
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.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 5.030632019042969e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.5555403232574463s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.256227970123291s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 6.222724914550781e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-lebsanft-org took 2.659261703491211s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.26480817794799805s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.02072286605834961s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0008494853973388672s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 0.00010442733764648438s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.731896162033081s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 0.0001068115234375s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.25141191482543945s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.020259618759155273s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011491775512695312s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.505452871322632s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 5.412101745605469e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.001373291015625s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.3153104782104492s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.02037334442138672s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.698204040527344e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-ludost-net took 4.666792631149292s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.2802460193634033s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.020426034927368164s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 9.989738464355469e-05s
Believability | Calculation of trust value for statusnet-lydiastench-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-lydiastench-com took 2.4839136600494385s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 9.5367431640625e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.2551121711730957s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.020447492599487305s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.4836273193359375e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 1.71661376953125e-05s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.4651365280151367s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.29308485984802246s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.020828723907470703s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.000152587890625s
Believability | Calculation of trust value for statusnet-macno-org took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-macno-org took 2.5395262241363525s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.28023576736450195s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.021014928817749023s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.580352783203125e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.4792518615722656s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0007112026214599609s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.2733304500579834s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.020453453063964844s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 7.724761962890625e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-maymay-net took 42.12503695487976s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.2660539150238037s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.020268917083740234s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.00016021728515625s
Believability | Calculation of trust value for statusnet-morphtown-de took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-morphtown-de took 2.5398519039154053s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.26939821243286133s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.020310163497924805s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 0.0001010894775390625s
Believability | Calculation of trust value for statusnet-mrblog-nl took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-mrblog-nl took 2.566567897796631s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.26712918281555176s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.020147085189819336s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.269050598144531e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-mulestable-net took 2.5814192295074463s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 0.00010442733764648438s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.2797694206237793s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.02029705047607422s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 4.9114227294921875e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 7.62939453125e-06s
INFO | --- Analysis for statusnet-my-status-tk took 2.620274782180786s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.2436683177947998s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.020060300827026367s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00010275840759277344s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.5185530185699463s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.27637290954589844s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.020323753356933594s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 5.602836608886719e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.70088791847229s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 5.14984130859375e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.29538679122924805s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.02043604850769043s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.198883056640625e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-otbm-fr took 2.6628777980804443s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.2921781539916992s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.020624399185180664s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.225440979003906e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 3.0990049839019775s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.2724316120147705s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.020407676696777344s
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.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 4.57763671875e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-panda-id-au took 3.5026566982269287s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.28681445121765137s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.020305395126342773s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.512901306152344e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 7.62939453125e-06s
INFO | --- Analysis for statusnet-piana-eu took 2.724238634109497s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.3028378486633301s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.020407676696777344s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.486343383789062e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-planet-libre-org took 2.665358304977417s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.2664189338684082s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.020308256149291992s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.00023031234741210938s
Believability | Calculation of trust value for statusnet-postblue-info took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-postblue-info took 2.9980390071868896s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 4.9114227294921875e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.2977786064147949s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.020373821258544922s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 6.818771362304688e-05s
Believability | Calculation of trust value for statusnet-progval-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-progval-net took 2.619596481323242s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.2928287982940674s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.02033066749572754s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00011229515075683594s
Believability | Calculation of trust value for statusnet-qdnx-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-qdnx-org took 2.9617269039154053s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.2681915760040283s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.020321369171142578s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.151199340820312e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-qth-fr took 3.2552247047424316s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 5.817413330078125e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.265484094619751s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.020673036575317383s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.0002155303955078125s
Believability | Calculation of trust value for statusnet-quitter-se took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-quitter-se took 2.972809076309204s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.27821969985961914s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.020397186279296875s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00010538101196289062s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.585036277770996s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 6.508827209472656e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0006415843963623047s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.29212522506713867s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.020454883575439453s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 6.794929504394531e-05s
Believability | Calculation of trust value for statusnet-recit-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-recit-org took 4.5716869831085205s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.27069830894470215s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.02032923698425293s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.0001468658447265625s
Believability | Calculation of trust value for statusnet-russwurm-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-russwurm-org took 3.3935208320617676s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0006933212280273438s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.28452634811401367s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.020215749740600586s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.058547973632812e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-samnoble-org took 4.92203164100647s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.2769203186035156s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.020358562469482422s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.0108642578125e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-schiessle-org took 2.662461280822754s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.29909825325012207s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.020186662673950195s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 9.775161743164062e-05s
Believability | Calculation of trust value for statusnet-scoffoni-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-scoffoni-net took 2.5468456745147705s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 5.650520324707031e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.26035475730895996s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.020305633544921875s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.127357482910156e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-sebseb01-net took 2.534594774246216s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.27369117736816406s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.02046990394592285s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.271766662597656e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-shnoulle-net took 3.4215359687805176s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.30057334899902344s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.020039796829223633s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.0002090930938720703s
Believability | Calculation of trust value for statusnet-skilledtests-com took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-skilledtests-com took 3.0556838512420654s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.268618106842041s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.02015089988708496s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.0001068115234375s
Believability | Calculation of trust value for statusnet-somsants-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-somsants-net took 2.4695944786071777s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.27734971046447754s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.02034759521484375s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.00013446807861328125s
Believability | Calculation of trust value for statusnet-soucy-cc took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-soucy-cc took 2.5755538940429688s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.2793102264404297s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.02030324935913086s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 5.91278076171875e-05s
Believability | Calculation of trust value for statusnet-spip-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-spip-org took 3.4910335540771484s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.29091906547546387s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.02018451690673828s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.461143493652344e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-spraci-org took 2.4679453372955322s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0006730556488037109s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.2722959518432617s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.020373106002807617s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00010991096496582031s
Believability | Calculation of trust value for statusnet-ssweeny-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-ssweeny-net took 5.556495428085327s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.2771902084350586s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.020240068435668945s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00022363662719726562s
Believability | Calculation of trust value for statusnet-status-net took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-status-net took 3.584571123123169s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.28266286849975586s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.02022242546081543s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.793571472167969e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.473466157913208s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0015299320220947266s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.29514527320861816s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.020189523696899414s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 9.059906005859375e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.965700626373291s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 0.00011014938354492188s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.2695431709289551s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.020252466201782227s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.00012373924255371094s
Believability | Calculation of trust value for statusnet-thelovebug-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-thelovebug-org took 2.450188636779785s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.25609350204467773s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.020348787307739258s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 8.082389831542969e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-thornton2-com took 4.995349645614624s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.27627062797546387s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.020301342010498047s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00010752677917480469s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.8594090938568115s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 5.316734313964844e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.000518798828125s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.2767174243927002s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.020758628845214844s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 4.5299530029296875e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-tl1n-com took 3.5638957023620605s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 4.696846008300781e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.2375473976135254s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.0202639102935791s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.508827209472656e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.7196130752563477s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.00063323974609375s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.26940226554870605s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.02067708969116211s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 1.52587890625e-05s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 3.8623809814453125e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-uni-siegen-de took 2.606203556060791s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 4.38690185546875e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0006234645843505859s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.2655355930328369s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.020425796508789062s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 2.8133392333984375e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for steak took 3.676398277282715s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 4.363059997558594e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.28677821159362793s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.020339250564575195s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007252693176269531s
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 4.171155214309692s
Availability | SPARQL endpoint availability check for Strukturované popisy z FDA took 4.363059997558594e-05s
Availability | VoID file availability check for Strukturované popisy z FDA took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for Strukturované popisy z FDA took 0.2535881996154785s
Reputation | Calculation of the PageRank for Strukturované popisy z FDA took 0.021126985549926758s
Interlinking | Calculation of Degree of Connection for Strukturované popisy z FDA took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Strukturované popisy z FDA took 0.0008769035339355469s
Interlinking | Calculation of Clustering coefficient for Strukturované popisy z FDA took 3.5762786865234375e-05s
Believability | Calculation of trust value for Strukturované popisy z FDA took 7.62939453125e-06s
INFO | --- Analysis for strukturovan--popisy-z-fda took 3.0264062881469727s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.37264394760131836s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0014126300811767578s
Extra | Recovery of all triples for STW Thesaurus for Economics took 15.919244766235352s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.1768124103546143s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.5482923984527588s
Interoperability | New terms check for STW Thesaurus for Economics took 1.5977540016174316s
Versatility | Languages check for STW Thesaurus for Economics took 1.5064311027526855s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.4624812602996826s
Security | Check HTTPS for STW Thesaurus for Economics took 0.16254734992980957s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.2653813362121582s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.25400233268737793s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.25271129608154297s
License | MR license check for STW Thesaurus for Economics took 0.2389538288116455s
License | HR license check for STW Thesaurus for Economics took 2.3645923137664795s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.25938963890075684s
Understandability | Number of label check for STW Thesaurus for Economics took 0.5403120517730713s
Understandability | URI regex check for STW Thesaurus for Economics took 0.4766995906829834s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.22029924392700195s
Verifiability | Authors check for STW Thesaurus for Economics took 0.25350379943847656s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.24869298934936523s
Performance | Throughput check for STW Thesaurus for Economics took 11.094640254974365s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.7428395748138428s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.24656057357788086s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.27468013763427734s
Interlinking | skos check for STW Thesaurus for Economics took 0.31390810012817383s
Interlinking | skos check for STW Thesaurus for Economics took 0.30304598808288574s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.24220538139343262s
Currency | Creation date check for STW Thesaurus for Economics took 0.4955017566680908s
Currency | Modification date check for STW Thesaurus for Economics took 0.5217182636260986s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 7.470148086547852s
Interoperability | New vocabularies check for STW Thesaurus for Economics took 4.926206111907959s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.27274417877197266s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.2875797748565674s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.24202299118041992s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 6.550971031188965s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0674054622650146s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.4445629119873047s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.27714061737060547s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.2632029056549072s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 2.4566969871520996s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.3633720874786377s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.3388376235961914s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.6705076694488525s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.25780272483825684s
Security | Sign check for STW Thesaurus for Economics took 0.2475888729095459s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 3021.680623292923s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.6787235736846924s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.020892620086669922s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 2.7418136596679688e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.0001277923583984375s
Interoperability | Check the re-using of existing vocabs for STW Thesaurus for Economics took 4.3345208168029785s
Believability | Calculation of trust value for STW Thesaurus for Economics took 8.106231689453125e-06s
INFO | --- Analysis for stw-thesaurus-for-economics took 3124.1964247226715s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.8597884178161621s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.2927896976470947s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.02017998695373535s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 4.9591064453125e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 7.62939453125e-06s
INFO | --- Analysis for sudocfr took 7.873443126678467s
Availability | SPARQL endpoint availability check for Surge Radio took 4.3392181396484375e-05s
Availability | VoID file availability check for Surge Radio took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.28189563751220703s
Reputation | Calculation of the PageRank for Surge Radio took 0.020195960998535156s
Interlinking | Calculation of Degree of Connection for Surge Radio took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.368492126464844e-05s
Believability | Calculation of trust value for Surge Radio took 7.152557373046875e-06s
INFO | --- Analysis for surge-radio took 4.364377737045288s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 4.363059997558594e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.43811559677124023s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.25875139236450195s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.02013683319091797s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 6.842613220214844e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 7.867813110351562e-06s
INFO | --- Analysis for swedish-open-cultural-heritage took 6.02330207824707s
Availability | SPARQL endpoint availability check for SweFN-RDF took 0.9541919231414795s
Availability | VoID file availability check for SweFN-RDF took 0.0005660057067871094s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.2922370433807373s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.020078420639038086s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.361701965332031e-05s
Believability | Calculation of trust value for SweFN-RDF took 8.344650268554688e-06s
INFO | --- Analysis for swefn-rdf took 5.4383392333984375s
Availability | SPARQL endpoint availability check for SwetoDblp took 4.673004150390625e-05s
Availability | VoID file availability check for SwetoDblp took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.26544189453125s
Reputation | Calculation of the PageRank for SwetoDblp took 0.020350217819213867s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.528594970703125e-05s
Believability | Calculation of trust value for SwetoDblp took 1.33514404296875e-05s
INFO | --- Analysis for sweto-dblp took 22.734997510910034s
Availability | SPARQL endpoint availability check for SymbolicData took 4.172325134277344e-05s
Availability | VoID file availability check for SymbolicData took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for SymbolicData took 0.24803829193115234s
Reputation | Calculation of the PageRank for SymbolicData took 0.020432710647583008s
Interlinking | Calculation of Degree of Connection for SymbolicData took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for SymbolicData took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for SymbolicData took 3.314018249511719e-05s
Believability | Calculation of trust value for SymbolicData took 8.58306884765625e-06s
INFO | --- Analysis for symbolicdata took 2.928393602371216s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.5220110416412354s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0006465911865234375s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.4833652973175049s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.8606281280517578s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 9.08555817604065s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 20.654388427734375s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.16887712478637695s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 3.3223485946655273s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.09835171699523926s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.8232598304748535s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 1.0146214962005615s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.16511869430541992s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.4209733009338379s
License | HR license check for National Digital Data Archive of Hungary (partial) took 53.88481950759888s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.5375757217407227s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 40.51817297935486s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.3578681945800781s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.20515704154968262s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.19245433807373047s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 1.22432279586792s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.983664751052856s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 8.463859558105469e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.7149739265441895s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 2.0007524490356445s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.4978599548339844s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.4321632385253906s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.438917875289917s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 3.492175579071045s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 2.7384917736053467s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 68.75466704368591s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.1920163631439209s
Accuracy | Check Functional Property for National Digital Data Archive of Hungary (partial) took 0.1963059902191162s
Accuracy | Check Inverse Functional Property for National Digital Data Archive of Hungary (partial) took 0.17673897743225098s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.27022695541381836s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.002710103988647461s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.0022344589233398438s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.23514986038208008s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 45.28639817237854s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.26028943061828613s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.557586908340454s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.2744989395141602s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 45.70917272567749s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.002036571502685547s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.3800795078277588s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.1732158660888672s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 18.718000173568726s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.8027570247650146s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.020804166793823242s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 9.059906005859375e-05s
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 1.8358230590820312e-05s
INFO | --- Analysis for sztaki-lod took 444.85192918777466s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 4.4345855712890625e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0006520748138427734s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.25949954986572266s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.02048182487487793s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.1021575927734375e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 7.867813110351562e-06s
INFO | --- Analysis for t4gm-info took 5.3672637939453125s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.172325134277344e-05s
Availability | VoID file availability check for tags2con delicious took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.2650768756866455s
Reputation | Calculation of the PageRank for tags2con delicious took 0.02055048942565918s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 4.1961669921875e-05s
Believability | Calculation of trust value for tags2con delicious took 7.867813110351562e-06s
INFO | --- Analysis for tags2con-delicious took 44.96764302253723s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 262.8114492893219s
Availability | VoID file availability check for Taiwan geographic names took 0.0008153915405273438s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.2830014228820801s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.020583152770996094s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 5.435943603515625e-05s
Believability | Calculation of trust value for Taiwan geographic names took 7.867813110351562e-06s
INFO | --- Analysis for taiwan-geographic-names took 666.8399245738983s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 4.744529724121094e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0006864070892333984s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.7623395919799805s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.020537614822387695s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 9.584426879882812e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 8.106231689453125e-06s
INFO | --- Analysis for talis-openlibrary took 6.662672519683838s
Availability | SPARQL endpoint availability check for TalkBank took 3.981590270996094e-05s
Availability | VoID file availability check for TalkBank took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for TalkBank took 0.2532312870025635s
Reputation | Calculation of the PageRank for TalkBank took 0.020414113998413086s
Interlinking | Calculation of Degree of Connection for TalkBank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for TalkBank took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for TalkBank took 2.9087066650390625e-05s
Believability | Calculation of trust value for TalkBank took 1.1682510375976562e-05s
INFO | --- Analysis for talkbank took 3.871351480484009s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 0.9040470123291016s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.27088475227355957s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.020606279373168945s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00012111663818359375s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 7.62939453125e-06s
INFO | --- Analysis for taxonconcept took 13.939176797866821s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 4.2438507080078125e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.0005502700805664062s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.2923564910888672s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.020358800888061523s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 8.153915405273438e-05s
Believability | Calculation of trust value for taxonconcept-assets took 8.106231689453125e-06s
INFO | --- Analysis for taxonconcept-assets took 3.376413345336914s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 4.315376281738281e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0006234645843505859s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.2555508613586426s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.02031397819519043s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 5.245208740234375e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 7.867813110351562e-06s
INFO | --- Analysis for taxonconcept-occurences took 3.1569392681121826s
Availability | SPARQL endpoint availability check for TAXREF-LD: Linked Data French Taxonomic Register took 1.885880708694458s
Availability | VoID file availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Linked Data French Taxonomic Register took 0.27616238594055176s
Reputation | Calculation of the PageRank for TAXREF-LD: Linked Data French Taxonomic Register took 0.020437240600585938s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Linked Data French Taxonomic Register took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Linked Data French Taxonomic Register took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Linked Data French Taxonomic Register took 5.507469177246094e-05s
Believability | Calculation of trust value for TAXREF-LD: Linked Data French Taxonomic Register took 7.62939453125e-06s
INFO | --- Analysis for taxref-ld took 8.27518630027771s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 263.03303575515747s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0006327629089355469s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.727118968963623s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.52587890625e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 4.100799560546875e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 1.33514404296875e-05s
INFO | --- Analysis for tcga took 541.4115898609161s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.398820161819458s
Availability | VoID file availability check for TCGA Roadmap took 0.0006432533264160156s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.2636678218841553s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.020394325256347656s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 7.390975952148438e-05s
Believability | Calculation of trust value for TCGA Roadmap took 7.3909759521484375e-06s
INFO | --- Analysis for tcga-roadmap took 7.677099227905273s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 1.7551350593566895s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.3433802127838135s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00010395050048828125s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 7.152557373046875e-06s
INFO | --- Analysis for tcmgenedit_dataset took 140.30589604377747s
Availability | SPARQL endpoint availability check for TDS took 4.2438507080078125e-05s
Availability | VoID file availability check for TDS took 0.0008082389831542969s
Completeness | Calculation of interlinking completeness for TDS took 0.2523493766784668s
Reputation | Calculation of the PageRank for TDS took 0.020736217498779297s
Interlinking | Calculation of Degree of Connection for TDS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TDS took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for TDS took 4.315376281738281e-05s
Believability | Calculation of trust value for TDS took 1.33514404296875e-05s
INFO | --- Analysis for tds took 5.966918468475342s
Availability | SPARQL endpoint availability check for TED Talks took 4.2438507080078125e-05s
Availability | VoID file availability check for TED Talks took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for TED Talks took 0.2711977958679199s
Reputation | Calculation of the PageRank for TED Talks took 0.02042222023010254s
Interlinking | Calculation of Degree of Connection for TED Talks took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TED Talks took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for TED Talks took 3.123283386230469e-05s
Believability | Calculation of trust value for TED Talks took 7.62939453125e-06s
INFO | --- Analysis for ted-talks took 3.6666388511657715s
Availability | SPARQL endpoint availability check for TEKORD took 5.698204040527344e-05s
Availability | VoID file availability check for TEKORD took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for TEKORD took 0.273730993270874s
Reputation | Calculation of the PageRank for TEKORD took 0.020461320877075195s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for TEKORD took 5.173683166503906e-05s
Believability | Calculation of trust value for TEKORD took 6.9141387939453125e-06s
INFO | --- Analysis for tekord took 7.167312860488892s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 2.636744737625122s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.27316999435424805s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.020573854446411133s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00011610984802246094s
Believability | Calculation of trust value for Telegraphis Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for telegraphis took 9.865986824035645s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 6.961822509765625e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.2806107997894287s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.02032184600830078s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 6.818771362304688e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 7.867813110351562e-06s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 13.628263235092163s
Availability | SPARQL endpoint availability check for TERENCE Reading Comprehension Dataset took 4.8160552978515625e-05s
Availability | VoID file availability check for TERENCE Reading Comprehension Dataset took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for TERENCE Reading Comprehension Dataset took 0.2532377243041992s
Reputation | Calculation of the PageRank for TERENCE Reading Comprehension Dataset took 0.021441936492919922s
Interlinking | Calculation of Degree of Connection for TERENCE Reading Comprehension Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TERENCE Reading Comprehension Dataset took 0.0008134841918945312s
Interlinking | Calculation of Clustering coefficient for TERENCE Reading Comprehension Dataset took 3.170967102050781e-05s
Believability | Calculation of trust value for TERENCE Reading Comprehension Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for terence-reading-comprehension-dataset took 2.904973030090332s
Availability | SPARQL endpoint availability check for Terminesp Linked Data took 4.0531158447265625e-05s
Availability | VoID file availability check for Terminesp Linked Data took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Terminesp Linked Data took 0.2553422451019287s
Reputation | Calculation of the PageRank for Terminesp Linked Data took 0.021338939666748047s
Interlinking | Calculation of Degree of Connection for Terminesp Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Terminesp Linked Data took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Terminesp Linked Data took 2.86102294921875e-05s
Believability | Calculation of trust value for Terminesp Linked Data took 7.62939453125e-06s
INFO | --- Analysis for terminesp took 2.899268627166748s
Availability | SPARQL endpoint availability check for Tesauro materias BUPM took 4.1961669921875e-05s
Availability | VoID file availability check for Tesauro materias BUPM took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Tesauro materias BUPM took 0.26380372047424316s
Reputation | Calculation of the PageRank for Tesauro materias BUPM took 0.02039790153503418s
Interlinking | Calculation of Degree of Connection for Tesauro materias BUPM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Tesauro materias BUPM took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Tesauro materias BUPM took 2.7894973754882812e-05s
Believability | Calculation of trust value for Tesauro materias BUPM took 6.67572021484375e-06s
INFO | --- Analysis for tesauro-materias-bupm took 3.3681411743164062s
Availability | SPARQL endpoint availability check for Teseo took 4.100799560546875e-05s
Availability | VoID file availability check for Teseo took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Teseo took 0.26784181594848633s
Reputation | Calculation of the PageRank for Teseo took 0.020264148712158203s
Interlinking | Calculation of Degree of Connection for Teseo took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Teseo took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Teseo took 2.8848648071289062e-05s
Believability | Calculation of trust value for Teseo took 8.106231689453125e-06s
INFO | --- Analysis for teseo took 2.916639804840088s
Availability | SPARQL endpoint availability check for xxxxx took 262.38414764404297s
Availability | VoID file availability check for xxxxx took 0.0008578300476074219s
Completeness | Calculation of interlinking completeness for xxxxx took 0.7173116207122803s
Reputation | Calculation of the PageRank for xxxxx took 0.020535945892333984s
Interlinking | Calculation of Degree of Connection for xxxxx took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for xxxxx took 6.031990051269531e-05s
Believability | Calculation of trust value for xxxxx took 7.62939453125e-06s
INFO | --- Analysis for testee took 799.4932913780212s
Availability | SPARQL endpoint availability check for Texai Lexicon took 4.410743713378906e-05s
Availability | VoID file availability check for Texai Lexicon took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for Texai Lexicon took 0.2759876251220703s
Reputation | Calculation of the PageRank for Texai Lexicon took 0.020713090896606445s
Interlinking | Calculation of Degree of Connection for Texai Lexicon took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Texai Lexicon took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Texai Lexicon took 3.695487976074219e-05s
Believability | Calculation of trust value for Texai Lexicon took 8.58306884765625e-06s
INFO | --- Analysis for texai_lexicon took 5.135479927062988s
Availability | SPARQL endpoint availability check for The CIARD RING took 4.100799560546875e-05s
Availability | VoID file availability check for The CIARD RING took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for The CIARD RING took 0.7506442070007324s
Reputation | Calculation of the PageRank for The CIARD RING took 0.020300865173339844s
Interlinking | Calculation of Degree of Connection for The CIARD RING took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The CIARD RING took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for The CIARD RING took 3.0994415283203125e-05s
Believability | Calculation of trust value for The CIARD RING took 1.3589859008789062e-05s
INFO | --- Analysis for the-ciard-ring took 4.393136501312256s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 0.14284038543701172s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.26003289222717285s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.020592451095581055s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 3.0994415283203125e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 8.106231689453125e-06s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 2.992222309112549s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 0.8751051425933838s
Availability | VoID file availability check for The European Library Open Dataset took 0.0006868839263916016s
Extra | Recovery of all triples for The European Library Open Dataset took 1.2450916767120361s
Performance | Total latancy measurement for The European Library Open Dataset took 1.1620643138885498s
Amount of data | Number of triples check for The European Library Open Dataset took 30.19576930999756s
Versatility | Languages check for The European Library Open Dataset took 0.26537227630615234s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 30.178118228912354s
Interpretability | RDF structures check for The European Library Open Dataset took 0.24724698066711426s
Versatility | Serialization formats check for The European Library Open Dataset took 0.24825692176818848s
Availability | RDF dump link check for The European Library Open Dataset took 0.28906893730163574s
License | MR license check for The European Library Open Dataset took 0.29004812240600586s
License | HR license check for The European Library Open Dataset took 0.24913907051086426s
Amount of data | Number of property check for The European Library Open Dataset took 0.2529129981994629s
Understandability | Number of label check for The European Library Open Dataset took 0.8998548984527588s
Understandability | URI regex check for The European Library Open Dataset took 0.46620750427246094s
Understandability | Vocabs check for The European Library Open Dataset took 0.25743985176086426s
Verifiability | Authors check for The European Library Open Dataset took 0.2575533390045166s
Verifiability | Publishers check for The European Library Open Dataset took 0.23003053665161133s
Performance | Throughput check for The European Library Open Dataset took 11.662401914596558s
Amount of data | Check the number of entities for The European Library Open Dataset took 7.43865966796875e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 0.23720502853393555s
Interlinking | sameAs chians check for The European Library Open Dataset took 0.328948974609375s
Interlinking | skos check for The European Library Open Dataset took 0.23909544944763184s
Interlinking | skos check for The European Library Open Dataset took 0.2779510021209717s
Timeliness | dataset update frequency check for The European Library Open Dataset took 0.25142836570739746s
Currency | Creation date check for The European Library Open Dataset took 0.4279322624206543s
Currency | Modification date check for The European Library Open Dataset took 0.4725685119628906s
Rep.Conc. | URIs length for The European Library Open Dataset took 60.51392126083374s
Interoperability | New vocabularies check for The European Library Open Dataset took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 0.20508599281311035s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 0.5204336643218994s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.027831077575683594s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.028635263442993164s
Consistency | Disjoint class check for The European Library Open Dataset took 0.25780224800109863s
Consistency | Check Misplaced properties for The European Library Open Dataset took 30.43950319290161s
Consistency | Misplaced classes for The European Library Open Dataset took 0.31337618827819824s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 1.721407413482666s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.3189611434936523s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 31.522990465164185s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.0329587459564209s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 0.2634584903717041s
Security | Sign check for The European Library Open Dataset took 0.23341774940490723s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 9.433465719223022s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.8096599578857422s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.020624876022338867s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 6.818771362304688e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 8.106231689453125e-06s
INFO | --- Analysis for the-european-library-open-dataset took 397.61981987953186s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 60.05164170265198s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0007555484771728516s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.7002959251403809s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.02509784698486328s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00011563301086425781s
Believability | Calculation of trust value for The Eurostat Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for the-eurostat-linked-data took 245.3382384777069s
Availability | SPARQL endpoint availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 6.413459777832031e-05s
Availability | VoID file availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.7291488647460938s
Reputation | Calculation of the PageRank for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.02058243751525879s
Interlinking | Calculation of Degree of Connection for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 3.147125244140625e-05s
Believability | Calculation of trust value for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 7.62939453125e-06s
INFO | --- Analysis for the-kazan-university-museum-as-linked-open-data-in-the-europeana-data-model took 3.8447036743164062s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 4.315376281738281e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.6897106170654297s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.020938634872436523s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0007910728454589844s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 8.96453857421875e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 8.344650268554688e-06s
INFO | --- Analysis for the-living-lod-cloud took 41.67252206802368s
Availability | SPARQL endpoint availability check for The MIDI Linked Data Cloud took 7.534027099609375e-05s
Availability | VoID file availability check for The MIDI Linked Data Cloud took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for The MIDI Linked Data Cloud took 0.27980947494506836s
Reputation | Calculation of the PageRank for The MIDI Linked Data Cloud took 0.02110433578491211s
Interlinking | Calculation of Degree of Connection for The MIDI Linked Data Cloud took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The MIDI Linked Data Cloud took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for The MIDI Linked Data Cloud took 3.3855438232421875e-05s
Believability | Calculation of trust value for The MIDI Linked Data Cloud took 8.58306884765625e-06s
INFO | --- Analysis for the-midi-linked-data-cloud took 4.247753620147705s
Availability | SPARQL endpoint availability check for The View From took 0.08376789093017578s
Availability | VoID file availability check for The View From took 0.0004458427429199219s
Completeness | Calculation of interlinking completeness for The View From took 0.26037049293518066s
Reputation | Calculation of the PageRank for The View From took 0.020725488662719727s
Interlinking | Calculation of Degree of Connection for The View From took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The View From took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for The View From took 8.296966552734375e-05s
Believability | Calculation of trust value for The View From took 7.3909759521484375e-06s
INFO | --- Analysis for the-view-from took 2.5245420932769775s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 4.124641418457031e-05s
Availability | VoID file availability check for Thesaurus BNCF took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.26430273056030273s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020689010620117188s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 3.266334533691406e-05s
Believability | Calculation of trust value for Thesaurus BNCF took 7.152557373046875e-06s
INFO | --- Analysis for thesaurus-bncf took 2.947585105895996s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 6.031990051269531e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.2789022922515869s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 6.628036499023438e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 7.62939453125e-06s
INFO | --- Analysis for thesaurus-datenwissen took 2.5312156677246094s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.45267677307128906s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.25589871406555176s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.0200803279876709s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.43865966796875e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 7.867813110351562e-06s
INFO | --- Analysis for thesaurus-w took 4.068809270858765s
Availability | SPARQL endpoint availability check for theses.fr took 4.2438507080078125e-05s
Availability | VoID file availability check for theses.fr took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for theses.fr took 0.25604724884033203s
Reputation | Calculation of the PageRank for theses.fr took 0.0201718807220459s
Interlinking | Calculation of Degree of Connection for theses.fr took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for theses.fr took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for theses.fr took 5.364418029785156e-05s
Believability | Calculation of trust value for theses.fr took 8.106231689453125e-06s
INFO | --- Analysis for thesesfr took 3.9728357791900635s
Availability | SPARQL endpoint availability check for ThIST took 265.2687728404999s
Availability | VoID file availability check for ThIST took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for ThIST took 0.2855226993560791s
Reputation | Calculation of the PageRank for ThIST took 0.020460844039916992s
Interlinking | Calculation of Degree of Connection for ThIST took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ThIST took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for ThIST took 8.940696716308594e-05s
Believability | Calculation of trust value for ThIST took 8.106231689453125e-06s
INFO | --- Analysis for thist took 564.7047760486603s
Availability | SPARQL endpoint availability check for TIP took 40.03941869735718s
Availability | VoID file availability check for TIP took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for TIP took 0.2807331085205078s
Reputation | Calculation of the PageRank for TIP took 0.02051711082458496s
Interlinking | Calculation of Degree of Connection for TIP took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for TIP took 0.0009329319000244141s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00013566017150878906s
Believability | Calculation of trust value for TIP took 7.867813110351562e-06s
INFO | --- Analysis for tip took 105.87667155265808s
Availability | SPARQL endpoint availability check for Tourpedia took 4.1484832763671875e-05s
Availability | VoID file availability check for Tourpedia took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Tourpedia took 0.7142927646636963s
Reputation | Calculation of the PageRank for Tourpedia took 0.020255327224731445s
Interlinking | Calculation of Degree of Connection for Tourpedia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Tourpedia took 0.0008106231689453125s
Interlinking | Calculation of Clustering coefficient for Tourpedia took 3.147125244140625e-05s
Believability | Calculation of trust value for Tourpedia took 7.3909759521484375e-06s
INFO | --- Analysis for tourpedia took 4.32060694694519s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 0.6577403545379639s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.26753973960876465s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.020179033279418945s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.220008850097656e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 7.62939453125e-06s
INFO | --- Analysis for traditional-korean-medicine took 4.628396272659302s
Availability | SPARQL endpoint availability check for Traffic Scotland took 0.20614075660705566s
Availability | VoID file availability check for Traffic Scotland took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.23653388023376465s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.020265817642211914s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.4809112548828125e-05s
Believability | Calculation of trust value for Traffic Scotland took 5.4836273193359375e-06s
INFO | --- Analysis for traffic-scotland took 2.69592547416687s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 1.0419154167175293s
Availability | VoID file availability check for Transparency International Linked Data took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.2692720890045166s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.02035999298095703s
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.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00010728836059570312s
Believability | Calculation of trust value for Transparency International Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for transparency-linked-data took 3.4784457683563232s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 0.644197940826416s
Availability | VoID file availability check for transport.data.gov.uk took 0.0006668567657470703s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.2659432888031006s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.020409107208251953s
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.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 9.369850158691406e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 5.9604644775390625e-06s
INFO | --- Analysis for transport-data-gov-uk took 3.8782732486724854s
Availability | SPARQL endpoint availability check for OpenUpLabs Transport took 4.0531158447265625e-05s
Availability | VoID file availability check for OpenUpLabs Transport took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for OpenUpLabs Transport took 0.25977587699890137s
Reputation | Calculation of the PageRank for OpenUpLabs Transport took 0.020240306854248047s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Transport took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Transport took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Transport took 2.9325485229492188e-05s
Believability | Calculation of trust value for OpenUpLabs Transport took 7.867813110351562e-06s
INFO | --- Analysis for transport-openuplabs took 2.948030471801758s
Availability | SPARQL endpoint availability check for Twarql took 10.582581758499146s
Availability | VoID file availability check for Twarql took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for Twarql took 0.2677004337310791s
Reputation | Calculation of the PageRank for Twarql took 0.020485401153564453s
Interlinking | Calculation of Degree of Connection for Twarql took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Twarql took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Twarql took 7.343292236328125e-05s
Believability | Calculation of trust value for Twarql took 7.62939453125e-06s
INFO | --- Analysis for twarql took 13.481297492980957s
Availability | SPARQL endpoint availability check for TWC Data-gov took 4.2438507080078125e-05s
Availability | VoID file availability check for TWC Data-gov took 0.0013058185577392578s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.25505900382995605s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.020447254180908203s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 3.123283386230469e-05s
Believability | Calculation of trust value for TWC Data-gov took 9.5367431640625e-06s
INFO | --- Analysis for twc-data-gov took 2.5081796646118164s
Availability | SPARQL endpoint availability check for Tetherless World Constellation Demonstrations took 4.863739013671875e-05s
Availability | VoID file availability check for Tetherless World Constellation Demonstrations took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Tetherless World Constellation Demonstrations took 0.257993221282959s
Reputation | Calculation of the PageRank for Tetherless World Constellation Demonstrations took 0.020342350006103516s
Interlinking | Calculation of Degree of Connection for Tetherless World Constellation Demonstrations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Tetherless World Constellation Demonstrations took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Tetherless World Constellation Demonstrations took 2.9087066650390625e-05s
Believability | Calculation of trust value for Tetherless World Constellation Demonstrations took 1.0967254638671875e-05s
INFO | --- Analysis for twc-demos took 2.898177146911621s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.13675761222839355s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.25057005882263184s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.024124622344970703s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 1.52587890625e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0011737346649169922s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 4.0531158447265625e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 6.9141387939453125e-06s
INFO | --- Analysis for twc-healthdata took 14.399877786636353s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 4.231240749359131s
Availability | VoID file availability check for Instance Hub (all) took 0.0007383823394775391s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.7228286266326904s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.02053689956665039s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 6.771087646484375e-05s
Believability | Calculation of trust value for Instance Hub (all) took 8.58306884765625e-06s
INFO | --- Analysis for twc-hub took 65.40099334716797s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 0.1470956802368164s
Availability | VoID file availability check for IEEE VIS Source Data took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.40041589736938477s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.020756006240844727s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.00011086463928222656s
Believability | Calculation of trust value for IEEE VIS Source Data took 7.62939453125e-06s
INFO | --- Analysis for twc-ieeevis took 116.12012147903442s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 4.220008850097656e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.00028443336486816406s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.2660791873931885s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.020449161529541016s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 9.298324584960938e-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 8.96453857421875e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 5.7220458984375e-06s
INFO | --- Analysis for twc-logd took 2.5935933589935303s
Availability | SPARQL endpoint availability check for twc-opendap took 0.12469267845153809s
Availability | VoID file availability check for twc-opendap took 0.0005855560302734375s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.28351593017578125s
Reputation | Calculation of the PageRank for twc-opendap took 0.020401716232299805s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 7.128715515136719e-05s
Believability | Calculation of trust value for twc-opendap took 1.0251998901367188e-05s
INFO | --- Analysis for twc-opendap took 50.07244825363159s
Availability | SPARQL endpoint availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 4.1961669921875e-05s
Availability | VoID file availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0003018379211425781s
Completeness | Calculation of interlinking completeness for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.26247549057006836s
Reputation | Calculation of the PageRank for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.020867586135864258s
Interlinking | Calculation of Degree of Connection for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 3.0517578125e-05s
Believability | Calculation of trust value for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 9.059906005859375e-06s
INFO | --- Analysis for tweetskb took 2.9443554878234863s
Availability | SPARQL endpoint availability check for Twitter Linked Data Service took 4.1484832763671875e-05s
Availability | VoID file availability check for Twitter Linked Data Service took 0.0002884864807128906s
Completeness | Calculation of interlinking completeness for Twitter Linked Data Service took 0.26768040657043457s
Reputation | Calculation of the PageRank for Twitter Linked Data Service took 0.020966768264770508s
Interlinking | Calculation of Degree of Connection for Twitter Linked Data Service took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Twitter Linked Data Service took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Twitter Linked Data Service took 3.1948089599609375e-05s
Believability | Calculation of trust value for Twitter Linked Data Service took 8.821487426757812e-06s
INFO | --- Analysis for twitter-lids took 2.9508776664733887s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.9680249691009521s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.28878068923950195s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.02097773551940918s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 4.506111145019531e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 8.821487426757812e-06s
INFO | --- Analysis for ub-mannheim-linked-data took 4.826594352722168s
Availability | SPARQL endpoint availability check for Uberblic.org took 2.9528696537017822s
Availability | VoID file availability check for Uberblic.org took 0.0008080005645751953s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.24597573280334473s
Reputation | Calculation of the PageRank for Uberblic.org took 0.020656824111938477s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00011134147644042969s
Believability | Calculation of trust value for Uberblic.org took 1.0728836059570312e-05s
INFO | --- Analysis for uberblic took 9.844407796859741s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.15384650230407715s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.2835347652435303s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.020535945892333984s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 0.00010514259338378906s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for uis-linked-data took 2.657794237136841s
Availability | SPARQL endpoint availability check for UK Legislation took 4.363059997558594e-05s
Availability | VoID file availability check for UK Legislation took 0.0007257461547851562s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.2745246887207031s
Reputation | Calculation of the PageRank for UK Legislation took 0.020992040634155273s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.0008654594421386719s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 9.1552734375e-05s
Believability | Calculation of trust value for UK Legislation took 6.198883056640625e-06s
INFO | --- Analysis for uk-legislation-api took 3.633418321609497s
Availability | SPARQL endpoint availability check for UK Postcodes took 4.363059997558594e-05s
Availability | VoID file availability check for UK Postcodes took 0.0006835460662841797s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.2732353210449219s
Reputation | Calculation of the PageRank for UK Postcodes took 0.020867586135864258s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0010311603546142578s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 7.843971252441406e-05s
Believability | Calculation of trust value for UK Postcodes took 8.58306884765625e-06s
INFO | --- Analysis for uk-postcodes took 22.42410707473755s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 4.410743713378906e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.2484149932861328s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0001342296600341797s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 7.62939453125e-06s
INFO | --- Analysis for umbel took 4.779689311981201s
Availability | SPARQL endpoint availability check for UMTHES took 4.315376281738281e-05s
Availability | VoID file availability check for UMTHES took 0.0007221698760986328s
Completeness | Calculation of interlinking completeness for UMTHES took 0.27176451683044434s
Reputation | Calculation of the PageRank for UMTHES took 0.020663738250732422s
Interlinking | Calculation of Degree of Connection for UMTHES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UMTHES took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for UMTHES took 4.2438507080078125e-05s
Believability | Calculation of trust value for UMTHES took 6.9141387939453125e-06s
INFO | --- Analysis for umthes took 6.285833120346069s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 1.6894714832305908s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.0007944107055664062s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.28115105628967285s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.020979881286621094s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 3.314018249511719e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 5.9604644775390625e-06s
INFO | --- Analysis for un-hazardous-numbers took 9.06058382987976s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 4.553794860839844e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.28383660316467285s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.020557880401611328s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0008976459503173828s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 3.266334533691406e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for unesco-thesaurus took 2.949115753173828s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.23640012741088867s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.02034616470336914s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 3.0279159545898438e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for unescothes took 2.9537692070007324s
Availability | SPARQL endpoint availability check for UniProt took 1.6757688522338867s
Availability | VoID file availability check for UniProt took 0.0005564689636230469s
Extra | Recovery of all triples for UniProt took 16.431139707565308s
Performance | Total latancy measurement for UniProt took 3.6447906494140625s
Amount of data | Number of triples check for UniProt took 0.35550737380981445s
Versatility | Languages check for UniProt took 0.4687190055847168s
Interpretability | Number of blank nodes check for UniProt took 0.7606244087219238s
Security | Check HTTPS for UniProt took 1.4073057174682617s
Interpretability | RDF structures check for UniProt took 0.16052913665771484s
Versatility | Serialization formats check for UniProt took 0.17360925674438477s
Availability | RDF dump link check for UniProt took 0.16873645782470703s
License | MR license check for UniProt took 0.1692209243774414s
License | HR license check for UniProt took 0.18129563331604004s
Amount of data | Number of property check for UniProt took 0.1873607635498047s
Understandability | Number of label check for UniProt took 0.17651820182800293s
Understandability | URI regex check for UniProt took 0.33972787857055664s
Understandability | Vocabs check for UniProt took 0.18538355827331543s
Verifiability | Authors check for UniProt took 0.17530179023742676s
Verifiability | Publishers check for UniProt took 0.18869328498840332s
Performance | Throughput check for UniProt took 17.07272171974182s
Amount of data | Check the number of entities for UniProt took 0.00015664100646972656s
Verifiability | Contribs. check for UniProt took 0.16826367378234863s
Interlinking | sameAs chians check for UniProt took 0.1770915985107422s
Interlinking | skos check for UniProt took 0.1698157787322998s
Interlinking | skos check for UniProt took 0.15065670013427734s
Timeliness | dataset update frequency check for UniProt took 0.16957902908325195s
Currency | Creation date check for UniProt took 0.3280370235443115s
Currency | Modification date check for UniProt took 0.34102368354797363s
Rep.Conc. | URIs length for UniProt took 111.79468393325806s
Interoperability | New vocabularies check for UniProt took 2.384185791015625e-07s
Consistency | Deprecated classes/propertiers check for UniProt took 0.17459678649902344s
Accuracy | Check Datatype consistency for UniProt took 7.116328239440918s
Consistency | Disjoint class check for UniProt took 0.16478919982910156s
Consistency | Check Ontology hijacking for UniProt took 0.17179322242736816s
Consistency | Check Invalid usage of undefined properties for UniProt took 1.70084547996521s
Conciseness | Check Extensional conciseness for UniProt took 2.6518023014068604s
Security | Sign check for UniProt took 0.16394495964050293s
Availability | Check URIs Dereferenciability for UniProt took 4.308757781982422s
Completeness | Calculation of interlinking completeness for UniProt took 0.8167920112609863s
Reputation | Calculation of the PageRank for UniProt took 0.020916223526000977s
Interlinking | Calculation of Degree of Connection for UniProt took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UniProt took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for UniProt took 5.8650970458984375e-05s
Interoperability | Check the re-using of existing vocabs for UniProt took 1.1920928955078125e-06s
Believability | Calculation of trust value for UniProt took 8.344650268554688e-06s
INFO | --- Analysis for uniprot took 706.2046413421631s
Availability | SPARQL endpoint availability check for UniProt citations took 4.076957702636719e-05s
Availability | VoID file availability check for UniProt citations took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for UniProt citations took 0.7118129730224609s
Reputation | Calculation of the PageRank for UniProt citations took 0.02133488655090332s
Interlinking | Calculation of Degree of Connection for UniProt citations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UniProt citations took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for UniProt citations took 2.9802322387695312e-05s
Believability | Calculation of trust value for UniProt citations took 1.239776611328125e-05s
INFO | --- Analysis for uniprot-citations took 4.74828314781189s
Availability | SPARQL endpoint availability check for UniProt databases took 4.124641418457031e-05s
Availability | VoID file availability check for UniProt databases took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for UniProt databases took 0.2678675651550293s
Reputation | Calculation of the PageRank for UniProt databases took 0.020113706588745117s
Interlinking | Calculation of Degree of Connection for UniProt databases took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for UniProt databases took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for UniProt databases took 2.9325485229492188e-05s
Believability | Calculation of trust value for UniProt databases took 7.62939453125e-06s
INFO | --- Analysis for uniprot-databases took 2.8716068267822266s
Availability | SPARQL endpoint availability check for uniprot-metadata took 5.53131103515625e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.2691187858581543s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.02005147933959961s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 6.937980651855469e-05s
Believability | Calculation of trust value for uniprot-metadata took 7.152557373046875e-06s
INFO | --- Analysis for uniprot-metadata took 4.2935450077056885s
Availability | SPARQL endpoint availability check for UniProtKB Taxonomy took 5.459785461425781e-05s
Availability | VoID file availability check for UniProtKB Taxonomy took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for UniProtKB Taxonomy took 0.2556941509246826s
Reputation | Calculation of the PageRank for UniProtKB Taxonomy took 0.020429611206054688s
Interlinking | Calculation of Degree of Connection for UniProtKB Taxonomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UniProtKB Taxonomy took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for UniProtKB Taxonomy took 3.0994415283203125e-05s
Believability | Calculation of trust value for UniProtKB Taxonomy took 7.867813110351562e-06s
INFO | --- Analysis for uniprot-taxonomy took 2.8755910396575928s
Availability | SPARQL endpoint availability check for UniProt UniParc took 4.100799560546875e-05s
Availability | VoID file availability check for UniProt UniParc took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for UniProt UniParc took 0.26346564292907715s
Reputation | Calculation of the PageRank for UniProt UniParc took 0.020483970642089844s
Interlinking | Calculation of Degree of Connection for UniProt UniParc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UniProt UniParc took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for UniProt UniParc took 3.218650817871094e-05s
Believability | Calculation of trust value for UniProt UniParc took 7.867813110351562e-06s
INFO | --- Analysis for uniprot-uniparc took 2.9103872776031494s
Availability | SPARQL endpoint availability check for UniProt UniPathway took 4.172325134277344e-05s
Availability | VoID file availability check for UniProt UniPathway took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for UniProt UniPathway took 0.26287412643432617s
Reputation | Calculation of the PageRank for UniProt UniPathway took 0.020348072052001953s
Interlinking | Calculation of Degree of Connection for UniProt UniPathway took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UniProt UniPathway took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for UniProt UniPathway took 3.0279159545898438e-05s
Believability | Calculation of trust value for UniProt UniPathway took 8.821487426757812e-06s
INFO | --- Analysis for uniprot-unipathway took 3.418511152267456s
Availability | SPARQL endpoint availability check for UniProtKB took 1.2297146320343018s
Availability | VoID file availability check for UniProtKB took 0.0006167888641357422s
Extra | Recovery of all triples for UniProtKB took 12.42486023902893s
Performance | Total latancy measurement for UniProtKB took 2.835999011993408s
Amount of data | Number of triples check for UniProtKB took 0.1589043140411377s
Interoperability | New terms check for UniProtKB took 1.5633506774902344s
Versatility | Languages check for UniProtKB took 0.3863105773925781s
Interpretability | Number of blank nodes check for UniProtKB took 0.7191331386566162s
Interpretability | RDF structures check for UniProtKB took 0.19522380828857422s
Versatility | Serialization formats check for UniProtKB took 0.10601258277893066s
Availability | RDF dump link check for UniProtKB took 0.09001874923706055s
License | MR license check for UniProtKB took 0.10831284523010254s
License | HR license check for UniProtKB took 300.1515038013458s
Amount of data | Number of property check for UniProtKB took 0.0913083553314209s
Understandability | Number of label check for UniProtKB took 41.265743017196655s
Understandability | URI regex check for UniProtKB took 0.17548346519470215s
Understandability | Vocabs check for UniProtKB took 0.08491659164428711s
Verifiability | Authors check for UniProtKB took 0.0980076789855957s
Verifiability | Publishers check for UniProtKB took 0.11997509002685547s
Performance | Throughput check for UniProtKB took 16.128387689590454s
Amount of data | Check the number of entities for UniProtKB took 6.866455078125e-05s
Verifiability | Contribs. check for UniProtKB took 0.14199161529541016s
Interlinking | sameAs chians check for UniProtKB took 0.11126542091369629s
Interlinking | skos check for UniProtKB took 0.14664030075073242s
Interlinking | skos check for UniProtKB took 0.16150259971618652s
Timeliness | dataset update frequency check for UniProtKB took 0.09476566314697266s
Currency | Creation date check for UniProtKB took 0.20682954788208008s
Currency | Modification date check for UniProtKB took 0.24297189712524414s
Rep.Conc. | URIs length for UniProtKB took 107.20542669296265s
Interoperability | New vocabularies check for UniProtKB took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for UniProtKB took 0.09241151809692383s
Accuracy | Check Functional Property for UniProtKB took 0.07953715324401855s
Accuracy | Check Inverse Functional Property for UniProtKB took 0.1014716625213623s
Accuracy | Check Empty annotation labels for UniProtKB took 8.134368181228638s
Accuracy | Check White space in annotation for UniProtKB took 2.526146173477173s
Accuracy | Check Datatype consistency for UniProtKB took 7.148398160934448s
Consistency | Disjoint class check for UniProtKB took 0.08135080337524414s
Consistency | Check Misplaced properties for UniProtKB took 3.7378382682800293s
Consistency | Check Ontology hijacking for UniProtKB took 7.129528284072876s
Consistency | Check Invalid usage of undefined classes for UniProtKB took 20628.11913228035s
Consistency | Check Invalid usage of undefined properties for UniProtKB took 1.7414331436157227s
Conciseness | Check Extensional conciseness for UniProtKB took 2.706395387649536s
Conciseness | Check Intensional conciseness for UniProtKB took 0.12439393997192383s
Security | Sign check for UniProtKB took 0.07498788833618164s
Availability | Check URIs Dereferenciability for UniProtKB took 4.469264030456543s
Completeness | Calculation of interlinking completeness for UniProtKB took 1.569319486618042s
Reputation | Calculation of the PageRank for UniProtKB took 0.7463338375091553s
Interlinking | Calculation of Degree of Connection for UniProtKB took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.000995635986328125s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 6.628036499023438e-05s
Interoperability | Check the re-using of existing vocabs for UniProtKB took 2.1457672119140625e-06s
Believability | Calculation of trust value for UniProtKB took 7.867813110351562e-06s
INFO | --- Analysis for uniprotkb took 21566.183737277985s
Availability | SPARQL endpoint availability check for UniProt UniRef took 4.649162292480469e-05s
Availability | VoID file availability check for UniProt UniRef took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for UniProt UniRef took 0.25742006301879883s
Reputation | Calculation of the PageRank for UniProt UniRef took 0.020374774932861328s
Interlinking | Calculation of Degree of Connection for UniProt UniRef took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UniProt UniRef took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for UniProt UniRef took 3.0040740966796875e-05s
Believability | Calculation of trust value for UniProt UniRef took 7.3909759521484375e-06s
INFO | --- Analysis for uniref took 4.717655658721924s
Availability | SPARQL endpoint availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 4.291534423828125e-05s
Availability | VoID file availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.0003266334533691406s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.2930445671081543s
Reputation | Calculation of the PageRank for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.02041339874267578s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 2.86102294921875e-05s
Believability | Calculation of trust value for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 7.3909759521484375e-06s
INFO | --- Analysis for unistat-kis-2011-2012-in-rdf-key-information-set-uk-universities took 3.419595718383789s
Availability | SPARQL endpoint availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 4.100799560546875e-05s
Availability | VoID file availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.27300190925598145s
Reputation | Calculation of the PageRank for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.020421743392944336s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 2.8371810913085938e-05s
Believability | Calculation of trust value for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 7.62939453125e-06s
INFO | --- Analysis for unistat-kis-in-rdf-key-information-set-uk-universities took 3.4215214252471924s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 5.53131103515625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.2762916088104248s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.020292043685913086s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 14.440194129943848s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.28871798515319824s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.020374536514282227s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 5.346054315567017s
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.0007827281951904297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.29604101181030273s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 13.23558235168457s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 6.842613220214844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.2538783550262451s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.02047586441040039s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-basque took 13.587605714797974s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 5.650520324707031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.001298666000366211s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.30053138732910156s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.02024388313293457s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 14.54451298713684s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.26924657821655273s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.020238399505615234s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 13.30893611907959s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.2914388179779053s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.020571470260620117s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 8.842748403549194s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0007185935974121094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.30191802978515625s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.020609140396118164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 13.310338735580444s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 8.678436279296875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.2935643196105957s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 13.809557676315308s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.2829456329345703s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.02046656608581543s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech took 13.22916841506958s
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.0006666183471679688s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.2831418514251709s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.0204317569732666s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 13.208581924438477s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 7.772445678710938e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.28826022148132324s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 4.482269287109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 9.5367431640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 13.080444574356079s
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.00044345855712890625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.2566819190979004s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.020195722579956055s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-danish took 5.261225700378418s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.00041031837463378906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.25531625747680664s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.02045917510986328s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 13.228833198547363s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.24986624717712402s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.020257234573364258s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 8.821487426757812e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 13.175904750823975s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.23768877983093262s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.020625829696655273s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-english took 13.149334907531738s
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.0007534027099609375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.27277135848999023s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.020905256271362305s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 13.077192544937134s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.27477455139160156s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.020313262939453125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 13.111427783966064s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 6.985664367675781e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.0007102489471435547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.3059394359588623s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.020195484161376953s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 13.277353763580322s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.28083014488220215s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.02036595344543457s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 5.609938383102417s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.32106828689575195s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.020520925521850586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0009734630584716797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 4.458427429199219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 13.208590984344482s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 5.459785461425781e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0007550716400146484s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.25708699226379395s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.02044081687927246s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 4.863739013671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 6.67572021484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-french took 13.162398338317871s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.2994554042816162s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.020403146743774414s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician took 13.721850395202637s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.0006163120269775391s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.26303863525390625s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.020365476608276367s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 5.137869119644165s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 6.389617919921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.28365039825439453s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.020671367645263672s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-german took 5.449957609176636s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 7.2479248046875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.0007236003875732422s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.31699442863464355s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.020664691925048828s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 5.407649993896484s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 4.696846008300781e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.2772941589355469s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.0204470157623291s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 6.198883056640625e-06s
INFO | --- Analysis for universal-dependencies-treebank-greek took 5.404294729232788s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0006666183471679688s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.2689526081085205s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.020516157150268555s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 1.6689300537109375e-05s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 13.28330945968628s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0007569789886474609s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.26952242851257324s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.020437002182006836s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 13.08841872215271s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.0006532669067382812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.2722475528717041s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.02037644386291504s
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.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 7.724761962890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 5.448147535324097s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.0007188320159912109s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.28746747970581055s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.020195722579956055s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 13.311307191848755s
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.0006418228149414062s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.2789187431335449s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.02040266990661621s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-irish took 5.322342395782471s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.2662220001220703s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.020784616470336914s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-italian took 13.240736961364746s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 8.320808410644531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.2642035484313965s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.020829200744628906s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 13.2160165309906s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.29474306106567383s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.020645618438720703s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 5.097700595855713s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0007212162017822266s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.28415393829345703s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.02066516876220703s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 6.4373016357421875e-06s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 13.181706428527832s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0012350082397460938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.2872903347015381s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.020666837692260742s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin took 5.39557409286499s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.2868499755859375s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.02019214630126953s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 3.8623809814453125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 9.298324584960938e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 13.065672159194946s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.267498254776001s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.02048468589782715s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 13.096880912780762s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.000789642333984375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.2594771385192871s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.020740270614624023s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 4.5299530029296875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 21.94776964187622s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0007531642913818359s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.25330257415771484s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.020496606826782227s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.0008382797241210938s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 4.3392181396484375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 13.044248104095459s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.2678205966949463s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.020567655563354492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 9.059906005859375e-06s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 13.325771808624268s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 5.626678466796875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.2594618797302246s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.020577430725097656s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-persian took 5.28005313873291s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 6.67572021484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.0006964206695556641s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.24296784400939941s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.02141261100769043s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0010035037994384766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 4.696846008300781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 8.821487426757812e-06s
INFO | --- Analysis for universal-dependencies-treebank-polish took 13.279078722000122s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 5.7220458984375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.0008296966552734375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.2445812225341797s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.020418405532836914s
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.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 12.821106433868408s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.0007560253143310547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.2784268856048584s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 13.198029518127441s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0007593631744384766s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.27819156646728516s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.02130126953125s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0008242130279541016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 5.14984130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 13.257008790969849s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.2593722343444824s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020552873611450195s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 13.246550559997559s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.27698779106140137s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.020447731018066406s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian took 13.205350875854492s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.0006215572357177734s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.2630655765533447s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.02016615867614746s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 6.4373016357421875e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 5.0619518756866455s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 8.988380432128906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.24919462203979492s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.020402193069458008s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 13.441736698150635s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0007195472717285156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.26456427574157715s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.02034616470336914s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 13.278931140899658s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 4.553794860839844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.0007412433624267578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.29195356369018555s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.020696640014648438s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 5.9604644775390625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 8.821487426757812e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 13.3290274143219s
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.0007126331329345703s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.29044246673583984s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.02037787437438965s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 13.28910493850708s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 5.5789947509765625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.0006663799285888672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.2447223663330078s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.020331859588623047s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 8.821487426757812e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 13.53421664237976s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 4.363059997558594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.2888004779815674s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.020377159118652344s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 13.166088104248047s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.2564680576324463s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 5.226968288421631s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.2810351848602295s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.02059030532836914s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 5.669738292694092s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 5.888938903808594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.2624814510345459s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.02054309844970703s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 13.309575080871582s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.0008153915405273438s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.26244091987609863s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.02057170867919922s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 4.792213439941406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 13.248273849487305s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 4.458427429199219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.2858860492706299s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.020273685455322266s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 13.300415515899658s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.2656235694885254s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.024955272674560547s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 14.74521780014038s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.2752654552459717s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.02061319351196289s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0008275508880615234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 5.340576171875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 13.332871913909912s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 4.9591064453125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0006954669952392578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.30728793144226074s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.02052164077758789s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0010144710540771484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 4.6253204345703125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 13.36298131942749s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 4.363059997558594e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.2843818664550781s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.02044057846069336s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 7.033348083496094e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 7.867813110351562e-06s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 6.576889753341675s
Availability | SPARQL endpoint availability check for Universitat Pompeu Fabra - linked data took 5.4836273193359375e-05s
Availability | VoID file availability check for Universitat Pompeu Fabra - linked data took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Universitat Pompeu Fabra - linked data took 0.2734673023223877s
Reputation | Calculation of the PageRank for Universitat Pompeu Fabra - linked data took 0.020471572875976562s
Interlinking | Calculation of Degree of Connection for Universitat Pompeu Fabra - linked data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universitat Pompeu Fabra - linked data took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Universitat Pompeu Fabra - linked data took 2.9325485229492188e-05s
Believability | Calculation of trust value for Universitat Pompeu Fabra - linked data took 8.344650268554688e-06s
INFO | --- Analysis for universitat-pompeu-fabra-linked-data took 2.9904963970184326s
Availability | SPARQL endpoint availability check for University of Bristol took 5.3882598876953125e-05s
Availability | VoID file availability check for University of Bristol took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for University of Bristol took 0.27615833282470703s
Reputation | Calculation of the PageRank for University of Bristol took 0.020500659942626953s
Interlinking | Calculation of Degree of Connection for University of Bristol took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for University of Bristol took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for University of Bristol took 3.0040740966796875e-05s
Believability | Calculation of trust value for University of Bristol took 1.4066696166992188e-05s
INFO | --- Analysis for university-of-bristol took 2.9804861545562744s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 4.291534423828125e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.2948744297027588s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.02065277099609375s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 4.863739013671875e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 8.58306884765625e-06s
INFO | --- Analysis for university-plymouth-reading-lists took 3.0833306312561035s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 4.3392181396484375e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.25748443603515625s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.020642757415771484s
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.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 3.6716461181640625e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 1.4781951904296875e-05s
INFO | --- Analysis for university-sussex-reading-lists took 2.7015247344970703s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 0.1541290283203125s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.2609078884124756s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.020746231079101562s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 7.367134094238281e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 7.3909759521484375e-06s
INFO | --- Analysis for unodc took 2.7363429069519043s
Availability | SPARQL endpoint availability check for URIBurner took 0.6984868049621582s
Availability | VoID file availability check for URIBurner took 0.0005939006805419922s
Extra | Recovery of all triples for URIBurner took 122.25779461860657s
Performance | Total latancy measurement for URIBurner took 1.6426775455474854s
Amount of data | Number of triples check for URIBurner took 6.3534064292907715s
Interoperability | New terms check for URIBurner took 42.35627007484436s
Versatility | Languages check for URIBurner took 123.38291430473328s
Interpretability | Number of blank nodes check for URIBurner took 3.687142848968506s
Security | Check HTTPS for URIBurner took 0.4948718547821045s
Interpretability | RDF structures check for URIBurner took 4.639953374862671s
Versatility | Serialization formats check for URIBurner took 39.94798946380615s
Availability | RDF dump link check for URIBurner took 48.15068483352661s
License | MR license check for URIBurner took 2.4404470920562744s
License | HR license check for URIBurner took 120.46742391586304s
Amount of data | Number of property check for URIBurner took 0.5452954769134521s
Understandability | Number of label check for URIBurner took 4.199531555175781s
Understandability | URI regex check for URIBurner took 0.9487762451171875s
Understandability | Vocabs check for URIBurner took 0.3466629981994629s
Verifiability | Authors check for URIBurner took 0.4131934642791748s
Verifiability | Publishers check for URIBurner took 0.3276221752166748s
Performance | Throughput check for URIBurner took 11.089511156082153s
Amount of data | Check the number of entities for URIBurner took 0.00010776519775390625s
Verifiability | Contribs. check for URIBurner took 0.4040553569793701s
Interlinking | sameAs chians check for URIBurner took 1.244187831878662s
Interlinking | skos check for URIBurner took 0.6310567855834961s
Interlinking | skos check for URIBurner took 0.2951071262359619s
Timeliness | dataset update frequency check for URIBurner took 0.7045748233795166s
Currency | Creation date check for URIBurner took 2.3780550956726074s
Currency | Modification date check for URIBurner took 0.4597334861755371s
Rep.Conc. | URIs length for URIBurner took 146.81609654426575s
Interoperability | New vocabularies check for URIBurner took 42.69538950920105s
Consistency | Deprecated classes/propertiers check for URIBurner took 0.3232545852661133s
Accuracy | Check Functional Property for URIBurner took 0.2822732925415039s
Accuracy | Check Inverse Functional Property for URIBurner took 0.2907891273498535s
Accuracy | Check Empty annotation labels for URIBurner took 66.56092262268066s
Accuracy | Check White space in annotation for URIBurner took 0.1832261085510254s
Consistency | Disjoint class check for URIBurner took 0.30933237075805664s
Consistency | Check Misplaced properties for URIBurner took 356.3040494918823s
Consistency | Misplaced classes for URIBurner took 66.29318118095398s
Consistency | Check Ontology hijacking for URIBurner took 103.71852111816406s
Consistency | Check Invalid usage of undefined properties for URIBurner took 95.76424527168274s
Conciseness | Check Extensional conciseness for URIBurner took 0.0001399517059326172s
Security | Sign check for URIBurner took 0.5133640766143799s
Completeness | Calculation of interlinking completeness for URIBurner took 0.5598878860473633s
Reputation | Calculation of the PageRank for URIBurner took 0.02110457420349121s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for URIBurner took 0.00010776519775390625s
Interoperability | Check the re-using of existing vocabs for URIBurner took 34.64791536331177s
Believability | Calculation of trust value for URIBurner took 7.3909759521484375e-06s
INFO | --- Analysis for uriburner took 6296.356557607651s
Availability | SPARQL endpoint availability check for US Political Violence took 4.38690185546875e-05s
Availability | VoID file availability check for US Political Violence took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for US Political Violence took 0.7296528816223145s
Reputation | Calculation of the PageRank for US Political Violence took 0.02069234848022461s
Interlinking | Calculation of Degree of Connection for US Political Violence took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for US Political Violence took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for US Political Violence took 3.0994415283203125e-05s
Believability | Calculation of trust value for US Political Violence took 8.344650268554688e-06s
INFO | --- Analysis for us-political-violence took 5.282768487930298s
Availability | SPARQL endpoint availability check for USAGE review corpus took 0.46498537063598633s
Availability | VoID file availability check for USAGE review corpus took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.29238295555114746s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.020041227340698242s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 3.0517578125e-05s
Believability | Calculation of trust value for USAGE review corpus took 6.67572021484375e-06s
INFO | --- Analysis for usage-review-corpus took 4.72430944442749s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 6.480135440826416s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.28302669525146484s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.020336389541625977s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 7.677078247070312e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 1.1444091796875e-05s
INFO | --- Analysis for utpl-lod took 12.308656692504883s
Availability | SPARQL endpoint availability check for Výkazy zisku a ztrát obcí ČR took 4.4345855712890625e-05s
Availability | VoID file availability check for Výkazy zisku a ztrát obcí ČR took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Výkazy zisku a ztrát obcí ČR took 0.2610776424407959s
Reputation | Calculation of the PageRank for Výkazy zisku a ztrát obcí ČR took 0.020165681838989258s
Interlinking | Calculation of Degree of Connection for Výkazy zisku a ztrát obcí ČR took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Výkazy zisku a ztrát obcí ČR took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Výkazy zisku a ztrát obcí ČR took 3.0994415283203125e-05s
Believability | Calculation of trust value for Výkazy zisku a ztrát obcí ČR took 6.198883056640625e-06s
INFO | --- Analysis for v-kazy-zisku-a-ztr-t-obc---r took 3.906400442123413s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 6.333254814147949s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.0007374286651611328s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.2700188159942627s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 8.893013000488281e-05s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 6.198883056640625e-06s
INFO | --- Analysis for verrijktkoninkrijk took 14.959369659423828s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 5.626678466796875e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.00033664703369140625s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.2652881145477295s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.00017833709716796875s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 1.1682510375976562e-05s
INFO | --- Analysis for viaf took 19.942327976226807s
Availability | SPARQL endpoint availability check for Vías Públicas de Zaragoza (Localización) took 4.1961669921875e-05s
Availability | VoID file availability check for Vías Públicas de Zaragoza (Localización) took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for Vías Públicas de Zaragoza (Localización) took 0.27850985527038574s
Reputation | Calculation of the PageRank for Vías Públicas de Zaragoza (Localización) took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for Vías Públicas de Zaragoza (Localización) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vías Públicas de Zaragoza (Localización) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Vías Públicas de Zaragoza (Localización) took 3.075599670410156e-05s
Believability | Calculation of trust value for Vías Públicas de Zaragoza (Localización) took 7.62939453125e-06s
INFO | --- Analysis for vias-publicas-zaragoza took 2.9464986324310303s
Availability | SPARQL endpoint availability check for vimeo.videoobject took 4.100799560546875e-05s
Availability | VoID file availability check for vimeo.videoobject took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for vimeo.videoobject took 0.2705268859863281s
Reputation | Calculation of the PageRank for vimeo.videoobject took 0.020405292510986328s
Interlinking | Calculation of Degree of Connection for vimeo.videoobject took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for vimeo.videoobject took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for vimeo.videoobject took 3.0994415283203125e-05s
Believability | Calculation of trust value for vimeo.videoobject took 7.3909759521484375e-06s
INFO | --- Analysis for vimeo_videoobject took 3.0118448734283447s
Availability | SPARQL endpoint availability check for VIVO took 4.315376281738281e-05s
Availability | VoID file availability check for VIVO took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for VIVO took 0.28745150566101074s
Reputation | Calculation of the PageRank for VIVO took 0.02075052261352539s
Interlinking | Calculation of Degree of Connection for VIVO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for VIVO took 7.343292236328125e-05s
Believability | Calculation of trust value for VIVO took 8.106231689453125e-06s
INFO | --- Analysis for vivo took 5.141643524169922s
Availability | SPARQL endpoint availability check for VIVO Cornell took 5.078315734863281e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0007328987121582031s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.29155969619750977s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.02021622657775879s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 8.153915405273438e-05s
Believability | Calculation of trust value for VIVO Cornell took 7.3909759521484375e-06s
INFO | --- Analysis for vivo-cornell-university took 6.492896795272827s
Availability | SPARQL endpoint availability check for VIVO CU-Boulder took 4.076957702636719e-05s
Availability | VoID file availability check for VIVO CU-Boulder took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for VIVO CU-Boulder took 0.2744140625s
Reputation | Calculation of the PageRank for VIVO CU-Boulder took 0.02034783363342285s
Interlinking | Calculation of Degree of Connection for VIVO CU-Boulder took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for VIVO CU-Boulder took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for VIVO CU-Boulder took 2.7894973754882812e-05s
Believability | Calculation of trust value for VIVO CU-Boulder took 7.867813110351562e-06s
INFO | --- Analysis for vivo-cu-boulder took 3.002633571624756s
Availability | SPARQL endpoint availability check for VIVO Indiana took 4.1484832763671875e-05s
Availability | VoID file availability check for VIVO Indiana took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.256544828414917s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.020141124725341797s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 8.368492126464844e-05s
Believability | Calculation of trust value for VIVO Indiana took 7.3909759521484375e-06s
INFO | --- Analysis for vivo-indiana-university took 3.1503546237945557s
Availability | SPARQL endpoint availability check for VIVO Ponce took 4.1961669921875e-05s
Availability | VoID file availability check for VIVO Ponce took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.25887370109558105s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.020351886749267578s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.1948089599609375e-05s
Believability | Calculation of trust value for VIVO Ponce took 7.152557373046875e-06s
INFO | --- Analysis for vivo-ponce took 2.863342046737671s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 4.673004150390625e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.2581162452697754s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.020183086395263672s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 3.5762786865234375e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 8.106231689453125e-06s
INFO | --- Analysis for vivo-scripps-research-institute took 2.9280824661254883s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 4.3392181396484375e-05s
Availability | VoID file availability check for VIVO University of Florida took 0.0006718635559082031s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.2705717086791992s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.02056431770324707s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 9.989738464355469e-05s
Believability | Calculation of trust value for VIVO University of Florida took 8.821487426757812e-06s
INFO | --- Analysis for vivo-university-of-florida took 2.5450780391693115s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 4.3392181396484375e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.0006804466247558594s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.2743358612060547s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.020647048950195312s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 3.814697265625e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 1.6450881958007812e-05s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 2.917923927307129s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 4.3392181396484375e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.2828679084777832s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.020032167434692383s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007328987121582031s
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.864084243774414s
Availability | SPARQL endpoint availability check for vivo2doi took 4.267692565917969e-05s
Availability | VoID file availability check for vivo2doi took 0.0007486343383789062s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.25935816764831543s
Reputation | Calculation of the PageRank for vivo2doi took 0.020180702209472656s
Interlinking | Calculation of Degree of Connection for vivo2doi took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 5.221366882324219e-05s
Believability | Calculation of trust value for vivo2doi took 9.059906005859375e-06s
INFO | --- Analysis for vivo2doi took 24.076521158218384s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 4.291534423828125e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.0007402896881103516s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.25168395042419434s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.02043747901916504s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 7.033348083496094e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 8.344650268554688e-06s
INFO | --- Analysis for vu-wordnet took 14.75841236114502s
Availability | SPARQL endpoint availability check for vulnerapedia took 0.8786704540252686s
Availability | VoID file availability check for vulnerapedia took 0.0005548000335693359s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.287996768951416s
Reputation | Calculation of the PageRank for vulnerapedia took 0.021137714385986328s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 8.058547973632812e-05s
Believability | Calculation of trust value for vulnerapedia took 8.106231689453125e-06s
INFO | --- Analysis for vulnerapedia took 3.9796576499938965s
Availability | SPARQL endpoint availability check for W3C took 4.410743713378906e-05s
Availability | VoID file availability check for W3C took 0.0007314682006835938s
Completeness | Calculation of interlinking completeness for W3C took 0.29313111305236816s
Reputation | Calculation of the PageRank for W3C took 0.020703792572021484s
Interlinking | Calculation of Degree of Connection for W3C took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for W3C took 0.0007927417755126953s
Interlinking | Calculation of Clustering coefficient for W3C took 0.0001499652862548828s
Believability | Calculation of trust value for W3C took 7.62939453125e-06s
INFO | --- Analysis for w3c took 2.664862632751465s
Availability | SPARQL endpoint availability check for W3C Provenance Incubator Group Vocabulary Mappings took 4.2438507080078125e-05s
Availability | VoID file availability check for W3C Provenance Incubator Group Vocabulary Mappings took 0.00029277801513671875s
Completeness | Calculation of interlinking completeness for W3C Provenance Incubator Group Vocabulary Mappings took 0.27446937561035156s
Reputation | Calculation of the PageRank for W3C Provenance Incubator Group Vocabulary Mappings took 0.02051520347595215s
Interlinking | Calculation of Degree of Connection for W3C Provenance Incubator Group Vocabulary Mappings took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for W3C Provenance Incubator Group Vocabulary Mappings took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for W3C Provenance Incubator Group Vocabulary Mappings took 3.0279159545898438e-05s
Believability | Calculation of trust value for W3C Provenance Incubator Group Vocabulary Mappings took 7.62939453125e-06s
INFO | --- Analysis for w3c-provenance-incubator-group-vocabulary-mappings took 2.953080177307129s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 4.4345855712890625e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.2680685520172119s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.02025008201599121s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.0001125335693359375s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 7.152557373046875e-06s
INFO | --- Analysis for w3c-wordnet took 3.220064163208008s
Availability | SPARQL endpoint availability check for WarSampo took 0.3784921169281006s
Availability | VoID file availability check for WarSampo took 0.0006618499755859375s
Extra | Recovery of all triples for WarSampo took 249.74839735031128s
Performance | Total latancy measurement for WarSampo took 1.3045282363891602s
Amount of data | Number of triples check for WarSampo took 18.12293767929077s
Interoperability | New terms check for WarSampo took 3.791381597518921s
Versatility | Languages check for WarSampo took 53.146437644958496s
Interpretability | Number of blank nodes check for WarSampo took 18.29471254348755s
Security | Check HTTPS for WarSampo took 0.4113898277282715s
Interpretability | RDF structures check for WarSampo took 0.20392990112304688s
Versatility | Serialization formats check for WarSampo took 0.1945180892944336s
Availability | RDF dump link check for WarSampo took 0.9843969345092773s
License | MR license check for WarSampo took 0.20486664772033691s
License | HR license check for WarSampo took 44.191335916519165s
Amount of data | Number of property check for WarSampo took 0.18179917335510254s
Understandability | Number of label check for WarSampo took 9.5415620803833s
Understandability | URI regex check for WarSampo took 0.3664677143096924s
Understandability | Vocabs check for WarSampo took 0.1878986358642578s
Verifiability | Authors check for WarSampo took 0.18952512741088867s
Verifiability | Publishers check for WarSampo took 0.21611595153808594s
Performance | Throughput check for WarSampo took 10.894193649291992s
Amount of data | Check the number of entities for WarSampo took 15.31469440460205s
Verifiability | Contribs. check for WarSampo took 0.2099471092224121s
Interlinking | sameAs chians check for WarSampo took 0.22986578941345215s
Interlinking | skos check for WarSampo took 0.2310643196105957s
Interlinking | skos check for WarSampo took 0.1700582504272461s
Timeliness | dataset update frequency check for WarSampo took 0.18024897575378418s
Currency | Creation date check for WarSampo took 0.3979039192199707s
Currency | Modification date check for WarSampo took 0.4045524597167969s
Rep.Conc. | URIs length for WarSampo took 97.576007604599s
Interoperability | New vocabularies check for WarSampo took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.2126626968383789s
Accuracy | Check Functional Property for WarSampo took 0.21344423294067383s
Accuracy | Check Inverse Functional Property for WarSampo took 0.17974448204040527s
Accuracy | Check Empty annotation labels for WarSampo took 60.044190406799316s
Accuracy | Check White space in annotation for WarSampo took 2.274045944213867s
Accuracy | Check Datatype consistency for WarSampo took 5.4197070598602295s
Consistency | Disjoint class check for WarSampo took 0.21775364875793457s
Consistency | Check Misplaced properties for WarSampo took 20.444013357162476s
Consistency | Check Ontology hijacking for WarSampo took 64.95845866203308s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.4454843997955322s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.6927525997161865s
Conciseness | Check Extensional conciseness for WarSampo took 2.8414649963378906s
Conciseness | Check Intensional conciseness for WarSampo took 0.31014084815979004s
Security | Sign check for WarSampo took 0.18372297286987305s
Availability | Check URIs Dereferenciability for WarSampo took 3.4345240592956543s
Completeness | Calculation of interlinking completeness for WarSampo took 1.4749274253845215s
Reputation | Calculation of the PageRank for WarSampo took 0.020943164825439453s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0008554458618164062s
Interlinking | Calculation of Clustering coefficient for WarSampo took 9.393692016601562e-05s
Interoperability | Check the re-using of existing vocabs for WarSampo took 1.1920928955078125e-06s
Believability | Calculation of trust value for WarSampo took 8.344650268554688e-06s
INFO | --- Analysis for warsampo took 1283.051503419876s
Availability | SPARQL endpoint availability check for WebIsALOD took 7.610933780670166s
Availability | VoID file availability check for WebIsALOD took 0.0006012916564941406s
Extra | Recovery of all triples for WebIsALOD took 2.8502635955810547s
Performance | Total latancy measurement for WebIsALOD took 1.1398100852966309s
Amount of data | Number of triples check for WebIsALOD took 45.864360332489014s
Interoperability | New terms check for WebIsALOD took 41.966888427734375s
Versatility | Languages check for WebIsALOD took 65.80050849914551s
Interpretability | Number of blank nodes check for WebIsALOD took 0.24072957038879395s
Security | Check HTTPS for WebIsALOD took 0.16518688201904297s
Interpretability | RDF structures check for WebIsALOD took 0.4379689693450928s
Versatility | Serialization formats check for WebIsALOD took 0.2496938705444336s
Availability | RDF dump link check for WebIsALOD took 1.7801730632781982s
License | MR license check for WebIsALOD took 0.29419422149658203s
License | HR license check for WebIsALOD took 28.032659769058228s
Amount of data | Number of property check for WebIsALOD took 0.43828678131103516s
Understandability | Number of label check for WebIsALOD took 0.7656052112579346s
Understandability | URI regex check for WebIsALOD took 31.958654165267944s
Understandability | Vocabs check for WebIsALOD took 0.3222846984863281s
Verifiability | Authors check for WebIsALOD took 28.617223978042603s
Verifiability | Publishers check for WebIsALOD took 3.533623695373535s
Performance | Throughput check for WebIsALOD took 10.635828971862793s
Amount of data | Check the number of entities for WebIsALOD took 7.2479248046875e-05s
Verifiability | Contribs. check for WebIsALOD took 0.2746236324310303s
Interlinking | sameAs chians check for WebIsALOD took 0.31563425064086914s
Interlinking | skos check for WebIsALOD took 0.26662755012512207s
Interlinking | skos check for WebIsALOD took 0.20621609687805176s
Timeliness | dataset update frequency check for WebIsALOD took 0.21984529495239258s
Currency | Creation date check for WebIsALOD took 0.5090291500091553s
Currency | Modification date check for WebIsALOD took 0.5159010887145996s
Rep.Conc. | URIs length for WebIsALOD took 105.83768796920776s
Interoperability | New vocabularies check for WebIsALOD took 4.084934711456299s
Consistency | Deprecated classes/propertiers check for WebIsALOD took 0.22915291786193848s
Accuracy | Check Functional Property for WebIsALOD took 0.3041064739227295s
Accuracy | Check Inverse Functional Property for WebIsALOD took 0.27365565299987793s
Accuracy | Check Empty annotation labels for WebIsALOD took 0.6693353652954102s
Accuracy | Check White space in annotation for WebIsALOD took 0.03024458885192871s
Accuracy | Check Datatype consistency for WebIsALOD took 0.027932405471801758s
Consistency | Disjoint class check for WebIsALOD took 0.27169060707092285s
Consistency | Check Misplaced properties for WebIsALOD took 62.37071776390076s
Consistency | Misplaced classes for WebIsALOD took 0.3883218765258789s
Consistency | Check Ontology hijacking for WebIsALOD took 2.4353885650634766s
Consistency | Check Invalid usage of undefined classes for WebIsALOD took 1.8803870677947998s
Consistency | Check Invalid usage of undefined properties for WebIsALOD took 63.57398343086243s
Conciseness | Check Extensional conciseness for WebIsALOD took 0.031104564666748047s
Conciseness | Check Intensional conciseness for WebIsALOD took 0.27582430839538574s
Security | Sign check for WebIsALOD took 0.2516465187072754s
Availability | Check URIs Dereferenciability for WebIsALOD took 10.698380708694458s
Completeness | Calculation of interlinking completeness for WebIsALOD took 1.3329627513885498s
Reputation | Calculation of the PageRank for WebIsALOD took 0.020527124404907227s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 8.177757263183594e-05s
Interoperability | Check the re-using of existing vocabs for WebIsALOD took 2.9511663913726807s
Believability | Calculation of trust value for WebIsALOD took 8.344650268554688e-06s
INFO | --- Analysis for webisalod took 800.8316595554352s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 4.410743713378906e-05s
Availability | VoID file availability check for webnmasunotraveler took 0.0012235641479492188s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.2512848377227783s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.02021932601928711s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 3.4809112548828125e-05s
Believability | Calculation of trust value for webnmasunotraveler took 8.106231689453125e-06s
INFO | --- Analysis for webnmasunotraveler took 7.067543029785156s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 7.700920104980469e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.6977357864379883s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.021323204040527344s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0009527206420898438s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 8.106231689453125e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 7.152557373046875e-06s
INFO | --- Analysis for wikilinks-rdf-nif took 3.3569095134735107s
Availability | SPARQL endpoint availability check for WikiPathways took 4.172325134277344e-05s
Availability | VoID file availability check for WikiPathways took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.2682363986968994s
Reputation | Calculation of the PageRank for WikiPathways took 0.02029585838317871s
Interlinking | Calculation of Degree of Connection for WikiPathways took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for WikiPathways took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 2.8133392333984375e-05s
Believability | Calculation of trust value for WikiPathways took 7.62939453125e-06s
INFO | --- Analysis for wikipathways took 3.8147177696228027s
Availability | SPARQL endpoint availability check for WikiWord Thesaurus Data took 8.96453857421875e-05s
Availability | VoID file availability check for WikiWord Thesaurus Data took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for WikiWord Thesaurus Data took 0.2822856903076172s
Reputation | Calculation of the PageRank for WikiWord Thesaurus Data took 0.02121424674987793s
Interlinking | Calculation of Degree of Connection for WikiWord Thesaurus Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for WikiWord Thesaurus Data took 0.0008759498596191406s
Interlinking | Calculation of Clustering coefficient for WikiWord Thesaurus Data took 3.552436828613281e-05s
Believability | Calculation of trust value for WikiWord Thesaurus Data took 7.867813110351562e-06s
INFO | --- Analysis for wikiword_thesaurus took 3.0089752674102783s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 0.2864065170288086s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.0008528232574462891s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.33921313285827637s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.02024078369140625s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 9.059906005859375e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 7.62939453125e-06s
INFO | --- Analysis for wiktionary-dbpedia-org took 14.43467116355896s
Availability | SPARQL endpoint availability check for Wings workflow provenance dataset took 5.7220458984375e-05s
Availability | VoID file availability check for Wings workflow provenance dataset took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for Wings workflow provenance dataset took 0.26883578300476074s
Reputation | Calculation of the PageRank for Wings workflow provenance dataset took 0.020566701889038086s
Interlinking | Calculation of Degree of Connection for Wings workflow provenance dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Wings workflow provenance dataset took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Wings workflow provenance dataset took 2.86102294921875e-05s
Believability | Calculation of trust value for Wings workflow provenance dataset took 7.867813110351562e-06s
INFO | --- Analysis for wings-workflow-provenance-dataset took 3.437547445297241s
Availability | SPARQL endpoint availability check for World Loanword Database took 0.14923095703125s
Availability | VoID file availability check for World Loanword Database took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.2689802646636963s
Reputation | Calculation of the PageRank for World Loanword Database took 0.02018260955810547s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 7.2479248046875e-05s
Believability | Calculation of trust value for World Loanword Database took 1.6927719116210938e-05s
INFO | --- Analysis for wold took 3.085354804992676s
Availability | SPARQL endpoint availability check for Wordnet took 4.1961669921875e-05s
Availability | VoID file availability check for Wordnet took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Wordnet took 0.25608038902282715s
Reputation | Calculation of the PageRank for Wordnet took 0.020222902297973633s
Interlinking | Calculation of Degree of Connection for Wordnet took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Wordnet took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Wordnet took 3.62396240234375e-05s
Believability | Calculation of trust value for Wordnet took 7.62939453125e-06s
INFO | --- Analysis for wordnet took 2.935378074645996s
Availability | SPARQL endpoint availability check for WordNet-RDF took 4.291534423828125e-05s
Availability | VoID file availability check for WordNet-RDF took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.2785000801086426s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.02247023582458496s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0010535717010498047s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 0.00010085105895996094s
Believability | Calculation of trust value for WordNet-RDF took 7.867813110351562e-06s
INFO | --- Analysis for wordnet-rdf took 2.529428482055664s
Availability | SPARQL endpoint availability check for wordpress took 4.4345855712890625e-05s
Availability | VoID file availability check for wordpress took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for wordpress took 0.27048420906066895s
Reputation | Calculation of the PageRank for wordpress took 0.02028489112854004s
Interlinking | Calculation of Degree of Connection for wordpress took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for wordpress took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for wordpress took 8.249282836914062e-05s
Believability | Calculation of trust value for wordpress took 7.3909759521484375e-06s
INFO | --- Analysis for wordpress took 2.894131660461426s
Availability | SPARQL endpoint availability check for wordpress.post took 4.100799560546875e-05s
Availability | VoID file availability check for wordpress.post took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for wordpress.post took 0.26343584060668945s
Reputation | Calculation of the PageRank for wordpress.post took 0.020857572555541992s
Interlinking | Calculation of Degree of Connection for wordpress.post took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for wordpress.post took 0.0011687278747558594s
Interlinking | Calculation of Clustering coefficient for wordpress.post took 4.00543212890625e-05s
Believability | Calculation of trust value for wordpress.post took 1.049041748046875e-05s
INFO | --- Analysis for wordpress_post took 2.895867347717285s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 1.1253159046173096s
Availability | VoID file availability check for World Bank Linked Data took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.2515144348144531s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.020134449005126953s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.00012493133544921875s
Believability | Calculation of trust value for World Bank Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for world-bank-linked-data took 3.5663692951202393s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 0.9071779251098633s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.2815248966217041s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.02012467384338379s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 8.225440979003906e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 7.3909759521484375e-06s
INFO | --- Analysis for world-factbook-fu-berlin took 5.354067802429199s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 4.291534423828125e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.0003941059112548828s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.23389196395874023s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.020655155181884766s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 8.702278137207031e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 5.9604644775390625e-06s
INFO | --- Analysis for world-wide-web-foundation took 5.4334495067596436s
Availability | SPARQL endpoint availability check for WikiPathways took 4.076957702636719e-05s
Availability | VoID file availability check for WikiPathways took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.24330925941467285s
Reputation | Calculation of the PageRank for WikiPathways took 0.020217180252075195s
Interlinking | Calculation of Degree of Connection for WikiPathways took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for WikiPathways took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 2.956390380859375e-05s
Believability | Calculation of trust value for WikiPathways took 8.821487426757812e-06s
INFO | --- Analysis for wp took 2.8714451789855957s
Availability | SPARQL endpoint availability check for wunderground.weatherreport took 8.749961853027344e-05s
Availability | VoID file availability check for wunderground.weatherreport took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for wunderground.weatherreport took 0.26156187057495117s
Reputation | Calculation of the PageRank for wunderground.weatherreport took 0.0209963321685791s
Interlinking | Calculation of Degree of Connection for wunderground.weatherreport took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for wunderground.weatherreport took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for wunderground.weatherreport took 2.8848648071289062e-05s
Believability | Calculation of trust value for wunderground.weatherreport took 8.344650268554688e-06s
INFO | --- Analysis for wunderground_weatherreport took 2.9849252700805664s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.2997579574584961s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0005850791931152344s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 17.66298007965088s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.8623502254486084s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.2428290843963623s
Interoperability | New terms check for World War 1 as Linked Open Data took 2.596123218536377s
Versatility | Languages check for World War 1 as Linked Open Data took 0.3693540096282959s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.2227334976196289s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.4266352653503418s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.9807307720184326s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.29088807106018066s
Availability | RDF dump link check for World War 1 as Linked Open Data took 5.333206653594971s
License | MR license check for World War 1 as Linked Open Data took 0.19455218315124512s
License | HR license check for World War 1 as Linked Open Data took 1.6501233577728271s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.20041203498840332s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.27677273750305176s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.3606135845184326s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.24343657493591309s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.19067788124084473s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.19816040992736816s
Performance | Throughput check for World War 1 as Linked Open Data took 11.044198989868164s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.06670379638671875s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.19998669624328613s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.6887862682342529s
Interlinking | skos check for World War 1 as Linked Open Data took 0.19193148612976074s
Interlinking | skos check for World War 1 as Linked Open Data took 0.1609351634979248s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.17957639694213867s
Currency | Creation date check for World War 1 as Linked Open Data took 0.3715476989746094s
Currency | Modification date check for World War 1 as Linked Open Data took 0.1871354579925537s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 3.6395912170410156s
Interoperability | New vocabularies check for World War 1 as Linked Open Data took 6.356600999832153s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.2037792205810547s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.19610929489135742s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.16397404670715332s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.95463228225708s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.05100417137145996s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.318636417388916s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.19546818733215332s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.6178655624389648s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 2.3708882331848145s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.3304054737091064s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.5914535522460938s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.19354486465454102s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 0.9612088203430176s
Security | Sign check for World War 1 as Linked Open Data took 0.24731731414794922s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 1621.3712196350098s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 1.756974220275879s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.02149653434753418s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 2.574920654296875e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 0.00011324882507324219s
Interoperability | Check the re-using of existing vocabs for World War 1 as Linked Open Data took 7.435451030731201s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 8.344650268554688e-06s
INFO | --- Analysis for ww1lod took 1730.5322849750519s
Availability | SPARQL endpoint availability check for XlendiAmphorae took 4.172325134277344e-05s
Availability | VoID file availability check for XlendiAmphorae took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for XlendiAmphorae took 0.6986379623413086s
Reputation | Calculation of the PageRank for XlendiAmphorae took 0.020411014556884766s
Interlinking | Calculation of Degree of Connection for XlendiAmphorae took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for XlendiAmphorae took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for XlendiAmphorae took 3.1948089599609375e-05s
Believability | Calculation of trust value for XlendiAmphorae took 8.106231689453125e-06s
INFO | --- Analysis for xlendiamphorae took 4.835978984832764s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 0.3080596923828125s
Availability | VoID file availability check for xLiD-Lexica took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.26602649688720703s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.020208120346069336s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 6.890296936035156e-05s
Believability | Calculation of trust value for xLiD-Lexica took 1.7881393432617188e-05s
INFO | --- Analysis for xlid-lexica took 3.9351561069488525s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 4.363059997558594e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.27840542793273926s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.020399808883666992s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 3.8623809814453125e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 7.62939453125e-06s
INFO | --- Analysis for xwn took 2.6073787212371826s
Availability | SPARQL endpoint availability check for YAGO took 5.078315734863281e-05s
Availability | VoID file availability check for YAGO took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for YAGO took 0.2736544609069824s
Reputation | Calculation of the PageRank for YAGO took 0.020174026489257812s
Interlinking | Calculation of Degree of Connection for YAGO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for YAGO took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.0001323223114013672s
Believability | Calculation of trust value for YAGO took 6.67572021484375e-06s
INFO | --- Analysis for yago took 4.456468105316162s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 1.7429871559143066s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.0007593631744384766s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.7137570381164551s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.02001333236694336s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 7.724761962890625e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 6.9141387939453125e-06s
INFO | --- Analysis for yahoo_geoplanet took 11.672124147415161s
Availability | SPARQL endpoint availability check for Yale Senselab took 0.20755743980407715s
Availability | VoID file availability check for Yale Senselab took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.2735428810119629s
Reputation | Calculation of the PageRank for Yale Senselab took 0.02034926414489746s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Yale Senselab took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 3.0279159545898438e-05s
Believability | Calculation of trust value for Yale Senselab took 6.9141387939453125e-06s
INFO | --- Analysis for yale_senselab took 11.800601243972778s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 1.0670866966247559s
Availability | VoID file availability check for Yovisto - academic video search took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.27547621726989746s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.020831584930419922s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 6.914138793945312e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 5.4836273193359375e-06s
INFO | --- Analysis for yovisto took 27.45441961288452s
Availability | SPARQL endpoint availability check for Yleinen suomalainen asiasanasto - YSA took 4.363059997558594e-05s
Availability | VoID file availability check for Yleinen suomalainen asiasanasto - YSA took 0.0008096694946289062s
Completeness | Calculation of interlinking completeness for Yleinen suomalainen asiasanasto - YSA took 0.2655656337738037s
Reputation | Calculation of the PageRank for Yleinen suomalainen asiasanasto - YSA took 0.02025437355041504s
Interlinking | Calculation of Degree of Connection for Yleinen suomalainen asiasanasto - YSA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Yleinen suomalainen asiasanasto - YSA took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Yleinen suomalainen asiasanasto - YSA took 3.314018249511719e-05s
Believability | Calculation of trust value for Yleinen suomalainen asiasanasto - YSA took 7.62939453125e-06s
INFO | --- Analysis for ysa took 5.042234420776367s
Availability | SPARQL endpoint availability check for yso-fi-allars took 5.555152893066406e-05s
Availability | VoID file availability check for yso-fi-allars took 0.0007023811340332031s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.29220151901245117s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.020306825637817383s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.314018249511719e-05s
Believability | Calculation of trust value for yso-fi-allars took 8.106231689453125e-06s
INFO | --- Analysis for yso-fi-allars took 3.691372871398926s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 4.3392181396484375e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.0007417201995849609s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.2544097900390625s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.020277023315429688s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 3.266334533691406e-05s
Believability | Calculation of trust value for yso-fi-ysa took 7.62939453125e-06s
INFO | --- Analysis for yso-fi-ysa took 7.37199330329895s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 4.267692565917969e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.0008716583251953125s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.2676241397857666s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.020376205444335938s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 3.528594970703125e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 6.4373016357421875e-06s
INFO | --- Analysis for zaragoza-datosabiertos took 6.668446779251099s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 4.3392181396484375e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.2674691677093506s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.02041912078857422s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.2901763916015625e-05s
Believability | Calculation of trust value for zaragoza_turruta took 7.3909759521484375e-06s
INFO | --- Analysis for zaragoza_turruta took 2.6358742713928223s
Availability | SPARQL endpoint availability check for ZBW Labs took 4.291534423828125e-05s
Availability | VoID file availability check for ZBW Labs took 0.0006344318389892578s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.24996328353881836s
Reputation | Calculation of the PageRank for ZBW Labs took 0.02066969871520996s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0008668899536132812s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 7.271766662597656e-05s
Believability | Calculation of trust value for ZBW Labs took 1.33514404296875e-05s
INFO | --- Analysis for zbw-labs took 3.350222110748291s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.16406583786010742s
Availability | VoID file availability check for 20th Century Press Archives took 0.0006079673767089844s
Extra | Recovery of all triples for 20th Century Press Archives took 77.15592360496521s
Performance | Total latancy measurement for 20th Century Press Archives took 0.793677568435669s
Amount of data | Number of triples check for 20th Century Press Archives took 0.9183766841888428s
Interoperability | New terms check for 20th Century Press Archives took 1.6220219135284424s
Versatility | Languages check for 20th Century Press Archives took 2.936290979385376s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 0.735734224319458s
Interpretability | RDF structures check for 20th Century Press Archives took 0.1604313850402832s
Versatility | Serialization formats check for 20th Century Press Archives took 0.14179158210754395s
Availability | RDF dump link check for 20th Century Press Archives took 0.15175175666809082s
License | MR license check for 20th Century Press Archives took 0.18558335304260254s
License | HR license check for 20th Century Press Archives took 4.912062406539917s
Amount of data | Number of property check for 20th Century Press Archives took 0.1315150260925293s
Understandability | Number of label check for 20th Century Press Archives took 0.443544864654541s
Understandability | URI regex check for 20th Century Press Archives took 0.2626488208770752s
Understandability | Vocabs check for 20th Century Press Archives took 0.17766571044921875s
Verifiability | Authors check for 20th Century Press Archives took 0.16479969024658203s
Verifiability | Publishers check for 20th Century Press Archives took 0.16440653800964355s
Performance | Throughput check for 20th Century Press Archives took 10.847070455551147s
Amount of data | Check the number of entities for 20th Century Press Archives took 6.937980651855469e-05s
Verifiability | Contribs. check for 20th Century Press Archives took 0.1308286190032959s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.14245939254760742s
Interlinking | skos check for 20th Century Press Archives took 0.17138433456420898s
Interlinking | skos check for 20th Century Press Archives took 0.20341086387634277s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.13950300216674805s
Currency | Creation date check for 20th Century Press Archives took 0.2563638687133789s
Currency | Modification date check for 20th Century Press Archives took 0.29790353775024414s
Rep.Conc. | URIs length for 20th Century Press Archives took 21.87105679512024s
Interoperability | New vocabularies check for 20th Century Press Archives took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.1497664451599121s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.15084266662597656s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.15552091598510742s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 10.203835248947144s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.8905131816864014s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.215698719024658s
Consistency | Disjoint class check for 20th Century Press Archives took 0.17106270790100098s
Consistency | Check Misplaced properties for 20th Century Press Archives took 2.154174327850342s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 3.594590187072754s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 7.718888521194458s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 3.317016363143921s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.77359676361084s
Security | Sign check for 20th Century Press Archives took 0.1569669246673584s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 1060.1095943450928s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 0.3662726879119873s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.022522687911987305s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 2.86102294921875e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.00010609626770019531s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 3.5762786865234375e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 6.9141387939453125e-06s
INFO | --- Analysis for zbw-pressemappe20 took 1242.4346539974213s
Availability | SPARQL endpoint availability check for zhishi.lemon took 4.315376281738281e-05s
Availability | VoID file availability check for zhishi.lemon took 0.0006532669067382812s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.7298283576965332s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.025435447692871094s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 4.673004150390625e-05s
Believability | Calculation of trust value for zhishi.lemon took 1.2636184692382812e-05s
INFO | --- Analysis for zhishi-lemon took 25.887217044830322s
Availability | SPARQL endpoint availability check for Zhishi.me took 1.6179919242858887s
Availability | VoID file availability check for Zhishi.me took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.2570188045501709s
Reputation | Calculation of the PageRank for Zhishi.me took 0.02003955841064453s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 6.985664367675781e-05s
Believability | Calculation of trust value for Zhishi.me took 7.3909759521484375e-06s
INFO | --- Analysis for zhishi-me took 6.0843305587768555s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 4.220008850097656e-05s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.6963541507720947s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.020305395126342773s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0007832050323486328s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 5.841255187988281e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 7.152557373046875e-06s
INFO | --- Analysis for zitgist-musicbrainz took 3.8340795040130615s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.3518941402435303s
Availability | VoID file availability check for performing-arts.ch took 0.0002415180206298828s
Extra | Recovery of all triples for performing-arts.ch took 90.79428005218506s
Performance | Total latancy measurement for performing-arts.ch took 0.7609646320343018s
Amount of data | Number of triples check for performing-arts.ch took 32.56943368911743s
Interoperability | New terms check for performing-arts.ch took 1.4691243171691895s
Versatility | Languages check for performing-arts.ch took 60.14633083343506s
Interpretability | Number of blank nodes check for performing-arts.ch took 60.12905287742615s
Interpretability | RDF structures check for performing-arts.ch took 0.7826416492462158s
Versatility | Serialization formats check for performing-arts.ch took 0.17535734176635742s
Availability | RDF dump link check for performing-arts.ch took 0.16625213623046875s
License | MR license check for performing-arts.ch took 0.1723644733428955s
License | HR license check for performing-arts.ch took 44.15522217750549s
Amount of data | Number of property check for performing-arts.ch took 0.17973899841308594s
Understandability | Number of label check for performing-arts.ch took 4.748373746871948s
Understandability | URI regex check for performing-arts.ch took 0.3270914554595947s
Understandability | Vocabs check for performing-arts.ch took 0.1624746322631836s
Verifiability | Authors check for performing-arts.ch took 0.1504836082458496s
Verifiability | Publishers check for performing-arts.ch took 0.16662907600402832s
Performance | Throughput check for performing-arts.ch took 10.728142499923706s
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.17741703987121582s
Interlinking | sameAs chians check for performing-arts.ch took 0.7047171592712402s
Interlinking | skos check for performing-arts.ch took 0.16040682792663574s
Interlinking | skos check for performing-arts.ch took 0.17134809494018555s
Timeliness | dataset update frequency check for performing-arts.ch took 0.17440462112426758s
Currency | Creation date check for performing-arts.ch took 0.32079505920410156s
Currency | Modification date check for performing-arts.ch took 0.37058448791503906s
Rep.Conc. | URIs length for performing-arts.ch took 46.31309366226196s
Interoperability | New vocabularies check for performing-arts.ch took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.1564342975616455s
Accuracy | Check Functional Property for performing-arts.ch took 0.14859437942504883s
Accuracy | Check Inverse Functional Property for performing-arts.ch took 0.17940044403076172s
Accuracy | Check Empty annotation labels for performing-arts.ch took 42.82976675033569s
Accuracy | Check White space in annotation for performing-arts.ch took 2.5508244037628174s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.809094429016113s
Consistency | Disjoint class check for performing-arts.ch took 0.1701807975769043s
Consistency | Check Misplaced properties for performing-arts.ch took 0.3681049346923828s
Consistency | Misplaced classes for performing-arts.ch took 8.56171464920044s
Consistency | Check Ontology hijacking for performing-arts.ch took 51.11233878135681s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 17347.03020119667s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 1.8927040100097656s
Conciseness | Check Extensional conciseness for performing-arts.ch took 2.9166502952575684s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.30250120162963867s
Security | Sign check for performing-arts.ch took 0.17621731758117676s
Availability | Check URIs Dereferenciability for performing-arts.ch took 3.4570109844207764s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 0.7187628746032715s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.02160358428955078s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.0009429454803466797s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 1.621246337890625e-05s
Interoperability | Check the re-using of existing vocabs for performing-arts.ch took 2.1457672119140625e-06s
Believability | Calculation of trust value for performing-arts.ch took 8.106231689453125e-06s
INFO | --- Analysis for performing-arts.ch took 18216.40038394928s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 2.739168643951416s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.2815589904785156s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.02033376693725586s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.2636184692382812e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 8.58306884765625e-06s
INFO | --- Analysis for The-AA-Thesaurus took 11.70944857597351s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.5170927047729492s
Availability | VoID file availability check for MiMoTextBase took 0.0007240772247314453s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.25351572036743164s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.02049541473388672s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.8596649169921875e-05s
Believability | Calculation of trust value for MiMoTextBase took 8.58306884765625e-06s
INFO | --- Analysis for MiMoTextBase took 7.024112701416016s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.49752354621887207s
Availability | VoID file availability check for National Library of Sweden took 0.0006878376007080078s
Extra | Recovery of all triples for National Library of Sweden took 15.013018369674683s
Performance | Total latancy measurement for National Library of Sweden took 1.0710792541503906s
Amount of data | Number of triples check for National Library of Sweden took 20.47988533973694s
Interoperability | New terms check for National Library of Sweden took 14.706762313842773s
Versatility | Languages check for National Library of Sweden took 0.21376347541809082s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.2258367538452s
Interpretability | RDF structures check for National Library of Sweden took 0.2135639190673828s
Versatility | Serialization formats check for National Library of Sweden took 0.23767542839050293s
Availability | RDF dump link check for National Library of Sweden took 0.21509051322937012s
License | MR license check for National Library of Sweden took 0.2222909927368164s
License | HR license check for National Library of Sweden took 0.22391057014465332s
Amount of data | Number of property check for National Library of Sweden took 0.22574567794799805s
Understandability | Number of label check for National Library of Sweden took 0.26476550102233887s
Understandability | URI regex check for National Library of Sweden took 0.48247718811035156s
Understandability | Vocabs check for National Library of Sweden took 0.22556591033935547s
Verifiability | Authors check for National Library of Sweden took 0.2297523021697998s
Verifiability | Publishers check for National Library of Sweden took 0.2686800956726074s
Performance | Throughput check for National Library of Sweden took 10.938556671142578s
Amount of data | Check the number of entities for National Library of Sweden took 0.00012564659118652344s
Verifiability | Contribs. check for National Library of Sweden took 0.21266722679138184s
Interlinking | sameAs chians check for National Library of Sweden took 0.2350907325744629s
Interlinking | skos check for National Library of Sweden took 0.24482274055480957s
Interlinking | skos check for National Library of Sweden took 0.21538686752319336s
Timeliness | dataset update frequency check for National Library of Sweden took 0.21430087089538574s
Currency | Creation date check for National Library of Sweden took 0.41573357582092285s
Currency | Modification date check for National Library of Sweden took 0.4417741298675537s
Rep.Conc. | URIs length for National Library of Sweden took 83.3779125213623s
Interoperability | New vocabularies check for National Library of Sweden took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.20430684089660645s
Accuracy | Check Functional Property for National Library of Sweden took 0.22367024421691895s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.22723674774169922s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.27539539337158203s
Consistency | Disjoint class check for National Library of Sweden took 0.20244193077087402s
Consistency | Check Misplaced properties for National Library of Sweden took 61.000988721847534s
Consistency | Misplaced classes for National Library of Sweden took 1.1695539951324463s
Consistency | Check Ontology hijacking for National Library of Sweden took 6.365912914276123s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.3042595386505127s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 62.1559522151947s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.28287434577941895s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.36230015754699707s
Security | Sign check for National Library of Sweden took 0.2814023494720459s
Availability | Check URIs Dereferenciability for National Library of Sweden took 9.595935106277466s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 0.8003804683685303s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.020637035369873047s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 2.5987625122070312e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 1.4781951904296875e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Library of Sweden took 7.867813110351562e-06s
INFO | --- Analysis for NLS took 1380.9538207054138s
Availability | SPARQL endpoint availability check for Japan Search took 1.4040639400482178s
Availability | VoID file availability check for Japan Search took 0.00029587745666503906s
Extra | Recovery of all triples for Japan Search took 3.201493740081787s
Performance | Total latancy measurement for Japan Search took 1.4147837162017822s
Amount of data | Number of triples check for Japan Search took 4.892362117767334s
Interoperability | New terms check for Japan Search took 3.310573101043701s
Versatility | Languages check for Japan Search took 0.301668643951416s
Interpretability | Number of blank nodes check for Japan Search took 13.528593301773071s
Interpretability | RDF structures check for Japan Search took 0.40213584899902344s
Versatility | Serialization formats check for Japan Search took 0.3995065689086914s
Availability | RDF dump link check for Japan Search took 0.32505249977111816s
License | MR license check for Japan Search took 0.7152018547058105s
License | HR license check for Japan Search took 12.058323621749878s
Amount of data | Number of property check for Japan Search took 0.28910255432128906s
Understandability | Number of label check for Japan Search took 2.93198823928833s
Understandability | URI regex check for Japan Search took 0.5796239376068115s
Understandability | Vocabs check for Japan Search took 0.3111715316772461s
Verifiability | Authors check for Japan Search took 0.32517123222351074s
Verifiability | Publishers check for Japan Search took 0.3205852508544922s
Performance | Throughput check for Japan Search took 11.41050386428833s
Amount of data | Check the number of entities for Japan Search took 6.937980651855469e-05s
Verifiability | Contribs. check for Japan Search took 0.3173081874847412s
Interlinking | sameAs chians check for Japan Search took 0.3164832592010498s
Interlinking | skos check for Japan Search took 0.45145201683044434s
Interlinking | skos check for Japan Search took 0.2722663879394531s
Timeliness | dataset update frequency check for Japan Search took 0.31558752059936523s
Currency | Creation date check for Japan Search took 0.6629540920257568s
Currency | Modification date check for Japan Search took 0.6418781280517578s
Rep.Conc. | URIs length for Japan Search took 15.003981590270996s
Interoperability | New vocabularies check for Japan Search took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.30626916885375977s
Accuracy | Check Empty annotation labels for Japan Search took 0.47631263732910156s
Accuracy | Check White space in annotation for Japan Search took 0.03185915946960449s
Accuracy | Check Datatype consistency for Japan Search took 0.029127836227416992s
Consistency | Disjoint class check for Japan Search took 0.32966136932373047s
Consistency | Check Misplaced properties for Japan Search took 11.72397780418396s
Consistency | Misplaced classes for Japan Search took 0.35727620124816895s
Consistency | Check Ontology hijacking for Japan Search took 1.8776826858520508s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.3176789283752441s
Consistency | Check Invalid usage of undefined properties for Japan Search took 12.975374698638916s
Conciseness | Check Extensional conciseness for Japan Search took 0.03530287742614746s
Conciseness | Check Intensional conciseness for Japan Search took 0.32910799980163574s
Security | Sign check for Japan Search took 0.2687695026397705s
Availability | Check URIs Dereferenciability for Japan Search took 9.001603364944458s
Completeness | Calculation of interlinking completeness for Japan Search took 1.3397297859191895s
Reputation | Calculation of the PageRank for Japan Search took 0.025618553161621094s
Interlinking | Calculation of Degree of Connection for Japan Search took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0008254051208496094s
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.430511474609375e-06s
Believability | Calculation of trust value for Japan Search took 8.106231689453125e-06s
INFO | --- Analysis for Japan-Search took 389.5048990249634s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 1.1602561473846436s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.2717552185058594s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.2159347534179688e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 7.62939453125e-06s
INFO | --- Analysis for Rijksmuseum took 5.910106897354126s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 0.5340137481689453s
Availability | VoID file availability check for Finnish Public Libraries took 0.0006532669067382812s
Extra | Recovery of all triples for Finnish Public Libraries took 34.81699228286743s
Performance | Total latancy measurement for Finnish Public Libraries took 2.2215375900268555s
Amount of data | Number of triples check for Finnish Public Libraries took 60.41393446922302s
Interoperability | New terms check for Finnish Public Libraries took 17.236300468444824s
Versatility | Languages check for Finnish Public Libraries took 60.12379264831543s
Interpretability | Number of blank nodes check for Finnish Public Libraries took 60.199525117874146s
Interpretability | RDF structures check for Finnish Public Libraries took 0.26053476333618164s
Versatility | Serialization formats check for Finnish Public Libraries took 0.13741469383239746s
Availability | RDF dump link check for Finnish Public Libraries took 0.872694730758667s
License | MR license check for Finnish Public Libraries took 0.2828967571258545s
License | HR license check for Finnish Public Libraries took 48.75991725921631s
Amount of data | Number of property check for Finnish Public Libraries took 0.27304768562316895s
Understandability | Number of label check for Finnish Public Libraries took 15.862967491149902s
Understandability | URI regex check for Finnish Public Libraries took 0.7621572017669678s
Understandability | Vocabs check for Finnish Public Libraries took 0.13164567947387695s
Verifiability | Authors check for Finnish Public Libraries took 0.20593762397766113s
Verifiability | Publishers check for Finnish Public Libraries took 0.1168062686920166s
Performance | Throughput check for Finnish Public Libraries took 11.069680213928223s
Amount of data | Check the number of entities for Finnish Public Libraries took 7.295608520507812e-05s
Verifiability | Contribs. check for Finnish Public Libraries took 0.12476277351379395s
Interlinking | sameAs chians check for Finnish Public Libraries took 7.060088396072388s
Interlinking | skos check for Finnish Public Libraries took 0.26973891258239746s
Interlinking | skos check for Finnish Public Libraries took 0.2906825542449951s
Timeliness | dataset update frequency check for Finnish Public Libraries took 0.30556511878967285s
Currency | Creation date check for Finnish Public Libraries took 0.25948190689086914s
Currency | Modification date check for Finnish Public Libraries took 0.43317437171936035s
Rep.Conc. | URIs length for Finnish Public Libraries took 99.64687371253967s
Interoperability | New vocabularies check for Finnish Public Libraries took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for Finnish Public Libraries took 0.357525110244751s
Accuracy | Check Empty annotation labels for Finnish Public Libraries took 15.95804476737976s
Accuracy | Check White space in annotation for Finnish Public Libraries took 2.214236259460449s
Accuracy | Check Datatype consistency for Finnish Public Libraries took 4.379955530166626s
Consistency | Disjoint class check for Finnish Public Libraries took 0.19815707206726074s
Consistency | Check Misplaced properties for Finnish Public Libraries took 60.6051025390625s
Consistency | Check Ontology hijacking for Finnish Public Libraries took 17.791988611221313s
Consistency | Check Invalid usage of undefined classes for Finnish Public Libraries took 1.5774526596069336s
Consistency | Check Invalid usage of undefined properties for Finnish Public Libraries took 61.75694990158081s
Conciseness | Check Extensional conciseness for Finnish Public Libraries took 2.735717296600342s
Security | Sign check for Finnish Public Libraries took 0.715064287185669s
Availability | Check URIs Dereferenciability for Finnish Public Libraries took 1.9583532810211182s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 0.45081639289855957s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.02477121353149414s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 2.09808349609375e-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.821487426757812e-06s
INFO | --- Analysis for FI-Library took 833.6389226913452s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 31.49882435798645s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.2776048183441162s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.02091836929321289s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 1.3113021850585938e-05s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 8.106231689453125e-06s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 65.95258283615112s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.3599915504455566s
Availability | VoID file availability check for National Library Netherlands took 0.0005974769592285156s
Extra | Recovery of all triples for National Library Netherlands took 1.2300729751586914s
Performance | Total latancy measurement for National Library Netherlands took 0.7242491245269775s
Amount of data | Number of triples check for National Library Netherlands took 0.15136432647705078s
Interoperability | New terms check for National Library Netherlands took 1.3980751037597656s
Versatility | Languages check for National Library Netherlands took 58.13246464729309s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.15839743614196777s
Interpretability | RDF structures check for National Library Netherlands took 0.14712190628051758s
Versatility | Serialization formats check for National Library Netherlands took 0.1537008285522461s
Availability | RDF dump link check for National Library Netherlands took 0.13654303550720215s
License | MR license check for National Library Netherlands took 0.144683837890625s
License | HR license check for National Library Netherlands took 0.19826269149780273s
Amount of data | Number of property check for National Library Netherlands took 0.15248990058898926s
Understandability | Number of label check for National Library Netherlands took 0.14674067497253418s
Understandability | URI regex check for National Library Netherlands took 0.3089268207550049s
Understandability | Vocabs check for National Library Netherlands took 0.1295173168182373s
Verifiability | Authors check for National Library Netherlands took 0.1512148380279541s
Verifiability | Publishers check for National Library Netherlands took 0.17412924766540527s
Performance | Throughput check for National Library Netherlands took 10.54916787147522s
Amount of data | Check the number of entities for National Library Netherlands took 8.320808410644531e-05s
Verifiability | Contribs. check for National Library Netherlands took 0.12789034843444824s
Interlinking | sameAs chians check for National Library Netherlands took 0.15287423133850098s
Interlinking | skos check for National Library Netherlands took 0.15322303771972656s
Interlinking | skos check for National Library Netherlands took 0.1522834300994873s
Timeliness | dataset update frequency check for National Library Netherlands took 0.13640427589416504s
Currency | Creation date check for National Library Netherlands took 0.27198076248168945s
Currency | Modification date check for National Library Netherlands took 0.28266024589538574s
Rep.Conc. | URIs length for National Library Netherlands took 0.6499645709991455s
Interoperability | New vocabularies check for National Library Netherlands took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 0.16163229942321777s
Accuracy | Check Functional Property for National Library Netherlands took 0.1338367462158203s
Accuracy | Check Inverse Functional Property for National Library Netherlands took 0.16224455833435059s
Accuracy | Check Empty annotation labels for National Library Netherlands took 0.39896559715270996s
Accuracy | Check White space in annotation for National Library Netherlands took 0.025078773498535156s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.028187036514282227s
Consistency | Disjoint class check for National Library Netherlands took 0.16658949851989746s
Consistency | Check Misplaced properties for National Library Netherlands took 0.2711985111236572s
Consistency | Check Ontology hijacking for National Library Netherlands took 1.8234968185424805s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 2.1179749965667725s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.4558799266815186s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.03433346748352051s
Security | Sign check for National Library Netherlands took 0.15139102935791016s
Availability | Check URIs Dereferenciability for National Library Netherlands took 2.025615692138672s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 0.7992699146270752s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.020503997802734375s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 4.1961669921875e-05s
Interoperability | Check the re-using of existing vocabs for National Library Netherlands took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Library Netherlands took 8.344650268554688e-06s
INFO | --- Analysis for National-Library-Netherlands took 169.57402396202087s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.7262325286865234s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.28302597999572754s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0201873779296875s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007288455963134766s
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 7.867813110351562e-06s
INFO | --- Analysis for Antique-Renaissance took 6.647695064544678s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 4.061082601547241s
Availability | VoID file availability check for ARTSDATA.CA took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.23725557327270508s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.020292997360229492s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.2874603271484375e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 1.0967254638671875e-05s
INFO | --- Analysis for ARTSDATA-CA took 10.087847232818604s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.22966289520263672s
Availability | VoID file availability check for Architecture of Knowledge took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.2686166763305664s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.020438671112060547s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.1920928955078125e-05s
Believability | Calculation of trust value for Architecture of Knowledge took 8.344650268554688e-06s
INFO | --- Analysis for ArCo took 3.4915871620178223s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.3857860565185547s
Availability | VoID file availability check for ConfermentSampo took 0.00027251243591308594s
Extra | Recovery of all triples for ConfermentSampo took 166.3144826889038s
Performance | Total latancy measurement for ConfermentSampo took 0.8688390254974365s
Amount of data | Number of triples check for ConfermentSampo took 8.630263566970825s
Interoperability | New terms check for ConfermentSampo took 2.5827577114105225s
Versatility | Languages check for ConfermentSampo took 27.35801911354065s
Interpretability | Number of blank nodes check for ConfermentSampo took 8.10995864868164s
Security | Check HTTPS for ConfermentSampo took 0.44736576080322266s
Interpretability | RDF structures check for ConfermentSampo took 0.21921038627624512s
Versatility | Serialization formats check for ConfermentSampo took 0.21649646759033203s
Availability | RDF dump link check for ConfermentSampo took 3.180164337158203s
License | MR license check for ConfermentSampo took 0.21229910850524902s
License | HR license check for ConfermentSampo took 0.26013970375061035s
Amount of data | Number of property check for ConfermentSampo took 0.19662261009216309s
Understandability | Number of label check for ConfermentSampo took 5.989515542984009s
Understandability | URI regex check for ConfermentSampo took 0.386702299118042s
Understandability | Vocabs check for ConfermentSampo took 0.17331528663635254s
Verifiability | Authors check for ConfermentSampo took 0.19614434242248535s
Verifiability | Publishers check for ConfermentSampo took 0.1955735683441162s
Performance | Throughput check for ConfermentSampo took 10.680737972259521s
Amount of data | Check the number of entities for ConfermentSampo took 3.9616382122039795s
Verifiability | Contribs. check for ConfermentSampo took 0.18003559112548828s
Interlinking | sameAs chians check for ConfermentSampo took 0.4699544906616211s
Interlinking | skos check for ConfermentSampo took 0.17670774459838867s
Interlinking | skos check for ConfermentSampo took 0.1628730297088623s
Timeliness | dataset update frequency check for ConfermentSampo took 0.17589712142944336s
Currency | Creation date check for ConfermentSampo took 0.37412524223327637s
Currency | Modification date check for ConfermentSampo took 0.37237024307250977s
Rep.Conc. | URIs length for ConfermentSampo took 94.12748312950134s
Interoperability | New vocabularies check for ConfermentSampo took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.2001640796661377s
Accuracy | Check Functional Property for ConfermentSampo took 0.19921207427978516s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.1721649169921875s
Accuracy | Check Empty annotation labels for ConfermentSampo took 54.119802474975586s
Accuracy | Check White space in annotation for ConfermentSampo took 3.012815475463867s
Accuracy | Check Datatype consistency for ConfermentSampo took 5.267832040786743s
Consistency | Disjoint class check for ConfermentSampo took 0.18397116661071777s
Consistency | Check Misplaced properties for ConfermentSampo took 7.154292583465576s
Consistency | Check Ontology hijacking for ConfermentSampo took 64.08392763137817s
Consistency | Check Invalid usage of undefined classes for ConfermentSampo took 1.4621295928955078s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.5628643035888672s
Conciseness | Check Extensional conciseness for ConfermentSampo took 2.82753849029541s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.20312738418579102s
Security | Sign check for ConfermentSampo took 0.18294405937194824s
Availability | Check URIs Dereferenciability for ConfermentSampo took 1425.0622005462646s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 0.7543346881866455s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.022296428680419922s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 2.1457672119140625e-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 2026.0691769123077s
Availability | SPARQL endpoint availability check for Museum Finland took 0.48752689361572266s
Availability | VoID file availability check for Museum Finland took 0.0002720355987548828s
Extra | Recovery of all triples for Museum Finland took 45.51564145088196s
Performance | Total latancy measurement for Museum Finland took 0.8753364086151123s
Amount of data | Number of triples check for Museum Finland took 0.35343003273010254s
Interoperability | New terms check for Museum Finland took 2.2047312259674072s
Versatility | Languages check for Museum Finland took 0.6775872707366943s
Interpretability | Number of blank nodes check for Museum Finland took 0.32634592056274414s
Security | Check HTTPS for Museum Finland took 0.4343726634979248s
Interpretability | RDF structures check for Museum Finland took 0.7846975326538086s
Versatility | Serialization formats check for Museum Finland took 0.19090580940246582s
Availability | RDF dump link check for Museum Finland took 0.16330504417419434s
License | MR license check for Museum Finland took 0.1660606861114502s
License | HR license check for Museum Finland took 0.3533346652984619s
Amount of data | Number of property check for Museum Finland took 0.20035243034362793s
Understandability | Number of label check for Museum Finland took 0.46997642517089844s
Understandability | URI regex check for Museum Finland took 0.34163355827331543s
Understandability | Vocabs check for Museum Finland took 0.1723313331604004s
Verifiability | Authors check for Museum Finland took 0.17015695571899414s
Verifiability | Publishers check for Museum Finland took 0.16462445259094238s
Performance | Throughput check for Museum Finland took 11.08951210975647s
Amount of data | Check the number of entities for Museum Finland took 0.00011873245239257812s
Verifiability | Contribs. check for Museum Finland took 0.16475749015808105s
Interlinking | sameAs chians check for Museum Finland took 0.16300344467163086s
Interlinking | skos check for Museum Finland took 0.17814850807189941s
Interlinking | skos check for Museum Finland took 0.1671285629272461s
Timeliness | dataset update frequency check for Museum Finland took 0.17618417739868164s
Currency | Creation date check for Museum Finland took 0.37116432189941406s
Currency | Modification date check for Museum Finland took 0.34480929374694824s
Rep.Conc. | URIs length for Museum Finland took 3.5933334827423096s
Interoperability | New vocabularies check for Museum Finland took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.20042014122009277s
Accuracy | Check Functional Property for Museum Finland took 0.17454004287719727s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.17767119407653809s
Accuracy | Check Empty annotation labels for Museum Finland took 1.0766777992248535s
Accuracy | Check White space in annotation for Museum Finland took 0.06179976463317871s
Accuracy | Check Datatype consistency for Museum Finland took 0.9654281139373779s
Consistency | Disjoint class check for Museum Finland took 0.16582942008972168s
Consistency | Check Misplaced properties for Museum Finland took 0.6436822414398193s
Consistency | Check Ontology hijacking for Museum Finland took 2.370164632797241s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.5886383056640625s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 1.8046071529388428s
Conciseness | Check Extensional conciseness for Museum Finland took 0.677731990814209s
Conciseness | Check Intensional conciseness for Museum Finland took 0.7100632190704346s
Security | Sign check for Museum Finland took 0.1704716682434082s
Availability | Check URIs Dereferenciability for Museum Finland took 13.959701299667358s
Completeness | Calculation of interlinking completeness for Museum Finland took 0.25988197326660156s
Reputation | Calculation of the PageRank for Museum Finland took 0.02065753936767578s
Interlinking | Calculation of Degree of Connection for Museum Finland took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 1.1920928955078125e-05s
Interoperability | Check the re-using of existing vocabs for Museum Finland took 1.9073486328125e-06s
Believability | Calculation of trust value for Museum Finland took 8.821487426757812e-06s
INFO | --- Analysis for FI-Museum took 114.74419951438904s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.1814868450164795s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0006957054138183594s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 16.716018676757812s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.8164966106414795s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 33.552878618240356s
Interoperability | New terms check for Mapping Manuscript Migrations took 5.9672088623046875s
Versatility | Languages check for Mapping Manuscript Migrations took 82.21569657325745s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 32.61659598350525s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.25768136978149414s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.1649765968322754s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.16580915451049805s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.16282010078430176s
License | MR license check for Mapping Manuscript Migrations took 0.20205450057983398s
License | HR license check for Mapping Manuscript Migrations took 1.6716697216033936s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.1575303077697754s
Understandability | Number of label check for Mapping Manuscript Migrations took 59.521491289138794s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.3723418712615967s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.1741025447845459s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.19006061553955078s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.20185184478759766s
Performance | Throughput check for Mapping Manuscript Migrations took 11.09425973892212s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 1.0672030448913574s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.19654417037963867s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 5.398966073989868s
Interlinking | skos check for Mapping Manuscript Migrations took 0.17103934288024902s
Interlinking | skos check for Mapping Manuscript Migrations took 0.1676628589630127s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.17187905311584473s
Currency | Creation date check for Mapping Manuscript Migrations took 0.3738417625427246s
Currency | Modification date check for Mapping Manuscript Migrations took 0.18933439254760742s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 52.412907123565674s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.21849584579467773s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.2012951374053955s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.17293190956115723s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 10.804782390594482s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.464270830154419s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.813516139984131s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.18682312965393066s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 24.647005081176758s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 17.946480751037598s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.636871099472046s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.642183780670166s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.912865161895752s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.19034409523010254s
Security | Sign check for Mapping Manuscript Migrations took 0.17110991477966309s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 1656.703101158142s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 0.9656100273132324s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.020786285400390625s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 2.8371810913085938e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 2.2649765014648438e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 1.6689300537109375e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 8.821487426757812e-06s
INFO | --- Analysis for MMM took 2146.6465570926666s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.35198187828063965s
Availability | VoID file availability check for Semantic Kalevala took 0.0002739429473876953s
Extra | Recovery of all triples for Semantic Kalevala took 10.131714344024658s
Performance | Total latancy measurement for Semantic Kalevala took 0.8356564044952393s
Amount of data | Number of triples check for Semantic Kalevala took 0.4237179756164551s
Interoperability | New terms check for Semantic Kalevala took 2.990687131881714s
Versatility | Languages check for Semantic Kalevala took 1.1591806411743164s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.3805394172668457s
Security | Check HTTPS for Semantic Kalevala took 0.42063069343566895s
Interpretability | RDF structures check for Semantic Kalevala took 0.20766544342041016s
Versatility | Serialization formats check for Semantic Kalevala took 0.18747782707214355s
Availability | RDF dump link check for Semantic Kalevala took 0.1671741008758545s
License | MR license check for Semantic Kalevala took 0.16741704940795898s
License | HR license check for Semantic Kalevala took 1.0002524852752686s
Amount of data | Number of property check for Semantic Kalevala took 0.19882607460021973s
Understandability | Number of label check for Semantic Kalevala took 0.3158605098724365s
Understandability | URI regex check for Semantic Kalevala took 0.3373682498931885s
Understandability | Vocabs check for Semantic Kalevala took 0.16929411888122559s
Verifiability | Authors check for Semantic Kalevala took 0.17092251777648926s
Verifiability | Publishers check for Semantic Kalevala took 0.1710975170135498s
Performance | Throughput check for Semantic Kalevala took 11.340193271636963s
Amount of data | Check the number of entities for Semantic Kalevala took 5.984306335449219e-05s
Verifiability | Contribs. check for Semantic Kalevala took 0.17721962928771973s
Interlinking | sameAs chians check for Semantic Kalevala took 0.19301939010620117s
Interlinking | skos check for Semantic Kalevala took 0.298994779586792s
Interlinking | skos check for Semantic Kalevala took 0.1671595573425293s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.16199851036071777s
Currency | Creation date check for Semantic Kalevala took 0.3414466381072998s
Currency | Modification date check for Semantic Kalevala took 0.35201239585876465s
Rep.Conc. | URIs length for Semantic Kalevala took 4.975181341171265s
Interoperability | New vocabularies check for Semantic Kalevala took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.1856851577758789s
Accuracy | Check Functional Property for Semantic Kalevala took 0.19553112983703613s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.17789626121520996s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 2.00260591506958s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.29924964904785156s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.396216869354248s
Consistency | Disjoint class check for Semantic Kalevala took 0.15662193298339844s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.8093745708465576s
Consistency | Check Ontology hijacking for Semantic Kalevala took 2.3532323837280273s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.4564905166625977s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.6439557075500488s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.8956325054168701s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.33986902236938477s
Security | Sign check for Semantic Kalevala took 0.16962981224060059s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 4193.500131607056s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 0.7132487297058105s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.020588159561157227s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.239776611328125e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 1.6689300537109375e-06s
Believability | Calculation of trust value for Semantic Kalevala took 7.3909759521484375e-06s
INFO | --- Analysis for Semantic-Kalevala took 4262.638108491898s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 0.9198150634765625s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.0007259845733642578s
Extra | Recovery of all triples for Smithsonian American Art Museum took 277.5752389431s
Performance | Total latancy measurement for Smithsonian American Art Museum took 3.038161039352417s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.5819664001464844s
Interoperability | New terms check for Smithsonian American Art Museum took 3.2124156951904297s
Versatility | Languages check for Smithsonian American Art Museum took 40.84097647666931s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.5995962619781494s
Security | Check HTTPS for Smithsonian American Art Museum took 0.38414430618286133s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.6509931087493896s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.6170873641967773s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.6033306121826172s
License | MR license check for Smithsonian American Art Museum took 0.6024532318115234s
License | HR license check for Smithsonian American Art Museum took 16.826239109039307s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.5986719131469727s
Understandability | Number of label check for Smithsonian American Art Museum took 0.6032140254974365s
Understandability | URI regex check for Smithsonian American Art Museum took 1.235511064529419s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.6209795475006104s
Verifiability | Authors check for Smithsonian American Art Museum took 0.6090514659881592s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.609126091003418s
Performance | Throughput check for Smithsonian American Art Museum took 11.948600769042969s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 7.414817810058594e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.5993285179138184s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.5783593654632568s
Interlinking | skos check for Smithsonian American Art Museum took 0.5929374694824219s
Interlinking | skos check for Smithsonian American Art Museum took 0.5844569206237793s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.593052864074707s
Currency | Creation date check for Smithsonian American Art Museum took 1.228602647781372s
Currency | Modification date check for Smithsonian American Art Museum took 1.204293966293335s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 111.27930355072021s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.6110472679138184s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 26.38390350341797s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.5052366256713867s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.3935534954071045s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.6123907566070557s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 6.8116984367370605s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 102.27451133728027s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.6042563915252686s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 5.146507024765015s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.900848388671875s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.6612379550933838s
Security | Sign check for Smithsonian American Art Museum took 0.6006605625152588s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.4828200340271s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 0.9687027931213379s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.02106189727783203s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.8358230590820312e-05s
Interoperability | Check the re-using of existing vocabs for Smithsonian American Art Museum took 2.6226043701171875e-06s
Believability | Calculation of trust value for Smithsonian American Art Museum took 8.58306884765625e-06s
INFO | --- Analysis for Smithsonian took 731.7367136478424s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.2081317901611328s
Availability | VoID file availability check for Zeri Photo Archive took 0.0006606578826904297s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.2982828617095947s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.021342039108276367s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.4781951904296875e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 7.867813110351562e-06s
INFO | --- Analysis for Zeri-Photo-Archive took 6.949475526809692s
Availability | SPARQL endpoint availability check for Archives Hub took 21.531912326812744s
Availability | VoID file availability check for Archives Hub took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.2587451934814453s
Reputation | Calculation of the PageRank for Archives Hub took 0.020595073699951172s
Interlinking | Calculation of Degree of Connection for Archives Hub took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.2159347534179688e-05s
Believability | Calculation of trust value for Archives Hub took 7.3909759521484375e-06s
INFO | --- Analysis for Archives-Hub took 55.97520470619202s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.5330359935760498s
Availability | VoID file availability check for Yale centre of British Art took 0.00038051605224609375s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.2783236503601074s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.02063775062561035s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.33514404296875e-05s
Believability | Calculation of trust value for Yale centre of British Art took 7.152557373046875e-06s
INFO | --- Analysis for Yale took 5.3690102100372314s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 261.4428563117981s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.00029349327087402344s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.24561429023742676s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.020901918411254883s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 1.2159347534179688e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 7.152557373046875e-06s
INFO | --- Analysis for ADL took 536.4230802059174s
Availability | SPARQL endpoint availability check for MusicKG took 5.157350301742554s
Availability | VoID file availability check for MusicKG took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for MusicKG took 0.2578449249267578s
Reputation | Calculation of the PageRank for MusicKG took 0.020802974700927734s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.2636184692382812e-05s
Believability | Calculation of trust value for MusicKG took 9.298324584960938e-06s
INFO | --- Analysis for MusicKG took 9.016754150390625s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 0.8233687877655029s
Availability | VoID file availability check for CIDOC-CRM took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.28625965118408203s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.02059483528137207s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.1920928955078125e-05s
Believability | Calculation of trust value for CIDOC-CRM took 7.3909759521484375e-06s
INFO | --- Analysis for CIDOC-CRM took 5.327313661575317s
Availability | SPARQL endpoint availability check for Mondis took 0.43962883949279785s
Availability | VoID file availability check for Mondis took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for Mondis took 0.2823643684387207s
Reputation | Calculation of the PageRank for Mondis took 0.02060675621032715s
Interlinking | Calculation of Degree of Connection for Mondis took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.1444091796875e-05s
Believability | Calculation of trust value for Mondis took 7.3909759521484375e-06s
INFO | --- Analysis for Mondis took 3.437227249145508s
Availability | SPARQL endpoint availability check for DigitalNZ took 3.3242740631103516s
Availability | VoID file availability check for DigitalNZ took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.30268311500549316s
Reputation | Calculation of the PageRank for DigitalNZ took 0.02038264274597168s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.1444091796875e-05s
Believability | Calculation of trust value for DigitalNZ took 7.3909759521484375e-06s
INFO | --- Analysis for DigitalNZ took 7.236173152923584s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.18167781829833984s
Availability | VoID file availability check for Fondazione Zeri took 0.001134634017944336s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.2745213508605957s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.02071094512939453s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.000850677490234375s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.2874603271484375e-05s
Believability | Calculation of trust value for Fondazione Zeri took 7.152557373046875e-06s
INFO | --- Analysis for Fondazione-Zeri took 4.304065942764282s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 1.0394303798675537s
Availability | VoID file availability check for Digital Public Library of America took 0.0004088878631591797s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.25371265411376953s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.021219491958618164s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.1920928955078125e-05s
Believability | Calculation of trust value for Digital Public Library of America took 7.3909759521484375e-06s
INFO | --- Analysis for Library-of-America took 4.730488300323486s
Availability | SPARQL endpoint availability check for Auckland Museum took 1.12361478805542s
Availability | VoID file availability check for Auckland Museum took 0.0007081031799316406s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.29524707794189453s
Reputation | Calculation of the PageRank for Auckland Museum took 0.02083420753479004s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.3113021850585938e-05s
Believability | Calculation of trust value for Auckland Museum took 8.58306884765625e-06s
INFO | --- Analysis for Auckland-Museum took 5.718615531921387s
Availability | SPARQL endpoint availability check for National Library of Spain took 5.632927417755127s
Availability | VoID file availability check for National Library of Spain took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.2565193176269531s
Reputation | Calculation of the PageRank for National Library of Spain took 0.020476341247558594s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 1.0728836059570312e-05s
Believability | Calculation of trust value for National Library of Spain took 7.62939453125e-06s
INFO | --- Analysis for BNE took 8.6199369430542s
Availability | SPARQL endpoint availability check for National Library of Korea took 2.4195029735565186s
Availability | VoID file availability check for National Library of Korea took 0.0003306865692138672s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.2569448947906494s
Reputation | Calculation of the PageRank for National Library of Korea took 0.020502567291259766s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.239776611328125e-05s
Believability | Calculation of trust value for National Library of Korea took 7.152557373046875e-06s
INFO | --- Analysis for Korea-Library took 5.411441087722778s
Availability | SPARQL endpoint availability check for The State Russian Museum took 2.413856029510498s
Availability | VoID file availability check for The State Russian Museum took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.23987603187561035s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.020475387573242188s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 1.1444091796875e-05s
Believability | Calculation of trust value for The State Russian Museum took 8.106231689453125e-06s
INFO | --- Analysis for Russian-Museum took 5.782699346542358s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.664086103439331s
Availability | VoID file availability check for National Library of Scotland took 0.0006699562072753906s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.286649227142334s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.02173328399658203s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for National Library of Scotland took 1.33514404296875e-05s
Believability | Calculation of trust value for National Library of Scotland took 6.9141387939453125e-06s
INFO | --- Analysis for National-Library-of-Scotland took 6.987057685852051s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 0.3586752414703369s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.2698237895965576s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.020237207412719727s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.2874603271484375e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 8.344650268554688e-06s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 3.3920443058013916s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.18519926071166992s
Availability | VoID file availability check for OntoComedySources took 0.0007326602935791016s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.2929954528808594s
Reputation | Calculation of the PageRank for OntoComedySources took 0.02062058448791504s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.33514404296875e-05s
Believability | Calculation of trust value for OntoComedySources took 8.106231689453125e-06s
INFO | --- Analysis for OntoComedySources took 4.16333532333374s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.19703006744384766s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0006628036499023438s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.2645399570465088s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.020407676696777344s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.2874603271484375e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 8.821487426757812e-06s
INFO | --- Analysis for OntoCeramic-2.0 took 4.5969557762146s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.1361842155456543s
Availability | VoID file availability check for SaintGall Ontology took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.2525510787963867s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.021311521530151367s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.2159347534179688e-05s
Believability | Calculation of trust value for SaintGall Ontology took 8.106231689453125e-06s
INFO | --- Analysis for SaintGall-Ontology took 3.1356582641601562s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.7846417427062988s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.0005893707275390625s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.25932860374450684s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.020637035369873047s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.2636184692382812e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 7.867813110351562e-06s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 3.829122304916382s
Availability | SPARQL endpoint availability check for ICON took 0.33835458755493164s
Availability | VoID file availability check for ICON took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for ICON took 0.2833857536315918s
Reputation | Calculation of the PageRank for ICON took 0.020345211029052734s
Interlinking | Calculation of Degree of Connection for ICON took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for ICON took 0.0008025169372558594s
Interlinking | Calculation of Clustering coefficient for ICON took 1.2159347534179688e-05s
Believability | Calculation of trust value for ICON took 7.152557373046875e-06s
INFO | --- Analysis for ICON took 4.185344219207764s
Availability | SPARQL endpoint availability check for Polifonia took 0.26706528663635254s
Availability | VoID file availability check for Polifonia took 0.0005800724029541016s
Completeness | Calculation of interlinking completeness for Polifonia took 0.2528691291809082s
Reputation | Calculation of the PageRank for Polifonia took 0.020735502243041992s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.2636184692382812e-05s
Believability | Calculation of trust value for Polifonia took 8.58306884765625e-06s
INFO | --- Analysis for Polifonia took 4.300386190414429s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 0.2643461227416992s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.2557356357574463s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.020740032196044922s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.0008084774017333984s
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 7.152557373046875e-06s
INFO | --- Analysis for Atlas-of-Paths took 3.821815252304077s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.2125701904296875s
Availability | VoID file availability check for Music Note Ontology took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.2808549404144287s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.2874603271484375e-05s
Believability | Calculation of trust value for Music Note Ontology took 7.62939453125e-06s
INFO | --- Analysis for Music-Note-Ontology took 8.906397342681885s
Availability | SPARQL endpoint availability check for HaMSE took 0.19561529159545898s
Availability | VoID file availability check for HaMSE took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for HaMSE took 0.26743650436401367s
Reputation | Calculation of the PageRank for HaMSE took 0.020656347274780273s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.1920928955078125e-05s
Believability | Calculation of trust value for HaMSE took 1.0728836059570312e-05s
INFO | --- Analysis for HaMSE took 5.77316689491272s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.10532569885253906s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0003190040588378906s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.24180197715759277s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.020259857177734375s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.1444091796875e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 6.67572021484375e-06s
INFO | --- Analysis for FOod took 3.3073389530181885s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 0.7335672378540039s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.27484631538391113s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.020752906799316406s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.000762939453125s
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 7.3909759521484375e-06s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 5.082886457443237s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 1.7227542400360107s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.000576019287109375s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.27933788299560547s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.020467042922973633s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.1444091796875e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 7.62939453125e-06s
INFO | --- Analysis for ARIADNE took 5.788005352020264s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.4430537223815918s
Availability | VoID file availability check for Nomisma.org  took 0.0006339550018310547s
Extra | Recovery of all triples for Nomisma.org  took 884.666930437088s
Performance | Total latancy measurement for Nomisma.org  took 1.7003247737884521s
Amount of data | Number of triples check for Nomisma.org  took 39.45235753059387s
Interoperability | New terms check for Nomisma.org  took 8.933977365493774s
Versatility | Languages check for Nomisma.org  took 106.42299556732178s
Interpretability | Number of blank nodes check for Nomisma.org  took 34.1541588306427s
Security | Check HTTPS for Nomisma.org  took 0.7988977432250977s
Interpretability | RDF structures check for Nomisma.org  took 0.34533143043518066s
Versatility | Serialization formats check for Nomisma.org  took 0.3662757873535156s
Availability | RDF dump link check for Nomisma.org  took 889.5638246536255s
License | MR license check for Nomisma.org  took 0.39731788635253906s
License | HR license check for Nomisma.org  took 60.57470631599426s
Amount of data | Number of property check for Nomisma.org  took 0.3823885917663574s
Understandability | Number of label check for Nomisma.org  took 6.980525255203247s
Understandability | URI regex check for Nomisma.org  took 0.680525541305542s
Understandability | Vocabs check for Nomisma.org  took 0.32172703742980957s
Verifiability | Authors check for Nomisma.org  took 0.32756638526916504s
Verifiability | Publishers check for Nomisma.org  took 0.4141271114349365s
Performance | Throughput check for Nomisma.org  took 12.272925615310669s
Amount of data | Check the number of entities for Nomisma.org  took 63.86092734336853s
Verifiability | Contribs. check for Nomisma.org  took 10.079468011856079s
Interlinking | sameAs chians check for Nomisma.org  took 9.999945640563965s
Interlinking | skos check for Nomisma.org  took 10.004528999328613s
Interlinking | skos check for Nomisma.org  took 10.09248685836792s
Timeliness | dataset update frequency check for Nomisma.org  took 10.00893259048462s
Currency | Creation date check for Nomisma.org  took 20.098166942596436s
Currency | Modification date check for Nomisma.org  took 20.19284749031067s
Rep.Conc. | URIs length for Nomisma.org  took 23.400960445404053s
Interoperability | New vocabularies check for Nomisma.org  took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 109.21528744697571s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 22.150469064712524s
Accuracy | Check Empty annotation labels for Nomisma.org  took 279.20293831825256s
Accuracy | Check White space in annotation for Nomisma.org  took 2.8324294090270996s
Accuracy | Check Datatype consistency for Nomisma.org  took 5.574318885803223s
Consistency | Disjoint class check for Nomisma.org  took 3.749711275100708s
Consistency | Check Ontology hijacking for Nomisma.org  took 0.1336817741394043s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 1.4109470844268799s
Conciseness | Check Extensional conciseness for Nomisma.org  took 2.842068910598755s
Conciseness | Check Intensional conciseness for Nomisma.org  took 4.186850309371948s
Security | Sign check for Nomisma.org  took 1.203019380569458s
Availability | Check URIs Dereferenciability for Nomisma.org  took 2008.8802027702332s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 1.6572797298431396s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.021613121032714844s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 3.409385681152344e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0009043216705322266s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 5.7220458984375e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 1.9073486328125e-06s
Believability | Calculation of trust value for Nomisma.org  took 7.867813110351562e-06s
INFO | --- Analysis for nomisma_org took 8141.893378973007s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.410743713378906e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0007386207580566406s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.74015212059021s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.02047443389892578s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.34600830078125e-05s
Believability | Calculation of trust value for Discogs in RDF took 8.106231689453125e-06s
INFO | --- Analysis for data-incubator-discogs took 8.185257911682129s
Availability | SPARQL endpoint availability check for Enslaved.org took 5.340576171875e-05s
Availability | VoID file availability check for Enslaved.org took 0.0007121562957763672s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.2725059986114502s
Reputation | Calculation of the PageRank for Enslaved.org took 0.020366191864013672s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 2.765655517578125e-05s
Believability | Calculation of trust value for Enslaved.org took 7.152557373046875e-06s
INFO | --- Analysis for enslaved.org took 5.382727861404419s
Availability | SPARQL endpoint availability check for EventKG took 4.124641418457031e-05s
Availability | VoID file availability check for EventKG took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for EventKG took 0.2783935070037842s
Reputation | Calculation of the PageRank for EventKG took 0.02080392837524414s
Interlinking | Calculation of Degree of Connection for EventKG took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.606910705566406e-05s
Believability | Calculation of trust value for EventKG took 7.152557373046875e-06s
INFO | --- Analysis for eventkg took 6.615298271179199s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.2823629379272461s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0007417201995849609s
Extra | Recovery of all triples for ROCEEH Out of Africa Database (ROAD) took 44.152539014816284s
Performance | Total latancy measurement for ROCEEH Out of Africa Database (ROAD) took 0.42823100090026855s
Amount of data | Number of triples check for ROCEEH Out of Africa Database (ROAD) took 1.7614591121673584s
Interoperability | New terms check for ROCEEH Out of Africa Database (ROAD) took 1.8053605556488037s
Versatility | Languages check for ROCEEH Out of Africa Database (ROAD) took 5.510942697525024s
Interpretability | Number of blank nodes check for ROCEEH Out of Africa Database (ROAD) took 1.3905608654022217s
Interpretability | RDF structures check for ROCEEH Out of Africa Database (ROAD) took 0.08105301856994629s
Versatility | Serialization formats check for ROCEEH Out of Africa Database (ROAD) took 0.08168411254882812s
Availability | RDF dump link check for ROCEEH Out of Africa Database (ROAD) took 0.08506059646606445s
License | MR license check for ROCEEH Out of Africa Database (ROAD) took 0.08626246452331543s
License | HR license check for ROCEEH Out of Africa Database (ROAD) took 0.08761739730834961s
Amount of data | Number of property check for ROCEEH Out of Africa Database (ROAD) took 0.08551859855651855s
Understandability | Number of label check for ROCEEH Out of Africa Database (ROAD) took 0.09701013565063477s
Understandability | URI regex check for ROCEEH Out of Africa Database (ROAD) took 0.16364192962646484s
Understandability | Vocabs check for ROCEEH Out of Africa Database (ROAD) took 0.08607792854309082s
Verifiability | Authors check for ROCEEH Out of Africa Database (ROAD) took 0.08879518508911133s
Verifiability | Publishers check for ROCEEH Out of Africa Database (ROAD) took 0.07906675338745117s
Performance | Throughput check for ROCEEH Out of Africa Database (ROAD) took 10.316508054733276s
Amount of data | Check the number of entities for ROCEEH Out of Africa Database (ROAD) took 8.296966552734375e-05s
Verifiability | Contribs. check for ROCEEH Out of Africa Database (ROAD) took 0.08660316467285156s
Interlinking | sameAs chians check for ROCEEH Out of Africa Database (ROAD) took 0.09445905685424805s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.09434771537780762s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.08772516250610352s
Timeliness | dataset update frequency check for ROCEEH Out of Africa Database (ROAD) took 0.08723759651184082s
Currency | Creation date check for ROCEEH Out of Africa Database (ROAD) took 0.1822500228881836s
Currency | Modification date check for ROCEEH Out of Africa Database (ROAD) took 0.19124770164489746s
Rep.Conc. | URIs length for ROCEEH Out of Africa Database (ROAD) took 20.27219581604004s
Interoperability | New vocabularies check for ROCEEH Out of Africa Database (ROAD) took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for ROCEEH Out of Africa Database (ROAD) took 0.08104181289672852s
Accuracy | Check Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.08556079864501953s
Accuracy | Check Inverse Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.07701325416564941s
Accuracy | Check Datatype consistency for ROCEEH Out of Africa Database (ROAD) took 3.982100486755371s
Consistency | Disjoint class check for ROCEEH Out of Africa Database (ROAD) took 0.09259772300720215s
Consistency | Check Misplaced properties for ROCEEH Out of Africa Database (ROAD) took 3.181305408477783s
Consistency | Check Ontology hijacking for ROCEEH Out of Africa Database (ROAD) took 7.292592525482178s
Consistency | Check Invalid usage of undefined classes for ROCEEH Out of Africa Database (ROAD) took 1.5006470680236816s
Consistency | Check Invalid usage of undefined properties for ROCEEH Out of Africa Database (ROAD) took 4.601783990859985s
Conciseness | Check Extensional conciseness for ROCEEH Out of Africa Database (ROAD) took 3.081646680831909s
Security | Sign check for ROCEEH Out of Africa Database (ROAD) took 0.08622407913208008s
Availability | Check URIs Dereferenciability for ROCEEH Out of Africa Database (ROAD) took 715.8087866306305s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.8783776760101318s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.021149873733520508s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 3.409385681152344e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 8.702278137207031e-05s
Interoperability | Check the re-using of existing vocabs for ROCEEH Out of Africa Database (ROAD) took 4.291534423828125e-06s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 1.0967254638671875e-05s
INFO | --- Analysis for roceeh-road took 848.4323961734772s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.23840761184692383s
Availability | VoID file availability check for Thesaurus BNCF took 0.0005950927734375s
Extra | Recovery of all triples for Thesaurus BNCF took 53.74668598175049s
Performance | Total latancy measurement for Thesaurus BNCF took 0.6183249950408936s
Amount of data | Number of triples check for Thesaurus BNCF took 1.0438401699066162s
Interoperability | New terms check for Thesaurus BNCF took 1.47882080078125s
Versatility | Languages check for Thesaurus BNCF took 9.013892650604248s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 1.3433997631072998s
Security | Check HTTPS for Thesaurus BNCF took 0.09927868843078613s
Interpretability | RDF structures check for Thesaurus BNCF took 0.11369895935058594s
Versatility | Serialization formats check for Thesaurus BNCF took 0.11040973663330078s
Availability | RDF dump link check for Thesaurus BNCF took 0.11319518089294434s
License | MR license check for Thesaurus BNCF took 0.10814285278320312s
License | HR license check for Thesaurus BNCF took 0.25523948669433594s
Amount of data | Number of property check for Thesaurus BNCF took 0.11226868629455566s
Understandability | Number of label check for Thesaurus BNCF took 0.2678678035736084s
Understandability | URI regex check for Thesaurus BNCF took 0.23343539237976074s
Understandability | Vocabs check for Thesaurus BNCF took 0.10525703430175781s
Verifiability | Authors check for Thesaurus BNCF took 0.10594010353088379s
Verifiability | Publishers check for Thesaurus BNCF took 0.11320829391479492s
Performance | Throughput check for Thesaurus BNCF took 10.830956220626831s
Amount of data | Check the number of entities for Thesaurus BNCF took 7.843971252441406e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.11097526550292969s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.11591219902038574s
Interlinking | skos check for Thesaurus BNCF took 0.20645356178283691s
Interlinking | skos check for Thesaurus BNCF took 0.19480371475219727s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.10891008377075195s
Currency | Creation date check for Thesaurus BNCF took 0.21393656730651855s
Currency | Modification date check for Thesaurus BNCF took 0.22440862655639648s
Rep.Conc. | URIs length for Thesaurus BNCF took 27.372340440750122s
Interoperability | New vocabularies check for Thesaurus BNCF took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.11693978309631348s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.13663864135742188s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.11158919334411621s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 13.442945957183838s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.5120820999145508s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.927765130996704s
Consistency | Disjoint class check for Thesaurus BNCF took 0.10682940483093262s
Consistency | Check Misplaced properties for Thesaurus BNCF took 1.2290263175964355s
Consistency | Misplaced classes for Thesaurus BNCF took 6.770792722702026s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 7.967872142791748s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.465871810913086s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.5542023181915283s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.507746458053589s
Security | Sign check for Thesaurus BNCF took 0.10501217842102051s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 21.603026151657104s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.2646939754486084s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.0205078125s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 8.153915405273438e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 1.430511474609375e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 8.821487426757812e-06s
INFO | --- Analysis for bncf-ns took 204.8328173160553s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.5042979717254639s
Availability | VoID file availability check for COURAGE Dataset took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.2727549076080322s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.0201876163482666s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 3.0994415283203125e-05s
Believability | Calculation of trust value for COURAGE Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for http:cultural-opposition.eu took 5.523578405380249s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.4345855712890625e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.2582981586456299s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0202939510345459s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.291534423828125e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for bll-thesaurus took 4.0895774364471436s
Availability | SPARQL endpoint availability check for Inztrow took 4.2438507080078125e-05s
Availability | VoID file availability check for Inztrow took 0.0007197856903076172s
Completeness | Calculation of interlinking completeness for Inztrow took 0.7129402160644531s
Reputation | Calculation of the PageRank for Inztrow took 0.02040386199951172s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Inztrow took 2.8848648071289062e-05s
Believability | Calculation of trust value for Inztrow took 7.152557373046875e-06s
INFO | --- Analysis for Inztrow took 4.513397455215454s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 21.316561460494995s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0007295608520507812s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.3824598789215088s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.020967960357666016s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 5.245208740234375e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 6.9141387939453125e-06s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 175.20172429084778s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.482269287109375e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.29416418075561523s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.02065563201904297s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0008099079132080078s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.337860107421875e-05s
Believability | Calculation of trust value for Temples of the Classical World took 7.3909759521484375e-06s
INFO | --- Analysis for classical_temples took 3.632079601287842s
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 3.4886932373046875s
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.0005776882171630859s
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.2564058303833008s
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.020228147506713867s
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 9.5367431640625e-06s
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.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 7.915496826171875e-05s
Believability | Calculation of trust value for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 12.610774278640747s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.3820996284484863s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.24724268913269043s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.024873018264770508s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.001374959945678711s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.00012373924255371094s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 12.208874464035034s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.4147274494171143s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.00041794776916503906s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.2660655975341797s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.172325134277344e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC-CRB took 15.175495862960815s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.396623373031616s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.26947999000549316s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.02042865753173828s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.131431579589844e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 8.106231689453125e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 12.086754560470581s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.3857829570770264s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006928443908691406s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.2782120704650879s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.020857810974121094s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.695487976074219e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-DQOT took 12.714478254318237s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.394810199737549s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.2834951877593994s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.020354270935058594s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.939338684082031e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC-IHP-WCD took 12.769765138626099s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 5.841099500656128s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.25316643714904785s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.02066826820373535s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007984638214111328s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 9.512901306152344e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 17.69805359840393s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.4059886932373047s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.2561459541320801s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.020699024200439453s
Interlinking | Calculation of Degree of Connection for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.340576171875e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 11.645440816879272s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.4080557823181152s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.000720977783203125s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.2777745723724365s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.02076125144958496s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.435943603515625e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 11.666109323501587s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.445142030715942s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.2687506675720215s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.020784616470336914s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.863739013671875e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 8.106231689453125e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 16.613471746444702s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.4053077697753906s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007140636444091797s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.2917153835296631s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.02037525177001953s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 8.368492126464844e-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.216109275817871s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 2.369169235229492s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006549358367919922s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.28704118728637695s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.02003335952758789s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.891654968261719e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.344650268554688e-06s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 11.731927633285522s
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.4088213443756104s
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.000652313232421875s
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.29513096809387207s
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.020418167114257812s
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.0967254638671875e-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.0007419586181640625s
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.273124694824219e-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.344650268554688e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 12.841991424560547s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.398475408554077s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0006411075592041016s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.2698824405670166s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.02107524871826172s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.9114227294921875e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 8.344650268554688e-06s
INFO | --- Analysis for ASCDC_-_DNB took 11.164684534072876s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.5494043827056885s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.00058746337890625s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 8.154345273971558s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.7366204261779785s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.43596649169921875s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.7858021259307861s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 45.74864435195923s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.36434054374694824s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.23243474960327148s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.5679025650024414s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.3892791271209717s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.3465418815612793s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.4374370574951172s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 20.37507653236389s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.32453227043151855s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.8630416393280029s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.6974773406982422s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.3456752300262451s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.591102123260498s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.41832828521728516s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 12.055608987808228s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 7.009506225585938e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.3195047378540039s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.34059572219848633s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.4895193576812744s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.3839602470397949s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.3598322868347168s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.8560569286346436s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.7187449932098389s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 2.986098289489746s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.3390226364135742s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.5810184478759766s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.5399413108825684s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 0.9940402507781982s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.03354144096374512s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.029653549194335938s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.3980984687805176s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.6178107261657715s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.43628382682800293s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.6299540996551514s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.2773058414459229s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.5010671615600586s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.03225088119506836s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.42847442626953125s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.39727354049682617s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 10074.54451584816s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 1.698373794555664s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.021412372589111328s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 3.266334533691406e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 6.365776062011719e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.6689300537109375e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 8.106231689453125e-06s
INFO | --- Analysis for BVMC took 10315.23017334938s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 393.32287764549255s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0007121562957763672s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.28215575218200684s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.020839691162109375s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 4.363059997558594e-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.3852984905243s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.7672207355499268s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.25348401069641113s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.020601749420166016s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 3.62396240234375e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for LucaniPharsalia took 5.323633670806885s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.42194271087646484s
Availability | VoID file availability check for Querolus in LiLa took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.27173471450805664s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.020572900772094727s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.504753112792969e-05s
Believability | Calculation of trust value for Querolus in LiLa took 7.62939453125e-06s
INFO | --- Analysis for Querolus took 3.7253611087799072s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.4004220962524414s
Availability | VoID file availability check for UDante in LiLa took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.24087858200073242s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.024090051651000977s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 3.886222839355469e-05s
Believability | Calculation of trust value for UDante in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for UDante took 4.1690449714660645s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.45583462715148926s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.00025391578674316406s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.0189580917358398s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.7283046245574951s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2965269088745117s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6842069625854492s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.138694047927856s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15044808387756348s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.46425366401672363s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15417861938476562s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16671371459960938s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.27994394302368164s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2904362678527832s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16599416732788086s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.30077648162841797s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3012223243713379s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1482546329498291s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.21540355682373047s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18111896514892578s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.972652196884155s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.367134094238281e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18382501602172852s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.21331787109375s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4030952453613281s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16008520126342773s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17276310920715332s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.41233110427856445s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.20823884010314941s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.0321106910705566s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.13324189186096191s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.18226122856140137s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.17164182662963867s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.562751293182373s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.03191232681274414s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.028925657272338867s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.199326753616333s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.2444493770599365s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 1.8537566661834717s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.294734001159668s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.4877829551696777s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.028196096420288086s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.17699646949768066s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1679213047027588s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2017.8011713027954s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.958979606628418s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.020920276641845703s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.839897155761719e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.9073486328125e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 7.867813110351562e-06s
INFO | --- Analysis for ceo took 2141.9673326015472s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.5688686370849609s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0006623268127441406s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 89.54456496238708s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.5594778060913086s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.6412627696990967s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.9218227863311768s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.6137068271636963s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.5705335140228271s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.28180575370788574s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.3127570152282715s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 10.506329774856567s
License | MR license check for Cultural Heritage Thesaurus took 0.30274271965026855s
License | HR license check for Cultural Heritage Thesaurus took 0.4224083423614502s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.32146143913269043s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.35329627990722656s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.5386989116668701s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.3159451484680176s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.2989978790283203s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.2647976875305176s
Performance | Throughput check for Cultural Heritage Thesaurus took 12.191996574401855s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 7.581710815429688e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.29428696632385254s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.29338598251342773s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.31206345558166504s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.3109917640686035s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.27558398246765137s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.5609197616577148s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.5892312526702881s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 24.540735960006714s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 1.9563484191894531s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.27573442459106445s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.31324315071105957s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.29173803329467773s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 5.569631814956665s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.22452044486999512s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.2808654308319092s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.0488908290863037s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.29706597328186035s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 6.610318899154663s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.0985639095306396s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00014519691467285156s
Security | Sign check for Cultural Heritage Thesaurus took 0.307387113571167s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 304.05905961990356s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.3277311325073242s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.03713536262512207s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 0.0003895759582519531s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 9.918212890625e-05s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 2.098918914794922s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for cht took 501.4218235015869s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 1.067615270614624s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.2675204277038574s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.02059769630432129s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.915496826171875e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 6.67572021484375e-06s
INFO | --- Analysis for greekchildrensartmuseum took 5.629241466522217s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 4.2438507080078125e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.2735438346862793s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020336151123046875s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.62939453125e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 7.62939453125e-06s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 3.3930792808532715s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 9.228759765625s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.4290168285369873s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.02028489112854004s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.291534423828125e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 6.9141387939453125e-06s
INFO | --- Analysis for ldt@library took 36.66650414466858s
Availability | SPARQL endpoint availability check for Muziekweb took 0.6299469470977783s
Availability | VoID file availability check for Muziekweb took 0.00058746337890625s
Extra | Recovery of all triples for Muziekweb took 1.5065913200378418s
Performance | Total latancy measurement for Muziekweb took 1.372208595275879s
Amount of data | Number of triples check for Muziekweb took 0.37001848220825195s
Interoperability | New terms check for Muziekweb took 1.643049955368042s
Versatility | Languages check for Muziekweb took 52.02968978881836s
Interpretability | Number of blank nodes check for Muziekweb took 0.30536365509033203s
Interpretability | RDF structures check for Muziekweb took 0.7951831817626953s
Versatility | Serialization formats check for Muziekweb took 0.28256726264953613s
Availability | RDF dump link check for Muziekweb took 0.29851222038269043s
License | MR license check for Muziekweb took 0.3133242130279541s
License | HR license check for Muziekweb took 12.044479608535767s
Amount of data | Number of property check for Muziekweb took 0.27567028999328613s
Understandability | Number of label check for Muziekweb took 0.34305381774902344s
Understandability | URI regex check for Muziekweb took 0.5828652381896973s
Understandability | Vocabs check for Muziekweb took 0.2869908809661865s
Verifiability | Authors check for Muziekweb took 0.3264780044555664s
Verifiability | Publishers check for Muziekweb took 0.31655335426330566s
Performance | Throughput check for Muziekweb took 11.453885793685913s
Amount of data | Check the number of entities for Muziekweb took 8.082389831542969e-05s
Verifiability | Contribs. check for Muziekweb took 0.3444838523864746s
Interlinking | sameAs chians check for Muziekweb took 0.30199170112609863s
Interlinking | skos check for Muziekweb took 0.30645251274108887s
Interlinking | skos check for Muziekweb took 0.2917172908782959s
Timeliness | dataset update frequency check for Muziekweb took 0.2939186096191406s
Currency | Creation date check for Muziekweb took 0.9182746410369873s
Currency | Modification date check for Muziekweb took 0.9527022838592529s
Rep.Conc. | URIs length for Muziekweb took 1.746109962463379s
Interoperability | New vocabularies check for Muziekweb took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.30764341354370117s
Accuracy | Check Functional Property for Muziekweb took 0.5761275291442871s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.5594589710235596s
Accuracy | Check Empty annotation labels for Muziekweb took 0.7939229011535645s
Accuracy | Check White space in annotation for Muziekweb took 0.028029441833496094s
Accuracy | Check Datatype consistency for Muziekweb took 0.029817581176757812s
Consistency | Disjoint class check for Muziekweb took 0.525343656539917s
Consistency | Check Misplaced properties for Muziekweb took 1.1350123882293701s
Consistency | Check Ontology hijacking for Muziekweb took 2.06221079826355s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.3417940139770508s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.6229991912841797s
Conciseness | Check Extensional conciseness for Muziekweb took 0.03513669967651367s
Conciseness | Check Intensional conciseness for Muziekweb took 0.31638360023498535s
Security | Sign check for Muziekweb took 0.5212666988372803s
Availability | Check URIs Dereferenciability for Muziekweb took 1784.5207221508026s
Completeness | Calculation of interlinking completeness for Muziekweb took 1.973869800567627s
Reputation | Calculation of the PageRank for Muziekweb took 0.03747153282165527s
Interlinking | Calculation of Degree of Connection for Muziekweb took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 6.365776062011719e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 2.1457672119140625e-06s
Believability | Calculation of trust value for Muziekweb took 7.62939453125e-06s
INFO | --- Analysis for muziekweb took 1912.3495845794678s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 5.765667915344238s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0007050037384033203s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.2779695987701416s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.020235776901245117s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 9.1552734375e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 7.3909759521484375e-06s
INFO | --- Analysis for nom took 22.94042158126831s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.7829537391662598s
Availability | VoID file availability check for Linked Stage Graph took 0.0003809928894042969s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.25510692596435547s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.020181655883789062s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 4.982948303222656e-05s
Believability | Calculation of trust value for Linked Stage Graph took 6.67572021484375e-06s
INFO | --- Analysis for slod took 3.7864990234375s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 0.5783181190490723s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.2655174732208252s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.020262956619262695s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 7.939338684082031e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 7.62939453125e-06s
INFO | --- Analysis for wasabi took 6.000596046447754s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.2499713897705078s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.2926056385040283s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.0206301212310791s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 8.535385131835938e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 8.821487426757812e-06s
INFO | --- Analysis for wl-kg took 4.410401821136475s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 6.794929504394531e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.0007266998291015625s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.25295138359069824s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.020607948303222656s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 5.888938903808594e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 8.106231689453125e-06s
INFO | --- Analysis for yso took 6.186812877655029s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.57763671875e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.27849721908569336s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.02049732208251953s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.1948089599609375e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 8.58306884765625e-06s
INFO | --- Analysis for ISSN:0080-3626 took 2.3818576335906982s
Availability | SPARQL endpoint availability check for Copyright Free Music took 5.888938903808594e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0007104873657226562s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.25876712799072266s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.020605087280273438s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0008485317230224609s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 3.1948089599609375e-05s
Believability | Calculation of trust value for Copyright Free Music took 1.3113021850585938e-05s
INFO | --- Analysis for Copyright_Free_Music took 3.479621648788452s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 4.5299530029296875e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.2730584144592285s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.02035236358642578s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 3.075599670410156e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 7.867813110351562e-06s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.3878157138824463s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 4.220008850097656e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.25566959381103516s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.02030491828918457s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 3.0279159545898438e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 1.33514404296875e-05s
INFO | --- Analysis for Sherry_Wine took 3.0640029907226562s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.2438507080078125e-05s
Availability | VoID file availability check for Sherry Wine took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.2674143314361572s
Reputation | Calculation of the PageRank for Sherry Wine took 0.020333528518676758s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 3.3855438232421875e-05s
Believability | Calculation of trust value for Sherry Wine took 7.152557373046875e-06s
INFO | --- Analysis for Sherry_Wine_ took 2.3981027603149414s
Availability | SPARQL endpoint availability check for Freeyork took 4.220008850097656e-05s
Availability | VoID file availability check for Freeyork took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for Freeyork took 0.2628459930419922s
Reputation | Calculation of the PageRank for Freeyork took 0.0204315185546875s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007479190826416016s
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.3960683345794678s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.57763671875e-05s
Availability | VoID file availability check for Informatics Studies took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.27906131744384766s
Reputation | Calculation of the PageRank for Informatics Studies took 0.02039337158203125s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0008394718170166016s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 2.9325485229492188e-05s
Believability | Calculation of trust value for Informatics Studies took 7.152557373046875e-06s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 2.9545812606811523s
Availability | SPARQL endpoint availability check for MappingChange took 20.44392228126526s
Availability | VoID file availability check for MappingChange took 0.0003237724304199219s
Completeness | Calculation of interlinking completeness for MappingChange took 0.2536180019378662s
Reputation | Calculation of the PageRank for MappingChange took 0.02630615234375s
Interlinking | Calculation of Degree of Connection for MappingChange took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for MappingChange took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for MappingChange took 1.1920928955078125e-05s
Believability | Calculation of trust value for MappingChange took 7.3909759521484375e-06s
INFO | --- Analysis for mappingch took 53.420610666275024s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.4194180965423584s
Availability | VoID file availability check for Odeuropa Ontology took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.24926543235778809s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.020347118377685547s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.1920928955078125e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 7.152557373046875e-06s
INFO | --- Analysis for Odeuropa took 3.7574496269226074s

--- Total time for analysis:275648.0522222519s ---
--- Total time for analysis:76.56890339506997 hours ---