Availability | SPARQL endpoint availability check for Open Data Web took 4.3392181396484375e-05s
Availability | VoID file availability check for Open Data Web took 3.814697265625e-06s
Completeness | Calculation of interlinking completeness for Open Data Web took 3.9667818546295166s
Reputation | Calculation of the PageRank for Open Data Web took 1.5683073997497559s
Interlinking | Calculation of Degree of Connection for Open Data Web took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 0.00023794174194335938s
Believability | Calculation of trust value for Open Data Web took 1.2159347534179688e-05s
INFO | --- Analysis for Open Data Web took 129.24084639549255s
Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 9.465217590332031e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.2641434669494629s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 180.33312582969666s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.042012691497802734s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0005035400390625s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 1.9311904907226562e-05s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 1.9550323486328125e-05s
INFO | --- Analysis for Korespondencja Emila Szramka z Janem Kuderą took 753.315197467804s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 2.248265266418457s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 1.3297865390777588s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.3615117073059082s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.020017385482788086s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0005075931549072266s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 0.00021195411682128906s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 1.1444091796875e-05s
INFO | --- Analysis for 2000 U.S. Census in RDF (rdfabout.com) took 487.4367024898529s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 0.8284835815429688s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.5755970478057861s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.3812425136566162s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.0183408260345459s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0005109310150146484s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 4.792213439941406e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 1.3589859008789062e-05s
INFO | --- Analysis for 2001 Spanish Census to RDF took 311.606591463089s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.267692565917969e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 4.5299530029296875e-06s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 1.5808565616607666s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.017340421676635742s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0005056858062744141s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 1.2636184692382812e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 6.67572021484375e-06s
INFO | --- Analysis for A collection of Papers for LREC2014 and related Workshops took 24.338260173797607s
Availability | SPARQL endpoint availability check for Test took 4.2438507080078125e-05s
Availability | VoID file availability check for Test took 0.34099817276000977s
Completeness | Calculation of interlinking completeness for Test took 0.5084190368652344s
Reputation | Calculation of the PageRank for Test took 0.017708301544189453s
Interlinking | Calculation of Degree of Connection for Test took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Test took 0.0005044937133789062s
Interlinking | Calculation of Clustering coefficient for Test took 1.049041748046875e-05s
Believability | Calculation of trust value for Test took 1.2159347534179688e-05s
INFO | --- Analysis for Test took 3.2359728813171387s
Availability | SPARQL endpoint availability check for my intro took 0.00010466575622558594s
Availability | VoID file availability check for my intro took 5.245208740234375e-06s
Completeness | Calculation of interlinking completeness for my intro took 0.596635103225708s
Reputation | Calculation of the PageRank for my intro took 0.019665956497192383s
Interlinking | Calculation of Degree of Connection for my intro took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for my intro took 0.0005099773406982422s
Interlinking | Calculation of Clustering coefficient for my intro took 1.1682510375976562e-05s
Believability | Calculation of trust value for my intro took 1.1920928955078125e-05s
INFO | --- Analysis for my intro took 3.252840518951416s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.17559266090393066s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 8.821487426757812e-06s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.32406044006347656s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.01750016212463379s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.000537872314453125s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.0001049041748046875s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 1.0728836059570312e-05s
INFO | --- Analysis for Australian Bureau of Statistics (ABS) Linked Data took 2.385286808013916s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 262.2658450603485s
Availability | VoID file availability check for Academic Offer of UNL took 8.106231689453125e-06s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.5974745750427246s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.018537521362304688s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.000537872314453125s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 2.3365020751953125e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 9.298324584960938e-06s
INFO | --- Analysis for Academic Offer of UNL took 397.22504568099976s
Availability | SPARQL endpoint availability check for AcadOnto took 8.7738037109375e-05s
Availability | VoID file availability check for AcadOnto took 4.76837158203125e-06s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.9017705917358398s
Reputation | Calculation of the PageRank for AcadOnto took 0.018219470977783203s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0005147457122802734s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 1.1920928955078125e-05s
Believability | Calculation of trust value for AcadOnto took 1.0967254638671875e-05s
INFO | --- Analysis for AcadOnto took 7.240955591201782s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 14.47243857383728s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 5.152350664138794s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.3913898468017578s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.017937898635864258s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0005190372467041016s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 5.0067901611328125e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.0013580322265625e-05s
INFO | --- Analysis for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 54.79754400253296s
Availability | SPARQL endpoint availability check for Addgene took 8.726119995117188e-05s
Availability | VoID file availability check for Addgene took 1.3498609066009521s
Completeness | Calculation of interlinking completeness for Addgene took 0.30112552642822266s
Reputation | Calculation of the PageRank for Addgene took 0.017756938934326172s
Interlinking | Calculation of Degree of Connection for Addgene took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0005352497100830078s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.695487976074219e-05s
Believability | Calculation of trust value for Addgene took 1.0967254638671875e-05s
INFO | --- Analysis for Addgene took 16.172863245010376s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.38690185546875e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 1.8068840503692627s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.34919118881225586s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.017784833908081055s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0005245208740234375s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.179115295410156e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.33514404296875e-05s
INFO | --- Analysis for AEGP, Spanish Textile and Clothing Association took 9.838085651397705s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.3511388301849365s
Availability | VoID file availability check for AEMET metereological dataset took 0.15962719917297363s
Extra | Recovery of all triples for AEMET metereological dataset took 3.8254411220550537s
Performance | Total latancy measurement for AEMET metereological dataset took 0.5776543617248535s
Amount of data | Number of triples check for AEMET metereological dataset took 14.821027517318726s
Interoperability | New terms check for AEMET metereological dataset took 9.003269672393799s
Versatility | Languages check for AEMET metereological dataset took 0.15612244606018066s
Interpretability | Number of blank nodes check for AEMET metereological dataset took 4.125732421875s
Interpretability | RDF structures check for AEMET metereological dataset took 0.1788463592529297s
Versatility | Serialization formats check for AEMET metereological dataset took 0.157057523727417s
Availability | RDF dump link check for AEMET metereological dataset took 0.09995484352111816s
License | MR license check for AEMET metereological dataset took 0.1943981647491455s
License | HR license check for AEMET metereological dataset took 62.7717924118042s
Amount of data | Number of property check for AEMET metereological dataset took 0.17653489112854004s
Understandability | Number of label check for AEMET metereological dataset took 63.202635526657104s
Understandability | URI regex check for AEMET metereological dataset took 0.1927027702331543s
Understandability | Vocabs check for AEMET metereological dataset took 0.11000633239746094s
Verifiability | Authors check for AEMET metereological dataset took 0.1663827896118164s
Verifiability | Publishers check for AEMET metereological dataset took 0.110137939453125s
Performance | Throughput check for AEMET metereological dataset took 10.538898468017578s
Amount of data | Check the number of entities for AEMET metereological dataset took 7.414817810058594e-05s
Verifiability | Contribs. check for AEMET metereological dataset took 0.11394214630126953s
Interlinking | sameAs chians check for AEMET metereological dataset took 0.16062712669372559s
Interlinking | skos check for AEMET metereological dataset took 0.10909056663513184s
Interlinking | skos check for AEMET metereological dataset took 0.11608409881591797s
Timeliness | dataset update frequency check for AEMET metereological dataset took 0.09887480735778809s
Currency | Creation date check for AEMET metereological dataset took 0.15094208717346191s
Currency | Modification date check for AEMET metereological dataset took 0.17980623245239258s
Rep.Conc. | URIs length for AEMET metereological dataset took 65.63884615898132s
Interoperability | New vocabularies check for AEMET metereological dataset took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for AEMET metereological dataset took 0.1490468978881836s
Accuracy | Check Functional Property for AEMET metereological dataset took 0.15560698509216309s
Accuracy | Check Inverse Functional Property for AEMET metereological dataset took 0.07975101470947266s
Accuracy | Check Empty annotation labels for AEMET metereological dataset took 1.2176644802093506s
Accuracy | Check White space in annotation for AEMET metereological dataset took 0.03599691390991211s
Accuracy | Check Datatype consistency for AEMET metereological dataset took 0.026950836181640625s
Consistency | Disjoint class check for AEMET metereological dataset took 0.1571352481842041s
Consistency | Check Misplaced properties for AEMET metereological dataset took 59.163904428482056s
Consistency | Misplaced classes for AEMET metereological dataset took 0.2579772472381592s
Consistency | Check Ontology hijacking for AEMET metereological dataset took 2.517282485961914s
Consistency | Check Invalid usage of undefined classes for AEMET metereological dataset took 1.3070402145385742s
Consistency | Check Invalid usage of undefined properties for AEMET metereological dataset took 60.026729345321655s
Conciseness | Check Extensional conciseness for AEMET metereological dataset took 0.10113525390625s
Conciseness | Check Intensional conciseness for AEMET metereological dataset took 0.16339397430419922s
Security | Sign check for AEMET metereological dataset took 0.08178067207336426s
Availability | Check URIs Dereferenciability for AEMET metereological dataset took 3.8697879314422607s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.38240814208984375s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.017929792404174805s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0005185604095458984s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 4.5299530029296875e-05s
Interoperability | Check the re-using of existing vocabs for AEMET metereological dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for AEMET metereological dataset took 1.0967254638671875e-05s
INFO | --- Analysis for AEMET metereological dataset took 413.59376335144043s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 0.0001380443572998047s
Availability | VoID file availability check for Agenda de Zaragoza took 5.245208740234375e-06s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 1.0129823684692383s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.021027565002441406s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0006060600280761719s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 1.2636184692382812e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 1.2159347534179688e-05s
INFO | --- Analysis for Agenda de Zaragoza took 5.130586862564087s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.044785499572753906s
Availability | VoID file availability check for AgriNepalData took 8.344650268554688e-06s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.35341405868530273s
Reputation | Calculation of the PageRank for AgriNepalData took 0.019866943359375s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0005083084106445312s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 7.62939453125e-05s
Believability | Calculation of trust value for AgriNepalData took 9.775161743164062e-06s
INFO | --- Analysis for AgriNepalData took 2.352182388305664s
Availability | SPARQL endpoint availability check for AGRIS took 263.3028562068939s
Availability | VoID file availability check for AGRIS took 0.316119909286499s
Completeness | Calculation of interlinking completeness for AGRIS took 0.4072842597961426s
Reputation | Calculation of the PageRank for AGRIS took 0.01864933967590332s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0005216598510742188s
Interlinking | Calculation of Clustering coefficient for AGRIS took 7.796287536621094e-05s
Believability | Calculation of trust value for AGRIS took 1.1920928955078125e-05s
INFO | --- Analysis for AGRIS took 436.700724363327s
Availability | SPARQL endpoint availability check for AGROVOC took 0.10398483276367188s
Availability | VoID file availability check for AGROVOC took 0.8332781791687012s
Extra | Recovery of all triples for AGROVOC took 19.58680248260498s
Performance | Total latancy measurement for AGROVOC took 0.28638362884521484s
Amount of data | Number of triples check for AGROVOC took 14.78351354598999s
Interoperability | New terms check for AGROVOC took 3.3904242515563965s
Versatility | Languages check for AGROVOC took 45.07224631309509s
Interpretability | Number of blank nodes check for AGROVOC took 13.839564323425293s
Interpretability | RDF structures check for AGROVOC took 0.037233591079711914s
Versatility | Serialization formats check for AGROVOC took 0.06105756759643555s
Availability | RDF dump link check for AGROVOC took 0.07177019119262695s
License | MR license check for AGROVOC took 0.0992269515991211s
License | HR license check for AGROVOC took 0.5947673320770264s
Amount of data | Number of property check for AGROVOC took 0.0582432746887207s
Understandability | Number of label check for AGROVOC took 24.020593643188477s
Understandability | URI regex check for AGROVOC took 0.6796207427978516s
Understandability | Vocabs check for AGROVOC took 0.2512049674987793s
Verifiability | Authors check for AGROVOC took 0.18677997589111328s
Verifiability | Publishers check for AGROVOC took 0.06988358497619629s
Performance | Throughput check for AGROVOC took 10.751822471618652s
Amount of data | Check the number of entities for AGROVOC took 0.0001010894775390625s
Verifiability | Contribs. check for AGROVOC took 0.09036064147949219s
Interlinking | sameAs chians check for AGROVOC took 0.03663825988769531s
Interlinking | skos check for AGROVOC took 0.3645169734954834s
Interlinking | skos check for AGROVOC took 0.13688278198242188s
Timeliness | dataset update frequency check for AGROVOC took 0.03547191619873047s
Currency | Creation date check for AGROVOC took 3.6938138008117676s
Currency | Modification date check for AGROVOC took 1.0557756423950195s
Rep.Conc. | URIs length for AGROVOC took 44.17333197593689s
Interoperability | New vocabularies check for AGROVOC took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.057973384857177734s
Accuracy | Check Functional Property for AGROVOC took 0.06511354446411133s
Accuracy | Check Inverse Functional Property for AGROVOC took 0.07143282890319824s
Accuracy | Check Empty annotation labels for AGROVOC took 17.405094861984253s
Accuracy | Check White space in annotation for AGROVOC took 2.9774458408355713s
Accuracy | Check Datatype consistency for AGROVOC took 4.361067533493042s
Consistency | Disjoint class check for AGROVOC took 0.11046147346496582s
Consistency | Check Misplaced properties for AGROVOC took 14.662615060806274s
Consistency | Check Ontology hijacking for AGROVOC took 14.52261757850647s
Consistency | Check Invalid usage of undefined classes for AGROVOC took 1.4913253784179688s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 16.198671102523804s
Conciseness | Check Extensional conciseness for AGROVOC took 2.5604281425476074s
Conciseness | Check Intensional conciseness for AGROVOC took 0.04196524620056152s
Security | Sign check for AGROVOC took 0.10315346717834473s
Availability | Check URIs Dereferenciability for AGROVOC took 5.977057218551636s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.3033938407897949s
Reputation | Calculation of the PageRank for AGROVOC took 0.018191099166870117s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.000522613525390625s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00011205673217773438s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.6689300537109375e-06s
Believability | Calculation of trust value for AGROVOC took 4.839897155761719e-05s
INFO | --- Analysis for AGROVOC took 722.1088223457336s
Availability | SPARQL endpoint availability check for AGROVOC took 8.463859558105469e-05s
Availability | VoID file availability check for AGROVOC took 5.245208740234375e-06s
Completeness | Calculation of interlinking completeness for AGROVOC took 2.870356798171997s
Reputation | Calculation of the PageRank for AGROVOC took 0.018381595611572266s
Interlinking | Calculation of Degree of Connection for AGROVOC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AGROVOC took 0.0005171298980712891s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 6.365776062011719e-05s
Believability | Calculation of trust value for AGROVOC took 1.1682510375976562e-05s
INFO | --- Analysis for AGROVOC took 8.845540046691895s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 260.5198435783386s
Availability | VoID file availability check for All India Survey of Higher Education took 0.008352041244506836s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.3798964023590088s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0005841255187988281s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 3.9577484130859375e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 7.867813110351562e-06s
INFO | --- Analysis for All India Survey of Higher Education took 263.04085993766785s
Availability | SPARQL endpoint availability check for  equipment ontology took 7.796287536621094e-05s
Availability | VoID file availability check for  equipment ontology took 0.2570834159851074s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.3890998363494873s
Reputation | Calculation of the PageRank for  equipment ontology took 0.017864465713500977s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0005362033843994141s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 1.1205673217773438e-05s
Believability | Calculation of trust value for  equipment ontology took 6.9141387939453125e-06s
INFO | --- Analysis for  equipment ontology took 2.2926390171051025s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 1.6039316654205322s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.789069414138794s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.5018913745880127s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.02144479751586914s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0005075931549072266s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 1.2159347534179688e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 1.239776611328125e-05s
INFO | --- Analysis for aksw.org Research Group dataset took 11.627169132232666s
Availability | SPARQL endpoint availability check for AlchemyAPI took 8.654594421386719e-05s
Availability | VoID file availability check for AlchemyAPI took 7.867813110351562e-06s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.3509054183959961s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.018471717834472656s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0005235671997070312s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 1.2636184692382812e-05s
Believability | Calculation of trust value for AlchemyAPI took 9.298324584960938e-06s
INFO | --- Analysis for AlchemyAPI took 3.6705150604248047s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 392.84119033813477s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 262.1437146663666s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.4911653995513916s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.01926255226135254s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0005471706390380859s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 2.0503997802734375e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 7.62939453125e-06s
INFO | --- Analysis for Alexandria Digital Library (ADL) Gazetteer took 788.1124024391174s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 263.593407869339s
Availability | VoID file availability check for aliada-scanbit-net took 1.0191497802734375s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 1.486532211303711s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.019847393035888672s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0005319118499755859s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00011229515075683594s
Believability | Calculation of trust value for aliada-scanbit-net took 1.1920928955078125e-05s
INFO | --- Analysis for aliada-scanbit-net took 1322.4244809150696s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 8.678436279296875e-05s
Availability | VoID file availability check for Allen Brain Atlas took 2.230714797973633s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.821953296661377s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.01930546760559082s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0005276203155517578s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 1.2874603271484375e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 2.193450927734375e-05s
INFO | --- Analysis for Allen Brain Atlas took 24.186294317245483s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 1.0321307182312012s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 3.3296072483062744s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 138.72539019584656s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.7228822708129883s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.5229666233062744s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.411693572998047s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.0645158290863s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 3.391258955001831s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8762884140014648s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 1.1479735374450684s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.7667031288146973s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.5815021991729736s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.5986943244934082s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 30.6195285320282s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 2.0755176544189453s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.8739726543426514s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.5121450424194336s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.5730407238006592s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.7522845268249512s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.582716703414917s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.9382905960083s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 8.463859558105469e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5455546379089355s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.576026439666748s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5907998085021973s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5657367706298828s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.5986437797546387s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 0.5776598453521729s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 0.5662651062011719s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 51.332695960998535s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 1.662221908569336s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5798702239990234s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6745150089263916s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6440365314483643s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 35.89964509010315s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.0840227603912354s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.5959835052490234s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.646944522857666s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 9.748723030090332s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.800452709197998s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 31.629185914993286s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.3621776103973389s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 10.621906757354736s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.724438190460205s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.867164134979248s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 1.3739380836486816s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 13551.878350257874s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 5.824355602264404s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.019241809844970703s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0005362033843994141s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 8.296966552734375e-05s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 1.3038134574890137s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 1.239776611328125e-05s
INFO | --- Analysis for Allie Abbreviation And Long Form Database in Life Science took 14300.62183046341s
Availability | SPARQL endpoint availability check for Alojamientos took 8.20159912109375e-05s
Availability | VoID file availability check for Alojamientos took 5.245208740234375e-06s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.5784018039703369s
Reputation | Calculation of the PageRank for Alojamientos took 0.018315792083740234s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0005114078521728516s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 1.4066696166992188e-05s
Believability | Calculation of trust value for Alojamientos took 1.0728836059570312e-05s
INFO | --- Analysis for Alojamientos took 3.3791472911834717s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.3417041301727295s
Availability | VoID file availability check for ALPINO RDF Treebank took 8.821487426757812e-06s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.5345742702484131s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.01828789710998535s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0005190372467041016s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 4.029273986816406e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.0967254638671875e-05s
INFO | --- Analysis for ALPINO RDF Treebank took 4.025070905685425s
Availability | SPARQL endpoint availability check for AAT-atawil took 8.630752563476562e-05s
Availability | VoID file availability check for AAT-atawil took 1.3776872158050537s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.3536529541015625s
Reputation | Calculation of the PageRank for AAT-atawil took 0.018227100372314453s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0005159378051757812s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 1.3589859008789062e-05s
Believability | Calculation of trust value for AAT-atawil took 6.866455078125e-05s
INFO | --- Analysis for AAT-atawil took 3.6313257217407227s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 5.375576019287109s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.33886170387268066s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.020175933837890625s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0005323886871337891s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 1.3828277587890625e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 1.0251998901367188e-05s
INFO | --- Analysis for Auckland Museum Collections Online took 9.967069387435913s
Availability | SPARQL endpoint availability check for Amer Nejma took 6.771087646484375e-05s
Availability | VoID file availability check for Amer Nejma took 4.291534423828125e-06s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.33059263229370117s
Reputation | Calculation of the PageRank for Amer Nejma took 0.01776719093322754s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.000518798828125s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 1.33514404296875e-05s
Believability | Calculation of trust value for Amer Nejma took 1.33514404296875e-05s
INFO | --- Analysis for Amer Nejma took 1.990757703781128s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 8.440017700195312e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 5.7220458984375e-06s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.6900267601013184s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.018072843551635742s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0005159378051757812s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.1444091796875e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.430511474609375e-05s
INFO | --- Analysis for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.3660287857055664s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.8588640689849854s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.4581265449523926s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.4165365695953369s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.017881155014038086s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0005154609680175781s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 8.726119995117188e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.0728836059570312e-05s
INFO | --- Analysis for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 14.448528289794922s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 9.036064147949219e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 9.5367431640625e-06s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.31267571449279785s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.018440723419189453s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0005202293395996094s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 1.3113021850585938e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 1.1444091796875e-05s
INFO | --- Analysis for Analisi del blog http://www.beppegrillo.it/ took 4.4513280391693115s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 9.799003601074219e-05s
Availability | VoID file availability check for Animal Diversity Web took 1.3853411674499512s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.36160969734191895s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.020802974700927734s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0005130767822265625s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 1.1920928955078125e-05s
Believability | Calculation of trust value for Animal Diversity Web took 1.049041748046875e-05s
INFO | --- Analysis for Animal Diversity Web took 18.68118953704834s
Availability | SPARQL endpoint availability check for apache took 0.00012755393981933594s
Availability | VoID file availability check for apache took 5.9604644775390625e-06s
Completeness | Calculation of interlinking completeness for apache took 0.8193774223327637s
Reputation | Calculation of the PageRank for apache took 0.01786041259765625s
Interlinking | Calculation of Degree of Connection for apache took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for apache took 0.0005176067352294922s
Interlinking | Calculation of Clustering coefficient for apache took 5.221366882324219e-05s
Believability | Calculation of trust value for apache took 1.0728836059570312e-05s
INFO | --- Analysis for apache took 3.7601165771484375s
Availability | SPARQL endpoint availability check for Apertium RDF took 0.5635993480682373s
Availability | VoID file availability check for Apertium RDF took 9.059906005859375e-06s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.3016819953918457s
Reputation | Calculation of the PageRank for Apertium RDF took 0.018299102783203125s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0005178451538085938s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF took 1.0967254638671875e-05s
INFO | --- Analysis for Apertium RDF took 14.664834260940552s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 0.11161613464355469s
Availability | VoID file availability check for Apertium RDF CA-IT took 1.1444091796875e-05s
Extra | Recovery of all triples for Apertium RDF CA-IT took 265.1133587360382s
Performance | Total latancy measurement for Apertium RDF CA-IT took 0.5831377506256104s
Amount of data | Number of triples check for Apertium RDF CA-IT took 2.066514492034912s
Interoperability | New terms check for Apertium RDF CA-IT took 2.79565691947937s
Versatility | Languages check for Apertium RDF CA-IT took 44.263710021972656s
Interpretability | Number of blank nodes check for Apertium RDF CA-IT took 0.976360559463501s
Interpretability | RDF structures check for Apertium RDF CA-IT took 0.17249011993408203s
Versatility | Serialization formats check for Apertium RDF CA-IT took 0.1456470489501953s
Availability | RDF dump link check for Apertium RDF CA-IT took 0.1362295150756836s
License | MR license check for Apertium RDF CA-IT took 0.1819155216217041s
License | HR license check for Apertium RDF CA-IT took 0.20192313194274902s
Amount of data | Number of property check for Apertium RDF CA-IT took 0.18565678596496582s
Understandability | Number of label check for Apertium RDF CA-IT took 0.21549749374389648s
Understandability | URI regex check for Apertium RDF CA-IT took 0.20819473266601562s
Understandability | Vocabs check for Apertium RDF CA-IT took 0.0822594165802002s
Verifiability | Authors check for Apertium RDF CA-IT took 0.19231200218200684s
Verifiability | Publishers check for Apertium RDF CA-IT took 0.163071870803833s
Performance | Throughput check for Apertium RDF CA-IT took 10.740015745162964s
Amount of data | Check the number of entities for Apertium RDF CA-IT took 0.0001304149627685547s
Verifiability | Contribs. check for Apertium RDF CA-IT took 0.09110093116760254s
Interlinking | sameAs chians check for Apertium RDF CA-IT took 0.16592621803283691s
Interlinking | skos check for Apertium RDF CA-IT took 0.16319799423217773s
Interlinking | skos check for Apertium RDF CA-IT took 0.1097724437713623s
Timeliness | dataset update frequency check for Apertium RDF CA-IT took 0.11603569984436035s
Currency | Creation date check for Apertium RDF CA-IT took 0.15779590606689453s
Currency | Modification date check for Apertium RDF CA-IT took 0.16541838645935059s
Rep.Conc. | URIs length for Apertium RDF CA-IT took 97.15155863761902s
Interoperability | New vocabularies check for Apertium RDF CA-IT took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF CA-IT took 0.1770622730255127s
Accuracy | Check Functional Property for Apertium RDF CA-IT took 0.15419292449951172s
Accuracy | Check Inverse Functional Property for Apertium RDF CA-IT took 0.08009219169616699s
Accuracy | Check Empty annotation labels for Apertium RDF CA-IT took 0.7891910076141357s
Accuracy | Check White space in annotation for Apertium RDF CA-IT took 0.010294675827026367s
Accuracy | Check Datatype consistency for Apertium RDF CA-IT took 2.663374662399292s
Consistency | Disjoint class check for Apertium RDF CA-IT took 0.10477924346923828s
Consistency | Check Misplaced properties for Apertium RDF CA-IT took 4.455477237701416s
Consistency | Misplaced classes for Apertium RDF CA-IT took 8.251197099685669s
Consistency | Check Ontology hijacking for Apertium RDF CA-IT took 95.26364946365356s
Consistency | Check Invalid usage of undefined classes for Apertium RDF CA-IT took 1.4815034866333008s
Consistency | Check Invalid usage of undefined properties for Apertium RDF CA-IT took 5.655986785888672s
Conciseness | Check Extensional conciseness for Apertium RDF CA-IT took 2.8815433979034424s
Conciseness | Check Intensional conciseness for Apertium RDF CA-IT took 0.1625075340270996s
Security | Sign check for Apertium RDF CA-IT took 0.10115885734558105s
Availability | Check URIs Dereferenciability for Apertium RDF CA-IT took 3.652787923812866s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.40123891830444336s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.0182645320892334s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0005133152008056641s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 5.459785461425781e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF CA-IT took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF CA-IT took 1.4066696166992188e-05s
INFO | --- Analysis for Apertium RDF CA-IT took 632.7683870792389s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 0.09185576438903809s
Availability | VoID file availability check for Apertium RDF EN-CA took 1.049041748046875e-05s
Extra | Recovery of all triples for Apertium RDF EN-CA took 264.89368867874146s
Performance | Total latancy measurement for Apertium RDF EN-CA took 0.6145036220550537s
Amount of data | Number of triples check for Apertium RDF EN-CA took 2.1195902824401855s
Interoperability | New terms check for Apertium RDF EN-CA took 2.9256591796875s
Versatility | Languages check for Apertium RDF EN-CA took 44.91127109527588s
Interpretability | Number of blank nodes check for Apertium RDF EN-CA took 1.0389604568481445s
Interpretability | RDF structures check for Apertium RDF EN-CA took 0.1718289852142334s
Versatility | Serialization formats check for Apertium RDF EN-CA took 0.1584627628326416s
Availability | RDF dump link check for Apertium RDF EN-CA took 0.07800602912902832s
License | MR license check for Apertium RDF EN-CA took 0.1659989356994629s
License | HR license check for Apertium RDF EN-CA took 0.2022252082824707s
Amount of data | Number of property check for Apertium RDF EN-CA took 0.16663169860839844s
Understandability | Number of label check for Apertium RDF EN-CA took 0.2075498104095459s
Understandability | URI regex check for Apertium RDF EN-CA took 0.1812138557434082s
Understandability | Vocabs check for Apertium RDF EN-CA took 0.09066247940063477s
Verifiability | Authors check for Apertium RDF EN-CA took 0.22095918655395508s
Verifiability | Publishers check for Apertium RDF EN-CA took 0.16193127632141113s
Performance | Throughput check for Apertium RDF EN-CA took 10.687280178070068s
Amount of data | Check the number of entities for Apertium RDF EN-CA took 0.00011515617370605469s
Verifiability | Contribs. check for Apertium RDF EN-CA took 0.10673379898071289s
Interlinking | sameAs chians check for Apertium RDF EN-CA took 0.14472460746765137s
Interlinking | skos check for Apertium RDF EN-CA took 0.18666458129882812s
Interlinking | skos check for Apertium RDF EN-CA took 0.0814974308013916s
Timeliness | dataset update frequency check for Apertium RDF EN-CA took 0.10674571990966797s
Currency | Creation date check for Apertium RDF EN-CA took 0.17425990104675293s
Currency | Modification date check for Apertium RDF EN-CA took 0.1485459804534912s
Rep.Conc. | URIs length for Apertium RDF EN-CA took 93.14906144142151s
Interoperability | New vocabularies check for Apertium RDF EN-CA took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF EN-CA took 0.1659412384033203s
Accuracy | Check Functional Property for Apertium RDF EN-CA took 0.16094112396240234s
Accuracy | Check Inverse Functional Property for Apertium RDF EN-CA took 0.07831144332885742s
Accuracy | Check Empty annotation labels for Apertium RDF EN-CA took 0.7797398567199707s
Accuracy | Check White space in annotation for Apertium RDF EN-CA took 0.010346412658691406s
Accuracy | Check Datatype consistency for Apertium RDF EN-CA took 2.725201368331909s
Consistency | Disjoint class check for Apertium RDF EN-CA took 0.09239006042480469s
Consistency | Check Misplaced properties for Apertium RDF EN-CA took 4.566622257232666s
Consistency | Misplaced classes for Apertium RDF EN-CA took 8.362236022949219s
Consistency | Check Ontology hijacking for Apertium RDF EN-CA took 92.88880562782288s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EN-CA took 1.4811632633209229s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EN-CA took 5.773672580718994s
Conciseness | Check Extensional conciseness for Apertium RDF EN-CA took 3.0440833568573s
Conciseness | Check Intensional conciseness for Apertium RDF EN-CA took 0.1678612232208252s
Security | Sign check for Apertium RDF EN-CA took 0.11339807510375977s
Availability | Check URIs Dereferenciability for Apertium RDF EN-CA took 3.492183208465576s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.5715622901916504s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.01800847053527832s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0005152225494384766s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.9591064453125e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EN-CA took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EN-CA took 1.3589859008789062e-05s
INFO | --- Analysis for Apertium RDF EN-CA took 637.6212999820709s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 0.07981014251708984s
Availability | VoID file availability check for Apertium RDF EN-ES took 5.245208740234375e-06s
Extra | Recovery of all triples for Apertium RDF EN-ES took 289.8983738422394s
Performance | Total latancy measurement for Apertium RDF EN-ES took 0.5517172813415527s
Amount of data | Number of triples check for Apertium RDF EN-ES took 2.062798023223877s
Interoperability | New terms check for Apertium RDF EN-ES took 2.6478214263916016s
Versatility | Languages check for Apertium RDF EN-ES took 45.53040385246277s
Interpretability | Number of blank nodes check for Apertium RDF EN-ES took 1.001358985900879s
Interpretability | RDF structures check for Apertium RDF EN-ES took 0.15448498725891113s
Versatility | Serialization formats check for Apertium RDF EN-ES took 0.16367411613464355s
Availability | RDF dump link check for Apertium RDF EN-ES took 0.08946943283081055s
License | MR license check for Apertium RDF EN-ES took 0.1490154266357422s
License | HR license check for Apertium RDF EN-ES took 0.19374370574951172s
Amount of data | Number of property check for Apertium RDF EN-ES took 0.16729950904846191s
Understandability | Number of label check for Apertium RDF EN-ES took 0.20296263694763184s
Understandability | URI regex check for Apertium RDF EN-ES took 0.1701068878173828s
Understandability | Vocabs check for Apertium RDF EN-ES took 0.09168076515197754s
Verifiability | Authors check for Apertium RDF EN-ES took 0.21656346321105957s
Verifiability | Publishers check for Apertium RDF EN-ES took 0.1440432071685791s
Performance | Throughput check for Apertium RDF EN-ES took 10.872904300689697s
Amount of data | Check the number of entities for Apertium RDF EN-ES took 0.0004475116729736328s
Verifiability | Contribs. check for Apertium RDF EN-ES took 0.09837675094604492s
Interlinking | sameAs chians check for Apertium RDF EN-ES took 0.1422874927520752s
Interlinking | skos check for Apertium RDF EN-ES took 0.16698336601257324s
Interlinking | skos check for Apertium RDF EN-ES took 0.09337997436523438s
Timeliness | dataset update frequency check for Apertium RDF EN-ES took 0.07858872413635254s
Currency | Creation date check for Apertium RDF EN-ES took 0.1640927791595459s
Currency | Modification date check for Apertium RDF EN-ES took 0.1638185977935791s
Rep.Conc. | URIs length for Apertium RDF EN-ES took 85.64692521095276s
Interoperability | New vocabularies check for Apertium RDF EN-ES took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EN-ES took 0.15504884719848633s
Accuracy | Check Functional Property for Apertium RDF EN-ES took 0.17306733131408691s
Accuracy | Check Inverse Functional Property for Apertium RDF EN-ES took 0.08035159111022949s
Accuracy | Check Empty annotation labels for Apertium RDF EN-ES took 0.7792105674743652s
Accuracy | Check White space in annotation for Apertium RDF EN-ES took 0.010295391082763672s
Accuracy | Check Datatype consistency for Apertium RDF EN-ES took 2.675971746444702s
Consistency | Disjoint class check for Apertium RDF EN-ES took 0.08392596244812012s
Consistency | Check Misplaced properties for Apertium RDF EN-ES took 4.63135290145874s
Consistency | Misplaced classes for Apertium RDF EN-ES took 8.276492595672607s
Consistency | Check Ontology hijacking for Apertium RDF EN-ES took 83.67457699775696s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EN-ES took 1.5523645877838135s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EN-ES took 5.680417776107788s
Conciseness | Check Extensional conciseness for Apertium RDF EN-ES took 3.006187915802002s
Conciseness | Check Intensional conciseness for Apertium RDF EN-ES took 0.17908787727355957s
Security | Sign check for Apertium RDF EN-ES took 0.09148430824279785s
Availability | Check URIs Dereferenciability for Apertium RDF EN-ES took 3.5888924598693848s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.573951005935669s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.017999887466430664s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0005156993865966797s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.696846008300781e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EN-ES took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF EN-ES took 1.1682510375976562e-05s
INFO | --- Analysis for Apertium RDF EN-ES took 643.377366065979s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 0.08234691619873047s
Availability | VoID file availability check for Apertium RDF EN-GL took 1.0728836059570312e-05s
Extra | Recovery of all triples for Apertium RDF EN-GL took 274.9962613582611s
Performance | Total latancy measurement for Apertium RDF EN-GL took 0.519977331161499s
Amount of data | Number of triples check for Apertium RDF EN-GL took 2.1071813106536865s
Interoperability | New terms check for Apertium RDF EN-GL took 2.788865327835083s
Versatility | Languages check for Apertium RDF EN-GL took 45.04010319709778s
Interpretability | Number of blank nodes check for Apertium RDF EN-GL took 0.9596319198608398s
Interpretability | RDF structures check for Apertium RDF EN-GL took 0.17849159240722656s
Versatility | Serialization formats check for Apertium RDF EN-GL took 0.14632320404052734s
Availability | RDF dump link check for Apertium RDF EN-GL took 0.10725045204162598s
License | MR license check for Apertium RDF EN-GL took 0.1538689136505127s
License | HR license check for Apertium RDF EN-GL took 0.21110844612121582s
Amount of data | Number of property check for Apertium RDF EN-GL took 0.16483211517333984s
Understandability | Number of label check for Apertium RDF EN-GL took 0.23040127754211426s
Understandability | URI regex check for Apertium RDF EN-GL took 0.18230462074279785s
Understandability | Vocabs check for Apertium RDF EN-GL took 0.09136843681335449s
Verifiability | Authors check for Apertium RDF EN-GL took 0.20408082008361816s
Verifiability | Publishers check for Apertium RDF EN-GL took 0.14490771293640137s
Performance | Throughput check for Apertium RDF EN-GL took 10.739416122436523s
Amount of data | Check the number of entities for Apertium RDF EN-GL took 8.630752563476562e-05s
Verifiability | Contribs. check for Apertium RDF EN-GL took 0.07749724388122559s
Interlinking | sameAs chians check for Apertium RDF EN-GL took 0.1661367416381836s
Interlinking | skos check for Apertium RDF EN-GL took 0.17471551895141602s
Interlinking | skos check for Apertium RDF EN-GL took 0.10233449935913086s
Timeliness | dataset update frequency check for Apertium RDF EN-GL took 0.08922529220581055s
Currency | Creation date check for Apertium RDF EN-GL took 0.15675067901611328s
Currency | Modification date check for Apertium RDF EN-GL took 0.1635880470275879s
Rep.Conc. | URIs length for Apertium RDF EN-GL took 92.91214108467102s
Interoperability | New vocabularies check for Apertium RDF EN-GL took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EN-GL took 0.16046762466430664s
Accuracy | Check Functional Property for Apertium RDF EN-GL took 0.16234922409057617s
Accuracy | Check Inverse Functional Property for Apertium RDF EN-GL took 0.07819175720214844s
Accuracy | Check Empty annotation labels for Apertium RDF EN-GL took 0.8116965293884277s
Accuracy | Check White space in annotation for Apertium RDF EN-GL took 0.010381937026977539s
Accuracy | Check Datatype consistency for Apertium RDF EN-GL took 2.6477885246276855s
Consistency | Disjoint class check for Apertium RDF EN-GL took 0.09968090057373047s
Consistency | Check Misplaced properties for Apertium RDF EN-GL took 4.475400686264038s
Consistency | Misplaced classes for Apertium RDF EN-GL took 8.336673974990845s
Consistency | Check Ontology hijacking for Apertium RDF EN-GL took 83.30272054672241s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EN-GL took 1.5043189525604248s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EN-GL took 5.700863361358643s
Conciseness | Check Extensional conciseness for Apertium RDF EN-GL took 3.0033960342407227s
Conciseness | Check Intensional conciseness for Apertium RDF EN-GL took 0.16711211204528809s
Security | Sign check for Apertium RDF EN-GL took 0.09987115859985352s
Availability | Check URIs Dereferenciability for Apertium RDF EN-GL took 3.557746410369873s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.34081172943115234s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.018764734268188477s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0005898475646972656s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 5.1021575927734375e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EN-GL took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF EN-GL took 1.239776611328125e-05s
INFO | --- Analysis for Apertium RDF EN-GL took 636.0392353534698s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 0.08484292030334473s
Availability | VoID file availability check for Apertium RDF EO-CA took 1.71661376953125e-05s
Extra | Recovery of all triples for Apertium RDF EO-CA took 305.49894309043884s
Performance | Total latancy measurement for Apertium RDF EO-CA took 0.5749597549438477s
Amount of data | Number of triples check for Apertium RDF EO-CA took 2.0415728092193604s
Interoperability | New terms check for Apertium RDF EO-CA took 2.774688720703125s
Versatility | Languages check for Apertium RDF EO-CA took 44.91851353645325s
Interpretability | Number of blank nodes check for Apertium RDF EO-CA took 0.9137532711029053s
Interpretability | RDF structures check for Apertium RDF EO-CA took 0.18139958381652832s
Versatility | Serialization formats check for Apertium RDF EO-CA took 0.1828446388244629s
Availability | RDF dump link check for Apertium RDF EO-CA took 0.08898329734802246s
License | MR license check for Apertium RDF EO-CA took 0.15899872779846191s
License | HR license check for Apertium RDF EO-CA took 0.18431949615478516s
Amount of data | Number of property check for Apertium RDF EO-CA took 0.15882444381713867s
Understandability | Number of label check for Apertium RDF EO-CA took 0.22277450561523438s
Understandability | URI regex check for Apertium RDF EO-CA took 0.18111157417297363s
Understandability | Vocabs check for Apertium RDF EO-CA took 0.08864045143127441s
Verifiability | Authors check for Apertium RDF EO-CA took 0.258467435836792s
Verifiability | Publishers check for Apertium RDF EO-CA took 0.17147159576416016s
Performance | Throughput check for Apertium RDF EO-CA took 10.848974466323853s
Amount of data | Check the number of entities for Apertium RDF EO-CA took 0.0003750324249267578s
Verifiability | Contribs. check for Apertium RDF EO-CA took 0.0830991268157959s
Interlinking | sameAs chians check for Apertium RDF EO-CA took 0.18058538436889648s
Interlinking | skos check for Apertium RDF EO-CA took 0.14991140365600586s
Interlinking | skos check for Apertium RDF EO-CA took 0.09329104423522949s
Timeliness | dataset update frequency check for Apertium RDF EO-CA took 0.08029842376708984s
Currency | Creation date check for Apertium RDF EO-CA took 0.18359589576721191s
Currency | Modification date check for Apertium RDF EO-CA took 0.17283368110656738s
Rep.Conc. | URIs length for Apertium RDF EO-CA took 85.26290655136108s
Interoperability | New vocabularies check for Apertium RDF EO-CA took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-CA took 0.16756558418273926s
Accuracy | Check Functional Property for Apertium RDF EO-CA took 0.15588951110839844s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-CA took 0.09702491760253906s
Accuracy | Check Empty annotation labels for Apertium RDF EO-CA took 0.7584853172302246s
Accuracy | Check White space in annotation for Apertium RDF EO-CA took 0.010351181030273438s
Accuracy | Check Datatype consistency for Apertium RDF EO-CA took 2.669901132583618s
Consistency | Disjoint class check for Apertium RDF EO-CA took 0.09783124923706055s
Consistency | Check Misplaced properties for Apertium RDF EO-CA took 4.81738543510437s
Consistency | Misplaced classes for Apertium RDF EO-CA took 8.24049973487854s
Consistency | Check Ontology hijacking for Apertium RDF EO-CA took 91.9378490447998s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-CA took 1.5023982524871826s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-CA took 5.792232036590576s
Conciseness | Check Extensional conciseness for Apertium RDF EO-CA took 3.020289421081543s
Conciseness | Check Intensional conciseness for Apertium RDF EO-CA took 0.21126556396484375s
Security | Sign check for Apertium RDF EO-CA took 0.10102009773254395s
Availability | Check URIs Dereferenciability for Apertium RDF EO-CA took 3.4451258182525635s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 5.291962385177612s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.01821279525756836s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0005145072937011719s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 5.340576171875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-CA took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.4066696166992188e-05s
INFO | --- Analysis for Apertium RDF EO-CA took 678.1971907615662s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 0.08287596702575684s
Availability | VoID file availability check for Apertium RDF EO-EN took 6.9141387939453125e-06s
Extra | Recovery of all triples for Apertium RDF EO-EN took 248.35273385047913s
Performance | Total latancy measurement for Apertium RDF EO-EN took 0.5855927467346191s
Amount of data | Number of triples check for Apertium RDF EO-EN took 1.9991917610168457s
Interoperability | New terms check for Apertium RDF EO-EN took 2.940281629562378s
Versatility | Languages check for Apertium RDF EO-EN took 44.74861741065979s
Interpretability | Number of blank nodes check for Apertium RDF EO-EN took 0.9921987056732178s
Interpretability | RDF structures check for Apertium RDF EO-EN took 0.18361997604370117s
Versatility | Serialization formats check for Apertium RDF EO-EN took 0.16179656982421875s
Availability | RDF dump link check for Apertium RDF EO-EN took 0.09641242027282715s
License | MR license check for Apertium RDF EO-EN took 0.15962910652160645s
License | HR license check for Apertium RDF EO-EN took 0.20705342292785645s
Amount of data | Number of property check for Apertium RDF EO-EN took 0.1791553497314453s
Understandability | Number of label check for Apertium RDF EO-EN took 0.20815753936767578s
Understandability | URI regex check for Apertium RDF EO-EN took 0.17009902000427246s
Understandability | Vocabs check for Apertium RDF EO-EN took 0.1149144172668457s
Verifiability | Authors check for Apertium RDF EO-EN took 0.19050097465515137s
Verifiability | Publishers check for Apertium RDF EO-EN took 0.1619420051574707s
Performance | Throughput check for Apertium RDF EO-EN took 10.99863862991333s
Amount of data | Check the number of entities for Apertium RDF EO-EN took 9.465217590332031e-05s
Verifiability | Contribs. check for Apertium RDF EO-EN took 0.0789482593536377s
Interlinking | sameAs chians check for Apertium RDF EO-EN took 0.15450215339660645s
Interlinking | skos check for Apertium RDF EO-EN took 0.16903233528137207s
Interlinking | skos check for Apertium RDF EO-EN took 0.08064961433410645s
Timeliness | dataset update frequency check for Apertium RDF EO-EN took 0.11455726623535156s
Currency | Creation date check for Apertium RDF EO-EN took 0.15810132026672363s
Currency | Modification date check for Apertium RDF EO-EN took 0.1725142002105713s
Rep.Conc. | URIs length for Apertium RDF EO-EN took 101.74281644821167s
Interoperability | New vocabularies check for Apertium RDF EO-EN took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-EN took 0.1679527759552002s
Accuracy | Check Functional Property for Apertium RDF EO-EN took 0.15988588333129883s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-EN took 0.09859251976013184s
Accuracy | Check Empty annotation labels for Apertium RDF EO-EN took 0.71114182472229s
Accuracy | Check White space in annotation for Apertium RDF EO-EN took 0.01052713394165039s
Accuracy | Check Datatype consistency for Apertium RDF EO-EN took 2.651254653930664s
Consistency | Disjoint class check for Apertium RDF EO-EN took 0.08122563362121582s
Consistency | Check Misplaced properties for Apertium RDF EO-EN took 4.596713066101074s
Consistency | Misplaced classes for Apertium RDF EO-EN took 8.282730340957642s
Consistency | Check Ontology hijacking for Apertium RDF EO-EN took 91.66355276107788s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-EN took 1.507744550704956s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-EN took 5.961636304855347s
Conciseness | Check Extensional conciseness for Apertium RDF EO-EN took 3.0712978839874268s
Conciseness | Check Intensional conciseness for Apertium RDF EO-EN took 0.17618608474731445s
Security | Sign check for Apertium RDF EO-EN took 0.10179805755615234s
Availability | Check URIs Dereferenciability for Apertium RDF EO-EN took 3.536048650741577s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 1.0113317966461182s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.018001794815063477s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0005080699920654297s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.57763671875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-EN took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.3589859008789062e-05s
INFO | --- Analysis for Apertium RDF EO-EN took 628.3598392009735s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 0.09892487525939941s
Availability | VoID file availability check for Apertium RDF EO-ES took 1.0251998901367188e-05s
Extra | Recovery of all triples for Apertium RDF EO-ES took 263.95997881889343s
Performance | Total latancy measurement for Apertium RDF EO-ES took 0.6262972354888916s
Amount of data | Number of triples check for Apertium RDF EO-ES took 2.0574915409088135s
Interoperability | New terms check for Apertium RDF EO-ES took 2.9386448860168457s
Versatility | Languages check for Apertium RDF EO-ES took 45.19950079917908s
Interpretability | Number of blank nodes check for Apertium RDF EO-ES took 0.9520838260650635s
Interpretability | RDF structures check for Apertium RDF EO-ES took 0.1622450351715088s
Versatility | Serialization formats check for Apertium RDF EO-ES took 0.1725456714630127s
Availability | RDF dump link check for Apertium RDF EO-ES took 0.09748196601867676s
License | MR license check for Apertium RDF EO-ES took 0.15900635719299316s
License | HR license check for Apertium RDF EO-ES took 0.1989305019378662s
Amount of data | Number of property check for Apertium RDF EO-ES took 0.16878747940063477s
Understandability | Number of label check for Apertium RDF EO-ES took 0.21100234985351562s
Understandability | URI regex check for Apertium RDF EO-ES took 0.19065189361572266s
Understandability | Vocabs check for Apertium RDF EO-ES took 0.08045029640197754s
Verifiability | Authors check for Apertium RDF EO-ES took 0.18845558166503906s
Verifiability | Publishers check for Apertium RDF EO-ES took 0.17806601524353027s
Performance | Throughput check for Apertium RDF EO-ES took 10.801615953445435s
Amount of data | Check the number of entities for Apertium RDF EO-ES took 0.0001232624053955078s
Verifiability | Contribs. check for Apertium RDF EO-ES took 0.09791755676269531s
Interlinking | sameAs chians check for Apertium RDF EO-ES took 0.14269495010375977s
Interlinking | skos check for Apertium RDF EO-ES took 0.16092395782470703s
Interlinking | skos check for Apertium RDF EO-ES took 0.09260439872741699s
Timeliness | dataset update frequency check for Apertium RDF EO-ES took 0.10004305839538574s
Currency | Creation date check for Apertium RDF EO-ES took 0.15802788734436035s
Currency | Modification date check for Apertium RDF EO-ES took 0.16738510131835938s
Rep.Conc. | URIs length for Apertium RDF EO-ES took 92.70701313018799s
Interoperability | New vocabularies check for Apertium RDF EO-ES took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-ES took 0.1513662338256836s
Accuracy | Check Functional Property for Apertium RDF EO-ES took 0.17357659339904785s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-ES took 0.07969260215759277s
Accuracy | Check Empty annotation labels for Apertium RDF EO-ES took 0.7603528499603271s
Accuracy | Check White space in annotation for Apertium RDF EO-ES took 0.010459661483764648s
Accuracy | Check Datatype consistency for Apertium RDF EO-ES took 2.6741933822631836s
Consistency | Disjoint class check for Apertium RDF EO-ES took 0.08995580673217773s
Consistency | Check Misplaced properties for Apertium RDF EO-ES took 4.578746318817139s
Consistency | Misplaced classes for Apertium RDF EO-ES took 8.29476809501648s
Consistency | Check Ontology hijacking for Apertium RDF EO-ES took 91.30625867843628s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-ES took 1.482787847518921s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-ES took 5.876649379730225s
Conciseness | Check Extensional conciseness for Apertium RDF EO-ES took 3.010613203048706s
Conciseness | Check Intensional conciseness for Apertium RDF EO-ES took 0.1705634593963623s
Security | Sign check for Apertium RDF EO-ES took 0.0994260311126709s
Availability | Check URIs Dereferenciability for Apertium RDF EO-ES took 3.4791548252105713s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.9017026424407959s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.017976045608520508s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0005478858947753906s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.649162292480469e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-ES took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EO-ES took 1.2159347534179688e-05s
INFO | --- Analysis for Apertium RDF EO-ES took 647.1384689807892s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 0.09251284599304199s
Availability | VoID file availability check for Apertium RDF EO-FR took 1.0967254638671875e-05s
Extra | Recovery of all triples for Apertium RDF EO-FR took 276.12707901000977s
Performance | Total latancy measurement for Apertium RDF EO-FR took 0.5275988578796387s
Amount of data | Number of triples check for Apertium RDF EO-FR took 2.0913102626800537s
Interoperability | New terms check for Apertium RDF EO-FR took 2.8226332664489746s
Versatility | Languages check for Apertium RDF EO-FR took 45.06491708755493s
Interpretability | Number of blank nodes check for Apertium RDF EO-FR took 0.9314250946044922s
Interpretability | RDF structures check for Apertium RDF EO-FR took 0.16324448585510254s
Versatility | Serialization formats check for Apertium RDF EO-FR took 0.14657187461853027s
Availability | RDF dump link check for Apertium RDF EO-FR took 0.0793006420135498s
License | MR license check for Apertium RDF EO-FR took 0.15839838981628418s
License | HR license check for Apertium RDF EO-FR took 0.19830060005187988s
Amount of data | Number of property check for Apertium RDF EO-FR took 0.1589369773864746s
Understandability | Number of label check for Apertium RDF EO-FR took 0.20202207565307617s
Understandability | URI regex check for Apertium RDF EO-FR took 0.19063758850097656s
Understandability | Vocabs check for Apertium RDF EO-FR took 0.09629034996032715s
Verifiability | Authors check for Apertium RDF EO-FR took 0.2299349308013916s
Verifiability | Publishers check for Apertium RDF EO-FR took 0.14392805099487305s
Performance | Throughput check for Apertium RDF EO-FR took 10.706763744354248s
Amount of data | Check the number of entities for Apertium RDF EO-FR took 8.916854858398438e-05s
Verifiability | Contribs. check for Apertium RDF EO-FR took 0.1136939525604248s
Interlinking | sameAs chians check for Apertium RDF EO-FR took 0.16414451599121094s
Interlinking | skos check for Apertium RDF EO-FR took 0.1508166790008545s
Interlinking | skos check for Apertium RDF EO-FR took 0.1087648868560791s
Timeliness | dataset update frequency check for Apertium RDF EO-FR took 0.09825563430786133s
Currency | Creation date check for Apertium RDF EO-FR took 0.1676316261291504s
Currency | Modification date check for Apertium RDF EO-FR took 0.17281651496887207s
Rep.Conc. | URIs length for Apertium RDF EO-FR took 98.50904941558838s
Interoperability | New vocabularies check for Apertium RDF EO-FR took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-FR took 0.16694378852844238s
Accuracy | Check Functional Property for Apertium RDF EO-FR took 0.15393352508544922s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-FR took 0.1005704402923584s
Accuracy | Check Empty annotation labels for Apertium RDF EO-FR took 0.8754589557647705s
Accuracy | Check White space in annotation for Apertium RDF EO-FR took 0.010214805603027344s
Accuracy | Check Datatype consistency for Apertium RDF EO-FR took 2.644474506378174s
Consistency | Disjoint class check for Apertium RDF EO-FR took 0.1168069839477539s
Consistency | Check Misplaced properties for Apertium RDF EO-FR took 4.8439860343933105s
Consistency | Misplaced classes for Apertium RDF EO-FR took 8.37706971168518s
Consistency | Check Ontology hijacking for Apertium RDF EO-FR took 96.62692356109619s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-FR took 1.518812894821167s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-FR took 5.883553504943848s
Conciseness | Check Extensional conciseness for Apertium RDF EO-FR took 3.026298999786377s
Conciseness | Check Intensional conciseness for Apertium RDF EO-FR took 0.15971899032592773s
Security | Sign check for Apertium RDF EO-FR took 0.09937071800231934s
Availability | Check URIs Dereferenciability for Apertium RDF EO-FR took 3.515331506729126s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.9776396751403809s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.018018722534179688s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0005228519439697266s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.5299530029296875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-FR took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF EO-FR took 8.344650268554688e-06s
INFO | --- Analysis for Apertium RDF EO-FR took 676.3034818172455s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 0.09181094169616699s
Availability | VoID file availability check for Apertium RDF ES-AN took 1.1920928955078125e-05s
Extra | Recovery of all triples for Apertium RDF ES-AN took 248.67761611938477s
Performance | Total latancy measurement for Apertium RDF ES-AN took 0.549304723739624s
Amount of data | Number of triples check for Apertium RDF ES-AN took 2.0885562896728516s
Interoperability | New terms check for Apertium RDF ES-AN took 2.792132616043091s
Versatility | Languages check for Apertium RDF ES-AN took 44.74601697921753s
Interpretability | Number of blank nodes check for Apertium RDF ES-AN took 0.8436288833618164s
Interpretability | RDF structures check for Apertium RDF ES-AN took 0.16306185722351074s
Versatility | Serialization formats check for Apertium RDF ES-AN took 0.17214608192443848s
Availability | RDF dump link check for Apertium RDF ES-AN took 0.0975034236907959s
License | MR license check for Apertium RDF ES-AN took 0.15017485618591309s
License | HR license check for Apertium RDF ES-AN took 0.1766650676727295s
Amount of data | Number of property check for Apertium RDF ES-AN took 0.15321016311645508s
Understandability | Number of label check for Apertium RDF ES-AN took 0.19857287406921387s
Understandability | URI regex check for Apertium RDF ES-AN took 0.1893620491027832s
Understandability | Vocabs check for Apertium RDF ES-AN took 0.10704565048217773s
Verifiability | Authors check for Apertium RDF ES-AN took 0.20281052589416504s
Verifiability | Publishers check for Apertium RDF ES-AN took 0.15280771255493164s
Performance | Throughput check for Apertium RDF ES-AN took 10.64695954322815s
Amount of data | Check the number of entities for Apertium RDF ES-AN took 0.0004718303680419922s
Verifiability | Contribs. check for Apertium RDF ES-AN took 0.11036539077758789s
Interlinking | sameAs chians check for Apertium RDF ES-AN took 0.1530168056488037s
Interlinking | skos check for Apertium RDF ES-AN took 0.16829156875610352s
Interlinking | skos check for Apertium RDF ES-AN took 0.09998130798339844s
Timeliness | dataset update frequency check for Apertium RDF ES-AN took 0.09195685386657715s
Currency | Creation date check for Apertium RDF ES-AN took 0.18458914756774902s
Currency | Modification date check for Apertium RDF ES-AN took 0.17397022247314453s
Rep.Conc. | URIs length for Apertium RDF ES-AN took 84.09495759010315s
Interoperability | New vocabularies check for Apertium RDF ES-AN took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-AN took 0.14434146881103516s
Accuracy | Check Functional Property for Apertium RDF ES-AN took 0.16387534141540527s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-AN took 0.09192776679992676s
Accuracy | Check Empty annotation labels for Apertium RDF ES-AN took 0.8970730304718018s
Accuracy | Check White space in annotation for Apertium RDF ES-AN took 0.010236740112304688s
Accuracy | Check Datatype consistency for Apertium RDF ES-AN took 2.6720998287200928s
Consistency | Disjoint class check for Apertium RDF ES-AN took 0.09788227081298828s
Consistency | Check Misplaced properties for Apertium RDF ES-AN took 4.611361265182495s
Consistency | Misplaced classes for Apertium RDF ES-AN took 8.285999536514282s
Consistency | Check Ontology hijacking for Apertium RDF ES-AN took 85.13438129425049s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-AN took 1.5548968315124512s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-AN took 5.920737266540527s
Conciseness | Check Extensional conciseness for Apertium RDF ES-AN took 3.058201313018799s
Conciseness | Check Intensional conciseness for Apertium RDF ES-AN took 0.17009425163269043s
Security | Sign check for Apertium RDF ES-AN took 0.11560702323913574s
Availability | Check URIs Dereferenciability for Apertium RDF ES-AN took 3.4220480918884277s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 4.027300834655762s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.018480539321899414s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 2.8133392333984375e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0005354881286621094s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.9591064453125e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-AN took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.3589859008789062e-05s
INFO | --- Analysis for Apertium RDF ES-AN took 612.8865082263947s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 0.09277915954589844s
Availability | VoID file availability check for Apertium RDF ES-AST took 7.3909759521484375e-06s
Extra | Recovery of all triples for Apertium RDF ES-AST took 277.3990092277527s
Performance | Total latancy measurement for Apertium RDF ES-AST took 0.6363718509674072s
Amount of data | Number of triples check for Apertium RDF ES-AST took 2.192148208618164s
Interoperability | New terms check for Apertium RDF ES-AST took 2.7806453704833984s
Versatility | Languages check for Apertium RDF ES-AST took 45.111732721328735s
Interpretability | Number of blank nodes check for Apertium RDF ES-AST took 1.0976147651672363s
Interpretability | RDF structures check for Apertium RDF ES-AST took 0.1559910774230957s
Versatility | Serialization formats check for Apertium RDF ES-AST took 0.16122174263000488s
Availability | RDF dump link check for Apertium RDF ES-AST took 0.09124207496643066s
License | MR license check for Apertium RDF ES-AST took 0.15970754623413086s
License | HR license check for Apertium RDF ES-AST took 0.17293953895568848s
Amount of data | Number of property check for Apertium RDF ES-AST took 0.16630291938781738s
Understandability | Number of label check for Apertium RDF ES-AST took 0.19414162635803223s
Understandability | URI regex check for Apertium RDF ES-AST took 0.18786215782165527s
Understandability | Vocabs check for Apertium RDF ES-AST took 0.08068013191223145s
Verifiability | Authors check for Apertium RDF ES-AST took 0.20449614524841309s
Verifiability | Publishers check for Apertium RDF ES-AST took 0.145768404006958s
Performance | Throughput check for Apertium RDF ES-AST took 10.80412220954895s
Amount of data | Check the number of entities for Apertium RDF ES-AST took 0.0005052089691162109s
Verifiability | Contribs. check for Apertium RDF ES-AST took 0.0985558032989502s
Interlinking | sameAs chians check for Apertium RDF ES-AST took 0.1439206600189209s
Interlinking | skos check for Apertium RDF ES-AST took 0.16530156135559082s
Interlinking | skos check for Apertium RDF ES-AST took 0.10984086990356445s
Timeliness | dataset update frequency check for Apertium RDF ES-AST took 0.0803518295288086s
Currency | Creation date check for Apertium RDF ES-AST took 0.14907312393188477s
Currency | Modification date check for Apertium RDF ES-AST took 0.16185879707336426s
Rep.Conc. | URIs length for Apertium RDF ES-AST took 84.35038948059082s
Interoperability | New vocabularies check for Apertium RDF ES-AST took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-AST took 0.17388415336608887s
Accuracy | Check Functional Property for Apertium RDF ES-AST took 0.14260315895080566s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-AST took 0.09715771675109863s
Accuracy | Check Empty annotation labels for Apertium RDF ES-AST took 0.7060103416442871s
Accuracy | Check White space in annotation for Apertium RDF ES-AST took 0.010280609130859375s
Accuracy | Check Datatype consistency for Apertium RDF ES-AST took 2.72833514213562s
Consistency | Disjoint class check for Apertium RDF ES-AST took 0.0928349494934082s
Consistency | Check Misplaced properties for Apertium RDF ES-AST took 5.093842267990112s
Consistency | Misplaced classes for Apertium RDF ES-AST took 8.392522096633911s
Consistency | Check Ontology hijacking for Apertium RDF ES-AST took 93.44916367530823s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-AST took 1.5967168807983398s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-AST took 6.0623695850372314s
Conciseness | Check Extensional conciseness for Apertium RDF ES-AST took 3.1216864585876465s
Conciseness | Check Intensional conciseness for Apertium RDF ES-AST took 0.22776150703430176s
Security | Sign check for Apertium RDF ES-AST took 0.09970259666442871s
Availability | Check URIs Dereferenciability for Apertium RDF ES-AST took 3.585308313369751s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.7392733097076416s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.01961231231689453s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0005240440368652344s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.8160552978515625e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-AST took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF ES-AST took 8.821487426757812e-06s
INFO | --- Analysis for Apertium RDF ES-AST took 649.5561618804932s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 0.09792542457580566s
Availability | VoID file availability check for Apertium RDF ES-CA took 1.7881393432617188e-05s
Extra | Recovery of all triples for Apertium RDF ES-CA took 264.8250660896301s
Performance | Total latancy measurement for Apertium RDF ES-CA took 0.5462408065795898s
Amount of data | Number of triples check for Apertium RDF ES-CA took 2.0442473888397217s
Interoperability | New terms check for Apertium RDF ES-CA took 2.98468279838562s
Versatility | Languages check for Apertium RDF ES-CA took 44.63788199424744s
Interpretability | Number of blank nodes check for Apertium RDF ES-CA took 1.0099329948425293s
Interpretability | RDF structures check for Apertium RDF ES-CA took 0.1541447639465332s
Versatility | Serialization formats check for Apertium RDF ES-CA took 0.16151952743530273s
Availability | RDF dump link check for Apertium RDF ES-CA took 0.08895039558410645s
License | MR license check for Apertium RDF ES-CA took 0.15157175064086914s
License | HR license check for Apertium RDF ES-CA took 0.18287205696105957s
Amount of data | Number of property check for Apertium RDF ES-CA took 0.16647005081176758s
Understandability | Number of label check for Apertium RDF ES-CA took 0.19496583938598633s
Understandability | URI regex check for Apertium RDF ES-CA took 0.18662738800048828s
Understandability | Vocabs check for Apertium RDF ES-CA took 0.09795117378234863s
Verifiability | Authors check for Apertium RDF ES-CA took 0.22608113288879395s
Verifiability | Publishers check for Apertium RDF ES-CA took 0.15647315979003906s
Performance | Throughput check for Apertium RDF ES-CA took 10.508285522460938s
Amount of data | Check the number of entities for Apertium RDF ES-CA took 9.441375732421875e-05s
Verifiability | Contribs. check for Apertium RDF ES-CA took 0.09600305557250977s
Interlinking | sameAs chians check for Apertium RDF ES-CA took 0.1770763397216797s
Interlinking | skos check for Apertium RDF ES-CA took 0.178206205368042s
Interlinking | skos check for Apertium RDF ES-CA took 0.09278059005737305s
Timeliness | dataset update frequency check for Apertium RDF ES-CA took 0.11510992050170898s
Currency | Creation date check for Apertium RDF ES-CA took 0.15722918510437012s
Currency | Modification date check for Apertium RDF ES-CA took 0.17017388343811035s
Rep.Conc. | URIs length for Apertium RDF ES-CA took 85.29515242576599s
Interoperability | New vocabularies check for Apertium RDF ES-CA took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-CA took 0.14564251899719238s
Accuracy | Check Functional Property for Apertium RDF ES-CA took 0.15974712371826172s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-CA took 0.09690237045288086s
Accuracy | Check Empty annotation labels for Apertium RDF ES-CA took 0.9563899040222168s
Accuracy | Check White space in annotation for Apertium RDF ES-CA took 0.010196924209594727s
Accuracy | Check Datatype consistency for Apertium RDF ES-CA took 2.6801438331604004s
Consistency | Disjoint class check for Apertium RDF ES-CA took 0.09078192710876465s
Consistency | Check Misplaced properties for Apertium RDF ES-CA took 4.592968463897705s
Consistency | Misplaced classes for Apertium RDF ES-CA took 8.363358497619629s
Consistency | Check Ontology hijacking for Apertium RDF ES-CA took 104.71590995788574s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-CA took 1.517225980758667s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-CA took 5.92156457901001s
Conciseness | Check Extensional conciseness for Apertium RDF ES-CA took 3.066087007522583s
Conciseness | Check Intensional conciseness for Apertium RDF ES-CA took 0.1613607406616211s
Security | Sign check for Apertium RDF ES-CA took 0.0937962532043457s
Availability | Check URIs Dereferenciability for Apertium RDF ES-CA took 3.3204636573791504s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.3566107749938965s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.018335580825805664s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0005311965942382812s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 5.316734313964844e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-CA took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.2874603271484375e-05s
INFO | --- Analysis for Apertium RDF ES-CA took 666.6122543811798s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 0.11579537391662598s
Availability | VoID file availability check for Apertium RDF ES-GL took 1.1682510375976562e-05s
Extra | Recovery of all triples for Apertium RDF ES-GL took 250.731853723526s
Performance | Total latancy measurement for Apertium RDF ES-GL took 0.6586310863494873s
Amount of data | Number of triples check for Apertium RDF ES-GL took 2.1017398834228516s
Interoperability | New terms check for Apertium RDF ES-GL took 2.824246406555176s
Versatility | Languages check for Apertium RDF ES-GL took 44.9176287651062s
Interpretability | Number of blank nodes check for Apertium RDF ES-GL took 1.128913164138794s
Interpretability | RDF structures check for Apertium RDF ES-GL took 0.1643352508544922s
Versatility | Serialization formats check for Apertium RDF ES-GL took 0.15602421760559082s
Availability | RDF dump link check for Apertium RDF ES-GL took 0.18462634086608887s
License | MR license check for Apertium RDF ES-GL took 0.18615961074829102s
License | HR license check for Apertium RDF ES-GL took 0.19002389907836914s
Amount of data | Number of property check for Apertium RDF ES-GL took 0.1479017734527588s
Understandability | Number of label check for Apertium RDF ES-GL took 0.19751596450805664s
Understandability | URI regex check for Apertium RDF ES-GL took 0.20329713821411133s
Understandability | Vocabs check for Apertium RDF ES-GL took 0.1006920337677002s
Verifiability | Authors check for Apertium RDF ES-GL took 0.22956585884094238s
Verifiability | Publishers check for Apertium RDF ES-GL took 0.15356945991516113s
Performance | Throughput check for Apertium RDF ES-GL took 10.909008502960205s
Amount of data | Check the number of entities for Apertium RDF ES-GL took 8.749961853027344e-05s
Verifiability | Contribs. check for Apertium RDF ES-GL took 0.07942080497741699s
Interlinking | sameAs chians check for Apertium RDF ES-GL took 0.14380574226379395s
Interlinking | skos check for Apertium RDF ES-GL took 0.1785295009613037s
Interlinking | skos check for Apertium RDF ES-GL took 0.09826540946960449s
Timeliness | dataset update frequency check for Apertium RDF ES-GL took 0.08017444610595703s
Currency | Creation date check for Apertium RDF ES-GL took 0.14872312545776367s
Currency | Modification date check for Apertium RDF ES-GL took 0.17274928092956543s
Rep.Conc. | URIs length for Apertium RDF ES-GL took 84.80104327201843s
Interoperability | New vocabularies check for Apertium RDF ES-GL took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-GL took 0.165999174118042s
Accuracy | Check Functional Property for Apertium RDF ES-GL took 0.15448236465454102s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-GL took 0.10766911506652832s
Accuracy | Check Empty annotation labels for Apertium RDF ES-GL took 0.8191432952880859s
Accuracy | Check White space in annotation for Apertium RDF ES-GL took 0.010271072387695312s
Accuracy | Check Datatype consistency for Apertium RDF ES-GL took 2.6620397567749023s
Consistency | Disjoint class check for Apertium RDF ES-GL took 0.08174324035644531s
Consistency | Check Misplaced properties for Apertium RDF ES-GL took 4.512377738952637s
Consistency | Misplaced classes for Apertium RDF ES-GL took 8.349331378936768s
Consistency | Check Ontology hijacking for Apertium RDF ES-GL took 93.73876070976257s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-GL took 1.5236096382141113s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-GL took 5.767490386962891s
Conciseness | Check Extensional conciseness for Apertium RDF ES-GL took 3.0464375019073486s
Conciseness | Check Intensional conciseness for Apertium RDF ES-GL took 0.23930740356445312s
Security | Sign check for Apertium RDF ES-GL took 0.09430694580078125s
Availability | Check URIs Dereferenciability for Apertium RDF ES-GL took 3.550961494445801s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 3.607403516769409s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.01789069175720215s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0005288124084472656s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.482269287109375e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-GL took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF ES-GL took 1.3113021850585938e-05s
INFO | --- Analysis for Apertium RDF ES-GL took 619.8290548324585s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 0.09956145286560059s
Availability | VoID file availability check for Apertium RDF ES-PT took 1.0251998901367188e-05s
Extra | Recovery of all triples for Apertium RDF ES-PT took 286.2998945713043s
Performance | Total latancy measurement for Apertium RDF ES-PT took 0.5775198936462402s
Amount of data | Number of triples check for Apertium RDF ES-PT took 2.0541024208068848s
Interoperability | New terms check for Apertium RDF ES-PT took 2.6743545532226562s
Versatility | Languages check for Apertium RDF ES-PT took 43.86050343513489s
Interpretability | Number of blank nodes check for Apertium RDF ES-PT took 0.9984076023101807s
Interpretability | RDF structures check for Apertium RDF ES-PT took 0.18711614608764648s
Versatility | Serialization formats check for Apertium RDF ES-PT took 0.14480280876159668s
Availability | RDF dump link check for Apertium RDF ES-PT took 0.07962679862976074s
License | MR license check for Apertium RDF ES-PT took 0.1605665683746338s
License | HR license check for Apertium RDF ES-PT took 0.18670082092285156s
Amount of data | Number of property check for Apertium RDF ES-PT took 0.16161751747131348s
Understandability | Number of label check for Apertium RDF ES-PT took 0.20806288719177246s
Understandability | URI regex check for Apertium RDF ES-PT took 0.19986653327941895s
Understandability | Vocabs check for Apertium RDF ES-PT took 0.1066582202911377s
Verifiability | Authors check for Apertium RDF ES-PT took 0.20636844635009766s
Verifiability | Publishers check for Apertium RDF ES-PT took 0.17921662330627441s
Performance | Throughput check for Apertium RDF ES-PT took 10.83171534538269s
Amount of data | Check the number of entities for Apertium RDF ES-PT took 0.00010204315185546875s
Verifiability | Contribs. check for Apertium RDF ES-PT took 0.10727095603942871s
Interlinking | sameAs chians check for Apertium RDF ES-PT took 0.160933256149292s
Interlinking | skos check for Apertium RDF ES-PT took 0.15494656562805176s
Interlinking | skos check for Apertium RDF ES-PT took 0.08180093765258789s
Timeliness | dataset update frequency check for Apertium RDF ES-PT took 0.1244668960571289s
Currency | Creation date check for Apertium RDF ES-PT took 0.14553332328796387s
Currency | Modification date check for Apertium RDF ES-PT took 0.14716172218322754s
Rep.Conc. | URIs length for Apertium RDF ES-PT took 92.94325280189514s
Interoperability | New vocabularies check for Apertium RDF ES-PT took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-PT took 0.1546037197113037s
Accuracy | Check Functional Property for Apertium RDF ES-PT took 0.1440727710723877s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-PT took 0.08144688606262207s
Accuracy | Check Empty annotation labels for Apertium RDF ES-PT took 0.679051399230957s
Accuracy | Check White space in annotation for Apertium RDF ES-PT took 0.010257244110107422s
Accuracy | Check Datatype consistency for Apertium RDF ES-PT took 2.794243812561035s
Consistency | Disjoint class check for Apertium RDF ES-PT took 0.09205436706542969s
Consistency | Check Misplaced properties for Apertium RDF ES-PT took 4.524895191192627s
Consistency | Misplaced classes for Apertium RDF ES-PT took 8.292735815048218s
Consistency | Check Ontology hijacking for Apertium RDF ES-PT took 109.66717314720154s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-PT took 1.5227947235107422s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-PT took 5.596350431442261s
Conciseness | Check Extensional conciseness for Apertium RDF ES-PT took 3.0194408893585205s
Conciseness | Check Intensional conciseness for Apertium RDF ES-PT took 0.14877104759216309s
Security | Sign check for Apertium RDF ES-PT took 0.10240507125854492s
Availability | Check URIs Dereferenciability for Apertium RDF ES-PT took 3.6559367179870605s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.4776928424835205s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.01807236671447754s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0005183219909667969s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.506111145019531e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-PT took 2.384185791015625e-06s
Believability | Calculation of trust value for Apertium RDF ES-PT took 1.3113021850585938e-05s
INFO | --- Analysis for Apertium RDF ES-PT took 676.7765083312988s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 0.10852909088134766s
Availability | VoID file availability check for Apertium RDF ES-RO took 1.049041748046875e-05s
Extra | Recovery of all triples for Apertium RDF ES-RO took 290.13464975357056s
Performance | Total latancy measurement for Apertium RDF ES-RO took 0.5948607921600342s
Amount of data | Number of triples check for Apertium RDF ES-RO took 2.0391178131103516s
Interoperability | New terms check for Apertium RDF ES-RO took 2.9498672485351562s
Versatility | Languages check for Apertium RDF ES-RO took 44.89072895050049s
Interpretability | Number of blank nodes check for Apertium RDF ES-RO took 0.947664737701416s
Interpretability | RDF structures check for Apertium RDF ES-RO took 0.1553821563720703s
Versatility | Serialization formats check for Apertium RDF ES-RO took 0.17508316040039062s
Availability | RDF dump link check for Apertium RDF ES-RO took 0.09041428565979004s
License | MR license check for Apertium RDF ES-RO took 0.14981722831726074s
License | HR license check for Apertium RDF ES-RO took 0.17186832427978516s
Amount of data | Number of property check for Apertium RDF ES-RO took 0.16121125221252441s
Understandability | Number of label check for Apertium RDF ES-RO took 0.1930088996887207s
Understandability | URI regex check for Apertium RDF ES-RO took 0.19315576553344727s
Understandability | Vocabs check for Apertium RDF ES-RO took 0.10661745071411133s
Verifiability | Authors check for Apertium RDF ES-RO took 0.21819853782653809s
Verifiability | Publishers check for Apertium RDF ES-RO took 0.16297030448913574s
Performance | Throughput check for Apertium RDF ES-RO took 10.981975555419922s
Amount of data | Check the number of entities for Apertium RDF ES-RO took 8.749961853027344e-05s
Verifiability | Contribs. check for Apertium RDF ES-RO took 0.09950470924377441s
Interlinking | sameAs chians check for Apertium RDF ES-RO took 0.14517521858215332s
Interlinking | skos check for Apertium RDF ES-RO took 0.1681218147277832s
Interlinking | skos check for Apertium RDF ES-RO took 0.08006834983825684s
Timeliness | dataset update frequency check for Apertium RDF ES-RO took 0.10016775131225586s
Currency | Creation date check for Apertium RDF ES-RO took 0.14806795120239258s
Currency | Modification date check for Apertium RDF ES-RO took 0.15898513793945312s
Rep.Conc. | URIs length for Apertium RDF ES-RO took 89.04623603820801s
Interoperability | New vocabularies check for Apertium RDF ES-RO took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-RO took 0.15652871131896973s
Accuracy | Check Functional Property for Apertium RDF ES-RO took 0.15328097343444824s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-RO took 0.10718679428100586s
Accuracy | Check Empty annotation labels for Apertium RDF ES-RO took 0.7951877117156982s
Accuracy | Check White space in annotation for Apertium RDF ES-RO took 0.010306119918823242s
Accuracy | Check Datatype consistency for Apertium RDF ES-RO took 2.773805618286133s
Consistency | Disjoint class check for Apertium RDF ES-RO took 0.10092306137084961s
Consistency | Check Misplaced properties for Apertium RDF ES-RO took 4.560027599334717s
Consistency | Misplaced classes for Apertium RDF ES-RO took 8.413707256317139s
Consistency | Check Ontology hijacking for Apertium RDF ES-RO took 98.66670680046082s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-RO took 1.5320699214935303s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-RO took 5.824434995651245s
Conciseness | Check Extensional conciseness for Apertium RDF ES-RO took 3.0272467136383057s
Conciseness | Check Intensional conciseness for Apertium RDF ES-RO took 0.16958951950073242s
Security | Sign check for Apertium RDF ES-RO took 0.1208031177520752s
Availability | Check URIs Dereferenciability for Apertium RDF ES-RO took 3.4258196353912354s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 2.1523032188415527s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.018795013427734375s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0005390644073486328s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.9591064453125e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-RO took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF ES-RO took 8.344650268554688e-06s
INFO | --- Analysis for Apertium RDF ES-RO took 662.7558901309967s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 0.07877516746520996s
Availability | VoID file availability check for Apertium RDF EU-EN took 1.049041748046875e-05s
Extra | Recovery of all triples for Apertium RDF EU-EN took 276.11909008026123s
Performance | Total latancy measurement for Apertium RDF EU-EN took 0.6657710075378418s
Amount of data | Number of triples check for Apertium RDF EU-EN took 2.1866912841796875s
Interoperability | New terms check for Apertium RDF EU-EN took 2.77419114112854s
Versatility | Languages check for Apertium RDF EU-EN took 44.93128848075867s
Interpretability | Number of blank nodes check for Apertium RDF EU-EN took 1.1382298469543457s
Interpretability | RDF structures check for Apertium RDF EU-EN took 0.15503692626953125s
Versatility | Serialization formats check for Apertium RDF EU-EN took 0.14666438102722168s
Availability | RDF dump link check for Apertium RDF EU-EN took 0.08021903038024902s
License | MR license check for Apertium RDF EU-EN took 0.14900517463684082s
License | HR license check for Apertium RDF EU-EN took 0.1772291660308838s
Amount of data | Number of property check for Apertium RDF EU-EN took 0.16837000846862793s
Understandability | Number of label check for Apertium RDF EU-EN took 0.20319056510925293s
Understandability | URI regex check for Apertium RDF EU-EN took 0.16037487983703613s
Understandability | Vocabs check for Apertium RDF EU-EN took 0.09614348411560059s
Verifiability | Authors check for Apertium RDF EU-EN took 0.18851017951965332s
Verifiability | Publishers check for Apertium RDF EU-EN took 0.17169976234436035s
Performance | Throughput check for Apertium RDF EU-EN took 10.85567855834961s
Amount of data | Check the number of entities for Apertium RDF EU-EN took 0.00045680999755859375s
Verifiability | Contribs. check for Apertium RDF EU-EN took 0.07965493202209473s
Interlinking | sameAs chians check for Apertium RDF EU-EN took 0.17099213600158691s
Interlinking | skos check for Apertium RDF EU-EN took 0.1488356590270996s
Interlinking | skos check for Apertium RDF EU-EN took 0.10021591186523438s
Timeliness | dataset update frequency check for Apertium RDF EU-EN took 0.08917999267578125s
Currency | Creation date check for Apertium RDF EU-EN took 0.16998028755187988s
Currency | Modification date check for Apertium RDF EU-EN took 0.16634607315063477s
Rep.Conc. | URIs length for Apertium RDF EU-EN took 83.98644733428955s
Interoperability | New vocabularies check for Apertium RDF EU-EN took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EU-EN took 0.1454029083251953s
Accuracy | Check Functional Property for Apertium RDF EU-EN took 0.17083287239074707s
Accuracy | Check Inverse Functional Property for Apertium RDF EU-EN took 0.09658026695251465s
Accuracy | Check Empty annotation labels for Apertium RDF EU-EN took 0.8235673904418945s
Accuracy | Check White space in annotation for Apertium RDF EU-EN took 0.010370016098022461s
Accuracy | Check Datatype consistency for Apertium RDF EU-EN took 2.6490259170532227s
Consistency | Disjoint class check for Apertium RDF EU-EN took 0.0815269947052002s
Consistency | Check Misplaced properties for Apertium RDF EU-EN took 4.85152006149292s
Consistency | Misplaced classes for Apertium RDF EU-EN took 8.312711954116821s
Consistency | Check Ontology hijacking for Apertium RDF EU-EN took 100.4147162437439s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EU-EN took 1.612894058227539s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EU-EN took 5.948928594589233s
Conciseness | Check Extensional conciseness for Apertium RDF EU-EN took 3.1615185737609863s
Conciseness | Check Intensional conciseness for Apertium RDF EU-EN took 0.1860806941986084s
Security | Sign check for Apertium RDF EU-EN took 0.10362529754638672s
Availability | Check URIs Dereferenciability for Apertium RDF EU-EN took 3.5223209857940674s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.636347770690918s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.018154144287109375s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0005142688751220703s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 5.626678466796875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EU-EN took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF EU-EN took 1.239776611328125e-05s
INFO | --- Analysis for Apertium RDF EU-EN took 648.4643862247467s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 0.0983114242553711s
Availability | VoID file availability check for Apertium RDF EU-ES took 5.9604644775390625e-06s
Extra | Recovery of all triples for Apertium RDF EU-ES took 290.8430745601654s
Performance | Total latancy measurement for Apertium RDF EU-ES took 0.6190314292907715s
Amount of data | Number of triples check for Apertium RDF EU-ES took 2.2157490253448486s
Interoperability | New terms check for Apertium RDF EU-ES took 2.9146158695220947s
Versatility | Languages check for Apertium RDF EU-ES took 45.326584577560425s
Interpretability | Number of blank nodes check for Apertium RDF EU-ES took 1.1687860488891602s
Interpretability | RDF structures check for Apertium RDF EU-ES took 0.17614221572875977s
Versatility | Serialization formats check for Apertium RDF EU-ES took 0.1813962459564209s
Availability | RDF dump link check for Apertium RDF EU-ES took 0.08885526657104492s
License | MR license check for Apertium RDF EU-ES took 0.1743602752685547s
License | HR license check for Apertium RDF EU-ES took 0.1986253261566162s
Amount of data | Number of property check for Apertium RDF EU-ES took 0.15031099319458008s
Understandability | Number of label check for Apertium RDF EU-ES took 0.19681239128112793s
Understandability | URI regex check for Apertium RDF EU-ES took 0.19576215744018555s
Understandability | Vocabs check for Apertium RDF EU-ES took 0.09781861305236816s
Verifiability | Authors check for Apertium RDF EU-ES took 0.20593714714050293s
Verifiability | Publishers check for Apertium RDF EU-ES took 0.14599871635437012s
Performance | Throughput check for Apertium RDF EU-ES took 10.658605337142944s
Amount of data | Check the number of entities for Apertium RDF EU-ES took 0.0005152225494384766s
Verifiability | Contribs. check for Apertium RDF EU-ES took 0.09723949432373047s
Interlinking | sameAs chians check for Apertium RDF EU-ES took 0.1560077667236328s
Interlinking | skos check for Apertium RDF EU-ES took 0.16374802589416504s
Interlinking | skos check for Apertium RDF EU-ES took 0.09333324432373047s
Timeliness | dataset update frequency check for Apertium RDF EU-ES took 0.09766244888305664s
Currency | Creation date check for Apertium RDF EU-ES took 0.16390538215637207s
Currency | Modification date check for Apertium RDF EU-ES took 0.17541027069091797s
Rep.Conc. | URIs length for Apertium RDF EU-ES took 92.14948606491089s
Interoperability | New vocabularies check for Apertium RDF EU-ES took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EU-ES took 0.15097308158874512s
Accuracy | Check Functional Property for Apertium RDF EU-ES took 0.1775496006011963s
Accuracy | Check Inverse Functional Property for Apertium RDF EU-ES took 0.09001326560974121s
Accuracy | Check Empty annotation labels for Apertium RDF EU-ES took 0.7513735294342041s
Accuracy | Check White space in annotation for Apertium RDF EU-ES took 0.010334014892578125s
Accuracy | Check Datatype consistency for Apertium RDF EU-ES took 2.642361879348755s
Consistency | Disjoint class check for Apertium RDF EU-ES took 0.10067081451416016s
Consistency | Check Misplaced properties for Apertium RDF EU-ES took 4.462054252624512s
Consistency | Misplaced classes for Apertium RDF EU-ES took 8.25623083114624s
Consistency | Check Ontology hijacking for Apertium RDF EU-ES took 96.69888305664062s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EU-ES took 1.4972121715545654s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EU-ES took 5.783952951431274s
Conciseness | Check Extensional conciseness for Apertium RDF EU-ES took 3.0147294998168945s
Conciseness | Check Intensional conciseness for Apertium RDF EU-ES took 0.16692113876342773s
Security | Sign check for Apertium RDF EU-ES took 0.08266615867614746s
Availability | Check URIs Dereferenciability for Apertium RDF EU-ES took 3.702901840209961s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.4492309093475342s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.0181124210357666s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0005114078521728516s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.482269287109375e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EU-ES took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EU-ES took 1.1205673217773438e-05s
INFO | --- Analysis for Apertium RDF EU-ES took 666.4620785713196s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 0.0998239517211914s
Availability | VoID file availability check for Apertium RDF FR-CA took 1.049041748046875e-05s
Extra | Recovery of all triples for Apertium RDF FR-CA took 277.0533072948456s
Performance | Total latancy measurement for Apertium RDF FR-CA took 0.5403311252593994s
Amount of data | Number of triples check for Apertium RDF FR-CA took 2.063807487487793s
Interoperability | New terms check for Apertium RDF FR-CA took 2.847571611404419s
Versatility | Languages check for Apertium RDF FR-CA took 45.22121214866638s
Interpretability | Number of blank nodes check for Apertium RDF FR-CA took 1.163419246673584s
Interpretability | RDF structures check for Apertium RDF FR-CA took 0.1751265525817871s
Versatility | Serialization formats check for Apertium RDF FR-CA took 0.17244768142700195s
Availability | RDF dump link check for Apertium RDF FR-CA took 0.0996854305267334s
License | MR license check for Apertium RDF FR-CA took 0.17075896263122559s
License | HR license check for Apertium RDF FR-CA took 0.17824220657348633s
Amount of data | Number of property check for Apertium RDF FR-CA took 0.17779541015625s
Understandability | Number of label check for Apertium RDF FR-CA took 0.2133626937866211s
Understandability | URI regex check for Apertium RDF FR-CA took 0.177473783493042s
Understandability | Vocabs check for Apertium RDF FR-CA took 0.09007811546325684s
Verifiability | Authors check for Apertium RDF FR-CA took 0.1946403980255127s
Verifiability | Publishers check for Apertium RDF FR-CA took 0.17110228538513184s
Performance | Throughput check for Apertium RDF FR-CA took 10.833913564682007s
Amount of data | Check the number of entities for Apertium RDF FR-CA took 8.821487426757812e-05s
Verifiability | Contribs. check for Apertium RDF FR-CA took 0.11537766456604004s
Interlinking | sameAs chians check for Apertium RDF FR-CA took 0.15340328216552734s
Interlinking | skos check for Apertium RDF FR-CA took 0.17460060119628906s
Interlinking | skos check for Apertium RDF FR-CA took 0.09788155555725098s
Timeliness | dataset update frequency check for Apertium RDF FR-CA took 0.08922457695007324s
Currency | Creation date check for Apertium RDF FR-CA took 0.18458795547485352s
Currency | Modification date check for Apertium RDF FR-CA took 0.162980318069458s
Rep.Conc. | URIs length for Apertium RDF FR-CA took 90.2458553314209s
Interoperability | New vocabularies check for Apertium RDF FR-CA took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF FR-CA took 0.1449284553527832s
Accuracy | Check Functional Property for Apertium RDF FR-CA took 0.1618022918701172s
Accuracy | Check Inverse Functional Property for Apertium RDF FR-CA took 0.09175372123718262s
Accuracy | Check Empty annotation labels for Apertium RDF FR-CA took 0.7317543029785156s
Accuracy | Check White space in annotation for Apertium RDF FR-CA took 0.010561704635620117s
Accuracy | Check Datatype consistency for Apertium RDF FR-CA took 2.654414653778076s
Consistency | Disjoint class check for Apertium RDF FR-CA took 0.09937787055969238s
Consistency | Check Misplaced properties for Apertium RDF FR-CA took 4.9926323890686035s
Consistency | Misplaced classes for Apertium RDF FR-CA took 8.274306774139404s
Consistency | Check Ontology hijacking for Apertium RDF FR-CA took 83.98406457901001s
Consistency | Check Invalid usage of undefined classes for Apertium RDF FR-CA took 1.6122395992279053s
Consistency | Check Invalid usage of undefined properties for Apertium RDF FR-CA took 5.6368231773376465s
Conciseness | Check Extensional conciseness for Apertium RDF FR-CA took 3.053715229034424s
Conciseness | Check Intensional conciseness for Apertium RDF FR-CA took 0.14827179908752441s
Security | Sign check for Apertium RDF FR-CA took 0.08370375633239746s
Availability | Check URIs Dereferenciability for Apertium RDF FR-CA took 3.358708620071411s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.42714715003967285s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.018207073211669922s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0005202293395996094s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 5.626678466796875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF FR-CA took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.1205673217773438e-05s
INFO | --- Analysis for Apertium RDF FR-CA took 637.9361758232117s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 0.09948563575744629s
Availability | VoID file availability check for Apertium RDF FR-ES took 5.9604644775390625e-06s
Extra | Recovery of all triples for Apertium RDF FR-ES took 274.3181948661804s
Performance | Total latancy measurement for Apertium RDF FR-ES took 0.5439634323120117s
Amount of data | Number of triples check for Apertium RDF FR-ES took 2.2456140518188477s
Interoperability | New terms check for Apertium RDF FR-ES took 2.7858681678771973s
Versatility | Languages check for Apertium RDF FR-ES took 45.699467182159424s
Interpretability | Number of blank nodes check for Apertium RDF FR-ES took 0.9588050842285156s
Interpretability | RDF structures check for Apertium RDF FR-ES took 0.16282153129577637s
Versatility | Serialization formats check for Apertium RDF FR-ES took 0.15874576568603516s
Availability | RDF dump link check for Apertium RDF FR-ES took 0.10188794136047363s
License | MR license check for Apertium RDF FR-ES took 0.14934325218200684s
License | HR license check for Apertium RDF FR-ES took 0.18899321556091309s
Amount of data | Number of property check for Apertium RDF FR-ES took 0.17810511589050293s
Understandability | Number of label check for Apertium RDF FR-ES took 0.2082056999206543s
Understandability | URI regex check for Apertium RDF FR-ES took 0.169189453125s
Understandability | Vocabs check for Apertium RDF FR-ES took 0.10742020606994629s
Verifiability | Authors check for Apertium RDF FR-ES took 0.20694351196289062s
Verifiability | Publishers check for Apertium RDF FR-ES took 0.15440964698791504s
Performance | Throughput check for Apertium RDF FR-ES took 10.651781558990479s
Amount of data | Check the number of entities for Apertium RDF FR-ES took 0.00014781951904296875s
Verifiability | Contribs. check for Apertium RDF FR-ES took 0.09046745300292969s
Interlinking | sameAs chians check for Apertium RDF FR-ES took 0.17482590675354004s
Interlinking | skos check for Apertium RDF FR-ES took 0.19211244583129883s
Interlinking | skos check for Apertium RDF FR-ES took 0.0955810546875s
Timeliness | dataset update frequency check for Apertium RDF FR-ES took 0.08069658279418945s
Currency | Creation date check for Apertium RDF FR-ES took 0.18083643913269043s
Currency | Modification date check for Apertium RDF FR-ES took 0.17039108276367188s
Rep.Conc. | URIs length for Apertium RDF FR-ES took 84.67048764228821s
Interoperability | New vocabularies check for Apertium RDF FR-ES took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF FR-ES took 0.15898990631103516s
Accuracy | Check Functional Property for Apertium RDF FR-ES took 0.14635276794433594s
Accuracy | Check Inverse Functional Property for Apertium RDF FR-ES took 0.07862448692321777s
Accuracy | Check Empty annotation labels for Apertium RDF FR-ES took 0.8305709362030029s
Accuracy | Check White space in annotation for Apertium RDF FR-ES took 0.010241031646728516s
Accuracy | Check Datatype consistency for Apertium RDF FR-ES took 2.737624168395996s
Consistency | Disjoint class check for Apertium RDF FR-ES took 0.10149073600769043s
Consistency | Check Misplaced properties for Apertium RDF FR-ES took 4.691828489303589s
Consistency | Misplaced classes for Apertium RDF FR-ES took 8.388264656066895s
Consistency | Check Ontology hijacking for Apertium RDF FR-ES took 85.60787868499756s
Consistency | Check Invalid usage of undefined classes for Apertium RDF FR-ES took 1.6084911823272705s
Consistency | Check Invalid usage of undefined properties for Apertium RDF FR-ES took 5.995347261428833s
Conciseness | Check Extensional conciseness for Apertium RDF FR-ES took 3.1392343044281006s
Conciseness | Check Intensional conciseness for Apertium RDF FR-ES took 0.16065549850463867s
Security | Sign check for Apertium RDF FR-ES took 0.08074307441711426s
Availability | Check URIs Dereferenciability for Apertium RDF FR-ES took 3.4808967113494873s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.7896809577941895s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.018117904663085938s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0005180835723876953s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 5.340576171875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF FR-ES took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.5497207641601562e-05s
INFO | --- Analysis for Apertium RDF FR-ES took 628.5702047348022s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 0.11617422103881836s
Availability | VoID file availability check for Apertium RDF OC-CA took 1.0251998901367188e-05s
Extra | Recovery of all triples for Apertium RDF OC-CA took 249.83054733276367s
Performance | Total latancy measurement for Apertium RDF OC-CA took 0.5221390724182129s
Amount of data | Number of triples check for Apertium RDF OC-CA took 2.111144542694092s
Interoperability | New terms check for Apertium RDF OC-CA took 2.7664802074432373s
Versatility | Languages check for Apertium RDF OC-CA took 45.49660062789917s
Interpretability | Number of blank nodes check for Apertium RDF OC-CA took 0.9197633266448975s
Interpretability | RDF structures check for Apertium RDF OC-CA took 0.1771993637084961s
Versatility | Serialization formats check for Apertium RDF OC-CA took 0.16121125221252441s
Availability | RDF dump link check for Apertium RDF OC-CA took 0.07895803451538086s
License | MR license check for Apertium RDF OC-CA took 0.15088725090026855s
License | HR license check for Apertium RDF OC-CA took 0.21672725677490234s
Amount of data | Number of property check for Apertium RDF OC-CA took 0.15883183479309082s
Understandability | Number of label check for Apertium RDF OC-CA took 0.20200419425964355s
Understandability | URI regex check for Apertium RDF OC-CA took 0.18582415580749512s
Understandability | Vocabs check for Apertium RDF OC-CA took 0.08916640281677246s
Verifiability | Authors check for Apertium RDF OC-CA took 0.20493841171264648s
Verifiability | Publishers check for Apertium RDF OC-CA took 0.16129851341247559s
Performance | Throughput check for Apertium RDF OC-CA took 10.85397744178772s
Amount of data | Check the number of entities for Apertium RDF OC-CA took 0.0001480579376220703s
Verifiability | Contribs. check for Apertium RDF OC-CA took 0.10730528831481934s
Interlinking | sameAs chians check for Apertium RDF OC-CA took 0.16356945037841797s
Interlinking | skos check for Apertium RDF OC-CA took 0.14742565155029297s
Interlinking | skos check for Apertium RDF OC-CA took 0.08330774307250977s
Timeliness | dataset update frequency check for Apertium RDF OC-CA took 0.07921433448791504s
Currency | Creation date check for Apertium RDF OC-CA took 0.1462385654449463s
Currency | Modification date check for Apertium RDF OC-CA took 0.16075682640075684s
Rep.Conc. | URIs length for Apertium RDF OC-CA took 93.10459399223328s
Interoperability | New vocabularies check for Apertium RDF OC-CA took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF OC-CA took 0.17269039154052734s
Accuracy | Check Functional Property for Apertium RDF OC-CA took 0.15511655807495117s
Accuracy | Check Inverse Functional Property for Apertium RDF OC-CA took 0.10084652900695801s
Accuracy | Check Empty annotation labels for Apertium RDF OC-CA took 0.7361783981323242s
Accuracy | Check White space in annotation for Apertium RDF OC-CA took 0.010127782821655273s
Accuracy | Check Datatype consistency for Apertium RDF OC-CA took 2.7013652324676514s
Consistency | Disjoint class check for Apertium RDF OC-CA took 0.09747195243835449s
Consistency | Check Misplaced properties for Apertium RDF OC-CA took 4.903659820556641s
Consistency | Misplaced classes for Apertium RDF OC-CA took 8.286998987197876s
Consistency | Check Ontology hijacking for Apertium RDF OC-CA took 96.05759358406067s
Consistency | Check Invalid usage of undefined classes for Apertium RDF OC-CA took 1.530280351638794s
Consistency | Check Invalid usage of undefined properties for Apertium RDF OC-CA took 5.786736249923706s
Conciseness | Check Extensional conciseness for Apertium RDF OC-CA took 3.026186943054199s
Conciseness | Check Intensional conciseness for Apertium RDF OC-CA took 0.156141996383667s
Security | Sign check for Apertium RDF OC-CA took 0.11725020408630371s
Availability | Check URIs Dereferenciability for Apertium RDF OC-CA took 3.7510931491851807s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.3409876823425293s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.021981000900268555s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0005297660827636719s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 5.412101745605469e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF OC-CA took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.0728836059570312e-05s
INFO | --- Analysis for Apertium RDF OC-CA took 613.7173020839691s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 0.07944297790527344s
Availability | VoID file availability check for Apertium RDF OC-ES took 1.239776611328125e-05s
Extra | Recovery of all triples for Apertium RDF OC-ES took 264.6349925994873s
Performance | Total latancy measurement for Apertium RDF OC-ES took 0.5948858261108398s
Amount of data | Number of triples check for Apertium RDF OC-ES took 2.121631145477295s
Interoperability | New terms check for Apertium RDF OC-ES took 2.770524501800537s
Versatility | Languages check for Apertium RDF OC-ES took 45.53617882728577s
Interpretability | Number of blank nodes check for Apertium RDF OC-ES took 0.9137609004974365s
Interpretability | RDF structures check for Apertium RDF OC-ES took 0.1541576385498047s
Versatility | Serialization formats check for Apertium RDF OC-ES took 0.1612682342529297s
Availability | RDF dump link check for Apertium RDF OC-ES took 0.08088254928588867s
License | MR license check for Apertium RDF OC-ES took 0.16527271270751953s
License | HR license check for Apertium RDF OC-ES took 0.17508649826049805s
Amount of data | Number of property check for Apertium RDF OC-ES took 0.16430258750915527s
Understandability | Number of label check for Apertium RDF OC-ES took 0.21612000465393066s
Understandability | URI regex check for Apertium RDF OC-ES took 0.16231131553649902s
Understandability | Vocabs check for Apertium RDF OC-ES took 0.09669971466064453s
Verifiability | Authors check for Apertium RDF OC-ES took 0.1890249252319336s
Verifiability | Publishers check for Apertium RDF OC-ES took 0.14516210556030273s
Performance | Throughput check for Apertium RDF OC-ES took 10.79938268661499s
Amount of data | Check the number of entities for Apertium RDF OC-ES took 8.726119995117188e-05s
Verifiability | Contribs. check for Apertium RDF OC-ES took 0.07897424697875977s
Interlinking | sameAs chians check for Apertium RDF OC-ES took 0.17847132682800293s
Interlinking | skos check for Apertium RDF OC-ES took 0.17795801162719727s
Interlinking | skos check for Apertium RDF OC-ES took 0.10931658744812012s
Timeliness | dataset update frequency check for Apertium RDF OC-ES took 0.09365987777709961s
Currency | Creation date check for Apertium RDF OC-ES took 0.1579735279083252s
Currency | Modification date check for Apertium RDF OC-ES took 0.17400479316711426s
Rep.Conc. | URIs length for Apertium RDF OC-ES took 84.50829100608826s
Interoperability | New vocabularies check for Apertium RDF OC-ES took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF OC-ES took 0.16235899925231934s
Accuracy | Check Functional Property for Apertium RDF OC-ES took 0.1571946144104004s
Accuracy | Check Inverse Functional Property for Apertium RDF OC-ES took 0.08056020736694336s
Accuracy | Check Empty annotation labels for Apertium RDF OC-ES took 0.8434393405914307s
Accuracy | Check White space in annotation for Apertium RDF OC-ES took 0.010225772857666016s
Accuracy | Check Datatype consistency for Apertium RDF OC-ES took 2.6591057777404785s
Consistency | Disjoint class check for Apertium RDF OC-ES took 0.09180355072021484s
Consistency | Check Misplaced properties for Apertium RDF OC-ES took 4.656848669052124s
Consistency | Misplaced classes for Apertium RDF OC-ES took 8.38096308708191s
Consistency | Check Ontology hijacking for Apertium RDF OC-ES took 90.8491358757019s
Consistency | Check Invalid usage of undefined classes for Apertium RDF OC-ES took 1.5197091102600098s
Consistency | Check Invalid usage of undefined properties for Apertium RDF OC-ES took 5.801470994949341s
Conciseness | Check Extensional conciseness for Apertium RDF OC-ES took 3.027340888977051s
Conciseness | Check Intensional conciseness for Apertium RDF OC-ES took 0.17857837677001953s
Security | Sign check for Apertium RDF OC-ES took 0.09345483779907227s
Availability | Check URIs Dereferenciability for Apertium RDF OC-ES took 3.4103922843933105s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.39026331901550293s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.01801776885986328s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0005218982696533203s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.935264587402344e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF OC-ES took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.0013580322265625e-05s
INFO | --- Analysis for Apertium RDF OC-ES took 615.6944687366486s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 0.09234142303466797s
Availability | VoID file availability check for Apertium RDF PT-CA took 1.049041748046875e-05s
Extra | Recovery of all triples for Apertium RDF PT-CA took 269.6483507156372s
Performance | Total latancy measurement for Apertium RDF PT-CA took 0.5663700103759766s
Amount of data | Number of triples check for Apertium RDF PT-CA took 2.094724416732788s
Interoperability | New terms check for Apertium RDF PT-CA took 2.6636974811553955s
Versatility | Languages check for Apertium RDF PT-CA took 45.17494797706604s
Interpretability | Number of blank nodes check for Apertium RDF PT-CA took 0.9669654369354248s
Interpretability | RDF structures check for Apertium RDF PT-CA took 0.16935062408447266s
Versatility | Serialization formats check for Apertium RDF PT-CA took 0.1718757152557373s
Availability | RDF dump link check for Apertium RDF PT-CA took 0.07839560508728027s
License | MR license check for Apertium RDF PT-CA took 0.18535494804382324s
License | HR license check for Apertium RDF PT-CA took 0.1993401050567627s
Amount of data | Number of property check for Apertium RDF PT-CA took 0.16709327697753906s
Understandability | Number of label check for Apertium RDF PT-CA took 0.19442224502563477s
Understandability | URI regex check for Apertium RDF PT-CA took 0.18130731582641602s
Understandability | Vocabs check for Apertium RDF PT-CA took 0.08159375190734863s
Verifiability | Authors check for Apertium RDF PT-CA took 0.21802520751953125s
Verifiability | Publishers check for Apertium RDF PT-CA took 0.17178916931152344s
Performance | Throughput check for Apertium RDF PT-CA took 10.762266635894775s
Amount of data | Check the number of entities for Apertium RDF PT-CA took 0.00043511390686035156s
Verifiability | Contribs. check for Apertium RDF PT-CA took 0.08896040916442871s
Interlinking | sameAs chians check for Apertium RDF PT-CA took 0.14619898796081543s
Interlinking | skos check for Apertium RDF PT-CA took 0.16674065589904785s
Interlinking | skos check for Apertium RDF PT-CA took 0.11670160293579102s
Timeliness | dataset update frequency check for Apertium RDF PT-CA took 0.09053468704223633s
Currency | Creation date check for Apertium RDF PT-CA took 0.14698123931884766s
Currency | Modification date check for Apertium RDF PT-CA took 0.15791082382202148s
Rep.Conc. | URIs length for Apertium RDF PT-CA took 93.31006789207458s
Interoperability | New vocabularies check for Apertium RDF PT-CA took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF PT-CA took 0.19876408576965332s
Accuracy | Check Functional Property for Apertium RDF PT-CA took 0.14787960052490234s
Accuracy | Check Inverse Functional Property for Apertium RDF PT-CA took 0.11789298057556152s
Accuracy | Check Empty annotation labels for Apertium RDF PT-CA took 0.8277134895324707s
Accuracy | Check White space in annotation for Apertium RDF PT-CA took 0.010288715362548828s
Accuracy | Check Datatype consistency for Apertium RDF PT-CA took 2.7848527431488037s
Consistency | Disjoint class check for Apertium RDF PT-CA took 0.09958076477050781s
Consistency | Check Misplaced properties for Apertium RDF PT-CA took 4.580114841461182s
Consistency | Misplaced classes for Apertium RDF PT-CA took 8.381948471069336s
Consistency | Check Ontology hijacking for Apertium RDF PT-CA took 98.95918464660645s
Consistency | Check Invalid usage of undefined classes for Apertium RDF PT-CA took 1.5000851154327393s
Consistency | Check Invalid usage of undefined properties for Apertium RDF PT-CA took 6.080090045928955s
Conciseness | Check Extensional conciseness for Apertium RDF PT-CA took 3.0404412746429443s
Conciseness | Check Intensional conciseness for Apertium RDF PT-CA took 0.16429853439331055s
Security | Sign check for Apertium RDF PT-CA took 0.08320283889770508s
Availability | Check URIs Dereferenciability for Apertium RDF PT-CA took 3.3410732746124268s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.6279036998748779s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.018180131912231445s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0005185604095458984s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.553794860839844e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF PT-CA took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.430511474609375e-05s
INFO | --- Analysis for Apertium RDF PT-CA took 634.8781907558441s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 0.09084248542785645s
Availability | VoID file availability check for Apertium RDF PT-GL took 1.1682510375976562e-05s
Extra | Recovery of all triples for Apertium RDF PT-GL took 270.7880492210388s
Performance | Total latancy measurement for Apertium RDF PT-GL took 0.5847263336181641s
Amount of data | Number of triples check for Apertium RDF PT-GL took 2.2069804668426514s
Interoperability | New terms check for Apertium RDF PT-GL took 2.9459967613220215s
Versatility | Languages check for Apertium RDF PT-GL took 44.55377221107483s
Interpretability | Number of blank nodes check for Apertium RDF PT-GL took 1.1465427875518799s
Interpretability | RDF structures check for Apertium RDF PT-GL took 0.16566705703735352s
Versatility | Serialization formats check for Apertium RDF PT-GL took 0.16794276237487793s
Availability | RDF dump link check for Apertium RDF PT-GL took 0.09053683280944824s
License | MR license check for Apertium RDF PT-GL took 0.1483750343322754s
License | HR license check for Apertium RDF PT-GL took 0.19614553451538086s
Amount of data | Number of property check for Apertium RDF PT-GL took 0.15196490287780762s
Understandability | Number of label check for Apertium RDF PT-GL took 0.19808602333068848s
Understandability | URI regex check for Apertium RDF PT-GL took 0.2097175121307373s
Understandability | Vocabs check for Apertium RDF PT-GL took 0.10802483558654785s
Verifiability | Authors check for Apertium RDF PT-GL took 0.2150726318359375s
Verifiability | Publishers check for Apertium RDF PT-GL took 0.1608726978302002s
Performance | Throughput check for Apertium RDF PT-GL took 10.699420928955078s
Amount of data | Check the number of entities for Apertium RDF PT-GL took 9.393692016601562e-05s
Verifiability | Contribs. check for Apertium RDF PT-GL took 0.11534738540649414s
Interlinking | sameAs chians check for Apertium RDF PT-GL took 0.14415836334228516s
Interlinking | skos check for Apertium RDF PT-GL took 0.18239402770996094s
Interlinking | skos check for Apertium RDF PT-GL took 0.1091454029083252s
Timeliness | dataset update frequency check for Apertium RDF PT-GL took 0.0924837589263916s
Currency | Creation date check for Apertium RDF PT-GL took 0.16411471366882324s
Currency | Modification date check for Apertium RDF PT-GL took 0.16298842430114746s
Rep.Conc. | URIs length for Apertium RDF PT-GL took 88.29722189903259s
Interoperability | New vocabularies check for Apertium RDF PT-GL took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF PT-GL took 0.16231870651245117s
Accuracy | Check Functional Property for Apertium RDF PT-GL took 0.16225194931030273s
Accuracy | Check Inverse Functional Property for Apertium RDF PT-GL took 0.10940694808959961s
Accuracy | Check Empty annotation labels for Apertium RDF PT-GL took 0.8104703426361084s
Accuracy | Check White space in annotation for Apertium RDF PT-GL took 0.010292530059814453s
Accuracy | Check Datatype consistency for Apertium RDF PT-GL took 2.7073750495910645s
Consistency | Disjoint class check for Apertium RDF PT-GL took 0.11937594413757324s
Consistency | Check Misplaced properties for Apertium RDF PT-GL took 4.512880802154541s
Consistency | Misplaced classes for Apertium RDF PT-GL took 8.277467250823975s
Consistency | Check Ontology hijacking for Apertium RDF PT-GL took 104.73682475090027s
Consistency | Check Invalid usage of undefined classes for Apertium RDF PT-GL took 1.5519444942474365s
Consistency | Check Invalid usage of undefined properties for Apertium RDF PT-GL took 5.765522718429565s
Conciseness | Check Extensional conciseness for Apertium RDF PT-GL took 3.1223807334899902s
Conciseness | Check Intensional conciseness for Apertium RDF PT-GL took 0.1570112705230713s
Security | Sign check for Apertium RDF PT-GL took 0.08369660377502441s
Availability | Check URIs Dereferenciability for Apertium RDF PT-GL took 3.624210834503174s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.37477803230285645s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.018280744552612305s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0005109310150146484s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.76837158203125e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF PT-GL took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF PT-GL took 1.3113021850585938e-05s
INFO | --- Analysis for Apertium RDF PT-GL took 637.8790121078491s
Availability | SPARQL endpoint availability check for AragoDBPedia took 0.6594195365905762s
Availability | VoID file availability check for AragoDBPedia took 1.0013580322265625e-05s
Extra | Recovery of all triples for AragoDBPedia took 2.848534107208252s
Performance | Total latancy measurement for AragoDBPedia took 1.9203076362609863s
Amount of data | Number of triples check for AragoDBPedia took 1.4005928039550781s
Interoperability | New terms check for AragoDBPedia took 2.0789151191711426s
Versatility | Languages check for AragoDBPedia took 60.54295468330383s
Interpretability | Number of blank nodes check for AragoDBPedia took 1.605863094329834s
Security | Check HTTPS for AragoDBPedia took 0.19745659828186035s
Interpretability | RDF structures check for AragoDBPedia took 0.6856653690338135s
Versatility | Serialization formats check for AragoDBPedia took 0.428131103515625s
Availability | RDF dump link check for AragoDBPedia took 0.4085578918457031s
License | MR license check for AragoDBPedia took 0.553917646408081s
License | HR license check for AragoDBPedia took 4.353907108306885s
Amount of data | Number of property check for AragoDBPedia took 0.42122840881347656s
Understandability | Number of label check for AragoDBPedia took 0.6281898021697998s
Understandability | URI regex check for AragoDBPedia took 0.9503540992736816s
Understandability | Vocabs check for AragoDBPedia took 0.40688037872314453s
Verifiability | Authors check for AragoDBPedia took 0.7744777202606201s
Verifiability | Publishers check for AragoDBPedia took 0.5262646675109863s
Performance | Throughput check for AragoDBPedia took 11.703075408935547s
Amount of data | Check the number of entities for AragoDBPedia took 9.751319885253906e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.4160487651824951s
Interlinking | sameAs chians check for AragoDBPedia took 0.41628098487854004s
Interlinking | skos check for AragoDBPedia took 0.5106534957885742s
Interlinking | skos check for AragoDBPedia took 0.36083984375s
Timeliness | dataset update frequency check for AragoDBPedia took 0.45053744316101074s
Currency | Creation date check for AragoDBPedia took 0.4011070728302002s
Currency | Modification date check for AragoDBPedia took 0.7668731212615967s
Rep.Conc. | URIs length for AragoDBPedia took 5.217885255813599s
Interoperability | New vocabularies check for AragoDBPedia took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.41828203201293945s
Accuracy | Check Functional Property for AragoDBPedia took 0.39827752113342285s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.4281730651855469s
Accuracy | Check Empty annotation labels for AragoDBPedia took 0.9402599334716797s
Accuracy | Check White space in annotation for AragoDBPedia took 0.030802011489868164s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.0287783145904541s
Consistency | Disjoint class check for AragoDBPedia took 0.4219551086425781s
Consistency | Check Misplaced properties for AragoDBPedia took 3.776362180709839s
Consistency | Misplaced classes for AragoDBPedia took 0.6509461402893066s
Consistency | Check Ontology hijacking for AragoDBPedia took 2.575061798095703s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.43243408203125s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 4.74487042427063s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.03431534767150879s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.5463762283325195s
Security | Sign check for AragoDBPedia took 0.5436568260192871s
Availability | Check URIs Dereferenciability for AragoDBPedia took 3136.48286986351s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 20.43665838241577s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.019098281860351562s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0005605220794677734s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 4.649162292480469e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.6689300537109375e-06s
Believability | Calculation of trust value for AragoDBPedia took 1.1920928955078125e-05s
INFO | --- Analysis for AragoDBPedia took 3371.0981855392456s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.416348695755005s
Availability | VoID file availability check for Archives Hub Linked Data took 20.101998567581177s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.327404260635376s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.018354177474975586s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0005533695220947266s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.6743621826171875e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 1.2159347534179688e-05s
INFO | --- Analysis for Archives Hub Linked Data took 132.55852484703064s
Availability | SPARQL endpoint availability check for Archivi ISMA took 30.074353218078613s
Availability | VoID file availability check for Archivi ISMA took 20.00702142715454s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.533550500869751s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.019043445587158203s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.000560760498046875s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 1.9311904907226562e-05s
Believability | Calculation of trust value for Archivi ISMA took 9.775161743164062e-06s
INFO | --- Analysis for Archivi ISMA took 92.42135834693909s
Availability | SPARQL endpoint availability check for ARIADNE took 0.5257217884063721s
Availability | VoID file availability check for ARIADNE took 1.239776611328125e-05s
Completeness | Calculation of interlinking completeness for ARIADNE took 1.9901340007781982s
Reputation | Calculation of the PageRank for ARIADNE took 0.018195152282714844s
Interlinking | Calculation of Degree of Connection for ARIADNE took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ARIADNE took 0.0005083084106445312s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 1.239776611328125e-05s
Believability | Calculation of trust value for ARIADNE took 1.0967254638671875e-05s
INFO | --- Analysis for ARIADNE took 137.9665505886078s
Availability | SPARQL endpoint availability check for Aristotle University took 2.0009706020355225s
Availability | VoID file availability check for Aristotle University took 0.01616048812866211s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.3182032108306885s
Reputation | Calculation of the PageRank for Aristotle University took 0.018397092819213867s
Interlinking | Calculation of Degree of Connection for Aristotle University took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Aristotle University took 0.0005204677581787109s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 2.0742416381835938e-05s
Believability | Calculation of trust value for Aristotle University took 1.1444091796875e-05s
INFO | --- Analysis for Aristotle University took 7.890782117843628s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 24.48649263381958s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 4.76837158203125e-06s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.32430052757263184s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.018111467361450195s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0005390644073486328s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 1.2636184692382812e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 1.239776611328125e-05s
INFO | --- Analysis for Transcription profiling of human, chimp and mouse brain took 49.42418026924133s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 8.511543273925781e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 8.106231689453125e-06s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.4805622100830078s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.020972013473510742s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0005321502685546875s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.3828277587890625e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.1920928955078125e-05s
INFO | --- Analysis for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 3.338887929916382s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 22.872140169143677s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 8.344650268554688e-06s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.43083643913269043s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.019846677780151367s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0006132125854492188s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 4.482269287109375e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.0728836059570312e-05s
INFO | --- Analysis for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 63.18618702888489s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 8.726119995117188e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 2.4592535495758057s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.3138692378997803s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.018369197845458984s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0005652904510498047s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00010347366333007812s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.239776611328125e-05s
INFO | --- Analysis for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 12.693859338760376s
Availability | SPARQL endpoint availability check for Arthroscopy community took 0.00012683868408203125s
Availability | VoID file availability check for Arthroscopy community took 2.5403859615325928s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.8681862354278564s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.018317461013793945s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0005271434783935547s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 9.965896606445312e-05s
Believability | Calculation of trust value for Arthroscopy community took 1.2159347534179688e-05s
INFO | --- Analysis for Arthroscopy community took 15.985322713851929s
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 9.250640869140625e-05s
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 5.4836273193359375e-06s
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 1.1039276123046875s
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.01870870590209961s
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.0013580322265625e-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.0005366802215576172s
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.0108642578125e-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 1.3113021850585938e-05s
INFO | --- Analysis for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 7.424142599105835s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 9.512901306152344e-05s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 6.9141387939453125e-06s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 2.4936845302581787s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.019934892654418945s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0005402565002441406s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.935264587402344e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 1.1205673217773438e-05s
INFO | --- Analysis for Database of Names and Biographies (DNB) took 6.500253200531006s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.416175842285156e-05s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 6.198883056640625e-06s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.5774140357971191s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020768165588378906s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006337165832519531s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.58306884765625e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.2636184692382812e-05s
INFO | --- Analysis for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.014688968658447s
Availability | SPARQL endpoint availability check for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 4.130568504333496s
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 1.8500909805297852s
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 2.2028439044952393s
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.019495725631713867s
Interlinking | Calculation of Degree of Connection for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.0005342960357666016s
Interlinking | Calculation of Clustering coefficient for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 8.177757263183594e-05s
Believability | Calculation of trust value for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 8.58306884765625e-06s
INFO | --- Analysis for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 20.83350419998169s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.8494138717651367s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.8850805759429932s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.2433860301971436s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0194399356842041s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006029605865478516s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.560585021972656e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1920928955078125e-05s
INFO | --- Analysis for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 21.376559019088745s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.8501601219177246s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 1.8575737476348877s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.5265381336212158s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.018540143966674805s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0005364418029785156s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.291534423828125e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 1.2636184692382812e-05s
INFO | --- Analysis for Database of Chinese Rare Books (CRB) took 19.653482675552368s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.9978294372558594s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 6.94190239906311s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.6246387958526611s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.018778085708618164s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0005357265472412109s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.226799011230469e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.2874603271484375e-05s
INFO | --- Analysis for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 25.418179988861084s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.817950487136841s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 1.8505408763885498s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.47652673721313477s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.0187225341796875s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0005552768707275391s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.3855438232421875e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 1.1205673217773438e-05s
INFO | --- Analysis for Database of Qing Official Titles (DQOT) took 17.647648334503174s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.8467471599578857s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.9310777187347412s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.710115909576416s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.018454790115356445s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0005397796630859375s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.772445678710938e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.1682510375976562e-05s
INFO | --- Analysis for Database of the Han Wooden Slips Character Dictionary (WCD) took 19.807050466537476s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 4.10895848274231s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 1.9263837337493896s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 2.3175549507141113s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.019044876098632812s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0005228519439697266s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.130073547363281e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.2874603271484375e-05s
INFO | --- Analysis for Linked Taiwan Artists (LTA) took 23.147658824920654s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 3.352250814437866s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.8888723850250244s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.3268857002258301s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.018802642822265625s
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.0251998901367188e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0005483627319335938s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.173683166503906e-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.867813110351562e-06s
INFO | --- Analysis for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 18.074836254119873s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.815335750579834s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.8514416217803955s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.9450337886810303s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.018654584884643555s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0005512237548828125s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.3882598876953125e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.049041748046875e-05s
INFO | --- Analysis for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 17.368550300598145s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.8597986698150635s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.8843402862548828s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.4444870948791504s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.018787145614624023s
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.000537872314453125s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 8.320808410644531e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.1920928955078125e-05s
INFO | --- Analysis for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 18.268059492111206s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 9.34600830078125e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 3.2319178581237793s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 1.8748304843902588s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.018498897552490234s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0005414485931396484s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.67572021484375e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.1682510375976562e-05s
INFO | --- Analysis for Atlante Sintattico d'Italia (ASIt) took 12.680293083190918s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 8.58306884765625e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.01727581024169922s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.293670654296875s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.018450021743774414s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0005309581756591797s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 4.0531158447265625e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 1.1920928955078125e-05s
INFO | --- Analysis for Automated Similarity Judgment Program lexical data took 6.129988193511963s
Availability | SPARQL endpoint availability check for ASN:US took 1.9890289306640625s
Availability | VoID file availability check for ASN:US took 0.5966975688934326s
Completeness | Calculation of interlinking completeness for ASN:US took 0.5753929615020752s
Reputation | Calculation of the PageRank for ASN:US took 0.018528223037719727s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0005714893341064453s
Interlinking | Calculation of Clustering coefficient for ASN:US took 6.794929504394531e-05s
Believability | Calculation of trust value for ASN:US took 1.2874603271484375e-05s
INFO | --- Analysis for ASN:US took 13.847118139266968s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 0.0001423358917236328s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 1.031592607498169s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.3572096824645996s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.018235206604003906s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0005474090576171875s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 1.1444091796875e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 8.821487426757812e-06s
INFO | --- Analysis for Talis Aspire - Manchester Metropolitan University took 11.196778059005737s
Availability | SPARQL endpoint availability check for associations took 8.7738037109375e-05s
Availability | VoID file availability check for associations took 0.5660622119903564s
Completeness | Calculation of interlinking completeness for associations took 0.6005702018737793s
Reputation | Calculation of the PageRank for associations took 0.018578767776489258s
Interlinking | Calculation of Degree of Connection for associations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for associations took 0.0005185604095458984s
Interlinking | Calculation of Clustering coefficient for associations took 7.152557373046875e-05s
Interoperability | Check the re-using of existing vocabs for associations took 0.9339232444763184s
Believability | Calculation of trust value for associations took 1.3589859008789062e-05s
INFO | --- Analysis for associations took 17.488890171051025s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 1.0885391235351562s
Availability | VoID file availability check for ATC publikovaná SÚKL took 6.67572021484375e-06s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 2.048980951309204s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.01831984519958496s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0005221366882324219s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 1.2636184692382812e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 1.2159347534179688e-05s
INFO | --- Analysis for ATC publikovaná SÚKL took 7.736185312271118s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 4.887580871582031e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 1.642676591873169s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 1.121495246887207s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.019315242767333984s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0005338191986083984s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 8.845329284667969e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.1205673217773438e-05s
INFO | --- Analysis for Athelia RFID, a global knowledge network of RFID technology took 17.052171230316162s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 5.227681875228882s
Availability | VoID file availability check for AUEB Linked Open Data took 7.152557373046875e-06s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.3314938545227051s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.01817917823791504s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0005538463592529297s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 1.2159347534179688e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 1.33514404296875e-05s
INFO | --- Analysis for AUEB Linked Open Data took 8.437462329864502s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.5821897983551025s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.471998929977417s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.3483455181121826s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.02128314971923828s
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.000518798828125s
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 1.2159347534179688e-05s
INFO | --- Analysis for Alpine Ski Racers of Austria took 3.7926251888275146s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24596047401428223s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.20183539390563965s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 13.507298707962036s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.5959696769714355s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0252351760864s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.493635654449463s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1041855812073s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 299.3732063770294s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.23416733741760254s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.21293234825134277s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.18865704536437988s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11292052268981934s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 198.40707325935364s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0564706325531s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.18964624404907227s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1047134399414s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24378037452697754s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2068617343902588s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.820590496063232s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 848.6351764202118s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.722197771072388s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.00013327598571777344s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 164.78385996818542s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0791826248169s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16002845764160156s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14356756210327148s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1407032012939453s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 183.74773645401s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2704198360443115s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 160.83681917190552s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16523027420043945s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 9.830682277679443s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.446343183517456s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.777368545532227s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.19240593910217285s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2801337242126465s
Consistency | Misplaced classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.7999906539917s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 13.221981048583984s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 21295.79933977127s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.728663682937622s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.9280388355255127s
Conciseness | Check Intensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13604021072387695s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1403975486755371s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 327.2263882160187s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.1066339015960693s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.01960277557373047s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0005736351013183594s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.605552673339844e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.6689300537109375e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 9.5367431640625e-06s
INFO | --- Analysis for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 26285.940458774567s
Availability | SPARQL endpoint availability check for BabelNet took 0.6024477481842041s
Availability | VoID file availability check for BabelNet took 1.0013580322265625e-05s
Completeness | Calculation of interlinking completeness for BabelNet took 0.3091392517089844s
Reputation | Calculation of the PageRank for BabelNet took 0.018877029418945312s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0005259513854980469s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.0001614093780517578s
Believability | Calculation of trust value for BabelNet took 1.1205673217773438e-05s
INFO | --- Analysis for BabelNet took 5.264428615570068s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 8.630752563476562e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.991340160369873s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 1.0401194095611572s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.018416166305541992s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0005102157592773438s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 1.3113021850585938e-05s
Believability | Calculation of trust value for Bacevicius.lt took 6.461143493652344e-05s
INFO | --- Analysis for Bacevicius.lt took 6.245169639587402s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.6328384876251221s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.7775764465332031s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.6411032676696777s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.018451929092407227s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0005316734313964844s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.601478576660156e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 1.2636184692382812e-05s
INFO | --- Analysis for Basisregistratie Adressen en Gebouwen took 7.0901198387146s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.5809800624847412s
Availability | VoID file availability check for 红色经典歌曲 took 0.017027616500854492s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.5423526763916016s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.018483877182006836s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.000518798828125s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 1.3589859008789062e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.2159347534179688e-05s
INFO | --- Analysis for 红色经典歌曲 took 4.4827916622161865s
Availability | SPARQL endpoint availability check for baixue composer took 9.012222290039062e-05s
Availability | VoID file availability check for baixue composer took 5.4836273193359375e-06s
Completeness | Calculation of interlinking completeness for baixue composer took 0.3493509292602539s
Reputation | Calculation of the PageRank for baixue composer took 0.019150495529174805s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0005290508270263672s
Interlinking | Calculation of Clustering coefficient for baixue composer took 1.239776611328125e-05s
Believability | Calculation of trust value for baixue composer took 1.2636184692382812e-05s
INFO | --- Analysis for baixue composer took 3.4990286827087402s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 9.036064147949219e-05s
Availability | VoID file availability check for 红色经典歌曲 took 6.198883056640625e-06s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.5672483444213867s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.021108150482177734s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0005185604095458984s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 1.1920928955078125e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.5020370483398438e-05s
INFO | --- Analysis for 红色经典歌曲 took 4.5447540283203125s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 8.58306884765625e-05s
Availability | VoID file availability check for 红色经典歌曲 took 5.4836273193359375e-06s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.39356422424316406s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.018232107162475586s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0005176067352294922s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 1.3113021850585938e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.2874603271484375e-05s
INFO | --- Analysis for 红色经典歌曲 took 2.463258743286133s
Availability | SPARQL endpoint availability check for BAMS took 8.344650268554688e-05s
Availability | VoID file availability check for BAMS took 20.24270534515381s
Completeness | Calculation of interlinking completeness for BAMS took 0.3111143112182617s
Reputation | Calculation of the PageRank for BAMS took 0.018435239791870117s
Interlinking | Calculation of Degree of Connection for BAMS took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0005180835723876953s
Interlinking | Calculation of Clustering coefficient for BAMS took 2.1457672119140625e-05s
Believability | Calculation of trust value for BAMS took 1.0251998901367188e-05s
INFO | --- Analysis for BAMS took 30.318026542663574s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 8.416175842285156e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 7.152557373046875e-06s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.3047926425933838s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.018253326416015625s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0006053447723388672s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 5.0067901611328125e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 9.775161743164062e-06s
INFO | --- Analysis for Basque EuroWordNet-lemon lexicon (3.0) took 2.235999345779419s
Availability | SPARQL endpoint availability check for BBC Music took 0.4022648334503174s
Availability | VoID file availability check for BBC Music took 0.2304520606994629s
Completeness | Calculation of interlinking completeness for BBC Music took 0.43499231338500977s
Reputation | Calculation of the PageRank for BBC Music took 0.018265485763549805s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0005605220794677734s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00012946128845214844s
Believability | Calculation of trust value for BBC Music took 1.4781951904296875e-05s
INFO | --- Analysis for BBC Music took 4.1826560497283936s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.2901921272277832s
Availability | VoID file availability check for BBC Programmes took 0.38941526412963867s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.30585265159606934s
Reputation | Calculation of the PageRank for BBC Programmes took 0.01965641975402832s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0005161762237548828s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010085105895996094s
Believability | Calculation of trust value for BBC Programmes took 1.4781951904296875e-05s
INFO | --- Analysis for BBC Programmes took 9.663374662399292s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.26795339584350586s
Availability | VoID file availability check for BBC Wildlife Finder took 0.3222618103027344s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 1.106041431427002s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.02021169662475586s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0005376338958740234s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010085105895996094s
Believability | Calculation of trust value for BBC Wildlife Finder took 1.2636184692382812e-05s
INFO | --- Analysis for BBC Wildlife Finder took 11.04283356666565s
Availability | SPARQL endpoint availability check for BBOP took 8.487701416015625e-05s
Availability | VoID file availability check for BBOP took 0.5383634567260742s
Completeness | Calculation of interlinking completeness for BBOP took 0.3416109085083008s
Reputation | Calculation of the PageRank for BBOP took 0.020310640335083008s
Interlinking | Calculation of Degree of Connection for BBOP took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for BBOP took 0.00055694580078125s
Interlinking | Calculation of Clustering coefficient for BBOP took 1.2159347534179688e-05s
Believability | Calculation of trust value for BBOP took 9.775161743164062e-06s
INFO | --- Analysis for BBOP took 25.70239567756653s
Availability | SPARQL endpoint availability check for BBOP took 7.390975952148438e-05s
Availability | VoID file availability check for BBOP took 0.4724757671356201s
Completeness | Calculation of interlinking completeness for BBOP took 0.40403223037719727s
Reputation | Calculation of the PageRank for BBOP took 0.018067598342895508s
Interlinking | Calculation of Degree of Connection for BBOP took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0005152225494384766s
Interlinking | Calculation of Clustering coefficient for BBOP took 1.1920928955078125e-05s
Believability | Calculation of trust value for BBOP took 1.3828277587890625e-05s
INFO | --- Analysis for BBOP took 19.373991012573242s
Availability | SPARQL endpoint availability check for Bdgp took 1.3686251640319824s
Availability | VoID file availability check for Bdgp took 0.7354505062103271s
Completeness | Calculation of interlinking completeness for Bdgp took 0.6375319957733154s
Reputation | Calculation of the PageRank for Bdgp took 0.0181732177734375s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0005261898040771484s
Interlinking | Calculation of Clustering coefficient for Bdgp took 1.1444091796875e-05s
Believability | Calculation of trust value for Bdgp took 1.1920928955078125e-05s
INFO | --- Analysis for Bdgp took 5.415372371673584s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 5.087568283081055s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 3.982232093811035s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.4782447814941406s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.01801919937133789s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0005211830139160156s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.4849853515625e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 7.867813110351562e-06s
INFO | --- Analysis for EU: fintrans.publicdata.eu took 18.41995620727539s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 4.076957702636719e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.01458597183227539s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.30028653144836426s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.01795339584350586s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0005242824554443359s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 1.2159347534179688e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 8.106231689453125e-06s
INFO | --- Analysis for Berlin Offener Haushalt took 2.5163729190826416s
Availability | SPARQL endpoint availability check for berlios took 8.511543273925781e-05s
Availability | VoID file availability check for berlios took 6.67572021484375e-06s
Completeness | Calculation of interlinking completeness for berlios took 0.49734926223754883s
Reputation | Calculation of the PageRank for berlios took 0.019620656967163086s
Interlinking | Calculation of Degree of Connection for berlios took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for berlios took 0.0005135536193847656s
Interlinking | Calculation of Clustering coefficient for berlios took 8.296966552734375e-05s
Believability | Calculation of trust value for berlios took 1.1682510375976562e-05s
INFO | --- Analysis for berlios took 4.639461994171143s
Availability | SPARQL endpoint availability check for Between Our Worlds took 0.00012445449829101562s
Availability | VoID file availability check for Between Our Worlds took 0.5173177719116211s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.43700242042541504s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.01836371421813965s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0005276203155517578s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 6.4849853515625e-05s
Believability | Calculation of trust value for Between Our Worlds took 1.2159347534179688e-05s
INFO | --- Analysis for Between Our Worlds took 10.612815618515015s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.13625502586364746s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.01434636116027832s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.49295592308044434s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.018842220306396484s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0005354881286621094s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.083747863769531e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.0013580322265625e-05s
INFO | --- Analysis for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 5.082243919372559s
Availability | SPARQL endpoint availability check for BibBase took 0.23789691925048828s
Availability | VoID file availability check for BibBase took 0.01573014259338379s
Completeness | Calculation of interlinking completeness for BibBase took 0.45097875595092773s
Reputation | Calculation of the PageRank for BibBase took 0.018122434616088867s
Interlinking | Calculation of Degree of Connection for BibBase took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0005242824554443359s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.369850158691406e-05s
Believability | Calculation of trust value for BibBase took 1.1682510375976562e-05s
INFO | --- Analysis for BibBase took 2.5998010635375977s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 8.630752563476562e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.9051637649536133s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.8103675842285156s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.020799875259399414s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0005285739898681641s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 9.5367431640625e-05s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 1.1444091796875e-05s
INFO | --- Analysis for Biblioteca Escolar Digital CITA took 13.104599714279175s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 8.320808410644531e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 8.344650268554688e-06s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.46094775199890137s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.01967477798461914s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0005371570587158203s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.00010848045349121094s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 1.2159347534179688e-05s
INFO | --- Analysis for Biblioteca Nacional Escolar (BNEscolar) took 7.473299264907837s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 8.463859558105469e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 7.152557373046875e-06s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.4462094306945801s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.020127296447753906s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0005095005035400391s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.4066696166992188e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.2636184692382812e-05s
INFO | --- Analysis for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 4.2439844608306885s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.00010228157043457031s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.7132689952850342s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 1.6597490310668945s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.019898414611816406s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0005214214324951172s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.457069396972656e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 1.1682510375976562e-05s
INFO | --- Analysis for BibSonomy - The blue social bookmark and publication sharing system. took 6.85450553894043s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 8.296966552734375e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 1.0349385738372803s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.35449838638305664s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.018169641494750977s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0005524158477783203s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 1.3113021850585938e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 9.775161743164062e-06s
INFO | --- Analysis for Billion Triples Challenge Dataset 2008 took 6.482077121734619s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 4.124641418457031e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.1981518268585205s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.33156728744506836s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.01838064193725586s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0008103847503662109s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 1.3828277587890625e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 7.867813110351562e-06s
INFO | --- Analysis for Billion Triples Challenge Dataset 2010 took 3.3933990001678467s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 1.9181795120239258s
Availability | VoID file availability check for Bio2RDF::ACFSID took 7.62939453125e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.34831905364990234s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.01850414276123047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0005142688751220703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 1.430511474609375e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 1.4066696166992188e-05s
INFO | --- Analysis for Bio2RDF::ACFSID took 17.232651472091675s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 0.37624430656433105s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.7392692565917969s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 19.16254997253418s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.5357301235198975s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 49.459922790527344s
Interoperability | New terms check for Bio2RDF::Affymetrix took 40.039578437805176s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.12485361099243s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.16956329345703125s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.3868873119354248s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.15282654762268066s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 1.1668968200683594s
License | MR license check for Bio2RDF::Affymetrix took 0.5588791370391846s
License | HR license check for Bio2RDF::Affymetrix took 60.10737657546997s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.18663954734802246s
Understandability | Number of label check for Bio2RDF::Affymetrix took 10.522636413574219s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.8963947296142578s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.17440009117126465s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.44850850105285645s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.3776993751525879s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.451127290725708s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.5888354778289795s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.15753984451293945s
Interlinking | skos check for Bio2RDF::Affymetrix took 1.132598638534546s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.22547698020935059s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.35362792015075684s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.9025187492370605s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.18187594413757324s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 107.11034965515137s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 21.18753695487976s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.3852717876434326s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.1755983829498291s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.12314081192016602s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 6.833249568939209s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.8981666564941406s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6654810905456543s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.2903625965118408s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 64.74804544448853s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.311711311340332s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.290176153182983s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.3361895084381104s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.45985269546509s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.7193067073822021s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.34255218505859375s
Security | Sign check for Bio2RDF::Affymetrix took 0.13684892654418945s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 3.7158992290496826s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.6247165203094482s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.017953872680664062s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0005178451538085938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.00010561943054199219s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 21.610532522201538s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.33514404296875e-05s
INFO | --- Analysis for Bio2RDF::Affymetrix took 1045.4506359100342s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.6322782039642334s
Availability | VoID file availability check for Bio2RDF::Biomodels took 1.0232605934143066s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 18.622157096862793s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.380436658859253s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 48.89220190048218s
Interoperability | New terms check for Bio2RDF::Biomodels took 40.37133479118347s
Versatility | Languages check for Bio2RDF::Biomodels took 60.29419016838074s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.2762017250061035s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.17321085929870605s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.23814129829406738s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.2760944366455078s
Availability | RDF dump link check for Bio2RDF::Biomodels took 1.0327367782592773s
License | MR license check for Bio2RDF::Biomodels took 0.27440738677978516s
License | HR license check for Bio2RDF::Biomodels took 60.28172588348389s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.2716841697692871s
Understandability | Number of label check for Bio2RDF::Biomodels took 10.118157386779785s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.6050903797149658s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.2675011157989502s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.2933051586151123s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.37873005867004395s
Performance | Throughput check for Bio2RDF::Biomodels took 10.609450578689575s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 2.1865344047546387s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.26666808128356934s
Interlinking | skos check for Bio2RDF::Biomodels took 0.3888576030731201s
Interlinking | skos check for Bio2RDF::Biomodels took 0.3664968013763428s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.267575740814209s
Currency | Creation date check for Bio2RDF::Biomodels took 0.4007894992828369s
Currency | Modification date check for Bio2RDF::Biomodels took 0.2415454387664795s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 108.64798474311829s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 20.85201120376587s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.4910116195678711s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.3099944591522217s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.24441742897033691s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 6.926087856292725s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.9025554656982422s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6555979251861572s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.44245219230651855s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.17039465904236s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.43245792388916s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 6.5235490798950195s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.2873163223266602s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.60259485244751s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.7089495658874512s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.5171937942504883s
Security | Sign check for Bio2RDF::Biomodels took 0.27332377433776855s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 3.6296348571777344s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.5063033103942871s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.01814723014831543s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0005245208740234375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00011277198791503906s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 22.018179178237915s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.1444091796875e-05s
INFO | --- Analysis for Bio2RDF::Biomodels took 1046.7456271648407s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 0.14715051651000977s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 7.867813110351562e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.3755173683166504s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.019501209259033203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0005211830139160156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 1.239776611328125e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 1.2159347534179688e-05s
INFO | --- Analysis for Bio2RDF::BioModels::BioPAX took 4.789123058319092s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.6146724224090576s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.9956495761871338s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 18.10007357597351s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.3612291812896729s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 48.610119104385376s
Interoperability | New terms check for Bio2RDF::Bioportal took 41.92941188812256s
Versatility | Languages check for Bio2RDF::Bioportal took 60.25779938697815s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.27112483978271484s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.17318010330200195s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.2718513011932373s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.2772104740142822s
Availability | RDF dump link check for Bio2RDF::Bioportal took 1.0520033836364746s
License | MR license check for Bio2RDF::Bioportal took 0.5749077796936035s
License | HR license check for Bio2RDF::Bioportal took 60.27137017250061s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.2914431095123291s
Understandability | Number of label check for Bio2RDF::Bioportal took 10.302874565124512s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.6292726993560791s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.2877461910247803s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.2866477966308594s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.4747347831726074s
Performance | Throughput check for Bio2RDF::Bioportal took 10.967737436294556s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.7873179912567139s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.2716655731201172s
Interlinking | skos check for Bio2RDF::Bioportal took 0.5501542091369629s
Interlinking | skos check for Bio2RDF::Bioportal took 0.37499022483825684s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.2640705108642578s
Currency | Creation date check for Bio2RDF::Bioportal took 0.42226433753967285s
Currency | Modification date check for Bio2RDF::Bioportal took 0.26910996437072754s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 110.61474061012268s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 20.618091344833374s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.4229917526245117s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.27080750465393066s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.25258564949035645s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 6.633779764175415s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.9106276035308838s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6803979873657227s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.3973078727722168s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 64.95743060112s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.492098331451416s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.146291494369507s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.343677282333374s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.556875228881836s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7350890636444092s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.4857628345489502s
Security | Sign check for Bio2RDF::Bioportal took 0.3161623477935791s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 3.6043663024902344s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 1.3589980602264404s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.01791667938232422s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0005283355712890625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.00042510032653808594s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 19.283479690551758s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.1205673217773438e-05s
INFO | --- Analysis for Bio2RDF::Bioportal took 1058.0484120845795s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.15832304954528809s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.017415761947631836s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.7078611850738525s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.01856207847595215s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0005421638488769531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.3882598876953125e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 7.152557373046875e-06s
INFO | --- Analysis for Bio2RDF::Chembl took 19.60246968269348s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.7139623165130615s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 1.041799545288086s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 17.99200177192688s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.3309040069580078s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 48.72807550430298s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 40.05697464942932s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.27031493186951s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.2751445770263672s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.15598297119140625s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.5145137310028076s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.2741875648498535s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 1.037966012954712s
License | MR license check for Bio2RDF::Clinicaltrials took 0.5328927040100098s
License | HR license check for Bio2RDF::Clinicaltrials took 60.24671411514282s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.24341273307800293s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 9.75705361366272s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.6132678985595703s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.26331472396850586s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.27737927436828613s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.5751638412475586s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 10.990054607391357s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.835871696472168s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.28661274909973145s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.5811645984649658s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.3688321113586426s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.258192777633667s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.3821275234222412s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.3188462257385254s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 106.25178074836731s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 21.659542322158813s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.4175851345062256s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.2520754337310791s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.3139920234680176s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 6.889702081680298s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.893364667892456s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.66573166847229s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.397289514541626s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 65.1427915096283s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.4614017009735107s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 5.986268997192383s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.3244094848632812s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.51290822029114s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.7107927799224854s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.457744836807251s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.314314603805542s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 3.3895535469055176s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.3500230312347412s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.17888903617858887s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0005180835723876953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 7.963180541992188e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 22.612701416015625s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 2.193450927734375e-05s
INFO | --- Analysis for Bio2RDF::Clinicaltrials took 1046.8685593605042s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.6391048431396484s
Availability | VoID file availability check for Bio2RDF::Ctd took 1.032205581665039s
Extra | Recovery of all triples for Bio2RDF::Ctd took 18.569949865341187s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.3827412128448486s
Amount of data | Number of triples check for Bio2RDF::Ctd took 48.860758781433105s
Interoperability | New terms check for Bio2RDF::Ctd took 43.21363544464111s
Versatility | Languages check for Bio2RDF::Ctd took 60.2645742893219s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.2717282772064209s
Security | Check HTTPS for Bio2RDF::Ctd took 0.15951275825500488s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.5296237468719482s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.26132822036743164s
Availability | RDF dump link check for Bio2RDF::Ctd took 0.9882869720458984s
License | MR license check for Bio2RDF::Ctd took 0.5486505031585693s
License | HR license check for Bio2RDF::Ctd took 60.276246309280396s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.2615644931793213s
Understandability | Number of label check for Bio2RDF::Ctd took 9.439927816390991s
Understandability | URI regex check for Bio2RDF::Ctd took 0.5909552574157715s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.2707371711730957s
Verifiability | Authors check for Bio2RDF::Ctd took 0.29010915756225586s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.5092716217041016s
Performance | Throughput check for Bio2RDF::Ctd took 10.558680295944214s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.8016700744628906s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.29042887687683105s
Interlinking | skos check for Bio2RDF::Ctd took 0.6688382625579834s
Interlinking | skos check for Bio2RDF::Ctd took 0.3878970146179199s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.2647879123687744s
Currency | Creation date check for Bio2RDF::Ctd took 0.36035585403442383s
Currency | Modification date check for Bio2RDF::Ctd took 0.2904031276702881s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 108.92659378051758s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 23.582883834838867s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.4386563301086426s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.2997250556945801s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.29724597930908203s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 6.445155620574951s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8854601383209229s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6801655292510986s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.28910088539123535s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.41485691070557s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.3984317779541016s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.565686225891113s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.286102294921875s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.5093674659729s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.693087100982666s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.42996692657470703s
Security | Sign check for Bio2RDF::Ctd took 0.26599979400634766s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 3.606952428817749s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 1.3883893489837646s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.022672176361083984s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0005433559417724609s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 5.91278076171875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 21.255723476409912s
Believability | Calculation of trust value for Bio2RDF::Ctd took 1.239776611328125e-05s
INFO | --- Analysis for Bio2RDF::Ctd took 1067.531606912613s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 5.0067901611328125e-05s
Availability | VoID file availability check for bio2rdf-dataset took 8.106231689453125e-06s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.5862712860107422s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.019083738327026367s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0005354881286621094s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 6.0558319091796875e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-dataset took 4.593263387680054s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.6256201267242432s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.9890313148498535s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 18.907960414886475s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.384537935256958s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 48.79096722602844s
Interoperability | New terms check for Bio2RDF::Dbsnp took 39.38805437088013s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.23972511291504s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.2948262691497803s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.14138364791870117s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.3802163600921631s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.260944128036499s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 1.0214717388153076s
License | MR license check for Bio2RDF::Dbsnp took 0.43496108055114746s
License | HR license check for Bio2RDF::Dbsnp took 60.25269913673401s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.24125075340270996s
Understandability | Number of label check for Bio2RDF::Dbsnp took 9.705774545669556s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.6367275714874268s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.26107048988342285s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.28063535690307617s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.44507622718811035s
Performance | Throughput check for Bio2RDF::Dbsnp took 10.710503101348877s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.7824640274047852s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.2872734069824219s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.40976548194885254s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.37134313583374023s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.2572782039642334s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.40411829948425293s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.2862710952758789s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 111.37665629386902s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 25.040804624557495s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.4551701545715332s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.2582888603210449s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.3044612407684326s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 6.256444931030273s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.8970539569854736s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6678857803344727s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.39672231674194336s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 65.46757650375366s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.4468119144439697s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 5.976516962051392s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.3041133880615234s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.52902340888977s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.709707498550415s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.46932196617126465s
Security | Sign check for Bio2RDF::Dbsnp took 0.28758955001831055s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 3.4081854820251465s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.37784242630004883s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.1896991729736328s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0005183219909667969s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 6.508827209472656e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 43.05263328552246s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 1.1920928955078125e-05s
INFO | --- Analysis for Bio2RDF::Dbsnp took 1070.5964894294739s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.649559736251831s
Availability | VoID file availability check for Bio2RDF::Drugbank took 1.1390349864959717s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 19.834322690963745s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.2943129539489746s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 49.92003417015076s
Interoperability | New terms check for Bio2RDF::Drugbank took 39.29284882545471s
Versatility | Languages check for Bio2RDF::Drugbank took 60.267799615859985s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.2725198268890381s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.16801929473876953s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.7159140110015869s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.3139638900756836s
Availability | RDF dump link check for Bio2RDF::Drugbank took 1.0461833477020264s
License | MR license check for Bio2RDF::Drugbank took 0.46028757095336914s
License | HR license check for Bio2RDF::Drugbank took 60.278520345687866s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.2725512981414795s
Understandability | Number of label check for Bio2RDF::Drugbank took 9.919796228408813s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.668053388595581s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.2658863067626953s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.3062591552734375s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.5087587833404541s
Performance | Throughput check for Bio2RDF::Drugbank took 10.831273317337036s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.7479329109191895s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.29028820991516113s
Interlinking | skos check for Bio2RDF::Drugbank took 0.6631696224212646s
Interlinking | skos check for Bio2RDF::Drugbank took 0.41455507278442383s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.2565574645996094s
Currency | Creation date check for Bio2RDF::Drugbank took 0.3809654712677002s
Currency | Modification date check for Bio2RDF::Drugbank took 0.261979341506958s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 107.22380924224854s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 23.519317150115967s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.4941582679748535s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.2811417579650879s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.2783935070037842s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 6.674838304519653s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.8902425765991211s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.668907642364502s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.4894382953643799s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 65.56693243980408s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.4608676433563232s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 6.305752992630005s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.3162531852722168s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.544082164764404s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.7114377021789551s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.4451320171356201s
Security | Sign check for Bio2RDF::Drugbank took 0.28475451469421387s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 3.4971985816955566s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 1.4650602340698242s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.018082380294799805s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0005483627319335938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00011229515075683594s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 24.292171955108643s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 1.5020370483398438e-05s
INFO | --- Analysis for Bio2RDF::Drugbank took 1054.669326543808s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.6538667678833008s
Availability | VoID file availability check for Bio2RDF::Genage took 1.073559284210205s
Extra | Recovery of all triples for Bio2RDF::Genage took 17.81097912788391s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.2944018840789795s
Amount of data | Number of triples check for Bio2RDF::Genage took 48.866206884384155s
Interoperability | New terms check for Bio2RDF::Genage took 39.72823405265808s
Versatility | Languages check for Bio2RDF::Genage took 60.23296666145325s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.32073044776916504s
Security | Check HTTPS for Bio2RDF::Genage took 0.1440753936767578s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.27330851554870605s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.312694787979126s
Availability | RDF dump link check for Bio2RDF::Genage took 0.9998831748962402s
License | MR license check for Bio2RDF::Genage took 0.43724584579467773s
License | HR license check for Bio2RDF::Genage took 60.26615858078003s
Amount of data | Number of property check for Bio2RDF::Genage took 0.2946903705596924s
Understandability | Number of label check for Bio2RDF::Genage took 9.703106880187988s
Understandability | URI regex check for Bio2RDF::Genage took 0.6127841472625732s
Understandability | Vocabs check for Bio2RDF::Genage took 0.247300386428833s
Verifiability | Authors check for Bio2RDF::Genage took 0.2541344165802002s
Verifiability | Publishers check for Bio2RDF::Genage took 0.5289115905761719s
Performance | Throughput check for Bio2RDF::Genage took 10.770745277404785s
Verifiability | Contribs. check for Bio2RDF::Genage took 0.8234906196594238s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.3023049831390381s
Interlinking | skos check for Bio2RDF::Genage took 0.670867919921875s
Interlinking | skos check for Bio2RDF::Genage took 0.3815486431121826s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.2545466423034668s
Currency | Creation date check for Bio2RDF::Genage took 0.4239957332611084s
Currency | Modification date check for Bio2RDF::Genage took 0.23680377006530762s
Rep.Conc. | URIs length for Bio2RDF::Genage took 107.72450947761536s
Interoperability | New vocabularies check for Bio2RDF::Genage took 23.890710592269897s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.44386887550354004s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.33429551124572754s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.2713601589202881s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 6.321605920791626s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.9022796154022217s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6820669174194336s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.4416673183441162s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 65.14360499382019s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.4326493740081787s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.308184623718262s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.2996196746826172s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.5331392288208s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7109811305999756s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.44268226623535156s
Security | Sign check for Bio2RDF::Genage took 0.2734055519104004s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 3.407322645187378s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.8347530364990234s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.018197059631347656s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0005154609680175781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 6.508827209472656e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 20.093813180923462s
Believability | Calculation of trust value for Bio2RDF::Genage took 1.3589859008789062e-05s
INFO | --- Analysis for Bio2RDF::Genage took 1049.5031077861786s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 0.15259647369384766s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.02045607566833496s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.41776490211486816s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.0198214054107666s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0005393028259277344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 6.079673767089844e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 1.52587890625e-05s
INFO | --- Analysis for Bio2RDF::GenBank took 65.64368939399719s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.7012135982513428s
Availability | VoID file availability check for Bio2RDF::Gendr took 1.0038762092590332s
Extra | Recovery of all triples for Bio2RDF::Gendr took 18.129499912261963s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.3211185932159424s
Amount of data | Number of triples check for Bio2RDF::Gendr took 48.32691478729248s
Interoperability | New terms check for Bio2RDF::Gendr took 39.21864461898804s
Versatility | Languages check for Bio2RDF::Gendr took 60.226354360580444s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.29820895195007324s
Security | Check HTTPS for Bio2RDF::Gendr took 0.14568233489990234s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.45566630363464355s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.280580997467041s
Availability | RDF dump link check for Bio2RDF::Gendr took 1.0405097007751465s
License | MR license check for Bio2RDF::Gendr took 0.5695950984954834s
License | HR license check for Bio2RDF::Gendr took 60.26980423927307s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.7851805686950684s
Understandability | Number of label check for Bio2RDF::Gendr took 9.647839784622192s
Understandability | URI regex check for Bio2RDF::Gendr took 0.6202249526977539s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.2645578384399414s
Verifiability | Authors check for Bio2RDF::Gendr took 0.2868502140045166s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.39194154739379883s
Performance | Throughput check for Bio2RDF::Gendr took 10.530828714370728s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.2646830081939697s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.3220400810241699s
Interlinking | skos check for Bio2RDF::Gendr took 0.7659919261932373s
Interlinking | skos check for Bio2RDF::Gendr took 0.45818591117858887s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.2906491756439209s
Currency | Creation date check for Bio2RDF::Gendr took 0.41358375549316406s
Currency | Modification date check for Bio2RDF::Gendr took 0.28130364418029785s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 106.85420799255371s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 20.142595052719116s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.4257223606109619s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.2391979694366455s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.2887001037597656s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 6.575050592422485s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.8952524662017822s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6623959541320801s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.41704607009887695s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 65.15807867050171s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.8111090660095215s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 5.9252753257751465s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.3288421630859375s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.613871335983276s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.7085139751434326s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.43936896324157715s
Security | Sign check for Bio2RDF::Gendr took 0.29703402519226074s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 3.6089279651641846s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 180.5733048915863s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.18982338905334473s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0005614757537841797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.125999450683594e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 17.88643503189087s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.239776611328125e-05s
INFO | --- Analysis for Bio2RDF::Gendr took 1460.584284543991s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.584266185760498s
Availability | VoID file availability check for Bio2RDF::Goa took 1.1315100193023682s
Extra | Recovery of all triples for Bio2RDF::Goa took 20.601845026016235s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.3334505558013916s
Amount of data | Number of triples check for Bio2RDF::Goa took 48.67696189880371s
Interoperability | New terms check for Bio2RDF::Goa took 39.58261489868164s
Versatility | Languages check for Bio2RDF::Goa took 60.22491478919983s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.27341651916503906s
Security | Check HTTPS for Bio2RDF::Goa took 0.1475820541381836s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.26256871223449707s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.25220823287963867s
Availability | RDF dump link check for Bio2RDF::Goa took 1.008397102355957s
License | MR license check for Bio2RDF::Goa took 0.5535054206848145s
License | HR license check for Bio2RDF::Goa took 60.26870369911194s
Amount of data | Number of property check for Bio2RDF::Goa took 0.25652098655700684s
Understandability | Number of label check for Bio2RDF::Goa took 10.176016092300415s
Understandability | URI regex check for Bio2RDF::Goa took 0.6660680770874023s
Understandability | Vocabs check for Bio2RDF::Goa took 0.2680330276489258s
Verifiability | Authors check for Bio2RDF::Goa took 0.2754676342010498s
Verifiability | Publishers check for Bio2RDF::Goa took 0.5781731605529785s
Performance | Throughput check for Bio2RDF::Goa took 10.65630054473877s
Verifiability | Contribs. check for Bio2RDF::Goa took 1.6327569484710693s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.306626558303833s
Interlinking | skos check for Bio2RDF::Goa took 0.7560513019561768s
Interlinking | skos check for Bio2RDF::Goa took 0.40261292457580566s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.2757585048675537s
Currency | Creation date check for Bio2RDF::Goa took 0.40132713317871094s
Currency | Modification date check for Bio2RDF::Goa took 0.2728710174560547s
Rep.Conc. | URIs length for Bio2RDF::Goa took 107.56503653526306s
Interoperability | New vocabularies check for Bio2RDF::Goa took 17.779192686080933s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.44652795791625977s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.2682797908782959s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.27728796005249023s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 7.020354270935059s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.8927469253540039s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6513030529022217s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.44502925872802734s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 64.8674488067627s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.4536752700805664s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 6.038716077804565s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.3317649364471436s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.62385940551758s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.704519510269165s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.4827446937561035s
Security | Sign check for Bio2RDF::Goa took 0.3109474182128906s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 3.3343160152435303s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 1.7623991966247559s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.018551349639892578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0005550384521484375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.365776062011719e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 17.536139965057373s
Believability | Calculation of trust value for Bio2RDF::Goa took 1.2636184692382812e-05s
INFO | --- Analysis for Bio2RDF::Goa took 1058.029406785965s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.6169681549072266s
Availability | VoID file availability check for Bio2RDF::Hgnc took 1.084336280822754s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 21.944761276245117s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.3451769351959229s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 48.88751268386841s
Interoperability | New terms check for Bio2RDF::Hgnc took 40.191524028778076s
Versatility | Languages check for Bio2RDF::Hgnc took 60.24335169792175s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.28249454498291016s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.1710519790649414s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.28060054779052734s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.2832014560699463s
Availability | RDF dump link check for Bio2RDF::Hgnc took 1.0223817825317383s
License | MR license check for Bio2RDF::Hgnc took 0.41299939155578613s
License | HR license check for Bio2RDF::Hgnc took 60.28187322616577s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.2842731475830078s
Understandability | Number of label check for Bio2RDF::Hgnc took 9.489603757858276s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.6104114055633545s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.25773024559020996s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.3060448169708252s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.5670795440673828s
Performance | Throughput check for Bio2RDF::Hgnc took 10.620114803314209s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.7874770164489746s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.2822539806365967s
Interlinking | skos check for Bio2RDF::Hgnc took 0.7868645191192627s
Interlinking | skos check for Bio2RDF::Hgnc took 0.380842924118042s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.2512533664703369s
Currency | Creation date check for Bio2RDF::Hgnc took 0.3985435962677002s
Currency | Modification date check for Bio2RDF::Hgnc took 0.28075146675109863s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 107.35927319526672s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 20.436346769332886s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.4886047840118408s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.32686376571655273s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.28179097175598145s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 6.5076398849487305s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.895158052444458s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6623501777648926s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.3292362689971924s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.19375228881836s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.453866481781006s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 6.129366874694824s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.2927720546722412s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.51644515991211s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7177951335906982s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.4873623847961426s
Security | Sign check for Bio2RDF::Hgnc took 0.25073814392089844s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 3.5768911838531494s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.7010626792907715s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.01797032356262207s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0005280971527099609s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00011467933654785156s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 18.624955654144287s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.1682510375976562e-05s
INFO | --- Analysis for Bio2RDF::Hgnc took 1044.5765264034271s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.6070563793182373s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.9583590030670166s
Extra | Recovery of all triples for Bio2RDF::Homologene took 18.171030044555664s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.3535332679748535s
Amount of data | Number of triples check for Bio2RDF::Homologene took 48.777297258377075s
Interoperability | New terms check for Bio2RDF::Homologene took 40.9384982585907s
Versatility | Languages check for Bio2RDF::Homologene took 60.299148082733154s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.30577993392944336s
Security | Check HTTPS for Bio2RDF::Homologene took 0.17266058921813965s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.4037351608276367s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.2532680034637451s
Availability | RDF dump link check for Bio2RDF::Homologene took 1.060516119003296s
License | MR license check for Bio2RDF::Homologene took 0.5523004531860352s
License | HR license check for Bio2RDF::Homologene took 60.26934790611267s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.2816770076751709s
Understandability | Number of label check for Bio2RDF::Homologene took 9.67784571647644s
Understandability | URI regex check for Bio2RDF::Homologene took 0.6224284172058105s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.29248619079589844s
Verifiability | Authors check for Bio2RDF::Homologene took 0.2924222946166992s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.3812253475189209s
Performance | Throughput check for Bio2RDF::Homologene took 10.799563646316528s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.7932031154632568s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.2799079418182373s
Interlinking | skos check for Bio2RDF::Homologene took 0.7913165092468262s
Interlinking | skos check for Bio2RDF::Homologene took 0.40000176429748535s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.2791557312011719s
Currency | Creation date check for Bio2RDF::Homologene took 0.41484975814819336s
Currency | Modification date check for Bio2RDF::Homologene took 0.2610132694244385s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 106.85857343673706s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 17.951300859451294s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.4669036865234375s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.26168012619018555s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.31006431579589844s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 6.520063400268555s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8961396217346191s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6857271194458008s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.3176419734954834s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.1392412185669s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.460550546646118s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.090213298797607s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.3285529613494873s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.521504163742065s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7255034446716309s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.5242445468902588s
Security | Sign check for Bio2RDF::Homologene took 0.29782915115356445s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 3.423290967941284s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.5244696140289307s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.018049240112304688s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0005176067352294922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.9604644775390625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 18.66956615447998s
Believability | Calculation of trust value for Bio2RDF::Homologene took 1.2159347534179688e-05s
INFO | --- Analysis for Bio2RDF::Homologene took 1037.751615524292s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 0.93977952003479s
Availability | VoID file availability check for Bio2RDF::INOH took 3.5762786865234375e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.9522585868835449s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.01867985725402832s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0005199909210205078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 1.1444091796875e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 1.3828277587890625e-05s
INFO | --- Analysis for Bio2RDF::INOH took 4.414782285690308s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.6551022529602051s
Availability | VoID file availability check for Bio2RDF::Interpro took 1.0553574562072754s
Extra | Recovery of all triples for Bio2RDF::Interpro took 18.39198613166809s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.2949399948120117s
Amount of data | Number of triples check for Bio2RDF::Interpro took 48.62295579910278s
Interoperability | New terms check for Bio2RDF::Interpro took 39.710997581481934s
Versatility | Languages check for Bio2RDF::Interpro took 60.23812508583069s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.32010436058044434s
Security | Check HTTPS for Bio2RDF::Interpro took 0.1711890697479248s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.29613208770751953s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.24930357933044434s
Availability | RDF dump link check for Bio2RDF::Interpro took 1.063735008239746s
License | MR license check for Bio2RDF::Interpro took 0.4204287528991699s
License | HR license check for Bio2RDF::Interpro took 60.266295433044434s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.27074646949768066s
Understandability | Number of label check for Bio2RDF::Interpro took 9.719568490982056s
Understandability | URI regex check for Bio2RDF::Interpro took 0.6276657581329346s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.27577710151672363s
Verifiability | Authors check for Bio2RDF::Interpro took 0.2893049716949463s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.5618996620178223s
Performance | Throughput check for Bio2RDF::Interpro took 10.812580823898315s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.7507510185241699s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.28871750831604004s
Interlinking | skos check for Bio2RDF::Interpro took 0.6275200843811035s
Interlinking | skos check for Bio2RDF::Interpro took 0.38538146018981934s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.28104686737060547s
Currency | Creation date check for Bio2RDF::Interpro took 0.381375789642334s
Currency | Modification date check for Bio2RDF::Interpro took 0.26518940925598145s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 107.65090727806091s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 17.740562200546265s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.4437265396118164s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.22884178161621094s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.255565881729126s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 6.7225072383880615s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.9061696529388428s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6678605079650879s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.2579500675201416s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.11657547950745s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.489248275756836s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.03966498374939s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.3094196319580078s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.54443335533142s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.7124147415161133s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.476931095123291s
Security | Sign check for Bio2RDF::Interpro took 0.283613920211792s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 3.804915189743042s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 3.8081202507019043s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.018126487731933594s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0005655288696289062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 9.703636169433594e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 18.761930227279663s
Believability | Calculation of trust value for Bio2RDF::Interpro took 1.2636184692382812e-05s
INFO | --- Analysis for Bio2RDF::Interpro took 1044.80122256279s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.15975022315979004s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.01642632484436035s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.7188377380371094s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.019360780715942383s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0005381107330322266s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 8.249282836914062e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 1.3589859008789062e-05s
INFO | --- Analysis for Bio2RDF::Iproclass took 21.69704556465149s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.640172004699707s
Availability | VoID file availability check for Bio2RDF::Irefindex took 1.038898229598999s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 18.11606454849243s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.340911626815796s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 48.7294807434082s
Interoperability | New terms check for Bio2RDF::Irefindex took 39.01087021827698s
Versatility | Languages check for Bio2RDF::Irefindex took 60.23989152908325s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.25701284408569336s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.14225029945373535s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.4640071392059326s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.26517677307128906s
Availability | RDF dump link check for Bio2RDF::Irefindex took 1.02351713180542s
License | MR license check for Bio2RDF::Irefindex took 0.45229244232177734s
License | HR license check for Bio2RDF::Irefindex took 60.28221940994263s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.2812981605529785s
Understandability | Number of label check for Bio2RDF::Irefindex took 9.795674562454224s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.5707223415374756s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.28225064277648926s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.269899845123291s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.44696474075317383s
Performance | Throughput check for Bio2RDF::Irefindex took 10.949614763259888s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.7338404655456543s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.3167574405670166s
Interlinking | skos check for Bio2RDF::Irefindex took 0.8000071048736572s
Interlinking | skos check for Bio2RDF::Irefindex took 0.4021482467651367s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.2666969299316406s
Currency | Creation date check for Bio2RDF::Irefindex took 0.3834412097930908s
Currency | Modification date check for Bio2RDF::Irefindex took 0.2577097415924072s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 107.03234100341797s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 16.123754739761353s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.4564816951751709s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.2755272388458252s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.27116823196411133s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 6.574834823608398s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.8918089866638184s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6601052284240723s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.3313906192779541s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 65.14312744140625s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.406878709793091s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 5.999052286148071s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.3134751319885254s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.572083473205566s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.723752498626709s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.4216136932373047s
Security | Sign check for Bio2RDF::Irefindex took 0.28783655166625977s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 3.407952070236206s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.6513795852661133s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.18616223335266113s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0005171298980712891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 9.131431579589844e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 16.8583402633667s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 1.2636184692382812e-05s
INFO | --- Analysis for Bio2RDF::Irefindex took 1031.4245066642761s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 0.6257345676422119s
Availability | VoID file availability check for Bio2RDF::KEGG took 4.76837158203125e-06s
Extra | Recovery of all triples for Bio2RDF::KEGG took 18.319841384887695s
Performance | Total latancy measurement for Bio2RDF::KEGG took 1.38759183883667s
Amount of data | Number of triples check for Bio2RDF::KEGG took 49.22359013557434s
Interoperability | New terms check for Bio2RDF::KEGG took 40.1015899181366s
Versatility | Languages check for Bio2RDF::KEGG took 60.283607482910156s
Interpretability | Number of blank nodes check for Bio2RDF::KEGG took 0.27546072006225586s
Security | Check HTTPS for Bio2RDF::KEGG took 0.1681535243988037s
Interpretability | RDF structures check for Bio2RDF::KEGG took 0.2875983715057373s
Versatility | Serialization formats check for Bio2RDF::KEGG took 0.276397705078125s
Availability | RDF dump link check for Bio2RDF::KEGG took 1.087045431137085s
License | MR license check for Bio2RDF::KEGG took 0.4447445869445801s
License | HR license check for Bio2RDF::KEGG took 60.262349367141724s
Amount of data | Number of property check for Bio2RDF::KEGG took 0.27394890785217285s
Understandability | Number of label check for Bio2RDF::KEGG took 9.756335496902466s
Understandability | URI regex check for Bio2RDF::KEGG took 0.6292910575866699s
Understandability | Vocabs check for Bio2RDF::KEGG took 0.2899184226989746s
Verifiability | Authors check for Bio2RDF::KEGG took 0.2889690399169922s
Verifiability | Publishers check for Bio2RDF::KEGG took 0.49028563499450684s
Performance | Throughput check for Bio2RDF::KEGG took 10.713422298431396s
Verifiability | Contribs. check for Bio2RDF::KEGG took 0.7605068683624268s
Interlinking | sameAs chians check for Bio2RDF::KEGG took 0.27811479568481445s
Interlinking | skos check for Bio2RDF::KEGG took 0.7583720684051514s
Interlinking | skos check for Bio2RDF::KEGG took 0.3853332996368408s
Timeliness | dataset update frequency check for Bio2RDF::KEGG took 0.24877500534057617s
Currency | Creation date check for Bio2RDF::KEGG took 0.4004096984863281s
Currency | Modification date check for Bio2RDF::KEGG took 0.2489466667175293s
Rep.Conc. | URIs length for Bio2RDF::KEGG took 108.17702674865723s
Interoperability | New vocabularies check for Bio2RDF::KEGG took 14.917948246002197s
Consistency | Deprecated classes/propertiers check for Bio2RDF::KEGG took 0.4800834655761719s
Accuracy | Check Functional Property for Bio2RDF::KEGG took 0.2783348560333252s
Accuracy | Check Inverse Functional Property for Bio2RDF::KEGG took 0.3117525577545166s
Accuracy | Check Empty annotation labels for Bio2RDF::KEGG took 6.2241432666778564s
Accuracy | Check White space in annotation for Bio2RDF::KEGG took 0.8957023620605469s
Accuracy | Check Datatype consistency for Bio2RDF::KEGG took 0.6634838581085205s
Consistency | Disjoint class check for Bio2RDF::KEGG took 0.4237518310546875s
Consistency | Check Misplaced properties for Bio2RDF::KEGG took 65.23285818099976s
Consistency | Misplaced classes for Bio2RDF::KEGG took 2.4241392612457275s
Consistency | Check Ontology hijacking for Bio2RDF::KEGG took 5.746577024459839s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::KEGG took 1.2764692306518555s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::KEGG took 61.58126974105835s
Conciseness | Check Extensional conciseness for Bio2RDF::KEGG took 0.7136950492858887s
Conciseness | Check Intensional conciseness for Bio2RDF::KEGG took 0.45978760719299316s
Security | Sign check for Bio2RDF::KEGG took 0.32354259490966797s
Availability | Check URIs Dereferenciability for Bio2RDF::KEGG took 3.586470365524292s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.633155345916748s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.01819777488708496s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0005214214324951172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.580352783203125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::KEGG took 16.638349056243896s
Believability | Calculation of trust value for Bio2RDF::KEGG took 6.67572021484375e-06s
INFO | --- Analysis for Bio2RDF::KEGG took 1024.866593837738s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 0.14910054206848145s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 4.5299530029296875e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.49054789543151855s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.018978595733642578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0005354881286621094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 1.3828277587890625e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 5.7220458984375e-05s
INFO | --- Analysis for Bio2RDF::KEGG::BioPAX took 8.109604358673096s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.21039843559265137s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.015981197357177734s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.31459856033325195s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.0184171199798584s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0005290508270263672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 1.33514404296875e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 1.33514404296875e-05s
INFO | --- Analysis for Bio2RDF::Linkedspl took 13.180451154708862s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.6853165626525879s
Availability | VoID file availability check for Bio2RDF::Lsr took 1.0072004795074463s
Extra | Recovery of all triples for Bio2RDF::Lsr took 19.16895055770874s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.373223066329956s
Amount of data | Number of triples check for Bio2RDF::Lsr took 47.93444085121155s
Interoperability | New terms check for Bio2RDF::Lsr took 39.28209614753723s
Versatility | Languages check for Bio2RDF::Lsr took 60.25231647491455s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.2926630973815918s
Security | Check HTTPS for Bio2RDF::Lsr took 0.17064523696899414s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.45301175117492676s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.28663063049316406s
Availability | RDF dump link check for Bio2RDF::Lsr took 0.9964361190795898s
License | MR license check for Bio2RDF::Lsr took 0.6141197681427002s
License | HR license check for Bio2RDF::Lsr took 60.267712116241455s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.27593469619750977s
Understandability | Number of label check for Bio2RDF::Lsr took 9.546383380889893s
Understandability | URI regex check for Bio2RDF::Lsr took 0.6289410591125488s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.24721169471740723s
Verifiability | Authors check for Bio2RDF::Lsr took 0.2789156436920166s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.5522749423980713s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.751823902130127s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.26267170906066895s
Interlinking | skos check for Bio2RDF::Lsr took 0.5610570907592773s
Interlinking | skos check for Bio2RDF::Lsr took 0.3662753105163574s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.24217462539672852s
Currency | Creation date check for Bio2RDF::Lsr took 0.38461947441101074s
Currency | Modification date check for Bio2RDF::Lsr took 0.2526979446411133s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 106.91149497032166s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 16.278782606124878s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.4062356948852539s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.2642695903778076s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.27938079833984375s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 6.600233554840088s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.8987114429473877s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.66188645362854s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.3040142059326172s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 64.91494154930115s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.4087893962860107s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.171817779541016s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.3312537670135498s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.55658316612244s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.7068209648132324s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.4915947914123535s
Security | Sign check for Bio2RDF::Lsr took 0.25240445137023926s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 3.6127922534942627s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.44690632820129395s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.017690658569335938s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0005214214324951172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 5.173683166503906e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 16.67596411705017s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.8358230590820312e-05s
INFO | --- Analysis for Bio2RDF::Lsr took 1024.5443387031555s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.7003965377807617s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.9936792850494385s
Extra | Recovery of all triples for Bio2RDF::Mesh took 18.419724702835083s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.3033201694488525s
Amount of data | Number of triples check for Bio2RDF::Mesh took 48.293616771698s
Interoperability | New terms check for Bio2RDF::Mesh took 38.854689598083496s
Versatility | Languages check for Bio2RDF::Mesh took 60.25331163406372s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.2596101760864258s
Security | Check HTTPS for Bio2RDF::Mesh took 0.16605043411254883s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.26683783531188965s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.27290892601013184s
Availability | RDF dump link check for Bio2RDF::Mesh took 1.0396666526794434s
License | MR license check for Bio2RDF::Mesh took 0.44156336784362793s
License | HR license check for Bio2RDF::Mesh took 60.249058961868286s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.29610776901245117s
Understandability | Number of label check for Bio2RDF::Mesh took 9.40118670463562s
Understandability | URI regex check for Bio2RDF::Mesh took 0.5991189479827881s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.27466368675231934s
Verifiability | Authors check for Bio2RDF::Mesh took 0.3289816379547119s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.39360904693603516s
Performance | Throughput check for Bio2RDF::Mesh took 10.463849782943726s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.8264870643615723s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.2934749126434326s
Interlinking | skos check for Bio2RDF::Mesh took 0.6096057891845703s
Interlinking | skos check for Bio2RDF::Mesh took 0.36383986473083496s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.29734134674072266s
Currency | Creation date check for Bio2RDF::Mesh took 0.37243008613586426s
Currency | Modification date check for Bio2RDF::Mesh took 0.291240930557251s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 107.32130885124207s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 17.49220108985901s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.5444753170013428s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.27555108070373535s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.30391836166381836s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 6.80507755279541s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.8989870548248291s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6524996757507324s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.44054269790649414s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 65.70134019851685s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.4658775329589844s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.1243555545806885s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.3346021175384521s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.562766790390015s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.6983859539031982s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.4544520378112793s
Security | Sign check for Bio2RDF::Mesh took 0.28094959259033203s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 3.5919840335845947s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 3.2526259422302246s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.018169879913330078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0005128383636474609s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.486343383789062e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 15.060009956359863s
Believability | Calculation of trust value for Bio2RDF::Mesh took 6.67572021484375e-06s
INFO | --- Analysis for Bio2RDF::Mesh took 1040.4826338291168s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.6628613471984863s
Availability | VoID file availability check for Bio2RDF::Mgi took 1.1405518054962158s
Extra | Recovery of all triples for Bio2RDF::Mgi took 18.562828063964844s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.3322844505310059s
Amount of data | Number of triples check for Bio2RDF::Mgi took 48.03946375846863s
Interoperability | New terms check for Bio2RDF::Mgi took 39.74129295349121s
Versatility | Languages check for Bio2RDF::Mgi took 60.279398918151855s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.29761838912963867s
Security | Check HTTPS for Bio2RDF::Mgi took 0.162933349609375s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.31742310523986816s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.25063514709472656s
Availability | RDF dump link check for Bio2RDF::Mgi took 0.9723153114318848s
License | MR license check for Bio2RDF::Mgi took 0.5891213417053223s
License | HR license check for Bio2RDF::Mgi took 60.26099252700806s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.23517298698425293s
Understandability | Number of label check for Bio2RDF::Mgi took 9.733951568603516s
Understandability | URI regex check for Bio2RDF::Mgi took 0.6529650688171387s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.23410344123840332s
Verifiability | Authors check for Bio2RDF::Mgi took 0.28560686111450195s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.5343012809753418s
Performance | Throughput check for Bio2RDF::Mgi took 10.799816370010376s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.8164889812469482s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.29039883613586426s
Interlinking | skos check for Bio2RDF::Mgi took 0.4015779495239258s
Interlinking | skos check for Bio2RDF::Mgi took 0.40996646881103516s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.24365949630737305s
Currency | Creation date check for Bio2RDF::Mgi took 0.40607643127441406s
Currency | Modification date check for Bio2RDF::Mgi took 0.29388880729675293s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 110.4955997467041s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 16.647566080093384s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.46295714378356934s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.24959087371826172s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.2679891586303711s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 6.681748390197754s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.9019925594329834s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.7025268077850342s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.43210315704345703s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.08244824409485s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.4121525287628174s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 5.832708120346069s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.2809836864471436s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.518877029418945s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7189421653747559s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.47512221336364746s
Security | Sign check for Bio2RDF::Mgi took 0.24522614479064941s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 3.414008378982544s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 1.6065301895141602s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.02370738983154297s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0005388259887695312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 0.00010824203491210938s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 19.178747415542603s
Believability | Calculation of trust value for Bio2RDF::Mgi took 1.1444091796875e-05s
INFO | --- Analysis for Bio2RDF::Mgi took 1060.5379133224487s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.6317892074584961s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 1.0561349391937256s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 20.168174505233765s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.408926248550415s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 49.473673582077026s
Interoperability | New terms check for Bio2RDF::Ncbigene took 44.324973344802856s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.27363443374634s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.2774949073791504s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.16661643981933594s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.44817495346069336s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.2964181900024414s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 1.0099077224731445s
License | MR license check for Bio2RDF::Ncbigene took 0.4498262405395508s
License | HR license check for Bio2RDF::Ncbigene took 60.281378984451294s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.2479081153869629s
Understandability | Number of label check for Bio2RDF::Ncbigene took 9.683242321014404s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.6604230403900146s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.24518799781799316s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.2968170642852783s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.4551098346710205s
Performance | Throughput check for Bio2RDF::Ncbigene took 10.726227760314941s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.8902997970581055s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.27696800231933594s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.687279462814331s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.3565952777862549s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.2747969627380371s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.4191865921020508s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.24157285690307617s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 113.20252966880798s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 16.27076268196106s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.528611421585083s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.3350980281829834s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.23151469230651855s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 6.504781246185303s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.8941500186920166s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.663733720779419s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.4043612480163574s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.2708158493042s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.463224411010742s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 5.975426912307739s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.342890977859497s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.588560581207275s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.7224898338317871s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.49280452728271484s
Security | Sign check for Bio2RDF::Ncbigene took 0.26447272300720215s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 3.7111783027648926s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 3.04848051071167s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.018291711807250977s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0005140304565429688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012731552124023438s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 17.218236923217773s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 1.2874603271484375e-05s
INFO | --- Analysis for Bio2RDF::Ncbigene took 1062.3890509605408s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.6043791770935059s
Availability | VoID file availability check for Bio2RDF::Ndc took 1.112088918685913s
Extra | Recovery of all triples for Bio2RDF::Ndc took 18.78090786933899s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.2955148220062256s
Amount of data | Number of triples check for Bio2RDF::Ndc took 48.3748733997345s
Interoperability | New terms check for Bio2RDF::Ndc took 41.84563493728638s
Versatility | Languages check for Bio2RDF::Ndc took 60.2608118057251s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.30621862411499023s
Security | Check HTTPS for Bio2RDF::Ndc took 0.14271807670593262s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.45113301277160645s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.26803159713745117s
Availability | RDF dump link check for Bio2RDF::Ndc took 1.0520002841949463s
License | MR license check for Bio2RDF::Ndc took 0.4111955165863037s
License | HR license check for Bio2RDF::Ndc took 60.32799291610718s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.2832303047180176s
Understandability | Number of label check for Bio2RDF::Ndc took 9.989893436431885s
Understandability | URI regex check for Bio2RDF::Ndc took 0.6771254539489746s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.23731017112731934s
Verifiability | Authors check for Bio2RDF::Ndc took 0.29071640968322754s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.3608975410461426s
Performance | Throughput check for Bio2RDF::Ndc took 10.760331392288208s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.7834568023681641s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.28350353240966797s
Interlinking | skos check for Bio2RDF::Ndc took 0.7393331527709961s
Interlinking | skos check for Bio2RDF::Ndc took 0.4313499927520752s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.2310657501220703s
Currency | Creation date check for Bio2RDF::Ndc took 0.4001462459564209s
Currency | Modification date check for Bio2RDF::Ndc took 0.25905656814575195s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 107.45401549339294s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 18.67964005470276s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.5081233978271484s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.24275779724121094s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.3005716800689697s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 6.4286582469940186s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.8973240852355957s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6819629669189453s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.44837450981140137s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 65.64964127540588s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.4847936630249023s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.382364749908447s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.3307204246520996s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.635497093200684s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7337710857391357s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.43358707427978516s
Security | Sign check for Bio2RDF::Ndc took 0.3072683811187744s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 3.477511167526245s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.486130952835083s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.018532514572143555s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0005333423614501953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 5.173683166503906e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 15.873685121536255s
Believability | Calculation of trust value for Bio2RDF::Ndc took 1.3113021850585938e-05s
INFO | --- Analysis for Bio2RDF::Ndc took 1046.7286009788513s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 0.1456446647644043s
Availability | VoID file availability check for Bio2RDF::NetPath took 8.106231689453125e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.716865062713623s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.01894235610961914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0005168914794921875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 1.2636184692382812e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 1.1682510375976562e-05s
INFO | --- Analysis for Bio2RDF::NetPath took 124.27079749107361s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.17867755889892578s
Availability | VoID file availability check for Bio2RDF::neXtProt took 7.867813110351562e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.5413119792938232s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.01851797103881836s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0005211830139160156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 1.3113021850585938e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 1.0251998901367188e-05s
INFO | --- Analysis for Bio2RDF::neXtProt took 3.35843825340271s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.6225898265838623s
Availability | VoID file availability check for Bio2RDF::Omim took 1.053173303604126s
Extra | Recovery of all triples for Bio2RDF::Omim took 18.062468767166138s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.3615827560424805s
Amount of data | Number of triples check for Bio2RDF::Omim took 49.15107250213623s
Interoperability | New terms check for Bio2RDF::Omim took 41.478991985321045s
Versatility | Languages check for Bio2RDF::Omim took 60.23373746871948s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.595081090927124s
Security | Check HTTPS for Bio2RDF::Omim took 0.1711139678955078s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.4148402214050293s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.22997379302978516s
Availability | RDF dump link check for Bio2RDF::Omim took 1.1947228908538818s
License | MR license check for Bio2RDF::Omim took 0.27059459686279297s
License | HR license check for Bio2RDF::Omim took 60.29354953765869s
Amount of data | Number of property check for Bio2RDF::Omim took 0.29468679428100586s
Understandability | Number of label check for Bio2RDF::Omim took 9.54088044166565s
Understandability | URI regex check for Bio2RDF::Omim took 0.5457379817962646s
Understandability | Vocabs check for Bio2RDF::Omim took 0.2701094150543213s
Verifiability | Authors check for Bio2RDF::Omim took 0.30964040756225586s
Verifiability | Publishers check for Bio2RDF::Omim took 0.36849045753479004s
Performance | Throughput check for Bio2RDF::Omim took 10.501026391983032s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.753389835357666s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.2791168689727783s
Interlinking | skos check for Bio2RDF::Omim took 0.5038821697235107s
Interlinking | skos check for Bio2RDF::Omim took 0.4203367233276367s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.2595689296722412s
Currency | Creation date check for Bio2RDF::Omim took 0.3878767490386963s
Currency | Modification date check for Bio2RDF::Omim took 0.2600247859954834s
Rep.Conc. | URIs length for Bio2RDF::Omim took 106.19613671302795s
Interoperability | New vocabularies check for Bio2RDF::Omim took 16.711088180541992s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.4885375499725342s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.28351473808288574s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.2497117519378662s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 6.38868522644043s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.9012863636016846s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6681911945343018s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.44406890869140625s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 64.9852876663208s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.4690611362457275s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 6.1054182052612305s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.2950890064239502s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.598193645477295s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.7179582118988037s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.41590285301208496s
Security | Sign check for Bio2RDF::Omim took 0.2788112163543701s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 3.551265239715576s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 1.8711841106414795s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.01816844940185547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0005192756652832031s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.0001366138458251953s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 14.912304639816284s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.1682510375976562e-05s
INFO | --- Analysis for Bio2RDF::Omim took 1039.777829170227s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 8.749961853027344e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 5.9604644775390625e-06s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.48131823539733887s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.020316123962402344s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0005345344543457031s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.743171691894531e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-omim-resources took 3.970223903656006s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.6427719593048096s
Availability | VoID file availability check for Bio2RDF::Orphanet took 1.0134735107421875s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 18.896286487579346s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.3069262504577637s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 50.457693099975586s
Interoperability | New terms check for Bio2RDF::Orphanet took 41.85051941871643s
Versatility | Languages check for Bio2RDF::Orphanet took 60.26285171508789s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.29438090324401855s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.17040777206420898s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.4160425662994385s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.3002340793609619s
Availability | RDF dump link check for Bio2RDF::Orphanet took 0.9835333824157715s
License | MR license check for Bio2RDF::Orphanet took 0.5238232612609863s
License | HR license check for Bio2RDF::Orphanet took 60.290213108062744s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.30063915252685547s
Understandability | Number of label check for Bio2RDF::Orphanet took 9.594746112823486s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.6353521347045898s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.2514512538909912s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.29483795166015625s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.45801353454589844s
Performance | Throughput check for Bio2RDF::Orphanet took 10.638891696929932s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.875502347946167s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.2929813861846924s
Interlinking | skos check for Bio2RDF::Orphanet took 1.1180074214935303s
Interlinking | skos check for Bio2RDF::Orphanet took 0.3993504047393799s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.2818474769592285s
Currency | Creation date check for Bio2RDF::Orphanet took 0.36806225776672363s
Currency | Modification date check for Bio2RDF::Orphanet took 0.24337077140808105s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 113.26321601867676s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 15.964381694793701s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.4944889545440674s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.26442623138427734s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.2697470188140869s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 6.9741530418396s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.8846888542175293s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6961483955383301s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.49909448623657227s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 65.76373028755188s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.4077036380767822s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.547120094299316s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.2903661727905273s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.50662016868591s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.694913387298584s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.48918867111206055s
Security | Sign check for Bio2RDF::Orphanet took 0.27518200874328613s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 3.486387252807617s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 1.23799729347229s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.20750689506530762s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0005171298980712891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 8.082389831542969e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 15.432399034500122s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 1.2636184692382812e-05s
INFO | --- Analysis for Bio2RDF::Orphanet took 1058.2717461585999s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.14998507499694824s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.01545262336730957s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 1.0912065505981445s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.017931222915649414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0005247592926025391s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 1.3589859008789062e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 1.4781951904296875e-05s
INFO | --- Analysis for Bio2RDF::Pathwaycommons took 16.016624689102173s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.7407519817352295s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.9827580451965332s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 21.33688449859619s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.2843077182769775s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 50.5403265953064s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 42.575493574142456s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.277291774749756s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.28827762603759766s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.17407441139221191s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.4359455108642578s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.2310047149658203s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 0.9998445510864258s
License | MR license check for Bio2RDF::Pharmgkb took 0.322023868560791s
License | HR license check for Bio2RDF::Pharmgkb took 60.293076276779175s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.2715582847595215s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 9.582025051116943s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5625855922698975s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.2570674419403076s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.2513926029205322s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.36854004859924316s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.074575662612915s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 1.8399627208709717s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.3121302127838135s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.5956172943115234s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.37104272842407227s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.27580928802490234s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.378140926361084s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.2909562587738037s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 111.37528920173645s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 19.96126079559326s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.5142166614532471s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.2762901782989502s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.22847938537597656s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 6.817337512969971s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.8950934410095215s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6703269481658936s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.2756388187408447s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 65.61114716529846s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.453617811203003s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 6.7616188526153564s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.3471565246582031s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.56843042373657s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7158560752868652s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.41748976707458496s
Security | Sign check for Bio2RDF::Pharmgkb took 0.27057313919067383s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 3.7022147178649902s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 1.633223056793213s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.017827510833740234s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0005328655242919922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.867813110351562e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 19.984380960464478s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 1.2159347534179688e-05s
INFO | --- Analysis for Bio2RDF::Pharmgkb took 1068.1774694919586s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 0.14469599723815918s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 7.3909759521484375e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.690894603729248s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.018908023834228516s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0005331039428710938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 2.002716064453125e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 1.33514404296875e-05s
INFO | --- Analysis for Bio2RDF::PharmGKB::BioPAX took 7.294084787368774s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 0.14091801643371582s
Availability | VoID file availability check for Bio2RDF::PID took 6.9141387939453125e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.33950090408325195s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.01849198341369629s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0005202293395996094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 1.2874603271484375e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 1.2874603271484375e-05s
INFO | --- Analysis for Bio2RDF::PID took 2.240006446838379s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 0.14531612396240234s
Availability | VoID file availability check for Bio2RDF::PubChem took 7.3909759521484375e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.3513803482055664s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.020337581634521484s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0005548000335693359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 1.239776611328125e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 2.0742416381835938e-05s
INFO | --- Analysis for Bio2RDF::PubChem took 3.6095645427703857s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.7287373542785645s
Availability | VoID file availability check for Bio2RDF::Pubmed took 1.1201190948486328s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 18.63241171836853s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2984139919281006s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 50.63986587524414s
Interoperability | New terms check for Bio2RDF::Pubmed took 43.43158674240112s
Versatility | Languages check for Bio2RDF::Pubmed took 60.240376234054565s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.2754528522491455s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.14170360565185547s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.285797119140625s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.2945246696472168s
Availability | RDF dump link check for Bio2RDF::Pubmed took 1.030015468597412s
License | MR license check for Bio2RDF::Pubmed took 0.5050241947174072s
License | HR license check for Bio2RDF::Pubmed took 60.30477714538574s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.2971615791320801s
Understandability | Number of label check for Bio2RDF::Pubmed took 9.236981868743896s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.6405103206634521s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.27565717697143555s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.23827123641967773s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.3682067394256592s
Performance | Throughput check for Bio2RDF::Pubmed took 10.773452043533325s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.7380030155181885s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.29036760330200195s
Interlinking | skos check for Bio2RDF::Pubmed took 0.569631814956665s
Interlinking | skos check for Bio2RDF::Pubmed took 0.37769389152526855s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.27873730659484863s
Currency | Creation date check for Bio2RDF::Pubmed took 0.4119279384613037s
Currency | Modification date check for Bio2RDF::Pubmed took 0.2892792224884033s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 108.47778463363647s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 19.55758261680603s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.5106050968170166s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.2923569679260254s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.31050944328308105s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 6.695252180099487s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.8986608982086182s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.670950174331665s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.3178713321685791s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.05010557174683s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.4607832431793213s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.779943943023682s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.3096415996551514s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.54185199737549s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.7111608982086182s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.4573173522949219s
Security | Sign check for Bio2RDF::Pubmed took 0.2644965648651123s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 3.448085069656372s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.5208568572998047s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.01998114585876465s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0005545616149902344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00014781951904296875s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 18.209433555603027s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 1.1444091796875e-05s
INFO | --- Analysis for Bio2RDF::Pubmed took 1046.385036945343s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 0.14705753326416016s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.01074528694152832s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.45084428787231445s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.018318891525268555s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0005402565002441406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 7.390975952148438e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 1.1444091796875e-05s
INFO | --- Analysis for Bio2RDF::Reactome took 9.45512866973877s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 0.1344587802886963s
Availability | VoID file availability check for Bio2RDF::Rhea took 5.0067901611328125e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.33109188079833984s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.018449068069458008s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0005433559417724609s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 5.364418029785156e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 8.58306884765625e-06s
INFO | --- Analysis for Bio2RDF::Rhea took 6.962631940841675s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.18319916725158691s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.008774042129516602s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 2.167715311050415s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.020851612091064453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0005273818969726562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.557868957519531e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 1.049041748046875e-05s
INFO | --- Analysis for Bio2RDF::Sabiork took 11.526159763336182s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.65415358543396s
Availability | VoID file availability check for Bio2RDF::Sgd took 1.0647656917572021s
Extra | Recovery of all triples for Bio2RDF::Sgd took 18.88143491744995s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.3484785556793213s
Amount of data | Number of triples check for Bio2RDF::Sgd took 50.619452714920044s
Interoperability | New terms check for Bio2RDF::Sgd took 40.37869310379028s
Versatility | Languages check for Bio2RDF::Sgd took 60.2360143661499s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.2643404006958008s
Security | Check HTTPS for Bio2RDF::Sgd took 0.1716141700744629s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.2944943904876709s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.28888678550720215s
Availability | RDF dump link check for Bio2RDF::Sgd took 1.0683350563049316s
License | MR license check for Bio2RDF::Sgd took 0.4879581928253174s
License | HR license check for Bio2RDF::Sgd took 60.257761001586914s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.2844512462615967s
Understandability | Number of label check for Bio2RDF::Sgd took 9.416851282119751s
Understandability | URI regex check for Bio2RDF::Sgd took 0.6219649314880371s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.2641005516052246s
Verifiability | Authors check for Bio2RDF::Sgd took 0.24741721153259277s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.40911269187927246s
Performance | Throughput check for Bio2RDF::Sgd took 10.908056735992432s
Verifiability | Contribs. check for Bio2RDF::Sgd took 1.5707886219024658s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.29018712043762207s
Interlinking | skos check for Bio2RDF::Sgd took 0.5120768547058105s
Interlinking | skos check for Bio2RDF::Sgd took 0.36472010612487793s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.2279057502746582s
Currency | Creation date check for Bio2RDF::Sgd took 0.4354703426361084s
Currency | Modification date check for Bio2RDF::Sgd took 0.2829585075378418s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 112.12874436378479s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 15.60950779914856s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.4749424457550049s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.3013589382171631s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.2604861259460449s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 6.31840705871582s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.8937580585479736s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6564638614654541s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.23839974403381348s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 65.71100091934204s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.413705587387085s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 6.288522958755493s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.3073480129241943s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.555245876312256s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.7146964073181152s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.4667835235595703s
Security | Sign check for Bio2RDF::Sgd took 0.257004976272583s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 3.700592517852783s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.7758452892303467s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.18305110931396484s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0005135536193847656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00010466575622558594s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 14.53287124633789s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.3589859008789062e-05s
INFO | --- Analysis for Bio2RDF::Sgd took 1046.8689811229706s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 8.630752563476562e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 7.3909759521484375e-06s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 1.4715428352355957s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.01788616180419922s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0005054473876953125s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.743171691894531e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-sgd-resources took 5.147592544555664s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.6326413154602051s
Availability | VoID file availability check for Bio2RDF::Sider took 1.0678248405456543s
Extra | Recovery of all triples for Bio2RDF::Sider took 18.16884160041809s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.3294517993927002s
Amount of data | Number of triples check for Bio2RDF::Sider took 49.61631727218628s
Interoperability | New terms check for Bio2RDF::Sider took 40.201515436172485s
Versatility | Languages check for Bio2RDF::Sider took 60.26718020439148s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.28848910331726074s
Security | Check HTTPS for Bio2RDF::Sider took 0.16284918785095215s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.38558220863342285s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.3077406883239746s
Availability | RDF dump link check for Bio2RDF::Sider took 1.0391063690185547s
License | MR license check for Bio2RDF::Sider took 0.2871127128601074s
License | HR license check for Bio2RDF::Sider took 60.25440812110901s
Amount of data | Number of property check for Bio2RDF::Sider took 0.27410316467285156s
Understandability | Number of label check for Bio2RDF::Sider took 9.43212628364563s
Understandability | URI regex check for Bio2RDF::Sider took 0.6002750396728516s
Understandability | Vocabs check for Bio2RDF::Sider took 0.26830339431762695s
Verifiability | Authors check for Bio2RDF::Sider took 0.28406834602355957s
Verifiability | Publishers check for Bio2RDF::Sider took 0.3722569942474365s
Performance | Throughput check for Bio2RDF::Sider took 10.903762340545654s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.7940654754638672s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.2871365547180176s
Interlinking | skos check for Bio2RDF::Sider took 0.6769769191741943s
Interlinking | skos check for Bio2RDF::Sider took 0.36518216133117676s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.23030638694763184s
Currency | Creation date check for Bio2RDF::Sider took 0.38674139976501465s
Currency | Modification date check for Bio2RDF::Sider took 0.24285650253295898s
Rep.Conc. | URIs length for Bio2RDF::Sider took 106.9872796535492s
Interoperability | New vocabularies check for Bio2RDF::Sider took 16.93621063232422s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.43964147567749023s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.29497623443603516s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.2724945545196533s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 7.040620565414429s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.8923420906066895s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6608114242553711s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.4006059169769287s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 65.27258825302124s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.4223268032073975s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 5.6210198402404785s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.286170244216919s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.54865336418152s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7019915580749512s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.4833834171295166s
Security | Sign check for Bio2RDF::Sider took 0.30243897438049316s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 3.4653191566467285s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 1.9667778015136719s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.18643641471862793s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.00066375732421875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.4345855712890625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 17.292852640151978s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.0728836059570312e-05s
INFO | --- Analysis for Bio2RDF::Sider took 1048.6726310253143s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 0.1485593318939209s
Availability | VoID file availability check for Bio2RDF::SPIKE took 3.814697265625e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.45960140228271484s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.017836809158325195s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0005080699920654297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 1.7404556274414062e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 1.0251998901367188e-05s
INFO | --- Analysis for Bio2RDF::SPIKE took 5.427271127700806s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.1961669921875e-05s
Availability | VoID file availability check for bio2rdf-taxon took 6.198883056640625e-06s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.29891133308410645s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.018374204635620117s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0005221366882324219s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 3.981590270996094e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-taxon took 2.1879661083221436s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.6570510864257812s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.9953708648681641s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 18.093265771865845s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.301046371459961s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 50.22639513015747s
Interoperability | New terms check for Bio2RDF::Taxonomy took 40.66291046142578s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.25506830215454s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.24999237060546875s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.14478015899658203s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.2862362861633301s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.24144339561462402s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 1.077143669128418s
License | MR license check for Bio2RDF::Taxonomy took 0.31807947158813477s
License | HR license check for Bio2RDF::Taxonomy took 60.272536516189575s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.2647218704223633s
Understandability | Number of label check for Bio2RDF::Taxonomy took 10.036818742752075s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.6429178714752197s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.25326037406921387s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.2890160083770752s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.42634105682373047s
Performance | Throughput check for Bio2RDF::Taxonomy took 10.832513093948364s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.7786293029785156s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.29483652114868164s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.48528409004211426s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.3708198070526123s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.25476670265197754s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.43495726585388184s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.2653768062591553s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 107.58160161972046s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 15.973777055740356s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.4753553867340088s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.2683684825897217s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.3255350589752197s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 6.622771501541138s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8900980949401855s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6828978061676025s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.2749757766723633s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 65.30239701271057s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.3843939304351807s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 5.701023817062378s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.3342795372009277s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.65737867355347s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7328858375549316s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.520233154296875s
Security | Sign check for Bio2RDF::Taxonomy took 0.3105459213256836s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 3.622469186782837s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 1.385798692703247s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.21435809135437012s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0005371570587158203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00012373924255371094s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 16.702363967895508s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 1.2636184692382812e-05s
INFO | --- Analysis for Bio2RDF::Taxonomy took 1050.711345911026s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.1771078109741211s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.011643171310424805s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.5545985698699951s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.01784205436706543s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0005197525024414062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 1.2874603271484375e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 1.4781951904296875e-05s
INFO | --- Analysis for Bio2RDF::Wikipathways took 20.91274642944336s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.749614953994751s
Availability | VoID file availability check for Bio2RDF::Wormbase took 1.0194039344787598s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 18.354658126831055s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.3073146343231201s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 50.95968794822693s
Interoperability | New terms check for Bio2RDF::Wormbase took 40.05665469169617s
Versatility | Languages check for Bio2RDF::Wormbase took 60.27338933944702s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.2667574882507324s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.16303539276123047s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.29745054244995117s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.29784297943115234s
Availability | RDF dump link check for Bio2RDF::Wormbase took 1.0234620571136475s
License | MR license check for Bio2RDF::Wormbase took 0.26427674293518066s
License | HR license check for Bio2RDF::Wormbase took 60.25619626045227s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.30015087127685547s
Understandability | Number of label check for Bio2RDF::Wormbase took 9.372583627700806s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.6182475090026855s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.25005245208740234s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.3231658935546875s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.5615193843841553s
Performance | Throughput check for Bio2RDF::Wormbase took 10.987094640731812s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.7673585414886475s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.25754570960998535s
Interlinking | skos check for Bio2RDF::Wormbase took 0.6764039993286133s
Interlinking | skos check for Bio2RDF::Wormbase took 0.35714125633239746s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.24245047569274902s
Currency | Creation date check for Bio2RDF::Wormbase took 0.3868281841278076s
Currency | Modification date check for Bio2RDF::Wormbase took 0.2665739059448242s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 109.09511256217957s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 14.767110347747803s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.43334341049194336s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.24942278861999512s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.24359750747680664s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 6.356005907058716s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.8941636085510254s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6634175777435303s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.3202188014984131s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 65.40272951126099s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.438737392425537s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 6.176177263259888s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.3059756755828857s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.53463292121887s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7089483737945557s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.4839799404144287s
Security | Sign check for Bio2RDF::Wormbase took 0.30281519889831543s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 19.288947820663452s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 3.8595094680786133s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.018092870712280273s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0005271434783935547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.916854858398438e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 15.247641801834106s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 1.0967254638671875e-05s
INFO | --- Analysis for Bio2RDF::Wormbase took 1061.8872842788696s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.30057358741760254s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.17990541458129883s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.38636231422424316s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.018372774124145508s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0005371570587158203s
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 1.0251998901367188e-05s
INFO | --- Analysis for Biographical Directory of the United States Congress took 4.038717746734619s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.07555627822875977s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.010856866836547852s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.4095001220703125s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.018651962280273438s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0005254745483398438s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.1682510375976562e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for A Short Biographical Dictionary of English Literature (RKBExplorer) took 2.555551290512085s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 9.560585021972656e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 3.5914294719696045s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.31290411949157715s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.018269062042236328s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0005254745483398438s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 4.029273986816406e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 1.3113021850585938e-05s
INFO | --- Analysis for BioLOD for Protein Data Bank Japan took 15.214513540267944s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.7777915000915527s
Availability | VoID file availability check for BioModels RDF took 0.2153313159942627s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.3842630386352539s
Reputation | Calculation of the PageRank for BioModels RDF took 0.018187284469604492s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0005331039428710938s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.647804260253906e-05s
Believability | Calculation of trust value for BioModels RDF took 1.1920928955078125e-05s
INFO | --- Analysis for BioModels RDF took 4.936476945877075s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 4.553794860839844e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 2.3841562271118164s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.5996184349060059s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.018610477447509766s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0005190372467041016s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006110668182373047s
Believability | Calculation of trust value for Amphibian gross anatomy took 9.775161743164062e-06s
INFO | --- Analysis for Amphibian gross anatomy took 15.885465145111084s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.506111145019531e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 2.0621542930603027s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.8474509716033936s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.018495559692382812s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0002911090850830078s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 9.298324584960938e-06s
INFO | --- Analysis for ABA Adult Mouse Brain took 15.072103261947632s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 9.274482727050781e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 2.1145718097686768s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.4938962459564209s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.018088102340698242s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0005252361297607422s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0014486312866210938s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 8.821487426757812e-06s
INFO | --- Analysis for Cancer Research and Management ACGT Master Ontology took 11.487673282623291s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 8.96453857421875e-05s
Availability | VoID file availability check for Animal natural history and life history took 2.014507293701172s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 1.6178696155548096s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.018238544464111328s
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.0005190372467041016s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.00031495094299316406s
Believability | Calculation of trust value for Animal natural history and life history took 9.775161743164062e-06s
INFO | --- Analysis for Animal natural history and life history took 11.168036460876465s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 2.543102264404297s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 1.7654876708984375s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.01815962791442871s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.00045609474182128906s
Believability | Calculation of trust value for Anatomical Entity Ontology took 8.344650268554688e-06s
INFO | --- Analysis for Anatomical Entity Ontology took 12.742832899093628s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 8.893013000488281e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 2.024358034133911s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.5386998653411865s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.01816844940185547s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0005297660827636719s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009505748748779297s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 6.9141387939453125e-06s
INFO | --- Analysis for Adverse Event Reporting ontology took 14.437827110290527s
Availability | SPARQL endpoint availability check for AI/RHEUM took 8.702278137207031e-05s
Availability | VoID file availability check for AI/RHEUM took 2.040933847427368s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.3845951557159424s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.018262386322021484s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0005366802215576172s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0003864765167236328s
Believability | Calculation of trust value for AI/RHEUM took 9.059906005859375e-06s
INFO | --- Analysis for AI/RHEUM took 12.751142263412476s
Availability | SPARQL endpoint availability check for Amino Acid took 8.368492126464844e-05s
Availability | VoID file availability check for Amino Acid took 2.0431206226348877s
Completeness | Calculation of interlinking completeness for Amino Acid took 2.0569510459899902s
Reputation | Calculation of the PageRank for Amino Acid took 0.018408536911010742s
Interlinking | Calculation of Degree of Connection for Amino Acid took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Amino Acid took 0.0005238056182861328s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.0002503395080566406s
Believability | Calculation of trust value for Amino Acid took 9.298324584960938e-06s
INFO | --- Analysis for Amino Acid took 15.003904104232788s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 8.58306884765625e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 2.1451830863952637s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 1.1682207584381104s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.018096446990966797s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0005247592926025391s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.00028228759765625s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 8.58306884765625e-06s
INFO | --- Analysis for Ascomycete phenotype ontology took 12.80254316329956s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 8.726119995117188e-05s
Availability | VoID file availability check for African Traditional Medicine took 1.9724864959716797s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 2.506007432937622s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.01863551139831543s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0005297660827636719s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.0002486705780029297s
Believability | Calculation of trust value for African Traditional Medicine took 1.049041748046875e-05s
INFO | --- Analysis for African Traditional Medicine took 16.88127565383911s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 8.726119995117188e-05s
Availability | VoID file availability check for Amphibian taxonomy took 1.9504575729370117s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.5520162582397461s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.018337488174438477s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0005309581756591797s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 9.822845458984375e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 8.821487426757812e-06s
INFO | --- Analysis for Amphibian taxonomy took 10.966321468353271s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 9.012222290039062e-05s
Availability | VoID file availability check for BioAssay Ontology took 2.0810434818267822s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 2.780646324157715s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.01861405372619629s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0005295276641845703s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013298988342285156s
Believability | Calculation of trust value for BioAssay Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for BioAssay Ontology took 13.335016965866089s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 8.58306884765625e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 2.0430431365966797s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.46605873107910156s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.01830148696899414s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0005397796630859375s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0003714561462402344s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 9.298324584960938e-06s
INFO | --- Analysis for Basic Vertebrate Anatomy took 11.489408493041992s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 8.821487426757812e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 1.959688663482666s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.3431432247161865s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.018798112869262695s
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.0005347728729248047s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003161430358886719s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 8.58306884765625e-06s
INFO | --- Analysis for Breast Cancer Grading Ontology took 10.863677501678467s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 0.00010371208190917969s
Availability | VoID file availability check for Bone Dysplasia Ontology took 1.864546298980713s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.3061954975128174s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.018103599548339844s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0005218982696533203s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0013432502746582031s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 9.5367431640625e-06s
INFO | --- Analysis for Bone Dysplasia Ontology took 13.830529689788818s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 9.512901306152344e-05s
Availability | VoID file availability check for Basic Formal Ontology took 1.8569073677062988s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.31120967864990234s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.01824641227722168s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0005395412445068359s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0004887580871582031s
Believability | Calculation of trust value for Basic Formal Ontology took 5.7220458984375e-06s
INFO | --- Analysis for Basic Formal Ontology took 12.756821155548096s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.3392181396484375e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 1.8689558506011963s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 2.876469850540161s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.018479585647583008s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0005242824554443359s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007004737854003906s
Believability | Calculation of trust value for Bleeding History Phenotype took 1.0251998901367188e-05s
INFO | --- Analysis for Bleeding History Phenotype took 13.3227698802948s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.3392181396484375e-05s
Availability | VoID file availability check for Bilateria anatomy took 2.3571972846984863s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.3925929069519043s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.018582582473754883s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0005362033843994141s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004305839538574219s
Believability | Calculation of trust value for Bilateria anatomy took 5.7220458984375e-06s
INFO | --- Analysis for Bilateria anatomy took 11.700483560562134s
Availability | SPARQL endpoint availability check for BIRNLex took 4.3392181396484375e-05s
Availability | VoID file availability check for BIRNLex took 1.8511488437652588s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.29122185707092285s
Reputation | Calculation of the PageRank for BIRNLex took 0.018196821212768555s
Interlinking | Calculation of Degree of Connection for BIRNLex took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BIRNLex took 0.000522613525390625s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014541149139404297s
Believability | Calculation of trust value for BIRNLex took 1.0251998901367188e-05s
INFO | --- Analysis for BIRNLex took 8.932141304016113s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 1.8512535095214844s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 1.0444955825805664s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020023822784423828s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0005371570587158203s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007202625274658203s
Believability | Calculation of trust value for Gene Regulation Ontology took 9.775161743164062e-06s
INFO | --- Analysis for Gene Regulation Ontology took 10.264353036880493s
Availability | SPARQL endpoint availability check for BioPAX took 8.678436279296875e-05s
Availability | VoID file availability check for BioPAX took 1.784501075744629s
Completeness | Calculation of interlinking completeness for BioPAX took 0.4799635410308838s
Reputation | Calculation of the PageRank for BioPAX took 0.018614530563354492s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0005266666412353516s
Interlinking | Calculation of Clustering coefficient for BioPAX took 9.751319885253906e-05s
Believability | Calculation of trust value for BioPAX took 8.821487426757812e-06s
INFO | --- Analysis for BioPAX took 9.519141912460327s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 8.344650268554688e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 1.8274376392364502s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 1.2491230964660645s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.01818537712097168s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0005421638488769531s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.00030994415283203125s
Believability | Calculation of trust value for Biomedical Resource Ontology took 9.5367431640625e-06s
INFO | --- Analysis for Biomedical Resource Ontology took 12.082340955734253s
Availability | SPARQL endpoint availability check for Spatial Ontology took 8.893013000488281e-05s
Availability | VoID file availability check for Spatial Ontology took 1.8534276485443115s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 1.3077847957611084s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.018976211547851562s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0005526542663574219s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00023221969604492188s
Believability | Calculation of trust value for Spatial Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for Spatial Ontology took 14.363206386566162s
Availability | SPARQL endpoint availability check for BioTop took 9.179115295410156e-05s
Availability | VoID file availability check for BioTop took 1.8327305316925049s
Completeness | Calculation of interlinking completeness for BioTop took 0.7453274726867676s
Reputation | Calculation of the PageRank for BioTop took 0.01868724822998047s
Interlinking | Calculation of Degree of Connection for BioTop took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0005300045013427734s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006420612335205078s
Believability | Calculation of trust value for BioTop took 9.298324584960938e-06s
INFO | --- Analysis for BioTop took 12.084744215011597s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 8.702278137207031e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 1.8854613304138184s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.3382687568664551s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.018157243728637695s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0005686283111572266s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008606910705566406s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 8.58306884765625e-06s
INFO | --- Analysis for BRENDA tissue / enzyme source took 9.546500205993652s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 1.8555972576141357s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.9502835273742676s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.01848006248474121s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0005419254302978516s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.001802206039428711s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 5.7220458984375e-06s
INFO | --- Analysis for Cancer Chemoprevention Ontology took 11.730117559432983s
Availability | SPARQL endpoint availability check for CAO took 4.172325134277344e-05s
Availability | VoID file availability check for CAO took 1.7889673709869385s
Completeness | Calculation of interlinking completeness for CAO took 0.7495718002319336s
Reputation | Calculation of the PageRank for CAO took 0.018127918243408203s
Interlinking | Calculation of Degree of Connection for CAO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CAO took 0.0005333423614501953s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0005857944488525391s
Believability | Calculation of trust value for CAO took 5.0067901611328125e-06s
INFO | --- Analysis for CAO took 14.054120779037476s
Availability | SPARQL endpoint availability check for CareLex took 4.57763671875e-05s
Availability | VoID file availability check for CareLex took 1.8608300685882568s
Completeness | Calculation of interlinking completeness for CareLex took 1.5269699096679688s
Reputation | Calculation of the PageRank for CareLex took 0.01821160316467285s
Interlinking | Calculation of Degree of Connection for CareLex took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for CareLex took 0.0005309581756591797s
Interlinking | Calculation of Clustering coefficient for CareLex took 4.696846008300781e-05s
Believability | Calculation of trust value for CareLex took 8.58306884765625e-06s
INFO | --- Analysis for CareLex took 14.979531526565552s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 8.58306884765625e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 1.8185784816741943s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 1.4622101783752441s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.01815342903137207s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.000545501708984375s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0008275508880615234s
Believability | Calculation of trust value for Cell Cycle Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for Cell Cycle Ontology took 12.924585342407227s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 8.225440979003906e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 1.825643539428711s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 1.2268307209014893s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.018065452575683594s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0005602836608886719s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.0002455711364746094s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for Comparative Data Analysis Ontology took 11.92167615890503s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 5.14984130859375e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 1.7983572483062744s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 3.272488832473755s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.019370555877685547s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0005342960357666016s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0007798671722412109s
Believability | Calculation of trust value for Chemical entities of biological interest took 8.106231689453125e-06s
INFO | --- Analysis for Chemical entities of biological interest took 15.867820501327515s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 5.459785461425781e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 1.867387294769287s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.30918169021606445s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.018121719360351562s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0006067752838134766s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002448558807373047s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 5.245208740234375e-06s
INFO | --- Analysis for Systems Chemical Biology/Chemogenomics took 12.918198823928833s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Chemical Information Ontology took 1.7883286476135254s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.396289587020874s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.018154621124267578s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0005214214324951172s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007352828979492188s
Believability | Calculation of trust value for Chemical Information Ontology took 7.867813110351562e-06s
INFO | --- Analysis for Chemical Information Ontology took 11.162832736968994s
Availability | SPARQL endpoint availability check for Cell type took 4.0531158447265625e-05s
Availability | VoID file availability check for Cell type took 1.8237881660461426s
Completeness | Calculation of interlinking completeness for Cell type took 0.5038759708404541s
Reputation | Calculation of the PageRank for Cell type took 0.018384218215942383s
Interlinking | Calculation of Degree of Connection for Cell type took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cell type took 0.0005846023559570312s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003829002380371094s
Believability | Calculation of trust value for Cell type took 1.2159347534179688e-05s
INFO | --- Analysis for Cell type took 11.543330907821655s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 8.702278137207031e-05s
Availability | VoID file availability check for Cell Line Ontology took 1.8515238761901855s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 1.8254637718200684s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.019715547561645508s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0005342960357666016s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008039474487304688s
Believability | Calculation of trust value for Cell Line Ontology took 8.106231689453125e-06s
INFO | --- Analysis for Cell Line Ontology took 10.863354206085205s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 0.00011301040649414062s
Availability | VoID file availability check for Clinical Measurement Ontology took 1.838517427444458s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 1.7480311393737793s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.018577098846435547s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0005383491516113281s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.0001685619354248047s
Believability | Calculation of trust value for Clinical Measurement Ontology took 9.059906005859375e-06s
INFO | --- Analysis for Clinical Measurement Ontology took 14.873966932296753s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 1.848008394241333s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.41442275047302246s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.018470287322998047s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0005192756652832031s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.00021958351135253906s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 9.5367431640625e-06s
INFO | --- Analysis for Computational Neuroscience Ontology took 11.85716199874878s
Availability | SPARQL endpoint availability check for Wheat trait took 4.124641418457031e-05s
Availability | VoID file availability check for Wheat trait took 1.8763370513916016s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.44464111328125s
Reputation | Calculation of the PageRank for Wheat trait took 0.01841139793395996s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0005311965942382812s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 6.103515625e-05s
Believability | Calculation of trust value for Wheat trait took 9.775161743164062e-06s
INFO | --- Analysis for Wheat trait took 10.39380931854248s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.6253204345703125e-05s
Availability | VoID file availability check for Cognitive Atlas took 1.8610365390777588s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.9043397903442383s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.018256425857543945s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0005300045013427734s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003287792205810547s
Believability | Calculation of trust value for Cognitive Atlas took 5.7220458984375e-06s
INFO | --- Analysis for Cognitive Atlas took 9.158665418624878s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 6.747245788574219e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 1.8147504329681396s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.30960702896118164s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.018508195877075195s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0005311965942382812s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007429122924804688s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 1.049041748046875e-05s
INFO | --- Analysis for Cognitive Paradigm Ontology took 11.919682264328003s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 4.124641418457031e-05s
Availability | VoID file availability check for Current Procedural Terminology took 1.8411364555358887s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.34422779083251953s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.018186330795288086s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0005490779876708984s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004031658172607422s
Believability | Calculation of trust value for Current Procedural Terminology took 4.76837158203125e-06s
INFO | --- Analysis for Current Procedural Terminology took 9.997799158096313s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 4.2438507080078125e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 1.819286823272705s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 1.3675057888031006s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.018056392669677734s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0005409717559814453s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017142295837402344s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 6.198883056640625e-06s
INFO | --- Analysis for CRISP Thesaurus, 2006 took 13.838928937911987s
Availability | SPARQL endpoint availability check for COSTART took 7.43865966796875e-05s
Availability | VoID file availability check for COSTART took 1.8794686794281006s
Completeness | Calculation of interlinking completeness for COSTART took 2.405343770980835s
Reputation | Calculation of the PageRank for COSTART took 0.018065214157104492s
Interlinking | Calculation of Degree of Connection for COSTART took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0005369186401367188s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009598731994628906s
Believability | Calculation of trust value for COSTART took 8.344650268554688e-06s
INFO | --- Analysis for COSTART took 16.452792406082153s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 8.320808410644531e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 1.9133687019348145s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.3106245994567871s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.018534421920776367s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0005643367767333984s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0004894733428955078s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 9.775161743164062e-06s
INFO | --- Analysis for Common Terminology Criteria for Adverse Events took 10.374038696289062s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 8.535385131835938e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 1.7948451042175293s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.3759191036224365s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.01833367347717285s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0005469322204589844s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.00044536590576171875s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 8.344650268554688e-06s
INFO | --- Analysis for Cerebrotendinous xanthomatosis took 10.652448892593384s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.124641418457031e-05s
Availability | VoID file availability check for Dendritic cell took 1.9028773307800293s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.46301913261413574s
Reputation | Calculation of the PageRank for Dendritic cell took 0.019032716751098633s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0005452632904052734s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.00029349327087402344s
Believability | Calculation of trust value for Dendritic cell took 9.775161743164062e-06s
INFO | --- Analysis for Dendritic cell took 12.176896095275879s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 8.511543273925781e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 1.828028917312622s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.36836862564086914s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.018993377685546875s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0005178451538085938s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.821487426757812e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 8.344650268554688e-06s
INFO | --- Analysis for Dictyostelium discoideum anatomy took 13.801965475082397s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 8.535385131835938e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 1.8350727558135986s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.7125186920166016s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.0182950496673584s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009262561798095703s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 1.0251998901367188e-05s
INFO | --- Analysis for Ontology for Drug Discovery Investigations took 12.630033016204834s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Diagnostic Ontology took 1.9017829895019531s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.29003167152404785s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.018230676651000977s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0005342960357666016s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.606910705566406e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 5.245208740234375e-06s
INFO | --- Analysis for Diagnostic Ontology took 8.99867844581604s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 1.8342039585113525s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.4207606315612793s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.018523693084716797s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0005216598510742188s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.0001575946807861328s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 7.867813110351562e-06s
INFO | --- Analysis for DIKB-Evidence-Ontology took 13.078083515167236s
Availability | SPARQL endpoint availability check for Human disease ontology took 8.440017700195312e-05s
Availability | VoID file availability check for Human disease ontology took 1.908311128616333s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.3253626823425293s
Reputation | Calculation of the PageRank for Human disease ontology took 0.018566370010375977s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0005278587341308594s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006082057952880859s
Believability | Calculation of trust value for Human disease ontology took 8.821487426757812e-06s
INFO | --- Analysis for Human disease ontology took 10.259555578231812s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 8.440017700195312e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 1.869023084640503s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.32749104499816895s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.018422842025756836s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0005242824554443359s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0007789134979248047s
Believability | Calculation of trust value for Electrocardiography Ontology took 9.059906005859375e-06s
INFO | --- Analysis for Electrocardiography Ontology took 12.070391416549683s
Availability | SPARQL endpoint availability check for Evidence codes took 9.179115295410156e-05s
Availability | VoID file availability check for Evidence codes took 2.128190279006958s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.42990612983703613s
Reputation | Calculation of the PageRank for Evidence codes took 0.01863884925842285s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.000518798828125s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 1.430511474609375e-05s
Believability | Calculation of trust value for Evidence codes took 8.344650268554688e-06s
INFO | --- Analysis for Evidence codes took 10.974883079528809s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 2.0653951168060303s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.6366312503814697s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.018496990203857422s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0005300045013427734s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0016820430755615234s
Believability | Calculation of trust value for Experimental Factor Ontology took 8.58306884765625e-06s
INFO | --- Analysis for Experimental Factor Ontology took 11.03325867652893s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 8.559226989746094e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 1.8460724353790283s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 1.8916635513305664s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.018453598022460938s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0005342960357666016s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011444091796875s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 8.344650268554688e-06s
INFO | --- Analysis for Human developmental anatomy, timed version took 12.058841228485107s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 8.58306884765625e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 1.8644287586212158s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.5188817977905273s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.01856398582458496s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0005276203155517578s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0006964206695556641s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 1.0013580322265625e-05s
INFO | --- Analysis for Human developmental anatomy, abstract version took 10.919435024261475s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 8.726119995117188e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 2.0196216106414795s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.30310845375061035s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.018526315689086914s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0005304813385009766s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0004980564117431641s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 1.0251998901367188e-05s
INFO | --- Analysis for Human developmental anatomy, abstract version, v2 took 11.755198240280151s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.315376281738281e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 1.8948180675506592s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.4323122501373291s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.01904749870300293s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.000522613525390625s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 1.33514404296875e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 9.059906005859375e-06s
INFO | --- Analysis for Mouse gross anatomy and development took 10.85494875907898s
Availability | SPARQL endpoint availability check for Environment Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for Environment Ontology took 2.618945360183716s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.45604658126831055s
Reputation | Calculation of the PageRank for Environment Ontology took 0.018313169479370117s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 2.86102294921875e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0005331039428710938s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.00038504600524902344s
Believability | Calculation of trust value for Environment Ontology took 8.58306884765625e-06s
INFO | --- Analysis for Environment Ontology took 10.395342111587524s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 8.320808410644531e-05s
Availability | VoID file availability check for Plant environmental conditions took 2.073754072189331s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.3318488597869873s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.018555641174316406s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0005464553833007812s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.00029015541076660156s
Believability | Calculation of trust value for Plant environmental conditions took 8.58306884765625e-06s
INFO | --- Analysis for Plant environmental conditions took 12.011288166046143s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 8.392333984375e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 1.9438390731811523s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 1.5910258293151855s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.018514633178710938s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0005240440368652344s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0011775493621826172s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 9.059906005859375e-06s
INFO | --- Analysis for Cardiac Electrophysiology Ontology took 14.190109729766846s
Availability | SPARQL endpoint availability check for Epilepsy took 8.678436279296875e-05s
Availability | VoID file availability check for Epilepsy took 1.8316717147827148s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.33382511138916016s
Reputation | Calculation of the PageRank for Epilepsy took 0.01846599578857422s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0005221366882324219s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.000125885009765625s
Believability | Calculation of trust value for Epilepsy took 8.58306884765625e-06s
INFO | --- Analysis for Epilepsy took 11.150595426559448s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.6253204345703125e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 1.920771598815918s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.9998831748962402s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.01809096336364746s
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.0005238056182861328s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011219978332519531s
Believability | Calculation of trust value for eagle-i research resource ontology took 9.298324584960938e-06s
INFO | --- Analysis for eagle-i research resource ontology took 11.282620429992676s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 9.512901306152344e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 1.8346519470214844s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.2801172733306885s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.018851518630981445s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0005300045013427734s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0010905265808105469s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 7.867813110351562e-06s
INFO | --- Analysis for eVOC (Expressed Sequence Annotation for Humans) took 11.785235166549683s
Availability | SPARQL endpoint availability check for ExO took 8.821487426757812e-05s
Availability | VoID file availability check for ExO took 1.9815161228179932s
Completeness | Calculation of interlinking completeness for ExO took 0.3598332405090332s
Reputation | Calculation of the PageRank for ExO took 0.019057035446166992s
Interlinking | Calculation of Degree of Connection for ExO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ExO took 0.0005252361297607422s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00024390220642089844s
Believability | Calculation of trust value for ExO took 9.059906005859375e-06s
INFO | --- Analysis for ExO took 12.566171169281006s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 0.0001556873321533203s
Availability | VoID file availability check for Fungal gross anatomy took 2.0663399696350098s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 1.277986764907837s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.018718481063842773s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0005259513854980469s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.000118255615234375s
Believability | Calculation of trust value for Fungal gross anatomy took 7.867813110351562e-06s
INFO | --- Analysis for Fungal gross anatomy took 12.6004478931427s
Availability | SPARQL endpoint availability check for Biological imaging methods took 9.036064147949219e-05s
Availability | VoID file availability check for Biological imaging methods took 1.864544153213501s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.6461114883422852s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.018303632736206055s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0005171298980712891s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00018596649169921875s
Believability | Calculation of trust value for Biological imaging methods took 8.821487426757812e-06s
INFO | --- Analysis for Biological imaging methods took 11.252774000167847s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 8.797645568847656e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 1.9109752178192139s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.7426772117614746s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.01868462562561035s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0005228519439697266s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006139278411865234s
Believability | Calculation of trust value for Drosophila gross anatomy took 7.62939453125e-06s
INFO | --- Analysis for Drosophila gross anatomy took 11.562065839767456s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 9.202957153320312e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 2.060234785079956s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.3087770938873291s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.019982099533081055s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0005331039428710938s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004038810729980469s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 7.62939453125e-06s
INFO | --- Analysis for FlyBase Controlled Vocabulary took 10.750316858291626s
Availability | SPARQL endpoint availability check for Drosophila development took 8.678436279296875e-05s
Availability | VoID file availability check for Drosophila development took 1.9106526374816895s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.5127997398376465s
Reputation | Calculation of the PageRank for Drosophila development took 0.018604516983032227s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0005295276641845703s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.553794860839844e-05s
Believability | Calculation of trust value for Drosophila development took 8.344650268554688e-06s
INFO | --- Analysis for Drosophila development took 10.026782274246216s
Availability | SPARQL endpoint availability check for Fly taxonomy took 8.678436279296875e-05s
Availability | VoID file availability check for Fly taxonomy took 1.9362342357635498s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.3897061347961426s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.019808053970336914s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0005235671997070312s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003790855407714844s
Believability | Calculation of trust value for Fly taxonomy took 1.239776611328125e-05s
INFO | --- Analysis for Fly taxonomy took 11.209226131439209s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 9.632110595703125e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 1.8552393913269043s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.3987550735473633s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.01866436004638672s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0005176067352294922s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.0002155303955078125s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 8.106231689453125e-06s
INFO | --- Analysis for FDA Medical Devices (2010) took 9.273902177810669s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 8.249282836914062e-05s
Availability | VoID file availability check for Family Health History Ontology took 1.862947702407837s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.5350360870361328s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.019173383712768555s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0005323886871337891s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0003960132598876953s
Believability | Calculation of trust value for Family Health History Ontology took 8.58306884765625e-06s
INFO | --- Analysis for Family Health History Ontology took 13.113148212432861s
Availability | SPARQL endpoint availability check for Influenza Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Influenza Ontology took 1.8708419799804688s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.3941972255706787s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.018860340118408203s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0005536079406738281s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0010416507720947266s
Believability | Calculation of trust value for Influenza Ontology took 7.867813110351562e-06s
INFO | --- Analysis for Influenza Ontology took 13.46885895729065s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 8.225440979003906e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 2.093729019165039s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.41034841537475586s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.018503427505493164s
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.000522613525390625s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.651878356933594e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 9.298324584960938e-06s
INFO | --- Analysis for Foundational Model of Anatomy took 10.697477340698242s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 8.440017700195312e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 2.3742856979370117s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.31922316551208496s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.020529508590698242s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0005307197570800781s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00014090538024902344s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 1.049041748046875e-05s
INFO | --- Analysis for Fission Yeast Phenotype Ontology took 11.66690468788147s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 8.940696716308594e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 1.8810820579528809s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.42627811431884766s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.018533706665039062s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0005207061767578125s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 8.940696716308594e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 9.059906005859375e-06s
INFO | --- Analysis for GeoSpecies Ontology took 15.127158641815186s
Availability | SPARQL endpoint availability check for General Formal Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for General Formal Ontology took 1.8933744430541992s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.4542558193206787s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.019925355911254883s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0005357265472412109s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00015974044799804688s
Believability | Calculation of trust value for General Formal Ontology took 9.775161743164062e-06s
INFO | --- Analysis for General Formal Ontology took 9.0541090965271s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 8.606910705566406e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 1.8973960876464844s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.4657630920410156s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.0182187557220459s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0005245208740234375s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0005877017974853516s
Believability | Calculation of trust value for General Formal Ontology: Biology took 8.344650268554688e-06s
INFO | --- Analysis for General Formal Ontology: Biology took 9.588403463363647s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 8.58306884765625e-05s
Availability | VoID file availability check for Gene Ontology Extension took 1.8753275871276855s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 2.2825467586517334s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.01792001724243164s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0005271434783935547s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008323192596435547s
Believability | Calculation of trust value for Gene Ontology Extension took 9.059906005859375e-06s
INFO | --- Analysis for Gene Ontology Extension took 11.97356653213501s
Availability | SPARQL endpoint availability check for Gene Ontology took 8.535385131835938e-05s
Availability | VoID file availability check for Gene Ontology took 1.8746507167816162s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.33564209938049316s
Reputation | Calculation of the PageRank for Gene Ontology took 0.018192529678344727s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0005190372467041016s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008733272552490234s
Believability | Calculation of trust value for Gene Ontology took 7.867813110351562e-06s
INFO | --- Analysis for Gene Ontology took 10.413480520248413s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 0.00010800361633300781s
Availability | VoID file availability check for Cereal Plant Development took 1.8728034496307373s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.2861611843109131s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.0186765193939209s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0005261898040771484s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 1.4066696166992188e-05s
Believability | Calculation of trust value for Cereal Plant Development took 8.58306884765625e-06s
INFO | --- Analysis for Cereal Plant Development took 11.428313493728638s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.3392181396484375e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 1.9503262042999268s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.6406853199005127s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.018471479415893555s
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.0005350112915039062s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004322528839111328s
Believability | Calculation of trust value for Cereal plant gross anatomy took 6.9141387939453125e-06s
INFO | --- Analysis for Cereal plant gross anatomy took 10.862223863601685s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 1.9284288883209229s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 1.4646327495574951s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.01909494400024414s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.00055694580078125s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007724761962890625s
Believability | Calculation of trust value for Gene Regulation Ontology took 9.775161743164062e-06s
INFO | --- Analysis for Gene Regulation Ontology took 13.193512678146362s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 1.8873538970947266s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.6039631366729736s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.019403457641601562s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0005197525024414062s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005602836608886719s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 5.245208740234375e-06s
INFO | --- Analysis for Hymenoptera Anatomy Ontology took 15.38368821144104s
Availability | SPARQL endpoint availability check for HCPCS took 6.127357482910156e-05s
Availability | VoID file availability check for HCPCS took 1.8713552951812744s
Completeness | Calculation of interlinking completeness for HCPCS took 0.4663515090942383s
Reputation | Calculation of the PageRank for HCPCS took 0.018452882766723633s
Interlinking | Calculation of Degree of Connection for HCPCS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HCPCS took 0.0005209445953369141s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00021147727966308594s
Believability | Calculation of trust value for HCPCS took 9.059906005859375e-06s
INFO | --- Analysis for HCPCS took 13.034243106842041s
Availability | SPARQL endpoint availability check for Health Level Seven took 9.036064147949219e-05s
Availability | VoID file availability check for Health Level Seven took 1.8078830242156982s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.371351957321167s
Reputation | Calculation of the PageRank for Health Level Seven took 0.01994919776916504s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0005223751068115234s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012350082397460938s
Believability | Calculation of trust value for Health Level Seven took 9.059906005859375e-06s
INFO | --- Analysis for Health Level Seven took 14.08304762840271s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 8.606910705566406e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 1.8625378608703613s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.30977463722229004s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020131587982177734s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0005185604095458984s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0003342628479003906s
Believability | Calculation of trust value for HEALTH_INDICATORS took 5.0067901611328125e-06s
INFO | --- Analysis for HEALTH_INDICATORS took 17.76793098449707s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 4.1961669921875e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 1.8560752868652344s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.36502504348754883s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.018293380737304688s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0005145072937011719s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 1.3589859008789062e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 8.344650268554688e-06s
INFO | --- Analysis for Ontology of homology and related concepts in biology took 10.399557113647461s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 9.632110595703125e-05s
Availability | VoID file availability check for HOM-HARVARD took 2.418748140335083s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 1.1573984622955322s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.018703699111938477s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0005452632904052734s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 1.4066696166992188e-05s
Believability | Calculation of trust value for HOM-HARVARD took 7.152557373046875e-06s
INFO | --- Analysis for HOM-HARVARD took 11.892881870269775s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 1.8934454917907715s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.31809401512145996s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.018986940383911133s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0011432170867919922s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0013365745544433594s
Believability | Calculation of trust value for Human Phenotype Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for Human Phenotype Ontology took 10.217771530151367s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 8.869171142578125e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 1.8931689262390137s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 1.9348013401031494s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.01930713653564453s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0005369186401367188s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.001013040542602539s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 8.344650268554688e-06s
INFO | --- Analysis for Host Pathogen Interactions Ontology took 15.192557334899902s
Availability | SPARQL endpoint availability check for HUGO took 8.58306884765625e-05s
Availability | VoID file availability check for HUGO took 1.854623556137085s
Completeness | Calculation of interlinking completeness for HUGO took 0.296464204788208s
Reputation | Calculation of the PageRank for HUGO took 0.02036309242248535s
Interlinking | Calculation of Degree of Connection for HUGO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0005457401275634766s
Interlinking | Calculation of Clustering coefficient for HUGO took 8.654594421386719e-05s
Believability | Calculation of trust value for HUGO took 9.5367431640625e-06s
INFO | --- Analysis for HUGO took 14.767132759094238s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Information Artifact Ontology took 1.8101320266723633s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.3772907257080078s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.018232345581054688s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0005190372467041016s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006349086761474609s
Believability | Calculation of trust value for Information Artifact Ontology took 8.106231689453125e-06s
INFO | --- Analysis for Information Artifact Ontology took 9.07349181175232s
Availability | SPARQL endpoint availability check for ICD10 took 8.249282836914062e-05s
Availability | VoID file availability check for ICD10 took 1.7883219718933105s
Completeness | Calculation of interlinking completeness for ICD10 took 0.7135083675384521s
Reputation | Calculation of the PageRank for ICD10 took 0.018568992614746094s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0005736351013183594s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.000797271728515625s
Believability | Calculation of trust value for ICD10 took 8.344650268554688e-06s
INFO | --- Analysis for ICD10 took 12.253899574279785s
Availability | SPARQL endpoint availability check for ICD10CM took 8.440017700195312e-05s
Availability | VoID file availability check for ICD10CM took 1.8291106224060059s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.2924337387084961s
Reputation | Calculation of the PageRank for ICD10CM took 0.0182492733001709s
Interlinking | Calculation of Degree of Connection for ICD10CM took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ICD10CM took 0.0005350112915039062s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0005948543548583984s
Believability | Calculation of trust value for ICD10CM took 8.344650268554688e-06s
INFO | --- Analysis for ICD10CM took 12.93677282333374s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.410743713378906e-05s
Availability | VoID file availability check for ICD-10-PCS took 1.8827779293060303s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 2.600957155227661s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.018116235733032227s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0005614757537841797s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00014901161193847656s
Believability | Calculation of trust value for ICD-10-PCS took 4.76837158203125e-06s
INFO | --- Analysis for ICD-10-PCS took 13.243700981140137s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 8.249282836914062e-05s
Availability | VoID file availability check for International Classification of Diseases took 1.8361105918884277s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.3965413570404053s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.018117666244506836s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0005345344543457031s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006215572357177734s
Believability | Calculation of trust value for International Classification of Diseases took 5.0067901611328125e-06s
INFO | --- Analysis for International Classification of Diseases took 11.294842720031738s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 4.172325134277344e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 1.788130521774292s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.6438043117523193s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.018401145935058594s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0005369186401367188s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.00045299530029296875s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 5.9604644775390625e-06s
INFO | --- Analysis for International Classification of Functioning, Disability and Health (ICF) took 11.179585456848145s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 4.315376281738281e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 1.7848782539367676s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.34891390800476074s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.018129825592041016s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0005245208740234375s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012035369873046875s
Believability | Calculation of trust value for International Classification for Nursing Practice took 5.245208740234375e-06s
INFO | --- Analysis for International Classification for Nursing Practice took 13.01319146156311s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 8.273124694824219e-05s
Availability | VoID file availability check for International Classification of Primary Care took 1.8165161609649658s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 1.8481595516204834s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.01827239990234375s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0005290508270263672s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.00044918060302734375s
Believability | Calculation of trust value for International Classification of Primary Care took 8.58306884765625e-06s
INFO | --- Analysis for International Classification of Primary Care took 15.628992795944214s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 8.416175842285156e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 2.3660593032836914s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.2810964584350586s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.018080711364746094s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008234977722167969s
Believability | Calculation of trust value for ICPC-2 PLUS took 8.344650268554688e-06s
INFO | --- Analysis for ICPC-2 PLUS took 10.854358673095703s
Availability | SPARQL endpoint availability check for ICPS Network took 8.344650268554688e-05s
Availability | VoID file availability check for ICPS Network took 1.9240217208862305s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.29216575622558594s
Reputation | Calculation of the PageRank for ICPS Network took 0.018311738967895508s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0005207061767578125s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00021576881408691406s
Believability | Calculation of trust value for ICPS Network took 4.76837158203125e-06s
INFO | --- Analysis for ICPS Network took 10.992533683776855s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 1.825148582458496s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 1.023611068725586s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.01828742027282715s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0005331039428710938s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008494853973388672s
Believability | Calculation of trust value for Infectious Disease Ontology took 8.106231689453125e-06s
INFO | --- Analysis for Infectious Disease Ontology took 11.38251256942749s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Brucellosis Ontology took 1.7977588176727295s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.2982494831085205s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.018169879913330078s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0005335807800292969s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.001165151596069336s
Believability | Calculation of trust value for Brucellosis Ontology took 4.76837158203125e-06s
INFO | --- Analysis for Brucellosis Ontology took 12.27041506767273s
Availability | SPARQL endpoint availability check for Malaria Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Malaria Ontology took 3.019770860671997s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 1.9878895282745361s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.018305540084838867s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0005276203155517578s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0012879371643066406s
Believability | Calculation of trust value for Malaria Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for Malaria Ontology took 14.446754217147827s
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 1.8468403816223145s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 3.200434446334839s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.018282651901245117s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.000537872314453125s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.00031185150146484375s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 4.76837158203125e-06s
INFO | --- Analysis for Event (INOH pathway ontology) took 17.657321214675903s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.5299530029296875e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 1.8196303844451904s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.48061084747314453s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.017998933792114258s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0005321502685546875s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.0001575946807861328s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 7.62939453125e-06s
INFO | --- Analysis for IMGT-ONTOLOGY took 12.47559142112732s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.57763671875e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 1.8259074687957764s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.5223855972290039s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.018187522888183594s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0005304813385009766s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005056858062744141s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 7.867813110351562e-06s
INFO | --- Analysis for Molecule role (INOH Protein name/family name ontology) took 11.492665767669678s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 5.9604644775390625e-05s
Availability | VoID file availability check for Interaction Network Ontology took 1.8623883724212646s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.7204651832580566s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.01836705207824707s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0005395412445068359s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007815361022949219s
Believability | Calculation of trust value for Interaction Network Ontology took 8.58306884765625e-06s
INFO | --- Analysis for Interaction Network Ontology took 14.910735607147217s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 8.440017700195312e-05s
Availability | VoID file availability check for Hewan Invertebrata took 1.8190011978149414s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.4813549518585205s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.019810914993286133s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0005578994750976562s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 1.3113021850585938e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 7.867813110351562e-06s
INFO | --- Analysis for Hewan Invertebrata took 10.313217878341675s
Availability | SPARQL endpoint availability check for IxnO took 4.3392181396484375e-05s
Availability | VoID file availability check for IxnO took 1.858452320098877s
Completeness | Calculation of interlinking completeness for IxnO took 0.8945708274841309s
Reputation | Calculation of the PageRank for IxnO took 0.018282651901245117s
Interlinking | Calculation of Degree of Connection for IxnO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0005247592926025391s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00018858909606933594s
Believability | Calculation of trust value for IxnO took 8.58306884765625e-06s
INFO | --- Analysis for IxnO took 13.597301483154297s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.267692565917969e-05s
Availability | VoID file availability check for SysMO-JERM took 1.81717848777771s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.48119282722473145s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.01821136474609375s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0005190372467041016s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0003726482391357422s
Believability | Calculation of trust value for SysMO-JERM took 5.245208740234375e-06s
INFO | --- Analysis for SysMO-JERM took 10.765677452087402s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 1.8771476745605469s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 2.942540407180786s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.018109798431396484s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 4.172325134277344e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0005228519439697266s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 1.1920928955078125e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for Kinetic Simulation Algorithm Ontology took 14.237138032913208s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.673004150390625e-05s
Availability | VoID file availability check for Loggerhead nesting took 1.8487446308135986s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 1.3146729469299316s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.01825237274169922s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0005705356597900391s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00020551681518554688s
Believability | Calculation of trust value for Loggerhead nesting took 8.821487426757812e-06s
INFO | --- Analysis for Loggerhead nesting took 13.963232517242432s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Lipid Ontology took 2.76602840423584s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 1.8075950145721436s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.019107341766357422s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0005447864532470703s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00020003318786621094s
Believability | Calculation of trust value for Lipid Ontology took 8.344650268554688e-06s
INFO | --- Analysis for Lipid Ontology took 14.835651874542236s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.291534423828125e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 1.8714797496795654s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.5428850650787354s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.018215656280517578s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0005228519439697266s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.001810312271118164s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 4.76837158203125e-06s
INFO | --- Analysis for Logical Observation Identifier Names and Codes took 15.126901388168335s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.410743713378906e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 1.782853603363037s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.335294246673584s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.025301218032836914s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0005311965942382812s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0007345676422119141s
Believability | Calculation of trust value for Mouse adult gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for Mouse adult gross anatomy took 10.341749429702759s
Availability | SPARQL endpoint availability check for Multiple alignment took 4.5299530029296875e-05s
Availability | VoID file availability check for Multiple alignment took 1.8294641971588135s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.31659889221191406s
Reputation | Calculation of the PageRank for Multiple alignment took 0.01813197135925293s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0005245208740234375s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.0002028942108154297s
Believability | Calculation of trust value for Multiple alignment took 5.0067901611328125e-06s
INFO | --- Analysis for Multiple alignment took 9.804020881652832s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 5.14984130859375e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 1.828136682510376s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 1.1961302757263184s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.018155813217163086s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0005316734313964844s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006861686706542969s
Believability | Calculation of trust value for Minimal anatomical terminology took 5.0067901611328125e-06s
INFO | --- Analysis for Minimal anatomical terminology took 14.160902500152588s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 4.2438507080078125e-05s
Availability | VoID file availability check for Breast tissue cell lines took 1.8337862491607666s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 1.3429126739501953s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.018288135528564453s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0005233287811279297s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004048347473144531s
Believability | Calculation of trust value for Breast tissue cell lines took 8.821487426757812e-06s
INFO | --- Analysis for Breast tissue cell lines took 13.248619556427002s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Cell line ontology took 1.853867530822754s
Completeness | Calculation of interlinking completeness for Cell line ontology took 1.410698413848877s
Reputation | Calculation of the PageRank for Cell line ontology took 0.018937349319458008s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0005178451538085938s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007231235504150391s
Believability | Calculation of trust value for Cell line ontology took 9.775161743164062e-06s
INFO | --- Analysis for Cell line ontology took 13.997204303741455s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Cell line ontology took 1.8606054782867432s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.6881544589996338s
Reputation | Calculation of the PageRank for Cell line ontology took 0.018480300903320312s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0005300045013427734s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0013904571533203125s
Believability | Calculation of trust value for Cell line ontology took 8.344650268554688e-06s
INFO | --- Analysis for Cell line ontology took 11.892197608947754s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 4.3392181396484375e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 1.8049705028533936s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.8242077827453613s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.018603086471557617s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0005466938018798828s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.0002751350402832031s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 8.344650268554688e-06s
INFO | --- Analysis for MIxS Controlled Vocabularies took 12.670078039169312s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.267692565917969e-05s
Availability | VoID file availability check for Master Drug Data Base took 1.8035492897033691s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.34107255935668945s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.018301010131835938s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0005462169647216797s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.0001773834228515625s
Believability | Calculation of trust value for Master Drug Data Base took 9.059906005859375e-06s
INFO | --- Analysis for Master Drug Data Base took 11.423079013824463s
Availability | SPARQL endpoint availability check for MedDRA took 4.363059997558594e-05s
Availability | VoID file availability check for MedDRA took 3.530869245529175s
Completeness | Calculation of interlinking completeness for MedDRA took 1.1927886009216309s
Reputation | Calculation of the PageRank for MedDRA took 0.018075942993164062s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.0005292892456054688s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011010169982910156s
Believability | Calculation of trust value for MedDRA took 5.0067901611328125e-06s
INFO | --- Analysis for MedDRA took 13.131851196289062s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 5.984306335449219e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 1.8292920589447021s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.34780216217041016s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.01821732521057129s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0005233287811279297s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008447170257568359s
Believability | Calculation of trust value for MedlinePlus Health Topics took 5.0067901611328125e-06s
INFO | --- Analysis for MedlinePlus Health Topics took 11.810671091079712s
Availability | SPARQL endpoint availability check for MeGO took 4.315376281738281e-05s
Availability | VoID file availability check for MeGO took 1.8242406845092773s
Completeness | Calculation of interlinking completeness for MeGO took 0.45482397079467773s
Reputation | Calculation of the PageRank for MeGO took 0.01897716522216797s
Interlinking | Calculation of Degree of Connection for MeGO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0005311965942382812s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00014710426330566406s
Believability | Calculation of trust value for MeGO took 9.298324584960938e-06s
INFO | --- Analysis for MeGO took 11.490073204040527s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 8.654594421386719e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 1.8109843730926514s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 3.0313212871551514s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.018219709396362305s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0005419254302978516s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0017597675323486328s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 9.059906005859375e-06s
INFO | --- Analysis for MESH Thesaurus (OWL version) took 16.158451080322266s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 1.8439946174621582s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 2.726647138595581s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.018107891082763672s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0005307197570800781s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006062984466552734s
Believability | Calculation of trust value for Mental Functioning Ontology took 7.867813110351562e-06s
INFO | --- Analysis for Mental Functioning Ontology took 13.884146213531494s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.76837158203125e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 1.8243811130523682s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 1.2090420722961426s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.01829051971435547s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0005340576171875s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005631446838378906s
Believability | Calculation of trust value for Medaka fish anatomy and development took 1.049041748046875e-05s
INFO | --- Analysis for Medaka fish anatomy and development took 12.43559455871582s
Availability | SPARQL endpoint availability check for Emotion Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Emotion Ontology took 1.8303563594818115s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 2.7775750160217285s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.0184633731842041s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0005438327789306641s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007505416870117188s
Believability | Calculation of trust value for Emotion Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for Emotion Ontology took 18.914358615875244s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 8.463859558105469e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 1.8398821353912354s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.48401618003845215s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.019089698791503906s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0005612373352050781s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00012254714965820312s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 9.5367431640625e-06s
INFO | --- Analysis for MaHCO - An MHC Ontology took 10.223953008651733s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 8.559226989746094e-05s
Availability | VoID file availability check for Protein-protein interaction took 2.5207812786102295s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.34938740730285645s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.018535852432250977s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0005412101745605469s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006761550903320312s
Believability | Calculation of trust value for Protein-protein interaction took 8.58306884765625e-06s
INFO | --- Analysis for Protein-protein interaction took 12.05816102027893s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.124641418457031e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 1.9098587036132812s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.4683685302734375s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.018790721893310547s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0005223751068115234s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0008404254913330078s
Believability | Calculation of trust value for Mosquito insecticide resistance took 7.62939453125e-06s
INFO | --- Analysis for Mosquito insecticide resistance took 11.952794790267944s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 5.3882598876953125e-05s
Availability | VoID file availability check for Measurement Method Ontology took 1.8763654232025146s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 1.0786960124969482s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.01837468147277832s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0005371570587158203s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00013971328735351562s
Believability | Calculation of trust value for Measurement Method Ontology took 7.867813110351562e-06s
INFO | --- Analysis for Measurement Method Ontology took 12.262290716171265s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for MGED Ontology took 2.10469913482666s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.49353599548339844s
Reputation | Calculation of the PageRank for MGED Ontology took 0.01843571662902832s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0005450248718261719s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0003809928894042969s
Believability | Calculation of trust value for MGED Ontology took 8.821487426757812e-06s
INFO | --- Analysis for MGED Ontology took 11.434252977371216s
Availability | SPARQL endpoint availability check for Protein modification took 4.100799560546875e-05s
Availability | VoID file availability check for Protein modification took 1.8210594654083252s
Completeness | Calculation of interlinking completeness for Protein modification took 1.3502912521362305s
Reputation | Calculation of the PageRank for Protein modification took 0.018569231033325195s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0005207061767578125s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00021767616271972656s
Believability | Calculation of trust value for Protein modification took 7.867813110351562e-06s
INFO | --- Analysis for Protein modification took 11.903344631195068s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 5.078315734863281e-05s
Availability | VoID file availability check for Mammalian phenotype took 1.8590567111968994s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 1.7111506462097168s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.018378496170043945s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0005290508270263672s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006325244903564453s
Believability | Calculation of trust value for Mammalian phenotype took 8.821487426757812e-06s
INFO | --- Analysis for Mammalian phenotype took 14.468433141708374s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.3392181396484375e-05s
Availability | VoID file availability check for Mouse pathology took 1.8070733547210693s
Completeness | Calculation of interlinking completeness for Mouse pathology took 3.1527295112609863s
Reputation | Calculation of the PageRank for Mouse pathology took 0.018401622772216797s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0005218982696533203s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.00046706199645996094s
Believability | Calculation of trust value for Mouse pathology took 9.298324584960938e-06s
INFO | --- Analysis for Mouse pathology took 19.699581146240234s
Availability | SPARQL endpoint availability check for Mass spectrometry took 8.153915405273438e-05s
Availability | VoID file availability check for Mass spectrometry took 1.8883354663848877s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 1.0745010375976562s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.018419981002807617s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0005362033843994141s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.00037360191345214844s
Believability | Calculation of trust value for Mass spectrometry took 8.106231689453125e-06s
INFO | --- Analysis for Mass spectrometry took 10.625216245651245s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 8.296966552734375e-05s
Availability | VoID file availability check for Medical Subject Headings took 3.982203245162964s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.7082152366638184s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.018698930740356445s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018131732940673828s
Believability | Calculation of trust value for Medical Subject Headings took 1.0251998901367188e-05s
INFO | --- Analysis for Medical Subject Headings took 12.862998247146606s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 0.00011467933654785156s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 1.8900001049041748s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.36745643615722656s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.018490314483642578s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0005276203155517578s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.0001761913299560547s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 9.059906005859375e-06s
INFO | --- Analysis for Metathesaurus CPT Hierarchical Terms took 9.986764669418335s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Natural Products Ontology took 1.9008467197418213s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 2.8371505737304688s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020050525665283203s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0005366802215576172s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0008027553558349609s
Believability | Calculation of trust value for Natural Products Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for Natural Products Ontology took 13.794727325439453s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 8.654594421386719e-05s
Availability | VoID file availability check for NCBI organismal classification took 2.340933322906494s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.5842444896697998s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.02079463005065918s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0005216598510742188s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0007772445678710938s
Believability | Calculation of trust value for NCBI organismal classification took 8.821487426757812e-06s
INFO | --- Analysis for NCBI organismal classification took 12.480616092681885s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 8.487701416015625e-05s
Availability | VoID file availability check for NCI Thesaurus took 2.2041664123535156s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.42946934700012207s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020109891891479492s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0005388259887695312s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0019233226776123047s
Believability | Calculation of trust value for NCI Thesaurus took 9.775161743164062e-06s
INFO | --- Analysis for NCI Thesaurus took 11.600571155548096s
Availability | SPARQL endpoint availability check for National Drug Data File took 7.700920104980469e-05s
Availability | VoID file availability check for National Drug Data File took 1.8116133213043213s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.8793675899505615s
Reputation | Calculation of the PageRank for National Drug Data File took 0.018531084060668945s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0005233287811279297s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006072521209716797s
Believability | Calculation of trust value for National Drug Data File took 1.0251998901367188e-05s
INFO | --- Analysis for National Drug Data File took 13.353839635848999s
Availability | SPARQL endpoint availability check for National Drug File took 0.00012874603271484375s
Availability | VoID file availability check for National Drug File took 1.8705828189849854s
Completeness | Calculation of interlinking completeness for National Drug File took 0.43694138526916504s
Reputation | Calculation of the PageRank for National Drug File took 0.020896196365356445s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0005359649658203125s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012004375457763672s
Believability | Calculation of trust value for National Drug File took 1.0728836059570312e-05s
INFO | --- Analysis for National Drug File took 9.708926916122437s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 8.559226989746094e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 1.844770908355713s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.31201910972595215s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.018546104431152344s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0005240440368652344s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011267662048339844s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 9.5367431640625e-06s
INFO | --- Analysis for Neural ElectroMagnetic Ontologies took 8.90913200378418s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 8.368492126464844e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 2.3803062438964844s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.4309067726135254s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.019409894943237305s
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.0005338191986083984s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.000675201416015625s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 9.775161743164062e-06s
INFO | --- Analysis for Neomark Oral Cancer Ontology took 11.578389883041382s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 0.00010466575622558594s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 1.8338541984558105s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.395160436630249s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.01861286163330078s
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.0005221366882324219s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00012302398681640625s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 8.821487426757812e-06s
INFO | --- Analysis for Neomark Oral Cancer-Centred Ontology took 9.95431637763977s
Availability | SPARQL endpoint availability check for NIFSTD took 9.059906005859375e-05s
Availability | VoID file availability check for NIFSTD took 1.874706506729126s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.4307723045349121s
Reputation | Calculation of the PageRank for NIFSTD took 0.0182187557220459s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0005173683166503906s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0018589496612548828s
Believability | Calculation of trust value for NIFSTD took 1.0013580322265625e-05s
INFO | --- Analysis for NIFSTD took 12.504016876220703s
Availability | SPARQL endpoint availability check for NIF Cell took 8.559226989746094e-05s
Availability | VoID file availability check for NIF Cell took 1.911083459854126s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.6239867210388184s
Reputation | Calculation of the PageRank for NIF Cell took 0.018273591995239258s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0005450248718261719s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013363361358642578s
Believability | Calculation of trust value for NIF Cell took 1.0251998901367188e-05s
INFO | --- Analysis for NIF Cell took 14.031025171279907s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 8.535385131835938e-05s
Availability | VoID file availability check for NIF Dysfunction took 1.845841407775879s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 1.8465139865875244s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.018596410751342773s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0005223751068115234s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0014619827270507812s
Believability | Calculation of trust value for NIF Dysfunction took 5.245208740234375e-06s
INFO | --- Analysis for NIF Dysfunction took 13.759107828140259s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 8.702278137207031e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 1.8662855625152588s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.33474254608154297s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.018619298934936523s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0005407333374023438s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005686283111572266s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 9.5367431640625e-06s
INFO | --- Analysis for Neural-Immune Gene Ontology took 18.71051573753357s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 8.416175842285156e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 1.8615055084228516s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.3945963382720947s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.018884897232055664s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.00057220458984375s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005469322204589844s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 8.58306884765625e-06s
INFO | --- Analysis for NMR-instrument specific component of metabolomics investigations took 12.198221683502197s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 1.9106709957122803s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 1.392672061920166s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.027173757553100586s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0009474754333496094s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.0001983642578125s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for Non Randomized Controlled Trials Ontology took 11.709524393081665s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 8.416175842285156e-05s
Availability | VoID file availability check for NanoParticle Ontology took 1.8396062850952148s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.3204817771911621s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.01834702491760254s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0005362033843994141s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.001172780990600586s
Believability | Calculation of trust value for NanoParticle Ontology took 9.059906005859375e-06s
INFO | --- Analysis for NanoParticle Ontology took 11.712231636047363s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 8.749961853027344e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 1.7995271682739258s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.4485023021697998s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.018183231353759766s
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.0005338191986083984s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007276535034179688s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 1.0251998901367188e-05s
INFO | --- Analysis for Ontology of Adverse Events (OAE) took 12.2132728099823s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 8.7738037109375e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 1.7899961471557617s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.30080437660217285s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.01854872703552246s
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.0005519390106201172s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0014374256134033203s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 8.821487426757812e-06s
INFO | --- Analysis for Ontology for Biomedical Investigations took 10.20037317276001s
Availability | SPARQL endpoint availability check for OBOE took 8.463859558105469e-05s
Availability | VoID file availability check for OBOE took 2.5553135871887207s
Completeness | Calculation of interlinking completeness for OBOE took 0.39853501319885254s
Reputation | Calculation of the PageRank for OBOE took 0.01851201057434082s
Interlinking | Calculation of Degree of Connection for OBOE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OBOE took 0.00052642822265625s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00011301040649414062s
Believability | Calculation of trust value for OBOE took 8.344650268554688e-06s
INFO | --- Analysis for OBOE took 10.479062795639038s
Availability | SPARQL endpoint availability check for OBOE SBC took 8.678436279296875e-05s
Availability | VoID file availability check for OBOE SBC took 1.828202486038208s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.4272012710571289s
Reputation | Calculation of the PageRank for OBOE SBC took 0.0185089111328125s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0005249977111816406s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007758140563964844s
Believability | Calculation of trust value for OBOE SBC took 9.775161743164062e-06s
INFO | --- Analysis for OBOE SBC took 9.61992073059082s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 9.059906005859375e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 2.49889874458313s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 1.8144056797027588s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.021694660186767578s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0005290508270263672s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005974769592285156s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 9.775161743164062e-06s
INFO | --- Analysis for Ontology of Clinical Research (OCRe) took 15.192129373550415s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 8.630752563476562e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 1.81901216506958s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 1.0271406173706055s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.01878499984741211s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0005276203155517578s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008404254913330078s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 9.298324584960938e-06s
INFO | --- Analysis for Ontology for disease genetic investigation took 10.579469442367554s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 8.7738037109375e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 1.814953088760376s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 5.701329231262207s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.018254518508911133s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0005199909210205078s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008490085601806641s
Believability | Calculation of trust value for Ontology for Genetic Interval took 9.059906005859375e-06s
INFO | --- Analysis for Ontology for Genetic Interval took 32.672738790512085s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 9.059906005859375e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 1.871034860610962s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 60.346274614334106s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.01892399787902832s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0005443096160888672s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.0002918243408203125s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 9.298324584960938e-06s
INFO | --- Analysis for Ontology of Glucose Metabolism Disorder took 455.4754955768585s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 9.512901306152344e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 1.8553860187530518s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 60.31165385246277s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.01858973503112793s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0005271434783935547s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006687641143798828s
Believability | Calculation of trust value for Ontology for General Medical Science took 9.059906005859375e-06s
INFO | --- Analysis for Ontology for General Medical Science took 251.16004705429077s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 8.463859558105469e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 1.8296151161193848s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 60.32740783691406s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.019455432891845703s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0005252361297607422s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0010974407196044922s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 1.0013580322265625e-05s
INFO | --- Analysis for Online Mendelian Inheritance in Man took 70.03121495246887s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 9.202957153320312e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 1.8905539512634277s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 119.67733860015869s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.01988077163696289s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.00037932395935058594s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 9.775161743164062e-06s
INFO | --- Analysis for Ontology for MicroRNA Target Prediction took 548.4066269397736s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 9.1552734375e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 1.860654354095459s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 179.80843925476074s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.01852130889892578s
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.0005238056182861328s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0006279945373535156s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 4.792213439941406e-05s
INFO | --- Analysis for Ontology of Medically Related Social Entities took 429.10185647010803s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 9.369850158691406e-05s
Availability | VoID file availability check for Ontology of Data Mining took 2.2120044231414795s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.41405177116394043s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.018620729446411133s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0005304813385009766s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007746219635009766s
Believability | Calculation of trust value for Ontology of Data Mining took 1.7404556274414062e-05s
INFO | --- Analysis for Ontology of Data Mining took 369.8505687713623s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 9.560585021972656e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 1.8288922309875488s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 120.08320426940918s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.018710613250732422s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0005407333374023438s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.0002543926239013672s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 5.245208740234375e-06s
INFO | --- Analysis for Ontology of General Purpose Datatypes took 309.2722759246826s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.863739013671875e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 1.883101224899292s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.41282081604003906s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.0183107852935791s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0005300045013427734s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006091594696044922s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 8.58306884765625e-06s
INFO | --- Analysis for Orphanet Ontology of Rare Diseases took 129.8983907699585s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 0.0001277923583984375s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 1.8637425899505615s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 60.30414819717407s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.019545316696166992s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0005221366882324219s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009241104125976562s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 8.106231689453125e-06s
INFO | --- Analysis for Ontology for Parasite LifeCycle took 69.43196868896484s
Availability | SPARQL endpoint availability check for Phenotypic quality took 0.00010180473327636719s
Availability | VoID file availability check for Phenotypic quality took 1.8869938850402832s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.3307609558105469s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020507335662841797s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0005433559417724609s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008680820465087891s
Believability | Calculation of trust value for Phenotypic quality took 9.5367431640625e-06s
INFO | --- Analysis for Phenotypic quality took 183.41687107086182s
Availability | SPARQL endpoint availability check for Physician Data Query took 8.630752563476562e-05s
Availability | VoID file availability check for Physician Data Query took 2.069401979446411s
Completeness | Calculation of interlinking completeness for Physician Data Query took 30.68226933479309s
Reputation | Calculation of the PageRank for Physician Data Query took 0.019951581954956055s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0005457401275634766s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008075237274169922s
Believability | Calculation of trust value for Physician Data Query took 9.059906005859375e-06s
INFO | --- Analysis for Physician Data Query took 117.90526723861694s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 9.226799011230469e-05s
Availability | VoID file availability check for Pediatric Terminology took 2.363022804260254s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.3083970546722412s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.0196688175201416s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0005335807800292969s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0008072853088378906s
Believability | Calculation of trust value for Pediatric Terminology took 8.821487426757812e-06s
INFO | --- Analysis for Pediatric Terminology took 41.9415009021759s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 9.274482727050781e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 1.841404914855957s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.3271336555480957s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.01862621307373047s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0005564689636230469s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00019979476928710938s
Believability | Calculation of trust value for Parasite Experiment Ontology took 9.775161743164062e-06s
INFO | --- Analysis for Parasite Experiment Ontology took 15.54539155960083s
Availability | SPARQL endpoint availability check for PHARE took 8.487701416015625e-05s
Availability | VoID file availability check for PHARE took 2.332852363586426s
Completeness | Calculation of interlinking completeness for PHARE took 0.340468168258667s
Reputation | Calculation of the PageRank for PHARE took 0.02017378807067871s
Interlinking | Calculation of Degree of Connection for PHARE took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PHARE took 0.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006377696990966797s
Believability | Calculation of trust value for PHARE took 8.58306884765625e-06s
INFO | --- Analysis for PHARE took 10.113690853118896s
Availability | SPARQL endpoint availability check for PKO_Re took 4.696846008300781e-05s
Availability | VoID file availability check for PKO_Re took 1.8225457668304443s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.34529805183410645s
Reputation | Calculation of the PageRank for PKO_Re took 0.01824951171875s
Interlinking | Calculation of Degree of Connection for PKO_Re took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PKO_Re took 0.0005466938018798828s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.0001697540283203125s
Believability | Calculation of trust value for PKO_Re took 9.298324584960938e-06s
INFO | --- Analysis for PKO_Re took 9.531863927841187s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.410743713378906e-05s
Availability | VoID file availability check for PMA 2010 took 1.9033620357513428s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.32576489448547363s
Reputation | Calculation of the PageRank for PMA 2010 took 0.018235445022583008s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0005233287811279297s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0008771419525146484s
Believability | Calculation of trust value for PMA 2010 took 9.059906005859375e-06s
INFO | --- Analysis for PMA 2010 took 9.24655294418335s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 9.751319885253906e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 2.4593029022216797s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.5495717525482178s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.019326448440551758s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0005326271057128906s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00019407272338867188s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 1.0013580322265625e-05s
INFO | --- Analysis for Physical Medicine and Rehabilitation took 11.039159536361694s
Availability | SPARQL endpoint availability check for Plant Anatomy took 8.702278137207031e-05s
Availability | VoID file availability check for Plant Anatomy took 2.366743564605713s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.4221458435058594s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.018529891967773438s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0005285739898681641s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.0003948211669921875s
Believability | Calculation of trust value for Plant Anatomy took 9.5367431640625e-06s
INFO | --- Analysis for Plant Anatomy took 10.731101036071777s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 8.702278137207031e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 1.840723991394043s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.46834778785705566s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.01823878288269043s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.000522613525390625s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 6.818771362304688e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 1.0251998901367188e-05s
INFO | --- Analysis for Plant Growth and Development Stage took 8.673346519470215s
Availability | SPARQL endpoint availability check for Plant Ontology took 0.0001285076141357422s
Availability | VoID file availability check for Plant Ontology took 1.8014655113220215s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.43094611167907715s
Reputation | Calculation of the PageRank for Plant Ontology took 0.018647432327270508s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0005333423614501953s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.00045108795166015625s
Believability | Calculation of trust value for Plant Ontology took 8.821487426757812e-06s
INFO | --- Analysis for Plant Ontology took 13.078744649887085s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 0.00010228157043457031s
Availability | VoID file availability check for PRotein Ontology (PRO) took 1.8648405075073242s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.3622279167175293s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.01810288429260254s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0005209445953369141s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006430149078369141s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 9.775161743164062e-06s
INFO | --- Analysis for PRotein Ontology (PRO) took 9.010007619857788s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 8.58306884765625e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 1.8187730312347412s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 1.3405425548553467s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.018678665161132812s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0006167888641357422s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.00029659271240234375s
Believability | Calculation of trust value for Proteomics data and process provenance took 9.775161743164062e-06s
INFO | --- Analysis for Proteomics data and process provenance took 11.305104970932007s
Availability | SPARQL endpoint availability check for Pathway ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Pathway ontology took 1.8811051845550537s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.40004897117614746s
Reputation | Calculation of the PageRank for Pathway ontology took 0.018229961395263672s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0005319118499755859s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00012969970703125s
Believability | Calculation of trust value for Pathway ontology took 9.5367431640625e-06s
INFO | --- Analysis for Pathway ontology took 14.647851705551147s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.7206878662109375e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 1.8242161273956299s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 1.1426002979278564s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.018256664276123047s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0005354881286621094s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 1.4066696166992188e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 9.775161743164062e-06s
INFO | --- Analysis for Quantitative Imaging Biomarker Ontology took 12.706588983535767s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 5.745887756347656e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 1.8387207984924316s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 1.1169581413269043s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.01847386360168457s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0005633831024169922s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017583370208740234s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 1.0013580322265625e-05s
INFO | --- Analysis for Read Codes, Clinical Terms Version 3 (CTV3) took 12.345696926116943s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 1.8736217021942139s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.358109712600708s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.01826786994934082s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0005464553833007812s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.0001285076141357422s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 9.059906005859375e-06s
INFO | --- Analysis for Randomized Controlled Trials (RCT) Ontology took 12.470415115356445s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 8.702278137207031e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 1.8459584712982178s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.30013513565063477s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.018862485885620117s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.894371032714844e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 9.059906005859375e-06s
INFO | --- Analysis for Reproductive trait and phenotype ontology took 8.474733352661133s
Availability | SPARQL endpoint availability check for Physico-chemical process took 4.3392181396484375e-05s
Availability | VoID file availability check for Physico-chemical process took 1.8090591430664062s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.38855433464050293s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.018492698669433594s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0005199909210205078s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00019359588623046875s
Believability | Calculation of trust value for Physico-chemical process took 8.106231689453125e-06s
INFO | --- Analysis for Physico-chemical process took 10.228045225143433s
Availability | SPARQL endpoint availability check for RadLex took 0.00010728836059570312s
Availability | VoID file availability check for RadLex took 1.8162949085235596s
Completeness | Calculation of interlinking completeness for RadLex took 0.3802313804626465s
Reputation | Calculation of the PageRank for RadLex took 0.018404722213745117s
Interlinking | Calculation of Degree of Connection for RadLex took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0005328655242919922s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.001461029052734375s
Believability | Calculation of trust value for RadLex took 9.059906005859375e-06s
INFO | --- Analysis for RadLex took 9.348987579345703s
Availability | SPARQL endpoint availability check for RNA ontology took 8.606910705566406e-05s
Availability | VoID file availability check for RNA ontology took 1.8535046577453613s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.3010265827178955s
Reputation | Calculation of the PageRank for RNA ontology took 0.018160104751586914s
Interlinking | Calculation of Degree of Connection for RNA ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RNA ontology took 0.0005564689636230469s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005507469177246094s
Believability | Calculation of trust value for RNA ontology took 9.298324584960938e-06s
INFO | --- Analysis for RNA ontology took 11.631940603256226s
Availability | SPARQL endpoint availability check for Role Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for Role Ontology took 1.8510594367980957s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.5003454685211182s
Reputation | Calculation of the PageRank for Role Ontology took 0.01860189437866211s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0005419254302978516s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00019931793212890625s
Believability | Calculation of trust value for Role Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for Role Ontology took 12.58055830001831s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Rat Strain Ontology took 1.8517816066741943s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.2922074794769287s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.018512725830078125s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0005242824554443359s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.0001766681671142578s
Believability | Calculation of trust value for Rat Strain Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for Rat Strain Ontology took 12.048835277557373s
Availability | SPARQL endpoint availability check for RxNORM took 8.821487426757812e-05s
Availability | VoID file availability check for RxNORM took 1.899932861328125s
Completeness | Calculation of interlinking completeness for RxNORM took 0.38891029357910156s
Reputation | Calculation of the PageRank for RxNORM took 0.01827239990234375s
Interlinking | Calculation of Degree of Connection for RxNORM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RxNORM took 0.0005323886871337891s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.000598907470703125s
Believability | Calculation of trust value for RxNORM took 9.775161743164062e-06s
INFO | --- Analysis for RxNORM took 11.705722570419312s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 8.678436279296875e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 1.7832045555114746s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.34286999702453613s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.018324613571166992s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0005252361297607422s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010266304016113281s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 8.58306884765625e-06s
INFO | --- Analysis for Subcellular Anatomy Ontology (SAO) took 11.383973836898804s
Availability | SPARQL endpoint availability check for Systems Biology took 8.916854858398438e-05s
Availability | VoID file availability check for Systems Biology took 1.8450250625610352s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.3481595516204834s
Reputation | Calculation of the PageRank for Systems Biology took 0.01862335205078125s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0005319118499755859s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.00048613548278808594s
Believability | Calculation of trust value for Systems Biology took 9.775161743164062e-06s
INFO | --- Analysis for Systems Biology took 12.877698421478271s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 1.8082633018493652s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 1.0838909149169922s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.019525527954101562s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0005199909210205078s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00010538101196289062s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 1.049041748046875e-05s
INFO | --- Analysis for Smoking Behavior Risk Ontology took 14.93881893157959s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 3.082467794418335s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 2.8241827487945557s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.018496036529541016s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0005383491516113281s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.001325368881225586s
Believability | Calculation of trust value for Sleep Domain Ontology took 9.775161743164062e-06s
INFO | --- Analysis for Sleep Domain Ontology took 14.907084703445435s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 8.678436279296875e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 1.8572709560394287s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.35298919677734375s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.019756793975830078s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0005297660827636719s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003325939178466797s
Believability | Calculation of trust value for Sample processing and separation techniques took 8.58306884765625e-06s
INFO | --- Analysis for Sample processing and separation techniques took 10.553011178970337s
Availability | SPARQL endpoint availability check for Student Health Record took 9.608268737792969e-05s
Availability | VoID file availability check for Student Health Record took 1.8674542903900146s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.3314676284790039s
Reputation | Calculation of the PageRank for Student Health Record took 0.01922917366027832s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0005168914794921875s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004394054412841797s
Believability | Calculation of trust value for Student Health Record took 8.106231689453125e-06s
INFO | --- Analysis for Student Health Record took 10.081236124038696s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 1.8462605476379395s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 1.4142670631408691s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.019194841384887695s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0005648136138916016s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012028217315673828s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for SemanticScience Integrated Ontology took 11.547794580459595s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 8.58306884765625e-05s
Availability | VoID file availability check for Situation-Based Access Control took 1.8280024528503418s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.30568599700927734s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.018492460250854492s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0005223751068115234s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00019884109497070312s
Believability | Calculation of trust value for Situation-Based Access Control took 9.775161743164062e-06s
INFO | --- Analysis for Situation-Based Access Control took 9.334570407867432s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 8.654594421386719e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 1.8552021980285645s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.41205382347106934s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.018412351608276367s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0005362033843994141s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0018780231475830078s
Believability | Calculation of trust value for SNOMED Clinical Terms took 8.58306884765625e-06s
INFO | --- Analysis for SNOMED Clinical Terms took 12.151260137557983s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.8160552978515625e-05s
Availability | VoID file availability check for SNP-Ontology took 1.8628904819488525s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.4710209369659424s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.018326282501220703s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0005383491516113281s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006773471832275391s
Believability | Calculation of trust value for SNP-Ontology took 9.5367431640625e-06s
INFO | --- Analysis for SNP-Ontology took 10.551701068878174s
Availability | SPARQL endpoint availability check for Sequence types and features took 8.487701416015625e-05s
Availability | VoID file availability check for Sequence types and features took 1.8866047859191895s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.4287679195404053s
Reputation | Calculation of the PageRank for Sequence types and features took 0.018796443939208984s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0005171298980712891s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.000553131103515625s
Believability | Calculation of trust value for Sequence types and features took 9.5367431640625e-06s
INFO | --- Analysis for Sequence types and features took 10.179004669189453s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 8.678436279296875e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 1.8078844547271729s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.534003734588623s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.01838827133178711s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0005300045013427734s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015420913696289062s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 9.775161743164062e-06s
INFO | --- Analysis for Suggested Ontology for Pharmacogenomics took 9.993829727172852s
Availability | SPARQL endpoint availability check for SoyOntology took 8.7738037109375e-05s
Availability | VoID file availability check for SoyOntology took 1.8080072402954102s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.7050936222076416s
Reputation | Calculation of the PageRank for SoyOntology took 0.018591642379760742s
Interlinking | Calculation of Degree of Connection for SoyOntology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SoyOntology took 0.0005180835723876953s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00012803077697753906s
Believability | Calculation of trust value for SoyOntology took 1.0013580322265625e-05s
INFO | --- Analysis for SoyOntology took 9.609325408935547s
Availability | SPARQL endpoint availability check for Spider Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Spider Ontology took 1.8638761043548584s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.47681140899658203s
Reputation | Calculation of the PageRank for Spider Ontology took 0.018776416778564453s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0005395412445068359s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00032401084899902344s
Believability | Calculation of trust value for Spider Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for Spider Ontology took 11.731841325759888s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 9.1552734375e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 2.328004837036133s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.9282073974609375s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.019446849822998047s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0006592273712158203s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.0003864765167236328s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for Solanaceae Phenotype Ontology took 12.899404764175415s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 4.7206878662109375e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 1.8648505210876465s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 1.1784932613372803s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.018338680267333984s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0005352497100830078s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004398822784423828s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 9.298324584960938e-06s
INFO | --- Analysis for Syndromic Surveillance Ontology took 10.265955209732056s
Availability | SPARQL endpoint availability check for Software Ontology took 9.369850158691406e-05s
Availability | VoID file availability check for Software Ontology took 3.8888638019561768s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.31731605529785156s
Reputation | Calculation of the PageRank for Software Ontology took 0.020279884338378906s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0005197525024414062s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00039267539978027344s
Believability | Calculation of trust value for Software Ontology took 9.5367431640625e-06s
INFO | --- Analysis for Software Ontology took 12.516940355300903s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 8.940696716308594e-05s
Availability | VoID file availability check for Tick gross anatomy took 1.8818073272705078s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.33721041679382324s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.018376588821411133s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.000553131103515625s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00025844573974609375s
Believability | Calculation of trust value for Tick gross anatomy took 4.506111145019531e-05s
INFO | --- Analysis for Tick gross anatomy took 12.451980829238892s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 1.8649816513061523s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.355039119720459s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.01843094825744629s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0005216598510742188s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008482933044433594s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 9.059906005859375e-06s
INFO | --- Analysis for Teleost Anatomy Ontology took 11.464059591293335s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 8.440017700195312e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 1.8008053302764893s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.4047064781188965s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.018270015716552734s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0005347728729248047s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 8.940696716308594e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 9.298324584960938e-06s
INFO | --- Analysis for Taxonomic rank vocabulary took 9.697099685668945s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 8.7738037109375e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 1.8517563343048096s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.4491262435913086s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.019308805465698242s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0005269050598144531s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.295608520507812e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 9.5367431640625e-06s
INFO | --- Analysis for Terminology for the Description of Dynamics took 9.367028713226318s
Availability | SPARQL endpoint availability check for Time Event Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Time Event Ontology took 1.8617103099822998s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.4375920295715332s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.018520355224609375s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.00054931640625s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008320808410644531s
Believability | Calculation of trust value for Time Event Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for Time Event Ontology took 12.111942291259766s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 0.000102996826171875s
Availability | VoID file availability check for Mosquito gross anatomy took 1.8389561176300049s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.3588395118713379s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.018040180206298828s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.000522613525390625s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.00037789344787597656s
Believability | Calculation of trust value for Mosquito gross anatomy took 8.344650268554688e-06s
INFO | --- Analysis for Mosquito gross anatomy took 12.720617055892944s
Availability | SPARQL endpoint availability check for thesaurus took 8.630752563476562e-05s
Availability | VoID file availability check for thesaurus took 1.8705415725708008s
Completeness | Calculation of interlinking completeness for thesaurus took 0.9775683879852295s
Reputation | Calculation of the PageRank for thesaurus took 0.018321990966796875s
Interlinking | Calculation of Degree of Connection for thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for thesaurus took 0.0005564689636230469s
Interlinking | Calculation of Clustering coefficient for thesaurus took 7.43865966796875e-05s
Believability | Calculation of trust value for thesaurus took 9.775161743164062e-06s
INFO | --- Analysis for thesaurus took 11.667637586593628s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 9.107589721679688e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 1.8597335815429688s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.8095662593841553s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.018181800842285156s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0005288124084472656s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.00033545494079589844s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 8.344650268554688e-06s
INFO | --- Analysis for Traditional Medicine Signs and Symptoms Value Set took 11.567958116531372s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 1.8077433109283447s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.8581407070159912s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.018281221389770508s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0005280971527099609s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008165836334228516s
Believability | Calculation of trust value for Translational Medicine Ontology took 9.059906005859375e-06s
INFO | --- Analysis for Translational Medicine Ontology took 10.37284803390503s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 8.821487426757812e-05s
Availability | VoID file availability check for Plant Trait Ontology took 1.8861188888549805s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 1.5310215950012207s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.018117189407348633s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0005292892456054688s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00015783309936523438s
Believability | Calculation of trust value for Plant Trait Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for Plant Trait Ontology took 11.280231952667236s
Availability | SPARQL endpoint availability check for TOK_Ontology took 6.723403930664062e-05s
Availability | VoID file availability check for TOK_Ontology took 1.8083512783050537s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.3232686519622803s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.01829075813293457s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0005269050598144531s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00017499923706054688s
Believability | Calculation of trust value for TOK_Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for TOK_Ontology took 11.20404601097107s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 8.726119995117188e-05s
Availability | VoID file availability check for Teleost taxonomy took 1.8414151668548584s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.3085310459136963s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.01839280128479004s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.0001952648162841797s
Believability | Calculation of trust value for Teleost taxonomy took 1.0013580322265625e-05s
INFO | --- Analysis for Teleost taxonomy took 9.350834369659424s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 8.893013000488281e-05s
Availability | VoID file availability check for Uber anatomy ontology took 2.403846502304077s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.30785369873046875s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.018114089965820312s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0005395412445068359s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0009925365447998047s
Believability | Calculation of trust value for Uber anatomy ontology took 9.5367431640625e-06s
INFO | --- Analysis for Uber anatomy ontology took 13.461201429367065s
Availability | SPARQL endpoint availability check for Units Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Units Ontology took 1.8273608684539795s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.32796454429626465s
Reputation | Calculation of the PageRank for Units Ontology took 0.018357038497924805s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0005750656127929688s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.0002396106719970703s
Believability | Calculation of trust value for Units Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for Units Ontology took 9.684128999710083s
Availability | SPARQL endpoint availability check for Units of measurement took 8.7738037109375e-05s
Availability | VoID file availability check for Units of measurement took 1.7985188961029053s
Completeness | Calculation of interlinking completeness for Units of measurement took 1.259423017501831s
Reputation | Calculation of the PageRank for Units of measurement took 0.0189058780670166s
Interlinking | Calculation of Degree of Connection for Units of measurement took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Units of measurement took 0.0005352497100830078s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.00028705596923828125s
Believability | Calculation of trust value for Units of measurement took 9.059906005859375e-06s
INFO | --- Analysis for Units of measurement took 12.072860717773438s
Availability | SPARQL endpoint availability check for VANDF took 0.0001373291015625s
Availability | VoID file availability check for VANDF took 1.863661289215088s
Completeness | Calculation of interlinking completeness for VANDF took 1.1111114025115967s
Reputation | Calculation of the PageRank for VANDF took 0.019041061401367188s
Interlinking | Calculation of Degree of Connection for VANDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for VANDF took 0.0005369186401367188s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0007004737854003906s
Believability | Calculation of trust value for VANDF took 9.298324584960938e-06s
INFO | --- Analysis for VANDF took 10.154672622680664s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 1.8850536346435547s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.4314589500427246s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.018209218978881836s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0005290508270263672s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0004222393035888672s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for Vertebrate Anatomy Ontology took 9.833930015563965s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 8.511543273925781e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 1.8335139751434326s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 1.3094098567962646s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.01839590072631836s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0005311965942382812s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006189346313476562s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 8.821487426757812e-06s
INFO | --- Analysis for vertebrate Homologous Organ Groups took 12.105401039123535s
Availability | SPARQL endpoint availability check for VIVO took 8.440017700195312e-05s
Availability | VoID file availability check for VIVO took 1.838649034500122s
Completeness | Calculation of interlinking completeness for VIVO took 0.39067602157592773s
Reputation | Calculation of the PageRank for VIVO took 0.018283843994140625s
Interlinking | Calculation of Degree of Connection for VIVO took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0005259513854980469s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003445148468017578s
Believability | Calculation of trust value for VIVO took 9.059906005859375e-06s
INFO | --- Analysis for VIVO took 8.93834114074707s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 9.250640869140625e-05s
Availability | VoID file availability check for Vaccine Ontology took 2.908252477645874s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.38249969482421875s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.018103361129760742s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0005156993865966797s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.001203775405883789s
Believability | Calculation of trust value for Vaccine Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for Vaccine Ontology took 10.596350193023682s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 1.854964256286621s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 1.6671836376190186s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.01927781105041504s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0005168914794921875s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.0001995563507080078s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 7.867813110351562e-06s
INFO | --- Analysis for Vertebrate Trait Ontology took 10.809203624725342s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 8.678436279296875e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 1.8442730903625488s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.343888521194458s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.018491268157958984s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0005428791046142578s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0005254745483398438s
Believability | Calculation of trust value for C. elegans gross anatomy took 1.049041748046875e-05s
INFO | --- Analysis for C. elegans gross anatomy took 13.183854341506958s
Availability | SPARQL endpoint availability check for C. elegans development took 0.00012135505676269531s
Availability | VoID file availability check for C. elegans development took 2.366999864578247s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.35564661026000977s
Reputation | Calculation of the PageRank for C. elegans development took 0.018326520919799805s
Interlinking | Calculation of Degree of Connection for C. elegans development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for C. elegans development took 0.0005316734313964844s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.38690185546875e-05s
Believability | Calculation of trust value for C. elegans development took 1.049041748046875e-05s
INFO | --- Analysis for C. elegans development took 11.04102611541748s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 8.511543273925781e-05s
Availability | VoID file availability check for C. elegans phenotype took 1.8686041831970215s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.3180563449859619s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.018123626708984375s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0005764961242675781s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 9.369850158691406e-05s
Believability | Calculation of trust value for C. elegans phenotype took 1.0967254638671875e-05s
INFO | --- Analysis for C. elegans phenotype took 9.676923990249634s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 8.749961853027344e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 2.349553346633911s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.4835817813873291s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.01844620704650879s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.00054168701171875s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0005781650543212891s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 8.106231689453125e-06s
INFO | --- Analysis for WHO Adverse Reaction Terminology took 11.640096187591553s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 8.630752563476562e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 1.8258671760559082s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.3433542251586914s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020415306091308594s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0005242824554443359s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006625652313232422s
Believability | Calculation of trust value for Xenopus anatomy and development took 1.0013580322265625e-05s
INFO | --- Analysis for Xenopus anatomy and development took 11.463883638381958s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 1.8289697170257568s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.3486905097961426s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.019986629486083984s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0005214214324951172s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00022864341735839844s
Believability | Calculation of trust value for Experimental Conditions Ontology took 9.5367431640625e-06s
INFO | --- Analysis for Experimental Conditions Ontology took 9.237731218338013s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 8.797645568847656e-05s
Availability | VoID file availability check for Yeast phenotypes took 1.8904540538787842s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 1.5954582691192627s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.018436908721923828s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0005204677581787109s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.00027441978454589844s
Believability | Calculation of trust value for Yeast phenotypes took 1.6927719116210938e-05s
INFO | --- Analysis for Yeast phenotypes took 14.070432424545288s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 8.845329284667969e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 1.8524549007415771s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.44225025177001953s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.018431663513183594s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.000530242919921875s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007433891296386719s
Believability | Calculation of trust value for Zebrafish anatomy and development took 1.0013580322265625e-05s
INFO | --- Analysis for Zebrafish anatomy and development took 10.682302236557007s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.7137682437896729s
Availability | VoID file availability check for BioSamples RDF took 0.2403886318206787s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.3107633590698242s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.0181429386138916s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0005269050598144531s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.409385681152344e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.2159347534179688e-05s
INFO | --- Analysis for BioSamples RDF took 3.9590818881988525s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.18422365188598633s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 8.58306884765625e-06s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 1.4674043655395508s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.01804971694946289s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0005280971527099609s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011324882507324219s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 1.1920928955078125e-05s
INFO | --- Analysis for Bank for International Settlements (BIS) Linked Data took 4.685580492019653s
Availability | SPARQL endpoint availability check for Bitzi took 4.2438507080078125e-05s
Availability | VoID file availability check for Bitzi took 0.267071008682251s
Completeness | Calculation of interlinking completeness for Bitzi took 0.4178905487060547s
Reputation | Calculation of the PageRank for Bitzi took 0.018146514892578125s
Interlinking | Calculation of Degree of Connection for Bitzi took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Bitzi took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Bitzi took 1.9311904907226562e-05s
Believability | Calculation of trust value for Bitzi took 9.775161743164062e-06s
INFO | --- Analysis for Bitzi took 2.979980945587158s
Availability | SPARQL endpoint availability check for BizkaiSense took 0.28345799446105957s
Availability | VoID file availability check for BizkaiSense took 0.11522221565246582s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.3931431770324707s
Reputation | Calculation of the PageRank for BizkaiSense took 0.01809978485107422s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0005261898040771484s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 1.1920928955078125e-05s
Believability | Calculation of trust value for BizkaiSense took 1.1205673217773438e-05s
INFO | --- Analysis for BizkaiSense took 2.759572982788086s
Availability | SPARQL endpoint availability check for blabla.itemlist took 8.797645568847656e-05s
Availability | VoID file availability check for blabla.itemlist took 20.004190921783447s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 1.4166593551635742s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.01809239387512207s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0005123615264892578s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 1.1444091796875e-05s
Believability | Calculation of trust value for blabla.itemlist took 1.1205673217773438e-05s
INFO | --- Analysis for blabla.itemlist took 53.88079047203064s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.100799560546875e-05s
Availability | VoID file availability check for blabla.itemlist took 20.10266423225403s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 1.927323341369629s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.018271207809448242s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0005204677581787109s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 1.2159347534179688e-05s
Believability | Calculation of trust value for blabla.itemlist took 1.1682510375976562e-05s
INFO | --- Analysis for blabla.itemlist took 53.86279249191284s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.1961669921875e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.6449840068817139s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.4042484760284424s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.018291950225830078s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0005290508270263672s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 3.7670135498046875e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.2006916999816895s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 30.273019552230835s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 20.08717131614685s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 1.166243314743042s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.018413782119750977s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0005350112915039062s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.604194641113281e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.2159347534179688e-05s
INFO | --- Analysis for British National Bibliography (BNB) - Linked Open Data took 141.96926045417786s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.4481387138366699s
Availability | VoID file availability check for Thesaurus BNCF took 0.2669398784637451s
Extra | Recovery of all triples for Thesaurus BNCF took 49.94015908241272s
Performance | Total latancy measurement for Thesaurus BNCF took 0.761953592300415s
Amount of data | Number of triples check for Thesaurus BNCF took 0.7544655799865723s
Interoperability | New terms check for Thesaurus BNCF took 1.4837422370910645s
Versatility | Languages check for Thesaurus BNCF took 6.17919659614563s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.9910910129547119s
Security | Check HTTPS for Thesaurus BNCF took 0.09639978408813477s
Interpretability | RDF structures check for Thesaurus BNCF took 0.13566946983337402s
Versatility | Serialization formats check for Thesaurus BNCF took 0.17171406745910645s
Availability | RDF dump link check for Thesaurus BNCF took 0.142333984375s
License | MR license check for Thesaurus BNCF took 0.1714458465576172s
License | HR license check for Thesaurus BNCF took 0.24768924713134766s
Amount of data | Number of property check for Thesaurus BNCF took 0.1471555233001709s
Understandability | Number of label check for Thesaurus BNCF took 0.26665592193603516s
Understandability | URI regex check for Thesaurus BNCF took 0.33053064346313477s
Understandability | Vocabs check for Thesaurus BNCF took 0.14301061630249023s
Verifiability | Authors check for Thesaurus BNCF took 0.1724538803100586s
Verifiability | Publishers check for Thesaurus BNCF took 0.14590787887573242s
Performance | Throughput check for Thesaurus BNCF took 10.903626441955566s
Amount of data | Check the number of entities for Thesaurus BNCF took 8.368492126464844e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.16089677810668945s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.15070414543151855s
Interlinking | skos check for Thesaurus BNCF took 0.21255016326904297s
Interlinking | skos check for Thesaurus BNCF took 0.21706366539001465s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.17428827285766602s
Currency | Creation date check for Thesaurus BNCF took 0.1618208885192871s
Currency | Modification date check for Thesaurus BNCF took 0.29613542556762695s
Rep.Conc. | URIs length for Thesaurus BNCF took 26.168619394302368s
Interoperability | New vocabularies check for Thesaurus BNCF took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.1589503288269043s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.19713521003723145s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.1555461883544922s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 10.782976865768433s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.4753227233886719s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.90435791015625s
Consistency | Disjoint class check for Thesaurus BNCF took 0.16417503356933594s
Consistency | Check Misplaced properties for Thesaurus BNCF took 1.5714750289916992s
Consistency | Misplaced classes for Thesaurus BNCF took 6.670377016067505s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 8.311103105545044s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.4970073699951172s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.4662868976593018s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.3522677421569824s
Security | Sign check for Thesaurus BNCF took 0.12320566177368164s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 24.108067750930786s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.336777925491333s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.017910480499267578s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.00051116943359375s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 5.888938903808594e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 1.9073486328125e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 1.2159347534179688e-05s
INFO | --- Analysis for Thesaurus BNCF took 199.8546872138977s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.21361064910888672s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.62939453125e-06s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.3646118640899658s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.4442102909088135s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.3868532180786133s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.7437520027160645s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.10577440261841s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.7263519763946533s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.16301465034484863s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.14187121391296387s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.24254798889160156s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.17898297309875488s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.09911465644836426s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.08338713645935s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.1151130199432373s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8209211826324463s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.19075894355773926s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.1892244815826416s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.44623279571533203s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4436304569244385s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 10.456496477127075s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 8.726119995117188e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3582956790924072s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.1416471004486084s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.14560532569885254s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.08324289321899414s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.1452937126159668s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2217090129852295s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.12472009658813477s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 14.833719968795776s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.18506741523742676s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.11614084243774414s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.18467926979064941s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5875225067138672s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.031037569046020508s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.028652191162109375s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.11802458763122559s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 10.880448818206787s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.21373271942138672s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.3547465801239014s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.8922412395477295s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.650076389312744s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03173565864562988s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.16489291191101074s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.07478690147399902s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6953914165496826s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.39066624641418457s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.11808443069458008s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0005228519439697266s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.6253204345703125e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.430511474609375e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1205673217773438e-05s
INFO | --- Analysis for BPR ? Bibliography of the Italian Parliament and electoral studies took 311.7708933353424s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 0.00012683868408203125s
Availability | VoID file availability check for Brazilian Politicians took 0.18534398078918457s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 1.4384410381317139s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.01877140998840332s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0005331039428710938s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 6.961822509765625e-05s
Believability | Calculation of trust value for Brazilian Politicians took 8.106231689453125e-06s
INFO | --- Analysis for Brazilian Politicians took 6.269421339035034s
Availability | SPARQL endpoint availability check for BrazilianCities took 254.91653752326965s
Availability | VoID file availability check for BrazilianCities took 6.67572021484375e-06s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.39856839179992676s
Reputation | Calculation of the PageRank for BrazilianCities took 0.018717050552368164s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0005738735198974609s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 1.621246337890625e-05s
Believability | Calculation of trust value for BrazilianCities took 1.0251998901367188e-05s
INFO | --- Analysis for BrazilianCities took 531.8428130149841s
Availability | SPARQL endpoint availability check for Bricklink took 1.239084243774414s
Availability | VoID file availability check for Bricklink took 0.5621147155761719s
Completeness | Calculation of interlinking completeness for Bricklink took 0.41546106338500977s
Reputation | Calculation of the PageRank for Bricklink took 0.018242597579956055s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0005192756652832031s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.580352783203125e-05s
Believability | Calculation of trust value for Bricklink took 1.2636184692382812e-05s
INFO | --- Analysis for Bricklink took 7.804126977920532s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.25072455406189s
Availability | VoID file availability check for British Museum Collection took 19.999687910079956s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.30715012550354004s
Reputation | Calculation of the PageRank for British Museum Collection took 0.01840829849243164s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 1.3589859008789062e-05s
Believability | Calculation of trust value for British Museum Collection took 1.2874603271484375e-05s
INFO | --- Analysis for British Museum Collection took 72.42535758018494s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 4.363059997558594e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 1.0251998901367188e-05s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.33881235122680664s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.01839423179626465s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.000518798828125s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 4.3392181396484375e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.2874603271484375e-05s
INFO | --- Analysis for Brown Corpus in RDF/NIF took 2.8821325302124023s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 60.065852880477905s
Availability | VoID file availability check for French Plant Health Bulletins took 40.09558725357056s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.38206934928894043s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.018346548080444336s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0005443096160888672s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 1.52587890625e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 1.3113021850585938e-05s
INFO | --- Analysis for French Plant Health Bulletins took 122.24910950660706s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 8.463859558105469e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.15173649787902832s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.30409955978393555s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.019864797592163086s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0005359649658203125s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 1.33514404296875e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 1.0967254638671875e-05s
INFO | --- Analysis for Bund Offener Haushalt took 2.421232223510742s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 0.04098033905029297s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.4694325923919678s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.018198728561401367s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0005400180816650391s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 1.3828277587890625e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 1.0967254638671875e-05s
INFO | --- Analysis for BundestagNebeneinkuenfte took 4.418817520141602s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.31183719635009766s
Availability | VoID file availability check for business.data.gov.uk took 0.3342318534851074s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.43263745307922363s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.019974708557128906s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0005297660827636719s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.078315734863281e-05s
Believability | Calculation of trust value for business.data.gov.uk took 9.775161743164062e-06s
INFO | --- Analysis for business.data.gov.uk took 3.6234471797943115s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.582648754119873s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.731137752532959s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 2.10422945022583s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 2.415196180343628s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.4249415397644043s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.7782495021820068s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 34.8385910987854s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.8223729133605957s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.7236015796661377s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 1.0813329219818115s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.5542304515838623s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.33394527435302734s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.38619112968444824s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 12.598453998565674s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.40059685707092285s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.41387248039245605s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.7344748973846436s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.3885204792022705s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.44240713119506836s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.3944437503814697s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 10.63890528678894s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 8.678436279296875e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.3607666492462158s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.3517134189605713s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.3821702003479004s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.39272546768188477s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.369006872177124s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.7858386039733887s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.5813052654266357s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 3.06868839263916s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.3723788261413574s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.47333431243896484s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.43543505668640137s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 0.8657772541046143s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.031876325607299805s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.028479576110839844s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.3772737979888916s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.481184482574463s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.4150681495666504s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.187687397003174s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.289639949798584s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.4622795581817627s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.032988786697387695s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.31911492347717285s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.37148571014404297s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1563.719927072525s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 1.1031646728515625s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.018522977828979492s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0005409717559814453s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.0067901611328125e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.430511474609375e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 1.1205673217773438e-05s
INFO | --- Analysis for Biblioteca Virtual Miguel de Cervantes took 1783.7556760311127s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 4.9114227294921875e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.29161834716796875s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.4218177795410156s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.020266294479370117s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0005202293395996094s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 1.2159347534179688e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 1.1444091796875e-05s
INFO | --- Analysis for Price changes due to cabbage imports took 17.804686546325684s
Availability | SPARQL endpoint availability check for cablegate took 2.066094398498535s
Availability | VoID file availability check for cablegate took 1.6421527862548828s
Completeness | Calculation of interlinking completeness for cablegate took 0.467679500579834s
Reputation | Calculation of the PageRank for cablegate took 0.01813530921936035s
Interlinking | Calculation of Degree of Connection for cablegate took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0005242824554443359s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.842613220214844e-05s
Believability | Calculation of trust value for cablegate took 1.0251998901367188e-05s
INFO | --- Analysis for cablegate took 18.893686294555664s
Availability | SPARQL endpoint availability check for Calames took 8.249282836914062e-05s
Availability | VoID file availability check for Calames took 21.369086980819702s
Completeness | Calculation of interlinking completeness for Calames took 0.3380441665649414s
Reputation | Calculation of the PageRank for Calames took 0.019278526306152344s
Interlinking | Calculation of Degree of Connection for Calames took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Calames took 0.0005204677581787109s
Interlinking | Calculation of Clustering coefficient for Calames took 3.6716461181640625e-05s
Believability | Calculation of trust value for Calames took 1.3828277587890625e-05s
INFO | --- Analysis for Calames took 45.010441303253174s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.2269589900970459s
Availability | VoID file availability check for CaLiGraph took 0.2453920841217041s
Extra | Recovery of all triples for CaLiGraph took 1.5005874633789062s
Performance | Total latancy measurement for CaLiGraph took 0.4854135513305664s
Amount of data | Number of triples check for CaLiGraph took 6.949442148208618s
Interoperability | New terms check for CaLiGraph took 1.9712715148925781s
Versatility | Languages check for CaLiGraph took 61.75078582763672s
Interpretability | Number of blank nodes check for CaLiGraph took 0.1363377571105957s
Interpretability | RDF structures check for CaLiGraph took 0.2830355167388916s
Versatility | Serialization formats check for CaLiGraph took 0.3377995491027832s
Availability | RDF dump link check for CaLiGraph took 0.22141408920288086s
License | MR license check for CaLiGraph took 0.8479735851287842s
License | HR license check for CaLiGraph took 61.59492301940918s
Amount of data | Number of property check for CaLiGraph took 0.12965607643127441s
Understandability | Number of label check for CaLiGraph took 3.408658981323242s
Understandability | URI regex check for CaLiGraph took 0.3916478157043457s
Understandability | Vocabs check for CaLiGraph took 0.16740918159484863s
Verifiability | Authors check for CaLiGraph took 0.27251482009887695s
Verifiability | Publishers check for CaLiGraph took 0.14889931678771973s
Performance | Throughput check for CaLiGraph took 10.55803894996643s
Amount of data | Check the number of entities for CaLiGraph took 0.013154745101928711s
Verifiability | Contribs. check for CaLiGraph took 0.23129796981811523s
Interlinking | sameAs chians check for CaLiGraph took 0.4571216106414795s
Interlinking | skos check for CaLiGraph took 0.17703819274902344s
Interlinking | skos check for CaLiGraph took 0.09644746780395508s
Timeliness | dataset update frequency check for CaLiGraph took 0.27054452896118164s
Currency | Creation date check for CaLiGraph took 0.2508127689361572s
Currency | Modification date check for CaLiGraph took 0.1374192237854004s
Rep.Conc. | URIs length for CaLiGraph took 43.19095969200134s
Interoperability | New vocabularies check for CaLiGraph took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.13711881637573242s
Accuracy | Check Functional Property for CaLiGraph took 0.24016594886779785s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.20322608947753906s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5128512382507324s
Accuracy | Check White space in annotation for CaLiGraph took 0.028627872467041016s
Accuracy | Check Datatype consistency for CaLiGraph took 0.028511524200439453s
Consistency | Disjoint class check for CaLiGraph took 0.14938974380493164s
Consistency | Check Misplaced properties for CaLiGraph took 42.5746865272522s
Consistency | Misplaced classes for CaLiGraph took 0.40682530403137207s
Consistency | Check Ontology hijacking for CaLiGraph took 1.9071261882781982s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.3007514476776123s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 43.3589391708374s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03340482711791992s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.41310906410217285s
Security | Sign check for CaLiGraph took 0.12215280532836914s
Availability | Check URIs Dereferenciability for CaLiGraph took 0.5249292850494385s
Completeness | Calculation of interlinking completeness for CaLiGraph took 2.0050292015075684s
Reputation | Calculation of the PageRank for CaLiGraph took 0.06269955635070801s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0005128383636474609s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 1.2636184692382812e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.430511474609375e-06s
Believability | Calculation of trust value for CaLiGraph took 1.0967254638671875e-05s
INFO | --- Analysis for CaLiGraph took 1466.5046014785767s
Availability | SPARQL endpoint availability check for can-link took 0.9138221740722656s
Availability | VoID file availability check for can-link took 0.5019698143005371s
Completeness | Calculation of interlinking completeness for can-link took 0.34246015548706055s
Reputation | Calculation of the PageRank for can-link took 0.0194547176361084s
Interlinking | Calculation of Degree of Connection for can-link took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for can-link took 0.0005311965942382812s
Interlinking | Calculation of Clustering coefficient for can-link took 1.1682510375976562e-05s
Believability | Calculation of trust value for can-link took 1.1444091796875e-05s
INFO | --- Analysis for can-link took 14.985714197158813s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.07293272018432617s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.447345495223999s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.020241260528564453s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0005326271057128906s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 1.1205673217773438e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 1.2159347534179688e-05s
INFO | --- Analysis for Postal codes Italy (LinkedOpenData.it) took 2.944159507751465s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 8.58306884765625e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 8.58306884765625e-06s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.43988847732543945s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.018702030181884766s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0005242824554443359s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 4.291534423828125e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 1.3828277587890625e-05s
INFO | --- Analysis for Catalan EuroWordNet-lemon lexicon (3.0) took 2.400916814804077s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 0.30738401412963867s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.13164496421813965s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.3737912178039551s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.01807093620300293s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0005199909210205078s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 1.4066696166992188e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 1.1682510375976562e-05s
INFO | --- Analysis for Catalogus Professorum Lipsiensis took 4.139273643493652s
Availability | SPARQL endpoint availability check for Norway catch records dataset took 9.608268737792969e-05s
Availability | VoID file availability check for Norway catch records dataset took 5.9604644775390625e-06s
Completeness | Calculation of interlinking completeness for Norway catch records dataset took 1.3519036769866943s
Reputation | Calculation of the PageRank for Norway catch records dataset took 0.028118133544921875s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset took 0.0008788108825683594s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset took 5.078315734863281e-05s
Believability | Calculation of trust value for Norway catch records dataset took 1.1682510375976562e-05s
INFO | --- Analysis for Norway catch records dataset took 3.9878692626953125s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 9.393692016601562e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.2165517807006836s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.0895321369171143s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.019461631774902344s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0005176067352294922s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 9.894371032714844e-05s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.2874603271484375e-05s
INFO | --- Analysis for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 37.22477841377258s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.951977014541626s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.35247087478637695s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.39078259468078613s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.01828289031982422s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0005125999450683594s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 3.695487976074219e-05s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 1.0967254638671875e-05s
INFO | --- Analysis for Linked Data Cultural Heritage Agency of the Netherlands took 15.211317777633667s
Availability | SPARQL endpoint availability check for Charging Stations took 4.744529724121094e-05s
Availability | VoID file availability check for Charging Stations took 1.2874603271484375e-05s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.43182992935180664s
Reputation | Calculation of the PageRank for Charging Stations took 0.01859450340270996s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.0005271434783935547s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 1.3589859008789062e-05s
Believability | Calculation of trust value for Charging Stations took 1.1682510375976562e-05s
INFO | --- Analysis for Charging Stations took 2.3109612464904785s
Availability | SPARQL endpoint availability check for Chat Game corpus took 9.059906005859375e-05s
Availability | VoID file availability check for Chat Game corpus took 9.5367431640625e-06s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.3139638900756836s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.018296480178833008s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0006325244903564453s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.62396240234375e-05s
Believability | Calculation of trust value for Chat Game corpus took 1.3113021850585938e-05s
INFO | --- Analysis for Chat Game corpus took 12.087285041809082s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 2.310885190963745s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.5198202133178711s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.29717421531677246s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.018073320388793945s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.000518798828125s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.4332275390625e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 7.3909759521484375e-06s
INFO | --- Analysis for Chemical Entities of Biological Interest (ChEBI) took 5.101694583892822s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.100799560546875e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.5269584655761719s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.27782368659973145s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.018062114715576172s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0005142688751220703s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.1975250244140625e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 7.3909759521484375e-06s
INFO | --- Analysis for Chem2Bio2RDF took 3.6329550743103027s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.6264026165008545s
Availability | VoID file availability check for ChEMBL RDF took 0.2353823184967041s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.6158196926116943s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.01836371421813965s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0005621910095214844s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 4.9591064453125e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.3589859008789062e-05s
INFO | --- Analysis for ChEMBL RDF took 3.809267520904541s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 0.00026226043701171875s
Availability | VoID file availability check for ChemPedia RDF took 1.0407865047454834s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.3645346164703369s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.018286943435668945s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0005388259887695312s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 1.0967254638671875e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.239776611328125e-05s
INFO | --- Analysis for ChemPedia RDF took 12.257801055908203s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 4.0531158447265625e-05s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 6.4373016357421875e-06s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 1.0003397464752197s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.01804351806640625s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0005278587341308594s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 1.4066696166992188e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 1.2874603271484375e-05s
INFO | --- Analysis for Chinese Red Song Linked Data Dataset took 3.9823672771453857s
Availability | SPARQL endpoint availability check for Chronicling America took 8.749961853027344e-05s
Availability | VoID file availability check for Chronicling America took 0.8021135330200195s
Completeness | Calculation of interlinking completeness for Chronicling America took 1.3722553253173828s
Reputation | Calculation of the PageRank for Chronicling America took 0.018595457077026367s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0005562305450439453s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.0001087188720703125s
Believability | Calculation of trust value for Chronicling America took 1.2159347534179688e-05s
INFO | --- Analysis for Chronicling America took 249.98773336410522s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.8399572372436523s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 2.465794801712036s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 64.12167811393738s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.6138808727264404s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.8382899761199951s
Interoperability | New terms check for Cultural Heritage Thesaurus took 1.7505731582641602s
Versatility | Languages check for Cultural Heritage Thesaurus took 2.754523277282715s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 1.1381983757019043s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.323322057723999s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.3125476837158203s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 9.391897201538086s
License | MR license check for Cultural Heritage Thesaurus took 0.2769622802734375s
License | HR license check for Cultural Heritage Thesaurus took 0.6445250511169434s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.31537723541259766s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.3899693489074707s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.534127950668335s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.2765960693359375s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.46793341636657715s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.28821349143981934s
Performance | Throughput check for Cultural Heritage Thesaurus took 12.416213035583496s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 3.814697265625e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.2675743103027344s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.2621927261352539s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.29123687744140625s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.34610533714294434s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.2784585952758789s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.3733692169189453s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.29984259605407715s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 11.55251955986023s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 1.060762643814087s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.28795313835144043s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.28140711784362793s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.3071322441101074s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 3.288846254348755s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.21958494186401367s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.31007957458496094s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.888777732849121s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.28931760787963867s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 17.27682876586914s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 4.505419492721558s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00014901161193847656s
Security | Sign check for Cultural Heritage Thesaurus took 0.27537989616394043s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 1.669753074645996s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.018359661102294922s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0005319118499755859s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 9.799003601074219e-05s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 0.49724507331848145s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 1.9311904907226562e-05s
INFO | --- Analysis for Cultural Heritage Thesaurus took 667.310546875s
Availability | SPARQL endpoint availability check for ciard-ring took 8.988380432128906e-05s
Availability | VoID file availability check for ciard-ring took 6.67572021484375e-06s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.7084689140319824s
Reputation | Calculation of the PageRank for ciard-ring took 0.018706798553466797s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0005433559417724609s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 5.507469177246094e-05s
Believability | Calculation of trust value for ciard-ring took 1.1205673217773438e-05s
INFO | --- Analysis for ciard-ring took 187.5775442123413s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 0.6829581260681152s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 1.205017328262329s
Extra | Recovery of all triples for Cinémathèque québécoise Linked Open Data took 19.831114768981934s
Performance | Total latancy measurement for Cinémathèque québécoise Linked Open Data took 1.8733835220336914s
Amount of data | Number of triples check for Cinémathèque québécoise Linked Open Data took 10.463765144348145s
Interoperability | New terms check for Cinémathèque québécoise Linked Open Data took 1.681699275970459s
Versatility | Languages check for Cinémathèque québécoise Linked Open Data took 60.39564847946167s
Interpretability | Number of blank nodes check for Cinémathèque québécoise Linked Open Data took 4.9178361892700195s
Interpretability | RDF structures check for Cinémathèque québécoise Linked Open Data took 0.37090301513671875s
Versatility | Serialization formats check for Cinémathèque québécoise Linked Open Data took 0.3912220001220703s
Availability | RDF dump link check for Cinémathèque québécoise Linked Open Data took 0.3511488437652588s
License | MR license check for Cinémathèque québécoise Linked Open Data took 0.35900068283081055s
License | HR license check for Cinémathèque québécoise Linked Open Data took 22.385860204696655s
Amount of data | Number of property check for Cinémathèque québécoise Linked Open Data took 0.3612818717956543s
Understandability | Number of label check for Cinémathèque québécoise Linked Open Data took 1.5185377597808838s
Understandability | URI regex check for Cinémathèque québécoise Linked Open Data took 0.7916834354400635s
Understandability | Vocabs check for Cinémathèque québécoise Linked Open Data took 0.34682703018188477s
Verifiability | Authors check for Cinémathèque québécoise Linked Open Data took 0.3520479202270508s
Verifiability | Publishers check for Cinémathèque québécoise Linked Open Data took 0.3447744846343994s
Performance | Throughput check for Cinémathèque québécoise Linked Open Data took 11.014263391494751s
Amount of data | Check the number of entities for Cinémathèque québécoise Linked Open Data took 9.608268737792969e-05s
Verifiability | Contribs. check for Cinémathèque québécoise Linked Open Data took 0.3506600856781006s
Interlinking | sameAs chians check for Cinémathèque québécoise Linked Open Data took 0.47405314445495605s
Interlinking | skos check for Cinémathèque québécoise Linked Open Data took 0.44284510612487793s
Interlinking | skos check for Cinémathèque québécoise Linked Open Data took 0.35024094581604004s
Timeliness | dataset update frequency check for Cinémathèque québécoise Linked Open Data took 0.3881866931915283s
Currency | Creation date check for Cinémathèque québécoise Linked Open Data took 0.3925786018371582s
Currency | Modification date check for Cinémathèque québécoise Linked Open Data took 0.7436394691467285s
Rep.Conc. | URIs length for Cinémathèque québécoise Linked Open Data took 19.598438024520874s
Interoperability | New vocabularies check for Cinémathèque québécoise Linked Open Data took 8.404367208480835s
Consistency | Deprecated classes/propertiers check for Cinémathèque québécoise Linked Open Data took 0.3604850769042969s
Accuracy | Check Functional Property for Cinémathèque québécoise Linked Open Data took 0.37498950958251953s
Accuracy | Check Inverse Functional Property for Cinémathèque québécoise Linked Open Data took 0.3711695671081543s
Accuracy | Check Empty annotation labels for Cinémathèque québécoise Linked Open Data took 9.018143653869629s
Accuracy | Check White space in annotation for Cinémathèque québécoise Linked Open Data took 2.006967544555664s
Accuracy | Check Datatype consistency for Cinémathèque québécoise Linked Open Data took 3.5141875743865967s
Consistency | Disjoint class check for Cinémathèque québécoise Linked Open Data took 0.3653380870819092s
Consistency | Check Misplaced properties for Cinémathèque québécoise Linked Open Data took 0.7271580696105957s
Consistency | Misplaced classes for Cinémathèque québécoise Linked Open Data took 7.864356279373169s
Consistency | Check Ontology hijacking for Cinémathèque québécoise Linked Open Data took 19.207353353500366s
Consistency | Check Invalid usage of undefined classes for Cinémathèque québécoise Linked Open Data took 1.324160099029541s
Consistency | Check Invalid usage of undefined properties for Cinémathèque québécoise Linked Open Data took 1.701740026473999s
Conciseness | Check Extensional conciseness for Cinémathèque québécoise Linked Open Data took 2.8031861782073975s
Conciseness | Check Intensional conciseness for Cinémathèque québécoise Linked Open Data took 0.7450113296508789s
Security | Sign check for Cinémathèque québécoise Linked Open Data took 0.3442254066467285s
Availability | Check URIs Dereferenciability for Cinémathèque québécoise Linked Open Data took 18.792843341827393s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 180.21617221832275s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.019163846969604492s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0005180835723876953s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 0.00010752677917480469s
Interoperability | Check the re-using of existing vocabs for Cinémathèque québécoise Linked Open Data took 7.755888938903809s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 1.33514404296875e-05s
INFO | --- Analysis for Cinémathèque québécoise Linked Open Data took 813.9661009311676s
Availability | SPARQL endpoint availability check for CIPFA took 9.34600830078125e-05s
Availability | VoID file availability check for CIPFA took 0.10163331031799316s
Completeness | Calculation of interlinking completeness for CIPFA took 120.16136431694031s
Reputation | Calculation of the PageRank for CIPFA took 0.023858308792114258s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0006625652313232422s
Interlinking | Calculation of Clustering coefficient for CIPFA took 5.459785461425781e-05s
Believability | Calculation of trust value for CIPFA took 1.1205673217773438e-05s
INFO | --- Analysis for CIPFA took 542.1066560745239s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.05002546310425s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 40.03192949295044s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.3730177879333496s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.019989490509033203s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0005483627319335938s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.00040459632873535156s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 1.6689300537109375e-05s
INFO | --- Analysis for Comprehensive Knowledge Archive Network took 621.8152494430542s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 0.787531852722168s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.1686389446258545s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.4153931140899658s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.018879175186157227s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0005288124084472656s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 9.202957153320312e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 9.059906005859375e-06s
INFO | --- Analysis for Linked Clean Energy Data (reegle.info) took 304.18052911758423s
Availability | SPARQL endpoint availability check for CLLD-afbo took 8.7738037109375e-05s
Availability | VoID file availability check for CLLD-afbo took 0.22760415077209473s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.3306756019592285s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.01838541030883789s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0005297660827636719s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.557868957519531e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-afbo took 3.0994415283203125e-06s
Believability | Calculation of trust value for CLLD-afbo took 1.1444091796875e-05s
INFO | --- Analysis for CLLD-afbo took 122.70621514320374s
Availability | SPARQL endpoint availability check for CLLD-APICS took 4.9591064453125e-05s
Availability | VoID file availability check for CLLD-APICS took 0.44654035568237305s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 180.40372157096863s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.01843404769897461s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0005431175231933594s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.891654968261719e-05s
Believability | Calculation of trust value for CLLD-APICS took 1.33514404296875e-05s
INFO | --- Analysis for CLLD-APICS took 423.3246877193451s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 0.00010037422180175781s
Availability | VoID file availability check for CLLD-EWAVE took 0.2155928611755371s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 60.479471921920776s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.019103050231933594s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0005254745483398438s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 5.698204040527344e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-EWAVE took 1.9073486328125e-06s
Believability | Calculation of trust value for CLLD-EWAVE took 1.1682510375976562e-05s
INFO | --- Analysis for CLLD-EWAVE took 363.62399554252625s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 8.58306884765625e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.24256110191345215s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.4309701919555664s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.018718242645263672s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0005331039428710938s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 9.942054748535156e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-GLOTTOLOG took 1.9073486328125e-06s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 1.0967254638671875e-05s
INFO | --- Analysis for CLLD-GLOTTOLOG took 3.8390555381774902s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 8.821487426757812e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.24858617782592773s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.3895690441131592s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.018840312957763672s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0005421638488769531s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 9.131431579589844e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-PHOIBLE took 1.9073486328125e-06s
Believability | Calculation of trust value for CLLD-PHOIBLE took 1.1205673217773438e-05s
INFO | --- Analysis for CLLD-PHOIBLE took 5.318037509918213s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 8.559226989746094e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.22887468338012695s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 60.335349798202515s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.018432140350341797s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 3.504753112792969e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0005509853363037109s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 8.535385131835938e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-SAILS took 1.6689300537109375e-06s
Believability | Calculation of trust value for CLLD-SAILS took 1.1920928955078125e-05s
INFO | --- Analysis for CLLD-SAILS took 63.726420164108276s
Availability | SPARQL endpoint availability check for CLLD-WALS took 8.988380432128906e-05s
Availability | VoID file availability check for CLLD-WALS took 0.24103474617004395s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.43372344970703125s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.018287181854248047s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0005285739898681641s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.106231689453125e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-WALS took 1.430511474609375e-06s
Believability | Calculation of trust value for CLLD-WALS took 1.1444091796875e-05s
INFO | --- Analysis for CLLD-WALS took 4.4945151805877686s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 8.511543273925781e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.25156664848327637s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.3619661331176758s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.018139123916625977s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0005340576171875s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.557868957519531e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-WOLD took 1.6689300537109375e-06s
Believability | Calculation of trust value for CLLD-WOLD took 1.239776611328125e-05s
INFO | --- Analysis for CLLD-WOLD took 63.84793519973755s
Availability | SPARQL endpoint availability check for COD inventory took 0.2616100311279297s
Availability | VoID file availability check for COD inventory took 8.344650268554688e-06s
Completeness | Calculation of interlinking completeness for COD inventory took 0.34369754791259766s
Reputation | Calculation of the PageRank for COD inventory took 0.02134108543395996s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.0005316734313964844s
Interlinking | Calculation of Clustering coefficient for COD inventory took 1.1920928955078125e-05s
Believability | Calculation of trust value for COD inventory took 1.1682510375976562e-05s
INFO | --- Analysis for COD inventory took 2.9756057262420654s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.16873669624328613s
Availability | VoID file availability check for Cooperation Databank took 0.007220029830932617s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.3880746364593506s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.019505739212036133s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0005273818969726562s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.814697265625e-05s
Believability | Calculation of trust value for Cooperation Databank took 1.1920928955078125e-05s
INFO | --- Analysis for Cooperation Databank took 241.73118495941162s
Availability | SPARQL endpoint availability check for CODE Endpoint took 0.00011181831359863281s
Availability | VoID file availability check for CODE Endpoint took 6.198883056640625e-06s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 120.44116187095642s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.018841028213500977s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 1.9311904907226562e-05s
Believability | Calculation of trust value for CODE Endpoint took 1.1682510375976562e-05s
INFO | --- Analysis for CODE Endpoint took 493.6080050468445s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 1.0914502143859863s
Availability | VoID file availability check for OpenUpLabs COINS took 1.0808017253875732s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.5107433795928955s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.01844930648803711s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0005338191986083984s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 1.3828277587890625e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 8.821487426757812e-06s
INFO | --- Analysis for OpenUpLabs COINS took 244.55578684806824s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.06952452659606934s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.015972614288330078s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 60.03524732589722s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.01857447624206543s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0005350112915039062s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 4.649162292480469e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 1.9073486328125e-05s
INFO | --- Analysis for COLINDA - Conference Linked Data took 420.5639052391052s
Availability | SPARQL endpoint availability check for CN  2012 took 25.339922189712524s
Availability | VoID file availability check for CN  2012 took 1.5013129711151123s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.3122236728668213s
Reputation | Calculation of the PageRank for CN  2012 took 0.018453598022460938s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0005385875701904297s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 3.6716461181640625e-05s
Believability | Calculation of trust value for CN  2012 took 9.059906005859375e-06s
INFO | --- Analysis for CN  2012 took 218.300635099411s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 2.7691867351531982s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 8.821487426757812e-06s
Extra | Recovery of all triples for Comments on Literature in Literature (CoLiL) took 154.26477003097534s
Performance | Total latancy measurement for Comments on Literature in Literature (CoLiL) took 8.189255475997925s
Amount of data | Number of triples check for Comments on Literature in Literature (CoLiL) took 301.4492664337158s
Interoperability | New terms check for Comments on Literature in Literature (CoLiL) took 140.89898371696472s
Versatility | Languages check for Comments on Literature in Literature (CoLiL) took 301.4952640533447s
Interpretability | Number of blank nodes check for Comments on Literature in Literature (CoLiL) took 209.68509984016418s
Security | Check HTTPS for Comments on Literature in Literature (CoLiL) took 1.1422297954559326s
Interpretability | RDF structures check for Comments on Literature in Literature (CoLiL) took 1.8601090908050537s
Versatility | Serialization formats check for Comments on Literature in Literature (CoLiL) took 1.6987743377685547s
Availability | RDF dump link check for Comments on Literature in Literature (CoLiL) took 1.710282802581787s
License | MR license check for Comments on Literature in Literature (CoLiL) took 1.8104629516601562s
License | HR license check for Comments on Literature in Literature (CoLiL) took 1.7741193771362305s
Amount of data | Number of property check for Comments on Literature in Literature (CoLiL) took 1.700704574584961s
Understandability | Number of label check for Comments on Literature in Literature (CoLiL) took 2.0774683952331543s
Understandability | URI regex check for Comments on Literature in Literature (CoLiL) took 3.3063039779663086s
Understandability | Vocabs check for Comments on Literature in Literature (CoLiL) took 1.7719459533691406s
Verifiability | Authors check for Comments on Literature in Literature (CoLiL) took 1.9253063201904297s
Verifiability | Publishers check for Comments on Literature in Literature (CoLiL) took 1.709650993347168s
Performance | Throughput check for Comments on Literature in Literature (CoLiL) took 16.477665185928345s
Amount of data | Check the number of entities for Comments on Literature in Literature (CoLiL) took 8.58306884765625e-05s
Verifiability | Contribs. check for Comments on Literature in Literature (CoLiL) took 1.6994328498840332s
Interlinking | sameAs chians check for Comments on Literature in Literature (CoLiL) took 1.7046785354614258s
Interlinking | skos check for Comments on Literature in Literature (CoLiL) took 2.3061702251434326s
Interlinking | skos check for Comments on Literature in Literature (CoLiL) took 1.842226266860962s
Timeliness | dataset update frequency check for Comments on Literature in Literature (CoLiL) took 1.6616835594177246s
Currency | Creation date check for Comments on Literature in Literature (CoLiL) took 1.8809142112731934s
Currency | Modification date check for Comments on Literature in Literature (CoLiL) took 1.6830792427062988s
Rep.Conc. | URIs length for Comments on Literature in Literature (CoLiL) took 479.453325510025s
Interoperability | New vocabularies check for Comments on Literature in Literature (CoLiL) took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Comments on Literature in Literature (CoLiL) took 1.7006733417510986s
Accuracy | Check Empty annotation labels for Comments on Literature in Literature (CoLiL) took 2.7727203369140625s
Accuracy | Check White space in annotation for Comments on Literature in Literature (CoLiL) took 0.0019152164459228516s
Accuracy | Check Datatype consistency for Comments on Literature in Literature (CoLiL) took 2.617602586746216s
Consistency | Disjoint class check for Comments on Literature in Literature (CoLiL) took 1.796043872833252s
Consistency | Check Misplaced properties for Comments on Literature in Literature (CoLiL) took 303.089879989624s
Consistency | Misplaced classes for Comments on Literature in Literature (CoLiL) took 10.754722833633423s
Consistency | Check Ontology hijacking for Comments on Literature in Literature (CoLiL) took 38.41649913787842s
Consistency | Check Invalid usage of undefined classes for Comments on Literature in Literature (CoLiL) took 1.321227788925171s
Consistency | Check Invalid usage of undefined properties for Comments on Literature in Literature (CoLiL) took 303.4538416862488s
Conciseness | Check Extensional conciseness for Comments on Literature in Literature (CoLiL) took 2.738455295562744s
Conciseness | Check Intensional conciseness for Comments on Literature in Literature (CoLiL) took 2.808976888656616s
Security | Sign check for Comments on Literature in Literature (CoLiL) took 2.9524295330047607s
Availability | Check URIs Dereferenciability for Comments on Literature in Literature (CoLiL) took 3.8041839599609375s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 1.38179349899292s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.018177032470703125s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.0005104541778564453s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 1.811981201171875e-05s
Interoperability | Check the re-using of existing vocabs for Comments on Literature in Literature (CoLiL) took 1.430511474609375e-06s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 1.4781951904296875e-05s
INFO | --- Analysis for Comments on Literature in Literature (CoLiL) took 3656.690356731415s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 0.00020647048950195312s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.05427289009094238s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.39049243927001953s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.020133256912231445s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0005259513854980469s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 2.0265579223632812e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 1.1682510375976562e-05s
INFO | --- Analysis for Comparative analysis of production volume by area of strawberry by period took 941.5312383174896s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 8.845329284667969e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.015465259552001953s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 3.1754772663116455s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.02063775062561035s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0005283355712890625s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 1.5020370483398438e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 9.298324584960938e-06s
INFO | --- Analysis for Price competitiveness of pear by region took 319.4758665561676s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 9.441375732421875e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 1.52587890625e-05s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 31.29099202156067s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.020719051361083984s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0005340576171875s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 1.4066696166992188e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 6.9141387939453125e-06s
INFO | --- Analysis for Comparative analysis of production volume by area of watermelon by period took 657.4536633491516s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 8.7738037109375e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.30019402503967285s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.9103548526763916s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.019462108612060547s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0006308555603027344s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 0.00011730194091796875s
Believability | Calculation of trust value for Price competitiveness of grape by region took 1.239776611328125e-05s
INFO | --- Analysis for Price competitiveness of grape by region took 67.09049034118652s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 0.6491274833679199s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.4595043659210205s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 1.5738210678100586s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.018595457077026367s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0005433559417724609s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 0.00011420249938964844s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 1.1920928955078125e-05s
INFO | --- Analysis for Requirements on the COMSODE project based on selected datasets took 8.22648286819458s
Availability | SPARQL endpoint availability check for ConceptNet took 8.273124694824219e-05s
Availability | VoID file availability check for ConceptNet took 1.8907732963562012s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.358905553817749s
Reputation | Calculation of the PageRank for ConceptNet took 0.018024921417236328s
Interlinking | Calculation of Degree of Connection for ConceptNet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ConceptNet took 0.0005362033843994141s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 1.1682510375976562e-05s
Believability | Calculation of trust value for ConceptNet took 1.1444091796875e-05s
INFO | --- Analysis for ConceptNet took 6.903706073760986s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 8.58306884765625e-05s
Availability | VoID file availability check for 2011 US Congress People took 3.2377982139587402s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.45412421226501465s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.018119096755981445s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0005247592926025391s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.106231689453125e-05s
Believability | Calculation of trust value for 2011 US Congress People took 7.62939453125e-06s
INFO | --- Analysis for 2011 US Congress People took 9.565202713012695s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 2.1989169120788574s
Availability | VoID file availability check for LODsyndesis Dataset took 0.0017631053924560547s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.3701355457305908s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0006313323974609375s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 1.33514404296875e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 1.1682510375976562e-05s
INFO | --- Analysis for LODsyndesis Dataset took 35.12689828872681s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 30.338829278945923s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 19.99994683265686s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.9251053333282471s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.018494844436645508s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0005390644073486328s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.3828277587890625e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.2159347534179688e-05s
INFO | --- Analysis for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 215.13689994812012s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 9.226799011230469e-05s
Availability | VoID file availability check for CopyrightTermBank took 8.344650268554688e-06s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 1.135652780532837s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.0187380313873291s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0005402565002441406s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 7.295608520507812e-05s
Believability | Calculation of trust value for CopyrightTermBank took 1.0728836059570312e-05s
INFO | --- Analysis for CopyrightTermBank took 37.06019830703735s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 1.6321055889129639s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.4081406593322754s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.39780735969543457s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.018598318099975586s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0005228519439697266s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.8623809814453125e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 1.0013580322265625e-05s
INFO | --- Analysis for CORE - Semantic Similarity of Open Access publications took 11.451555252075195s
Availability | SPARQL endpoint availability check for Corine linked dataset took 4.00543212890625e-05s
Availability | VoID file availability check for Corine linked dataset took 5.245208740234375e-06s
Completeness | Calculation of interlinking completeness for Corine linked dataset took 1.5459020137786865s
Reputation | Calculation of the PageRank for Corine linked dataset took 0.018456220626831055s
Interlinking | Calculation of Degree of Connection for Corine linked dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Corine linked dataset took 0.0005214214324951172s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset took 1.2874603271484375e-05s
Believability | Calculation of trust value for Corine linked dataset took 6.9141387939453125e-06s
INFO | --- Analysis for Corine linked dataset took 4.986109733581543s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 4.5299530029296875e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.01675128936767578s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.40486669540405273s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.018239498138427734s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0005772113800048828s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.6927719116210938e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.1682510375976562e-05s
INFO | --- Analysis for Corn's Famous mountainous district (Hongcheon) Environmental Status took 91.39040231704712s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 8.630752563476562e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.015858888626098633s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 1.9218885898590088s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.018823862075805664s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0005176067352294922s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 1.430511474609375e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 1.2636184692382812e-05s
INFO | --- Analysis for Corn's Famous mountainous district (Goesan) Environmental Status took 38.59047842025757s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.00010633468627929688s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.015142440795898438s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.5974609851837158s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.018210887908935547s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0005280971527099609s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.9788742065429688e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.0728836059570312e-05s
INFO | --- Analysis for Corn's Famous mountainous district (Jeongseon) Environmental Status took 28.098530292510986s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 0.00012302398681640625s
Availability | VoID file availability check for Cornetto1.2 took 1.0741019248962402s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.28125619888305664s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.01824021339416504s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0005588531494140625s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 6.246566772460938e-05s
Believability | Calculation of trust value for Cornetto1.2 took 1.049041748046875e-05s
INFO | --- Analysis for Cornetto1.2 took 9.727871894836426s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.23374605178833008s
Availability | VoID file availability check for Corporate Body Named Authority List  took 4.90214991569519s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 275.4784986972809s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.6254913806915283s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 28.431169033050537s
Interoperability | New terms check for Corporate Body Named Authority List  took 29.633240938186646s
Versatility | Languages check for Corporate Body Named Authority List  took 300.07155323028564s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 10.601733207702637s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.38158369064331055s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.44333577156066895s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 0.29918789863586426s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.20883512496948242s
License | MR license check for Corporate Body Named Authority List  took 0.22658848762512207s
License | HR license check for Corporate Body Named Authority List  took 6.099865913391113s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.1309349536895752s
Understandability | Number of label check for Corporate Body Named Authority List  took 1.345670223236084s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.27503180503845215s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.10858488082885742s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.31745076179504395s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.16618561744689941s
Performance | Throughput check for Corporate Body Named Authority List  took 10.572608709335327s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 9.775161743164062e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.1517951488494873s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 6.542999505996704s
Interlinking | skos check for Corporate Body Named Authority List  took 0.3170592784881592s
Interlinking | skos check for Corporate Body Named Authority List  took 0.31938672065734863s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.20872998237609863s
Currency | Creation date check for Corporate Body Named Authority List  took 1.1763241291046143s
Currency | Modification date check for Corporate Body Named Authority List  took 0.30964040756225586s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 297.60771775245667s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.20459532737731934s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.19328570365905762s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.15688085556030273s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 65.20913934707642s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.1941802501678467s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.8037917613983154s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.9834079742431641s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 193.06338334083557s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 7.683111667633057s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 55.88770937919617s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.4968030452728271s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 197.1046118736267s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 2.610802412033081s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.4145357608795166s
Security | Sign check for Corporate Body Named Authority List  took 0.15520811080932617s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 3.4218835830688477s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 0.8870489597320557s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.018703937530517578s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0005354881286621094s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 6.508827209472656e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 1.9073486328125e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 6.198883056640625e-06s
INFO | --- Analysis for Corporate Body Named Authority List  took 11454.57007408142s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.0874478816986084s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.01503300666809082s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.34750866889953613s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.017994165420532227s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0005314350128173828s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 1.2636184692382812e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 1.1205673217773438e-05s
INFO | --- Analysis for CORS Check - HTTP Header Logs for Linked Open Data took 1.9578263759613037s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.10661745071411133s
Availability | VoID file availability check for Country Name Authority List took 4.690832853317261s
Extra | Recovery of all triples for Country Name Authority List took 272.7155842781067s
Performance | Total latancy measurement for Country Name Authority List took 0.6309788227081299s
Amount of data | Number of triples check for Country Name Authority List took 26.28262495994568s
Interoperability | New terms check for Country Name Authority List took 29.738872528076172s
Versatility | Languages check for Country Name Authority List took 300.0939996242523s
Interpretability | Number of blank nodes check for Country Name Authority List took 10.394044876098633s
Security | Check HTTPS for Country Name Authority List took 0.33417177200317383s
Interpretability | RDF structures check for Country Name Authority List took 0.24713397026062012s
Versatility | Serialization formats check for Country Name Authority List took 0.13733530044555664s
Availability | RDF dump link check for Country Name Authority List took 0.22855901718139648s
License | MR license check for Country Name Authority List took 0.26012301445007324s
License | HR license check for Country Name Authority List took 6.355449914932251s
Amount of data | Number of property check for Country Name Authority List took 0.13919711112976074s
Understandability | Number of label check for Country Name Authority List took 1.4740700721740723s
Understandability | URI regex check for Country Name Authority List took 0.25340795516967773s
Understandability | Vocabs check for Country Name Authority List took 0.09767436981201172s
Verifiability | Authors check for Country Name Authority List took 0.15793752670288086s
Verifiability | Publishers check for Country Name Authority List took 0.23840999603271484s
Performance | Throughput check for Country Name Authority List took 10.478914499282837s
Amount of data | Check the number of entities for Country Name Authority List took 0.00012493133544921875s
Verifiability | Contribs. check for Country Name Authority List took 0.2159116268157959s
Interlinking | sameAs chians check for Country Name Authority List took 5.883378505706787s
Interlinking | skos check for Country Name Authority List took 0.1703794002532959s
Interlinking | skos check for Country Name Authority List took 0.1393568515777588s
Timeliness | dataset update frequency check for Country Name Authority List took 0.17341399192810059s
Currency | Creation date check for Country Name Authority List took 0.9569523334503174s
Currency | Modification date check for Country Name Authority List took 0.15663576126098633s
Rep.Conc. | URIs length for Country Name Authority List took 305.32046723365784s
Interoperability | New vocabularies check for Country Name Authority List took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.1787245273590088s
Accuracy | Check Functional Property for Country Name Authority List took 0.21434283256530762s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.16079926490783691s
Accuracy | Check Empty annotation labels for Country Name Authority List took 59.332436084747314s
Accuracy | Check White space in annotation for Country Name Authority List took 3.188884973526001s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.7436606884002686s
Consistency | Disjoint class check for Country Name Authority List took 0.1976475715637207s
Consistency | Check Misplaced properties for Country Name Authority List took 200.76049184799194s
Consistency | Misplaced classes for Country Name Authority List took 8.486404657363892s
Consistency | Check Ontology hijacking for Country Name Authority List took 58.45585751533508s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.5820765495300293s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 202.81278371810913s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.0179481506347656s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.39496755599975586s
Security | Sign check for Country Name Authority List took 0.16296648979187012s
Availability | Check URIs Dereferenciability for Country Name Authority List took 3.9310288429260254s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 0.9198617935180664s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.01966714859008789s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 6.389617919921875e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0005505084991455078s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 5.4836273193359375e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 1.9073486328125e-06s
Believability | Calculation of trust value for Country Name Authority List took 7.152557373046875e-06s
INFO | --- Analysis for Country Name Authority List took 10281.63779091835s
Availability | SPARQL endpoint availability check for Courts thesaurus took 30.280385732650757s
Availability | VoID file availability check for Courts thesaurus took 20.00477433204651s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.4416615962982178s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.020894289016723633s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0005466938018798828s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 7.557868957519531e-05s
Believability | Calculation of trust value for Courts thesaurus took 1.239776611328125e-05s
INFO | --- Analysis for Courts thesaurus took 142.41056180000305s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 0.3653533458709717s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.40991735458374023s
Extra | Recovery of all triples for Covid-on-the-Web Dataset took 2.365424156188965s
Performance | Total latancy measurement for Covid-on-the-Web Dataset took 0.6320226192474365s
Amount of data | Number of triples check for Covid-on-the-Web Dataset took 24.509456157684326s
Interoperability | New terms check for Covid-on-the-Web Dataset took 10.19597053527832s
Versatility | Languages check for Covid-on-the-Web Dataset took 300.1151158809662s
Interpretability | Number of blank nodes check for Covid-on-the-Web Dataset took 66.07662773132324s
Interpretability | RDF structures check for Covid-on-the-Web Dataset took 0.45171475410461426s
Versatility | Serialization formats check for Covid-on-the-Web Dataset took 0.36054396629333496s
Availability | RDF dump link check for Covid-on-the-Web Dataset took 5.559601545333862s
License | MR license check for Covid-on-the-Web Dataset took 0.19539546966552734s
License | HR license check for Covid-on-the-Web Dataset took 266.7814223766327s
Amount of data | Number of property check for Covid-on-the-Web Dataset took 0.12689495086669922s
Understandability | Number of label check for Covid-on-the-Web Dataset took 1.4570660591125488s
Understandability | URI regex check for Covid-on-the-Web Dataset took 0.5968732833862305s
Understandability | Vocabs check for Covid-on-the-Web Dataset took 0.1231224536895752s
Verifiability | Authors check for Covid-on-the-Web Dataset took 0.9804117679595947s
Verifiability | Publishers check for Covid-on-the-Web Dataset took 0.15502381324768066s
Performance | Throughput check for Covid-on-the-Web Dataset took 10.612752437591553s
Amount of data | Check the number of entities for Covid-on-the-Web Dataset took 0.11189532279968262s
Verifiability | Contribs. check for Covid-on-the-Web Dataset took 0.15579891204833984s
Interlinking | sameAs chians check for Covid-on-the-Web Dataset took 0.13522076606750488s
Interlinking | skos check for Covid-on-the-Web Dataset took 0.116973876953125s
Interlinking | skos check for Covid-on-the-Web Dataset took 0.15925335884094238s
Timeliness | dataset update frequency check for Covid-on-the-Web Dataset took 0.4113750457763672s
Currency | Creation date check for Covid-on-the-Web Dataset took 0.14303827285766602s
Currency | Modification date check for Covid-on-the-Web Dataset took 0.12291121482849121s
Rep.Conc. | URIs length for Covid-on-the-Web Dataset took 69.1961784362793s
Interoperability | New vocabularies check for Covid-on-the-Web Dataset took 10.970783233642578s
Consistency | Deprecated classes/propertiers check for Covid-on-the-Web Dataset took 0.11415600776672363s
Accuracy | Check Functional Property for Covid-on-the-Web Dataset took 0.28740358352661133s
Accuracy | Check Inverse Functional Property for Covid-on-the-Web Dataset took 0.25626301765441895s
Accuracy | Check Empty annotation labels for Covid-on-the-Web Dataset took 1.4075379371643066s
Accuracy | Check White space in annotation for Covid-on-the-Web Dataset took 0.06653165817260742s
Accuracy | Check Datatype consistency for Covid-on-the-Web Dataset took 0.08129525184631348s
Consistency | Disjoint class check for Covid-on-the-Web Dataset took 0.12126398086547852s
Consistency | Check Misplaced properties for Covid-on-the-Web Dataset took 29.60823941230774s
Consistency | Misplaced classes for Covid-on-the-Web Dataset took 1.2284269332885742s
Consistency | Check Ontology hijacking for Covid-on-the-Web Dataset took 2.18719744682312s
Consistency | Check Invalid usage of undefined classes for Covid-on-the-Web Dataset took 1.2490830421447754s
Consistency | Check Invalid usage of undefined properties for Covid-on-the-Web Dataset took 27.603559732437134s
Conciseness | Check Extensional conciseness for Covid-on-the-Web Dataset took 0.0858767032623291s
Conciseness | Check Intensional conciseness for Covid-on-the-Web Dataset took 1.3807222843170166s
Security | Sign check for Covid-on-the-Web Dataset took 0.2941746711730957s
Availability | Check URIs Dereferenciability for Covid-on-the-Web Dataset took 2104.4580733776093s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 9.952577590942383s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.08023810386657715s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0005240440368652344s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 8.535385131835938e-05s
Interoperability | Check the re-using of existing vocabs for Covid-on-the-Web Dataset took 9.623260974884033s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for Covid-on-the-Web Dataset took 4599.735689640045s
Availability | SPARQL endpoint availability check for CPA 2008 took 25.098825454711914s
Availability | VoID file availability check for CPA 2008 took 1.9083914756774902s
Completeness | Calculation of interlinking completeness for CPA 2008 took 1.001828670501709s
Reputation | Calculation of the PageRank for CPA 2008 took 0.019008159637451172s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0005311965942382812s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 3.910064697265625e-05s
Believability | Calculation of trust value for CPA 2008 took 7.867813110351562e-06s
INFO | --- Analysis for CPA 2008 took 103.82761001586914s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 203.72096920013428s
Availability | VoID file availability check for Cooperative Patent Classification took 0.22716903686523438s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 1.078615665435791s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.01938176155090332s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0005443096160888672s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 4.124641418457031e-05s
Believability | Calculation of trust value for Cooperative Patent Classification took 1.049041748046875e-05s
INFO | --- Analysis for Cooperative Patent Classification took 210.65517258644104s
Availability | SPARQL endpoint availability check for CPC 2008 took 24.26785373687744s
Availability | VoID file availability check for CPC 2008 took 1.9612104892730713s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.8061494827270508s
Reputation | Calculation of the PageRank for CPC 2008 took 0.01860642433166504s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.000545501708984375s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 4.673004150390625e-05s
Believability | Calculation of trust value for CPC 2008 took 9.775161743164062e-06s
INFO | --- Analysis for CPC 2008 took 103.55760526657104s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.935908794403076s
Availability | VoID file availability check for CPV  2003 took 2.3774075508117676s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.4501636028289795s
Reputation | Calculation of the PageRank for CPV  2003 took 0.01848006248474121s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0005311965942382812s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 4.57763671875e-05s
Believability | Calculation of trust value for CPV  2003 took 9.059906005859375e-06s
INFO | --- Analysis for CPV  2003 took 100.74365735054016s
Availability | SPARQL endpoint availability check for CPV 2008 took 23.658595323562622s
Availability | VoID file availability check for CPV 2008 took 1.5565228462219238s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.46092987060546875s
Reputation | Calculation of the PageRank for CPV 2008 took 0.01834392547607422s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0005316734313964844s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 6.127357482910156e-05s
Believability | Calculation of trust value for CPV 2008 took 6.67572021484375e-06s
INFO | --- Analysis for CPV 2008 took 102.56645774841309s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 260.24625158309937s
Availability | VoID file availability check for crowdsourcing-fb took 6.9141387939453125e-06s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 1.1664910316467285s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.018633604049682617s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.000553131103515625s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.076957702636719e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 1.4066696166992188e-05s
INFO | --- Analysis for crowdsourcing-fb took 395.80127358436584s
Availability | SPARQL endpoint availability check for CRTM took 20.398046255111694s
Availability | VoID file availability check for CRTM took 8.106231689453125e-06s
Completeness | Calculation of interlinking completeness for CRTM took 2.4461169242858887s
Reputation | Calculation of the PageRank for CRTM took 0.018326282501220703s
Interlinking | Calculation of Degree of Connection for CRTM took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for CRTM took 0.000530242919921875s
Interlinking | Calculation of Clustering coefficient for CRTM took 1.5020370483398438e-05s
Believability | Calculation of trust value for CRTM took 6.127357482910156e-05s
INFO | --- Analysis for CRTM took 46.7001748085022s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 1.185058832168579s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.20903825759887695s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.31014251708984375s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.02036118507385254s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.000522613525390625s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 1.2159347534179688e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 1.1205673217773438e-05s
INFO | --- Analysis for Crystal Eye: Aggregated Crystallographic Data took 5.640884876251221s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.647063970565796s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.23536109924316406s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 9.173419713973999s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.0181577205657959s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0005471706390380859s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 4.649162292480469e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 4.5299530029296875e-06s
INFO | --- Analysis for CTIC Public Dataset Catalogs took 52.851396322250366s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 8.630752563476562e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.04424881935119629s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 3.699596643447876s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.020308732986450195s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0005261898040771484s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 1.239776611328125e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 1.0728836059570312e-05s
INFO | --- Analysis for Cultivation status of GMO crops took 47.422364234924316s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.23136448860168457s
Availability | VoID file availability check for CulturaLinkedData took 0.28006720542907715s
Extra | Recovery of all triples for CulturaLinkedData took 3.6245803833007812s
Performance | Total latancy measurement for CulturaLinkedData took 0.5615286827087402s
Amount of data | Number of triples check for CulturaLinkedData took 0.36719775199890137s
Interoperability | New terms check for CulturaLinkedData took 1.541067123413086s
Versatility | Languages check for CulturaLinkedData took 0.15944194793701172s
Interpretability | Number of blank nodes check for CulturaLinkedData took 0.25551843643188477s
Interpretability | RDF structures check for CulturaLinkedData took 0.19373750686645508s
Versatility | Serialization formats check for CulturaLinkedData took 0.16765236854553223s
Availability | RDF dump link check for CulturaLinkedData took 0.09142780303955078s
License | MR license check for CulturaLinkedData took 0.09498286247253418s
License | HR license check for CulturaLinkedData took 0.21651363372802734s
Amount of data | Number of property check for CulturaLinkedData took 0.17584919929504395s
Understandability | Number of label check for CulturaLinkedData took 0.7230494022369385s
Understandability | URI regex check for CulturaLinkedData took 1.9365274906158447s
Understandability | Vocabs check for CulturaLinkedData took 1.033715009689331s
Verifiability | Authors check for CulturaLinkedData took 0.10118961334228516s
Verifiability | Publishers check for CulturaLinkedData took 0.10181188583374023s
Performance | Throughput check for CulturaLinkedData took 10.498181104660034s
Amount of data | Check the number of entities for CulturaLinkedData took 9.34600830078125e-05s
Verifiability | Contribs. check for CulturaLinkedData took 0.10761070251464844s
Interlinking | sameAs chians check for CulturaLinkedData took 0.16018319129943848s
Interlinking | skos check for CulturaLinkedData took 0.1704699993133545s
Interlinking | skos check for CulturaLinkedData took 0.09947061538696289s
Timeliness | dataset update frequency check for CulturaLinkedData took 0.10007214546203613s
Currency | Creation date check for CulturaLinkedData took 0.1498548984527588s
Currency | Modification date check for CulturaLinkedData took 0.16068291664123535s
Rep.Conc. | URIs length for CulturaLinkedData took 2.4377949237823486s
Interoperability | New vocabularies check for CulturaLinkedData took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 0.16853666305541992s
Accuracy | Check Functional Property for CulturaLinkedData took 0.16712093353271484s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 0.09208035469055176s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 0.38913941383361816s
Accuracy | Check White space in annotation for CulturaLinkedData took 0.00607609748840332s
Accuracy | Check Datatype consistency for CulturaLinkedData took 0.027869224548339844s
Consistency | Disjoint class check for CulturaLinkedData took 0.0914602279663086s
Consistency | Check Misplaced properties for CulturaLinkedData took 1.388498306274414s
Consistency | Misplaced classes for CulturaLinkedData took 0.360278844833374s
Consistency | Check Ontology hijacking for CulturaLinkedData took 2.4010448455810547s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.2738652229309082s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 2.5343048572540283s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 0.03164362907409668s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 0.4855315685272217s
Security | Sign check for CulturaLinkedData took 0.0815889835357666s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 3.636234998703003s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.30029296875s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.026912450790405273s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0010690689086914062s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 2.47955322265625e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 3.0994415283203125e-06s
Believability | Calculation of trust value for CulturaLinkedData took 1.2874603271484375e-05s
INFO | --- Analysis for CulturaLinkedData took 68.23457980155945s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.16560721397399902s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.08386015892028809s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.36171698570251465s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.018276214599609375s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0005292892456054688s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 4.029273986816406e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 8.58306884765625e-06s
INFO | --- Analysis for Data about business entities from the ARES system - business registry of the Czech Republic took 3.983534574508667s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.11108946800231934s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.07554411888122559s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.37051820755004883s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.01834869384765625s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0005216598510742188s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.647804260253906e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.0251998901367188e-05s
INFO | --- Analysis for Data about Czech business entities from the ARES system - Trade Licensing Register took 2.6687707901000977s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.11359500885009766s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.08734488487243652s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.9491760730743408s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.018383502960205078s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0005216598510742188s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.266334533691406e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 6.67572021484375e-06s
INFO | --- Analysis for Chemicals reported to the Integrated register of pollution took 8.410934686660767s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.10903596878051758s
Availability | VoID file availability check for Integrated pollution registry took 0.06626343727111816s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 1.6835384368896484s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.018505334854125977s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0005223751068115234s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.814697265625e-05s
Believability | Calculation of trust value for Integrated pollution registry took 6.67572021484375e-06s
INFO | --- Analysis for Integrated pollution registry took 11.12403917312622s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.10992312431335449s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.08108973503112793s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.43910932540893555s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.0180666446685791s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0005776882171630859s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.528594970703125e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 7.62939453125e-06s
INFO | --- Analysis for Registry of contracts of the Czech Republic - Contracts took 5.65572452545166s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 0.0748436450958252s
Availability | VoID file availability check for List of courts of the Czech Republic took 5.9604644775390625e-06s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.3141021728515625s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.01829218864440918s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0005252361297607422s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 1.1205673217773438e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 7.3909759521484375e-06s
INFO | --- Analysis for List of courts of the Czech Republic took 2.5278947353363037s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.14271259307861328s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.09295225143432617s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.2921907901763916s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.018126487731933594s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.361701965332031e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 7.62939453125e-06s
INFO | --- Analysis for Bans of the Czech Trade Inspection Authority took 7.048987865447998s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.11489987373352051s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.09192466735839844s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.3743715286254883s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.018428564071655273s
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.0005369186401367188s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.504753112792969e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 9.059906005859375e-06s
INFO | --- Analysis for Confiscations of the Czech Trade Inspection Authority took 3.364245653152466s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.11452436447143555s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.08342647552490234s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 1.9596915245056152s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.01804375648498535s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0005323886871337891s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.266334533691406e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 4.5299530029296875e-06s
INFO | --- Analysis for Focus of the Czech Trade Inspection Authority's inspections took 4.264310121536255s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.12546181678771973s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.08278083801269531s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.3463869094848633s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.01849985122680664s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0005266666412353516s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.458427429199219e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 1.0013580322265625e-05s
INFO | --- Analysis for Inspections of the Czech Trade Inspection Authority took 5.012688398361206s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.11488509178161621s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.08195352554321289s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.41610074043273926s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.01820540428161621s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0005309581756591797s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.4332275390625e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 5.245208740234375e-06s
INFO | --- Analysis for Sanctions of the Czech Trade Inspection Authority took 9.641742944717407s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.24180841445922852s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.08233880996704102s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.4547426700592041s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.01836872100830078s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0005228519439697266s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 4.076957702636719e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 5.0067901611328125e-06s
INFO | --- Analysis for Cadastre offices from Czech land registry took 3.308246612548828s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.11231231689453125s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.08096599578857422s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.39397573471069336s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.018084049224853516s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0005099773406982422s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.3855438232421875e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 9.298324584960938e-06s
INFO | --- Analysis for Code lists of the legal relationships and documents took 7.750126838684082s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.5929811000823975s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.4354119300842285s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.32390928268432617s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.018407583236694336s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0005767345428466797s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 4.172325134277344e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 1.0013580322265625e-05s
INFO | --- Analysis for Average salaries in regions of Czech republic took 8.6702561378479s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.3106040954589844s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.4192771911621094s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.4193892478942871s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.01831841468811035s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0005195140838623047s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 4.100799560546875e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 5.0067901611328125e-06s
INFO | --- Analysis for Deaths by selected causes of death in regions of Czech Republic took 4.284631252288818s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.3564732074737549s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.47788262367248535s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.42172670364379883s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.018356800079345703s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0005218982696533203s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.981590270996094e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.049041748046875e-05s
INFO | --- Analysis for Number of inhabitants in districts of Czech Republic in 5year age categories took 8.063798666000366s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.3258016109466553s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.4886012077331543s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.32555365562438965s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.01851963996887207s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0005125999450683594s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 4.076957702636719e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 8.58306884765625e-06s
INFO | --- Analysis for Job applicants in regions of Czech Republic took 6.075359106063843s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.2721443176269531s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.47420525550842285s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.7704169750213623s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.018457889556884766s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0005247592926025391s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 4.00543212890625e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 9.298324584960938e-06s
INFO | --- Analysis for Job applicants and unemployment rate in regions of Czech Republic took 5.156983375549316s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.30936264991760254s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.490924596786499s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.4387016296386719s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.018272876739501953s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0005626678466796875s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.719329833984375e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 1.0967254638671875e-05s
INFO | --- Analysis for Structure of regions of Czech Republic according to Czech Statistical Office took 5.699035406112671s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.30154943466186523s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.5001273155212402s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 1.0765316486358643s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.018915653228759766s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0005249977111816406s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 4.1961669921875e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 9.775161743164062e-06s
INFO | --- Analysis for Selected public health indicators in regions of Czech republic took 6.841451406478882s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.2866518497467041s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.45731377601623535s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.4138338565826416s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.018318891525268555s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0005304813385009766s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 4.1484832763671875e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 1.049041748046875e-05s
INFO | --- Analysis for Social service facilities and nursing in districts of Czech republic took 7.48506498336792s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.30946803092956543s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.47750043869018555s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.4150257110595703s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.01846146583557129s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0005288124084472656s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 4.9591064453125e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 8.58306884765625e-06s
INFO | --- Analysis for Unemployment rate in regions of Czech republic took 4.862370014190674s
Availability | SPARQL endpoint availability check for ATC groups took 0.11913251876831055s
Availability | VoID file availability check for ATC groups took 0.08041524887084961s
Completeness | Calculation of interlinking completeness for ATC groups took 1.5997216701507568s
Reputation | Calculation of the PageRank for ATC groups took 0.02018284797668457s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0005154609680175781s
Interlinking | Calculation of Clustering coefficient for ATC groups took 7.152557373046875e-05s
Believability | Calculation of trust value for ATC groups took 1.2636184692382812e-05s
INFO | --- Analysis for ATC groups took 10.875477313995361s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.1379096508026123s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.10251712799072266s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.45716047286987305s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.018660306930541992s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005588531494140625s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 4.100799560546875e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 9.5367431640625e-06s
INFO | --- Analysis for Registry of contracts of the Czech Republic - Financial fulfillments took 2.942070722579956s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.07624506950378418s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0010936260223388672s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.3687114715576172s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.01968669891357422s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0005276203155517578s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 5.173683166503906e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 9.059906005859375e-06s
INFO | --- Analysis for Czech Business Entity identification numbers and names took 4.213949203491211s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.1253061294555664s
Availability | VoID file availability check for List of Czech data boxes took 0.13826394081115723s
Extra | Recovery of all triples for List of Czech data boxes took 138.0165820121765s
Performance | Total latancy measurement for List of Czech data boxes took 0.6910068988800049s
Amount of data | Number of triples check for List of Czech data boxes took 58.272679805755615s
Interoperability | New terms check for List of Czech data boxes took 10.584772825241089s
Versatility | Languages check for List of Czech data boxes took 300.1777217388153s
Interpretability | Number of blank nodes check for List of Czech data boxes took 1.4524211883544922s
Interpretability | RDF structures check for List of Czech data boxes took 0.2991957664489746s
Versatility | Serialization formats check for List of Czech data boxes took 0.14750409126281738s
Availability | RDF dump link check for List of Czech data boxes took 17.002631425857544s
License | MR license check for List of Czech data boxes took 0.8053226470947266s
License | HR license check for List of Czech data boxes took 54.18446469306946s
Amount of data | Number of property check for List of Czech data boxes took 0.13625049591064453s
Understandability | Number of label check for List of Czech data boxes took 1.4294252395629883s
Understandability | URI regex check for List of Czech data boxes took 0.4235715866088867s
Understandability | Vocabs check for List of Czech data boxes took 0.23693537712097168s
Verifiability | Authors check for List of Czech data boxes took 5.596220970153809s
Verifiability | Publishers check for List of Czech data boxes took 0.7867472171783447s
Performance | Throughput check for List of Czech data boxes took 10.489536046981812s
Amount of data | Check the number of entities for List of Czech data boxes took 2.9415946006774902s
Verifiability | Contribs. check for List of Czech data boxes took 0.2715883255004883s
Interlinking | sameAs chians check for List of Czech data boxes took 0.28248047828674316s
Interlinking | skos check for List of Czech data boxes took 0.21949076652526855s
Interlinking | skos check for List of Czech data boxes took 0.12335467338562012s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.23799562454223633s
Currency | Creation date check for List of Czech data boxes took 0.6061646938323975s
Currency | Modification date check for List of Czech data boxes took 0.23758673667907715s
Rep.Conc. | URIs length for List of Czech data boxes took 107.17857027053833s
Interoperability | New vocabularies check for List of Czech data boxes took 9.63829755783081s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.4092826843261719s
Accuracy | Check Functional Property for List of Czech data boxes took 0.16849780082702637s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.19663500785827637s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 29.638131618499756s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.1162376403808594s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.603060722351074s
Consistency | Disjoint class check for List of Czech data boxes took 0.21689939498901367s
Consistency | Check Misplaced properties for List of Czech data boxes took 65.36385774612427s
Consistency | Misplaced classes for List of Czech data boxes took 7.591042518615723s
Consistency | Check Ontology hijacking for List of Czech data boxes took 30.71796226501465s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.3466932773590088s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 59.86562180519104s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.6140449047088623s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.4449303150177002s
Security | Sign check for List of Czech data boxes took 0.17122173309326172s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 407.9883186817169s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.6142737865447998s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.018918752670288086s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 5.817413330078125e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0005276203155517578s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 2.09808349609375e-05s
Interoperability | Check the re-using of existing vocabs for List of Czech data boxes took 8.416404962539673s
Believability | Calculation of trust value for List of Czech data boxes took 9.059906005859375e-06s
INFO | --- Analysis for List of Czech data boxes took 2146.7518780231476s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10783171653747559s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.14704084396362305s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 137.5345652103424s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6867902278900146s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.19992995262146s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.380606412887573s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.10194158554077s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.3290598392486572s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1333305835723877s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1397254467010498s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 15.922584295272827s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3910346031188965s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 51.3212194442749s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13224077224731445s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.4718518257141113s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.44272923469543457s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13428449630737305s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.246339321136475s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.705817461013794s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 11.108233213424683s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.145465850830078s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.15455222129821777s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3087034225463867s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.17764496803283691s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.14519286155700684s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.14271020889282227s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1802229881286621s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1349787712097168s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 107.45879602432251s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.780916690826416s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4427459239959717s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1720900535583496s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.15497994422912598s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 29.87765622138977s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.107147216796875s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.6224071979522705s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.16054391860961914s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 66.09027791023254s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.746656179428101s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 30.407898426055908s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.426440954208374s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 60.04266953468323s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.6981301307678223s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4087636470794678s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12684869766235352s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 401.85204100608826s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.8684635162353516s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.018611669540405273s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0005309581756591797s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.6689300537109375e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.837245225906372s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.775161743164062e-06s
INFO | --- Analysis for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2073.499643087387s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.38434529304504395s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0017156600952148438s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 401.50565791130066s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.9118726253509521s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.6812210083007812s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.1269187927246094s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 300.137494802475s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.529022455215454s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5598256587982178s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2546103000640869s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2617466449737549s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3475639820098877s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5422205924987793s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1819295883178711s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.581118106842041s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.35346221923828125s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2196793556213379s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3014845848083496s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2250359058380127s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.2 took 10.89317011833191s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.2 took 5.53131103515625e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16060948371887207s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.149092435836792s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.26822781562805176s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15218830108642578s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2224442958831787s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.6135604381561279s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3030970096588135s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.2 took 100.18796992301941s
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.14973711967468262s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3204782009124756s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.36922764778137207s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.2 took 79.16234993934631s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.617359161376953s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.673552989959717s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2185525894165039s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 7.956033945083618s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.108282566070557s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.2 took 80.98899984359741s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.7866008281707764s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 9.256540775299072s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.225923538208008s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2951486110687256s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.5300829410552979s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.2 took 1336.8869383335114s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.143479824066162s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.01986527442932129s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.6941299438476562e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0005505084991455078s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.6941299438476562e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.5762786865234375e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.2159347534179688e-05s
INFO | --- Analysis for Czech National Open Data Catalog in DCAT-AP v1.2 took 13943.891711235046s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.17248272895812988s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.07874679565429688s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.284224271774292s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.018207073211669922s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0005247592926025391s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.743171691894531e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 9.059906005859375e-06s
INFO | --- Analysis for Registry of contracts of the Czech Republic - Orders took 2.4900217056274414s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.1773529052734375s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.1091165542602539s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 143.73519587516785s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.58970046043396s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 9.285967350006104s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 10.46657133102417s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.1586022377014s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 1.3333570957183838s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.16963410377502441s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.11260390281677246s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 16.312678813934326s
License | MR license check for Institutions of public power of the Czech Republic took 0.4012932777404785s
License | HR license check for Institutions of public power of the Czech Republic took 52.10256481170654s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.15603208541870117s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 1.2780954837799072s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.4278707504272461s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.10854029655456543s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 4.961588621139526s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.7498342990875244s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.486016511917114s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.0391156673431396s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.1264047622680664s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.2801814079284668s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.1930551528930664s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.11950874328613281s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.21059203147888184s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.1847374439239502s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.13649392127990723s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 108.54606747627258s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 9.433991432189941s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.4268345832824707s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.17824912071228027s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.19604921340942383s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 30.239681005477905s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.0690903663635254s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.6762754917144775s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.12405133247375488s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 66.4249358177185s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 7.79562520980835s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 32.43414831161499s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.3465197086334229s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 60.54172348976135s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.6617817878723145s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.4122631549835205s
Security | Sign check for Institutions of public power of the Czech Republic took 0.18680953979492188s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 401.01817631721497s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.9487810134887695s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.01870131492614746s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.000530242919921875s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 5.316734313964844e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 7.908294677734375s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 1.1205673217773438e-05s
INFO | --- Analysis for Institutions of public power of the Czech Republic took 2076.426061630249s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.13019967079162598s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.08883881568908691s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 4.011224985122681s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.020401716232299805s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0005366802215576172s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.5762786865234375e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 8.58306884765625e-06s
INFO | --- Analysis for Agendas of institutions of public power of the Czech Republic took 16.468806982040405s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13757681846618652s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0023682117462158203s
Extra | Recovery of all triples for Registry of territorial identification, addresses and real estate of the Czech Republic took 42.90511965751648s
Performance | Total latancy measurement for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.6376993656158447s
Amount of data | Number of triples check for Registry of territorial identification, addresses and real estate of the Czech Republic took 18.648847103118896s
Interoperability | New terms check for Registry of territorial identification, addresses and real estate of the Czech Republic took 17.51441788673401s
Versatility | Languages check for Registry of territorial identification, addresses and real estate of the Czech Republic took 300.130975484848s
Interpretability | Number of blank nodes check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.3529188632965088s
Interpretability | RDF structures check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.4292280673980713s
Versatility | Serialization formats check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12561750411987305s
Availability | RDF dump link check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.8885362148284912s
License | MR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1646411418914795s
License | HR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11068367958068848s
Amount of data | Number of property check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.15004467964172363s
Understandability | Number of label check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.7184712886810303s
Understandability | URI regex check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.29437994956970215s
Understandability | Vocabs check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13112902641296387s
Verifiability | Authors check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.19518303871154785s
Verifiability | Publishers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.20459508895874023s
Performance | Throughput check for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.98405933380127s
Amount of data | Check the number of entities for Registry of territorial identification, addresses and real estate of the Czech Republic took 9.036064147949219e-05s
Verifiability | Contribs. check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13297748565673828s
Interlinking | sameAs chians check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0985407829284668s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.14877629280090332s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13750648498535156s
Timeliness | dataset update frequency check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13306140899658203s
Currency | Creation date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11176562309265137s
Currency | Modification date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.14937210083007812s
Rep.Conc. | URIs length for Registry of territorial identification, addresses and real estate of the Czech Republic took 118.21401882171631s
Interoperability | New vocabularies check for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12166881561279297s
Accuracy | Check Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.15527701377868652s
Accuracy | Check Inverse Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1418459415435791s
Accuracy | Check Empty annotation labels for Registry of territorial identification, addresses and real estate of the Czech Republic took 11.447195768356323s
Accuracy | Check White space in annotation for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.242410898208618s
Accuracy | Check Datatype consistency for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.7563884258270264s
Consistency | Disjoint class check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1417844295501709s
Consistency | Check Misplaced properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 86.28642845153809s
Consistency | Misplaced classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.991121292114258s
Consistency | Check Ontology hijacking for Registry of territorial identification, addresses and real estate of the Czech Republic took 14.740684986114502s
Consistency | Check Invalid usage of undefined classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.4320602416992188s
Consistency | Check Invalid usage of undefined properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 87.06106805801392s
Conciseness | Check Extensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 3.0657460689544678s
Conciseness | Check Intensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.3003232479095459s
Security | Sign check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10643148422241211s
Availability | Check URIs Dereferenciability for Registry of territorial identification, addresses and real estate of the Czech Republic took 1305.2146441936493s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.5382986068725586s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.020164012908935547s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.532669067382812e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0005216598510742188s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.00012421607971191406s
Interoperability | Check the re-using of existing vocabs for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.1457672119140625e-06s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.0967254638671875e-05s
INFO | --- Analysis for Registry of territorial identification, addresses and real estate of the Czech Republic took 2162.1137521266937s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.8013219833374023s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.9919390678405762s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.32703399658203125s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.018750667572021484s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0005311965942382812s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.176399230957031e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 8.344650268554688e-06s
INFO | --- Analysis for Audited subjects of Supreme Audit Office of the Czech Republic took 5.167526721954346s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.5828142166137695s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.9998390674591064s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.3487534523010254s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.018954992294311523s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0005507469177246094s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.910064697265625e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 5.9604644775390625e-06s
INFO | --- Analysis for Inspections of the Supreme Audit Office of the Czech Republic took 4.149998426437378s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.4962034225463867s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.8514628410339355s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.8934206962585449s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.02011728286743164s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0005335807800292969s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.457069396972656e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 1.0728836059570312e-05s
INFO | --- Analysis for List of laws used in inspection reports of SAO took 4.574582576751709s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.12247157096862793s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.08811020851135254s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.4398791790008545s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.018039941787719727s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0005397796630859375s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.337860107421875e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 1.1920928955078125e-05s
INFO | --- Analysis for Active ingredients of medicinal products available in Czech Republic took 3.256338357925415s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.15146660804748535s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0851287841796875s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.324908971786499s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.018147945404052734s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0005486011505126953s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.2901763916015625e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 8.821487426757812e-06s
INFO | --- Analysis for List of prices of reimbursed medicinal products marketed in Czech republic took 2.465505361557007s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.11390995979309082s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.07088637351989746s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.9645006656646729s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.018935680389404297s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0005528926849365234s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 4.2438507080078125e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 1.0728836059570312e-05s
INFO | --- Analysis for Medicinal products marketed in Czech Republic took 7.122866153717041s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.21005988121032715s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0024237632751464844s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 136.82503819465637s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.6379132270812988s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 9.660839796066284s
Interoperability | New terms check for Summary types of Czech institutions of public power took 10.642613649368286s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.1694905757904s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 1.3616225719451904s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.13547539710998535s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.10779571533203125s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 16.061214923858643s
License | MR license check for Summary types of Czech institutions of public power took 0.2489316463470459s
License | HR license check for Summary types of Czech institutions of public power took 51.11752390861511s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.13172554969787598s
Understandability | Number of label check for Summary types of Czech institutions of public power took 1.4133687019348145s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.3241593837738037s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.10486412048339844s
Verifiability | Authors check for Summary types of Czech institutions of public power took 5.015178918838501s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.7329204082489014s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.534871101379395s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.017975091934204s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.13675165176391602s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.2939317226409912s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.21219277381896973s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.12795448303222656s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.25669384002685547s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.20716309547424316s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.14148497581481934s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 107.37438368797302s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 9.072587013244629s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.40572357177734375s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.19446825981140137s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.173858642578125s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 30.262704133987427s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.0879335403442383s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.589998483657837s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.1311936378479004s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 65.60523056983948s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 7.5877697467803955s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 32.62977480888367s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.3507914543151855s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 59.91103744506836s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.650207281112671s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.49529242515563965s
Security | Sign check for Summary types of Czech institutions of public power took 0.18477678298950195s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 400.20568227767944s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.9142353534698486s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.01922011375427246s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 2.9087066650390625e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0005252361297607422s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 4.76837158203125e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 9.769649982452393s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 1.6927719116210938e-05s
INFO | --- Analysis for Summary types of Czech institutions of public power took 2070.676053762436s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.11349773406982422s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.07041239738464355s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.45533013343811035s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.01843428611755371s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0005333423614501953s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.62396240234375e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 9.298324584960938e-06s
INFO | --- Analysis for Evaluation of VaVaI results for 2013 took 17.904604196548462s
Availability | SPARQL endpoint availability check for State funding providers took 0.13651752471923828s
Availability | VoID file availability check for State funding providers took 0.08311629295349121s
Completeness | Calculation of interlinking completeness for State funding providers took 0.30603861808776855s
Reputation | Calculation of the PageRank for State funding providers took 0.018179893493652344s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0005314350128173828s
Interlinking | Calculation of Clustering coefficient for State funding providers took 4.029273986816406e-05s
Believability | Calculation of trust value for State funding providers took 9.059906005859375e-06s
INFO | --- Analysis for State funding providers took 8.429903745651245s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.11356925964355469s
Availability | VoID file availability check for Organizations active in R&D took 0.08843207359313965s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 4.470366477966309s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.018334627151489258s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0005269050598144531s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 5.316734313964844e-05s
Believability | Calculation of trust value for Organizations active in R&D took 1.1682510375976562e-05s
INFO | --- Analysis for Organizations active in R&D took 32.63531994819641s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.11307072639465332s
Availability | VoID file availability check for R&D Programmes took 0.06536626815795898s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.3488473892211914s
Reputation | Calculation of the PageRank for R&D Programmes took 0.01819610595703125s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0006692409515380859s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.7206878662109375e-05s
Believability | Calculation of trust value for R&D Programmes took 1.0013580322265625e-05s
INFO | --- Analysis for R&D Programmes took 14.064229488372803s
Availability | SPARQL endpoint availability check for R&D Projects took 0.12236857414245605s
Availability | VoID file availability check for R&D Projects took 0.08442282676696777s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.45829081535339355s
Reputation | Calculation of the PageRank for R&D Projects took 0.018321752548217773s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0005853176116943359s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.792213439941406e-05s
Believability | Calculation of trust value for R&D Projects took 8.821487426757812e-06s
INFO | --- Analysis for R&D Projects took 145.91960787773132s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.15473008155822754s
Availability | VoID file availability check for Institutional research plans took 0.07877993583679199s
Completeness | Calculation of interlinking completeness for Institutional research plans took 1.3810877799987793s
Reputation | Calculation of the PageRank for Institutional research plans took 0.01844167709350586s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0005562305450439453s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.410743713378906e-05s
Believability | Calculation of trust value for Institutional research plans took 9.5367431640625e-06s
INFO | --- Analysis for Institutional research plans took 4.265065908432007s
Availability | SPARQL endpoint availability check for Results of R&D took 0.10529851913452148s
Availability | VoID file availability check for Results of R&D took 0.08760905265808105s
Completeness | Calculation of interlinking completeness for Results of R&D took 60.155343770980835s
Reputation | Calculation of the PageRank for Results of R&D took 0.01829695701599121s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0005278587341308594s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.267692565917969e-05s
Believability | Calculation of trust value for Results of R&D took 8.821487426757812e-06s
INFO | --- Analysis for Results of R&D took 62.38372874259949s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.13234996795654297s
Availability | VoID file availability check for Tenders in R&D took 0.07883810997009277s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.9845333099365234s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.018256425857543945s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.3392181396484375e-05s
Believability | Calculation of trust value for Tenders in R&D took 8.344650268554688e-06s
INFO | --- Analysis for Tenders in R&D took 63.56199288368225s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 8.988380432128906e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.45055508613586426s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.412158727645874s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.018219709396362305s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0005221366882324219s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.24249267578125e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 1.1682510375976562e-05s
INFO | --- Analysis for Czech addresses – Adresy v České republice took 3.956951141357422s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.31190919876098633s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.2154827117919922s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 1.9793391227722168s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.019048213958740234s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0005304813385009766s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00013709068298339844s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 1.1682510375976562e-05s
INFO | --- Analysis for data.bnf.fr - Bibliothèque nationale de France took 68.00061416625977s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.433351993560791s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.3365178108215332s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 61.765915870666504s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.01828789710998535s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0005216598510742188s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 7.557868957519531e-05s
Interoperability | Check the re-using of existing vocabs for Open Data from the Italian National Research Council took 1.4848690032958984s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 8.58306884765625e-06s
INFO | --- Analysis for Open Data from the Italian National Research Council took 198.85600686073303s
Availability | SPARQL endpoint availability check for Data.gov took 1.8208136558532715s
Availability | VoID file availability check for Data.gov took 1.016326665878296s
Completeness | Calculation of interlinking completeness for Data.gov took 29.124337673187256s
Reputation | Calculation of the PageRank for Data.gov took 0.018207311630249023s
Interlinking | Calculation of Degree of Connection for Data.gov took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0005304813385009766s
Interlinking | Calculation of Clustering coefficient for Data.gov took 1.71661376953125e-05s
Believability | Calculation of trust value for Data.gov took 1.2874603271484375e-05s
INFO | --- Analysis for Data.gov took 293.69398260116577s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.04090571403503418s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.014427423477172852s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 113.38643264770508s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.01860332489013672s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0005314350128173828s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 7.414817810058594e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 9.298324584960938e-06s
INFO | --- Analysis for DataGovIE - Irish Government Data took 723.2343170642853s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 8.96453857421875e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 1.349149227142334s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.36957287788391113s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.019663095474243164s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0005650520324707031s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 8.177757263183594e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 4.1484832763671875e-05s
INFO | --- Analysis for data.gov.uk Time Intervals took 116.71090602874756s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 19.122855186462402s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.9044139385223389s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.7127370834350586s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.019436120986938477s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0005314350128173828s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.937980651855469e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 1.1920928955078125e-05s
INFO | --- Analysis for data-hnm-hu - Hungarian National Museum Datasets took 180.26601481437683s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.2842097282409668s
Availability | VoID file availability check for Climb Dataincubator took 0.015741825103759766s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.46741771697998047s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.01835465431213379s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0005478858947753906s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 8.58306884765625e-05s
Believability | Calculation of trust value for Climb Dataincubator took 7.3909759521484375e-06s
INFO | --- Analysis for Climb Dataincubator took 2.6143970489501953s
Availability | SPARQL endpoint availability check for Discogs in RDF took 8.749961853027344e-05s
Availability | VoID file availability check for Discogs in RDF took 0.6451356410980225s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.9833784103393555s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.0204470157623291s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0005533695220947266s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.274482727050781e-05s
Believability | Calculation of trust value for Discogs in RDF took 1.0728836059570312e-05s
INFO | --- Analysis for Discogs in RDF took 5.769242286682129s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.06696033477783203s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.017368793487548828s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.29799652099609375s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.018530845642089844s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0005197525024414062s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.364418029785156e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 8.106231689453125e-06s
INFO | --- Analysis for Metoffice Weather Forecasts took 5.070460796356201s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.0706019401550293s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.017543315887451172s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.31240105628967285s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.018428802490234375s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0005333423614501953s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.726119995117188e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 1.1682510375976562e-05s
INFO | --- Analysis for Moseley Folk Festival Data took 4.744024038314819s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.0709829330444336s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.01501607894897461s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.3241431713104248s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.019211530685424805s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0005245208740234375s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 8.487701416015625e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 7.62939453125e-06s
INFO | --- Analysis for Data Incubator: MusicBrainz took 1.9134838581085205s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 2.1634461879730225s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 1.6222517490386963s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.8726458549499512s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.01856398582458496s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0005846023559570312s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.845329284667969e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 8.821487426757812e-06s
INFO | --- Analysis for NASA Space Flight & Astronaut data in RDF took 12.73336148262024s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.07666420936584473s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.016175031661987305s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.8848061561584473s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.01804661750793457s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0005185604095458984s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.104873657226562e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 1.1920928955078125e-05s
INFO | --- Analysis for Airport data from Our Airports published as RDF took 4.036713123321533s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.06798219680786133s
Availability | VoID file availability check for Pokedex data in RDF took 0.018236160278320312s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.46155452728271484s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.018027067184448242s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0005280971527099609s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.107589721679688e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 1.239776611328125e-05s
INFO | --- Analysis for Pokedex data in RDF took 5.7543394565582275s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.06252741813659668s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.016428470611572266s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.6421303749084473s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0005419254302978516s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 8.606910705566406e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 1.1682510375976562e-05s
INFO | --- Analysis for Scottish Mountaineering Council Journals Issues 1-36 took 3.4574239253997803s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.28290629386901855s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.561638593673706s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 17.42186665534973s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 0.6356375217437744s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 15.828142881393433s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.5599579811096191s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.174718618392944s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.148862838745117s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.1710526943206787s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.18709540367126465s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.3281252384185791s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.14799094200134277s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.1753840446472168s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.13879656791687s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.5539946556091309s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 30.158862113952637s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 0.3647596836090088s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.22864270210266113s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 7.610267400741577s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.7353901863098145s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 11.309610843658447s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 8.654594421386719e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 1.4506902694702148s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.7212159633636475s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.21231412887573242s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.2970447540283203s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.15651512145996094s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 2.8534700870513916s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 3.152374029159546s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 38.27972865104675s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 58.89159345626831s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.19216656684875488s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.21893620491027832s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.13865876197814941s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 32.72761154174805s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 2.9946346282958984s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.065229177474976s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.6446983814239502s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 1.0550501346588135s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 7.9715354442596436s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 25.492987394332886s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.4054036140441895s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.5928819179534912s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 2.844486713409424s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.3788590431213379s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.13321423530578613s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 0.1086118221282959s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.4768636226654053s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.018099308013916016s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0005013942718505859s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 6.890296936035156e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 55.47577452659607s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 1.239776611328125e-05s
INFO | --- Analysis for data.open.ac.uk, Linked Data from the Open University took 648.8943729400635s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.8577075004577637s
Availability | VoID file availability check for Persée in RDF took 1.5175561904907227s
Extra | Recovery of all triples for Persée in RDF took 1.1965010166168213s
Performance | Total latancy measurement for Persée in RDF took 0.7557268142700195s
Amount of data | Number of triples check for Persée in RDF took 0.41947054862976074s
Interoperability | New terms check for Persée in RDF took 1.8571343421936035s
Versatility | Languages check for Persée in RDF took 106.1832206249237s
Interpretability | Number of blank nodes check for Persée in RDF took 0.3501002788543701s
Interpretability | RDF structures check for Persée in RDF took 1.0997161865234375s
Versatility | Serialization formats check for Persée in RDF took 1.5300757884979248s
Availability | RDF dump link check for Persée in RDF took 0.27484822273254395s
License | MR license check for Persée in RDF took 3.224628210067749s
License | HR license check for Persée in RDF took 26.74938988685608s
Amount of data | Number of property check for Persée in RDF took 0.1643962860107422s
Understandability | Number of label check for Persée in RDF took 3.2302136421203613s
Understandability | URI regex check for Persée in RDF took 1.4370713233947754s
Understandability | Vocabs check for Persée in RDF took 0.8313808441162109s
Verifiability | Authors check for Persée in RDF took 1.01519775390625s
Verifiability | Publishers check for Persée in RDF took 0.7446086406707764s
Performance | Throughput check for Persée in RDF took 10.817789793014526s
Amount of data | Check the number of entities for Persée in RDF took 9.441375732421875e-05s
Verifiability | Contribs. check for Persée in RDF took 0.5092506408691406s
Interlinking | sameAs chians check for Persée in RDF took 0.12314367294311523s
Interlinking | skos check for Persée in RDF took 1.8330645561218262s
Interlinking | skos check for Persée in RDF took 0.1557140350341797s
Timeliness | dataset update frequency check for Persée in RDF took 1.3890089988708496s
Currency | Creation date check for Persée in RDF took 0.7910311222076416s
Currency | Modification date check for Persée in RDF took 0.529130220413208s
Rep.Conc. | URIs length for Persée in RDF took 2.7343032360076904s
Interoperability | New vocabularies check for Persée in RDF took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.14697003364562988s
Accuracy | Check Functional Property for Persée in RDF took 0.19896245002746582s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.22861099243164062s
Accuracy | Check Empty annotation labels for Persée in RDF took 0.7074973583221436s
Accuracy | Check White space in annotation for Persée in RDF took 0.0376739501953125s
Accuracy | Check Datatype consistency for Persée in RDF took 0.027415990829467773s
Consistency | Disjoint class check for Persée in RDF took 0.7321751117706299s
Consistency | Check Misplaced properties for Persée in RDF took 2.0760059356689453s
Consistency | Misplaced classes for Persée in RDF took 0.24456238746643066s
Consistency | Check Ontology hijacking for Persée in RDF took 1.8883028030395508s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.2866308689117432s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.201780319213867s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.03143882751464844s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.13406944274902344s
Security | Sign check for Persée in RDF took 0.6479651927947998s
Availability | Check URIs Dereferenciability for Persée in RDF took 1380.0209546089172s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.6200277805328369s
Reputation | Calculation of the PageRank for Persée in RDF took 0.01894402503967285s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0005269050598144531s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00020956993103027344s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 1.1920928955078125e-06s
Believability | Calculation of trust value for Persée in RDF took 1.430511474609375e-05s
INFO | --- Analysis for Persée in RDF took 1652.785876750946s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 1.5889892578125s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 6.198883056640625e-06s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.33326244354248047s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.01856231689453125s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.000530242919921875s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 1.3828277587890625e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 1.1444091796875e-05s
INFO | --- Analysis for data.southampton.ac.uk with SPARQL endpoint took 3.7268283367156982s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.3165278434753418s
Availability | VoID file availability check for data-szepmuveszeti-hu took 1.0518436431884766s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.44846582412719727s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.01804971694946289s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0005323886871337891s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011205673217773438s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 1.1682510375976562e-05s
INFO | --- Analysis for data-szepmuveszeti-hu took 14.571971654891968s
Availability | SPARQL endpoint availability check for Open Data Web took 27.232725143432617s
Availability | VoID file availability check for Open Data Web took 10.472575902938843s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.33672523498535156s
Reputation | Calculation of the PageRank for Open Data Web took 0.019875764846801758s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0005247592926025391s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 1.5974044799804688e-05s
Believability | Calculation of trust value for Open Data Web took 1.1920928955078125e-05s
INFO | --- Analysis for Open Data Web took 41.693824768066406s
Availability | SPARQL endpoint availability check for DataFAQs took 8.0108642578125e-05s
Availability | VoID file availability check for DataFAQs took 5.245208740234375e-06s
Completeness | Calculation of interlinking completeness for DataFAQs took 1.0750343799591064s
Reputation | Calculation of the PageRank for DataFAQs took 0.01820540428161621s
Interlinking | Calculation of Degree of Connection for DataFAQs took 1.52587890625e-05s
Interlinking | Calculation of Centrality for DataFAQs took 0.0005998611450195312s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 1.2159347534179688e-05s
Believability | Calculation of trust value for DataFAQs took 1.1920928955078125e-05s
INFO | --- Analysis for DataFAQs took 4.408402919769287s
Availability | SPARQL endpoint availability check for datahub took 0.00010251998901367188s
Availability | VoID file availability check for datahub took 0.9371328353881836s
Completeness | Calculation of interlinking completeness for datahub took 0.3512589931488037s
Reputation | Calculation of the PageRank for datahub took 0.018311738967895508s
Interlinking | Calculation of Degree of Connection for datahub took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for datahub took 0.0005326271057128906s
Interlinking | Calculation of Clustering coefficient for datahub took 4.982948303222656e-05s
Believability | Calculation of trust value for datahub took 1.33514404296875e-05s
INFO | --- Analysis for datahub took 5.128268718719482s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.32768893241882324s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0967254638671875e-05s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.32410597801208496s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.020192623138427734s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0005125999450683594s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 6.794929504394531e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.1682510375976562e-05s
INFO | --- Analysis for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 4.975828170776367s
Availability | SPARQL endpoint availability check for datos-artium-org took 1.8474597930908203s
Availability | VoID file availability check for datos-artium-org took 1.0556988716125488s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.28255176544189453s
Reputation | Calculation of the PageRank for datos-artium-org took 0.018294334411621094s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0005915164947509766s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00011706352233886719s
Believability | Calculation of trust value for datos-artium-org took 1.0967254638671875e-05s
INFO | --- Analysis for datos-artium-org took 8.218077659606934s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.9021296501159668s
Availability | VoID file availability check for Datos.bcn.cl took 12.503806352615356s
Extra | Recovery of all triples for Datos.bcn.cl took 1065.5689554214478s
Performance | Total latancy measurement for Datos.bcn.cl took 6.720479965209961s
Amount of data | Number of triples check for Datos.bcn.cl took 9.331985235214233s
Interoperability | New terms check for Datos.bcn.cl took 5.671045541763306s
Versatility | Languages check for Datos.bcn.cl took 301.1941452026367s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.4969847202301025s
Security | Check HTTPS for Datos.bcn.cl took 0.7673254013061523s
Interpretability | RDF structures check for Datos.bcn.cl took 1.391775131225586s
Versatility | Serialization formats check for Datos.bcn.cl took 1.4792685508728027s
Availability | RDF dump link check for Datos.bcn.cl took 1.2207677364349365s
License | MR license check for Datos.bcn.cl took 1.4400708675384521s
License | HR license check for Datos.bcn.cl took 185.1745307445526s
Amount of data | Number of property check for Datos.bcn.cl took 1.4082932472229004s
Understandability | Number of label check for Datos.bcn.cl took 300.02213978767395s
Understandability | URI regex check for Datos.bcn.cl took 3.412187099456787s
Understandability | Vocabs check for Datos.bcn.cl took 1.3593807220458984s
Verifiability | Authors check for Datos.bcn.cl took 1.4982264041900635s
Verifiability | Publishers check for Datos.bcn.cl took 1.2915356159210205s
Performance | Throughput check for Datos.bcn.cl took 13.40444540977478s
Amount of data | Check the number of entities for Datos.bcn.cl took 3.886222839355469e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.2793376445770264s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.4217777252197266s
Interlinking | skos check for Datos.bcn.cl took 1.285106897354126s
Interlinking | skos check for Datos.bcn.cl took 1.2631778717041016s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.3986942768096924s
Currency | Creation date check for Datos.bcn.cl took 1.4185686111450195s
Currency | Modification date check for Datos.bcn.cl took 1.3112866878509521s
Rep.Conc. | URIs length for Datos.bcn.cl took 29.980988025665283s
Interoperability | New vocabularies check for Datos.bcn.cl took 6.67572021484375e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.3996503353118896s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.470562219619751s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.231351375579834s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 25.517091274261475s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.3225414752960205s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.26725125312805176s
Consistency | Disjoint class check for Datos.bcn.cl took 1.4188868999481201s
Consistency | Check Misplaced properties for Datos.bcn.cl took 8.156730651855469s
Consistency | Misplaced classes for Datos.bcn.cl took 2.135807752609253s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 19.11098623275757s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.2783846855163574s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 6.982351779937744s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.29299449920654297s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.5255730152130127s
Security | Sign check for Datos.bcn.cl took 1.385636568069458s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 9025.344628334045s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 0.9152266979217529s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.019217729568481445s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 0.0001289844512939453s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0005543231964111328s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 8.249282836914062e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 4.5299530029296875e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 6.9141387939453125e-06s
INFO | --- Analysis for Datos.bcn.cl took 11414.367868900299s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.4713008403778076s
Availability | VoID file availability check for datos.bne.es took 1.673187017440796s
Extra | Recovery of all triples for datos.bne.es took 145.24672842025757s
Performance | Total latancy measurement for datos.bne.es took 1.492614984512329s
Amount of data | Number of triples check for datos.bne.es took 1.2599515914916992s
Interoperability | New terms check for datos.bne.es took 2.469148635864258s
Versatility | Languages check for datos.bne.es took 60.46318030357361s
Interpretability | Number of blank nodes check for datos.bne.es took 0.3257465362548828s
Security | Check HTTPS for datos.bne.es took 0.16712307929992676s
Interpretability | RDF structures check for datos.bne.es took 0.3934164047241211s
Versatility | Serialization formats check for datos.bne.es took 0.3600337505340576s
Availability | RDF dump link check for datos.bne.es took 0.35690879821777344s
License | MR license check for datos.bne.es took 0.8626999855041504s
License | HR license check for datos.bne.es took 60.36593437194824s
Amount of data | Number of property check for datos.bne.es took 0.3449432849884033s
Understandability | Number of label check for datos.bne.es took 2.4257755279541016s
Understandability | URI regex check for datos.bne.es took 0.8073570728302002s
Understandability | Vocabs check for datos.bne.es took 0.3818237781524658s
Verifiability | Authors check for datos.bne.es took 0.7964761257171631s
Verifiability | Publishers check for datos.bne.es took 0.3712437152862549s
Performance | Throughput check for datos.bne.es took 11.692307949066162s
Amount of data | Check the number of entities for datos.bne.es took 8.821487426757812e-05s
Verifiability | Contribs. check for datos.bne.es took 0.36159324645996094s
Interlinking | sameAs chians check for datos.bne.es took 0.2957186698913574s
Interlinking | skos check for datos.bne.es took 0.8198635578155518s
Interlinking | skos check for datos.bne.es took 0.2881591320037842s
Timeliness | dataset update frequency check for datos.bne.es took 0.39685750007629395s
Currency | Creation date check for datos.bne.es took 0.3747832775115967s
Currency | Modification date check for datos.bne.es took 0.3196079730987549s
Rep.Conc. | URIs length for datos.bne.es took 69.87834620475769s
Interoperability | New vocabularies check for datos.bne.es took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for datos.bne.es took 0.31136298179626465s
Accuracy | Check Functional Property for datos.bne.es took 0.330242395401001s
Accuracy | Check Inverse Functional Property for datos.bne.es took 0.3800990581512451s
Accuracy | Check Empty annotation labels for datos.bne.es took 47.811484813690186s
Accuracy | Check White space in annotation for datos.bne.es took 1.6305897235870361s
Accuracy | Check Datatype consistency for datos.bne.es took 1.341127634048462s
Consistency | Disjoint class check for datos.bne.es took 0.3378868103027344s
Consistency | Check Misplaced properties for datos.bne.es took 9.341733455657959s
Consistency | Misplaced classes for datos.bne.es took 4.467920303344727s
Consistency | Check Ontology hijacking for datos.bne.es took 38.606943130493164s
Consistency | Check Invalid usage of undefined classes for datos.bne.es took 1.2636260986328125s
Consistency | Check Invalid usage of undefined properties for datos.bne.es took 10.843799114227295s
Conciseness | Check Extensional conciseness for datos.bne.es took 1.3902852535247803s
Conciseness | Check Intensional conciseness for datos.bne.es took 0.3507101535797119s
Security | Sign check for datos.bne.es took 1.0090899467468262s
Availability | Check URIs Dereferenciability for datos.bne.es took 3.428972005844116s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.3410377502441406s
Reputation | Calculation of the PageRank for datos.bne.es took 0.019081592559814453s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00014281272888183594s
Interoperability | Check the re-using of existing vocabs for datos.bne.es took 2.1457672119140625e-06s
Believability | Calculation of trust value for datos.bne.es took 1.1205673217773438e-05s
INFO | --- Analysis for datos.bne.es took 585.9697802066803s
Availability | SPARQL endpoint availability check for dbacademic took 0.07573795318603516s
Availability | VoID file availability check for dbacademic took 0.017618417739868164s
Completeness | Calculation of interlinking completeness for dbacademic took 0.3382878303527832s
Reputation | Calculation of the PageRank for dbacademic took 0.018131732940673828s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0005273818969726562s
Interlinking | Calculation of Clustering coefficient for dbacademic took 1.2159347534179688e-05s
Believability | Calculation of trust value for dbacademic took 1.1920928955078125e-05s
INFO | --- Analysis for dbacademic took 2.5662295818328857s
Availability | SPARQL endpoint availability check for DBkWik took 0.24414896965026855s
Availability | VoID file availability check for DBkWik took 0.19549107551574707s
Extra | Recovery of all triples for DBkWik took 1.824862003326416s
Performance | Total latancy measurement for DBkWik took 0.4663429260253906s
Amount of data | Number of triples check for DBkWik took 3.6700565814971924s
Interoperability | New terms check for DBkWik took 2.0198919773101807s
Versatility | Languages check for DBkWik took 60.620925188064575s
Interpretability | Number of blank nodes check for DBkWik took 0.13474678993225098s
Security | Check HTTPS for DBkWik took 0.37002992630004883s
Interpretability | RDF structures check for DBkWik took 0.1593773365020752s
Versatility | Serialization formats check for DBkWik took 0.2013094425201416s
Availability | RDF dump link check for DBkWik took 3.0407748222351074s
License | MR license check for DBkWik took 0.26804041862487793s
License | HR license check for DBkWik took 61.37213587760925s
Amount of data | Number of property check for DBkWik took 0.13541173934936523s
Understandability | Number of label check for DBkWik took 1.8214833736419678s
Understandability | URI regex check for DBkWik took 0.2605860233306885s
Understandability | Vocabs check for DBkWik took 0.11008429527282715s
Verifiability | Authors check for DBkWik took 0.12331986427307129s
Verifiability | Publishers check for DBkWik took 0.10989618301391602s
Performance | Throughput check for DBkWik took 10.633752346038818s
Amount of data | Check the number of entities for DBkWik took 0.00013875961303710938s
Verifiability | Contribs. check for DBkWik took 0.11477112770080566s
Interlinking | sameAs chians check for DBkWik took 0.16083955764770508s
Interlinking | skos check for DBkWik took 0.42700767517089844s
Interlinking | skos check for DBkWik took 0.07643651962280273s
Timeliness | dataset update frequency check for DBkWik took 0.21290063858032227s
Currency | Creation date check for DBkWik took 0.3284940719604492s
Currency | Modification date check for DBkWik took 0.10891127586364746s
Rep.Conc. | URIs length for DBkWik took 11.434133291244507s
Interoperability | New vocabularies check for DBkWik took 2.2743446826934814s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.13093805313110352s
Accuracy | Check Functional Property for DBkWik took 0.28420138359069824s
Accuracy | Check Inverse Functional Property for DBkWik took 0.242753267288208s
Accuracy | Check Empty annotation labels for DBkWik took 0.6402797698974609s
Accuracy | Check White space in annotation for DBkWik took 0.02373480796813965s
Accuracy | Check Datatype consistency for DBkWik took 0.03721761703491211s
Consistency | Disjoint class check for DBkWik took 0.10499739646911621s
Consistency | Check Misplaced properties for DBkWik took 12.043772459030151s
Consistency | Misplaced classes for DBkWik took 0.6163754463195801s
Consistency | Check Ontology hijacking for DBkWik took 1.7506117820739746s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.1883549690246582s
Consistency | Check Invalid usage of undefined properties for DBkWik took 11.632038831710815s
Conciseness | Check Extensional conciseness for DBkWik took 0.03284597396850586s
Conciseness | Check Intensional conciseness for DBkWik took 0.6703708171844482s
Security | Sign check for DBkWik took 0.23605942726135254s
Availability | Check URIs Dereferenciability for DBkWik took 3.7687830924987793s
Completeness | Calculation of interlinking completeness for DBkWik took 0.48102307319641113s
Reputation | Calculation of the PageRank for DBkWik took 0.05987739562988281s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0005135536193847656s
Interlinking | Calculation of Clustering coefficient for DBkWik took 0.00010061264038085938s
Interoperability | Check the re-using of existing vocabs for DBkWik took 2.446904182434082s
Believability | Calculation of trust value for DBkWik took 1.2159347534179688e-05s
INFO | --- Analysis for DBkWik took 1287.761271238327s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 8.726119995117188e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.18245911598205566s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.4095737934112549s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.01928257942199707s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0006206035614013672s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.000118255615234375s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 8.106231689453125e-06s
INFO | --- Analysis for DBLP Research Groups (University of Deusto-GNOSS) took 6.45206880569458s
Availability | SPARQL endpoint availability check for dbnary took 0.3104972839355469s
Availability | VoID file availability check for dbnary took 1.5411901473999023s
Extra | Recovery of all triples for dbnary took 1.1304783821105957s
Performance | Total latancy measurement for dbnary took 0.5209858417510986s
Amount of data | Number of triples check for dbnary took 1.145221471786499s
Interoperability | New terms check for dbnary took 3.3097941875457764s
Versatility | Languages check for dbnary took 62.14193677902222s
Interpretability | Number of blank nodes check for dbnary took 4.0874717235565186s
Security | Check HTTPS for dbnary took 0.23513269424438477s
Interpretability | RDF structures check for dbnary took 0.12064385414123535s
Versatility | Serialization formats check for dbnary took 0.11625790596008301s
Availability | RDF dump link check for dbnary took 0.0786588191986084s
License | MR license check for dbnary took 0.11248612403869629s
License | HR license check for dbnary took 56.33212757110596s
Amount of data | Number of property check for dbnary took 0.11291003227233887s
Understandability | Number of label check for dbnary took 0.46117520332336426s
Understandability | URI regex check for dbnary took 0.1381218433380127s
Understandability | Vocabs check for dbnary took 0.13315320014953613s
Verifiability | Authors check for dbnary took 0.08762216567993164s
Verifiability | Publishers check for dbnary took 0.09381675720214844s
Performance | Throughput check for dbnary took 10.508369445800781s
Amount of data | Check the number of entities for dbnary took 4.6253204345703125e-05s
Verifiability | Contribs. check for dbnary took 0.09880399703979492s
Interlinking | sameAs chians check for dbnary took 0.10793352127075195s
Interlinking | skos check for dbnary took 0.1831982135772705s
Interlinking | skos check for dbnary took 0.07863616943359375s
Timeliness | dataset update frequency check for dbnary took 0.21964144706726074s
Currency | Creation date check for dbnary took 0.1176767349243164s
Currency | Modification date check for dbnary took 0.1255660057067871s
Rep.Conc. | URIs length for dbnary took 10.269278287887573s
Interoperability | New vocabularies check for dbnary took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for dbnary took 0.10749650001525879s
Accuracy | Check Functional Property for dbnary took 0.11649513244628906s
Accuracy | Check Inverse Functional Property for dbnary took 0.11368823051452637s
Accuracy | Check Empty annotation labels for dbnary took 0.611595869064331s
Accuracy | Check White space in annotation for dbnary took 0.03023552894592285s
Accuracy | Check Datatype consistency for dbnary took 0.028375625610351562s
Consistency | Disjoint class check for dbnary took 0.12377285957336426s
Consistency | Check Misplaced properties for dbnary took 8.026066064834595s
Consistency | Misplaced classes for dbnary took 0.24689078330993652s
Consistency | Check Ontology hijacking for dbnary took 1.6193995475769043s
Consistency | Check Invalid usage of undefined classes for dbnary took 1.186638593673706s
Consistency | Check Invalid usage of undefined properties for dbnary took 8.913942813873291s
Conciseness | Check Extensional conciseness for dbnary took 0.034594058990478516s
Conciseness | Check Intensional conciseness for dbnary took 0.20615410804748535s
Security | Sign check for dbnary took 0.09226250648498535s
Availability | Check URIs Dereferenciability for dbnary took 1156.1020829677582s
Completeness | Calculation of interlinking completeness for dbnary took 0.523390531539917s
Reputation | Calculation of the PageRank for dbnary took 0.019237041473388672s
Interlinking | Calculation of Degree of Connection for dbnary took 6.747245788574219e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0005209445953369141s
Interlinking | Calculation of Clustering coefficient for dbnary took 0.00011038780212402344s
Interoperability | Check the re-using of existing vocabs for dbnary took 1.430511474609375e-06s
Believability | Calculation of trust value for dbnary took 1.3113021850585938e-05s
INFO | --- Analysis for dbnary took 1381.3881902694702s
Availability | SPARQL endpoint availability check for DBpedia took 0.45504093170166016s
Availability | VoID file availability check for DBpedia took 1.1467597484588623s
Extra | Recovery of all triples for DBpedia took 4.095126628875732s
Performance | Total latancy measurement for DBpedia took 1.4541616439819336s
Amount of data | Number of triples check for DBpedia took 1.5903525352478027s
Interoperability | New terms check for DBpedia took 3.945021390914917s
Versatility | Languages check for DBpedia took 31.190162181854248s
Interpretability | Number of blank nodes check for DBpedia took 0.29588913917541504s
Security | Check HTTPS for DBpedia took 0.23184800148010254s
Interpretability | RDF structures check for DBpedia took 1.1003999710083008s
Versatility | Serialization formats check for DBpedia took 0.2917044162750244s
Availability | RDF dump link check for DBpedia took 0.35402870178222656s
License | MR license check for DBpedia took 1.8995623588562012s
License | HR license check for DBpedia took 11.25540280342102s
Amount of data | Number of property check for DBpedia took 0.2995295524597168s
Understandability | Number of label check for DBpedia took 5.131056308746338s
Understandability | URI regex check for DBpedia took 0.5368130207061768s
Understandability | Vocabs check for DBpedia took 0.3868372440338135s
Verifiability | Authors check for DBpedia took 0.5960204601287842s
Verifiability | Publishers check for DBpedia took 1.7259511947631836s
Performance | Throughput check for DBpedia took 11.76518988609314s
Amount of data | Check the number of entities for DBpedia took 8.440017700195312e-05s
Verifiability | Contribs. check for DBpedia took 0.3161795139312744s
Interlinking | sameAs chians check for DBpedia took 0.501328706741333s
Interlinking | skos check for DBpedia took 0.8095889091491699s
Interlinking | skos check for DBpedia took 0.27933430671691895s
Timeliness | dataset update frequency check for DBpedia took 0.4852621555328369s
Currency | Creation date check for DBpedia took 0.6016898155212402s
Currency | Modification date check for DBpedia took 0.36663269996643066s
Rep.Conc. | URIs length for DBpedia took 33.58264923095703s
Interoperability | New vocabularies check for DBpedia took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.29722142219543457s
Accuracy | Check Functional Property for DBpedia took 0.30525851249694824s
Accuracy | Check Inverse Functional Property for DBpedia took 0.3189713954925537s
Accuracy | Check Empty annotation labels for DBpedia took 1.1189055442810059s
Accuracy | Check White space in annotation for DBpedia took 0.029850244522094727s
Accuracy | Check Datatype consistency for DBpedia took 0.028866052627563477s
Consistency | Disjoint class check for DBpedia took 0.38401341438293457s
Consistency | Check Misplaced properties for DBpedia took 27.745896577835083s
Consistency | Misplaced classes for DBpedia took 1.9630086421966553s
Consistency | Check Ontology hijacking for DBpedia took 2.098844051361084s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.1943089962005615s
Consistency | Check Invalid usage of undefined properties for DBpedia took 1.9592103958129883s
Conciseness | Check Extensional conciseness for DBpedia took 0.03488039970397949s
Conciseness | Check Intensional conciseness for DBpedia took 0.9772360324859619s
Security | Sign check for DBpedia took 0.3492848873138428s
Availability | Check URIs Dereferenciability for DBpedia took 2358.678686141968s
Completeness | Calculation of interlinking completeness for DBpedia took 0.9736678600311279s
Reputation | Calculation of the PageRank for DBpedia took 0.06594705581665039s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0005657672882080078s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0008628368377685547s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia took 8.821487426757812e-06s
INFO | --- Analysis for DBpedia took 3542.44330906868s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 4.172325134277344e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 1.33514404296875e-05s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.6795094013214111s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.019901752471923828s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0005290508270263672s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 6.508827209472656e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 1.239776611328125e-05s
INFO | --- Analysis for DBpedia abstract corpus took 7.246774911880493s
Availability | SPARQL endpoint availability check for DBpedia Commons took 6.2289879322052s
Availability | VoID file availability check for DBpedia Commons took 8.821487426757812e-06s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.4946744441986084s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.02058243751525879s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0005280971527099609s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 6.747245788574219e-05s
Believability | Calculation of trust value for DBpedia Commons took 1.1205673217773438e-05s
INFO | --- Analysis for DBpedia Commons took 12.775256633758545s
Availability | SPARQL endpoint availability check for DBpedia in German took 309.8705916404724s
Availability | VoID file availability check for DBpedia in German took 0.27279114723205566s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.37793564796447754s
Reputation | Calculation of the PageRank for DBpedia in German took 0.01864933967590332s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0005311965942382812s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 7.367134094238281e-05s
Believability | Calculation of trust value for DBpedia in German took 1.0251998901367188e-05s
INFO | --- Analysis for DBpedia in German took 519.0672307014465s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 192.3946888446808s
Availability | VoID file availability check for DBpedia in Greek took 0.18960237503051758s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.716693639755249s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.018735408782958984s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0005645751953125s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.0002129077911376953s
Believability | Calculation of trust value for DBpedia in Greek took 5.0067901611328125e-06s
INFO | --- Analysis for DBpedia in Greek took 713.8791265487671s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.47786521911621094s
Availability | VoID file availability check for DBpedia in Spanish took 0.5200140476226807s
Extra | Recovery of all triples for DBpedia in Spanish took 3.082338809967041s
Performance | Total latancy measurement for DBpedia in Spanish took 1.2377548217773438s
Amount of data | Number of triples check for DBpedia in Spanish took 0.9359338283538818s
Interoperability | New terms check for DBpedia in Spanish took 2.6047523021698s
Versatility | Languages check for DBpedia in Spanish took 62.261693716049194s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.36624598503112793s
Security | Check HTTPS for DBpedia in Spanish took 0.12615132331848145s
Interpretability | RDF structures check for DBpedia in Spanish took 1.336627721786499s
Versatility | Serialization formats check for DBpedia in Spanish took 0.505695104598999s
Availability | RDF dump link check for DBpedia in Spanish took 0.4021775722503662s
License | MR license check for DBpedia in Spanish took 1.058908462524414s
License | HR license check for DBpedia in Spanish took 62.33612060546875s
Amount of data | Number of property check for DBpedia in Spanish took 0.3032844066619873s
Understandability | Number of label check for DBpedia in Spanish took 1.4072353839874268s
Understandability | URI regex check for DBpedia in Spanish took 0.8195815086364746s
Understandability | Vocabs check for DBpedia in Spanish took 0.35880446434020996s
Verifiability | Authors check for DBpedia in Spanish took 0.29642510414123535s
Verifiability | Publishers check for DBpedia in Spanish took 0.32122015953063965s
Performance | Throughput check for DBpedia in Spanish took 12.197875738143921s
Amount of data | Check the number of entities for DBpedia in Spanish took 3.9577484130859375e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 0.28613948822021484s
Interlinking | sameAs chians check for DBpedia in Spanish took 0.5123262405395508s
Interlinking | skos check for DBpedia in Spanish took 0.6635880470275879s
Interlinking | skos check for DBpedia in Spanish took 0.2547163963317871s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.677884578704834s
Currency | Creation date check for DBpedia in Spanish took 0.2985658645629883s
Currency | Modification date check for DBpedia in Spanish took 0.3257017135620117s
Rep.Conc. | URIs length for DBpedia in Spanish took 7.446614980697632s
Interoperability | New vocabularies check for DBpedia in Spanish took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 0.3233306407928467s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.5138921737670898s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.5359656810760498s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 1.239912509918213s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.0320587158203125s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.028093576431274414s
Consistency | Disjoint class check for DBpedia in Spanish took 0.30611228942871094s
Consistency | Check Misplaced properties for DBpedia in Spanish took 8.152346849441528s
Consistency | Misplaced classes for DBpedia in Spanish took 1.145899772644043s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 2.9216575622558594s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.1818389892578125s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 6.692734956741333s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.03358626365661621s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 1.7591767311096191s
Security | Sign check for DBpedia in Spanish took 0.36448001861572266s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 3.708697557449341s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.6107723712921143s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.0207979679107666s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0005214214324951172s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00010514259338378906s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 1.9073486328125e-06s
Believability | Calculation of trust value for DBpedia in Spanish took 8.821487426757812e-06s
INFO | --- Analysis for DBpedia in Spanish took 736.182124376297s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.3874590396881104s
Availability | VoID file availability check for DBpedia in Basque took 0.6171000003814697s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.41947388648986816s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.01832437515258789s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0005581378936767578s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 1.2159347534179688e-05s
Believability | Calculation of trust value for DBpedia in Basque took 8.344650268554688e-06s
INFO | --- Analysis for DBpedia in Basque took 6.682253122329712s
Availability | SPARQL endpoint availability check for DBpedia in French took 0.18521380424499512s
Availability | VoID file availability check for DBpedia in French took 0.195448637008667s
Extra | Recovery of all triples for DBpedia in French took 84.1993727684021s
Performance | Total latancy measurement for DBpedia in French took 0.4843740463256836s
Amount of data | Number of triples check for DBpedia in French took 1.8054158687591553s
Interoperability | New terms check for DBpedia in French took 2.048511266708374s
Versatility | Languages check for DBpedia in French took 300.0897960662842s
Interpretability | Number of blank nodes check for DBpedia in French took 0.21651768684387207s
Security | Check HTTPS for DBpedia in French took 0.2207503318786621s
Interpretability | RDF structures check for DBpedia in French took 0.42205214500427246s
Versatility | Serialization formats check for DBpedia in French took 0.25843191146850586s
Availability | RDF dump link check for DBpedia in French took 7.68679404258728s
License | MR license check for DBpedia in French took 0.497053861618042s
License | HR license check for DBpedia in French took 63.259272813797s
Amount of data | Number of property check for DBpedia in French took 0.15411758422851562s
Understandability | Number of label check for DBpedia in French took 1.0354981422424316s
Understandability | URI regex check for DBpedia in French took 0.2423546314239502s
Understandability | Vocabs check for DBpedia in French took 0.13660049438476562s
Verifiability | Authors check for DBpedia in French took 0.16293859481811523s
Verifiability | Publishers check for DBpedia in French took 0.3467264175415039s
Performance | Throughput check for DBpedia in French took 10.413276672363281s
Amount of data | Check the number of entities for DBpedia in French took 2.093088150024414s
Verifiability | Contribs. check for DBpedia in French took 0.1201171875s
Interlinking | sameAs chians check for DBpedia in French took 0.44292140007019043s
Interlinking | skos check for DBpedia in French took 0.3623790740966797s
Interlinking | skos check for DBpedia in French took 0.08166122436523438s
Timeliness | dataset update frequency check for DBpedia in French took 0.4469571113586426s
Currency | Creation date check for DBpedia in French took 0.11197161674499512s
Currency | Modification date check for DBpedia in French took 0.11883735656738281s
Rep.Conc. | URIs length for DBpedia in French took 37.63678812980652s
Interoperability | New vocabularies check for DBpedia in French took 9.182463884353638s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 0.10919904708862305s
Accuracy | Check Functional Property for DBpedia in French took 0.11707162857055664s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.10580563545227051s
Accuracy | Check Empty annotation labels for DBpedia in French took 24.65407633781433s
Accuracy | Check White space in annotation for DBpedia in French took 3.108642101287842s
Accuracy | Check Datatype consistency for DBpedia in French took 2.6364827156066895s
Consistency | Disjoint class check for DBpedia in French took 0.12963485717773438s
Consistency | Check Misplaced properties for DBpedia in French took 7.068143129348755s
Consistency | Misplaced classes for DBpedia in French took 9.35145616531372s
Consistency | Check Ontology hijacking for DBpedia in French took 23.76994824409485s
Consistency | Check Invalid usage of undefined classes for DBpedia in French took 1.3395071029663086s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 8.137436866760254s
Conciseness | Check Extensional conciseness for DBpedia in French took 3.039159059524536s
Conciseness | Check Intensional conciseness for DBpedia in French took 1.25455641746521s
Security | Sign check for DBpedia in French took 0.13484525680541992s
Availability | Check URIs Dereferenciability for DBpedia in French took 2902.7778866291046s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.7620289325714111s
Reputation | Calculation of the PageRank for DBpedia in French took 0.022651195526123047s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 6.103515625e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0006349086761474609s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.00015926361083984375s
Interoperability | Check the re-using of existing vocabs for DBpedia in French took 7.038658142089844s
Believability | Calculation of trust value for DBpedia in French took 1.0967254638671875e-05s
INFO | --- Analysis for DBpedia in French took 3649.4913263320923s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 2.498566150665283s
Availability | VoID file availability check for DBpedia in Japanese took 3.1755197048187256s
Extra | Recovery of all triples for DBpedia in Japanese took 6.184375762939453s
Performance | Total latancy measurement for DBpedia in Japanese took 8.066277027130127s
Amount of data | Number of triples check for DBpedia in Japanese took 29.094181537628174s
Interoperability | New terms check for DBpedia in Japanese took 17.879255533218384s
Versatility | Languages check for DBpedia in Japanese took 1.5991806983947754s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.618818998336792s
Security | Check HTTPS for DBpedia in Japanese took 1.045454502105713s
Interpretability | RDF structures check for DBpedia in Japanese took 1.6468076705932617s
Versatility | Serialization formats check for DBpedia in Japanese took 1.6095175743103027s
Availability | RDF dump link check for DBpedia in Japanese took 1.6321427822113037s
License | MR license check for DBpedia in Japanese took 1.9565715789794922s
License | HR license check for DBpedia in Japanese took 121.61670541763306s
Amount of data | Number of property check for DBpedia in Japanese took 1.6277875900268555s
Understandability | Number of label check for DBpedia in Japanese took 7.187656879425049s
Understandability | URI regex check for DBpedia in Japanese took 3.205172300338745s
Understandability | Vocabs check for DBpedia in Japanese took 1.7236969470977783s
Verifiability | Authors check for DBpedia in Japanese took 1.6270251274108887s
Verifiability | Publishers check for DBpedia in Japanese took 3.493607521057129s
Performance | Throughput check for DBpedia in Japanese took 16.165971994400024s
Amount of data | Check the number of entities for DBpedia in Japanese took 8.344650268554688e-05s
Verifiability | Contribs. check for DBpedia in Japanese took 1.756194829940796s
Interlinking | sameAs chians check for DBpedia in Japanese took 2.7840075492858887s
Interlinking | skos check for DBpedia in Japanese took 1.7067580223083496s
Interlinking | skos check for DBpedia in Japanese took 1.6691944599151611s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.932502031326294s
Currency | Creation date check for DBpedia in Japanese took 1.640951156616211s
Currency | Modification date check for DBpedia in Japanese took 1.6180355548858643s
Rep.Conc. | URIs length for DBpedia in Japanese took 139.2082347869873s
Interoperability | New vocabularies check for DBpedia in Japanese took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.6394424438476562s
Accuracy | Check Functional Property for DBpedia in Japanese took 1.6474173069000244s
Accuracy | Check Inverse Functional Property for DBpedia in Japanese took 1.6317830085754395s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 4.419316053390503s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.02624678611755371s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.028240680694580078s
Consistency | Disjoint class check for DBpedia in Japanese took 1.7909095287322998s
Consistency | Check Misplaced properties for DBpedia in Japanese took 123.2243664264679s
Consistency | Misplaced classes for DBpedia in Japanese took 3.456775426864624s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 4.694801330566406s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.2764129638671875s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 122.91813373565674s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.03311729431152344s
Conciseness | Check Intensional conciseness for DBpedia in Japanese took 3.5395376682281494s
Security | Sign check for DBpedia in Japanese took 1.6596028804779053s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 3.367821455001831s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.3927583694458008s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.019852876663208008s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0005242824554443359s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00012040138244628906s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 1.9073486328125e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 1.0013580322265625e-05s
INFO | --- Analysis for DBpedia in Japanese took 1133.5138952732086s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.8160552978515625e-05s
Availability | VoID file availability check for dbpedia lite took 5.525212287902832s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.4919273853302002s
Reputation | Calculation of the PageRank for dbpedia lite took 0.030781984329223633s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0010960102081298828s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.000156402587890625s
Believability | Calculation of trust value for dbpedia lite took 8.821487426757812e-06s
INFO | --- Analysis for dbpedia lite took 15.009311199188232s
Availability | SPARQL endpoint availability check for DBpedia-Live took 1.1301300525665283s
Availability | VoID file availability check for DBpedia-Live took 0.5011036396026611s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.31350135803222656s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.019347190856933594s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 1.52587890625e-05s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0005161762237548828s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 1.2159347534179688e-05s
Believability | Calculation of trust value for DBpedia-Live took 1.1920928955078125e-05s
INFO | --- Analysis for DBpedia-Live took 5.920010566711426s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.2832374572753906s
Availability | VoID file availability check for DBpedia in Dutch took 0.14522290229797363s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.37876057624816895s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.018028736114501953s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0005266666412353516s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00016498565673828125s
Believability | Calculation of trust value for DBpedia in Dutch took 9.5367431640625e-06s
INFO | --- Analysis for DBpedia in Dutch took 2.888228178024292s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 1.1545398235321045s
Availability | VoID file availability check for DBpedia in Portuguese took 0.684105396270752s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.5108776092529297s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.019304990768432617s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0005333423614501953s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.821487426757812e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 1.430511474609375e-05s
INFO | --- Analysis for DBpedia in Portuguese took 5.49853777885437s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 8.606910705566406e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.5342187881469727s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.4938359260559082s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.018221378326416016s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0005466938018798828s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 1.1920928955078125e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 8.106231689453125e-06s
INFO | --- Analysis for DBpedia Spotlight took 5.318326950073242s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.220008850097656e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 5.0067901611328125e-06s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.48720884323120117s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.01826930046081543s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0005180835723876953s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 6.771087646484375e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 1.0967254638671875e-05s
INFO | --- Analysis for DBpedia Spotlight NIF NER Corpus took 5.174468040466309s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 0.3016242980957031s
Availability | VoID file availability check for DBpedia Wikidata took 7.62939453125e-06s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.4490652084350586s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.02122783660888672s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0006337165832519531s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 1.4781951904296875e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 8.344650268554688e-06s
INFO | --- Analysis for DBpedia Wikidata took 4.97829270362854s
Availability | SPARQL endpoint availability check for DBpedia took 7.557868957519531e-05s
Availability | VoID file availability check for DBpedia took 6.4373016357421875e-06s
Completeness | Calculation of interlinking completeness for DBpedia took 1.416046380996704s
Reputation | Calculation of the PageRank for DBpedia took 0.01830434799194336s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0005178451538085938s
Interlinking | Calculation of Clustering coefficient for DBpedia took 1.239776611328125e-05s
Believability | Calculation of trust value for DBpedia took 1.3113021850585938e-05s
INFO | --- Analysis for DBpedia took 9.117408037185669s
Availability | SPARQL endpoint availability check for DBTropes took 8.440017700195312e-05s
Availability | VoID file availability check for DBTropes took 0.7907505035400391s
Completeness | Calculation of interlinking completeness for DBTropes took 0.6773905754089355s
Reputation | Calculation of the PageRank for DBTropes took 0.018399715423583984s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0005552768707275391s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.036064147949219e-05s
Believability | Calculation of trust value for DBTropes took 8.821487426757812e-06s
INFO | --- Analysis for DBTropes took 6.219335556030273s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 4.982948303222656e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 5.4836273193359375e-06s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 1.052015781402588s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.02061772346496582s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0005204677581787109s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 3.7670135498046875e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 1.3113021850585938e-05s
INFO | --- Analysis for DBTune – Music-Related RDF took 7.678721904754639s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 0.00010895729064941406s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.1964101791381836s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.6275067329406738s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.018694639205932617s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0005197525024414062s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.626678466796875e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 1.3589859008789062e-05s
INFO | --- Analysis for DBTune.org Artists: Last.fm took 6.542569398880005s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 8.463859558105469e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.17779803276062012s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 1.0098464488983154s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.01936197280883789s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0005879402160644531s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.7670135498046875e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 1.239776611328125e-05s
INFO | --- Analysis for DBTune.org AudioScrobbler RDF Service took 4.105101585388184s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 5.684257507324219s
Availability | VoID file availability check for DBTune.org/classical took 0.26360297203063965s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.29987239837646484s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.018537521362304688s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0005214214324951172s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.534027099609375e-05s
Interoperability | Check the re-using of existing vocabs for DBTune.org/classical took 2.6226043701171875e-06s
Believability | Calculation of trust value for DBTune.org/classical took 3.147125244140625e-05s
INFO | --- Analysis for DBTune.org/classical took 10.999085187911987s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 5.578566312789917s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.23804068565368652s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.29967713356018066s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.01873183250427246s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0005304813385009766s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 6.604194641113281e-05s
Interoperability | Check the re-using of existing vocabs for DBTune.org John Peel sessions RDF server took 3.337860107421875e-06s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 1.1444091796875e-05s
INFO | --- Analysis for DBTune.org John Peel sessions RDF server took 11.399481534957886s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 5.86253023147583s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.3117504119873047s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.4154491424560547s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.01900315284729004s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0005323886871337891s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 7.128715515136719e-05s
Interoperability | Check the re-using of existing vocabs for DBTune.org Magnatune RDF server took 2.86102294921875e-06s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 1.3113021850585938e-05s
INFO | --- Analysis for DBTune.org Magnatune RDF server took 10.968181371688843s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 0.13892173767089844s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.37651705741882324s
Extra | Recovery of all triples for DBTune.org Musicbrainz D2R Server took 33.82026410102844s
Performance | Total latancy measurement for DBTune.org Musicbrainz D2R Server took 0.5891387462615967s
Amount of data | Number of triples check for DBTune.org Musicbrainz D2R Server took 1.1314561367034912s
Interoperability | New terms check for DBTune.org Musicbrainz D2R Server took 1.6624915599822998s
Versatility | Languages check for DBTune.org Musicbrainz D2R Server took 1.6631572246551514s
Interpretability | Number of blank nodes check for DBTune.org Musicbrainz D2R Server took 0.8888499736785889s
Interpretability | RDF structures check for DBTune.org Musicbrainz D2R Server took 0.11790180206298828s
Versatility | Serialization formats check for DBTune.org Musicbrainz D2R Server took 0.11316514015197754s
Availability | RDF dump link check for DBTune.org Musicbrainz D2R Server took 0.08330655097961426s
License | MR license check for DBTune.org Musicbrainz D2R Server took 0.10185718536376953s
License | HR license check for DBTune.org Musicbrainz D2R Server took 3.445600986480713s
Amount of data | Number of property check for DBTune.org Musicbrainz D2R Server took 0.11591911315917969s
Understandability | Number of label check for DBTune.org Musicbrainz D2R Server took 0.2846696376800537s
Understandability | URI regex check for DBTune.org Musicbrainz D2R Server took 0.19575977325439453s
Understandability | Vocabs check for DBTune.org Musicbrainz D2R Server took 0.11084842681884766s
Verifiability | Authors check for DBTune.org Musicbrainz D2R Server took 0.3064894676208496s
Verifiability | Publishers check for DBTune.org Musicbrainz D2R Server took 0.08473634719848633s
Performance | Throughput check for DBTune.org Musicbrainz D2R Server took 10.283553123474121s
Amount of data | Check the number of entities for DBTune.org Musicbrainz D2R Server took 8.559226989746094e-05s
Verifiability | Contribs. check for DBTune.org Musicbrainz D2R Server took 0.1194462776184082s
Interlinking | sameAs chians check for DBTune.org Musicbrainz D2R Server took 0.5317080020904541s
Interlinking | skos check for DBTune.org Musicbrainz D2R Server took 0.10540890693664551s
Interlinking | skos check for DBTune.org Musicbrainz D2R Server took 0.10281157493591309s
Timeliness | dataset update frequency check for DBTune.org Musicbrainz D2R Server took 0.08542537689208984s
Currency | Creation date check for DBTune.org Musicbrainz D2R Server took 0.20093655586242676s
Currency | Modification date check for DBTune.org Musicbrainz D2R Server took 0.23502063751220703s
Rep.Conc. | URIs length for DBTune.org Musicbrainz D2R Server took 9.595333099365234s
Interoperability | New vocabularies check for DBTune.org Musicbrainz D2R Server took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for DBTune.org Musicbrainz D2R Server took 0.11540389060974121s
Accuracy | Check Functional Property for DBTune.org Musicbrainz D2R Server took 0.11090660095214844s
Accuracy | Check Inverse Functional Property for DBTune.org Musicbrainz D2R Server took 0.12432670593261719s
Accuracy | Check Empty annotation labels for DBTune.org Musicbrainz D2R Server took 2.1797165870666504s
Accuracy | Check White space in annotation for DBTune.org Musicbrainz D2R Server took 0.09254860877990723s
Accuracy | Check Datatype consistency for DBTune.org Musicbrainz D2R Server took 1.1503379344940186s
Consistency | Disjoint class check for DBTune.org Musicbrainz D2R Server took 0.1034235954284668s
Consistency | Check Misplaced properties for DBTune.org Musicbrainz D2R Server took 1.164494514465332s
Consistency | Check Ontology hijacking for DBTune.org Musicbrainz D2R Server took 3.929466485977173s
Consistency | Check Invalid usage of undefined classes for DBTune.org Musicbrainz D2R Server took 1.288510799407959s
Consistency | Check Invalid usage of undefined properties for DBTune.org Musicbrainz D2R Server took 2.1410818099975586s
Conciseness | Check Extensional conciseness for DBTune.org Musicbrainz D2R Server took 0.6160895824432373s
Security | Sign check for DBTune.org Musicbrainz D2R Server took 0.08752965927124023s
Availability | Check URIs Dereferenciability for DBTune.org Musicbrainz D2R Server took 2.634432077407837s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.39867162704467773s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.018511056900024414s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0005171298980712891s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.0001087188720703125s
Interoperability | Check the re-using of existing vocabs for DBTune.org Musicbrainz D2R Server took 1.430511474609375e-06s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 1.0967254638671875e-05s
INFO | --- Analysis for DBTune.org Musicbrainz D2R Server took 108.2414288520813s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 0.3773617744445801s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.22369742393493652s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.41311216354370117s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.02045464515686035s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.000522613525390625s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.435943603515625e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 1.239776611328125e-05s
INFO | --- Analysis for DBTune.org MySpace RDF Service took 3.3358397483825684s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 0.9756307601928711s
Availability | VoID file availability check for OpenUpLabs DCLG took 1.2858452796936035s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 1.6532037258148193s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.01830267906188965s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0005199909210205078s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 1.2636184692382812e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 1.239776611328125e-05s
INFO | --- Analysis for OpenUpLabs DCLG took 6.603617191314697s
Availability | SPARQL endpoint availability check for data.dcs took 8.845329284667969e-05s
Availability | VoID file availability check for data.dcs took 0.013427019119262695s
Completeness | Calculation of interlinking completeness for data.dcs took 0.6388983726501465s
Reputation | Calculation of the PageRank for data.dcs took 0.01889657974243164s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0005116462707519531s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.389617919921875e-05s
Believability | Calculation of trust value for data.dcs took 5.1021575927734375e-05s
INFO | --- Analysis for data.dcs took 4.577065467834473s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 5.420023441314697s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 1.6019928455352783s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.4878120422363281s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.020288944244384766s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0005209445953369141s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 1.239776611328125e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 1.2874603271484375e-05s
INFO | --- Analysis for Germany - Bundesministerium der Finanzen - Budget took 16.87765598297119s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 0.00010848045349121094s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 9.5367431640625e-06s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.4002699851989746s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.018062829971313477s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0005238056182861328s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.5762786865234375e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 1.2636184692382812e-05s
INFO | --- Analysis for de-gaap-ontology-lexicon took 8.308820486068726s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 0.00010657310485839844s
Availability | VoID file availability check for Debian Package Tracking System took 1.928809404373169s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.307659387588501s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.01858663558959961s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0005259513854980469s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 5.459785461425781e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 1.33514404296875e-05s
INFO | --- Analysis for Debian Package Tracking System took 11.055732011795044s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 8.726119995117188e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 5.245208740234375e-06s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.6428735256195068s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.020417213439941406s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0005249977111816406s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.2636184692382812e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.1444091796875e-05s
INFO | --- Analysis for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 7.439976692199707s
Availability | SPARQL endpoint availability check for Demografie took 8.153915405273438e-05s
Availability | VoID file availability check for Demografie took 5.7220458984375e-06s
Completeness | Calculation of interlinking completeness for Demografie took 1.0046982765197754s
Reputation | Calculation of the PageRank for Demografie took 0.019575119018554688s
Interlinking | Calculation of Degree of Connection for Demografie took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0005478858947753906s
Interlinking | Calculation of Clustering coefficient for Demografie took 1.1444091796875e-05s
Believability | Calculation of trust value for Demografie took 1.2159347534179688e-05s
INFO | --- Analysis for Demografie took 5.918064117431641s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 0.3886868953704834s
Availability | VoID file availability check for Projeto Desaparecidos took 0.01638174057006836s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 1.0040006637573242s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.01892542839050293s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0005295276641845703s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.314018249511719e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 1.0251998901367188e-05s
INFO | --- Analysis for Projeto Desaparecidos took 4.020989894866943s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 8.630752563476562e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 40.0328483581543s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.742487907409668s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.018875598907470703s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0005283355712890625s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 9.918212890625e-05s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 1.1205673217773438e-05s
INFO | --- Analysis for Deusto Entrepreneurship: sharing business knowledge took 143.29316878318787s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 4.1484832763671875e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 40.03831934928894s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 1.1698389053344727s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.018601179122924805s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0005838871002197266s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.0001163482666015625s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 1.3828277587890625e-05s
INFO | --- Analysis for DeustoTech (Deusto Institute of Technology) took 145.7490394115448s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 3.990199089050293s
Availability | VoID file availability check for Deutsche Biographie took 0.4489436149597168s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.8579647541046143s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.01894998550415039s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0005209445953369141s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 3.528594970703125e-05s
Believability | Calculation of trust value for Deutsche Biographie took 1.33514404296875e-05s
INFO | --- Analysis for Deutsche Biographie took 8.20025634765625s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 8.58306884765625e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.8803768157958984s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.5922987461090088s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.018555879592895508s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 6.0558319091796875e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 1.049041748046875e-05s
INFO | --- Analysis for Deutsche Nationalbibliografie (DNB) took 11.428577423095703s
Availability | SPARQL endpoint availability check for dev8d took 0.00012493133544921875s
Availability | VoID file availability check for dev8d took 6.4373016357421875e-06s
Completeness | Calculation of interlinking completeness for dev8d took 0.33966779708862305s
Reputation | Calculation of the PageRank for dev8d took 0.021414518356323242s
Interlinking | Calculation of Degree of Connection for dev8d took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for dev8d took 8.463859558105469e-05s
Believability | Calculation of trust value for dev8d took 1.2159347534179688e-05s
INFO | --- Analysis for dev8d took 5.348795413970947s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.144877433776855s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 19.999621629714966s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.3397071361541748s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.018177032470703125s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0005273818969726562s
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 1.1682510375976562e-05s
INFO | --- Analysis for Dewey Decimal Classification (DDC) took 93.62797355651855s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 8.368492126464844e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 7.152557373046875e-06s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.9842512607574463s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.018114566802978516s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0005161762237548828s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 1.239776611328125e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 1.2874603271484375e-05s
INFO | --- Analysis for Diachronic Ontologies from People's Daily took 4.649138689041138s
Availability | SPARQL endpoint availability check for Diavgeia took 0.8752858638763428s
Availability | VoID file availability check for Diavgeia took 0.6561980247497559s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.3431122303009033s
Reputation | Calculation of the PageRank for Diavgeia took 0.01901841163635254s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0005180835723876953s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.296966552734375e-05s
Believability | Calculation of trust value for Diavgeia took 8.344650268554688e-06s
INFO | --- Analysis for Diavgeia took 9.005832433700562s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 8.96453857421875e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.127535343170166s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.35871219635009766s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.018227815628051758s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0005948543548583984s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011801719665527344s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.239776611328125e-05s
INFO | --- Analysis for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 8.555735349655151s
Availability | SPARQL endpoint availability check for diigo.feed took 8.869171142578125e-05s
Availability | VoID file availability check for diigo.feed took 19.997032642364502s
Completeness | Calculation of interlinking completeness for diigo.feed took 1.2059211730957031s
Reputation | Calculation of the PageRank for diigo.feed took 0.018599510192871094s
Interlinking | Calculation of Degree of Connection for diigo.feed took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for diigo.feed took 0.0005502700805664062s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 1.0967254638671875e-05s
Believability | Calculation of trust value for diigo.feed took 1.1444091796875e-05s
INFO | --- Analysis for diigo.feed took 54.12331533432007s
Availability | SPARQL endpoint availability check for DisGeNET took 0.4645726680755615s
Availability | VoID file availability check for DisGeNET took 1.0728836059570312e-05s
Extra | Recovery of all triples for DisGeNET took 139.37264370918274s
Performance | Total latancy measurement for DisGeNET took 0.6123340129852295s
Amount of data | Number of triples check for DisGeNET took 5.119110107421875s
Interoperability | New terms check for DisGeNET took 4.688097953796387s
Versatility | Languages check for DisGeNET took 180.57587432861328s
Interpretability | Number of blank nodes check for DisGeNET took 3.5876243114471436s
Interpretability | RDF structures check for DisGeNET took 0.7160983085632324s
Versatility | Serialization formats check for DisGeNET took 0.4698970317840576s
Availability | RDF dump link check for DisGeNET took 16.535150051116943s
License | MR license check for DisGeNET took 1.17641282081604s
License | HR license check for DisGeNET took 181.4404296875s
Amount of data | Number of property check for DisGeNET took 0.1701490879058838s
Understandability | Number of label check for DisGeNET took 5.365983724594116s
Understandability | URI regex check for DisGeNET took 0.7975893020629883s
Understandability | Vocabs check for DisGeNET took 0.1781139373779297s
Verifiability | Authors check for DisGeNET took 0.15934109687805176s
Verifiability | Publishers check for DisGeNET took 0.2539534568786621s
Performance | Throughput check for DisGeNET took 13.463895320892334s
Amount of data | Check the number of entities for DisGeNET took 6.917554616928101s
Verifiability | Contribs. check for DisGeNET took 0.6014490127563477s
Interlinking | sameAs chians check for DisGeNET took 0.14454245567321777s
Interlinking | skos check for DisGeNET took 0.6266610622406006s
Interlinking | skos check for DisGeNET took 0.5107476711273193s
Timeliness | dataset update frequency check for DisGeNET took 0.7441918849945068s
Currency | Creation date check for DisGeNET took 0.7897124290466309s
Currency | Modification date check for DisGeNET took 0.1641538143157959s
Rep.Conc. | URIs length for DisGeNET took 55.09763193130493s
Interoperability | New vocabularies check for DisGeNET took 6.129507780075073s
Consistency | Deprecated classes/propertiers check for DisGeNET took 0.15892648696899414s
Accuracy | Check Functional Property for DisGeNET took 0.5393450260162354s
Accuracy | Check Inverse Functional Property for DisGeNET took 0.5193824768066406s
Accuracy | Check Empty annotation labels for DisGeNET took 54.09092998504639s
Accuracy | Check White space in annotation for DisGeNET took 1.8502113819122314s
Accuracy | Check Datatype consistency for DisGeNET took 1.3422963619232178s
Consistency | Disjoint class check for DisGeNET took 0.143082857131958s
Consistency | Check Misplaced properties for DisGeNET took 47.83494424819946s
Consistency | Misplaced classes for DisGeNET took 4.3272294998168945s
Consistency | Check Ontology hijacking for DisGeNET took 14.800744533538818s
Consistency | Check Invalid usage of undefined classes for DisGeNET took 1.218189001083374s
Consistency | Check Invalid usage of undefined properties for DisGeNET took 30.620214223861694s
Conciseness | Check Extensional conciseness for DisGeNET took 1.4473447799682617s
Conciseness | Check Intensional conciseness for DisGeNET took 0.3038060665130615s
Security | Sign check for DisGeNET took 2.4293365478515625s
Availability | Check URIs Dereferenciability for DisGeNET took 1819.6106417179108s
Completeness | Calculation of interlinking completeness for DisGeNET took 1.0385692119598389s
Reputation | Calculation of the PageRank for DisGeNET took 0.018895864486694336s
Interlinking | Calculation of Degree of Connection for DisGeNET took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.0001819133758544922s
Interoperability | Check the re-using of existing vocabs for DisGeNET took 5.9423508644104s
Believability | Calculation of trust value for DisGeNET took 1.2874603271484375e-05s
INFO | --- Analysis for DisGeNET took 2702.357140302658s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 8.749961853027344e-05s
Availability | VoID file availability check for CAP Italia in RDF took 5.9604644775390625e-06s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.7878296375274658s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.01909351348876953s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0005309581756591797s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 1.6927719116210938e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 1.1682510375976562e-05s
INFO | --- Analysis for CAP Italia in RDF took 8.891695737838745s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 0.0001246929168701172s
Availability | VoID file availability check for Distritos de Zaragoza took 5.4836273193359375e-06s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.7839760780334473s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.018801212310791016s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0005242824554443359s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 1.3828277587890625e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 1.1920928955078125e-05s
INFO | --- Analysis for Distritos de Zaragoza took 6.326942443847656s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 8.559226989746094e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 8.58306884765625e-06s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.3665428161621094s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.018182992935180664s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0005292892456054688s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 1.2636184692382812e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 1.2159347534179688e-05s
INFO | --- Analysis for DKH (Deusto Knowledge Hub) took 8.482293844223022s
Availability | SPARQL endpoint availability check for DM2E took 8.797645568847656e-05s
Availability | VoID file availability check for DM2E took 7.867813110351562e-06s
Completeness | Calculation of interlinking completeness for DM2E took 2.4768459796905518s
Reputation | Calculation of the PageRank for DM2E took 0.018828630447387695s
Interlinking | Calculation of Degree of Connection for DM2E took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DM2E took 0.0005168914794921875s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00011396408081054688s
Believability | Calculation of trust value for DM2E took 1.2159347534179688e-05s
INFO | --- Analysis for DM2E took 9.97889518737793s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 8.797645568847656e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.018778562545776367s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.33785343170166016s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.02003622055053711s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0005319118499755859s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 1.9073486328125e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 1.2159347534179688e-05s
INFO | --- Analysis for DMOZ RDF Dump took 2.9782638549804688s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 0.00010466575622558594s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.4109327793121338s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.6504027843475342s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.018259763717651367s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0005407333374023438s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00016117095947265625s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 6.67572021484375e-06s
INFO | --- Analysis for Gemeinsame Normdatei (GND) took 15.052356719970703s
Availability | SPARQL endpoint availability check for DOAP Store took 8.7738037109375e-05s
Availability | VoID file availability check for DOAP Store took 20.095049619674683s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.3331117630004883s
Reputation | Calculation of the PageRank for DOAP Store took 0.018900394439697266s
Interlinking | Calculation of Degree of Connection for DOAP Store took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for DOAP Store took 0.0005202293395996094s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 1.239776611328125e-05s
Believability | Calculation of trust value for DOAP Store took 1.0967254638671875e-05s
INFO | --- Analysis for DOAP Store took 46.535855293273926s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 8.320808410644531e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 1.0550072193145752s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 1.6825580596923828s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.018092870712280273s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0005214214324951172s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.151199340820312e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 9.298324584960938e-06s
INFO | --- Analysis for CrossRef DOI Resolver took 12.669981241226196s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 1.0821809768676758s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 1.049041748046875e-05s
Extra | Recovery of all triples for Drug Data from the Health Insurance Fund of Macedonia took 276.40822315216064s
Performance | Total latancy measurement for Drug Data from the Health Insurance Fund of Macedonia took 0.5399580001831055s
Amount of data | Number of triples check for Drug Data from the Health Insurance Fund of Macedonia took 47.35275721549988s
Interoperability | New terms check for Drug Data from the Health Insurance Fund of Macedonia took 4.163242340087891s
Versatility | Languages check for Drug Data from the Health Insurance Fund of Macedonia took 300.034973859787s
Interpretability | Number of blank nodes check for Drug Data from the Health Insurance Fund of Macedonia took 10.096368074417114s
Interpretability | RDF structures check for Drug Data from the Health Insurance Fund of Macedonia took 1.1872828006744385s
Versatility | Serialization formats check for Drug Data from the Health Insurance Fund of Macedonia took 0.5258030891418457s
Availability | RDF dump link check for Drug Data from the Health Insurance Fund of Macedonia took 0.20047998428344727s
License | MR license check for Drug Data from the Health Insurance Fund of Macedonia took 0.6952416896820068s
License | HR license check for Drug Data from the Health Insurance Fund of Macedonia took 2.8463308811187744s
Amount of data | Number of property check for Drug Data from the Health Insurance Fund of Macedonia took 0.1476430892944336s
Understandability | Number of label check for Drug Data from the Health Insurance Fund of Macedonia took 3.511948347091675s
Understandability | URI regex check for Drug Data from the Health Insurance Fund of Macedonia took 0.3242783546447754s
Understandability | Vocabs check for Drug Data from the Health Insurance Fund of Macedonia took 0.23341131210327148s
Verifiability | Authors check for Drug Data from the Health Insurance Fund of Macedonia took 0.26879310607910156s
Verifiability | Publishers check for Drug Data from the Health Insurance Fund of Macedonia took 0.24915194511413574s
Performance | Throughput check for Drug Data from the Health Insurance Fund of Macedonia took 10.659438371658325s
Amount of data | Check the number of entities for Drug Data from the Health Insurance Fund of Macedonia took 9.393692016601562e-05s
Verifiability | Contribs. check for Drug Data from the Health Insurance Fund of Macedonia took 0.10913705825805664s
Interlinking | sameAs chians check for Drug Data from the Health Insurance Fund of Macedonia took 0.12575268745422363s
Interlinking | skos check for Drug Data from the Health Insurance Fund of Macedonia took 0.49159979820251465s
Interlinking | skos check for Drug Data from the Health Insurance Fund of Macedonia took 0.07957696914672852s
Timeliness | dataset update frequency check for Drug Data from the Health Insurance Fund of Macedonia took 0.2088322639465332s
Currency | Creation date check for Drug Data from the Health Insurance Fund of Macedonia took 0.11160993576049805s
Currency | Modification date check for Drug Data from the Health Insurance Fund of Macedonia took 0.21194100379943848s
Rep.Conc. | URIs length for Drug Data from the Health Insurance Fund of Macedonia took 217.56467270851135s
Interoperability | New vocabularies check for Drug Data from the Health Insurance Fund of Macedonia took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Drug Data from the Health Insurance Fund of Macedonia took 0.14430522918701172s
Accuracy | Check Functional Property for Drug Data from the Health Insurance Fund of Macedonia took 0.19463539123535156s
Accuracy | Check Inverse Functional Property for Drug Data from the Health Insurance Fund of Macedonia took 0.12114477157592773s
Accuracy | Check Empty annotation labels for Drug Data from the Health Insurance Fund of Macedonia took 27.763011693954468s
Accuracy | Check White space in annotation for Drug Data from the Health Insurance Fund of Macedonia took 2.4199938774108887s
Accuracy | Check Datatype consistency for Drug Data from the Health Insurance Fund of Macedonia took 2.6576344966888428s
Consistency | Disjoint class check for Drug Data from the Health Insurance Fund of Macedonia took 0.11347389221191406s
Consistency | Check Misplaced properties for Drug Data from the Health Insurance Fund of Macedonia took 125.42880868911743s
Consistency | Misplaced classes for Drug Data from the Health Insurance Fund of Macedonia took 6.514758825302124s
Consistency | Check Ontology hijacking for Drug Data from the Health Insurance Fund of Macedonia took 84.34735155105591s
Consistency | Check Invalid usage of undefined classes for Drug Data from the Health Insurance Fund of Macedonia took 1.2334959506988525s
Consistency | Check Invalid usage of undefined properties for Drug Data from the Health Insurance Fund of Macedonia took 126.47601628303528s
Conciseness | Check Extensional conciseness for Drug Data from the Health Insurance Fund of Macedonia took 2.2901549339294434s
Conciseness | Check Intensional conciseness for Drug Data from the Health Insurance Fund of Macedonia took 0.36979198455810547s
Security | Sign check for Drug Data from the Health Insurance Fund of Macedonia took 1.2881927490234375s
Availability | Check URIs Dereferenciability for Drug Data from the Health Insurance Fund of Macedonia took 3.6637051105499268s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.39457225799560547s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.01920318603515625s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0005309581756591797s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 4.9591064453125e-05s
Interoperability | Check the re-using of existing vocabs for Drug Data from the Health Insurance Fund of Macedonia took 1.9073486328125e-06s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 1.2159347534179688e-05s
INFO | --- Analysis for Drug Data from the Health Insurance Fund of Macedonia took 3473.6231560707092s
Availability | SPARQL endpoint availability check for dspace took 0.00010395050048828125s
Availability | VoID file availability check for dspace took 1.430511474609375e-05s
Completeness | Calculation of interlinking completeness for dspace took 42.43228197097778s
Reputation | Calculation of the PageRank for dspace took 0.019863128662109375s
Interlinking | Calculation of Degree of Connection for dspace took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for dspace took 0.0005173683166503906s
Interlinking | Calculation of Clustering coefficient for dspace took 2.002716064453125e-05s
Believability | Calculation of trust value for dspace took 1.4066696166992188e-05s
INFO | --- Analysis for dspace took 462.95520663261414s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 2.8352203369140625s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.7724499702453613s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.3134157657623291s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.018352985382080078s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0005404949188232422s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 1.7404556274414062e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 1.1682510375976562e-05s
INFO | --- Analysis for DURAARK - Linked Building Data took 15.301622152328491s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 271.7737603187561s
Availability | VoID file availability check for MetaLex Document Server took 20.000057220458984s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.382610559463501s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.018493175506591797s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0005123615264892578s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 1.811981201171875e-05s
Believability | Calculation of trust value for MetaLex Document Server took 1.239776611328125e-05s
INFO | --- Analysis for MetaLex Document Server took 434.7595679759979s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 0.9681668281555176s
Availability | VoID file availability check for Dutch Ships and Sailors took 4.76837158203125e-06s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.27956557273864746s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.018317699432373047s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0005743503570556641s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 3.695487976074219e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 1.1444091796875e-05s
INFO | --- Analysis for Dutch Ships and Sailors took 8.374676942825317s
Availability | SPARQL endpoint availability check for DWS-Group took 8.845329284667969e-05s
Availability | VoID file availability check for DWS-Group took 2.3187103271484375s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.5072941780090332s
Reputation | Calculation of the PageRank for DWS-Group took 0.01804351806640625s
Interlinking | Calculation of Degree of Connection for DWS-Group took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DWS-Group took 0.0005185604095458984s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010347366333007812s
Believability | Calculation of trust value for DWS-Group took 9.775161743164062e-06s
INFO | --- Analysis for DWS-Group took 4.51090145111084s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 8.630752563476562e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 5.554155349731445s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.3865389823913574s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.018000125885009766s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.000530242919921875s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 1.239776611328125e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 1.2159347534179688e-05s
INFO | --- Analysis for E1 - Nuvem dados took 10.881009340286255s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 1.1410229206085205s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.6388792991638184s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.8683443069458008s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.018271684646606445s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 2.9802322387695312e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0005156993865966797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00011658668518066406s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i @ University of Alaska Fairbanks took 11.082638502120972s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 30.157791137695312s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 20.09833002090454s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 2.0331356525421143s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020783424377441406s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0005586147308349609s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 6.413459777832031e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i @ Clark Atlanta University took 94.14991497993469s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 30.313241481781006s
Availability | VoID file availability check for eagle-i @ The City College of New York took 20.097975492477417s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.4363369941711426s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.01842641830444336s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0005810260772705078s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.794929504394531e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i @ The City College of New York took 94.13783669471741s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 30.074376106262207s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 20.094868898391724s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 1.1405813694000244s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.021190166473388672s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0005371570587158203s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 0.00010085105895996094s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i @ Charles R. Drew University took 96.03353381156921s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 30.172022581100464s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 20.19600486755371s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.4705991744995117s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.01914358139038086s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0005650520324707031s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00016069412231445312s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i @ Dartmouth College took 92.72295928001404s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 30.060293197631836s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 20.097667455673218s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 1.848572015762329s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.018378257751464844s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0005202293395996094s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.440017700195312e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i @ Florida Agricultural and Mechanical University took 93.75533390045166s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 5.974526882171631s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.6197547912597656s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.33516383171081543s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.019017696380615234s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0005190372467041016s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.0001366138458251953s
Believability | Calculation of trust value for eagle-i @ Harvard University took 1.4543533325195312e-05s
INFO | --- Analysis for eagle-i @ Harvard University took 12.261681079864502s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 2.9488027095794678s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 1.1091530323028564s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.3955965042114258s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.019448041915893555s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0005779266357421875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.0001347064971923828s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 1.3589859008789062e-05s
INFO | --- Analysis for eagle-i @ University of Hawai’i at Mānoa took 192.90213990211487s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 30.342936038970947s
Availability | VoID file availability check for eagle-i @ Howard University took 20.199748039245605s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.5742161273956299s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.018692493438720703s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0005128383636474609s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.29425048828125e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i @ Howard University took 94.22895216941833s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 30.23836088180542s
Availability | VoID file availability check for eagle-i @ Hunter College took 20.006344318389893s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.6055879592895508s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.018612384796142578s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0005245208740234375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.914138793945312e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 1.3589859008789062e-05s
INFO | --- Analysis for eagle-i @ Hunter College took 93.25905728340149s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 1.0676054954528809s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.649573564529419s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.4440009593963623s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.018506288528442383s
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.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011301040649414062s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 1.0251998901367188e-05s
INFO | --- Analysis for eagle-i @ Jackson State University took 12.23838472366333s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 30.174375534057617s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 20.199302434921265s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 1.2193324565887451s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.01889348030090332s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0005586147308349609s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 5.125999450683594e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 1.3828277587890625e-05s
INFO | --- Analysis for eagle-i @ Meharry Medical College took 94.7779746055603s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 30.088959217071533s
Availability | VoID file availability check for eagle-i @ Montana State University took 20.005274772644043s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.6737496852874756s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.020848989486694336s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0005342960357666016s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 9.369850158691406e-05s
Believability | Calculation of trust value for eagle-i @ Montana State University took 1.3589859008789062e-05s
INFO | --- Analysis for eagle-i @ Montana State University took 98.32147789001465s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 1.0846173763275146s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.6530318260192871s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 2.2711968421936035s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.019724369049072266s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0005388259887695312s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.489059448242188e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i @ Morehouse School of Medicine took 16.636391401290894s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 1.0830535888671875s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 7.457448959350586s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.7163984775543213s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.01869034767150879s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0005326271057128906s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00013518333435058594s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 1.2874603271484375e-05s
INFO | --- Analysis for eagle-i @ Oregon Health and Science University took 258.3565695285797s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 1.0883960723876953s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.6252315044403076s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 1.9872474670410156s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020063161849975586s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0005300045013427734s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.794929504394531e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i @ Ponce School of Medicine took 14.479483604431152s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 1.1085443496704102s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.6230499744415283s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.3318819999694824s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.018364429473876953s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0005316734313964844s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.723403930664062e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 1.3113021850585938e-05s
INFO | --- Analysis for eagle-i @ Texas Southern University took 10.088456869125366s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 1.067307710647583s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 2.246565103530884s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.3900303840637207s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.018572092056274414s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.00051116943359375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.604194641113281e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 1.33514404296875e-05s
INFO | --- Analysis for eagle-i @ Tuskegee University took 8.286197423934937s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 1.0447449684143066s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.6176331043243408s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.33529019355773926s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.01941204071044922s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.00052642822265625s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 9.5367431640625e-05s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 1.2874603271484375e-05s
INFO | --- Analysis for eagle-i @ Universidad Central del Caribe took 9.057424306869507s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.0838322639465332s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.6749770641326904s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 6.962654113769531s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.01840686798095703s
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.0005335807800292969s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00012540817260742188s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 31.434979915618896s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 1.085336685180664s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.6580729484558105s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.8664140701293945s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.018870115280151367s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0005304813385009766s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 5.91278076171875e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i @ University of Texas at El Paso took 16.963442087173462s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 30.048774003982544s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 19.99871015548706s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.2789123058319092s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.018712520599365234s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0005452632904052734s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 6.866455078125e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i @ University of Texas at San Antonio took 96.12515020370483s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.16799473762512207s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.015378236770629883s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 1.0204379558563232s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.018185853958129883s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.000530242919921875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.083747863769531e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i @ Vanderbilt University took 5.656823635101318s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 1.0564379692077637s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.6265270709991455s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.8406050205230713s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.018598318099975586s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0005249977111816406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.200241088867188e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i @ Xavier University of Louisiana took 11.351365327835083s
Availability | SPARQL endpoint availability check for Emergency situation took 0.8072621822357178s
Availability | VoID file availability check for Emergency situation took 0.4413576126098633s
Completeness | Calculation of interlinking completeness for Emergency situation took 2.6628847122192383s
Reputation | Calculation of the PageRank for Emergency situation took 0.018445253372192383s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0005204677581787109s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.458427429199219e-05s
Believability | Calculation of trust value for Emergency situation took 1.2874603271484375e-05s
INFO | --- Analysis for Emergency situation took 10.234948873519897s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.1817779541015625s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.016040325164794922s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 2.09000563621521s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.01936054229736328s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0005345344543457031s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 9.942054748535156e-05s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for European Central Bank (ECB) Linked Data took 4.598406791687012s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 2.8216464519500732s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 4.822816610336304s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.38160228729248047s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.018229961395263672s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0005214214324951172s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 4.7206878662109375e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 9.298324584960938e-06s
INFO | --- Analysis for European Central Bank Statistics (PublicData.eu) took 19.935125827789307s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 2.228900194168091s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.5983049869537354s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.5297379493713379s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.018238544464111328s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0005555152893066406s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.556510925292969e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 1.2636184692382812e-05s
INFO | --- Analysis for ECCO-TCP Eighteenth Century Texts Linked Data took 6.559653997421265s
Availability | SPARQL endpoint availability check for ECLAP took 6.295822381973267s
Availability | VoID file availability check for ECLAP took 7.62939453125e-06s
Completeness | Calculation of interlinking completeness for ECLAP took 0.5048668384552002s
Reputation | Calculation of the PageRank for ECLAP took 0.01862192153930664s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0005204677581787109s
Interlinking | Calculation of Clustering coefficient for ECLAP took 4.100799560546875e-05s
Believability | Calculation of trust value for ECLAP took 1.2636184692382812e-05s
INFO | --- Analysis for ECLAP took 12.322002172470093s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 8.916854858398438e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.07294058799743652s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.5221641063690186s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.018166542053222656s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0005204677581787109s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.2928924560546875e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 6.9141387939453125e-06s
INFO | --- Analysis for School of Electronics and Computer Science, University of Southampton took 3.244702100753784s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 8.58306884765625e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 5.245208740234375e-06s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 1.120220422744751s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.021003246307373047s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0005209445953369141s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 1.2159347534179688e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 1.2159347534179688e-05s
INFO | --- Analysis for Edificios Históricos en Zaragoza took 6.8676817417144775s
Availability | SPARQL endpoint availability check for Edublogs took 8.821487426757812e-05s
Availability | VoID file availability check for Edublogs took 8.821487426757812e-06s
Completeness | Calculation of interlinking completeness for Edublogs took 0.46347737312316895s
Reputation | Calculation of the PageRank for Edublogs took 0.018106698989868164s
Interlinking | Calculation of Degree of Connection for Edublogs took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Edublogs took 0.0005209445953369141s
Interlinking | Calculation of Clustering coefficient for Edublogs took 9.751319885253906e-05s
Believability | Calculation of trust value for Edublogs took 1.1920928955078125e-05s
INFO | --- Analysis for Edublogs took 8.336508750915527s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.7521147727966309s
Availability | VoID file availability check for education.data.gov.uk took 0.678948163986206s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.43204283714294434s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.019150257110595703s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0005207061767578125s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 8.678436279296875e-05s
Believability | Calculation of trust value for education.data.gov.uk took 9.059906005859375e-06s
INFO | --- Analysis for education.data.gov.uk took 11.64909029006958s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 0.0774080753326416s
Availability | VoID file availability check for OpenUpLabs Education took 0.014172077178955078s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.3871035575866699s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.018965721130371094s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0005843639373779297s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 5.245208740234375e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 1.1682510375976562e-05s
INFO | --- Analysis for OpenUpLabs Education took 2.5732004642486572s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 392.032497882843s
Availability | VoID file availability check for Educational programs - SISVU took 262.1437740325928s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 2.0252609252929688s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.019756078720092773s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.00058746337890625s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 5.555152893066406e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 1.2636184692382812e-05s
INFO | --- Analysis for Educational programs - SISVU took 1447.1751482486725s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 1.389901876449585s
Availability | VoID file availability check for European Environment Agency Published Products took 2.3493754863739014s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 1.4723937511444092s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.019823551177978516s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.000518798828125s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 3.695487976074219e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 9.059906005859375e-06s
INFO | --- Analysis for European Environment Agency Published Products took 11.851325035095215s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.5051538944244385s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.25827503204345703s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 1.0649118423461914s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.018385887145996094s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.00052642822265625s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.125999450683594e-05s
Interoperability | Check the re-using of existing vocabs for EEA Reporting Obligations Database took 1.7726073265075684s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 8.58306884765625e-06s
INFO | --- Analysis for EEA Reporting Obligations Database took 12.06754994392395s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.2381279468536377s
Availability | VoID file availability check for EEA Vocabularies took 6.67572021484375e-06s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.6528749465942383s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.020154237747192383s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0005154609680175781s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 7.724761962890625e-05s
Believability | Calculation of trust value for EEA Vocabularies took 1.1444091796875e-05s
INFO | --- Analysis for EEA Vocabularies took 13.27354907989502s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 32.55364513397217s
Availability | VoID file availability check for Ege University Linked Open Data took 20.09477710723877s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 1.111128568649292s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.018457651138305664s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0005180835723876953s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 1.239776611328125e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 1.0967254638671875e-05s
INFO | --- Analysis for Ege University Linked Open Data took 70.08342671394348s
Availability | SPARQL endpoint availability check for E-Government Ontology took 1.2210297584533691s
Availability | VoID file availability check for E-Government Ontology took 0.612267255783081s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 4.163153409957886s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.018162012100219727s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0005309581756591797s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 1.239776611328125e-05s
Believability | Calculation of trust value for E-Government Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for E-Government Ontology took 16.240107774734497s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5248091220855713s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8413143157958984s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 2.340444803237915s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.0966525077819824s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7008771896362305s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.8732168674468994s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.460169315338135s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 3.4291813373565674s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5956218242645264s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23854565620422363s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.20133304595947266s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.42919325828552246s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 4.55634880065918s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2025284767150879s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3828105926513672s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6658957004547119s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.29099082946777344s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6244518756866455s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23941349983215332s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 11.622827768325806s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 8.726119995117188e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.32057762145996094s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.26302194595336914s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5553865432739258s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.19991040229797363s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4155995845794678s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.28539490699768066s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.46230316162109375s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 4.931755542755127s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2450110912322998s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.31919360160827637s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2938251495361328s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 2.1017653942108154s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.027625560760498047s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0283510684967041s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4114718437194824s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 3.7959020137786865s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6459016799926758s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 3.4904582500457764s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.341139793395996s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.949019193649292s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03329038619995117s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.46739888191223145s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.38004446029663086s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 3207.836437225342s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5900375843048096s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.018445491790771484s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0005245208740234375s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 4.553794860839844e-05s
Interoperability | Check the re-using of existing vocabs for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1920928955078125e-06s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1682510375976562e-05s
INFO | --- Analysis for Aragon Interoperable Information Structure EI2A - aragon open data took 3396.3766174316406s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 0.6192965507507324s
Availability | VoID file availability check for EIONET RDF Data took 0.3189249038696289s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.3321647644042969s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.018514156341552734s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0005583763122558594s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00011038780212402344s
Interoperability | Check the re-using of existing vocabs for EIONET RDF Data took 1.6689300537109375e-06s
Believability | Calculation of trust value for EIONET RDF Data took 9.775161743164062e-06s
INFO | --- Analysis for EIONET RDF Data took 6.233812093734741s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 0.24308061599731445s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.6943292617797852s
Extra | Recovery of all triples for ELTE Digital Institutional Repository (EDIT) took 30.658737897872925s
Performance | Total latancy measurement for ELTE Digital Institutional Repository (EDIT) took 0.5706508159637451s
Amount of data | Number of triples check for ELTE Digital Institutional Repository (EDIT) took 27.829757928848267s
Interoperability | New terms check for ELTE Digital Institutional Repository (EDIT) took 1.6516125202178955s
Versatility | Languages check for ELTE Digital Institutional Repository (EDIT) took 23.589312076568604s
Interpretability | Number of blank nodes check for ELTE Digital Institutional Repository (EDIT) took 2.6885926723480225s
Security | Check HTTPS for ELTE Digital Institutional Repository (EDIT) took 0.1243739128112793s
Interpretability | RDF structures check for ELTE Digital Institutional Repository (EDIT) took 0.7720324993133545s
Versatility | Serialization formats check for ELTE Digital Institutional Repository (EDIT) took 0.15238595008850098s
Availability | RDF dump link check for ELTE Digital Institutional Repository (EDIT) took 0.09911918640136719s
License | MR license check for ELTE Digital Institutional Repository (EDIT) took 0.26424336433410645s
License | HR license check for ELTE Digital Institutional Repository (EDIT) took 0.31969165802001953s
Amount of data | Number of property check for ELTE Digital Institutional Repository (EDIT) took 0.1728498935699463s
Understandability | Number of label check for ELTE Digital Institutional Repository (EDIT) took 18.721598148345947s
Understandability | URI regex check for ELTE Digital Institutional Repository (EDIT) took 0.21912097930908203s
Understandability | Vocabs check for ELTE Digital Institutional Repository (EDIT) took 0.0786581039428711s
Verifiability | Authors check for ELTE Digital Institutional Repository (EDIT) took 6.887067079544067s
Verifiability | Publishers check for ELTE Digital Institutional Repository (EDIT) took 2.190469264984131s
Performance | Throughput check for ELTE Digital Institutional Repository (EDIT) took 14.8909432888031s
Amount of data | Check the number of entities for ELTE Digital Institutional Repository (EDIT) took 8.487701416015625e-05s
Verifiability | Contribs. check for ELTE Digital Institutional Repository (EDIT) took 0.0890657901763916s
Interlinking | sameAs chians check for ELTE Digital Institutional Repository (EDIT) took 0.10706877708435059s
Interlinking | skos check for ELTE Digital Institutional Repository (EDIT) took 0.20305466651916504s
Interlinking | skos check for ELTE Digital Institutional Repository (EDIT) took 0.10169720649719238s
Timeliness | dataset update frequency check for ELTE Digital Institutional Repository (EDIT) took 0.1478288173675537s
Currency | Creation date check for ELTE Digital Institutional Repository (EDIT) took 3.6405892372131348s
Currency | Modification date check for ELTE Digital Institutional Repository (EDIT) took 0.5368361473083496s
Rep.Conc. | URIs length for ELTE Digital Institutional Repository (EDIT) took 97.23681092262268s
Interoperability | New vocabularies check for ELTE Digital Institutional Repository (EDIT) took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for ELTE Digital Institutional Repository (EDIT) took 0.17792534828186035s
Accuracy | Check Functional Property for ELTE Digital Institutional Repository (EDIT) took 0.17487311363220215s
Accuracy | Check Inverse Functional Property for ELTE Digital Institutional Repository (EDIT) took 0.10110783576965332s
Accuracy | Check Empty annotation labels for ELTE Digital Institutional Repository (EDIT) took 2.3203072547912598s
Accuracy | Check White space in annotation for ELTE Digital Institutional Repository (EDIT) took 0.3761141300201416s
Accuracy | Check Datatype consistency for ELTE Digital Institutional Repository (EDIT) took 4.807382583618164s
Consistency | Disjoint class check for ELTE Digital Institutional Repository (EDIT) took 0.1953279972076416s
Consistency | Check Misplaced properties for ELTE Digital Institutional Repository (EDIT) took 4.888324975967407s
Consistency | Check Ontology hijacking for ELTE Digital Institutional Repository (EDIT) took 1.4076218605041504s
Consistency | Check Invalid usage of undefined classes for ELTE Digital Institutional Repository (EDIT) took 1.3483843803405762s
Consistency | Check Invalid usage of undefined properties for ELTE Digital Institutional Repository (EDIT) took 6.34352445602417s
Conciseness | Check Extensional conciseness for ELTE Digital Institutional Repository (EDIT) took 2.8743083477020264s
Security | Sign check for ELTE Digital Institutional Repository (EDIT) took 0.285689115524292s
Availability | Check URIs Dereferenciability for ELTE Digital Institutional Repository (EDIT) took 998.4553635120392s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 1.7978618144989014s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.022959232330322266s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 7.390975952148438e-05s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0005095005035400391s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 1.7642974853515625e-05s
Interoperability | Check the re-using of existing vocabs for ELTE Digital Institutional Repository (EDIT) took 1.6689300537109375e-06s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 1.33514404296875e-05s
INFO | --- Analysis for ELTE Digital Institutional Repository (EDIT) took 1474.9442780017853s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 0.29672718048095703s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.2529139518737793s
Extra | Recovery of all triples for El Viajero's tourism dataset took 4.843898773193359s
Performance | Total latancy measurement for El Viajero's tourism dataset took 0.5253841876983643s
Amount of data | Number of triples check for El Viajero's tourism dataset took 0.5692465305328369s
Interoperability | New terms check for El Viajero's tourism dataset took 1.8147227764129639s
Versatility | Languages check for El Viajero's tourism dataset took 12.57663106918335s
Interpretability | Number of blank nodes check for El Viajero's tourism dataset took 0.16232681274414062s
Interpretability | RDF structures check for El Viajero's tourism dataset took 0.1973576545715332s
Versatility | Serialization formats check for El Viajero's tourism dataset took 0.14271283149719238s
Availability | RDF dump link check for El Viajero's tourism dataset took 0.1010892391204834s
License | MR license check for El Viajero's tourism dataset took 0.10485339164733887s
License | HR license check for El Viajero's tourism dataset took 0.48480820655822754s
Amount of data | Number of property check for El Viajero's tourism dataset took 0.1875452995300293s
Understandability | Number of label check for El Viajero's tourism dataset took 0.20023012161254883s
Understandability | URI regex check for El Viajero's tourism dataset took 0.1968519687652588s
Understandability | Vocabs check for El Viajero's tourism dataset took 0.10088515281677246s
Verifiability | Authors check for El Viajero's tourism dataset took 0.14359068870544434s
Verifiability | Publishers check for El Viajero's tourism dataset took 0.10061907768249512s
Performance | Throughput check for El Viajero's tourism dataset took 10.557621240615845s
Amount of data | Check the number of entities for El Viajero's tourism dataset took 0.0006031990051269531s
Verifiability | Contribs. check for El Viajero's tourism dataset took 0.08075952529907227s
Interlinking | sameAs chians check for El Viajero's tourism dataset took 0.14036178588867188s
Interlinking | skos check for El Viajero's tourism dataset took 0.1588892936706543s
Interlinking | skos check for El Viajero's tourism dataset took 0.10155415534973145s
Timeliness | dataset update frequency check for El Viajero's tourism dataset took 0.07976794242858887s
Currency | Creation date check for El Viajero's tourism dataset took 0.16103363037109375s
Currency | Modification date check for El Viajero's tourism dataset took 0.13961243629455566s
Rep.Conc. | URIs length for El Viajero's tourism dataset took 2.352342128753662s
Interoperability | New vocabularies check for El Viajero's tourism dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for El Viajero's tourism dataset took 0.20050358772277832s
Accuracy | Check Functional Property for El Viajero's tourism dataset took 0.1758897304534912s
Accuracy | Check Inverse Functional Property for El Viajero's tourism dataset took 0.08206844329833984s
Accuracy | Check Empty annotation labels for El Viajero's tourism dataset took 1.2257592678070068s
Accuracy | Check White space in annotation for El Viajero's tourism dataset took 0.032318830490112305s
Accuracy | Check Datatype consistency for El Viajero's tourism dataset took 0.027281522750854492s
Consistency | Disjoint class check for El Viajero's tourism dataset took 0.18709301948547363s
Consistency | Check Misplaced properties for El Viajero's tourism dataset took 0.9603245258331299s
Consistency | Misplaced classes for El Viajero's tourism dataset took 0.26662540435791016s
Consistency | Check Ontology hijacking for El Viajero's tourism dataset took 2.727311372756958s
Consistency | Check Invalid usage of undefined classes for El Viajero's tourism dataset took 1.5587072372436523s
Consistency | Check Invalid usage of undefined properties for El Viajero's tourism dataset took 2.425509214401245s
Conciseness | Check Extensional conciseness for El Viajero's tourism dataset took 0.0317232608795166s
Conciseness | Check Intensional conciseness for El Viajero's tourism dataset took 0.2306814193725586s
Security | Sign check for El Viajero's tourism dataset took 0.10165905952453613s
Availability | Check URIs Dereferenciability for El Viajero's tourism dataset took 1424.110752105713s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 180.22678303718567s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.01941204071044922s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 5.793571472167969e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0005466938018798828s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 0.0001373291015625s
Interoperability | Check the re-using of existing vocabs for El Viajero's tourism dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for El Viajero's tourism dataset took 1.2874603271484375e-05s
INFO | --- Analysis for El Viajero's tourism dataset took 1972.2988379001617s
Availability | SPARQL endpoint availability check for EMN took 9.34600830078125e-05s
Availability | VoID file availability check for EMN took 6.4373016357421875e-06s
Completeness | Calculation of interlinking completeness for EMN took 0.31430506706237793s
Reputation | Calculation of the PageRank for EMN took 0.018450021743774414s
Interlinking | Calculation of Degree of Connection for EMN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EMN took 0.0005152225494384766s
Interlinking | Calculation of Clustering coefficient for EMN took 5.555152893066406e-05s
Believability | Calculation of trust value for EMN took 1.2159347534179688e-05s
INFO | --- Analysis for EMN took 146.40057849884033s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 8.416175842285156e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.01605057716369629s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.39593982696533203s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.020642518997192383s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0005223751068115234s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.0067901611328125e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 9.5367431640625e-06s
INFO | --- Analysis for EnAKTing CO2 Emission Dataset took 32.75897192955017s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 8.7738037109375e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.028014659881591797s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.31369519233703613s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.019296646118164062s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0005266666412353516s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 4.1484832763671875e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 9.775161743164062e-06s
INFO | --- Analysis for EnAKTing Crime Dataset took 2.6995437145233154s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 8.821487426757812e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.01599264144897461s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.3075699806213379s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.018462181091308594s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0005295276641845703s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 4.172325134277344e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 8.106231689453125e-06s
INFO | --- Analysis for EnAKTing Energy Dataset took 2.477023124694824s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 0.00011086463928222656s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.018108606338500977s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.28188562393188477s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.018947362899780273s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0005700588226318359s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 0.00010204315185546875s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 8.821487426757812e-06s
INFO | --- Analysis for EnAKTing Mortality Dataset took 1.9361841678619385s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 8.7738037109375e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.016221284866333008s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.5490028858184814s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.020201683044433594s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0005180835723876953s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 4.029273986816406e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 8.106231689453125e-06s
INFO | --- Analysis for EnAKTing NHS Dataset took 2.4826760292053223s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 8.749961853027344e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.023174524307250977s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.3472747802734375s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.018317461013793945s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0005245208740234375s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.459785461425781e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 8.106231689453125e-06s
INFO | --- Analysis for EnAKTing Population Dataset took 2.0139541625976562s
Availability | SPARQL endpoint availability check for Enel Shops took 8.893013000488281e-05s
Availability | VoID file availability check for Enel Shops took 1.430511474609375e-05s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.49807000160217285s
Reputation | Calculation of the PageRank for Enel Shops took 0.01846599578857422s
Interlinking | Calculation of Degree of Connection for Enel Shops took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Enel Shops took 0.0005197525024414062s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 1.239776611328125e-05s
Believability | Calculation of trust value for Enel Shops took 1.1205673217773438e-05s
INFO | --- Analysis for Enel Shops took 2.111813545227051s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 1.2137787342071533s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 8.58306884765625e-06s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.4730210304260254s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.019545793533325195s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0005142688751220703s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 1.2874603271484375e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 2.2172927856445312e-05s
INFO | --- Analysis for Energy efficiency assessments and improvements took 6.890410900115967s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 0.6473524570465088s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 5.4836273193359375e-06s
Extra | Recovery of all triples for English Heritage Archaeological Sciences Thesaurus took 0.3842470645904541s
Performance | Total latancy measurement for English Heritage Archaeological Sciences Thesaurus took 1.9091506004333496s
Amount of data | Number of triples check for English Heritage Archaeological Sciences Thesaurus took 0.624439001083374s
Versatility | Languages check for English Heritage Archaeological Sciences Thesaurus took 0.36542749404907227s
Interpretability | Number of blank nodes check for English Heritage Archaeological Sciences Thesaurus took 0.6388161182403564s
Security | Check HTTPS for English Heritage Archaeological Sciences Thesaurus took 0.26468849182128906s
Interpretability | RDF structures check for English Heritage Archaeological Sciences Thesaurus took 0.29701757431030273s
Versatility | Serialization formats check for English Heritage Archaeological Sciences Thesaurus took 0.39566946029663086s
Availability | RDF dump link check for English Heritage Archaeological Sciences Thesaurus took 0.3790287971496582s
License | MR license check for English Heritage Archaeological Sciences Thesaurus took 0.6256799697875977s
License | HR license check for English Heritage Archaeological Sciences Thesaurus took 0.4801771640777588s
Amount of data | Number of property check for English Heritage Archaeological Sciences Thesaurus took 0.5402147769927979s
Understandability | Number of label check for English Heritage Archaeological Sciences Thesaurus took 0.6444504261016846s
Understandability | URI regex check for English Heritage Archaeological Sciences Thesaurus took 0.7758231163024902s
Understandability | Vocabs check for English Heritage Archaeological Sciences Thesaurus took 0.4465627670288086s
Verifiability | Authors check for English Heritage Archaeological Sciences Thesaurus took 0.4418513774871826s
Verifiability | Publishers check for English Heritage Archaeological Sciences Thesaurus took 0.44550275802612305s
Performance | Throughput check for English Heritage Archaeological Sciences Thesaurus took 12.138073444366455s
Amount of data | Check the number of entities for English Heritage Archaeological Sciences Thesaurus took 8.440017700195312e-05s
Verifiability | Contribs. check for English Heritage Archaeological Sciences Thesaurus took 0.3746335506439209s
Interlinking | sameAs chians check for English Heritage Archaeological Sciences Thesaurus took 0.3929574489593506s
Interlinking | skos check for English Heritage Archaeological Sciences Thesaurus took 0.59653639793396s
Interlinking | skos check for English Heritage Archaeological Sciences Thesaurus took 0.5036654472351074s
Timeliness | dataset update frequency check for English Heritage Archaeological Sciences Thesaurus took 0.4458315372467041s
Currency | Creation date check for English Heritage Archaeological Sciences Thesaurus took 0.9373989105224609s
Currency | Modification date check for English Heritage Archaeological Sciences Thesaurus took 0.8342881202697754s
Rep.Conc. | URIs length for English Heritage Archaeological Sciences Thesaurus took 0.9278037548065186s
Interoperability | New vocabularies check for English Heritage Archaeological Sciences Thesaurus took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Archaeological Sciences Thesaurus took 0.4627346992492676s
Accuracy | Check Functional Property for English Heritage Archaeological Sciences Thesaurus took 0.4196910858154297s
Accuracy | Check Inverse Functional Property for English Heritage Archaeological Sciences Thesaurus took 0.4111602306365967s
Consistency | Disjoint class check for English Heritage Archaeological Sciences Thesaurus took 0.4053487777709961s
Consistency | Check Ontology hijacking for English Heritage Archaeological Sciences Thesaurus took 0.3742244243621826s
Consistency | Check Invalid usage of undefined properties for English Heritage Archaeological Sciences Thesaurus took 1.8160512447357178s
Conciseness | Check Extensional conciseness for English Heritage Archaeological Sciences Thesaurus took 0.00015306472778320312s
Security | Sign check for English Heritage Archaeological Sciences Thesaurus took 0.5906989574432373s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.3442983627319336s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.020218610763549805s
Interlinking | Calculation of Degree of Connection for English Heritage Archaeological Sciences Thesaurus took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for English Heritage Archaeological Sciences Thesaurus took 0.0005130767822265625s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 1.3589859008789062e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Archaeological Sciences Thesaurus took 1.430511474609375e-06s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 1.2159347534179688e-05s
INFO | --- Analysis for English Heritage Archaeological Sciences Thesaurus took 70.75242352485657s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 0.39527153968811035s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 1.1205673217773438e-05s
Extra | Recovery of all triples for English Heritage Building Materials Thesaurus took 0.475144624710083s
Performance | Total latancy measurement for English Heritage Building Materials Thesaurus took 1.9731519222259521s
Amount of data | Number of triples check for English Heritage Building Materials Thesaurus took 0.5327847003936768s
Versatility | Languages check for English Heritage Building Materials Thesaurus took 0.36226987838745117s
Interpretability | Number of blank nodes check for English Heritage Building Materials Thesaurus took 0.7548394203186035s
Security | Check HTTPS for English Heritage Building Materials Thesaurus took 0.3162987232208252s
Interpretability | RDF structures check for English Heritage Building Materials Thesaurus took 0.3452439308166504s
Versatility | Serialization formats check for English Heritage Building Materials Thesaurus took 0.49866485595703125s
Availability | RDF dump link check for English Heritage Building Materials Thesaurus took 0.3780100345611572s
License | MR license check for English Heritage Building Materials Thesaurus took 0.6132588386535645s
License | HR license check for English Heritage Building Materials Thesaurus took 0.5439424514770508s
Amount of data | Number of property check for English Heritage Building Materials Thesaurus took 0.6950094699859619s
Understandability | Number of label check for English Heritage Building Materials Thesaurus took 0.6313748359680176s
Understandability | URI regex check for English Heritage Building Materials Thesaurus took 1.0074570178985596s
Understandability | Vocabs check for English Heritage Building Materials Thesaurus took 0.4039039611816406s
Verifiability | Authors check for English Heritage Building Materials Thesaurus took 0.44297218322753906s
Verifiability | Publishers check for English Heritage Building Materials Thesaurus took 0.4604034423828125s
Performance | Throughput check for English Heritage Building Materials Thesaurus took 12.627521991729736s
Amount of data | Check the number of entities for English Heritage Building Materials Thesaurus took 0.00010061264038085938s
Verifiability | Contribs. check for English Heritage Building Materials Thesaurus took 0.5201694965362549s
Interlinking | sameAs chians check for English Heritage Building Materials Thesaurus took 0.40810227394104004s
Interlinking | skos check for English Heritage Building Materials Thesaurus took 0.4364159107208252s
Interlinking | skos check for English Heritage Building Materials Thesaurus took 0.5146691799163818s
Timeliness | dataset update frequency check for English Heritage Building Materials Thesaurus took 0.47701025009155273s
Currency | Creation date check for English Heritage Building Materials Thesaurus took 0.9904012680053711s
Currency | Modification date check for English Heritage Building Materials Thesaurus took 0.8007919788360596s
Rep.Conc. | URIs length for English Heritage Building Materials Thesaurus took 0.810556173324585s
Interoperability | New vocabularies check for English Heritage Building Materials Thesaurus took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Building Materials Thesaurus took 0.4732189178466797s
Accuracy | Check Functional Property for English Heritage Building Materials Thesaurus took 0.41712427139282227s
Accuracy | Check Inverse Functional Property for English Heritage Building Materials Thesaurus took 0.41521525382995605s
Consistency | Disjoint class check for English Heritage Building Materials Thesaurus took 0.3412656784057617s
Consistency | Check Ontology hijacking for English Heritage Building Materials Thesaurus took 0.3932313919067383s
Consistency | Check Invalid usage of undefined properties for English Heritage Building Materials Thesaurus took 1.7029473781585693s
Conciseness | Check Extensional conciseness for English Heritage Building Materials Thesaurus took 0.00014472007751464844s
Security | Sign check for English Heritage Building Materials Thesaurus took 0.4632091522216797s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.41765379905700684s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.01921844482421875s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0005438327789306641s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 2.0503997802734375e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Building Materials Thesaurus took 1.430511474609375e-06s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 1.1444091796875e-05s
INFO | --- Analysis for English Heritage Building Materials Thesaurus took 70.82482242584229s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 0.3589468002319336s
Availability | VoID file availability check for English Heritage Components Thesaurus took 1.1205673217773438e-05s
Extra | Recovery of all triples for English Heritage Components Thesaurus took 0.39266395568847656s
Performance | Total latancy measurement for English Heritage Components Thesaurus took 2.095308542251587s
Amount of data | Number of triples check for English Heritage Components Thesaurus took 0.6476244926452637s
Versatility | Languages check for English Heritage Components Thesaurus took 0.31282639503479004s
Interpretability | Number of blank nodes check for English Heritage Components Thesaurus took 0.6675474643707275s
Security | Check HTTPS for English Heritage Components Thesaurus took 0.3206307888031006s
Interpretability | RDF structures check for English Heritage Components Thesaurus took 0.34822940826416016s
Versatility | Serialization formats check for English Heritage Components Thesaurus took 0.44431591033935547s
Availability | RDF dump link check for English Heritage Components Thesaurus took 0.3569602966308594s
License | MR license check for English Heritage Components Thesaurus took 0.5684309005737305s
License | HR license check for English Heritage Components Thesaurus took 0.4746894836425781s
Amount of data | Number of property check for English Heritage Components Thesaurus took 0.5601060390472412s
Understandability | Number of label check for English Heritage Components Thesaurus took 0.7443177700042725s
Understandability | URI regex check for English Heritage Components Thesaurus took 0.9572129249572754s
Understandability | Vocabs check for English Heritage Components Thesaurus took 0.45883846282958984s
Verifiability | Authors check for English Heritage Components Thesaurus took 0.4796264171600342s
Verifiability | Publishers check for English Heritage Components Thesaurus took 0.502169132232666s
Performance | Throughput check for English Heritage Components Thesaurus took 12.515784502029419s
Amount of data | Check the number of entities for English Heritage Components Thesaurus took 8.20159912109375e-05s
Verifiability | Contribs. check for English Heritage Components Thesaurus took 0.5237760543823242s
Interlinking | sameAs chians check for English Heritage Components Thesaurus took 0.6343350410461426s
Interlinking | skos check for English Heritage Components Thesaurus took 0.4844355583190918s
Interlinking | skos check for English Heritage Components Thesaurus took 0.5649795532226562s
Timeliness | dataset update frequency check for English Heritage Components Thesaurus took 0.5237088203430176s
Currency | Creation date check for English Heritage Components Thesaurus took 1.2449543476104736s
Currency | Modification date check for English Heritage Components Thesaurus took 0.9886147975921631s
Rep.Conc. | URIs length for English Heritage Components Thesaurus took 1.0268933773040771s
Interoperability | New vocabularies check for English Heritage Components Thesaurus took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Components Thesaurus took 0.6294479370117188s
Accuracy | Check Functional Property for English Heritage Components Thesaurus took 0.520505428314209s
Accuracy | Check Inverse Functional Property for English Heritage Components Thesaurus took 0.4940683841705322s
Consistency | Disjoint class check for English Heritage Components Thesaurus took 0.39562344551086426s
Consistency | Check Ontology hijacking for English Heritage Components Thesaurus took 0.44836854934692383s
Consistency | Check Invalid usage of undefined properties for English Heritage Components Thesaurus took 1.8207104206085205s
Conciseness | Check Extensional conciseness for English Heritage Components Thesaurus took 0.0001468658447265625s
Security | Sign check for English Heritage Components Thesaurus took 0.48354172706604004s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.4681816101074219s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.02097010612487793s
Interlinking | Calculation of Degree of Connection for English Heritage Components Thesaurus took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for English Heritage Components Thesaurus took 0.0005512237548828125s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 1.430511474609375e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Components Thesaurus took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for English Heritage Components Thesaurus took 77.28857707977295s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 0.510869026184082s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 5.245208740234375e-06s
Extra | Recovery of all triples for English Heritage Event Types Thesaurus took 0.37102627754211426s
Performance | Total latancy measurement for English Heritage Event Types Thesaurus took 2.1593563556671143s
Amount of data | Number of triples check for English Heritage Event Types Thesaurus took 0.6520967483520508s
Versatility | Languages check for English Heritage Event Types Thesaurus took 0.2927546501159668s
Interpretability | Number of blank nodes check for English Heritage Event Types Thesaurus took 0.7792553901672363s
Security | Check HTTPS for English Heritage Event Types Thesaurus took 0.3037569522857666s
Interpretability | RDF structures check for English Heritage Event Types Thesaurus took 0.3385908603668213s
Versatility | Serialization formats check for English Heritage Event Types Thesaurus took 0.4347262382507324s
Availability | RDF dump link check for English Heritage Event Types Thesaurus took 0.3825376033782959s
License | MR license check for English Heritage Event Types Thesaurus took 0.6955757141113281s
License | HR license check for English Heritage Event Types Thesaurus took 0.5127151012420654s
Amount of data | Number of property check for English Heritage Event Types Thesaurus took 0.6613502502441406s
Understandability | Number of label check for English Heritage Event Types Thesaurus took 0.8781533241271973s
Understandability | URI regex check for English Heritage Event Types Thesaurus took 0.8895299434661865s
Understandability | Vocabs check for English Heritage Event Types Thesaurus took 0.4217865467071533s
Verifiability | Authors check for English Heritage Event Types Thesaurus took 0.40149474143981934s
Verifiability | Publishers check for English Heritage Event Types Thesaurus took 0.6433408260345459s
Performance | Throughput check for English Heritage Event Types Thesaurus took 12.179473638534546s
Amount of data | Check the number of entities for English Heritage Event Types Thesaurus took 9.751319885253906e-05s
Verifiability | Contribs. check for English Heritage Event Types Thesaurus took 0.448439359664917s
Interlinking | sameAs chians check for English Heritage Event Types Thesaurus took 0.43237876892089844s
Interlinking | skos check for English Heritage Event Types Thesaurus took 0.4397554397583008s
Interlinking | skos check for English Heritage Event Types Thesaurus took 0.49555206298828125s
Timeliness | dataset update frequency check for English Heritage Event Types Thesaurus took 0.4873199462890625s
Currency | Creation date check for English Heritage Event Types Thesaurus took 0.9256558418273926s
Currency | Modification date check for English Heritage Event Types Thesaurus took 0.8352615833282471s
Rep.Conc. | URIs length for English Heritage Event Types Thesaurus took 1.026564359664917s
Interoperability | New vocabularies check for English Heritage Event Types Thesaurus took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Event Types Thesaurus took 0.6572737693786621s
Accuracy | Check Functional Property for English Heritage Event Types Thesaurus took 0.517951488494873s
Accuracy | Check Inverse Functional Property for English Heritage Event Types Thesaurus took 0.5116753578186035s
Consistency | Disjoint class check for English Heritage Event Types Thesaurus took 0.5174582004547119s
Consistency | Check Ontology hijacking for English Heritage Event Types Thesaurus took 0.4247558116912842s
Consistency | Check Invalid usage of undefined properties for English Heritage Event Types Thesaurus took 1.8343591690063477s
Conciseness | Check Extensional conciseness for English Heritage Event Types Thesaurus took 0.0001404285430908203s
Security | Sign check for English Heritage Event Types Thesaurus took 0.4959592819213867s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 2.651980400085449s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.01764535903930664s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0005140304565429688s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 1.2159347534179688e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Event Types Thesaurus took 9.5367431640625e-07s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 1.1444091796875e-05s
INFO | --- Analysis for English Heritage Event Types Thesaurus took 73.78939509391785s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 8.535385131835938e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 4.76837158203125e-06s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 0.5842018127441406s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.018025636672973633s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 1.239776611328125e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 1.049041748046875e-05s
INFO | --- Analysis for English Heritage Evidence Thesaurus took 4.467673063278198s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 0.4601263999938965s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 1.0251998901367188e-05s
Extra | Recovery of all triples for English Heritage Maritime Craft Thesaurus took 0.46921658515930176s
Performance | Total latancy measurement for English Heritage Maritime Craft Thesaurus took 1.958617925643921s
Amount of data | Number of triples check for English Heritage Maritime Craft Thesaurus took 0.6372959613800049s
Versatility | Languages check for English Heritage Maritime Craft Thesaurus took 0.29944539070129395s
Interpretability | Number of blank nodes check for English Heritage Maritime Craft Thesaurus took 0.6504495143890381s
Security | Check HTTPS for English Heritage Maritime Craft Thesaurus took 0.27516841888427734s
Interpretability | RDF structures check for English Heritage Maritime Craft Thesaurus took 0.33672666549682617s
Versatility | Serialization formats check for English Heritage Maritime Craft Thesaurus took 0.4080824851989746s
Availability | RDF dump link check for English Heritage Maritime Craft Thesaurus took 0.3987133502960205s
License | MR license check for English Heritage Maritime Craft Thesaurus took 0.7030558586120605s
License | HR license check for English Heritage Maritime Craft Thesaurus took 0.4140286445617676s
Amount of data | Number of property check for English Heritage Maritime Craft Thesaurus took 0.4745023250579834s
Understandability | Number of label check for English Heritage Maritime Craft Thesaurus took 0.6135587692260742s
Understandability | URI regex check for English Heritage Maritime Craft Thesaurus took 0.7899234294891357s
Understandability | Vocabs check for English Heritage Maritime Craft Thesaurus took 0.5016396045684814s
Verifiability | Authors check for English Heritage Maritime Craft Thesaurus took 0.44142770767211914s
Verifiability | Publishers check for English Heritage Maritime Craft Thesaurus took 2.913407564163208s
Performance | Throughput check for English Heritage Maritime Craft Thesaurus took 12.21215009689331s
Amount of data | Check the number of entities for English Heritage Maritime Craft Thesaurus took 8.58306884765625e-05s
Verifiability | Contribs. check for English Heritage Maritime Craft Thesaurus took 0.4017467498779297s
Interlinking | sameAs chians check for English Heritage Maritime Craft Thesaurus took 0.46689295768737793s
Interlinking | skos check for English Heritage Maritime Craft Thesaurus took 1.0696008205413818s
Interlinking | skos check for English Heritage Maritime Craft Thesaurus took 4.928988456726074s
Timeliness | dataset update frequency check for English Heritage Maritime Craft Thesaurus took 0.4534118175506592s
Currency | Creation date check for English Heritage Maritime Craft Thesaurus took 1.4725444316864014s
Currency | Modification date check for English Heritage Maritime Craft Thesaurus took 0.8139588832855225s
Rep.Conc. | URIs length for English Heritage Maritime Craft Thesaurus took 1.0224230289459229s
Interoperability | New vocabularies check for English Heritage Maritime Craft Thesaurus took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Maritime Craft Thesaurus took 0.5901970863342285s
Accuracy | Check Functional Property for English Heritage Maritime Craft Thesaurus took 0.51112961769104s
Accuracy | Check Inverse Functional Property for English Heritage Maritime Craft Thesaurus took 0.5076098442077637s
Consistency | Disjoint class check for English Heritage Maritime Craft Thesaurus took 0.37187767028808594s
Consistency | Check Ontology hijacking for English Heritage Maritime Craft Thesaurus took 0.38399219512939453s
Consistency | Check Invalid usage of undefined properties for English Heritage Maritime Craft Thesaurus took 1.725942611694336s
Conciseness | Check Extensional conciseness for English Heritage Maritime Craft Thesaurus took 0.00014138221740722656s
Security | Sign check for English Heritage Maritime Craft Thesaurus took 0.513796329498291s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.5008847713470459s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.01980304718017578s
Interlinking | Calculation of Degree of Connection for English Heritage Maritime Craft Thesaurus took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for English Heritage Maritime Craft Thesaurus took 0.0005116462707519531s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 1.3113021850585938e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Maritime Craft Thesaurus took 1.430511474609375e-06s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for English Heritage Maritime Craft Thesaurus took 79.83693218231201s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 0.4450843334197998s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 1.0013580322265625e-05s
Extra | Recovery of all triples for English Heritage Monument Types Thesaurus took 0.43999338150024414s
Performance | Total latancy measurement for English Heritage Monument Types Thesaurus took 2.0418434143066406s
Amount of data | Number of triples check for English Heritage Monument Types Thesaurus took 0.5753734111785889s
Versatility | Languages check for English Heritage Monument Types Thesaurus took 0.30095934867858887s
Interpretability | Number of blank nodes check for English Heritage Monument Types Thesaurus took 0.5117030143737793s
Security | Check HTTPS for English Heritage Monument Types Thesaurus took 0.29050707817077637s
Interpretability | RDF structures check for English Heritage Monument Types Thesaurus took 0.3360583782196045s
Versatility | Serialization formats check for English Heritage Monument Types Thesaurus took 0.4285740852355957s
Availability | RDF dump link check for English Heritage Monument Types Thesaurus took 0.34342312812805176s
License | MR license check for English Heritage Monument Types Thesaurus took 0.6675739288330078s
License | HR license check for English Heritage Monument Types Thesaurus took 0.48953700065612793s
Amount of data | Number of property check for English Heritage Monument Types Thesaurus took 0.5555598735809326s
Understandability | Number of label check for English Heritage Monument Types Thesaurus took 0.628347635269165s
Understandability | URI regex check for English Heritage Monument Types Thesaurus took 0.9033868312835693s
Understandability | Vocabs check for English Heritage Monument Types Thesaurus took 0.45002126693725586s
Verifiability | Authors check for English Heritage Monument Types Thesaurus took 0.46939778327941895s
Verifiability | Publishers check for English Heritage Monument Types Thesaurus took 0.48917484283447266s
Performance | Throughput check for English Heritage Monument Types Thesaurus took 12.160907983779907s
Amount of data | Check the number of entities for English Heritage Monument Types Thesaurus took 8.416175842285156e-05s
Verifiability | Contribs. check for English Heritage Monument Types Thesaurus took 0.459946870803833s
Interlinking | sameAs chians check for English Heritage Monument Types Thesaurus took 0.4734196662902832s
Interlinking | skos check for English Heritage Monument Types Thesaurus took 0.5210509300231934s
Interlinking | skos check for English Heritage Monument Types Thesaurus took 0.6104412078857422s
Timeliness | dataset update frequency check for English Heritage Monument Types Thesaurus took 0.5113060474395752s
Currency | Creation date check for English Heritage Monument Types Thesaurus took 1.0489895343780518s
Currency | Modification date check for English Heritage Monument Types Thesaurus took 1.0461647510528564s
Rep.Conc. | URIs length for English Heritage Monument Types Thesaurus took 1.1432616710662842s
Interoperability | New vocabularies check for English Heritage Monument Types Thesaurus took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Monument Types Thesaurus took 0.6939761638641357s
Accuracy | Check Functional Property for English Heritage Monument Types Thesaurus took 0.5838906764984131s
Accuracy | Check Inverse Functional Property for English Heritage Monument Types Thesaurus took 0.5455341339111328s
Consistency | Disjoint class check for English Heritage Monument Types Thesaurus took 0.48368358612060547s
Consistency | Check Ontology hijacking for English Heritage Monument Types Thesaurus took 0.5280919075012207s
Consistency | Check Invalid usage of undefined properties for English Heritage Monument Types Thesaurus took 1.8905911445617676s
Conciseness | Check Extensional conciseness for English Heritage Monument Types Thesaurus took 0.0001399517059326172s
Security | Sign check for English Heritage Monument Types Thesaurus took 0.5973150730133057s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.38509106636047363s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.01786947250366211s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0005042552947998047s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 1.2874603271484375e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Monument Types Thesaurus took 1.430511474609375e-06s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 1.1444091796875e-05s
INFO | --- Analysis for English Heritage Monument Types Thesaurus took 78.04509472846985s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.38192009925842285s
Availability | VoID file availability check for English Heritage Periods List took 1.6502315998077393s
Extra | Recovery of all triples for English Heritage Periods List took 0.46303653717041016s
Performance | Total latancy measurement for English Heritage Periods List took 2.211228132247925s
Amount of data | Number of triples check for English Heritage Periods List took 0.537539005279541s
Versatility | Languages check for English Heritage Periods List took 0.31836628913879395s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.5910608768463135s
Security | Check HTTPS for English Heritage Periods List took 0.36554455757141113s
Interpretability | RDF structures check for English Heritage Periods List took 0.29841065406799316s
Versatility | Serialization formats check for English Heritage Periods List took 0.3993492126464844s
Availability | RDF dump link check for English Heritage Periods List took 0.44294285774230957s
License | MR license check for English Heritage Periods List took 0.6589145660400391s
License | HR license check for English Heritage Periods List took 0.47448182106018066s
Amount of data | Number of property check for English Heritage Periods List took 0.5625452995300293s
Understandability | Number of label check for English Heritage Periods List took 0.6965463161468506s
Understandability | URI regex check for English Heritage Periods List took 0.797936201095581s
Understandability | Vocabs check for English Heritage Periods List took 0.38101768493652344s
Verifiability | Authors check for English Heritage Periods List took 0.570326566696167s
Verifiability | Publishers check for English Heritage Periods List took 0.47891879081726074s
Performance | Throughput check for English Heritage Periods List took 11.781310796737671s
Amount of data | Check the number of entities for English Heritage Periods List took 8.463859558105469e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.4072391986846924s
Interlinking | sameAs chians check for English Heritage Periods List took 0.3931131362915039s
Interlinking | skos check for English Heritage Periods List took 0.5093247890472412s
Interlinking | skos check for English Heritage Periods List took 0.44904494285583496s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.4285008907318115s
Currency | Creation date check for English Heritage Periods List took 0.9089341163635254s
Currency | Modification date check for English Heritage Periods List took 0.775108814239502s
Rep.Conc. | URIs length for English Heritage Periods List took 0.9246096611022949s
Interoperability | New vocabularies check for English Heritage Periods List took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.5749273300170898s
Accuracy | Check Functional Property for English Heritage Periods List took 0.46415281295776367s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.5514178276062012s
Consistency | Disjoint class check for English Heritage Periods List took 0.5988659858703613s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.5408687591552734s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.8565936088562012s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.00015425682067871094s
Security | Sign check for English Heritage Periods List took 0.5808694362640381s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.3335757255554199s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.0185244083404541s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0005371570587158203s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 4.4345855712890625e-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 1.1444091796875e-05s
INFO | --- Analysis for English Heritage Periods List took 62.61703562736511s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.43121886253356934s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.6319234371185303s
Extra | Recovery of all triples for English Index of Multiple Deprivation Ranking 2010 took 1.2616562843322754s
Performance | Total latancy measurement for English Index of Multiple Deprivation Ranking 2010 took 0.895963191986084s
Amount of data | Number of triples check for English Index of Multiple Deprivation Ranking 2010 took 0.2504231929779053s
Interoperability | New terms check for English Index of Multiple Deprivation Ranking 2010 took 1.666100263595581s
Versatility | Languages check for English Index of Multiple Deprivation Ranking 2010 took 0.6349477767944336s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Ranking 2010 took 0.23163318634033203s
Security | Check HTTPS for English Index of Multiple Deprivation Ranking 2010 took 0.20742440223693848s
Interpretability | RDF structures check for English Index of Multiple Deprivation Ranking 2010 took 0.23435592651367188s
Versatility | Serialization formats check for English Index of Multiple Deprivation Ranking 2010 took 0.3050825595855713s
Availability | RDF dump link check for English Index of Multiple Deprivation Ranking 2010 took 60.81022334098816s
License | MR license check for English Index of Multiple Deprivation Ranking 2010 took 0.25174546241760254s
License | HR license check for English Index of Multiple Deprivation Ranking 2010 took 30.154261589050293s
Amount of data | Number of property check for English Index of Multiple Deprivation Ranking 2010 took 0.21533894538879395s
Understandability | Number of label check for English Index of Multiple Deprivation Ranking 2010 took 0.37628960609436035s
Understandability | URI regex check for English Index of Multiple Deprivation Ranking 2010 took 0.6469581127166748s
Understandability | Vocabs check for English Index of Multiple Deprivation Ranking 2010 took 0.2505519390106201s
Verifiability | Authors check for English Index of Multiple Deprivation Ranking 2010 took 0.28209948539733887s
Verifiability | Publishers check for English Index of Multiple Deprivation Ranking 2010 took 0.36869311332702637s
Performance | Throughput check for English Index of Multiple Deprivation Ranking 2010 took 11.432991027832031s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Ranking 2010 took 8.821487426757812e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Ranking 2010 took 0.23631000518798828s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Ranking 2010 took 0.29944491386413574s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.23241424560546875s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.21912121772766113s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Ranking 2010 took 0.3946971893310547s
Currency | Creation date check for English Index of Multiple Deprivation Ranking 2010 took 0.17690277099609375s
Currency | Modification date check for English Index of Multiple Deprivation Ranking 2010 took 0.5596349239349365s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Ranking 2010 took 2.4663217067718506s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Ranking 2010 took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Ranking 2010 took 0.452364444732666s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.3959474563598633s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.5539073944091797s
Consistency | Disjoint class check for English Index of Multiple Deprivation Ranking 2010 took 0.9929344654083252s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Ranking 2010 took 2.97571063041687s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Ranking 2010 took 4.206529140472412s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Ranking 2010 took 2.87854266166687s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.00014925003051757812s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 1.3393409252166748s
Security | Sign check for English Index of Multiple Deprivation Ranking 2010 took 1.8993217945098877s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 1.2923192977905273s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.023984193801879883s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 6.151199340820312e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0005216598510742188s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 8.96453857421875e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Ranking 2010 took 1.6689300537109375e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 9.298324584960938e-06s
INFO | --- Analysis for English Index of Multiple Deprivation Ranking 2010 took 992.8075940608978s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.18553423881530762s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.5568962097167969s
Extra | Recovery of all triples for English Index of Multiple Deprivation Score 2010 took 1.2295951843261719s
Performance | Total latancy measurement for English Index of Multiple Deprivation Score 2010 took 0.9257042407989502s
Amount of data | Number of triples check for English Index of Multiple Deprivation Score 2010 took 0.14484047889709473s
Interoperability | New terms check for English Index of Multiple Deprivation Score 2010 took 1.6495835781097412s
Versatility | Languages check for English Index of Multiple Deprivation Score 2010 took 0.4898815155029297s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Score 2010 took 0.2850630283355713s
Security | Check HTTPS for English Index of Multiple Deprivation Score 2010 took 0.15872550010681152s
Interpretability | RDF structures check for English Index of Multiple Deprivation Score 2010 took 0.3171114921569824s
Versatility | Serialization formats check for English Index of Multiple Deprivation Score 2010 took 0.16739273071289062s
Availability | RDF dump link check for English Index of Multiple Deprivation Score 2010 took 52.65830588340759s
License | MR license check for English Index of Multiple Deprivation Score 2010 took 0.22863435745239258s
License | HR license check for English Index of Multiple Deprivation Score 2010 took 30.177010774612427s
Amount of data | Number of property check for English Index of Multiple Deprivation Score 2010 took 0.21301817893981934s
Understandability | Number of label check for English Index of Multiple Deprivation Score 2010 took 0.16499805450439453s
Understandability | URI regex check for English Index of Multiple Deprivation Score 2010 took 0.40433573722839355s
Understandability | Vocabs check for English Index of Multiple Deprivation Score 2010 took 0.22221088409423828s
Verifiability | Authors check for English Index of Multiple Deprivation Score 2010 took 0.15303564071655273s
Verifiability | Publishers check for English Index of Multiple Deprivation Score 2010 took 0.1489849090576172s
Performance | Throughput check for English Index of Multiple Deprivation Score 2010 took 11.476667165756226s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Score 2010 took 9.679794311523438e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Score 2010 took 0.14293408393859863s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Score 2010 took 0.11843585968017578s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.14725112915039062s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.16514968872070312s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Score 2010 took 0.17187952995300293s
Currency | Creation date check for English Index of Multiple Deprivation Score 2010 took 0.17604804039001465s
Currency | Modification date check for English Index of Multiple Deprivation Score 2010 took 0.4601929187774658s
