Availability | SPARQL endpoint availability check for Open Data Web took 6.175041198730469e-05s
Availability | VoID file availability check for Open Data Web took 4.0531158447265625e-06s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.8164710998535156s
Reputation | Calculation of the PageRank for Open Data Web took 1.7702035903930664s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0006220340728759766s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 0.00021696090698242188s
Believability | Calculation of trust value for Open Data Web took 1.0967254638671875e-05s
INFO | --- Analysis for Open Data Web took 8.237032413482666s
Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 5.4836273193359375e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.2957444190979004s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.3805363178253174s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.017984867095947266s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0005948543548583984s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 1.2874603271484375e-05s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 1.2159347534179688e-05s
INFO | --- Analysis for Korespondencja Emila Szramka z Janem Kuderą took 3.9316177368164062s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 2.790390968322754s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 1.4035274982452393s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.7138099670410156s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.018608570098876953s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0006103515625s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 0.00019550323486328125s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 8.106231689453125e-06s
INFO | --- Analysis for 2000 U.S. Census in RDF (rdfabout.com) took 11.272992610931396s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 0.9788498878479004s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.6988494396209717s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.3849351406097412s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.017949342727661133s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0006000995635986328s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 4.2438507080078125e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 5.7220458984375e-06s
INFO | --- Analysis for 2001 Spanish Census to RDF took 5.856099843978882s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.410743713378906e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 5.245208740234375e-06s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.6173462867736816s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.017633914947509766s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0006422996520996094s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 1.430511474609375e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 8.58306884765625e-06s
INFO | --- Analysis for A collection of Papers for LREC2014 and related Workshops took 5.293173313140869s
Availability | SPARQL endpoint availability check for Test took 4.482269287109375e-05s
Availability | VoID file availability check for Test took 0.37817811965942383s
Completeness | Calculation of interlinking completeness for Test took 0.3746621608734131s
Reputation | Calculation of the PageRank for Test took 0.017968416213989258s
Interlinking | Calculation of Degree of Connection for Test took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Test took 0.0006084442138671875s
Interlinking | Calculation of Clustering coefficient for Test took 1.1920928955078125e-05s
Believability | Calculation of trust value for Test took 9.059906005859375e-06s
INFO | --- Analysis for Test took 3.0740556716918945s
Availability | SPARQL endpoint availability check for my intro took 7.677078247070312e-05s
Availability | VoID file availability check for my intro took 4.0531158447265625e-06s
Completeness | Calculation of interlinking completeness for my intro took 0.3874990940093994s
Reputation | Calculation of the PageRank for my intro took 0.01756906509399414s
Interlinking | Calculation of Degree of Connection for my intro took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for my intro took 0.0006203651428222656s
Interlinking | Calculation of Clustering coefficient for my intro took 1.2636184692382812e-05s
Believability | Calculation of trust value for my intro took 1.239776611328125e-05s
INFO | --- Analysis for my intro took 2.2336134910583496s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.2007913589477539s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 8.106231689453125e-06s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.4311535358428955s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.017487287521362305s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0005939006805419922s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00011777877807617188s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 8.821487426757812e-06s
INFO | --- Analysis for Australian Bureau of Statistics (ABS) Linked Data took 2.3477365970611572s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 262.0974016189575s
Availability | VoID file availability check for Academic Offer of UNL took 1.52587890625e-05s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.39937496185302734s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.05946612358093262s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0006482601165771484s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 2.4318695068359375e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 1.3113021850585938e-05s
INFO | --- Analysis for Academic Offer of UNL took 396.85347986221313s
Availability | SPARQL endpoint availability check for AcadOnto took 4.4345855712890625e-05s
Availability | VoID file availability check for AcadOnto took 5.7220458984375e-06s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.5399527549743652s
Reputation | Calculation of the PageRank for AcadOnto took 0.017900943756103516s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0005841255187988281s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 1.1920928955078125e-05s
Believability | Calculation of trust value for AcadOnto took 1.3589859008789062e-05s
INFO | --- Analysis for AcadOnto took 6.739125728607178s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 15.398131608963013s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 5.345019102096558s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.2488994598388672s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.01761007308959961s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0005846023559570312s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.910064697265625e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 8.821487426757812e-06s
INFO | --- Analysis for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 58.280781984329224s
Availability | SPARQL endpoint availability check for Addgene took 8.654594421386719e-05s
Availability | VoID file availability check for Addgene took 1.4409723281860352s
Completeness | Calculation of interlinking completeness for Addgene took 0.35563111305236816s
Reputation | Calculation of the PageRank for Addgene took 0.017951488494873047s
Interlinking | Calculation of Degree of Connection for Addgene took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Addgene took 0.0005862712860107422s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.552436828613281e-05s
Believability | Calculation of trust value for Addgene took 1.2636184692382812e-05s
INFO | --- Analysis for Addgene took 18.398689031600952s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 0.00012826919555664062s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 2.1881632804870605s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.9286656379699707s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.01766371726989746s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.00060272216796875s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.059906005859375e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.2874603271484375e-05s
INFO | --- Analysis for AEGP, Spanish Textile and Clothing Association took 13.624128818511963s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.3582172393798828s
Availability | VoID file availability check for AEMET metereological dataset took 0.18567371368408203s
Extra | Recovery of all triples for AEMET metereological dataset took 4.4691481590271s
Performance | Total latancy measurement for AEMET metereological dataset took 0.6546261310577393s
Amount of data | Number of triples check for AEMET metereological dataset took 10.850363492965698s
Interoperability | New terms check for AEMET metereological dataset took 9.334185361862183s
Versatility | Languages check for AEMET metereological dataset took 0.4501769542694092s
Interpretability | Number of blank nodes check for AEMET metereological dataset took 4.549938917160034s
Interpretability | RDF structures check for AEMET metereological dataset took 0.21775054931640625s
Versatility | Serialization formats check for AEMET metereological dataset took 0.18461203575134277s
Availability | RDF dump link check for AEMET metereological dataset took 0.1093447208404541s
License | MR license check for AEMET metereological dataset took 0.18067169189453125s
License | HR license check for AEMET metereological dataset took 64.31067776679993s
Amount of data | Number of property check for AEMET metereological dataset took 0.2058260440826416s
Understandability | Number of label check for AEMET metereological dataset took 64.41693329811096s
Understandability | URI regex check for AEMET metereological dataset took 0.21189045906066895s
Understandability | Vocabs check for AEMET metereological dataset took 0.10837268829345703s
Verifiability | Authors check for AEMET metereological dataset took 0.1859724521636963s
Verifiability | Publishers check for AEMET metereological dataset took 0.11574792861938477s
Performance | Throughput check for AEMET metereological dataset took 11.847398281097412s
Amount of data | Check the number of entities for AEMET metereological dataset took 0.00010085105895996094s
Verifiability | Contribs. check for AEMET metereological dataset took 0.10786604881286621s
Interlinking | sameAs chians check for AEMET metereological dataset took 0.17567038536071777s
Interlinking | skos check for AEMET metereological dataset took 0.11122298240661621s
Interlinking | skos check for AEMET metereological dataset took 0.1009063720703125s
Timeliness | dataset update frequency check for AEMET metereological dataset took 0.11171722412109375s
Currency | Creation date check for AEMET metereological dataset took 0.18035435676574707s
Currency | Modification date check for AEMET metereological dataset took 0.18384075164794922s
Rep.Conc. | URIs length for AEMET metereological dataset took 68.10596752166748s
Interoperability | New vocabularies check for AEMET metereological dataset took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for AEMET metereological dataset took 0.18446683883666992s
Accuracy | Check Functional Property for AEMET metereological dataset took 0.18010163307189941s
Accuracy | Check Inverse Functional Property for AEMET metereological dataset took 0.10797595977783203s
Accuracy | Check Empty annotation labels for AEMET metereological dataset took 1.357924222946167s
Accuracy | Check White space in annotation for AEMET metereological dataset took 0.03623509407043457s
Accuracy | Check Datatype consistency for AEMET metereological dataset took 0.0282132625579834s
Consistency | Disjoint class check for AEMET metereological dataset took 0.1780407428741455s
Consistency | Check Misplaced properties for AEMET metereological dataset took 60.08534097671509s
Consistency | Misplaced classes for AEMET metereological dataset took 0.2689518928527832s
Consistency | Check Ontology hijacking for AEMET metereological dataset took 2.697983503341675s
Consistency | Check Invalid usage of undefined classes for AEMET metereological dataset took 1.3729162216186523s
Consistency | Check Invalid usage of undefined properties for AEMET metereological dataset took 60.37058687210083s
Conciseness | Check Extensional conciseness for AEMET metereological dataset took 0.056999921798706055s
Conciseness | Check Intensional conciseness for AEMET metereological dataset took 0.1885387897491455s
Security | Sign check for AEMET metereological dataset took 0.11624693870544434s
Availability | Check URIs Dereferenciability for AEMET metereological dataset took 4.045720815658569s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.7600643634796143s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.01790642738342285s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0006244182586669922s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 4.506111145019531e-05s
Interoperability | Check the re-using of existing vocabs for AEMET metereological dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for AEMET metereological dataset took 1.4066696166992188e-05s
INFO | --- Analysis for AEMET metereological dataset took 429.06160283088684s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 5.888938903808594e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 4.76837158203125e-06s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 2.7098827362060547s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.02015542984008789s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0006167888641357422s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 1.4066696166992188e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 1.4066696166992188e-05s
INFO | --- Analysis for Agenda de Zaragoza took 7.3643879890441895s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.05031704902648926s
Availability | VoID file availability check for AgriNepalData took 7.867813110351562e-06s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.3832104206085205s
Reputation | Calculation of the PageRank for AgriNepalData took 0.017472505569458008s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0006053447723388672s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 7.128715515136719e-05s
Believability | Calculation of trust value for AgriNepalData took 1.1444091796875e-05s
INFO | --- Analysis for AgriNepalData took 2.699099063873291s
Availability | SPARQL endpoint availability check for AGRIS took 263.3256051540375s
Availability | VoID file availability check for AGRIS took 0.3423948287963867s
Completeness | Calculation of interlinking completeness for AGRIS took 0.4351646900177002s
Reputation | Calculation of the PageRank for AGRIS took 0.018390655517578125s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0006337165832519531s
Interlinking | Calculation of Clustering coefficient for AGRIS took 8.273124694824219e-05s
Believability | Calculation of trust value for AGRIS took 1.049041748046875e-05s
INFO | --- Analysis for AGRIS took 415.764524936676s
Availability | SPARQL endpoint availability check for AGROVOC took 0.1262218952178955s
Availability | VoID file availability check for AGROVOC took 0.9630138874053955s
Extra | Recovery of all triples for AGROVOC took 20.26330256462097s
Performance | Total latancy measurement for AGROVOC took 0.31976938247680664s
Amount of data | Number of triples check for AGROVOC took 14.47693657875061s
Interoperability | New terms check for AGROVOC took 3.469111919403076s
Versatility | Languages check for AGROVOC took 45.06021761894226s
Interpretability | Number of blank nodes check for AGROVOC took 13.192302703857422s
Interpretability | RDF structures check for AGROVOC took 0.06363105773925781s
Versatility | Serialization formats check for AGROVOC took 0.05702710151672363s
Availability | RDF dump link check for AGROVOC took 0.03440284729003906s
License | MR license check for AGROVOC took 0.07477807998657227s
License | HR license check for AGROVOC took 0.5852277278900146s
Amount of data | Number of property check for AGROVOC took 0.05971384048461914s
Understandability | Number of label check for AGROVOC took 22.306875705718994s
Understandability | URI regex check for AGROVOC took 0.15993833541870117s
Understandability | Vocabs check for AGROVOC took 0.05459189414978027s
Verifiability | Authors check for AGROVOC took 0.08938980102539062s
Verifiability | Publishers check for AGROVOC took 0.11959242820739746s
Performance | Throughput check for AGROVOC took 10.750067234039307s
Amount of data | Check the number of entities for AGROVOC took 0.00011229515075683594s
Verifiability | Contribs. check for AGROVOC took 0.1351308822631836s
Interlinking | sameAs chians check for AGROVOC took 0.03476238250732422s
Interlinking | skos check for AGROVOC took 0.3767397403717041s
Interlinking | skos check for AGROVOC took 0.31470227241516113s
Timeliness | dataset update frequency check for AGROVOC took 0.25847339630126953s
Currency | Creation date check for AGROVOC took 3.929918050765991s
Currency | Modification date check for AGROVOC took 1.0880017280578613s
Rep.Conc. | URIs length for AGROVOC took 48.19981360435486s
Interoperability | New vocabularies check for AGROVOC took 1.33514404296875e-05s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.05757498741149902s
Accuracy | Check Functional Property for AGROVOC took 0.07029223442077637s
Accuracy | Check Inverse Functional Property for AGROVOC took 0.08980941772460938s
Accuracy | Check Empty annotation labels for AGROVOC took 15.89933729171753s
Accuracy | Check White space in annotation for AGROVOC took 3.005261182785034s
Accuracy | Check Datatype consistency for AGROVOC took 4.580345153808594s
Consistency | Disjoint class check for AGROVOC took 0.033100128173828125s
Consistency | Check Misplaced properties for AGROVOC took 16.57905149459839s
Consistency | Check Ontology hijacking for AGROVOC took 15.710661888122559s
Consistency | Check Invalid usage of undefined classes for AGROVOC took 1.5049118995666504s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 18.80885148048401s
Conciseness | Check Extensional conciseness for AGROVOC took 2.5716686248779297s
Conciseness | Check Intensional conciseness for AGROVOC took 0.07621884346008301s
Security | Sign check for AGROVOC took 0.03249216079711914s
Availability | Check URIs Dereferenciability for AGROVOC took 6.223360776901245s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.6999571323394775s
Reputation | Calculation of the PageRank for AGROVOC took 0.017737627029418945s
Interlinking | Calculation of Degree of Connection for AGROVOC took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for AGROVOC took 0.0005850791931152344s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00010943412780761719s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.430511474609375e-06s
Believability | Calculation of trust value for AGROVOC took 1.2159347534179688e-05s
INFO | --- Analysis for AGROVOC took 605.8027226924896s
Availability | SPARQL endpoint availability check for AGROVOC took 0.00010657310485839844s
Availability | VoID file availability check for AGROVOC took 5.4836273193359375e-06s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.7854034900665283s
Reputation | Calculation of the PageRank for AGROVOC took 0.020807743072509766s
Interlinking | Calculation of Degree of Connection for AGROVOC took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for AGROVOC took 0.0006020069122314453s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 5.91278076171875e-05s
Believability | Calculation of trust value for AGROVOC took 1.3113021850585938e-05s
INFO | --- Analysis for AGROVOC took 5.374931812286377s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 261.4606647491455s
Availability | VoID file availability check for All India Survey of Higher Education took 0.008087873458862305s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.3861978054046631s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.019912004470825195s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0005357265472412109s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 3.886222839355469e-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.69570565223694s
Availability | SPARQL endpoint availability check for  equipment ontology took 7.796287536621094e-05s
Availability | VoID file availability check for  equipment ontology took 0.2939903736114502s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.4019596576690674s
Reputation | Calculation of the PageRank for  equipment ontology took 0.017825841903686523s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0005216598510742188s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 1.0967254638671875e-05s
Believability | Calculation of trust value for  equipment ontology took 1.0967254638671875e-05s
INFO | --- Analysis for  equipment ontology took 2.5069189071655273s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 1.5723626613616943s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.8677887916564941s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.3750340938568115s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.01787543296813965s
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.0005600452423095703s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 1.1920928955078125e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 7.152557373046875e-06s
INFO | --- Analysis for aksw.org Research Group dataset took 12.14440131187439s
Availability | SPARQL endpoint availability check for AlchemyAPI took 4.7206878662109375e-05s
Availability | VoID file availability check for AlchemyAPI took 7.867813110351562e-06s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.363116979598999s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.020403146743774414s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0005581378936767578s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 2.1696090698242188e-05s
Believability | Calculation of trust value for AlchemyAPI took 1.4066696166992188e-05s
INFO | --- Analysis for AlchemyAPI took 3.22285795211792s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 393.29322242736816s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 262.1439468860626s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.4335951805114746s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.018754959106445312s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0005121231079101562s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 2.3365020751953125e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 1.0967254638671875e-05s
INFO | --- Analysis for Alexandria Digital Library (ADL) Gazetteer took 788.3708980083466s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 263.72176122665405s
Availability | VoID file availability check for aliada-scanbit-net took 1.1021063327789307s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.8834121227264404s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.019408702850341797s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.00052642822265625s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.0001201629638671875s
Believability | Calculation of trust value for aliada-scanbit-net took 1.2636184692382812e-05s
INFO | --- Analysis for aliada-scanbit-net took 1314.7875730991364s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 8.940696716308594e-05s
Availability | VoID file availability check for Allen Brain Atlas took 2.695077657699585s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.35869789123535156s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.018207311630249023s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0005333423614501953s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 1.430511474609375e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 8.106231689453125e-06s
INFO | --- Analysis for Allen Brain Atlas took 17.634697914123535s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 0.8671669960021973s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 3.6191039085388184s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 140.4177680015564s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 3.0007174015045166s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 8.516520977020264s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.537691831588745s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.08763790130615s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 3.5768840312957764s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 2.035646438598633s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.8275594711303711s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.6206960678100586s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.6307294368743896s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.6397240161895752s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 30.76503276824951s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.6356632709503174s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.8750631809234619s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.2105867862701416s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.6383578777313232s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.7365450859069824s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.6373543739318848s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 11.920412063598633s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 8.916854858398438e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.6069614887237549s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.658754825592041s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6398203372955322s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6046385765075684s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.6237010955810547s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 0.6278529167175293s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 0.7167248725891113s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 55.146910429000854s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 1.7294459342956543s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.6450800895690918s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.7551741600036621s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6765060424804688s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 36.20417046546936s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.1150166988372803s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.664278507232666s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.7172191143035889s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 9.842589616775513s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.876907348632812s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 36.04136657714844s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.3752129077911377s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 10.719587564468384s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.7373900413513184s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.9386322498321533s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.5974335670471191s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 13847.287948131561s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 1.8341124057769775s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.021655797958374023s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 5.984306335449219e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0005567073822021484s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 0.00014662742614746094s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 2.0044758319854736s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 1.2636184692382812e-05s
INFO | --- Analysis for Allie Abbreviation And Long Form Database in Life Science took 14612.470088005066s
Availability | SPARQL endpoint availability check for Alojamientos took 8.869171142578125e-05s
Availability | VoID file availability check for Alojamientos took 4.5299530029296875e-06s
Completeness | Calculation of interlinking completeness for Alojamientos took 1.8242735862731934s
Reputation | Calculation of the PageRank for Alojamientos took 0.018790721893310547s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.00052642822265625s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 1.2159347534179688e-05s
Believability | Calculation of trust value for Alojamientos took 7.62939453125e-06s
INFO | --- Analysis for Alojamientos took 6.961017370223999s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.30251216888427734s
Availability | VoID file availability check for ALPINO RDF Treebank took 7.867813110351562e-06s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.4179370403289795s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.0185396671295166s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0005204677581787109s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.695487976074219e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.1920928955078125e-05s
INFO | --- Analysis for ALPINO RDF Treebank took 5.5653886795043945s
Availability | SPARQL endpoint availability check for AAT-atawil took 8.940696716308594e-05s
Availability | VoID file availability check for AAT-atawil took 1.3972816467285156s
Completeness | Calculation of interlinking completeness for AAT-atawil took 1.7694871425628662s
Reputation | Calculation of the PageRank for AAT-atawil took 0.018070459365844727s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0005123615264892578s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 1.1920928955078125e-05s
Believability | Calculation of trust value for AAT-atawil took 1.4066696166992188e-05s
INFO | --- Analysis for AAT-atawil took 8.68893814086914s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 5.537885665893555s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.017295360565185547s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 1.4150891304016113s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.018326997756958008s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0005221366882324219s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 1.4543533325195312e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 1.2159347534179688e-05s
INFO | --- Analysis for Auckland Museum Collections Online took 10.72750735282898s
Availability | SPARQL endpoint availability check for Amer Nejma took 8.678436279296875e-05s
Availability | VoID file availability check for Amer Nejma took 6.9141387939453125e-06s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.5824427604675293s
Reputation | Calculation of the PageRank for Amer Nejma took 0.017955780029296875s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0005266666412353516s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 1.430511474609375e-05s
Believability | Calculation of trust value for Amer Nejma took 1.1920928955078125e-05s
INFO | --- Analysis for Amer Nejma took 6.470408916473389s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 9.083747863769531e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 6.67572021484375e-06s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.9901750087738037s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.018024206161499023s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0005137920379638672s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.239776611328125e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 7.518399238586426s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.8954489231109619s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.5295658111572266s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.9984867572784424s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.018440961837768555s
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.0005419254302978516s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.679794311523438e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.33514404296875e-05s
INFO | --- Analysis for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 10.197966575622559s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 8.749961853027344e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 1.1205673217773438e-05s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.4736061096191406s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.018288135528564453s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0005216598510742188s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 1.52587890625e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 1.3828277587890625e-05s
INFO | --- Analysis for Analisi del blog http://www.beppegrillo.it/ took 10.37654972076416s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 8.96453857421875e-05s
Availability | VoID file availability check for Animal Diversity Web took 1.4574966430664062s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.39795780181884766s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.017982006072998047s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0005280971527099609s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 1.2159347534179688e-05s
Believability | Calculation of trust value for Animal Diversity Web took 1.1682510375976562e-05s
INFO | --- Analysis for Animal Diversity Web took 23.85426950454712s
Availability | SPARQL endpoint availability check for apache took 9.107589721679688e-05s
Availability | VoID file availability check for apache took 4.76837158203125e-06s
Completeness | Calculation of interlinking completeness for apache took 0.4962794780731201s
Reputation | Calculation of the PageRank for apache took 0.017993927001953125s
Interlinking | Calculation of Degree of Connection for apache took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for apache took 0.0005314350128173828s
Interlinking | Calculation of Clustering coefficient for apache took 5.7697296142578125e-05s
Believability | Calculation of trust value for apache took 1.2874603271484375e-05s
INFO | --- Analysis for apache took 9.357923984527588s
Availability | SPARQL endpoint availability check for Apertium RDF took 0.5959203243255615s
Availability | VoID file availability check for Apertium RDF took 9.059906005859375e-06s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.37306785583496094s
Reputation | Calculation of the PageRank for Apertium RDF took 0.018535614013671875s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0005266666412353516s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF took 1.2159347534179688e-05s
INFO | --- Analysis for Apertium RDF took 19.352128267288208s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 0.1374659538269043s
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 293.582720041275s
Performance | Total latancy measurement for Apertium RDF CA-IT took 0.6027805805206299s
Amount of data | Number of triples check for Apertium RDF CA-IT took 2.1134588718414307s
Interoperability | New terms check for Apertium RDF CA-IT took 2.945553779602051s
Versatility | Languages check for Apertium RDF CA-IT took 47.22992253303528s
Interpretability | Number of blank nodes check for Apertium RDF CA-IT took 1.1027569770812988s
Interpretability | RDF structures check for Apertium RDF CA-IT took 0.18987512588500977s
Versatility | Serialization formats check for Apertium RDF CA-IT took 0.18100953102111816s
Availability | RDF dump link check for Apertium RDF CA-IT took 0.10844731330871582s
License | MR license check for Apertium RDF CA-IT took 0.19504928588867188s
License | HR license check for Apertium RDF CA-IT took 0.23319697380065918s
Amount of data | Number of property check for Apertium RDF CA-IT took 0.21126246452331543s
Understandability | Number of label check for Apertium RDF CA-IT took 0.23838019371032715s
Understandability | URI regex check for Apertium RDF CA-IT took 0.21020174026489258s
Understandability | Vocabs check for Apertium RDF CA-IT took 0.09946799278259277s
Verifiability | Authors check for Apertium RDF CA-IT took 0.23313522338867188s
Verifiability | Publishers check for Apertium RDF CA-IT took 0.3135688304901123s
Performance | Throughput check for Apertium RDF CA-IT took 10.829507827758789s
Amount of data | Check the number of entities for Apertium RDF CA-IT took 9.107589721679688e-05s
Verifiability | Contribs. check for Apertium RDF CA-IT took 0.1142430305480957s
Interlinking | sameAs chians check for Apertium RDF CA-IT took 0.18484950065612793s
Interlinking | skos check for Apertium RDF CA-IT took 0.19072675704956055s
Interlinking | skos check for Apertium RDF CA-IT took 0.11695003509521484s
Timeliness | dataset update frequency check for Apertium RDF CA-IT took 0.1110997200012207s
Currency | Creation date check for Apertium RDF CA-IT took 0.1823735237121582s
Currency | Modification date check for Apertium RDF CA-IT took 0.18341445922851562s
Rep.Conc. | URIs length for Apertium RDF CA-IT took 94.66009902954102s
Interoperability | New vocabularies check for Apertium RDF CA-IT took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF CA-IT took 0.1865863800048828s
Accuracy | Check Functional Property for Apertium RDF CA-IT took 0.17779302597045898s
Accuracy | Check Inverse Functional Property for Apertium RDF CA-IT took 0.10165095329284668s
Accuracy | Check Empty annotation labels for Apertium RDF CA-IT took 0.8307197093963623s
Accuracy | Check White space in annotation for Apertium RDF CA-IT took 0.010515689849853516s
Accuracy | Check Datatype consistency for Apertium RDF CA-IT took 2.6111817359924316s
Consistency | Disjoint class check for Apertium RDF CA-IT took 0.10228180885314941s
Consistency | Check Misplaced properties for Apertium RDF CA-IT took 4.795606374740601s
Consistency | Misplaced classes for Apertium RDF CA-IT took 8.29776406288147s
Consistency | Check Ontology hijacking for Apertium RDF CA-IT took 103.66689038276672s
Consistency | Check Invalid usage of undefined classes for Apertium RDF CA-IT took 1.5729451179504395s
Consistency | Check Invalid usage of undefined properties for Apertium RDF CA-IT took 5.954304456710815s
Conciseness | Check Extensional conciseness for Apertium RDF CA-IT took 2.901301860809326s
Conciseness | Check Intensional conciseness for Apertium RDF CA-IT took 0.19016790390014648s
Security | Sign check for Apertium RDF CA-IT took 0.11404013633728027s
Availability | Check URIs Dereferenciability for Apertium RDF CA-IT took 3.9911253452301025s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.46589088439941406s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.018695354461669922s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0005314350128173828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 5.221366882324219e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF CA-IT took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF CA-IT took 1.239776611328125e-05s
INFO | --- Analysis for Apertium RDF CA-IT took 679.4318056106567s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 0.10818934440612793s
Availability | VoID file availability check for Apertium RDF EN-CA took 1.1682510375976562e-05s
Extra | Recovery of all triples for Apertium RDF EN-CA took 293.2964689731598s
Performance | Total latancy measurement for Apertium RDF EN-CA took 0.6244838237762451s
Amount of data | Number of triples check for Apertium RDF EN-CA took 2.2001733779907227s
Interoperability | New terms check for Apertium RDF EN-CA took 2.782625913619995s
Versatility | Languages check for Apertium RDF EN-CA took 48.67883539199829s
Interpretability | Number of blank nodes check for Apertium RDF EN-CA took 0.985318660736084s
Interpretability | RDF structures check for Apertium RDF EN-CA took 0.20489239692687988s
Versatility | Serialization formats check for Apertium RDF EN-CA took 0.18637299537658691s
Availability | RDF dump link check for Apertium RDF EN-CA took 0.10050463676452637s
License | MR license check for Apertium RDF EN-CA took 0.1859133243560791s
License | HR license check for Apertium RDF EN-CA took 0.22807765007019043s
Amount of data | Number of property check for Apertium RDF EN-CA took 0.2103579044342041s
Understandability | Number of label check for Apertium RDF EN-CA took 0.21057367324829102s
Understandability | URI regex check for Apertium RDF EN-CA took 0.22242307662963867s
Understandability | Vocabs check for Apertium RDF EN-CA took 0.10713577270507812s
Verifiability | Authors check for Apertium RDF EN-CA took 0.24025607109069824s
Verifiability | Publishers check for Apertium RDF EN-CA took 0.17745566368103027s
Performance | Throughput check for Apertium RDF EN-CA took 15.47308349609375s
Amount of data | Check the number of entities for Apertium RDF EN-CA took 8.654594421386719e-05s
Verifiability | Contribs. check for Apertium RDF EN-CA took 0.10647416114807129s
Interlinking | sameAs chians check for Apertium RDF EN-CA took 0.1686239242553711s
Interlinking | skos check for Apertium RDF EN-CA took 0.17503595352172852s
Interlinking | skos check for Apertium RDF EN-CA took 0.11760473251342773s
Timeliness | dataset update frequency check for Apertium RDF EN-CA took 0.10052895545959473s
Currency | Creation date check for Apertium RDF EN-CA took 0.18222522735595703s
Currency | Modification date check for Apertium RDF EN-CA took 0.18202996253967285s
Rep.Conc. | URIs length for Apertium RDF EN-CA took 99.2594108581543s
Interoperability | New vocabularies check for Apertium RDF EN-CA took 1.239776611328125e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF EN-CA took 0.17885828018188477s
Accuracy | Check Functional Property for Apertium RDF EN-CA took 0.18283677101135254s
Accuracy | Check Inverse Functional Property for Apertium RDF EN-CA took 0.11245465278625488s
Accuracy | Check Empty annotation labels for Apertium RDF EN-CA took 1.0177650451660156s
Accuracy | Check White space in annotation for Apertium RDF EN-CA took 0.010401010513305664s
Accuracy | Check Datatype consistency for Apertium RDF EN-CA took 2.724064350128174s
Consistency | Disjoint class check for Apertium RDF EN-CA took 0.10127377510070801s
Consistency | Check Misplaced properties for Apertium RDF EN-CA took 5.289688348770142s
Consistency | Misplaced classes for Apertium RDF EN-CA took 8.383363246917725s
Consistency | Check Ontology hijacking for Apertium RDF EN-CA took 109.83549737930298s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EN-CA took 1.557250738143921s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EN-CA took 5.97978138923645s
Conciseness | Check Extensional conciseness for Apertium RDF EN-CA took 2.933401584625244s
Conciseness | Check Intensional conciseness for Apertium RDF EN-CA took 0.1880948543548584s
Security | Sign check for Apertium RDF EN-CA took 0.10822033882141113s
Availability | Check URIs Dereferenciability for Apertium RDF EN-CA took 3.648372173309326s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 1.0307214260101318s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.018799781799316406s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0005285739898681641s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 5.698204040527344e-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.1920928955078125e-05s
INFO | --- Analysis for Apertium RDF EN-CA took 694.7738831043243s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 0.11041879653930664s
Availability | VoID file availability check for Apertium RDF EN-ES took 5.7220458984375e-06s
Extra | Recovery of all triples for Apertium RDF EN-ES took 281.63327383995056s
Performance | Total latancy measurement for Apertium RDF EN-ES took 0.6074244976043701s
Amount of data | Number of triples check for Apertium RDF EN-ES took 2.261687994003296s
Interoperability | New terms check for Apertium RDF EN-ES took 3.1588754653930664s
Versatility | Languages check for Apertium RDF EN-ES took 47.307783126831055s
Interpretability | Number of blank nodes check for Apertium RDF EN-ES took 0.9650411605834961s
Interpretability | RDF structures check for Apertium RDF EN-ES took 0.2039809226989746s
Versatility | Serialization formats check for Apertium RDF EN-ES took 0.18936824798583984s
Availability | RDF dump link check for Apertium RDF EN-ES took 0.11710119247436523s
License | MR license check for Apertium RDF EN-ES took 0.1975257396697998s
License | HR license check for Apertium RDF EN-ES took 0.21911096572875977s
Amount of data | Number of property check for Apertium RDF EN-ES took 0.1941525936126709s
Understandability | Number of label check for Apertium RDF EN-ES took 0.2529256343841553s
Understandability | URI regex check for Apertium RDF EN-ES took 0.21334052085876465s
Understandability | Vocabs check for Apertium RDF EN-ES took 0.11477851867675781s
Verifiability | Authors check for Apertium RDF EN-ES took 0.23081421852111816s
Verifiability | Publishers check for Apertium RDF EN-ES took 0.1842508316040039s
Performance | Throughput check for Apertium RDF EN-ES took 12.093552350997925s
Amount of data | Check the number of entities for Apertium RDF EN-ES took 0.00014162063598632812s
Verifiability | Contribs. check for Apertium RDF EN-ES took 0.10059213638305664s
Interlinking | sameAs chians check for Apertium RDF EN-ES took 0.17068171501159668s
Interlinking | skos check for Apertium RDF EN-ES took 0.9920761585235596s
Interlinking | skos check for Apertium RDF EN-ES took 0.10896754264831543s
Timeliness | dataset update frequency check for Apertium RDF EN-ES took 0.10786032676696777s
Currency | Creation date check for Apertium RDF EN-ES took 0.17413997650146484s
Currency | Modification date check for Apertium RDF EN-ES took 0.18694090843200684s
Rep.Conc. | URIs length for Apertium RDF EN-ES took 104.11989784240723s
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.17782807350158691s
Accuracy | Check Functional Property for Apertium RDF EN-ES took 0.19568204879760742s
Accuracy | Check Inverse Functional Property for Apertium RDF EN-ES took 0.10026383399963379s
Accuracy | Check Empty annotation labels for Apertium RDF EN-ES took 0.908632755279541s
Accuracy | Check White space in annotation for Apertium RDF EN-ES took 0.010483264923095703s
Accuracy | Check Datatype consistency for Apertium RDF EN-ES took 2.693495273590088s
Consistency | Disjoint class check for Apertium RDF EN-ES took 0.10251092910766602s
Consistency | Check Misplaced properties for Apertium RDF EN-ES took 4.617384433746338s
Consistency | Misplaced classes for Apertium RDF EN-ES took 8.283998489379883s
Consistency | Check Ontology hijacking for Apertium RDF EN-ES took 105.49063968658447s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EN-ES took 1.5216407775878906s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EN-ES took 5.8893373012542725s
Conciseness | Check Extensional conciseness for Apertium RDF EN-ES took 2.981079578399658s
Conciseness | Check Intensional conciseness for Apertium RDF EN-ES took 0.1848154067993164s
Security | Sign check for Apertium RDF EN-ES took 0.11240410804748535s
Availability | Check URIs Dereferenciability for Apertium RDF EN-ES took 3.650510787963867s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.6849358081817627s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.018201351165771484s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0005359649658203125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.887580871582031e-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.1444091796875e-05s
INFO | --- Analysis for Apertium RDF EN-ES took 686.2961854934692s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 0.10857844352722168s
Availability | VoID file availability check for Apertium RDF EN-GL took 1.0013580322265625e-05s
Extra | Recovery of all triples for Apertium RDF EN-GL took 288.5757522583008s
Performance | Total latancy measurement for Apertium RDF EN-GL took 0.5981025695800781s
Amount of data | Number of triples check for Apertium RDF EN-GL took 2.28940486907959s
Interoperability | New terms check for Apertium RDF EN-GL took 2.822633743286133s
Versatility | Languages check for Apertium RDF EN-GL took 47.65894818305969s
Interpretability | Number of blank nodes check for Apertium RDF EN-GL took 0.9572527408599854s
Interpretability | RDF structures check for Apertium RDF EN-GL took 0.20487499237060547s
Versatility | Serialization formats check for Apertium RDF EN-GL took 0.17840933799743652s
Availability | RDF dump link check for Apertium RDF EN-GL took 0.1080176830291748s
License | MR license check for Apertium RDF EN-GL took 0.17779970169067383s
License | HR license check for Apertium RDF EN-GL took 0.22317171096801758s
Amount of data | Number of property check for Apertium RDF EN-GL took 0.1833047866821289s
Understandability | Number of label check for Apertium RDF EN-GL took 0.24310779571533203s
Understandability | URI regex check for Apertium RDF EN-GL took 0.20029211044311523s
Understandability | Vocabs check for Apertium RDF EN-GL took 0.10742473602294922s
Verifiability | Authors check for Apertium RDF EN-GL took 0.25323915481567383s
Verifiability | Publishers check for Apertium RDF EN-GL took 0.17036938667297363s
Performance | Throughput check for Apertium RDF EN-GL took 11.989733457565308s
Amount of data | Check the number of entities for Apertium RDF EN-GL took 0.0005903244018554688s
Verifiability | Contribs. check for Apertium RDF EN-GL took 0.09871435165405273s
Interlinking | sameAs chians check for Apertium RDF EN-GL took 0.17589426040649414s
Interlinking | skos check for Apertium RDF EN-GL took 0.17988300323486328s
Interlinking | skos check for Apertium RDF EN-GL took 0.10971331596374512s
Timeliness | dataset update frequency check for Apertium RDF EN-GL took 0.10878181457519531s
Currency | Creation date check for Apertium RDF EN-GL took 0.1830596923828125s
Currency | Modification date check for Apertium RDF EN-GL took 0.1862778663635254s
Rep.Conc. | URIs length for Apertium RDF EN-GL took 95.6315689086914s
Interoperability | New vocabularies check for Apertium RDF EN-GL took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EN-GL took 0.1797034740447998s
Accuracy | Check Functional Property for Apertium RDF EN-GL took 0.19606804847717285s
Accuracy | Check Inverse Functional Property for Apertium RDF EN-GL took 0.11496186256408691s
Accuracy | Check Empty annotation labels for Apertium RDF EN-GL took 0.861746072769165s
Accuracy | Check White space in annotation for Apertium RDF EN-GL took 0.01043081283569336s
Accuracy | Check Datatype consistency for Apertium RDF EN-GL took 2.7947354316711426s
Consistency | Disjoint class check for Apertium RDF EN-GL took 0.11548066139221191s
Consistency | Check Misplaced properties for Apertium RDF EN-GL took 4.7869415283203125s
Consistency | Misplaced classes for Apertium RDF EN-GL took 8.3627188205719s
Consistency | Check Ontology hijacking for Apertium RDF EN-GL took 100.14398956298828s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EN-GL took 1.5576798915863037s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EN-GL took 5.856713533401489s
Conciseness | Check Extensional conciseness for Apertium RDF EN-GL took 3.0436768531799316s
Conciseness | Check Intensional conciseness for Apertium RDF EN-GL took 0.18551015853881836s
Security | Sign check for Apertium RDF EN-GL took 0.11391854286193848s
Availability | Check URIs Dereferenciability for Apertium RDF EN-GL took 4.013221502304077s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.5615439414978027s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.018154621124267578s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0005307197570800781s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 5.078315734863281e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EN-GL took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF EN-GL took 1.4066696166992188e-05s
INFO | --- Analysis for Apertium RDF EN-GL took 664.8971815109253s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 0.10925722122192383s
Availability | VoID file availability check for Apertium RDF EO-CA took 1.1205673217773438e-05s
Extra | Recovery of all triples for Apertium RDF EO-CA took 283.09795570373535s
Performance | Total latancy measurement for Apertium RDF EO-CA took 0.5912818908691406s
Amount of data | Number of triples check for Apertium RDF EO-CA took 2.2024407386779785s
Interoperability | New terms check for Apertium RDF EO-CA took 2.791321039199829s
Versatility | Languages check for Apertium RDF EO-CA took 47.36044692993164s
Interpretability | Number of blank nodes check for Apertium RDF EO-CA took 0.9662678241729736s
Interpretability | RDF structures check for Apertium RDF EO-CA took 0.20029711723327637s
Versatility | Serialization formats check for Apertium RDF EO-CA took 0.1882021427154541s
Availability | RDF dump link check for Apertium RDF EO-CA took 0.11497855186462402s
License | MR license check for Apertium RDF EO-CA took 0.17917704582214355s
License | HR license check for Apertium RDF EO-CA took 0.21209263801574707s
Amount of data | Number of property check for Apertium RDF EO-CA took 0.18909239768981934s
Understandability | Number of label check for Apertium RDF EO-CA took 0.2537248134613037s
Understandability | URI regex check for Apertium RDF EO-CA took 0.2101147174835205s
Understandability | Vocabs check for Apertium RDF EO-CA took 0.11530828475952148s
Verifiability | Authors check for Apertium RDF EO-CA took 0.22895503044128418s
Verifiability | Publishers check for Apertium RDF EO-CA took 0.18521904945373535s
Performance | Throughput check for Apertium RDF EO-CA took 12.298936367034912s
Amount of data | Check the number of entities for Apertium RDF EO-CA took 9.250640869140625e-05s
Verifiability | Contribs. check for Apertium RDF EO-CA took 0.10733652114868164s
Interlinking | sameAs chians check for Apertium RDF EO-CA took 0.17731595039367676s
Interlinking | skos check for Apertium RDF EO-CA took 0.17286920547485352s
Interlinking | skos check for Apertium RDF EO-CA took 0.10251760482788086s
Timeliness | dataset update frequency check for Apertium RDF EO-CA took 0.11566567420959473s
Currency | Creation date check for Apertium RDF EO-CA took 0.19002032279968262s
Currency | Modification date check for Apertium RDF EO-CA took 0.17280983924865723s
Rep.Conc. | URIs length for Apertium RDF EO-CA took 99.1932852268219s
Interoperability | New vocabularies check for Apertium RDF EO-CA took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-CA took 0.1814424991607666s
Accuracy | Check Functional Property for Apertium RDF EO-CA took 0.18104767799377441s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-CA took 0.11530923843383789s
Accuracy | Check Empty annotation labels for Apertium RDF EO-CA took 0.8824746608734131s
Accuracy | Check White space in annotation for Apertium RDF EO-CA took 0.010721445083618164s
Accuracy | Check Datatype consistency for Apertium RDF EO-CA took 2.695429801940918s
Consistency | Disjoint class check for Apertium RDF EO-CA took 0.10108685493469238s
Consistency | Check Misplaced properties for Apertium RDF EO-CA took 4.681333780288696s
Consistency | Misplaced classes for Apertium RDF EO-CA took 8.297440767288208s
Consistency | Check Ontology hijacking for Apertium RDF EO-CA took 100.15104627609253s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-CA took 1.5112707614898682s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-CA took 5.829855442047119s
Conciseness | Check Extensional conciseness for Apertium RDF EO-CA took 3.003286838531494s
Conciseness | Check Intensional conciseness for Apertium RDF EO-CA took 0.18053722381591797s
Security | Sign check for Apertium RDF EO-CA took 0.11093783378601074s
Availability | Check URIs Dereferenciability for Apertium RDF EO-CA took 3.6534130573272705s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.5523767471313477s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.018637657165527344s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0005221366882324219s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 5.173683166503906e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-CA took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.2636184692382812e-05s
INFO | --- Analysis for Apertium RDF EO-CA took 670.3256959915161s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 0.10858321189880371s
Availability | VoID file availability check for Apertium RDF EO-EN took 1.049041748046875e-05s
Extra | Recovery of all triples for Apertium RDF EO-EN took 305.8911724090576s
Performance | Total latancy measurement for Apertium RDF EO-EN took 0.7198727130889893s
Amount of data | Number of triples check for Apertium RDF EO-EN took 2.1397268772125244s
Interoperability | New terms check for Apertium RDF EO-EN took 2.812659978866577s
Versatility | Languages check for Apertium RDF EO-EN took 47.04091787338257s
Interpretability | Number of blank nodes check for Apertium RDF EO-EN took 0.9706504344940186s
Interpretability | RDF structures check for Apertium RDF EO-EN took 0.19270920753479004s
Versatility | Serialization formats check for Apertium RDF EO-EN took 0.18091654777526855s
Availability | RDF dump link check for Apertium RDF EO-EN took 0.10747790336608887s
License | MR license check for Apertium RDF EO-EN took 0.1934661865234375s
License | HR license check for Apertium RDF EO-EN took 0.22510266304016113s
Amount of data | Number of property check for Apertium RDF EO-EN took 0.17527008056640625s
Understandability | Number of label check for Apertium RDF EO-EN took 0.21906566619873047s
Understandability | URI regex check for Apertium RDF EO-EN took 0.21665525436401367s
Understandability | Vocabs check for Apertium RDF EO-EN took 0.10763764381408691s
Verifiability | Authors check for Apertium RDF EO-EN took 0.24025750160217285s
Verifiability | Publishers check for Apertium RDF EO-EN took 0.17668461799621582s
Performance | Throughput check for Apertium RDF EO-EN took 12.967821836471558s
Amount of data | Check the number of entities for Apertium RDF EO-EN took 0.00046253204345703125s
Verifiability | Contribs. check for Apertium RDF EO-EN took 0.1068263053894043s
Interlinking | sameAs chians check for Apertium RDF EO-EN took 0.16968774795532227s
Interlinking | skos check for Apertium RDF EO-EN took 0.1872262954711914s
Interlinking | skos check for Apertium RDF EO-EN took 0.11695384979248047s
Timeliness | dataset update frequency check for Apertium RDF EO-EN took 0.10784196853637695s
Currency | Creation date check for Apertium RDF EO-EN took 0.17586731910705566s
Currency | Modification date check for Apertium RDF EO-EN took 1.20365571975708s
Rep.Conc. | URIs length for Apertium RDF EO-EN took 99.08460593223572s
Interoperability | New vocabularies check for Apertium RDF EO-EN took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-EN took 0.18046259880065918s
Accuracy | Check Functional Property for Apertium RDF EO-EN took 0.21560430526733398s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-EN took 0.09978199005126953s
Accuracy | Check Empty annotation labels for Apertium RDF EO-EN took 0.8969454765319824s
Accuracy | Check White space in annotation for Apertium RDF EO-EN took 0.010411977767944336s
Accuracy | Check Datatype consistency for Apertium RDF EO-EN took 2.7470288276672363s
Consistency | Disjoint class check for Apertium RDF EO-EN took 0.10907530784606934s
Consistency | Check Misplaced properties for Apertium RDF EO-EN took 4.904360771179199s
Consistency | Misplaced classes for Apertium RDF EO-EN took 8.307110786437988s
Consistency | Check Ontology hijacking for Apertium RDF EO-EN took 110.58272290229797s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-EN took 1.5176444053649902s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-EN took 5.833643913269043s
Conciseness | Check Extensional conciseness for Apertium RDF EO-EN took 3.025155782699585s
Conciseness | Check Intensional conciseness for Apertium RDF EO-EN took 0.19115185737609863s
Security | Sign check for Apertium RDF EO-EN took 0.12230730056762695s
Availability | Check URIs Dereferenciability for Apertium RDF EO-EN took 3.629709005355835s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.9852583408355713s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.018113374710083008s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0005631446838378906s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 5.7220458984375e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-EN took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.1920928955078125e-05s
INFO | --- Analysis for Apertium RDF EO-EN took 707.9513680934906s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 0.1153101921081543s
Availability | VoID file availability check for Apertium RDF EO-ES took 1.0728836059570312e-05s
Extra | Recovery of all triples for Apertium RDF EO-ES took 281.94728207588196s
Performance | Total latancy measurement for Apertium RDF EO-ES took 0.6143238544464111s
Amount of data | Number of triples check for Apertium RDF EO-ES took 2.283510684967041s
Interoperability | New terms check for Apertium RDF EO-ES took 2.784553289413452s
Versatility | Languages check for Apertium RDF EO-ES took 49.505369901657104s
Interpretability | Number of blank nodes check for Apertium RDF EO-ES took 1.3762922286987305s
Interpretability | RDF structures check for Apertium RDF EO-ES took 0.20731639862060547s
Versatility | Serialization formats check for Apertium RDF EO-ES took 0.17778396606445312s
Availability | RDF dump link check for Apertium RDF EO-ES took 0.11496424674987793s
License | MR license check for Apertium RDF EO-ES took 0.18063926696777344s
License | HR license check for Apertium RDF EO-ES took 0.21558666229248047s
Amount of data | Number of property check for Apertium RDF EO-ES took 0.183302640914917s
Understandability | Number of label check for Apertium RDF EO-ES took 0.27450132369995117s
Understandability | URI regex check for Apertium RDF EO-ES took 0.2154216766357422s
Understandability | Vocabs check for Apertium RDF EO-ES took 0.1004033088684082s
Verifiability | Authors check for Apertium RDF EO-ES took 0.25136470794677734s
Verifiability | Publishers check for Apertium RDF EO-ES took 0.18453407287597656s
Performance | Throughput check for Apertium RDF EO-ES took 12.091040134429932s
Amount of data | Check the number of entities for Apertium RDF EO-ES took 0.0001513957977294922s
Verifiability | Contribs. check for Apertium RDF EO-ES took 0.1074068546295166s
Interlinking | sameAs chians check for Apertium RDF EO-ES took 0.1757674217224121s
Interlinking | skos check for Apertium RDF EO-ES took 0.17247247695922852s
Interlinking | skos check for Apertium RDF EO-ES took 0.11621403694152832s
Timeliness | dataset update frequency check for Apertium RDF EO-ES took 0.1009979248046875s
Currency | Creation date check for Apertium RDF EO-ES took 0.18587422370910645s
Currency | Modification date check for Apertium RDF EO-ES took 0.17946338653564453s
Rep.Conc. | URIs length for Apertium RDF EO-ES took 95.50999855995178s
Interoperability | New vocabularies check for Apertium RDF EO-ES took 1.2159347534179688e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-ES took 0.17835617065429688s
Accuracy | Check Functional Property for Apertium RDF EO-ES took 0.16967535018920898s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-ES took 0.1071012020111084s
Accuracy | Check Empty annotation labels for Apertium RDF EO-ES took 0.8311929702758789s
Accuracy | Check White space in annotation for Apertium RDF EO-ES took 0.010439634323120117s
Accuracy | Check Datatype consistency for Apertium RDF EO-ES took 2.739100933074951s
Consistency | Disjoint class check for Apertium RDF EO-ES took 0.11071300506591797s
Consistency | Check Misplaced properties for Apertium RDF EO-ES took 4.71972131729126s
Consistency | Misplaced classes for Apertium RDF EO-ES took 8.404675006866455s
Consistency | Check Ontology hijacking for Apertium RDF EO-ES took 109.88574504852295s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-ES took 1.506208896636963s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-ES took 5.71821141242981s
Conciseness | Check Extensional conciseness for Apertium RDF EO-ES took 3.031588315963745s
Conciseness | Check Intensional conciseness for Apertium RDF EO-ES took 0.17343473434448242s
Security | Sign check for Apertium RDF EO-ES took 0.11261105537414551s
Availability | Check URIs Dereferenciability for Apertium RDF EO-ES took 3.9588913917541504s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.5109326839447021s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.01818227767944336s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0005173683166503906s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.744529724121094e-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 7.62939453125e-06s
INFO | --- Analysis for Apertium RDF EO-ES took 675.2755632400513s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 0.10736894607543945s
Availability | VoID file availability check for Apertium RDF EO-FR took 6.4373016357421875e-06s
Extra | Recovery of all triples for Apertium RDF EO-FR took 294.8291771411896s
Performance | Total latancy measurement for Apertium RDF EO-FR took 0.6166610717773438s
Amount of data | Number of triples check for Apertium RDF EO-FR took 2.364060878753662s
Interoperability | New terms check for Apertium RDF EO-FR took 2.7461860179901123s
Versatility | Languages check for Apertium RDF EO-FR took 51.21669363975525s
Interpretability | Number of blank nodes check for Apertium RDF EO-FR took 0.9896864891052246s
Interpretability | RDF structures check for Apertium RDF EO-FR took 0.1948833465576172s
Versatility | Serialization formats check for Apertium RDF EO-FR took 0.17750954627990723s
Availability | RDF dump link check for Apertium RDF EO-FR took 0.10828328132629395s
License | MR license check for Apertium RDF EO-FR took 0.17926907539367676s
License | HR license check for Apertium RDF EO-FR took 0.21792078018188477s
Amount of data | Number of property check for Apertium RDF EO-FR took 0.19473695755004883s
Understandability | Number of label check for Apertium RDF EO-FR took 0.24379801750183105s
Understandability | URI regex check for Apertium RDF EO-FR took 0.21194863319396973s
Understandability | Vocabs check for Apertium RDF EO-FR took 0.10747599601745605s
Verifiability | Authors check for Apertium RDF EO-FR took 0.2402176856994629s
Verifiability | Publishers check for Apertium RDF EO-FR took 0.16942167282104492s
Performance | Throughput check for Apertium RDF EO-FR took 11.235766172409058s
Amount of data | Check the number of entities for Apertium RDF EO-FR took 4.267692565917969e-05s
Verifiability | Contribs. check for Apertium RDF EO-FR took 0.10567021369934082s
Interlinking | sameAs chians check for Apertium RDF EO-FR took 0.169342041015625s
Interlinking | skos check for Apertium RDF EO-FR took 0.17150521278381348s
Interlinking | skos check for Apertium RDF EO-FR took 0.11626720428466797s
Timeliness | dataset update frequency check for Apertium RDF EO-FR took 0.11433649063110352s
Currency | Creation date check for Apertium RDF EO-FR took 0.1791231632232666s
Currency | Modification date check for Apertium RDF EO-FR took 0.17270636558532715s
Rep.Conc. | URIs length for Apertium RDF EO-FR took 95.05602359771729s
Interoperability | New vocabularies check for Apertium RDF EO-FR took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-FR took 0.18700599670410156s
Accuracy | Check Functional Property for Apertium RDF EO-FR took 0.17713570594787598s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-FR took 0.11444330215454102s
Accuracy | Check Empty annotation labels for Apertium RDF EO-FR took 0.8941001892089844s
Accuracy | Check White space in annotation for Apertium RDF EO-FR took 0.010614395141601562s
Accuracy | Check Datatype consistency for Apertium RDF EO-FR took 2.698638439178467s
Consistency | Disjoint class check for Apertium RDF EO-FR took 0.10113739967346191s
Consistency | Check Misplaced properties for Apertium RDF EO-FR took 4.821526527404785s
Consistency | Misplaced classes for Apertium RDF EO-FR took 8.334481477737427s
Consistency | Check Ontology hijacking for Apertium RDF EO-FR took 104.73785758018494s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-FR took 1.5134251117706299s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-FR took 6.1909825801849365s
Conciseness | Check Extensional conciseness for Apertium RDF EO-FR took 3.00634503364563s
Conciseness | Check Intensional conciseness for Apertium RDF EO-FR took 0.1882944107055664s
Security | Sign check for Apertium RDF EO-FR took 0.10992622375488281s
Availability | Check URIs Dereferenciability for Apertium RDF EO-FR took 3.680239200592041s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.41042113304138184s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.022515058517456055s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0005199909210205078s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.839897155761719e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-FR took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EO-FR took 1.049041748046875e-05s
INFO | --- Analysis for Apertium RDF EO-FR took 690.8076250553131s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 0.10911417007446289s
Availability | VoID file availability check for Apertium RDF ES-AN took 1.239776611328125e-05s
Extra | Recovery of all triples for Apertium RDF ES-AN took 297.53771352767944s
Performance | Total latancy measurement for Apertium RDF ES-AN took 0.6156415939331055s
Amount of data | Number of triples check for Apertium RDF ES-AN took 2.2298946380615234s
Interoperability | New terms check for Apertium RDF ES-AN took 2.8421356678009033s
Versatility | Languages check for Apertium RDF ES-AN took 49.15245509147644s
Interpretability | Number of blank nodes check for Apertium RDF ES-AN took 0.9646518230438232s
Interpretability | RDF structures check for Apertium RDF ES-AN took 0.19494080543518066s
Versatility | Serialization formats check for Apertium RDF ES-AN took 0.19013690948486328s
Availability | RDF dump link check for Apertium RDF ES-AN took 0.10106396675109863s
License | MR license check for Apertium RDF ES-AN took 0.1774613857269287s
License | HR license check for Apertium RDF ES-AN took 0.21606826782226562s
Amount of data | Number of property check for Apertium RDF ES-AN took 0.17986536026000977s
Understandability | Number of label check for Apertium RDF ES-AN took 0.24597907066345215s
Understandability | URI regex check for Apertium RDF ES-AN took 0.21715235710144043s
Understandability | Vocabs check for Apertium RDF ES-AN took 0.10774040222167969s
Verifiability | Authors check for Apertium RDF ES-AN took 0.24605035781860352s
Verifiability | Publishers check for Apertium RDF ES-AN took 0.1767418384552002s
Performance | Throughput check for Apertium RDF ES-AN took 14.31794548034668s
Amount of data | Check the number of entities for Apertium RDF ES-AN took 0.00010347366333007812s
Verifiability | Contribs. check for Apertium RDF ES-AN took 0.10794234275817871s
Interlinking | sameAs chians check for Apertium RDF ES-AN took 0.1763155460357666s
Interlinking | skos check for Apertium RDF ES-AN took 0.17806744575500488s
Interlinking | skos check for Apertium RDF ES-AN took 0.10902929306030273s
Timeliness | dataset update frequency check for Apertium RDF ES-AN took 0.10708475112915039s
Currency | Creation date check for Apertium RDF ES-AN took 0.20902156829833984s
Currency | Modification date check for Apertium RDF ES-AN took 0.17252826690673828s
Rep.Conc. | URIs length for Apertium RDF ES-AN took 99.2436785697937s
Interoperability | New vocabularies check for Apertium RDF ES-AN took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-AN took 0.18056964874267578s
Accuracy | Check Functional Property for Apertium RDF ES-AN took 0.16938519477844238s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-AN took 0.10045051574707031s
Accuracy | Check Empty annotation labels for Apertium RDF ES-AN took 1.0064349174499512s
Accuracy | Check White space in annotation for Apertium RDF ES-AN took 0.011291027069091797s
Accuracy | Check Datatype consistency for Apertium RDF ES-AN took 2.765137195587158s
Consistency | Disjoint class check for Apertium RDF ES-AN took 0.10912966728210449s
Consistency | Check Misplaced properties for Apertium RDF ES-AN took 4.8734211921691895s
Consistency | Misplaced classes for Apertium RDF ES-AN took 8.35420536994934s
Consistency | Check Ontology hijacking for Apertium RDF ES-AN took 98.51660442352295s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-AN took 1.558318853378296s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-AN took 5.709009408950806s
Conciseness | Check Extensional conciseness for Apertium RDF ES-AN took 3.0348565578460693s
Conciseness | Check Intensional conciseness for Apertium RDF ES-AN took 0.18083786964416504s
Security | Sign check for Apertium RDF ES-AN took 0.10738706588745117s
Availability | Check URIs Dereferenciability for Apertium RDF ES-AN took 3.5981268882751465s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.7615790367126465s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.018362998962402344s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0005352497100830078s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 5.125999450683594e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-AN took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.4066696166992188e-05s
INFO | --- Analysis for Apertium RDF ES-AN took 679.658308506012s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 0.10799551010131836s
Availability | VoID file availability check for Apertium RDF ES-AST took 1.1205673217773438e-05s
Extra | Recovery of all triples for Apertium RDF ES-AST took 310.47161197662354s
Performance | Total latancy measurement for Apertium RDF ES-AST took 0.6171290874481201s
Amount of data | Number of triples check for Apertium RDF ES-AST took 2.2074015140533447s
Interoperability | New terms check for Apertium RDF ES-AST took 2.7893168926239014s
Versatility | Languages check for Apertium RDF ES-AST took 48.39479327201843s
Interpretability | Number of blank nodes check for Apertium RDF ES-AST took 0.9773135185241699s
Interpretability | RDF structures check for Apertium RDF ES-AST took 0.18725156784057617s
Versatility | Serialization formats check for Apertium RDF ES-AST took 0.18559908866882324s
Availability | RDF dump link check for Apertium RDF ES-AST took 0.1076056957244873s
License | MR license check for Apertium RDF ES-AST took 0.18511080741882324s
License | HR license check for Apertium RDF ES-AST took 0.21260571479797363s
Amount of data | Number of property check for Apertium RDF ES-AST took 0.18064570426940918s
Understandability | Number of label check for Apertium RDF ES-AST took 0.23822236061096191s
Understandability | URI regex check for Apertium RDF ES-AST took 0.23070907592773438s
Understandability | Vocabs check for Apertium RDF ES-AST took 0.1079256534576416s
Verifiability | Authors check for Apertium RDF ES-AST took 0.23487472534179688s
Verifiability | Publishers check for Apertium RDF ES-AST took 0.17885661125183105s
Performance | Throughput check for Apertium RDF ES-AST took 25.444741010665894s
Amount of data | Check the number of entities for Apertium RDF ES-AST took 0.00010728836059570312s
Verifiability | Contribs. check for Apertium RDF ES-AST took 0.10731363296508789s
Interlinking | sameAs chians check for Apertium RDF ES-AST took 0.17544317245483398s
Interlinking | skos check for Apertium RDF ES-AST took 0.1925504207611084s
Interlinking | skos check for Apertium RDF ES-AST took 0.1092383861541748s
Timeliness | dataset update frequency check for Apertium RDF ES-AST took 0.1087338924407959s
Currency | Creation date check for Apertium RDF ES-AST took 0.17916536331176758s
Currency | Modification date check for Apertium RDF ES-AST took 0.1853501796722412s
Rep.Conc. | URIs length for Apertium RDF ES-AST took 104.39888405799866s
Interoperability | New vocabularies check for Apertium RDF ES-AST took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-AST took 0.18301987648010254s
Accuracy | Check Functional Property for Apertium RDF ES-AST took 0.18166708946228027s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-AST took 0.10726451873779297s
Accuracy | Check Empty annotation labels for Apertium RDF ES-AST took 0.9463350772857666s
Accuracy | Check White space in annotation for Apertium RDF ES-AST took 0.010548830032348633s
Accuracy | Check Datatype consistency for Apertium RDF ES-AST took 2.745424270629883s
Consistency | Disjoint class check for Apertium RDF ES-AST took 0.1075277328491211s
Consistency | Check Misplaced properties for Apertium RDF ES-AST took 4.538522005081177s
Consistency | Misplaced classes for Apertium RDF ES-AST took 8.39158034324646s
Consistency | Check Ontology hijacking for Apertium RDF ES-AST took 106.167724609375s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-AST took 1.5329134464263916s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-AST took 5.854436635971069s
Conciseness | Check Extensional conciseness for Apertium RDF ES-AST took 3.044729232788086s
Conciseness | Check Intensional conciseness for Apertium RDF ES-AST took 0.18362998962402344s
Security | Sign check for Apertium RDF ES-AST took 0.11054825782775879s
Availability | Check URIs Dereferenciability for Apertium RDF ES-AST took 3.9459381103515625s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.6093204021453857s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.019234657287597656s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 6.151199340820312e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0005199909210205078s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 5.888938903808594e-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 1.3589859008789062e-05s
INFO | --- Analysis for Apertium RDF ES-AST took 734.7024703025818s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 0.18476176261901855s
Availability | VoID file availability check for Apertium RDF ES-CA took 1.4543533325195312e-05s
Extra | Recovery of all triples for Apertium RDF ES-CA took 298.38152503967285s
Performance | Total latancy measurement for Apertium RDF ES-CA took 0.6028718948364258s
Amount of data | Number of triples check for Apertium RDF ES-CA took 2.2502284049987793s
Interoperability | New terms check for Apertium RDF ES-CA took 2.7894225120544434s
Versatility | Languages check for Apertium RDF ES-CA took 47.86294913291931s
Interpretability | Number of blank nodes check for Apertium RDF ES-CA took 0.9606411457061768s
Interpretability | RDF structures check for Apertium RDF ES-CA took 0.21689414978027344s
Versatility | Serialization formats check for Apertium RDF ES-CA took 0.1774306297302246s
Availability | RDF dump link check for Apertium RDF ES-CA took 0.10650014877319336s
License | MR license check for Apertium RDF ES-CA took 0.1886610984802246s
License | HR license check for Apertium RDF ES-CA took 0.22323966026306152s
Amount of data | Number of property check for Apertium RDF ES-CA took 0.18805265426635742s
Understandability | Number of label check for Apertium RDF ES-CA took 0.25272202491760254s
Understandability | URI regex check for Apertium RDF ES-CA took 0.210158109664917s
Understandability | Vocabs check for Apertium RDF ES-CA took 0.10811901092529297s
Verifiability | Authors check for Apertium RDF ES-CA took 0.24543094635009766s
Verifiability | Publishers check for Apertium RDF ES-CA took 0.18391728401184082s
Performance | Throughput check for Apertium RDF ES-CA took 17.473578214645386s
Amount of data | Check the number of entities for Apertium RDF ES-CA took 8.678436279296875e-05s
Verifiability | Contribs. check for Apertium RDF ES-CA took 0.10044407844543457s
Interlinking | sameAs chians check for Apertium RDF ES-CA took 0.1793193817138672s
Interlinking | skos check for Apertium RDF ES-CA took 0.18278717994689941s
Interlinking | skos check for Apertium RDF ES-CA took 0.10968875885009766s
Timeliness | dataset update frequency check for Apertium RDF ES-CA took 0.1010596752166748s
Currency | Creation date check for Apertium RDF ES-CA took 0.18103742599487305s
Currency | Modification date check for Apertium RDF ES-CA took 0.1717526912689209s
Rep.Conc. | URIs length for Apertium RDF ES-CA took 98.41690635681152s
Interoperability | New vocabularies check for Apertium RDF ES-CA took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-CA took 0.17006397247314453s
Accuracy | Check Functional Property for Apertium RDF ES-CA took 0.17792081832885742s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-CA took 0.1076657772064209s
Accuracy | Check Empty annotation labels for Apertium RDF ES-CA took 0.8368754386901855s
Accuracy | Check White space in annotation for Apertium RDF ES-CA took 0.01037287712097168s
Accuracy | Check Datatype consistency for Apertium RDF ES-CA took 2.7366600036621094s
Consistency | Disjoint class check for Apertium RDF ES-CA took 0.10250568389892578s
Consistency | Check Misplaced properties for Apertium RDF ES-CA took 4.7198262214660645s
Consistency | Misplaced classes for Apertium RDF ES-CA took 8.523956298828125s
Consistency | Check Ontology hijacking for Apertium RDF ES-CA took 103.98329973220825s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-CA took 1.5292444229125977s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-CA took 5.857551336288452s
Conciseness | Check Extensional conciseness for Apertium RDF ES-CA took 3.024735927581787s
Conciseness | Check Intensional conciseness for Apertium RDF ES-CA took 0.18539142608642578s
Security | Sign check for Apertium RDF ES-CA took 0.11035799980163574s
Availability | Check URIs Dereferenciability for Apertium RDF ES-CA took 3.6817150115966797s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.410933256149292s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.018785953521728516s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0005664825439453125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 6.651878356933594e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-CA took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.2159347534179688e-05s
INFO | --- Analysis for Apertium RDF ES-CA took 729.1333665847778s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 0.10840082168579102s
Availability | VoID file availability check for Apertium RDF ES-GL took 7.152557373046875e-06s
Extra | Recovery of all triples for Apertium RDF ES-GL took 307.90325474739075s
Performance | Total latancy measurement for Apertium RDF ES-GL took 0.5942695140838623s
Amount of data | Number of triples check for Apertium RDF ES-GL took 2.205410957336426s
Interoperability | New terms check for Apertium RDF ES-GL took 3.0074336528778076s
Versatility | Languages check for Apertium RDF ES-GL took 47.591705083847046s
Interpretability | Number of blank nodes check for Apertium RDF ES-GL took 1.240600824356079s
Interpretability | RDF structures check for Apertium RDF ES-GL took 0.1932525634765625s
Versatility | Serialization formats check for Apertium RDF ES-GL took 0.17738986015319824s
Availability | RDF dump link check for Apertium RDF ES-GL took 0.10778450965881348s
License | MR license check for Apertium RDF ES-GL took 0.17325735092163086s
License | HR license check for Apertium RDF ES-GL took 0.21694469451904297s
Amount of data | Number of property check for Apertium RDF ES-GL took 0.1812293529510498s
Understandability | Number of label check for Apertium RDF ES-GL took 0.2311115264892578s
Understandability | URI regex check for Apertium RDF ES-GL took 0.2082197666168213s
Understandability | Vocabs check for Apertium RDF ES-GL took 0.10042047500610352s
Verifiability | Authors check for Apertium RDF ES-GL took 0.22908973693847656s
Verifiability | Publishers check for Apertium RDF ES-GL took 0.1755363941192627s
Performance | Throughput check for Apertium RDF ES-GL took 11.050388097763062s
Amount of data | Check the number of entities for Apertium RDF ES-GL took 8.916854858398438e-05s
Verifiability | Contribs. check for Apertium RDF ES-GL took 0.09996390342712402s
Interlinking | sameAs chians check for Apertium RDF ES-GL took 0.16901183128356934s
Interlinking | skos check for Apertium RDF ES-GL took 0.18758058547973633s
Interlinking | skos check for Apertium RDF ES-GL took 0.10204815864562988s
Timeliness | dataset update frequency check for Apertium RDF ES-GL took 0.11623549461364746s
Currency | Creation date check for Apertium RDF ES-GL took 0.18631219863891602s
Currency | Modification date check for Apertium RDF ES-GL took 0.17044663429260254s
Rep.Conc. | URIs length for Apertium RDF ES-GL took 98.25533771514893s
Interoperability | New vocabularies check for Apertium RDF ES-GL took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-GL took 0.17778396606445312s
Accuracy | Check Functional Property for Apertium RDF ES-GL took 0.17701196670532227s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-GL took 0.11424732208251953s
Accuracy | Check Empty annotation labels for Apertium RDF ES-GL took 0.8795442581176758s
Accuracy | Check White space in annotation for Apertium RDF ES-GL took 0.01074981689453125s
Accuracy | Check Datatype consistency for Apertium RDF ES-GL took 2.714531183242798s
Consistency | Disjoint class check for Apertium RDF ES-GL took 0.10978555679321289s
Consistency | Check Misplaced properties for Apertium RDF ES-GL took 4.612976551055908s
Consistency | Misplaced classes for Apertium RDF ES-GL took 8.330138921737671s
Consistency | Check Ontology hijacking for Apertium RDF ES-GL took 101.42915725708008s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-GL took 1.5322067737579346s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-GL took 5.7656495571136475s
Conciseness | Check Extensional conciseness for Apertium RDF ES-GL took 3.008754014968872s
Conciseness | Check Intensional conciseness for Apertium RDF ES-GL took 0.17480206489562988s
Security | Sign check for Apertium RDF ES-GL took 0.11505770683288574s
Availability | Check URIs Dereferenciability for Apertium RDF ES-GL took 3.8025972843170166s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.9145276546478271s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.01824474334716797s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0005283355712890625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-GL took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF ES-GL took 7.3909759521484375e-06s
INFO | --- Analysis for Apertium RDF ES-GL took 697.5004894733429s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 0.10751533508300781s
Availability | VoID file availability check for Apertium RDF ES-PT took 1.0967254638671875e-05s
Extra | Recovery of all triples for Apertium RDF ES-PT took 292.31041407585144s
Performance | Total latancy measurement for Apertium RDF ES-PT took 0.6189227104187012s
Amount of data | Number of triples check for Apertium RDF ES-PT took 2.1174328327178955s
Interoperability | New terms check for Apertium RDF ES-PT took 2.801173210144043s
Versatility | Languages check for Apertium RDF ES-PT took 48.856547355651855s
Interpretability | Number of blank nodes check for Apertium RDF ES-PT took 1.1214613914489746s
Interpretability | RDF structures check for Apertium RDF ES-PT took 0.20080804824829102s
Versatility | Serialization formats check for Apertium RDF ES-PT took 0.17043066024780273s
Availability | RDF dump link check for Apertium RDF ES-PT took 0.11527132987976074s
License | MR license check for Apertium RDF ES-PT took 0.17830395698547363s
License | HR license check for Apertium RDF ES-PT took 0.20413756370544434s
Amount of data | Number of property check for Apertium RDF ES-PT took 0.1809525489807129s
Understandability | Number of label check for Apertium RDF ES-PT took 0.22577476501464844s
Understandability | URI regex check for Apertium RDF ES-PT took 0.2239522933959961s
Understandability | Vocabs check for Apertium RDF ES-PT took 0.10700869560241699s
Verifiability | Authors check for Apertium RDF ES-PT took 0.2459554672241211s
Verifiability | Publishers check for Apertium RDF ES-PT took 0.17606687545776367s
Performance | Throughput check for Apertium RDF ES-PT took 16.975974082946777s
Amount of data | Check the number of entities for Apertium RDF ES-PT took 0.0001537799835205078s
Verifiability | Contribs. check for Apertium RDF ES-PT took 0.10745668411254883s
Interlinking | sameAs chians check for Apertium RDF ES-PT took 0.18343782424926758s
Interlinking | skos check for Apertium RDF ES-PT took 0.1828477382659912s
Interlinking | skos check for Apertium RDF ES-PT took 0.10897159576416016s
Timeliness | dataset update frequency check for Apertium RDF ES-PT took 0.11643218994140625s
Currency | Creation date check for Apertium RDF ES-PT took 0.17235493659973145s
Currency | Modification date check for Apertium RDF ES-PT took 0.17719244956970215s
Rep.Conc. | URIs length for Apertium RDF ES-PT took 100.25525403022766s
Interoperability | New vocabularies check for Apertium RDF ES-PT took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-PT took 0.1879253387451172s
Accuracy | Check Functional Property for Apertium RDF ES-PT took 0.17944884300231934s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-PT took 0.1378192901611328s
Accuracy | Check Empty annotation labels for Apertium RDF ES-PT took 3.728400707244873s
Accuracy | Check White space in annotation for Apertium RDF ES-PT took 0.01067662239074707s
Accuracy | Check Datatype consistency for Apertium RDF ES-PT took 2.694415330886841s
Consistency | Disjoint class check for Apertium RDF ES-PT took 0.10988950729370117s
Consistency | Check Misplaced properties for Apertium RDF ES-PT took 4.504603624343872s
Consistency | Misplaced classes for Apertium RDF ES-PT took 8.231810092926025s
Consistency | Check Ontology hijacking for Apertium RDF ES-PT took 98.73933577537537s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-PT took 1.5625720024108887s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-PT took 6.141447067260742s
Conciseness | Check Extensional conciseness for Apertium RDF ES-PT took 3.0588018894195557s
Conciseness | Check Intensional conciseness for Apertium RDF ES-PT took 0.17510652542114258s
Security | Sign check for Apertium RDF ES-PT took 0.11727714538574219s
Availability | Check URIs Dereferenciability for Apertium RDF ES-PT took 3.7889251708984375s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.43183469772338867s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.018115758895874023s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0005605220794677734s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.6253204345703125e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-PT took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF ES-PT took 1.4543533325195312e-05s
INFO | --- Analysis for Apertium RDF ES-PT took 681.8367035388947s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 0.10769534111022949s
Availability | VoID file availability check for Apertium RDF ES-RO took 1.0967254638671875e-05s
Extra | Recovery of all triples for Apertium RDF ES-RO took 304.78049778938293s
Performance | Total latancy measurement for Apertium RDF ES-RO took 0.624744176864624s
Amount of data | Number of triples check for Apertium RDF ES-RO took 2.033426523208618s
Interoperability | New terms check for Apertium RDF ES-RO took 2.9538793563842773s
Versatility | Languages check for Apertium RDF ES-RO took 47.9325168132782s
Interpretability | Number of blank nodes check for Apertium RDF ES-RO took 0.9468333721160889s
Interpretability | RDF structures check for Apertium RDF ES-RO took 0.1781601905822754s
Versatility | Serialization formats check for Apertium RDF ES-RO took 0.18009066581726074s
Availability | RDF dump link check for Apertium RDF ES-RO took 0.1002662181854248s
License | MR license check for Apertium RDF ES-RO took 0.18329095840454102s
License | HR license check for Apertium RDF ES-RO took 0.2176065444946289s
Amount of data | Number of property check for Apertium RDF ES-RO took 0.18971586227416992s
Understandability | Number of label check for Apertium RDF ES-RO took 0.272305965423584s
Understandability | URI regex check for Apertium RDF ES-RO took 0.2180325984954834s
Understandability | Vocabs check for Apertium RDF ES-RO took 0.10644149780273438s
Verifiability | Authors check for Apertium RDF ES-RO took 0.24164247512817383s
Verifiability | Publishers check for Apertium RDF ES-RO took 0.16936016082763672s
Performance | Throughput check for Apertium RDF ES-RO took 12.670507669448853s
Amount of data | Check the number of entities for Apertium RDF ES-RO took 0.00010943412780761719s
Verifiability | Contribs. check for Apertium RDF ES-RO took 0.11500215530395508s
Interlinking | sameAs chians check for Apertium RDF ES-RO took 0.1757354736328125s
Interlinking | skos check for Apertium RDF ES-RO took 0.1795511245727539s
Interlinking | skos check for Apertium RDF ES-RO took 0.1096796989440918s
Timeliness | dataset update frequency check for Apertium RDF ES-RO took 0.1003727912902832s
Currency | Creation date check for Apertium RDF ES-RO took 0.17907404899597168s
Currency | Modification date check for Apertium RDF ES-RO took 0.18523621559143066s
Rep.Conc. | URIs length for Apertium RDF ES-RO took 100.36820411682129s
Interoperability | New vocabularies check for Apertium RDF ES-RO took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-RO took 0.18468785285949707s
Accuracy | Check Functional Property for Apertium RDF ES-RO took 0.17805004119873047s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-RO took 0.11451530456542969s
Accuracy | Check Empty annotation labels for Apertium RDF ES-RO took 0.8578319549560547s
Accuracy | Check White space in annotation for Apertium RDF ES-RO took 0.010485172271728516s
Accuracy | Check Datatype consistency for Apertium RDF ES-RO took 2.707573890686035s
Consistency | Disjoint class check for Apertium RDF ES-RO took 0.10905742645263672s
Consistency | Check Misplaced properties for Apertium RDF ES-RO took 4.832159996032715s
Consistency | Misplaced classes for Apertium RDF ES-RO took 8.282581806182861s
Consistency | Check Ontology hijacking for Apertium RDF ES-RO took 104.9958004951477s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-RO took 1.5375034809112549s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-RO took 6.4932355880737305s
Conciseness | Check Extensional conciseness for Apertium RDF ES-RO took 3.129879951477051s
Conciseness | Check Intensional conciseness for Apertium RDF ES-RO took 0.1913597583770752s
Security | Sign check for Apertium RDF ES-RO took 0.10285139083862305s
Availability | Check URIs Dereferenciability for Apertium RDF ES-RO took 3.748499870300293s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.4646315574645996s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.01821732521057129s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0005478858947753906s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.8160552978515625e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-RO took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF ES-RO took 1.3113021850585938e-05s
INFO | --- Analysis for Apertium RDF ES-RO took 691.5489544868469s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 0.10834932327270508s
Availability | VoID file availability check for Apertium RDF EU-EN took 1.1920928955078125e-05s
Extra | Recovery of all triples for Apertium RDF EU-EN took 293.236478805542s
Performance | Total latancy measurement for Apertium RDF EU-EN took 0.6231532096862793s
Amount of data | Number of triples check for Apertium RDF EU-EN took 2.1433684825897217s
Interoperability | New terms check for Apertium RDF EU-EN took 2.8320977687835693s
Versatility | Languages check for Apertium RDF EU-EN took 47.68840312957764s
Interpretability | Number of blank nodes check for Apertium RDF EU-EN took 0.9695765972137451s
Interpretability | RDF structures check for Apertium RDF EU-EN took 2.1156678199768066s
Versatility | Serialization formats check for Apertium RDF EU-EN took 0.18807649612426758s
Availability | RDF dump link check for Apertium RDF EU-EN took 0.11440849304199219s
License | MR license check for Apertium RDF EU-EN took 0.19330692291259766s
License | HR license check for Apertium RDF EU-EN took 0.22184443473815918s
Amount of data | Number of property check for Apertium RDF EU-EN took 0.20314455032348633s
Understandability | Number of label check for Apertium RDF EU-EN took 0.2087571620941162s
Understandability | URI regex check for Apertium RDF EU-EN took 0.22316980361938477s
Understandability | Vocabs check for Apertium RDF EU-EN took 0.10825181007385254s
Verifiability | Authors check for Apertium RDF EU-EN took 0.24721121788024902s
Verifiability | Publishers check for Apertium RDF EU-EN took 0.1766188144683838s
Performance | Throughput check for Apertium RDF EU-EN took 11.488235235214233s
Amount of data | Check the number of entities for Apertium RDF EU-EN took 0.00010752677917480469s
Verifiability | Contribs. check for Apertium RDF EU-EN took 0.1064605712890625s
Interlinking | sameAs chians check for Apertium RDF EU-EN took 0.17557287216186523s
Interlinking | skos check for Apertium RDF EU-EN took 0.18213725090026855s
Interlinking | skos check for Apertium RDF EU-EN took 0.10973072052001953s
Timeliness | dataset update frequency check for Apertium RDF EU-EN took 0.10803437232971191s
Currency | Creation date check for Apertium RDF EU-EN took 0.18645644187927246s
Currency | Modification date check for Apertium RDF EU-EN took 0.18413829803466797s
Rep.Conc. | URIs length for Apertium RDF EU-EN took 98.16634202003479s
Interoperability | New vocabularies check for Apertium RDF EU-EN took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF EU-EN took 0.18642425537109375s
Accuracy | Check Functional Property for Apertium RDF EU-EN took 0.17651867866516113s
Accuracy | Check Inverse Functional Property for Apertium RDF EU-EN took 0.11539316177368164s
Accuracy | Check Empty annotation labels for Apertium RDF EU-EN took 0.9180536270141602s
Accuracy | Check White space in annotation for Apertium RDF EU-EN took 0.010486602783203125s
Accuracy | Check Datatype consistency for Apertium RDF EU-EN took 2.7471537590026855s
Consistency | Disjoint class check for Apertium RDF EU-EN took 0.10875177383422852s
Consistency | Check Misplaced properties for Apertium RDF EU-EN took 4.911200046539307s
Consistency | Misplaced classes for Apertium RDF EU-EN took 8.402010440826416s
Consistency | Check Ontology hijacking for Apertium RDF EU-EN took 98.47921848297119s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EU-EN took 1.4981403350830078s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EU-EN took 5.857544898986816s
Conciseness | Check Extensional conciseness for Apertium RDF EU-EN took 3.028648853302002s
Conciseness | Check Intensional conciseness for Apertium RDF EU-EN took 0.18361592292785645s
Security | Sign check for Apertium RDF EU-EN took 3.9163029193878174s
Availability | Check URIs Dereferenciability for Apertium RDF EU-EN took 3.757878065109253s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.7779498100280762s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.01816415786743164s
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.0005297660827636719s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.76837158203125e-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.1205673217773438e-05s
INFO | --- Analysis for Apertium RDF EU-EN took 676.2400162220001s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 0.10135746002197266s
Availability | VoID file availability check for Apertium RDF EU-ES took 7.152557373046875e-06s
Extra | Recovery of all triples for Apertium RDF EU-ES took 294.46821212768555s
Performance | Total latancy measurement for Apertium RDF EU-ES took 0.6440532207489014s
Amount of data | Number of triples check for Apertium RDF EU-ES took 2.284061908721924s
Interoperability | New terms check for Apertium RDF EU-ES took 2.8537960052490234s
Versatility | Languages check for Apertium RDF EU-ES took 49.29949140548706s
Interpretability | Number of blank nodes check for Apertium RDF EU-ES took 0.9685709476470947s
Interpretability | RDF structures check for Apertium RDF EU-ES took 0.19030475616455078s
Versatility | Serialization formats check for Apertium RDF EU-ES took 0.1783890724182129s
Availability | RDF dump link check for Apertium RDF EU-ES took 0.11526679992675781s
License | MR license check for Apertium RDF EU-ES took 0.18123650550842285s
License | HR license check for Apertium RDF EU-ES took 0.21971940994262695s
Amount of data | Number of property check for Apertium RDF EU-ES took 0.19033217430114746s
Understandability | Number of label check for Apertium RDF EU-ES took 0.24168705940246582s
Understandability | URI regex check for Apertium RDF EU-ES took 0.2307579517364502s
Understandability | Vocabs check for Apertium RDF EU-ES took 0.11521792411804199s
Verifiability | Authors check for Apertium RDF EU-ES took 0.22538232803344727s
Verifiability | Publishers check for Apertium RDF EU-ES took 0.18509411811828613s
Performance | Throughput check for Apertium RDF EU-ES took 10.592146635055542s
Amount of data | Check the number of entities for Apertium RDF EU-ES took 9.1552734375e-05s
Verifiability | Contribs. check for Apertium RDF EU-ES took 0.10700082778930664s
Interlinking | sameAs chians check for Apertium RDF EU-ES took 0.17824435234069824s
Interlinking | skos check for Apertium RDF EU-ES took 0.1886157989501953s
Interlinking | skos check for Apertium RDF EU-ES took 0.11736822128295898s
Timeliness | dataset update frequency check for Apertium RDF EU-ES took 0.11576318740844727s
Currency | Creation date check for Apertium RDF EU-ES took 0.18410301208496094s
Currency | Modification date check for Apertium RDF EU-ES took 0.18523073196411133s
Rep.Conc. | URIs length for Apertium RDF EU-ES took 102.49347400665283s
Interoperability | New vocabularies check for Apertium RDF EU-ES took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF EU-ES took 0.18603110313415527s
Accuracy | Check Functional Property for Apertium RDF EU-ES took 0.1768803596496582s
Accuracy | Check Inverse Functional Property for Apertium RDF EU-ES took 0.11521792411804199s
Accuracy | Check Empty annotation labels for Apertium RDF EU-ES took 0.8445553779602051s
Accuracy | Check White space in annotation for Apertium RDF EU-ES took 0.010530233383178711s
Accuracy | Check Datatype consistency for Apertium RDF EU-ES took 2.708997964859009s
Consistency | Disjoint class check for Apertium RDF EU-ES took 0.10216903686523438s
Consistency | Check Misplaced properties for Apertium RDF EU-ES took 4.629721641540527s
Consistency | Misplaced classes for Apertium RDF EU-ES took 8.382409811019897s
Consistency | Check Ontology hijacking for Apertium RDF EU-ES took 106.3772964477539s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EU-ES took 1.6044645309448242s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EU-ES took 6.159204483032227s
Conciseness | Check Extensional conciseness for Apertium RDF EU-ES took 3.106332540512085s
Conciseness | Check Intensional conciseness for Apertium RDF EU-ES took 0.1835639476776123s
Security | Sign check for Apertium RDF EU-ES took 0.1115570068359375s
Availability | Check URIs Dereferenciability for Apertium RDF EU-ES took 3.8531363010406494s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.4731159210205078s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.01845574378967285s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0005328655242919922s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.792213439941406e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EU-ES took 2.384185791015625e-06s
Believability | Calculation of trust value for Apertium RDF EU-ES took 1.0251998901367188e-05s
INFO | --- Analysis for Apertium RDF EU-ES took 687.4561622142792s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 0.11044430732727051s
Availability | VoID file availability check for Apertium RDF FR-CA took 2.193450927734375e-05s
Extra | Recovery of all triples for Apertium RDF FR-CA took 284.5521559715271s
Performance | Total latancy measurement for Apertium RDF FR-CA took 0.5971362590789795s
Amount of data | Number of triples check for Apertium RDF FR-CA took 2.0460712909698486s
Interoperability | New terms check for Apertium RDF FR-CA took 3.0140857696533203s
Versatility | Languages check for Apertium RDF FR-CA took 46.87606644630432s
Interpretability | Number of blank nodes check for Apertium RDF FR-CA took 1.0565013885498047s
Interpretability | RDF structures check for Apertium RDF FR-CA took 0.18550920486450195s
Versatility | Serialization formats check for Apertium RDF FR-CA took 0.17383790016174316s
Availability | RDF dump link check for Apertium RDF FR-CA took 0.11489605903625488s
License | MR license check for Apertium RDF FR-CA took 0.17932820320129395s
License | HR license check for Apertium RDF FR-CA took 0.23134660720825195s
Amount of data | Number of property check for Apertium RDF FR-CA took 0.19308018684387207s
Understandability | Number of label check for Apertium RDF FR-CA took 0.21131324768066406s
Understandability | URI regex check for Apertium RDF FR-CA took 0.2222461700439453s
Understandability | Vocabs check for Apertium RDF FR-CA took 0.1075286865234375s
Verifiability | Authors check for Apertium RDF FR-CA took 0.2345743179321289s
Verifiability | Publishers check for Apertium RDF FR-CA took 0.18406963348388672s
Performance | Throughput check for Apertium RDF FR-CA took 10.693624496459961s
Amount of data | Check the number of entities for Apertium RDF FR-CA took 9.465217590332031e-05s
Verifiability | Contribs. check for Apertium RDF FR-CA took 0.10699677467346191s
Interlinking | sameAs chians check for Apertium RDF FR-CA took 0.16820311546325684s
Interlinking | skos check for Apertium RDF FR-CA took 0.17502427101135254s
Interlinking | skos check for Apertium RDF FR-CA took 0.1091461181640625s
Timeliness | dataset update frequency check for Apertium RDF FR-CA took 0.10768437385559082s
Currency | Creation date check for Apertium RDF FR-CA took 0.1792600154876709s
Currency | Modification date check for Apertium RDF FR-CA took 0.1873159408569336s
Rep.Conc. | URIs length for Apertium RDF FR-CA took 100.50852966308594s
Interoperability | New vocabularies check for Apertium RDF FR-CA took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF FR-CA took 0.19272279739379883s
Accuracy | Check Functional Property for Apertium RDF FR-CA took 0.1910858154296875s
Accuracy | Check Inverse Functional Property for Apertium RDF FR-CA took 0.10837960243225098s
Accuracy | Check Empty annotation labels for Apertium RDF FR-CA took 0.9337501525878906s
Accuracy | Check White space in annotation for Apertium RDF FR-CA took 0.010631084442138672s
Accuracy | Check Datatype consistency for Apertium RDF FR-CA took 2.6783761978149414s
Consistency | Disjoint class check for Apertium RDF FR-CA took 0.11269044876098633s
Consistency | Check Misplaced properties for Apertium RDF FR-CA took 4.651355981826782s
Consistency | Misplaced classes for Apertium RDF FR-CA took 8.401839017868042s
Consistency | Check Ontology hijacking for Apertium RDF FR-CA took 109.25658321380615s
Consistency | Check Invalid usage of undefined classes for Apertium RDF FR-CA took 1.5638642311096191s
Consistency | Check Invalid usage of undefined properties for Apertium RDF FR-CA took 5.83196759223938s
Conciseness | Check Extensional conciseness for Apertium RDF FR-CA took 3.046102285385132s
Conciseness | Check Intensional conciseness for Apertium RDF FR-CA took 0.18696856498718262s
Security | Sign check for Apertium RDF FR-CA took 0.11768269538879395s
Availability | Check URIs Dereferenciability for Apertium RDF FR-CA took 3.7710487842559814s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.47286248207092285s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.022337913513183594s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0005350112915039062s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 5.316734313964844e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF FR-CA took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.3113021850585938e-05s
INFO | --- Analysis for Apertium RDF FR-CA took 677.9610438346863s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 0.11569643020629883s
Availability | VoID file availability check for Apertium RDF FR-ES took 1.0251998901367188e-05s
Extra | Recovery of all triples for Apertium RDF FR-ES took 307.7532277107239s
Performance | Total latancy measurement for Apertium RDF FR-ES took 0.6099717617034912s
Amount of data | Number of triples check for Apertium RDF FR-ES took 2.20560359954834s
Interoperability | New terms check for Apertium RDF FR-ES took 2.7971279621124268s
Versatility | Languages check for Apertium RDF FR-ES took 47.224709033966064s
Interpretability | Number of blank nodes check for Apertium RDF FR-ES took 1.1667513847351074s
Interpretability | RDF structures check for Apertium RDF FR-ES took 0.20426034927368164s
Versatility | Serialization formats check for Apertium RDF FR-ES took 0.18616294860839844s
Availability | RDF dump link check for Apertium RDF FR-ES took 0.11578774452209473s
License | MR license check for Apertium RDF FR-ES took 0.18798208236694336s
License | HR license check for Apertium RDF FR-ES took 0.20509934425354004s
Amount of data | Number of property check for Apertium RDF FR-ES took 0.19560766220092773s
Understandability | Number of label check for Apertium RDF FR-ES took 0.22050833702087402s
Understandability | URI regex check for Apertium RDF FR-ES took 0.21716761589050293s
Understandability | Vocabs check for Apertium RDF FR-ES took 0.10808634757995605s
Verifiability | Authors check for Apertium RDF FR-ES took 0.237884521484375s
Verifiability | Publishers check for Apertium RDF FR-ES took 0.1836872100830078s
Performance | Throughput check for Apertium RDF FR-ES took 11.096729755401611s
Amount of data | Check the number of entities for Apertium RDF FR-ES took 0.00018072128295898438s
Verifiability | Contribs. check for Apertium RDF FR-ES took 0.10786128044128418s
Interlinking | sameAs chians check for Apertium RDF FR-ES took 0.17119479179382324s
Interlinking | skos check for Apertium RDF FR-ES took 0.18354058265686035s
Interlinking | skos check for Apertium RDF FR-ES took 0.10948538780212402s
Timeliness | dataset update frequency check for Apertium RDF FR-ES took 0.10004925727844238s
Currency | Creation date check for Apertium RDF FR-ES took 0.18052101135253906s
Currency | Modification date check for Apertium RDF FR-ES took 0.17989015579223633s
Rep.Conc. | URIs length for Apertium RDF FR-ES took 94.63856530189514s
Interoperability | New vocabularies check for Apertium RDF FR-ES took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF FR-ES took 0.18584346771240234s
Accuracy | Check Functional Property for Apertium RDF FR-ES took 0.1777794361114502s
Accuracy | Check Inverse Functional Property for Apertium RDF FR-ES took 0.11484837532043457s
Accuracy | Check Empty annotation labels for Apertium RDF FR-ES took 0.97593092918396s
Accuracy | Check White space in annotation for Apertium RDF FR-ES took 0.010453224182128906s
Accuracy | Check Datatype consistency for Apertium RDF FR-ES took 2.7499804496765137s
Consistency | Disjoint class check for Apertium RDF FR-ES took 0.11665987968444824s
Consistency | Check Misplaced properties for Apertium RDF FR-ES took 4.663510799407959s
Consistency | Misplaced classes for Apertium RDF FR-ES took 8.382358312606812s
Consistency | Check Ontology hijacking for Apertium RDF FR-ES took 107.35484790802002s
Consistency | Check Invalid usage of undefined classes for Apertium RDF FR-ES took 1.619199275970459s
Consistency | Check Invalid usage of undefined properties for Apertium RDF FR-ES took 6.659526824951172s
Conciseness | Check Extensional conciseness for Apertium RDF FR-ES took 3.142625331878662s
Conciseness | Check Intensional conciseness for Apertium RDF FR-ES took 0.17629718780517578s
Security | Sign check for Apertium RDF FR-ES took 0.1185765266418457s
Availability | Check URIs Dereferenciability for Apertium RDF FR-ES took 3.934065103530884s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.9691171646118164s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.018728017807006836s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0005273818969726562s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.863739013671875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF FR-ES took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.2159347534179688e-05s
INFO | --- Analysis for Apertium RDF FR-ES took 696.5866913795471s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 0.10806822776794434s
Availability | VoID file availability check for Apertium RDF OC-CA took 1.0967254638671875e-05s
Extra | Recovery of all triples for Apertium RDF OC-CA took 286.6775143146515s
Performance | Total latancy measurement for Apertium RDF OC-CA took 0.6244297027587891s
Amount of data | Number of triples check for Apertium RDF OC-CA took 2.248562812805176s
Interoperability | New terms check for Apertium RDF OC-CA took 2.8059096336364746s
Versatility | Languages check for Apertium RDF OC-CA took 47.75701069831848s
Interpretability | Number of blank nodes check for Apertium RDF OC-CA took 0.9810833930969238s
Interpretability | RDF structures check for Apertium RDF OC-CA took 0.20279407501220703s
Versatility | Serialization formats check for Apertium RDF OC-CA took 0.17987751960754395s
Availability | RDF dump link check for Apertium RDF OC-CA took 0.10096883773803711s
License | MR license check for Apertium RDF OC-CA took 0.18129968643188477s
License | HR license check for Apertium RDF OC-CA took 0.20741748809814453s
Amount of data | Number of property check for Apertium RDF OC-CA took 0.17903804779052734s
Understandability | Number of label check for Apertium RDF OC-CA took 0.24475932121276855s
Understandability | URI regex check for Apertium RDF OC-CA took 0.20816564559936523s
Understandability | Vocabs check for Apertium RDF OC-CA took 0.11465692520141602s
Verifiability | Authors check for Apertium RDF OC-CA took 0.2456667423248291s
Verifiability | Publishers check for Apertium RDF OC-CA took 0.1844491958618164s
Performance | Throughput check for Apertium RDF OC-CA took 12.480080842971802s
Amount of data | Check the number of entities for Apertium RDF OC-CA took 9.655952453613281e-05s
Verifiability | Contribs. check for Apertium RDF OC-CA took 0.11388516426086426s
Interlinking | sameAs chians check for Apertium RDF OC-CA took 0.17951059341430664s
Interlinking | skos check for Apertium RDF OC-CA took 0.18770241737365723s
Interlinking | skos check for Apertium RDF OC-CA took 0.11645722389221191s
Timeliness | dataset update frequency check for Apertium RDF OC-CA took 0.10767555236816406s
Currency | Creation date check for Apertium RDF OC-CA took 0.18705511093139648s
Currency | Modification date check for Apertium RDF OC-CA took 0.1723337173461914s
Rep.Conc. | URIs length for Apertium RDF OC-CA took 98.6739022731781s
Interoperability | New vocabularies check for Apertium RDF OC-CA took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF OC-CA took 0.17972540855407715s
Accuracy | Check Functional Property for Apertium RDF OC-CA took 0.16970038414001465s
Accuracy | Check Inverse Functional Property for Apertium RDF OC-CA took 0.10753846168518066s
Accuracy | Check Empty annotation labels for Apertium RDF OC-CA took 0.865546464920044s
Accuracy | Check White space in annotation for Apertium RDF OC-CA took 0.01049661636352539s
Accuracy | Check Datatype consistency for Apertium RDF OC-CA took 2.736511707305908s
Consistency | Disjoint class check for Apertium RDF OC-CA took 0.11805367469787598s
Consistency | Check Misplaced properties for Apertium RDF OC-CA took 4.6075615882873535s
Consistency | Misplaced classes for Apertium RDF OC-CA took 8.373707294464111s
Consistency | Check Ontology hijacking for Apertium RDF OC-CA took 108.7994339466095s
Consistency | Check Invalid usage of undefined classes for Apertium RDF OC-CA took 1.5627832412719727s
Consistency | Check Invalid usage of undefined properties for Apertium RDF OC-CA took 5.750435829162598s
Conciseness | Check Extensional conciseness for Apertium RDF OC-CA took 3.0419912338256836s
Conciseness | Check Intensional conciseness for Apertium RDF OC-CA took 0.18252897262573242s
Security | Sign check for Apertium RDF OC-CA took 0.12081480026245117s
Availability | Check URIs Dereferenciability for Apertium RDF OC-CA took 4.125524520874023s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.45391392707824707s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.018192768096923828s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0005323886871337891s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.696846008300781e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF OC-CA took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.239776611328125e-05s
INFO | --- Analysis for Apertium RDF OC-CA took 679.2660682201385s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 0.10097742080688477s
Availability | VoID file availability check for Apertium RDF OC-ES took 9.775161743164062e-06s
Extra | Recovery of all triples for Apertium RDF OC-ES took 302.0292513370514s
Performance | Total latancy measurement for Apertium RDF OC-ES took 0.6059424877166748s
Amount of data | Number of triples check for Apertium RDF OC-ES took 2.164844512939453s
Interoperability | New terms check for Apertium RDF OC-ES took 2.7635014057159424s
Versatility | Languages check for Apertium RDF OC-ES took 45.20624923706055s
Interpretability | Number of blank nodes check for Apertium RDF OC-ES took 1.0068354606628418s
Interpretability | RDF structures check for Apertium RDF OC-ES took 0.1854698657989502s
Versatility | Serialization formats check for Apertium RDF OC-ES took 0.17084431648254395s
Availability | RDF dump link check for Apertium RDF OC-ES took 0.10677886009216309s
License | MR license check for Apertium RDF OC-ES took 0.1926867961883545s
License | HR license check for Apertium RDF OC-ES took 0.21049261093139648s
Amount of data | Number of property check for Apertium RDF OC-ES took 0.17559075355529785s
Understandability | Number of label check for Apertium RDF OC-ES took 0.2376575469970703s
Understandability | URI regex check for Apertium RDF OC-ES took 0.2082810401916504s
Understandability | Vocabs check for Apertium RDF OC-ES took 0.1144402027130127s
Verifiability | Authors check for Apertium RDF OC-ES took 0.24531269073486328s
Verifiability | Publishers check for Apertium RDF OC-ES took 0.1692044734954834s
Performance | Throughput check for Apertium RDF OC-ES took 13.535361528396606s
Amount of data | Check the number of entities for Apertium RDF OC-ES took 0.0004520416259765625s
Verifiability | Contribs. check for Apertium RDF OC-ES took 0.10672450065612793s
Interlinking | sameAs chians check for Apertium RDF OC-ES took 0.1750032901763916s
Interlinking | skos check for Apertium RDF OC-ES took 0.1823430061340332s
Interlinking | skos check for Apertium RDF OC-ES took 0.10799694061279297s
Timeliness | dataset update frequency check for Apertium RDF OC-ES took 0.10025167465209961s
Currency | Creation date check for Apertium RDF OC-ES took 0.18330955505371094s
Currency | Modification date check for Apertium RDF OC-ES took 0.1799764633178711s
Rep.Conc. | URIs length for Apertium RDF OC-ES took 95.92485570907593s
Interoperability | New vocabularies check for Apertium RDF OC-ES took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF OC-ES took 0.17054343223571777s
Accuracy | Check Functional Property for Apertium RDF OC-ES took 0.17573237419128418s
Accuracy | Check Inverse Functional Property for Apertium RDF OC-ES took 0.10872864723205566s
Accuracy | Check Empty annotation labels for Apertium RDF OC-ES took 0.8813531398773193s
Accuracy | Check White space in annotation for Apertium RDF OC-ES took 0.010354042053222656s
Accuracy | Check Datatype consistency for Apertium RDF OC-ES took 2.8053090572357178s
Consistency | Disjoint class check for Apertium RDF OC-ES took 0.10897541046142578s
Consistency | Check Misplaced properties for Apertium RDF OC-ES took 4.532611131668091s
Consistency | Misplaced classes for Apertium RDF OC-ES took 8.335034608840942s
Consistency | Check Ontology hijacking for Apertium RDF OC-ES took 103.94866180419922s
Consistency | Check Invalid usage of undefined classes for Apertium RDF OC-ES took 1.5188684463500977s
Consistency | Check Invalid usage of undefined properties for Apertium RDF OC-ES took 6.009554386138916s
Conciseness | Check Extensional conciseness for Apertium RDF OC-ES took 3.146660327911377s
Conciseness | Check Intensional conciseness for Apertium RDF OC-ES took 0.18874263763427734s
Security | Sign check for Apertium RDF OC-ES took 0.11836910247802734s
Availability | Check URIs Dereferenciability for Apertium RDF OC-ES took 3.6433494091033936s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.46295905113220215s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.0189669132232666s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0005233287811279297s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF OC-ES took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.1920928955078125e-05s
INFO | --- Analysis for Apertium RDF OC-ES took 682.9531860351562s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 0.11134672164916992s
Availability | VoID file availability check for Apertium RDF PT-CA took 2.0742416381835938e-05s
Extra | Recovery of all triples for Apertium RDF PT-CA took 282.87429571151733s
Performance | Total latancy measurement for Apertium RDF PT-CA took 0.6353354454040527s
Amount of data | Number of triples check for Apertium RDF PT-CA took 2.108677864074707s
Interoperability | New terms check for Apertium RDF PT-CA took 2.8455982208251953s
Versatility | Languages check for Apertium RDF PT-CA took 45.43631315231323s
Interpretability | Number of blank nodes check for Apertium RDF PT-CA took 1.1210205554962158s
Interpretability | RDF structures check for Apertium RDF PT-CA took 0.18917322158813477s
Versatility | Serialization formats check for Apertium RDF PT-CA took 0.17824816703796387s
Availability | RDF dump link check for Apertium RDF PT-CA took 0.1072237491607666s
License | MR license check for Apertium RDF PT-CA took 0.18129825592041016s
License | HR license check for Apertium RDF PT-CA took 0.21100711822509766s
Amount of data | Number of property check for Apertium RDF PT-CA took 0.2122201919555664s
Understandability | Number of label check for Apertium RDF PT-CA took 0.2405714988708496s
Understandability | URI regex check for Apertium RDF PT-CA took 0.2006380558013916s
Understandability | Vocabs check for Apertium RDF PT-CA took 0.10776352882385254s
Verifiability | Authors check for Apertium RDF PT-CA took 0.246002197265625s
Verifiability | Publishers check for Apertium RDF PT-CA took 0.18352913856506348s
Performance | Throughput check for Apertium RDF PT-CA took 12.05546522140503s
Amount of data | Check the number of entities for Apertium RDF PT-CA took 9.059906005859375e-05s
Verifiability | Contribs. check for Apertium RDF PT-CA took 0.11466097831726074s
Interlinking | sameAs chians check for Apertium RDF PT-CA took 0.18344831466674805s
Interlinking | skos check for Apertium RDF PT-CA took 0.173295259475708s
Interlinking | skos check for Apertium RDF PT-CA took 0.11857390403747559s
Timeliness | dataset update frequency check for Apertium RDF PT-CA took 0.10761213302612305s
Currency | Creation date check for Apertium RDF PT-CA took 0.1867542266845703s
Currency | Modification date check for Apertium RDF PT-CA took 0.17777180671691895s
Rep.Conc. | URIs length for Apertium RDF PT-CA took 102.95092415809631s
Interoperability | New vocabularies check for Apertium RDF PT-CA took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF PT-CA took 0.1782841682434082s
Accuracy | Check Functional Property for Apertium RDF PT-CA took 0.18235230445861816s
Accuracy | Check Inverse Functional Property for Apertium RDF PT-CA took 0.11392474174499512s
Accuracy | Check Empty annotation labels for Apertium RDF PT-CA took 0.901890754699707s
Accuracy | Check White space in annotation for Apertium RDF PT-CA took 0.010380983352661133s
Accuracy | Check Datatype consistency for Apertium RDF PT-CA took 2.8213560581207275s
Consistency | Disjoint class check for Apertium RDF PT-CA took 0.11543989181518555s
Consistency | Check Misplaced properties for Apertium RDF PT-CA took 4.630447864532471s
Consistency | Misplaced classes for Apertium RDF PT-CA took 8.515552043914795s
Consistency | Check Ontology hijacking for Apertium RDF PT-CA took 104.08198308944702s
Consistency | Check Invalid usage of undefined classes for Apertium RDF PT-CA took 1.4934110641479492s
Consistency | Check Invalid usage of undefined properties for Apertium RDF PT-CA took 5.804933071136475s
Conciseness | Check Extensional conciseness for Apertium RDF PT-CA took 3.0165536403656006s
Conciseness | Check Intensional conciseness for Apertium RDF PT-CA took 0.18318533897399902s
Security | Sign check for Apertium RDF PT-CA took 0.10332012176513672s
Availability | Check URIs Dereferenciability for Apertium RDF PT-CA took 3.7938039302825928s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.6893508434295654s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.01804637908935547s
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.0005464553833007812s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.7206878662109375e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF PT-CA took 1.430511474609375e-06s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.1444091796875e-05s
INFO | --- Analysis for Apertium RDF PT-CA took 669.170952796936s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 0.1151421070098877s
Availability | VoID file availability check for Apertium RDF PT-GL took 7.62939453125e-06s
Extra | Recovery of all triples for Apertium RDF PT-GL took 294.24213433265686s
Performance | Total latancy measurement for Apertium RDF PT-GL took 0.6949639320373535s
Amount of data | Number of triples check for Apertium RDF PT-GL took 2.855633497238159s
Interoperability | New terms check for Apertium RDF PT-GL took 2.965942621231079s
Versatility | Languages check for Apertium RDF PT-GL took 46.92969274520874s
Interpretability | Number of blank nodes check for Apertium RDF PT-GL took 0.9692492485046387s
Interpretability | RDF structures check for Apertium RDF PT-GL took 0.20151448249816895s
Versatility | Serialization formats check for Apertium RDF PT-GL took 0.1771390438079834s
Availability | RDF dump link check for Apertium RDF PT-GL took 0.10809516906738281s
License | MR license check for Apertium RDF PT-GL took 0.18855500221252441s
License | HR license check for Apertium RDF PT-GL took 0.2069838047027588s
Amount of data | Number of property check for Apertium RDF PT-GL took 0.1817624568939209s
Understandability | Number of label check for Apertium RDF PT-GL took 0.2192528247833252s
Understandability | URI regex check for Apertium RDF PT-GL took 0.21014189720153809s
Understandability | Vocabs check for Apertium RDF PT-GL took 0.11028265953063965s
Verifiability | Authors check for Apertium RDF PT-GL took 0.24529695510864258s
Verifiability | Publishers check for Apertium RDF PT-GL took 0.17673993110656738s
Performance | Throughput check for Apertium RDF PT-GL took 10.742549657821655s
Amount of data | Check the number of entities for Apertium RDF PT-GL took 0.00012350082397460938s
Verifiability | Contribs. check for Apertium RDF PT-GL took 0.10080695152282715s
Interlinking | sameAs chians check for Apertium RDF PT-GL took 0.18438434600830078s
Interlinking | skos check for Apertium RDF PT-GL took 0.17543363571166992s
Interlinking | skos check for Apertium RDF PT-GL took 0.10899925231933594s
Timeliness | dataset update frequency check for Apertium RDF PT-GL took 0.10001039505004883s
Currency | Creation date check for Apertium RDF PT-GL took 0.18634653091430664s
Currency | Modification date check for Apertium RDF PT-GL took 0.17991852760314941s
Rep.Conc. | URIs length for Apertium RDF PT-GL took 94.80578875541687s
Interoperability | New vocabularies check for Apertium RDF PT-GL took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF PT-GL took 0.18114757537841797s
Accuracy | Check Functional Property for Apertium RDF PT-GL took 0.17918133735656738s
Accuracy | Check Inverse Functional Property for Apertium RDF PT-GL took 0.11307024955749512s
Accuracy | Check Empty annotation labels for Apertium RDF PT-GL took 0.9175567626953125s
Accuracy | Check White space in annotation for Apertium RDF PT-GL took 0.010370254516601562s
Accuracy | Check Datatype consistency for Apertium RDF PT-GL took 2.8046963214874268s
Consistency | Disjoint class check for Apertium RDF PT-GL took 0.11885190010070801s
Consistency | Check Misplaced properties for Apertium RDF PT-GL took 5.436481475830078s
Consistency | Misplaced classes for Apertium RDF PT-GL took 8.535804033279419s
Consistency | Check Ontology hijacking for Apertium RDF PT-GL took 103.96533417701721s
Consistency | Check Invalid usage of undefined classes for Apertium RDF PT-GL took 1.5070254802703857s
Consistency | Check Invalid usage of undefined properties for Apertium RDF PT-GL took 5.9583446979522705s
Conciseness | Check Extensional conciseness for Apertium RDF PT-GL took 3.0430305004119873s
Conciseness | Check Intensional conciseness for Apertium RDF PT-GL took 0.18176507949829102s
Security | Sign check for Apertium RDF PT-GL took 0.11336612701416016s
Availability | Check URIs Dereferenciability for Apertium RDF PT-GL took 3.9573636054992676s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 2.7847578525543213s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.018539905548095703s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0005335807800292969s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 5.5789947509765625e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF PT-GL took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF PT-GL took 1.1444091796875e-05s
INFO | --- Analysis for Apertium RDF PT-GL took 679.4516401290894s
Availability | SPARQL endpoint availability check for AragoDBPedia took 0.859304666519165s
Availability | VoID file availability check for AragoDBPedia took 1.0728836059570312e-05s
Extra | Recovery of all triples for AragoDBPedia took 3.1669607162475586s
Performance | Total latancy measurement for AragoDBPedia took 2.1395366191864014s
Amount of data | Number of triples check for AragoDBPedia took 0.7707173824310303s
Interoperability | New terms check for AragoDBPedia took 2.1090681552886963s
Versatility | Languages check for AragoDBPedia took 60.62223410606384s
Interpretability | Number of blank nodes check for AragoDBPedia took 2.347890853881836s
Security | Check HTTPS for AragoDBPedia took 0.3041083812713623s
Interpretability | RDF structures check for AragoDBPedia took 0.7428700923919678s
Versatility | Serialization formats check for AragoDBPedia took 0.4735410213470459s
Availability | RDF dump link check for AragoDBPedia took 0.48377251625061035s
License | MR license check for AragoDBPedia took 0.64182448387146s
License | HR license check for AragoDBPedia took 3.3004462718963623s
Amount of data | Number of property check for AragoDBPedia took 0.48419833183288574s
Understandability | Number of label check for AragoDBPedia took 0.657785177230835s
Understandability | URI regex check for AragoDBPedia took 1.1157300472259521s
Understandability | Vocabs check for AragoDBPedia took 0.501389741897583s
Verifiability | Authors check for AragoDBPedia took 0.7863357067108154s
Verifiability | Publishers check for AragoDBPedia took 0.4635918140411377s
Performance | Throughput check for AragoDBPedia took 12.70721983909607s
Amount of data | Check the number of entities for AragoDBPedia took 9.512901306152344e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.5936355590820312s
Interlinking | sameAs chians check for AragoDBPedia took 0.4732685089111328s
Interlinking | skos check for AragoDBPedia took 0.7740154266357422s
Interlinking | skos check for AragoDBPedia took 0.43741798400878906s
Timeliness | dataset update frequency check for AragoDBPedia took 0.6244838237762451s
Currency | Creation date check for AragoDBPedia took 0.45081496238708496s
Currency | Modification date check for AragoDBPedia took 0.9162092208862305s
Rep.Conc. | URIs length for AragoDBPedia took 5.7388832569122314s
Interoperability | New vocabularies check for AragoDBPedia took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.4727919101715088s
Accuracy | Check Functional Property for AragoDBPedia took 0.5385982990264893s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.5440003871917725s
Accuracy | Check Empty annotation labels for AragoDBPedia took 1.4612789154052734s
Accuracy | Check White space in annotation for AragoDBPedia took 0.027623891830444336s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.03087592124938965s
Consistency | Disjoint class check for AragoDBPedia took 0.4637720584869385s
Consistency | Check Misplaced properties for AragoDBPedia took 2.7783918380737305s
Consistency | Misplaced classes for AragoDBPedia took 0.6216442584991455s
Consistency | Check Ontology hijacking for AragoDBPedia took 2.7542667388916016s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.4922401905059814s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 3.382004499435425s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.03646039962768555s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.8133795261383057s
Security | Sign check for AragoDBPedia took 0.6224410533905029s
Availability | Check URIs Dereferenciability for AragoDBPedia took 3700.733212709427s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 1.267850637435913s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.019559144973754883s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0005686283111572266s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 4.7206878662109375e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.430511474609375e-06s
Believability | Calculation of trust value for AragoDBPedia took 6.9141387939453125e-06s
INFO | --- Analysis for AragoDBPedia took 3886.4047515392303s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.15667700767517s
Availability | VoID file availability check for Archives Hub Linked Data took 20.00115728378296s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.5406670570373535s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.01856064796447754s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0005278587341308594s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.841255187988281e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 7.62939453125e-06s
INFO | --- Analysis for Archives Hub Linked Data took 82.83123064041138s
Availability | SPARQL endpoint availability check for Archivi ISMA took 30.111191034317017s
Availability | VoID file availability check for Archivi ISMA took 20.10416340827942s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.3472301959991455s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.018227338790893555s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0005497932434082031s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 1.239776611328125e-05s
Believability | Calculation of trust value for Archivi ISMA took 1.1682510375976562e-05s
INFO | --- Analysis for Archivi ISMA took 93.03902411460876s
Availability | SPARQL endpoint availability check for ARIADNE took 0.5676367282867432s
Availability | VoID file availability check for ARIADNE took 8.344650268554688e-06s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.4166836738586426s
Reputation | Calculation of the PageRank for ARIADNE took 0.018609285354614258s
Interlinking | Calculation of Degree of Connection for ARIADNE took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ARIADNE took 0.0005545616149902344s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 1.9550323486328125e-05s
Believability | Calculation of trust value for ARIADNE took 1.0967254638671875e-05s
INFO | --- Analysis for ARIADNE took 134.36806082725525s
Availability | SPARQL endpoint availability check for Aristotle University took 2.1859664916992188s
Availability | VoID file availability check for Aristotle University took 0.016566038131713867s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.3956177234649658s
Reputation | Calculation of the PageRank for Aristotle University took 0.02151656150817871s
Interlinking | Calculation of Degree of Connection for Aristotle University took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Aristotle University took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 1.2874603271484375e-05s
Believability | Calculation of trust value for Aristotle University took 6.67572021484375e-06s
INFO | --- Analysis for Aristotle University took 7.700398921966553s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 24.326433897018433s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 7.867813110351562e-06s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.35869765281677246s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.018726110458374023s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0005636215209960938s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 1.4543533325195312e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 1.1205673217773438e-05s
INFO | --- Analysis for Transcription profiling of human, chimp and mouse brain took 46.05863690376282s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.291534423828125e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 5.7220458984375e-06s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.42832231521606445s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.018351316452026367s
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.0005574226379394531s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.4066696166992188e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 6.9141387939453125e-06s
INFO | --- Analysis for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 2.0245749950408936s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 22.83365774154663s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 4.76837158203125e-06s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.3740849494934082s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.018286705017089844s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0005445480346679688s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.743171691894531e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.2874603271484375e-05s
INFO | --- Analysis for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 60.49506163597107s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.5299530029296875e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 2.744346857070923s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.41913890838623047s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.018298864364624023s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0005691051483154297s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00010037422180175781s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.1444091796875e-05s
INFO | --- Analysis for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 13.463324546813965s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.506111145019531e-05s
Availability | VoID file availability check for Arthroscopy community took 2.8344056606292725s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.3660721778869629s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.01816105842590332s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0005435943603515625s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.00010323524475097656s
Believability | Calculation of trust value for Arthroscopy community took 1.0728836059570312e-05s
INFO | --- Analysis for Arthroscopy community took 15.193710088729858s
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 8.511543273925781e-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 3.337860107421875e-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 0.3785982131958008s
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.018124818801879883s
Interlinking | Calculation of Degree of Connection for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.0005385875701904297s
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 0.00010156631469726562s
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.0013580322265625e-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 2.632544755935669s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 5.793571472167969e-05s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 4.76837158203125e-06s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.3846132755279541s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.01863384246826172s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0005762577056884766s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.9114227294921875e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 9.5367431640625e-06s
INFO | --- Analysis for Database of Names and Biographies (DNB) took 2.4575958251953125s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 5.650520324707031e-05s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.0994415283203125e-06s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.49667930603027344s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.018144845962524414s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0005555152893066406s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.677078247070312e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 6.67572021484375e-06s
INFO | --- Analysis for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 2.765017509460449s
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.529046535491943s
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.93833589553833s
Completeness | Calculation of interlinking completeness for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.5349056720733643s
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.018519163131713867s
Interlinking | Calculation of Degree of Connection for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.0005252361297607422s
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.225440979003906e-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 1.1682510375976562e-05s
INFO | --- Analysis for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 18.485533475875854s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.9378044605255127s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.929180383682251s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.37158823013305664s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.01854562759399414s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0005369186401367188s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 8.511543273925781e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 6.67572021484375e-06s
INFO | --- Analysis for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 16.085973024368286s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.938215494155884s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 2.148854970932007s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.3952758312225342s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.01839280128479004s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0005152225494384766s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.2438507080078125e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 2.1457672119140625e-05s
INFO | --- Analysis for Database of Chinese Rare Books (CRB) took 19.18611979484558s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.939866542816162s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.9269194602966309s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.39348268508911133s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.018420934677124023s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.059906005859375e-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 8.511543273925781e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.0967254638671875e-05s
INFO | --- Analysis for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 16.068565130233765s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.916630268096924s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 1.9473462104797363s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.38806724548339844s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.01851654052734375s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0005412101745605469s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.218650817871094e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 1.0728836059570312e-05s
INFO | --- Analysis for Database of Qing Official Titles (DQOT) took 19.279950857162476s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.894857168197632s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.9286103248596191s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.5071942806243896s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.018694400787353516s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0005316734313964844s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.963180541992188e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.1205673217773438e-05s
INFO | --- Analysis for Database of the Han Wooden Slips Character Dictionary (WCD) took 17.08917236328125s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 4.216012239456177s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 1.9371163845062256s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.41545581817626953s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.018519878387451172s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0005650520324707031s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 8.20159912109375e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 7.867813110351562e-06s
INFO | --- Analysis for Linked Taiwan Artists (LTA) took 20.118057012557983s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.9226737022399902s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.948169231414795s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.5868041515350342s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.019242048263549805s
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.0013580322265625e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0005373954772949219s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.269050598144531e-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.3909759521484375e-06s
INFO | --- Analysis for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 16.623033046722412s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.9203929901123047s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.9168007373809814s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.3690803050994873s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.01849508285522461s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0005543231964111328s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.2928924560546875e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 6.4373016357421875e-06s
INFO | --- Analysis for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 16.030122995376587s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 3.0368309020996094s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.9167728424072266s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.387847900390625s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.018570423126220703s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0005366802215576172s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.62939453125e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 9.5367431640625e-06s
INFO | --- Analysis for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 17.60604977607727s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 6.0558319091796875e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 3.080014944076538s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.9260058403015137s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.018306255340576172s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0005686283111572266s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.961822509765625e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.049041748046875e-05s
INFO | --- Analysis for Atlante Sintattico d'Italia (ASIt) took 11.56539011001587s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 7.200241088867188e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.394559383392334s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.01823115348815918s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0005218982696533203s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 3.790855407714844e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 8.58306884765625e-06s
INFO | --- Analysis for Automated Similarity Judgment Program lexical data took 4.965156316757202s
Availability | SPARQL endpoint availability check for ASN:US took 264.5613327026367s
Availability | VoID file availability check for ASN:US took 0.7102890014648438s
Completeness | Calculation of interlinking completeness for ASN:US took 1.035994291305542s
Reputation | Calculation of the PageRank for ASN:US took 0.018845081329345703s
Interlinking | Calculation of Degree of Connection for ASN:US took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ASN:US took 0.0005390644073486328s
Interlinking | Calculation of Clustering coefficient for ASN:US took 8.058547973632812e-05s
Believability | Calculation of trust value for ASN:US took 3.1948089599609375e-05s
INFO | --- Analysis for ASN:US took 406.0042881965637s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 6.389617919921875e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 1.1658079624176025s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.4518716335296631s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.01850295066833496s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0005731582641601562s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 1.3113021850585938e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 7.867813110351562e-06s
INFO | --- Analysis for Talis Aspire - Manchester Metropolitan University took 5.56626558303833s
Availability | SPARQL endpoint availability check for associations took 4.291534423828125e-05s
Availability | VoID file availability check for associations took 0.6173095703125s
Completeness | Calculation of interlinking completeness for associations took 0.36878490447998047s
Reputation | Calculation of the PageRank for associations took 0.018679141998291016s
Interlinking | Calculation of Degree of Connection for associations took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for associations took 0.0005269050598144531s
Interlinking | Calculation of Clustering coefficient for associations took 6.771087646484375e-05s
Interoperability | Check the re-using of existing vocabs for associations took 0.9386758804321289s
Believability | Calculation of trust value for associations took 1.2159347534179688e-05s
INFO | --- Analysis for associations took 10.009557247161865s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 0.31932926177978516s
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 0.35111308097839355s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.018507003784179688s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0005199909210205078s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 1.2874603271484375e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 5.650520324707031e-05s
INFO | --- Analysis for ATC publikovaná SÚKL took 2.479282855987549s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 8.916854858398438e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.6055655479431152s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 1.4275562763214111s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.01802515983581543s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0005180835723876953s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 8.749961853027344e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.2159347534179688e-05s
INFO | --- Analysis for Athelia RFID, a global knowledge network of RFID technology took 6.767140865325928s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 7.850177764892578s
Availability | VoID file availability check for AUEB Linked Open Data took 1.049041748046875e-05s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.35382652282714844s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.020400524139404297s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0005567073822021484s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 1.4066696166992188e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 1.1682510375976562e-05s
INFO | --- Analysis for AUEB Linked Open Data took 31.025573253631592s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.6551463603973389s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.5010416507720947s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.36461424827575684s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.018112897872924805s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0005314350128173828s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 8.654594421386719e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 1.1682510375976562e-05s
INFO | --- Analysis for Alpine Ski Racers of Austria took 4.4421350955963135s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.29343128204345703s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.19393682479858398s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 18.930020093917847s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.6379678249359131s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.01349997520447s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.5234835147857666s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0595018863678s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0040936470032s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2754795551300049s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2921719551086426s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1553034782409668s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13297057151794434s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 214.42455768585205s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10512042045593s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24893450736999512s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.00526189804077s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2904233932495117s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.30821895599365234s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 249.15848922729492s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 619.4534523487091s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.808412790298462s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 9.5367431640625e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 107.43158268928528s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 264.4963684082031s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.19033360481262207s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1321859359741211s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17052292823791504s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 95.68661952018738s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.3176097869873047s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 218.32772088050842s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16747498512268066s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 25.918716430664062s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.4736201763153076s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.604308366775513s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17028212547302246s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.42329955101013184s
Consistency | Misplaced classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.926694393157959s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 16.649805068969727s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 22174.62956547737s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.8362889289855957s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.938863754272461s
Conciseness | Check Intensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.18054986000061035s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16753339767456055s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 181.53041243553162s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.42791485786438s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.019323348999023438s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0005369186401367188s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.462501525878906e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 5.9604644775390625e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.1444091796875e-05s
INFO | --- Analysis for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 27250.524648189545s
Availability | SPARQL endpoint availability check for BabelNet took 0.7152016162872314s
Availability | VoID file availability check for BabelNet took 5.245208740234375e-06s
Completeness | Calculation of interlinking completeness for BabelNet took 0.45395708084106445s
Reputation | Calculation of the PageRank for BabelNet took 0.018963098526000977s
Interlinking | Calculation of Degree of Connection for BabelNet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BabelNet took 0.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.00017333030700683594s
Believability | Calculation of trust value for BabelNet took 1.2159347534179688e-05s
INFO | --- Analysis for BabelNet took 5.900979042053223s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 0.00010418891906738281s
Availability | VoID file availability check for Bacevicius.lt took 1.082751750946045s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.38896894454956055s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.020580291748046875s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0005176067352294922s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 6.031990051269531e-05s
Believability | Calculation of trust value for Bacevicius.lt took 9.775161743164062e-06s
INFO | --- Analysis for Bacevicius.lt took 4.261253356933594s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.7268309593200684s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.7349684238433838s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.3942995071411133s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.019594907760620117s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.57763671875e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 1.0967254638671875e-05s
INFO | --- Analysis for Basisregistratie Adressen en Gebouwen took 5.357372045516968s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.614795446395874s
Availability | VoID file availability check for 红色经典歌曲 took 0.016421794891357422s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.3993549346923828s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020358562469482422s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0005109310150146484s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 1.3828277587890625e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.0251998901367188e-05s
INFO | --- Analysis for 红色经典歌曲 took 3.39306640625s
Availability | SPARQL endpoint availability check for baixue composer took 8.273124694824219e-05s
Availability | VoID file availability check for baixue composer took 5.9604644775390625e-06s
Completeness | Calculation of interlinking completeness for baixue composer took 0.40074849128723145s
Reputation | Calculation of the PageRank for baixue composer took 0.01843118667602539s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0005190372467041016s
Interlinking | Calculation of Clustering coefficient for baixue composer took 1.4781951904296875e-05s
Believability | Calculation of trust value for baixue composer took 1.33514404296875e-05s
INFO | --- Analysis for baixue composer took 3.7724668979644775s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 8.749961853027344e-05s
Availability | VoID file availability check for 红色经典歌曲 took 6.9141387939453125e-06s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.6135551929473877s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02109384536743164s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0005261898040771484s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 1.4066696166992188e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.1205673217773438e-05s
INFO | --- Analysis for 红色经典歌曲 took 2.768779993057251s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 8.344650268554688e-05s
Availability | VoID file availability check for 红色经典歌曲 took 7.152557373046875e-06s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.37992334365844727s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020232200622558594s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0005278587341308594s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 1.4781951904296875e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.1205673217773438e-05s
INFO | --- Analysis for 红色经典歌曲 took 3.011690855026245s
Availability | SPARQL endpoint availability check for BAMS took 9.775161743164062e-05s
Availability | VoID file availability check for BAMS took 20.172701120376587s
Completeness | Calculation of interlinking completeness for BAMS took 0.3534069061279297s
Reputation | Calculation of the PageRank for BAMS took 0.018218278884887695s
Interlinking | Calculation of Degree of Connection for BAMS took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0005469322204589844s
Interlinking | Calculation of Clustering coefficient for BAMS took 1.239776611328125e-05s
Believability | Calculation of trust value for BAMS took 1.1920928955078125e-05s
INFO | --- Analysis for BAMS took 29.987671375274658s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 8.630752563476562e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 7.62939453125e-06s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.3525371551513672s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.018570661544799805s
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.0005447864532470703s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.5299530029296875e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 1.0967254638671875e-05s
INFO | --- Analysis for Basque EuroWordNet-lemon lexicon (3.0) took 2.4969959259033203s
Availability | SPARQL endpoint availability check for BBC Music took 0.44223475456237793s
Availability | VoID file availability check for BBC Music took 0.30475711822509766s
Completeness | Calculation of interlinking completeness for BBC Music took 0.36574649810791016s
Reputation | Calculation of the PageRank for BBC Music took 0.020427465438842773s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0005834102630615234s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00014543533325195312s
Believability | Calculation of trust value for BBC Music took 1.1920928955078125e-05s
INFO | --- Analysis for BBC Music took 3.690730571746826s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.20977568626403809s
Availability | VoID file availability check for BBC Programmes took 0.4400198459625244s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.3769397735595703s
Reputation | Calculation of the PageRank for BBC Programmes took 0.019736289978027344s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0005176067352294922s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010371208190917969s
Believability | Calculation of trust value for BBC Programmes took 1.2636184692382812e-05s
INFO | --- Analysis for BBC Programmes took 9.37891697883606s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.2672104835510254s
Availability | VoID file availability check for BBC Wildlife Finder took 0.39843153953552246s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.38101720809936523s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.01970362663269043s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0005316734313964844s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010228157043457031s
Believability | Calculation of trust value for BBC Wildlife Finder took 9.775161743164062e-06s
INFO | --- Analysis for BBC Wildlife Finder took 10.535573244094849s
Availability | SPARQL endpoint availability check for BBOP took 8.320808410644531e-05s
Availability | VoID file availability check for BBOP took 0.5246667861938477s
Completeness | Calculation of interlinking completeness for BBOP took 0.37543153762817383s
Reputation | Calculation of the PageRank for BBOP took 0.018118858337402344s
Interlinking | Calculation of Degree of Connection for BBOP took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0005280971527099609s
Interlinking | Calculation of Clustering coefficient for BBOP took 1.239776611328125e-05s
Believability | Calculation of trust value for BBOP took 1.0967254638671875e-05s
INFO | --- Analysis for BBOP took 19.857617139816284s
Availability | SPARQL endpoint availability check for BBOP took 8.559226989746094e-05s
Availability | VoID file availability check for BBOP took 0.5467250347137451s
Completeness | Calculation of interlinking completeness for BBOP took 0.4091012477874756s
Reputation | Calculation of the PageRank for BBOP took 0.01868462562561035s
Interlinking | Calculation of Degree of Connection for BBOP took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0005364418029785156s
Interlinking | Calculation of Clustering coefficient for BBOP took 1.4543533325195312e-05s
Believability | Calculation of trust value for BBOP took 1.3113021850585938e-05s
INFO | --- Analysis for BBOP took 18.142690896987915s
Availability | SPARQL endpoint availability check for Bdgp took 1.4783494472503662s
Availability | VoID file availability check for Bdgp took 0.8158383369445801s
Completeness | Calculation of interlinking completeness for Bdgp took 0.35174083709716797s
Reputation | Calculation of the PageRank for Bdgp took 0.018428564071655273s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0005192756652832031s
Interlinking | Calculation of Clustering coefficient for Bdgp took 1.33514404296875e-05s
Believability | Calculation of trust value for Bdgp took 1.2874603271484375e-05s
INFO | --- Analysis for Bdgp took 5.33996844291687s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 3.1170833110809326s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 4.68078088760376s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.3446500301361084s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.017988204956054688s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0005247592926025391s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.413459777832031e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 1.0013580322265625e-05s
INFO | --- Analysis for EU: fintrans.publicdata.eu took 17.55406379699707s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 8.463859558105469e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.01671743392944336s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.36835384368896484s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.019025087356567383s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0005884170532226562s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 1.3828277587890625e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 1.1920928955078125e-05s
INFO | --- Analysis for Berlin Offener Haushalt took 2.154982328414917s
Availability | SPARQL endpoint availability check for berlios took 8.845329284667969e-05s
Availability | VoID file availability check for berlios took 7.3909759521484375e-06s
Completeness | Calculation of interlinking completeness for berlios took 0.4853944778442383s
Reputation | Calculation of the PageRank for berlios took 0.018477678298950195s
Interlinking | Calculation of Degree of Connection for berlios took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for berlios took 0.0005168914794921875s
Interlinking | Calculation of Clustering coefficient for berlios took 9.059906005859375e-05s
Believability | Calculation of trust value for berlios took 1.2636184692382812e-05s
INFO | --- Analysis for berlios took 3.059624671936035s
Availability | SPARQL endpoint availability check for Between Our Worlds took 8.296966552734375e-05s
Availability | VoID file availability check for Between Our Worlds took 0.5452098846435547s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.6361844539642334s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.018568754196166992s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0005202293395996094s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 6.651878356933594e-05s
Believability | Calculation of trust value for Between Our Worlds took 1.1444091796875e-05s
INFO | --- Analysis for Between Our Worlds took 10.712799310684204s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.18361520767211914s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.017819881439208984s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.36479806900024414s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.018507719039916992s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0005164146423339844s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 8.940696716308594e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 2.5764472484588623s
Availability | SPARQL endpoint availability check for BibBase took 0.10439372062683105s
Availability | VoID file availability check for BibBase took 0.015903234481811523s
Completeness | Calculation of interlinking completeness for BibBase took 0.4623854160308838s
Reputation | Calculation of the PageRank for BibBase took 0.01997661590576172s
Interlinking | Calculation of Degree of Connection for BibBase took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BibBase took 0.0005223751068115234s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.608268737792969e-05s
Believability | Calculation of trust value for BibBase took 1.0728836059570312e-05s
INFO | --- Analysis for BibBase took 2.3003814220428467s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 8.654594421386719e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.9802484512329102s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.6974020004272461s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.018194913864135742s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0005214214324951172s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.0001010894775390625s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 1.2159347534179688e-05s
INFO | --- Analysis for Biblioteca Escolar Digital CITA took 14.162731647491455s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.00012493133544921875s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 8.58306884765625e-06s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.3486003875732422s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.02015995979309082s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0005228519439697266s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.00010418891906738281s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 1.3113021850585938e-05s
INFO | --- Analysis for Biblioteca Nacional Escolar (BNEscolar) took 6.675882816314697s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 8.678436279296875e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 7.3909759521484375e-06s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.3647899627685547s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.018458127975463867s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.00054168701171875s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.430511474609375e-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 2.877101182937622s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.00010967254638671875s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.7777252197265625s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.38016295433044434s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.018360614776611328s
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.0005385875701904297s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.981590270996094e-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 5.8712828159332275s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 8.511543273925781e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.8963823318481445s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.3753206729888916s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.018319129943847656s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0005099773406982422s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 1.4066696166992188e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 1.239776611328125e-05s
INFO | --- Analysis for Billion Triples Challenge Dataset 2008 took 6.955865859985352s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 8.559226989746094e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.2417449951171875s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.49230122566223145s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.01808929443359375s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0005218982696533203s
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 1.239776611328125e-05s
INFO | --- Analysis for Billion Triples Challenge Dataset 2010 took 3.681837797164917s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 1.8102619647979736s
Availability | VoID file availability check for Bio2RDF::ACFSID took 8.821487426757812e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.35518479347229004s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.01842188835144043s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 1.3113021850585938e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 1.1444091796875e-05s
INFO | --- Analysis for Bio2RDF::ACFSID took 14.57578730583191s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 0.45043087005615234s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.8536069393157959s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 20.368194580078125s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.598783016204834s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 45.99561834335327s
Interoperability | New terms check for Bio2RDF::Affymetrix took 44.05372977256775s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.16041707992554s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.1719658374786377s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.19880437850952148s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.1590871810913086s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 1.0375173091888428s
License | MR license check for Bio2RDF::Affymetrix took 0.43584704399108887s
License | HR license check for Bio2RDF::Affymetrix took 60.14173769950867s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.1765577793121338s
Understandability | Number of label check for Bio2RDF::Affymetrix took 9.931665897369385s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.42905569076538086s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.1691133975982666s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.18629050254821777s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.4531426429748535s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.52823781967163s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.7685368061065674s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.17423009872436523s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.8978383541107178s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.22819042205810547s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.1692371368408203s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.2884230613708496s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.16184711456298828s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 111.77497148513794s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 23.116254568099976s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.40181875228881836s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.20076799392700195s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.1559154987335205s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 7.014023065567017s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.905266523361206s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6572041511535645s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.32412266731262207s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 65.91922855377197s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.34146785736084s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.3244102001190186s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.292834758758545s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.46960520744324s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.7113242149353027s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.36969995498657227s
Security | Sign check for Bio2RDF::Affymetrix took 0.15269088745117188s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 3.8670380115509033s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.7185206413269043s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.021116018295288086s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0005769729614257812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.00010657310485839844s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 22.664110898971558s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.2636184692382812e-05s
INFO | --- Analysis for Bio2RDF::Affymetrix took 1064.5599749088287s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 1.5531244277954102s
Availability | VoID file availability check for Bio2RDF::Biomodels took 1.1717185974121094s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 20.367882251739502s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.4636313915252686s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 46.33477807044983s
Interoperability | New terms check for Bio2RDF::Biomodels took 44.12990474700928s
Versatility | Languages check for Bio2RDF::Biomodels took 60.29197382926941s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.30469846725463867s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.17771124839782715s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.2977266311645508s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.31437039375305176s
Availability | RDF dump link check for Bio2RDF::Biomodels took 1.2023468017578125s
License | MR license check for Bio2RDF::Biomodels took 0.3034517765045166s
License | HR license check for Bio2RDF::Biomodels took 60.29130554199219s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.28517866134643555s
Understandability | Number of label check for Bio2RDF::Biomodels took 9.3654305934906s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.6986680030822754s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.2923719882965088s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.3706800937652588s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.45000791549682617s
Performance | Throughput check for Bio2RDF::Biomodels took 11.850011587142944s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 0.8282368183135986s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.32204771041870117s
Interlinking | skos check for Bio2RDF::Biomodels took 0.7196516990661621s
Interlinking | skos check for Bio2RDF::Biomodels took 0.4241788387298584s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.2881767749786377s
Currency | Creation date check for Bio2RDF::Biomodels took 0.44548535346984863s
Currency | Modification date check for Bio2RDF::Biomodels took 0.3082129955291748s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 111.29165959358215s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 26.400748252868652s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.4976186752319336s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.28957223892211914s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.28922200202941895s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 6.784623384475708s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.9051940441131592s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6747620105743408s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.4817066192626953s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.47410726547241s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.493962526321411s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 6.406011343002319s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.3081481456756592s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.61495566368103s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.6995344161987305s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.55283522605896s
Security | Sign check for Bio2RDF::Biomodels took 0.3092339038848877s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 3.6245522499084473s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.42540955543518066s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.01802515983581543s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0005171298980712891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00011682510375976562s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 24.229416608810425s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.1682510375976562e-05s
INFO | --- Analysis for Bio2RDF::Biomodels took 1081.0455207824707s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 0.1528174877166748s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 5.4836273193359375e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.37565159797668457s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0005297660827636719s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 1.9788742065429688e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 1.0251998901367188e-05s
INFO | --- Analysis for Bio2RDF::BioModels::BioPAX took 2.444300889968872s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.6996407508850098s
Availability | VoID file availability check for Bio2RDF::Bioportal took 1.1884102821350098s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 20.010204553604126s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.4764540195465088s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 46.07752275466919s
Interoperability | New terms check for Bio2RDF::Bioportal took 45.889166593551636s
Versatility | Languages check for Bio2RDF::Bioportal took 60.299532890319824s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.3076157569885254s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.17510700225830078s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.30289244651794434s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.3106856346130371s
Availability | RDF dump link check for Bio2RDF::Bioportal took 1.133066177368164s
License | MR license check for Bio2RDF::Bioportal took 0.2974245548248291s
License | HR license check for Bio2RDF::Bioportal took 60.2964346408844s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.3153862953186035s
Understandability | Number of label check for Bio2RDF::Bioportal took 9.74305009841919s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.6844191551208496s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.2887849807739258s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.31742000579833984s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.4379439353942871s
Performance | Throughput check for Bio2RDF::Bioportal took 11.744550466537476s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 1.098867416381836s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.3151118755340576s
Interlinking | skos check for Bio2RDF::Bioportal took 0.9029757976531982s
Interlinking | skos check for Bio2RDF::Bioportal took 0.427886962890625s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.2962207794189453s
Currency | Creation date check for Bio2RDF::Bioportal took 0.41341614723205566s
Currency | Modification date check for Bio2RDF::Bioportal took 0.283430814743042s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 110.44944190979004s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 27.30120849609375s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.5413124561309814s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.3448948860168457s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.2874946594238281s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 7.122259140014648s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.9098730087280273s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6724414825439453s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.47498059272766113s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 65.51176118850708s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.4893510341644287s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.525222301483154s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.309542179107666s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.601569414138794s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.6944174766540527s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.5153377056121826s
Security | Sign check for Bio2RDF::Bioportal took 0.31366753578186035s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 3.7300732135772705s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 1.2397522926330566s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.017940044403076172s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0005154609680175781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004246234893798828s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 29.996142148971558s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 6.9141387939453125e-06s
INFO | --- Analysis for Bio2RDF::Bioportal took 1104.0953364372253s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.16218781471252441s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.016205310821533203s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 1.6947407722473145s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.01868915557861328s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0005559921264648438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.459785461425781e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 1.1920928955078125e-05s
INFO | --- Analysis for Bio2RDF::Chembl took 22.48487663269043s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.7402749061584473s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 1.2151830196380615s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 20.609769105911255s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.5382471084594727s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 46.51011276245117s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 44.13166522979736s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.30958151817322s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.3219482898712158s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.17258191108703613s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.2923583984375s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.2908143997192383s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 1.151907205581665s
License | MR license check for Bio2RDF::Clinicaltrials took 0.498929500579834s
License | HR license check for Bio2RDF::Clinicaltrials took 60.29394292831421s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.29618000984191895s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 9.430887699127197s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.7180023193359375s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.28112053871154785s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.33374500274658203s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.44727158546447754s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 11.910215616226196s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 1.649360179901123s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.30570125579833984s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.7822401523590088s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.4280829429626465s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.28626227378845215s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.43718624114990234s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.2922217845916748s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 112.40976619720459s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 31.1501042842865s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.49911928176879883s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.2901785373687744s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.3166968822479248s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 7.34710168838501s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.9079210758209229s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.681372880935669s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.3106567859649658s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 65.72104120254517s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.518256187438965s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 6.489784002304077s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.3718914985656738s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.65229892730713s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.7102038860321045s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.5532710552215576s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.3093574047088623s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 3.891049861907959s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.4359276294708252s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.20105481147766113s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0005168914794921875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 4.935264587402344e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 30.486692905426025s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 1.1444091796875e-05s
INFO | --- Analysis for Bio2RDF::Clinicaltrials took 1095.421133518219s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.6937806606292725s
Availability | VoID file availability check for Bio2RDF::Ctd took 1.1784873008728027s
Extra | Recovery of all triples for Bio2RDF::Ctd took 19.875489473342896s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.4378204345703125s
Amount of data | Number of triples check for Bio2RDF::Ctd took 45.87680149078369s
Interoperability | New terms check for Bio2RDF::Ctd took 43.216941833496094s
Versatility | Languages check for Bio2RDF::Ctd took 60.31421256065369s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.3075578212738037s
Security | Check HTTPS for Bio2RDF::Ctd took 0.1942451000213623s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.3113877773284912s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.3062708377838135s
Availability | RDF dump link check for Bio2RDF::Ctd took 1.3438992500305176s
License | MR license check for Bio2RDF::Ctd took 0.6227524280548096s
License | HR license check for Bio2RDF::Ctd took 60.31508660316467s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.29442524909973145s
Understandability | Number of label check for Bio2RDF::Ctd took 9.45012092590332s
Understandability | URI regex check for Bio2RDF::Ctd took 0.6972553730010986s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.2821969985961914s
Verifiability | Authors check for Bio2RDF::Ctd took 0.31415367126464844s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.4121897220611572s
Performance | Throughput check for Bio2RDF::Ctd took 11.992879867553711s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.9699299335479736s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.3005974292755127s
Interlinking | skos check for Bio2RDF::Ctd took 0.7349331378936768s
Interlinking | skos check for Bio2RDF::Ctd took 0.40229010581970215s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.29354190826416016s
Currency | Creation date check for Bio2RDF::Ctd took 0.42795419692993164s
Currency | Modification date check for Bio2RDF::Ctd took 0.34546923637390137s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 111.09344935417175s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 23.012016773223877s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.5677690505981445s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.2955350875854492s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.32750701904296875s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 7.055945158004761s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.9178361892700195s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6583707332611084s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.5010836124420166s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.41188430786133s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.4496850967407227s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.383941173553467s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.306366205215454s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.62519812583923s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.6998860836029053s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.49887919425964355s
Security | Sign check for Bio2RDF::Ctd took 0.3245832920074463s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 3.921992301940918s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 1.3946306705474854s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.017972946166992188s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0005228519439697266s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.246566772460938e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 23.148438930511475s
Believability | Calculation of trust value for Bio2RDF::Ctd took 1.1444091796875e-05s
INFO | --- Analysis for Bio2RDF::Ctd took 1090.7327902317047s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 8.893013000488281e-05s
Availability | VoID file availability check for bio2rdf-dataset took 6.4373016357421875e-06s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.37720370292663574s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.018833398818969727s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0005548000335693359s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 5.3882598876953125e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-dataset took 3.0186970233917236s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.702695369720459s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 1.2019116878509521s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 20.442205667495728s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.45011568069458s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 46.27483582496643s
Interoperability | New terms check for Bio2RDF::Dbsnp took 43.29974031448364s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.30991196632385s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.30713963508605957s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.18822813034057617s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.470947265625s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.31092214584350586s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 1.1758601665496826s
License | MR license check for Bio2RDF::Dbsnp took 0.6148228645324707s
License | HR license check for Bio2RDF::Dbsnp took 60.28473377227783s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.30956578254699707s
Understandability | Number of label check for Bio2RDF::Dbsnp took 9.789934873580933s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.7145566940307617s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.29368138313293457s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.30774450302124023s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.39810729026794434s
Performance | Throughput check for Bio2RDF::Dbsnp took 11.961740732192993s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.8554291725158691s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.33262181282043457s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.8232293128967285s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.42583441734313965s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.30657505989074707s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.4145524501800537s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.28586721420288086s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 111.6709315776825s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 24.05333638191223s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.5148136615753174s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.3101189136505127s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.29421567916870117s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 7.263850688934326s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.9066622257232666s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.677208423614502s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.37282490730285645s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 65.6930558681488s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.4620749950408936s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.284830093383789s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.3236031532287598s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.62271022796631s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7091076374053955s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.5292544364929199s
Security | Sign check for Bio2RDF::Dbsnp took 0.32913899421691895s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 3.686554431915283s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.489163875579834s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.20384645462036133s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0005207061767578125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 7.104873657226562e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 24.726775407791138s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 1.1920928955078125e-05s
INFO | --- Analysis for Bio2RDF::Dbsnp took 1084.364058971405s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 1.4912707805633545s
Availability | VoID file availability check for Bio2RDF::Drugbank took 1.1821932792663574s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 20.58991575241089s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.466153860092163s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 46.27959108352661s
Interoperability | New terms check for Bio2RDF::Drugbank took 44.619983196258545s
Versatility | Languages check for Bio2RDF::Drugbank took 60.30005240440369s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.3209645748138428s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.19725942611694336s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.29206013679504395s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.29680442810058594s
Availability | RDF dump link check for Bio2RDF::Drugbank took 1.1290593147277832s
License | MR license check for Bio2RDF::Drugbank took 0.3170952796936035s
License | HR license check for Bio2RDF::Drugbank took 60.28997850418091s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.296558141708374s
Understandability | Number of label check for Bio2RDF::Drugbank took 9.782495260238647s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.700141429901123s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.28690576553344727s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.30085182189941406s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.4255688190460205s
Performance | Throughput check for Bio2RDF::Drugbank took 11.905946254730225s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.9962863922119141s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.31415724754333496s
Interlinking | skos check for Bio2RDF::Drugbank took 0.8506593704223633s
Interlinking | skos check for Bio2RDF::Drugbank took 0.41161251068115234s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.29642152786254883s
Currency | Creation date check for Bio2RDF::Drugbank took 0.39354419708251953s
Currency | Modification date check for Bio2RDF::Drugbank took 0.29989004135131836s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 112.69003891944885s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 24.858797311782837s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.5277934074401855s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.28688478469848633s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.2852742671966553s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 7.098701477050781s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.8987898826599121s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.670283317565918s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.2866029739379883s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 65.39730477333069s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.5129430294036865s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 6.495882272720337s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.3057613372802734s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.58335876464844s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.6983506679534912s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.49048399925231934s
Security | Sign check for Bio2RDF::Drugbank took 0.3123295307159424s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 3.8369388580322266s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 1.5000498294830322s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.023964881896972656s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0005176067352294922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00010919570922851562s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 21.267826795578003s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 6.9141387939453125e-06s
INFO | --- Analysis for Bio2RDF::Drugbank took 1083.5519959926605s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.7009060382843018s
Availability | VoID file availability check for Bio2RDF::Genage took 1.1599302291870117s
Extra | Recovery of all triples for Bio2RDF::Genage took 19.95614981651306s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.4506683349609375s
Amount of data | Number of triples check for Bio2RDF::Genage took 46.394166231155396s
Interoperability | New terms check for Bio2RDF::Genage took 43.43277144432068s
Versatility | Languages check for Bio2RDF::Genage took 60.29443097114563s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 1.152923583984375s
Security | Check HTTPS for Bio2RDF::Genage took 0.17487168312072754s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.5342984199523926s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.3036186695098877s
Availability | RDF dump link check for Bio2RDF::Genage took 1.1655352115631104s
License | MR license check for Bio2RDF::Genage took 0.4862861633300781s
License | HR license check for Bio2RDF::Genage took 60.29219150543213s
Amount of data | Number of property check for Bio2RDF::Genage took 0.3097662925720215s
Understandability | Number of label check for Bio2RDF::Genage took 10.074224710464478s
Understandability | URI regex check for Bio2RDF::Genage took 0.6879837512969971s
Understandability | Vocabs check for Bio2RDF::Genage took 0.3042266368865967s
Verifiability | Authors check for Bio2RDF::Genage took 0.31294918060302734s
Verifiability | Publishers check for Bio2RDF::Genage took 0.4097614288330078s
Performance | Throughput check for Bio2RDF::Genage took 11.96463656425476s
Verifiability | Contribs. check for Bio2RDF::Genage took 0.8695237636566162s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.32295727729797363s
Interlinking | skos check for Bio2RDF::Genage took 0.7220616340637207s
Interlinking | skos check for Bio2RDF::Genage took 0.4173417091369629s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.29106593132019043s
Currency | Creation date check for Bio2RDF::Genage took 0.43401050567626953s
Currency | Modification date check for Bio2RDF::Genage took 0.2799515724182129s
Rep.Conc. | URIs length for Bio2RDF::Genage took 111.57679605484009s
Interoperability | New vocabularies check for Bio2RDF::Genage took 22.292262077331543s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.5450284481048584s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.3264608383178711s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.3114495277404785s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 7.508392810821533s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.8962273597717285s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6756610870361328s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.5712244510650635s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 65.5477306842804s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.4675889015197754s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.771656036376953s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.2898235321044922s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.55435132980347s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7064979076385498s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.5178937911987305s
Security | Sign check for Bio2RDF::Genage took 0.31726837158203125s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 3.750129222869873s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.7033755779266357s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.01792764663696289s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0005221366882324219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 5.984306335449219e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 23.396400451660156s
Believability | Calculation of trust value for Bio2RDF::Genage took 6.67572021484375e-06s
INFO | --- Analysis for Bio2RDF::Genage took 1081.2877159118652s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 0.16364216804504395s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.017699241638183594s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.355205774307251s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.01836848258972168s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0005300045013427734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 6.008148193359375e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 1.0967254638671875e-05s
INFO | --- Analysis for Bio2RDF::GenBank took 4.696199893951416s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.6910738945007324s
Availability | VoID file availability check for Bio2RDF::Gendr took 1.2164280414581299s
Extra | Recovery of all triples for Bio2RDF::Gendr took 19.852383136749268s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.490513563156128s
Amount of data | Number of triples check for Bio2RDF::Gendr took 45.818339347839355s
Interoperability | New terms check for Bio2RDF::Gendr took 44.36392378807068s
Versatility | Languages check for Bio2RDF::Gendr took 60.30081510543823s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.3137483596801758s
Security | Check HTTPS for Bio2RDF::Gendr took 0.1951007843017578s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.3044700622558594s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.31920552253723145s
Availability | RDF dump link check for Bio2RDF::Gendr took 1.1710326671600342s
License | MR license check for Bio2RDF::Gendr took 0.6442916393280029s
License | HR license check for Bio2RDF::Gendr took 60.33641195297241s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.31679344177246094s
Understandability | Number of label check for Bio2RDF::Gendr took 9.9965980052948s
Understandability | URI regex check for Bio2RDF::Gendr took 0.7133145332336426s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.3112623691558838s
Verifiability | Authors check for Bio2RDF::Gendr took 0.3176083564758301s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.4479694366455078s
Performance | Throughput check for Bio2RDF::Gendr took 11.89194369316101s
Verifiability | Contribs. check for Bio2RDF::Gendr took 1.667003870010376s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.30526280403137207s
Interlinking | skos check for Bio2RDF::Gendr took 0.8904604911804199s
Interlinking | skos check for Bio2RDF::Gendr took 0.4273533821105957s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.30836033821105957s
Currency | Creation date check for Bio2RDF::Gendr took 0.42293715476989746s
Currency | Modification date check for Bio2RDF::Gendr took 0.29835081100463867s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 111.79405331611633s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 26.790050268173218s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.5379869937896729s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.331437349319458s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.29463720321655273s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 6.942039728164673s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.8976373672485352s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6683354377746582s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.3447434902191162s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 65.57326579093933s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.4484941959381104s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.3971099853515625s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.3585381507873535s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.6366662979126s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.714608907699585s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.5303113460540771s
Security | Sign check for Bio2RDF::Gendr took 0.3057100772857666s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 3.9680817127227783s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.9471435546875s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.18716144561767578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0005228519439697266s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.650520324707031e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 22.765650510787964s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.1920928955078125e-05s
INFO | --- Analysis for Bio2RDF::Gendr took 1091.9819226264954s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.7120611667633057s
Availability | VoID file availability check for Bio2RDF::Goa took 1.1704392433166504s
Extra | Recovery of all triples for Bio2RDF::Goa took 20.6257004737854s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.5005931854248047s
Amount of data | Number of triples check for Bio2RDF::Goa took 46.316893339157104s
Interoperability | New terms check for Bio2RDF::Goa took 43.152503490448s
Versatility | Languages check for Bio2RDF::Goa took 60.295068979263306s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.308701753616333s
Security | Check HTTPS for Bio2RDF::Goa took 0.18668341636657715s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.2870755195617676s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.32135438919067383s
Availability | RDF dump link check for Bio2RDF::Goa took 1.1490216255187988s
License | MR license check for Bio2RDF::Goa took 0.5921878814697266s
License | HR license check for Bio2RDF::Goa took 60.29647445678711s
Amount of data | Number of property check for Bio2RDF::Goa took 0.2835104465484619s
Understandability | Number of label check for Bio2RDF::Goa took 9.638840198516846s
Understandability | URI regex check for Bio2RDF::Goa took 0.7168545722961426s
Understandability | Vocabs check for Bio2RDF::Goa took 0.288801908493042s
Verifiability | Authors check for Bio2RDF::Goa took 0.32398056983947754s
Verifiability | Publishers check for Bio2RDF::Goa took 0.4401838779449463s
Performance | Throughput check for Bio2RDF::Goa took 11.874759912490845s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.8492181301116943s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.3403298854827881s
Interlinking | skos check for Bio2RDF::Goa took 0.6922988891601562s
Interlinking | skos check for Bio2RDF::Goa took 0.4192538261413574s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.28839659690856934s
Currency | Creation date check for Bio2RDF::Goa took 0.40915536880493164s
Currency | Modification date check for Bio2RDF::Goa took 0.30169129371643066s
Rep.Conc. | URIs length for Bio2RDF::Goa took 110.78770184516907s
Interoperability | New vocabularies check for Bio2RDF::Goa took 21.979575634002686s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.5259320735931396s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.2906372547149658s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.29839301109313965s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 7.048419237136841s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.9026563167572021s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.68326735496521s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.29560327529907227s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 65.63083028793335s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.4727516174316406s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 6.355238437652588s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.2917885780334473s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.63480186462402s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.6941921710968018s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.5123391151428223s
Security | Sign check for Bio2RDF::Goa took 0.31882357597351074s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 3.6985292434692383s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 1.3621392250061035s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.020056724548339844s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.000518798828125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.031990051269531e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 21.941388368606567s
Believability | Calculation of trust value for Bio2RDF::Goa took 1.1682510375976562e-05s
INFO | --- Analysis for Bio2RDF::Goa took 1081.0901296138763s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.6882338523864746s
Availability | VoID file availability check for Bio2RDF::Hgnc took 1.1880097389221191s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 19.967320919036865s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.478428602218628s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 45.28824424743652s
Interoperability | New terms check for Bio2RDF::Hgnc took 45.02722454071045s
Versatility | Languages check for Bio2RDF::Hgnc took 60.30619287490845s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.3159477710723877s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.19437623023986816s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.3064267635345459s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.2950444221496582s
Availability | RDF dump link check for Bio2RDF::Hgnc took 1.1259288787841797s
License | MR license check for Bio2RDF::Hgnc took 0.47878408432006836s
License | HR license check for Bio2RDF::Hgnc took 60.27771854400635s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.29135560989379883s
Understandability | Number of label check for Bio2RDF::Hgnc took 10.089099884033203s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.6714510917663574s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.2948780059814453s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.32987332344055176s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.4328751564025879s
Performance | Throughput check for Bio2RDF::Hgnc took 11.867120504379272s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.8415267467498779s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.31658482551574707s
Interlinking | skos check for Bio2RDF::Hgnc took 0.750206708908081s
Interlinking | skos check for Bio2RDF::Hgnc took 0.38620471954345703s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.2970571517944336s
Currency | Creation date check for Bio2RDF::Hgnc took 0.4452967643737793s
Currency | Modification date check for Bio2RDF::Hgnc took 0.2913079261779785s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 111.592440366745s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 23.404096841812134s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.5001261234283447s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.3413705825805664s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.3176741600036621s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 7.1042702198028564s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.8991200923919678s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6662867069244385s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.2871119976043701s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.60971093177795s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.5031967163085938s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 6.1798975467681885s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.2958176136016846s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.59409427642822s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7165548801422119s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.49205517768859863s
Security | Sign check for Bio2RDF::Hgnc took 0.29689860343933105s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 3.9336726665496826s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.6906473636627197s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.018328428268432617s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0005309581756591797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00011205673217773438s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 21.22361445426941s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.1920928955078125e-05s
INFO | --- Analysis for Bio2RDF::Hgnc took 1076.013659477234s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.7062802314758301s
Availability | VoID file availability check for Bio2RDF::Homologene took 1.1565239429473877s
Extra | Recovery of all triples for Bio2RDF::Homologene took 20.289886951446533s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.4749794006347656s
Amount of data | Number of triples check for Bio2RDF::Homologene took 45.51766347885132s
Interoperability | New terms check for Bio2RDF::Homologene took 43.471259355545044s
Versatility | Languages check for Bio2RDF::Homologene took 60.31289529800415s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.3050053119659424s
Security | Check HTTPS for Bio2RDF::Homologene took 0.17625927925109863s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.9164409637451172s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.3049771785736084s
Availability | RDF dump link check for Bio2RDF::Homologene took 1.1525309085845947s
License | MR license check for Bio2RDF::Homologene took 0.6138279438018799s
License | HR license check for Bio2RDF::Homologene took 60.29995512962341s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.30579686164855957s
Understandability | Number of label check for Bio2RDF::Homologene took 9.63408088684082s
Understandability | URI regex check for Bio2RDF::Homologene took 0.6899714469909668s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.30370569229125977s
Verifiability | Authors check for Bio2RDF::Homologene took 0.3142509460449219s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.4210360050201416s
Performance | Throughput check for Bio2RDF::Homologene took 12.009655714035034s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.8502399921417236s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.32307958602905273s
Interlinking | skos check for Bio2RDF::Homologene took 0.7090198993682861s
Interlinking | skos check for Bio2RDF::Homologene took 0.40434741973876953s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.30049705505371094s
Currency | Creation date check for Bio2RDF::Homologene took 0.4310941696166992s
Currency | Modification date check for Bio2RDF::Homologene took 0.30691957473754883s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 118.08323979377747s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 22.495104789733887s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.5438849925994873s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.2879939079284668s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.28983640670776367s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 7.31815505027771s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.9069101810455322s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6766073703765869s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.36394333839416504s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.65004515647888s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.504333734512329s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.315749168395996s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.326077938079834s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.64145874977112s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7101633548736572s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.5130693912506104s
Security | Sign check for Bio2RDF::Homologene took 0.3288743495941162s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 3.713756561279297s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.47269153594970703s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.018375158309936523s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0005369186401367188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 6.389617919921875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 24.943203687667847s
Believability | Calculation of trust value for Bio2RDF::Homologene took 1.1920928955078125e-05s
INFO | --- Analysis for Bio2RDF::Homologene took 1084.6369433403015s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 0.15527081489562988s
Availability | VoID file availability check for Bio2RDF::INOH took 7.62939453125e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.3642997741699219s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.018714189529418945s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0005240440368652344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 1.3589859008789062e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 1.049041748046875e-05s
INFO | --- Analysis for Bio2RDF::INOH took 2.8140861988067627s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.6906940937042236s
Availability | VoID file availability check for Bio2RDF::Interpro took 1.1897380352020264s
Extra | Recovery of all triples for Bio2RDF::Interpro took 19.814438104629517s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.4714105129241943s
Amount of data | Number of triples check for Bio2RDF::Interpro took 46.18541193008423s
Interoperability | New terms check for Bio2RDF::Interpro took 44.371307373046875s
Versatility | Languages check for Bio2RDF::Interpro took 60.29753065109253s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.3058583736419678s
Security | Check HTTPS for Bio2RDF::Interpro took 0.19916677474975586s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.305422306060791s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.29702091217041016s
Availability | RDF dump link check for Bio2RDF::Interpro took 1.2090628147125244s
License | MR license check for Bio2RDF::Interpro took 0.6389119625091553s
License | HR license check for Bio2RDF::Interpro took 60.29270887374878s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.3120396137237549s
Understandability | Number of label check for Bio2RDF::Interpro took 9.299680948257446s
Understandability | URI regex check for Bio2RDF::Interpro took 0.7092928886413574s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.31372618675231934s
Verifiability | Authors check for Bio2RDF::Interpro took 0.33223581314086914s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.43041515350341797s
Performance | Throughput check for Bio2RDF::Interpro took 11.93325924873352s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.8440291881561279s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.2982912063598633s
Interlinking | skos check for Bio2RDF::Interpro took 0.41502952575683594s
Interlinking | skos check for Bio2RDF::Interpro took 0.3897416591644287s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.2992706298828125s
Currency | Creation date check for Bio2RDF::Interpro took 0.43412065505981445s
Currency | Modification date check for Bio2RDF::Interpro took 0.29256510734558105s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 110.75871896743774s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 25.872719526290894s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.501816987991333s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.35648131370544434s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.2862362861633301s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 7.617215156555176s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.9171197414398193s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6726932525634766s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.373288631439209s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.43945121765137s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.5279552936553955s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.739035129547119s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.3100059032440186s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.58338117599487s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.7054314613342285s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.5181324481964111s
Security | Sign check for Bio2RDF::Interpro took 0.317108154296875s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 4.205079793930054s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.7972514629364014s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.018002986907958984s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0005309581756591797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00011396408081054688s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 23.063658237457275s
Believability | Calculation of trust value for Bio2RDF::Interpro took 1.33514404296875e-05s
INFO | --- Analysis for Bio2RDF::Interpro took 1084.0219941139221s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.16768240928649902s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.018259525299072266s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.8765110969543457s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.018815279006958008s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0005307197570800781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 8.96453857421875e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 1.1920928955078125e-05s
INFO | --- Analysis for Bio2RDF::Iproclass took 21.399359703063965s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.7529709339141846s
Availability | VoID file availability check for Bio2RDF::Irefindex took 1.2086272239685059s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 20.269822359085083s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.4877471923828125s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 46.17278337478638s
Interoperability | New terms check for Bio2RDF::Irefindex took 43.1286985874176s
Versatility | Languages check for Bio2RDF::Irefindex took 60.322214126586914s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.33403754234313965s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.19783306121826172s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.47922325134277344s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.2795586585998535s
Availability | RDF dump link check for Bio2RDF::Irefindex took 1.154353141784668s
License | MR license check for Bio2RDF::Irefindex took 0.4649074077606201s
License | HR license check for Bio2RDF::Irefindex took 60.29807996749878s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.3055744171142578s
Understandability | Number of label check for Bio2RDF::Irefindex took 9.484479188919067s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.7176580429077148s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.28417372703552246s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.3019089698791504s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.45113515853881836s
Performance | Throughput check for Bio2RDF::Irefindex took 11.901568174362183s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.8596646785736084s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.2977292537689209s
Interlinking | skos check for Bio2RDF::Irefindex took 0.5403993129730225s
Interlinking | skos check for Bio2RDF::Irefindex took 0.37865543365478516s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.31836652755737305s
Currency | Creation date check for Bio2RDF::Irefindex took 0.42334985733032227s
Currency | Modification date check for Bio2RDF::Irefindex took 0.3035576343536377s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 112.06945872306824s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 21.669759273529053s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.5066494941711426s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.33929944038391113s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.3202838897705078s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 7.1235291957855225s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.9018476009368896s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6717898845672607s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.3328368663787842s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 65.41479587554932s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.4791979789733887s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.577362537384033s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.3193392753601074s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.5908727645874s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.711214542388916s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.49535465240478516s
Security | Sign check for Bio2RDF::Irefindex took 0.31041526794433594s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 3.8717684745788574s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.8046963214874268s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.20292878150939941s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0006694793701171875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 9.489059448242188e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 23.797173261642456s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 1.3113021850585938e-05s
INFO | --- Analysis for Bio2RDF::Irefindex took 1077.8782250881195s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 0.6777365207672119s
Availability | VoID file availability check for Bio2RDF::KEGG took 7.3909759521484375e-06s
Extra | Recovery of all triples for Bio2RDF::KEGG took 20.136208534240723s
Performance | Total latancy measurement for Bio2RDF::KEGG took 1.5121486186981201s
Amount of data | Number of triples check for Bio2RDF::KEGG took 46.20262408256531s
Interoperability | New terms check for Bio2RDF::KEGG took 43.089722633361816s
Versatility | Languages check for Bio2RDF::KEGG took 60.30481696128845s
Interpretability | Number of blank nodes check for Bio2RDF::KEGG took 0.3197007179260254s
Security | Check HTTPS for Bio2RDF::KEGG took 0.2638273239135742s
Interpretability | RDF structures check for Bio2RDF::KEGG took 0.31166768074035645s
Versatility | Serialization formats check for Bio2RDF::KEGG took 0.29694271087646484s
Availability | RDF dump link check for Bio2RDF::KEGG took 1.1745355129241943s
License | MR license check for Bio2RDF::KEGG took 0.32354140281677246s
License | HR license check for Bio2RDF::KEGG took 60.282607078552246s
Amount of data | Number of property check for Bio2RDF::KEGG took 0.30388402938842773s
Understandability | Number of label check for Bio2RDF::KEGG took 9.299766302108765s
Understandability | URI regex check for Bio2RDF::KEGG took 0.7600347995758057s
Understandability | Vocabs check for Bio2RDF::KEGG took 0.28377389907836914s
Verifiability | Authors check for Bio2RDF::KEGG took 0.32407665252685547s
Verifiability | Publishers check for Bio2RDF::KEGG took 0.6099908351898193s
Performance | Throughput check for Bio2RDF::KEGG took 11.85952353477478s
Verifiability | Contribs. check for Bio2RDF::KEGG took 0.9925262928009033s
Interlinking | sameAs chians check for Bio2RDF::KEGG took 0.30328893661499023s
Interlinking | skos check for Bio2RDF::KEGG took 0.7595109939575195s
Interlinking | skos check for Bio2RDF::KEGG took 0.3987269401550293s
Timeliness | dataset update frequency check for Bio2RDF::KEGG took 0.3076612949371338s
Currency | Creation date check for Bio2RDF::KEGG took 0.41178250312805176s
Currency | Modification date check for Bio2RDF::KEGG took 0.302509069442749s
Rep.Conc. | URIs length for Bio2RDF::KEGG took 117.3294186592102s
Interoperability | New vocabularies check for Bio2RDF::KEGG took 23.188196182250977s
Consistency | Deprecated classes/propertiers check for Bio2RDF::KEGG took 0.5378174781799316s
Accuracy | Check Functional Property for Bio2RDF::KEGG took 0.29625582695007324s
Accuracy | Check Inverse Functional Property for Bio2RDF::KEGG took 0.31031227111816406s
Accuracy | Check Empty annotation labels for Bio2RDF::KEGG took 7.97586727142334s
Accuracy | Check White space in annotation for Bio2RDF::KEGG took 0.9058334827423096s
Accuracy | Check Datatype consistency for Bio2RDF::KEGG took 0.6741788387298584s
Consistency | Disjoint class check for Bio2RDF::KEGG took 0.2957582473754883s
Consistency | Check Misplaced properties for Bio2RDF::KEGG took 66.10603904724121s
Consistency | Misplaced classes for Bio2RDF::KEGG took 2.48467755317688s
Consistency | Check Ontology hijacking for Bio2RDF::KEGG took 6.689510345458984s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::KEGG took 1.348175287246704s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::KEGG took 61.627931356430054s
Conciseness | Check Extensional conciseness for Bio2RDF::KEGG took 0.7150297164916992s
Conciseness | Check Intensional conciseness for Bio2RDF::KEGG took 0.5438523292541504s
Security | Sign check for Bio2RDF::KEGG took 0.31699514389038086s
Availability | Check URIs Dereferenciability for Bio2RDF::KEGG took 3.9599449634552s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.713402509689331s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.01813030242919922s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0005190372467041016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 7.224082946777344e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::KEGG took 24.578887939453125s
Believability | Calculation of trust value for Bio2RDF::KEGG took 7.3909759521484375e-06s
INFO | --- Analysis for Bio2RDF::KEGG took 1080.2851676940918s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 0.15333223342895508s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 7.62939453125e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.49102306365966797s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.018719196319580078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0005588531494140625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 1.3113021850585938e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 6.532669067382812e-05s
INFO | --- Analysis for Bio2RDF::KEGG::BioPAX took 7.539224863052368s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.16361069679260254s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.017610549926757812s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.3855552673339844s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.021622419357299805s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0005242824554443359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 1.3113021850585938e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 1.1444091796875e-05s
INFO | --- Analysis for Bio2RDF::Linkedspl took 10.577901840209961s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.7119991779327393s
Availability | VoID file availability check for Bio2RDF::Lsr took 1.2006456851959229s
Extra | Recovery of all triples for Bio2RDF::Lsr took 19.466869831085205s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.4840974807739258s
Amount of data | Number of triples check for Bio2RDF::Lsr took 46.52307868003845s
Interoperability | New terms check for Bio2RDF::Lsr took 43.504427909851074s
Versatility | Languages check for Bio2RDF::Lsr took 60.2993221282959s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.3250858783721924s
Security | Check HTTPS for Bio2RDF::Lsr took 0.18454599380493164s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.44252634048461914s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.29769182205200195s
Availability | RDF dump link check for Bio2RDF::Lsr took 1.148463249206543s
License | MR license check for Bio2RDF::Lsr took 0.30728864669799805s
License | HR license check for Bio2RDF::Lsr took 60.29538321495056s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.29863739013671875s
Understandability | Number of label check for Bio2RDF::Lsr took 9.273336410522461s
Understandability | URI regex check for Bio2RDF::Lsr took 0.677825927734375s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.30124545097351074s
Verifiability | Authors check for Bio2RDF::Lsr took 0.2982656955718994s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.5397212505340576s
Performance | Throughput check for Bio2RDF::Lsr took 11.84602952003479s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.8325483798980713s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.317030668258667s
Interlinking | skos check for Bio2RDF::Lsr took 0.5952260494232178s
Interlinking | skos check for Bio2RDF::Lsr took 0.4300053119659424s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.28497767448425293s
Currency | Creation date check for Bio2RDF::Lsr took 0.42625999450683594s
Currency | Modification date check for Bio2RDF::Lsr took 0.29638671875s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 111.59104943275452s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 25.06898856163025s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.51363205909729s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.327239990234375s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.28272247314453125s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 7.305352687835693s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.9084353446960449s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.6657311916351318s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.45318031311035156s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 65.57620120048523s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.4528791904449463s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.832226991653442s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.325040340423584s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.641886472702026s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.707665205001831s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.5049047470092773s
Security | Sign check for Bio2RDF::Lsr took 0.32996511459350586s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 3.719691276550293s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.4203789234161377s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.018160104751586914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0005507469177246094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 7.724761962890625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 28.58270764350891s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.52587890625e-05s
INFO | --- Analysis for Bio2RDF::Lsr took 1083.2695093154907s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.6800832748413086s
Availability | VoID file availability check for Bio2RDF::Mesh took 1.1986706256866455s
Extra | Recovery of all triples for Bio2RDF::Mesh took 20.004770755767822s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.495211124420166s
Amount of data | Number of triples check for Bio2RDF::Mesh took 46.22661209106445s
Interoperability | New terms check for Bio2RDF::Mesh took 43.24206519126892s
Versatility | Languages check for Bio2RDF::Mesh took 60.311832904815674s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.3116030693054199s
Security | Check HTTPS for Bio2RDF::Mesh took 0.1862180233001709s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.464489221572876s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.2906224727630615s
Availability | RDF dump link check for Bio2RDF::Mesh took 1.155500888824463s
License | MR license check for Bio2RDF::Mesh took 0.6258869171142578s
License | HR license check for Bio2RDF::Mesh took 60.29455375671387s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.3329627513885498s
Understandability | Number of label check for Bio2RDF::Mesh took 9.97252893447876s
Understandability | URI regex check for Bio2RDF::Mesh took 0.6581089496612549s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.29601597785949707s
Verifiability | Authors check for Bio2RDF::Mesh took 0.3020813465118408s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.4408092498779297s
Performance | Throughput check for Bio2RDF::Mesh took 12.008785247802734s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.8252410888671875s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.30529069900512695s
Interlinking | skos check for Bio2RDF::Mesh took 0.8565075397491455s
Interlinking | skos check for Bio2RDF::Mesh took 0.41840243339538574s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.297041654586792s
Currency | Creation date check for Bio2RDF::Mesh took 0.4465973377227783s
Currency | Modification date check for Bio2RDF::Mesh took 0.30384302139282227s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 112.16914367675781s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 22.820611238479614s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.5093257427215576s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.2900857925415039s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.34712743759155273s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 7.688780307769775s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.8946681022644043s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6742925643920898s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.4773881435394287s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 65.91107487678528s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.54858136177063s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.491182088851929s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.3075487613677979s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.624069929122925s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.7238004207611084s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.5307950973510742s
Security | Sign check for Bio2RDF::Mesh took 0.3260955810546875s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 3.9822752475738525s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.9029707908630371s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.018541574478149414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0005190372467041016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.796287536621094e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 21.909348964691162s
Believability | Calculation of trust value for Bio2RDF::Mesh took 1.2874603271484375e-05s
INFO | --- Analysis for Bio2RDF::Mesh took 1086.4348783493042s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.6697211265563965s
Availability | VoID file availability check for Bio2RDF::Mgi took 1.1672067642211914s
Extra | Recovery of all triples for Bio2RDF::Mgi took 20.96208930015564s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.4542262554168701s
Amount of data | Number of triples check for Bio2RDF::Mgi took 45.788135290145874s
Interoperability | New terms check for Bio2RDF::Mgi took 44.31552505493164s
Versatility | Languages check for Bio2RDF::Mgi took 60.31064295768738s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.31536006927490234s
Security | Check HTTPS for Bio2RDF::Mgi took 0.1864311695098877s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.30622196197509766s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.29917073249816895s
Availability | RDF dump link check for Bio2RDF::Mgi took 1.1902039051055908s
License | MR license check for Bio2RDF::Mgi took 0.32543134689331055s
License | HR license check for Bio2RDF::Mgi took 60.28936958312988s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.3257408142089844s
Understandability | Number of label check for Bio2RDF::Mgi took 9.747428178787231s
Understandability | URI regex check for Bio2RDF::Mgi took 0.6955881118774414s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.29967284202575684s
Verifiability | Authors check for Bio2RDF::Mgi took 0.315169095993042s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.44236159324645996s
Performance | Throughput check for Bio2RDF::Mgi took 11.912755250930786s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.8252871036529541s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.302692174911499s
Interlinking | skos check for Bio2RDF::Mgi took 0.7771713733673096s
Interlinking | skos check for Bio2RDF::Mgi took 0.4116709232330322s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.29661130905151367s
Currency | Creation date check for Bio2RDF::Mgi took 0.42666101455688477s
Currency | Modification date check for Bio2RDF::Mgi took 0.2914621829986572s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 113.82182002067566s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 34.351481437683105s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.5080966949462891s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.30200815200805664s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.30170679092407227s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 8.029617309570312s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.9041347503662109s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6627297401428223s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.42800021171569824s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.65656208992004s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.5083096027374268s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 6.648801565170288s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.3026080131530762s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.60753130912781s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7279140949249268s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.8481378555297852s
Security | Sign check for Bio2RDF::Mgi took 0.309783935546875s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 3.8385627269744873s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 1.485766887664795s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.01965928077697754s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0005259513854980469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 9.489059448242188e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 24.063676834106445s
Believability | Calculation of trust value for Bio2RDF::Mgi took 1.1205673217773438e-05s
INFO | --- Analysis for Bio2RDF::Mgi took 1098.628877878189s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.6743764877319336s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 1.1592655181884766s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 20.49926996231079s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.4516007900238037s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 45.689605951309204s
Interoperability | New terms check for Bio2RDF::Ncbigene took 44.648305892944336s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.29862189292908s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.31192755699157715s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.17214727401733398s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.4620702266693115s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.2922329902648926s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 1.173137903213501s
License | MR license check for Bio2RDF::Ncbigene took 0.32741785049438477s
License | HR license check for Bio2RDF::Ncbigene took 60.30603384971619s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.3558309078216553s
Understandability | Number of label check for Bio2RDF::Ncbigene took 9.417898178100586s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.6964223384857178s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.2970724105834961s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.3052177429199219s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.4143807888031006s
Performance | Throughput check for Bio2RDF::Ncbigene took 11.946839809417725s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.962148904800415s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.33295202255249023s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.5515077114105225s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.41237568855285645s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.2927572727203369s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.4419395923614502s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.2955467700958252s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 111.80067801475525s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 30.602748155593872s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.5285229682922363s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.29988741874694824s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.3020625114440918s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 7.723075866699219s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.897789716720581s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.67354416847229s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.5907039642333984s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.77534437179565s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.4350361824035645s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.503905534744263s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.354156494140625s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.56212639808655s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.7076334953308105s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.5474512577056885s
Security | Sign check for Bio2RDF::Ncbigene took 0.3109140396118164s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 3.8552651405334473s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 1.026353359222412s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.018204927444458008s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0005331039428710938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012135505676269531s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 27.558019876480103s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 1.2874603271484375e-05s
INFO | --- Analysis for Bio2RDF::Ncbigene took 1102.959634065628s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.7228574752807617s
Availability | VoID file availability check for Bio2RDF::Ndc took 1.188981294631958s
Extra | Recovery of all triples for Bio2RDF::Ndc took 20.164020538330078s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.5119054317474365s
Amount of data | Number of triples check for Bio2RDF::Ndc took 45.783108949661255s
Interoperability | New terms check for Bio2RDF::Ndc took 43.59403204917908s
Versatility | Languages check for Bio2RDF::Ndc took 60.3058762550354s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.3237335681915283s
Security | Check HTTPS for Bio2RDF::Ndc took 0.1854846477508545s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.3092074394226074s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.31983184814453125s
Availability | RDF dump link check for Bio2RDF::Ndc took 1.1786396503448486s
License | MR license check for Bio2RDF::Ndc took 0.47751808166503906s
License | HR license check for Bio2RDF::Ndc took 60.28760504722595s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.3053581714630127s
Understandability | Number of label check for Bio2RDF::Ndc took 9.744018793106079s
Understandability | URI regex check for Bio2RDF::Ndc took 0.6712441444396973s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.2894167900085449s
Verifiability | Authors check for Bio2RDF::Ndc took 0.34502434730529785s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.4373295307159424s
Performance | Throughput check for Bio2RDF::Ndc took 11.878899097442627s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.8515455722808838s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.3113746643066406s
Interlinking | skos check for Bio2RDF::Ndc took 0.5567440986633301s
Interlinking | skos check for Bio2RDF::Ndc took 0.39424753189086914s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.31059932708740234s
Currency | Creation date check for Bio2RDF::Ndc took 0.4311094284057617s
Currency | Modification date check for Bio2RDF::Ndc took 0.2847251892089844s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 112.18555498123169s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 27.577264547348022s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.5512819290161133s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.28078532218933105s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.34148597717285156s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 7.490418434143066s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.9215102195739746s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6787712574005127s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.5285162925720215s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 65.76739883422852s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.504369020462036s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.50763726234436s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.3299570083618164s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.62448835372925s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7151710987091064s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.518390417098999s
Security | Sign check for Bio2RDF::Ndc took 0.30351948738098145s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 3.590463399887085s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.4598398208618164s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.018100738525390625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0005431175231933594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 4.363059997558594e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 25.66828155517578s
Believability | Calculation of trust value for Bio2RDF::Ndc took 7.3909759521484375e-06s
INFO | --- Analysis for Bio2RDF::Ndc took 1083.426058769226s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 0.15058445930480957s
Availability | VoID file availability check for Bio2RDF::NetPath took 3.814697265625e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.5485274791717529s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.018896102905273438s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0005228519439697266s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 1.1444091796875e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 6.9141387939453125e-06s
INFO | --- Analysis for Bio2RDF::NetPath took 123.54516696929932s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.20636272430419922s
Availability | VoID file availability check for Bio2RDF::neXtProt took 5.7220458984375e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.34637880325317383s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.01819753646850586s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0005383491516113281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 1.1920928955078125e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 6.9141387939453125e-06s
INFO | --- Analysis for Bio2RDF::neXtProt took 3.194173812866211s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.7042281627655029s
Availability | VoID file availability check for Bio2RDF::Omim took 1.1949126720428467s
Extra | Recovery of all triples for Bio2RDF::Omim took 20.735816955566406s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.482097864151001s
Amount of data | Number of triples check for Bio2RDF::Omim took 45.71449422836304s
Interoperability | New terms check for Bio2RDF::Omim took 42.97094130516052s
Versatility | Languages check for Bio2RDF::Omim took 60.300734519958496s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.3222084045410156s
Security | Check HTTPS for Bio2RDF::Omim took 0.16794061660766602s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.30097460746765137s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.29370665550231934s
Availability | RDF dump link check for Bio2RDF::Omim took 1.1718528270721436s
License | MR license check for Bio2RDF::Omim took 0.5413119792938232s
License | HR license check for Bio2RDF::Omim took 60.281085729599s
Amount of data | Number of property check for Bio2RDF::Omim took 0.3196737766265869s
Understandability | Number of label check for Bio2RDF::Omim took 9.445930242538452s
Understandability | URI regex check for Bio2RDF::Omim took 0.7087352275848389s
Understandability | Vocabs check for Bio2RDF::Omim took 0.2860996723175049s
Verifiability | Authors check for Bio2RDF::Omim took 0.3395051956176758s
Verifiability | Publishers check for Bio2RDF::Omim took 0.4214668273925781s
Performance | Throughput check for Bio2RDF::Omim took 11.810908079147339s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.8471403121948242s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.31110429763793945s
Interlinking | skos check for Bio2RDF::Omim took 0.8260412216186523s
Interlinking | skos check for Bio2RDF::Omim took 0.4298825263977051s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.30637407302856445s
Currency | Creation date check for Bio2RDF::Omim took 0.41271352767944336s
Currency | Modification date check for Bio2RDF::Omim took 0.30407071113586426s
Rep.Conc. | URIs length for Bio2RDF::Omim took 113.65849423408508s
Interoperability | New vocabularies check for Bio2RDF::Omim took 25.071381330490112s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.5422103404998779s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.2988755702972412s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.3256199359893799s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 7.66911244392395s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.9019832611083984s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6778097152709961s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.4960639476776123s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 65.75120568275452s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.5156209468841553s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 7.0830466747283936s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.3316915035247803s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.6763436794281s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.722813606262207s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.5074851512908936s
Security | Sign check for Bio2RDF::Omim took 0.32442402839660645s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 3.749903917312622s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.6828396320343018s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.01825714111328125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0005199909210205078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00014591217041015625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 23.047788381576538s
Believability | Calculation of trust value for Bio2RDF::Omim took 7.3909759521484375e-06s
INFO | --- Analysis for Bio2RDF::Omim took 1093.2299387454987s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 4.2438507080078125e-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.4741349220275879s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.01825690269470215s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0005779266357421875s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 4.00543212890625e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-omim-resources took 3.4358596801757812s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 1.5168087482452393s
Availability | VoID file availability check for Bio2RDF::Orphanet took 1.1813642978668213s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 20.276583194732666s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.453531265258789s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 45.99913549423218s
Interoperability | New terms check for Bio2RDF::Orphanet took 43.47048234939575s
Versatility | Languages check for Bio2RDF::Orphanet took 60.28469634056091s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.3169691562652588s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.2105851173400879s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.30112552642822266s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.2976257801055908s
Availability | RDF dump link check for Bio2RDF::Orphanet took 1.2945630550384521s
License | MR license check for Bio2RDF::Orphanet took 0.303408145904541s
License | HR license check for Bio2RDF::Orphanet took 60.289873361587524s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.30948328971862793s
Understandability | Number of label check for Bio2RDF::Orphanet took 9.460922956466675s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.686032772064209s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.29273200035095215s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.2969086170196533s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.4205048084259033s
Performance | Throughput check for Bio2RDF::Orphanet took 11.788480043411255s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.8486635684967041s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.295074462890625s
Interlinking | skos check for Bio2RDF::Orphanet took 0.402585506439209s
Interlinking | skos check for Bio2RDF::Orphanet took 0.4197521209716797s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.2997615337371826s
Currency | Creation date check for Bio2RDF::Orphanet took 0.43097853660583496s
Currency | Modification date check for Bio2RDF::Orphanet took 0.3028559684753418s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 111.47494101524353s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 25.066282987594604s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.5511856079101562s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.2975654602050781s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.30695629119873047s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 7.3295276165008545s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.9089832305908203s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6686229705810547s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.48872923851013184s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 66.10299301147461s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.465768337249756s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.222559690475464s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.3541762828826904s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.635345458984375s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7111818790435791s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.5064759254455566s
Security | Sign check for Bio2RDF::Orphanet took 0.29918384552001953s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 3.829624652862549s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.7920944690704346s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.2190418243408203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0005192756652832031s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 9.059906005859375e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 28.272876262664795s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 1.5497207641601562e-05s
INFO | --- Analysis for Bio2RDF::Orphanet took 1089.2880506515503s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.9775192737579346s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.017360210418701172s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.36771225929260254s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.019673824310302734s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0005397796630859375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 1.3589859008789062e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 1.1682510375976562e-05s
INFO | --- Analysis for Bio2RDF::Pathwaycommons took 11.313375234603882s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.7062883377075195s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 1.2059071063995361s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 20.885419368743896s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.48378586769104s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 46.26977276802063s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 43.842787981033325s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.30789351463318s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.3295776844024658s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.17762088775634766s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.3063483238220215s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.3107774257659912s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 1.1253793239593506s
License | MR license check for Bio2RDF::Pharmgkb took 0.5094790458679199s
License | HR license check for Bio2RDF::Pharmgkb took 60.299760818481445s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.3112032413482666s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 9.653115034103394s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.7243690490722656s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.3207859992980957s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.33754992485046387s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.4190809726715088s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.918533325195312s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.8540663719177246s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.31073951721191406s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.7977211475372314s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.4125039577484131s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.31221914291381836s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.4405548572540283s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.3152899742126465s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 111.27645421028137s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 27.648657083511353s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.513599157333374s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.30373215675354004s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.3139002323150635s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 7.272673606872559s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.8997023105621338s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6782290935516357s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.4411296844482422s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 65.49189019203186s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.4688491821289062s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 6.6898651123046875s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.2986767292022705s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.61799478530884s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7109758853912354s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.5401418209075928s
Security | Sign check for Bio2RDF::Pharmgkb took 0.3081014156341553s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 4.033228397369385s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 1.4594054222106934s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.017914772033691406s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.00052642822265625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.724761962890625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 29.853015661239624s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 1.1682510375976562e-05s
INFO | --- Analysis for Bio2RDF::Pharmgkb took 1100.212303161621s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 0.15710067749023438s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 6.67572021484375e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 1.6786205768585205s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.018506526947021484s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0005199909210205078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 2.1696090698242188e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 1.1920928955078125e-05s
INFO | --- Analysis for Bio2RDF::PharmGKB::BioPAX took 10.509480953216553s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 0.16108489036560059s
Availability | VoID file availability check for Bio2RDF::PID took 7.152557373046875e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.46196675300598145s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.018154621124267578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0005238056182861328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 1.1920928955078125e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 1.1444091796875e-05s
INFO | --- Analysis for Bio2RDF::PID took 2.51593279838562s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 0.964280366897583s
Availability | VoID file availability check for Bio2RDF::PubChem took 7.3909759521484375e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 1.2251863479614258s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.018187761306762695s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0005307197570800781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 1.3113021850585938e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 1.33514404296875e-05s
INFO | --- Analysis for Bio2RDF::PubChem took 6.89403223991394s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.7672586441040039s
Availability | VoID file availability check for Bio2RDF::Pubmed took 1.1914653778076172s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 20.252615451812744s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.5040335655212402s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 45.992239475250244s
Interoperability | New terms check for Bio2RDF::Pubmed took 43.554102420806885s
Versatility | Languages check for Bio2RDF::Pubmed took 60.2945921421051s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.324951171875s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.19558191299438477s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 1.0621814727783203s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.30885839462280273s
Availability | RDF dump link check for Bio2RDF::Pubmed took 1.2157700061798096s
License | MR license check for Bio2RDF::Pubmed took 0.5983076095581055s
License | HR license check for Bio2RDF::Pubmed took 60.305806398391724s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.2990114688873291s
Understandability | Number of label check for Bio2RDF::Pubmed took 9.768029928207397s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.6904027462005615s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.2765388488769531s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.3293571472167969s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.42944884300231934s
Performance | Throughput check for Bio2RDF::Pubmed took 11.831213474273682s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 1.0669806003570557s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.3216547966003418s
Interlinking | skos check for Bio2RDF::Pubmed took 1.0037143230438232s
Interlinking | skos check for Bio2RDF::Pubmed took 0.422954797744751s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.3111002445220947s
Currency | Creation date check for Bio2RDF::Pubmed took 0.4143552780151367s
Currency | Modification date check for Bio2RDF::Pubmed took 0.30886006355285645s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 113.40189623832703s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 29.360758543014526s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.538367748260498s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.34130120277404785s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.2952687740325928s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 8.21924901008606s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.9053134918212891s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6680748462677002s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.5979709625244141s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.5079128742218s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.5841026306152344s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 7.286200046539307s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.3617596626281738s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.61622500419617s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.7058398723602295s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.5500555038452148s
Security | Sign check for Bio2RDF::Pubmed took 0.3238525390625s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 3.917977809906006s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.638951301574707s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.01959824562072754s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0005159378051757812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00014829635620117188s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 27.02568030357361s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 1.1682510375976562e-05s
INFO | --- Analysis for Bio2RDF::Pubmed took 1096.9667789936066s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 0.1599714756011963s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.016817092895507812s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.4536905288696289s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.020337581634521484s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0005440711975097656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 7.677078247070312e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 1.2874603271484375e-05s
INFO | --- Analysis for Bio2RDF::Reactome took 13.673110485076904s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 0.1832139492034912s
Availability | VoID file availability check for Bio2RDF::Rhea took 7.3909759521484375e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.38936829566955566s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.018099308013916016s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0005419254302978516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 5.245208740234375e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 1.0728836059570312e-05s
INFO | --- Analysis for Bio2RDF::Rhea took 6.2778966426849365s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.16136860847473145s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.01699042320251465s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.3758082389831543s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.02010822296142578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0005478858947753906s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.462501525878906e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 1.4066696166992188e-05s
INFO | --- Analysis for Bio2RDF::Sabiork took 9.825997591018677s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.6917376518249512s
Availability | VoID file availability check for Bio2RDF::Sgd took 1.1740427017211914s
Extra | Recovery of all triples for Bio2RDF::Sgd took 21.062166213989258s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.5028228759765625s
Amount of data | Number of triples check for Bio2RDF::Sgd took 54.71780562400818s
Interoperability | New terms check for Bio2RDF::Sgd took 44.92508935928345s
Versatility | Languages check for Bio2RDF::Sgd took 60.294228076934814s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.33112645149230957s
Security | Check HTTPS for Bio2RDF::Sgd took 0.17061996459960938s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.29274749755859375s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.2906339168548584s
Availability | RDF dump link check for Bio2RDF::Sgd took 1.172443151473999s
License | MR license check for Bio2RDF::Sgd took 0.34554481506347656s
License | HR license check for Bio2RDF::Sgd took 60.29843616485596s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.3134140968322754s
Understandability | Number of label check for Bio2RDF::Sgd took 9.277475833892822s
Understandability | URI regex check for Bio2RDF::Sgd took 0.7130300998687744s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.3177762031555176s
Verifiability | Authors check for Bio2RDF::Sgd took 0.3081963062286377s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.40602827072143555s
Performance | Throughput check for Bio2RDF::Sgd took 11.912992238998413s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.9855537414550781s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.3176558017730713s
Interlinking | skos check for Bio2RDF::Sgd took 0.7710282802581787s
Interlinking | skos check for Bio2RDF::Sgd took 0.41228699684143066s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.2868678569793701s
Currency | Creation date check for Bio2RDF::Sgd took 0.4207289218902588s
Currency | Modification date check for Bio2RDF::Sgd took 0.27913856506347656s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 112.55645775794983s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 24.71025276184082s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.517054557800293s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.3052365779876709s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.29392361640930176s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 7.544407844543457s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.9040682315826416s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6613123416900635s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.36679506301879883s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 65.7343761920929s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.560628890991211s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 6.866330146789551s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.3484420776367188s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.66545248031616s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.7091109752655029s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.5498762130737305s
Security | Sign check for Bio2RDF::Sgd took 0.31339478492736816s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 4.037546873092651s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.9039835929870605s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.18674468994140625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0005309581756591797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00011324882507324219s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 38.264240741729736s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.6450881958007812e-05s
INFO | --- Analysis for Bio2RDF::Sgd took 1107.3877682685852s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 8.58306884765625e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 6.4373016357421875e-06s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.4525728225708008s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.018500804901123047s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0005164146423339844s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.719329833984375e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-sgd-resources took 2.8489692211151123s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.6836869716644287s
Availability | VoID file availability check for Bio2RDF::Sider took 1.1431713104248047s
Extra | Recovery of all triples for Bio2RDF::Sider took 20.840976238250732s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.502399206161499s
Amount of data | Number of triples check for Bio2RDF::Sider took 46.558361530303955s
Interoperability | New terms check for Bio2RDF::Sider took 45.12193012237549s
Versatility | Languages check for Bio2RDF::Sider took 60.31490206718445s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.30379652976989746s
Security | Check HTTPS for Bio2RDF::Sider took 0.1958308219909668s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.32277584075927734s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.30339956283569336s
Availability | RDF dump link check for Bio2RDF::Sider took 1.1898062229156494s
License | MR license check for Bio2RDF::Sider took 0.3532099723815918s
License | HR license check for Bio2RDF::Sider took 60.30718159675598s
Amount of data | Number of property check for Bio2RDF::Sider took 0.38172388076782227s
Understandability | Number of label check for Bio2RDF::Sider took 9.560867309570312s
Understandability | URI regex check for Bio2RDF::Sider took 0.69789719581604s
Understandability | Vocabs check for Bio2RDF::Sider took 0.31099963188171387s
Verifiability | Authors check for Bio2RDF::Sider took 0.3084721565246582s
Verifiability | Publishers check for Bio2RDF::Sider took 0.41901087760925293s
Performance | Throughput check for Bio2RDF::Sider took 11.866694688796997s
Verifiability | Contribs. check for Bio2RDF::Sider took 1.590477705001831s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.33193349838256836s
Interlinking | skos check for Bio2RDF::Sider took 0.7272467613220215s
Interlinking | skos check for Bio2RDF::Sider took 0.45642590522766113s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.2999117374420166s
Currency | Creation date check for Bio2RDF::Sider took 0.41242098808288574s
Currency | Modification date check for Bio2RDF::Sider took 0.2967662811279297s
Rep.Conc. | URIs length for Bio2RDF::Sider took 112.8203182220459s
Interoperability | New vocabularies check for Bio2RDF::Sider took 22.53721523284912s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.5818891525268555s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.2979848384857178s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.29502344131469727s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 7.746986150741577s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.8979384899139404s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6709685325622559s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.30391645431518555s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 65.92159104347229s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.4932544231414795s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 6.966304063796997s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.3500065803527832s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.6108238697052s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7149174213409424s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.5221078395843506s
Security | Sign check for Bio2RDF::Sider took 0.30608510971069336s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 3.834148645401001s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 1.2829580307006836s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.22323250770568848s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0005321502685546875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.2438507080078125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 23.346179962158203s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.2874603271484375e-05s
INFO | --- Analysis for Bio2RDF::Sider took 1087.9318346977234s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 0.15912604331970215s
Availability | VoID file availability check for Bio2RDF::SPIKE took 8.344650268554688e-06s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.44191479682922363s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.0183413028717041s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0005567073822021484s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 1.3828277587890625e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 1.2874603271484375e-05s
INFO | --- Analysis for Bio2RDF::SPIKE took 4.021037340164185s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 8.440017700195312e-05s
Availability | VoID file availability check for bio2rdf-taxon took 7.3909759521484375e-06s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.41190147399902344s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.019583463668823242s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0005290508270263672s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.673004150390625e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-taxon took 2.7003183364868164s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.6984474658966064s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 1.1751148700714111s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 20.09951114654541s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.5131573677062988s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 46.02878427505493s
Interoperability | New terms check for Bio2RDF::Taxonomy took 43.5996150970459s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.308881759643555s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.31279730796813965s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.18514060974121094s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.30212831497192383s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.3223848342895508s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 1.1523983478546143s
License | MR license check for Bio2RDF::Taxonomy took 0.6351981163024902s
License | HR license check for Bio2RDF::Taxonomy took 60.29621624946594s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.3019406795501709s
Understandability | Number of label check for Bio2RDF::Taxonomy took 9.652663946151733s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.682884693145752s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.3119490146636963s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.30882692337036133s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.5623874664306641s
Performance | Throughput check for Bio2RDF::Taxonomy took 11.90433669090271s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.3524200916290283s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.32036805152893066s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.5639104843139648s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.4036250114440918s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.3069579601287842s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.42699432373046875s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.30189061164855957s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 111.6935658454895s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 25.179303884506226s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.515326738357544s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.3685455322265625s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.29854607582092285s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 8.011568784713745s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8987674713134766s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.674689531326294s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.5495471954345703s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 65.8233048915863s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.9270622730255127s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 6.49283766746521s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.3202645778656006s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.624974489212036s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7078397274017334s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.500328540802002s
Security | Sign check for Bio2RDF::Taxonomy took 0.32574892044067383s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 3.8878591060638428s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 2.532214641571045s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.18485569953918457s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0006678104400634766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010752677917480469s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 21.424426794052124s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 1.0728836059570312e-05s
INFO | --- Analysis for Bio2RDF::Taxonomy took 1107.5456540584564s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.16291475296020508s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.015417337417602539s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 1.2243866920471191s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.01780986785888672s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0005125999450683594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 1.2874603271484375e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 1.33514404296875e-05s
INFO | --- Analysis for Bio2RDF::Wikipathways took 22.332635641098022s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.6875567436218262s
Availability | VoID file availability check for Bio2RDF::Wormbase took 1.1811015605926514s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 19.84856939315796s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.4802510738372803s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 45.78490900993347s
Interoperability | New terms check for Bio2RDF::Wormbase took 43.91629195213318s
Versatility | Languages check for Bio2RDF::Wormbase took 60.313493728637695s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.3270688056945801s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.18473076820373535s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.3197140693664551s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.31356072425842285s
Availability | RDF dump link check for Bio2RDF::Wormbase took 1.145582914352417s
License | MR license check for Bio2RDF::Wormbase took 0.4703948497772217s
License | HR license check for Bio2RDF::Wormbase took 60.319830894470215s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.3179337978363037s
Understandability | Number of label check for Bio2RDF::Wormbase took 9.886226654052734s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.7078440189361572s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.296950101852417s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.30423951148986816s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.4056417942047119s
Performance | Throughput check for Bio2RDF::Wormbase took 11.863654851913452s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.8551199436187744s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.2928147315979004s
Interlinking | skos check for Bio2RDF::Wormbase took 0.6554265022277832s
Interlinking | skos check for Bio2RDF::Wormbase took 0.4088144302368164s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.2871072292327881s
Currency | Creation date check for Bio2RDF::Wormbase took 0.42101049423217773s
Currency | Modification date check for Bio2RDF::Wormbase took 0.2935943603515625s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 111.15643191337585s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 24.847673416137695s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.5478413105010986s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.3142247200012207s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.2733933925628662s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 6.931520938873291s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.9012646675109863s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6774470806121826s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.2877624034881592s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 65.53762745857239s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.442350387573242s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 6.723243951797485s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.3159372806549072s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.62381863594055s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7124898433685303s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.5222113132476807s
Security | Sign check for Bio2RDF::Wormbase took 0.33237195014953613s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 3.9262282848358154s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.7539100646972656s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.018486499786376953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0005757808685302734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 9.489059448242188e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 24.500577926635742s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 7.867813110351562e-06s
INFO | --- Analysis for Bio2RDF::Wormbase took 1085.2087631225586s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.32809996604919434s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.5875747203826904s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.952803373336792s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.018335819244384766s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0005269050598144531s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.893013000488281e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 7.62939453125e-06s
INFO | --- Analysis for Biographical Directory of the United States Congress took 3.8367760181427s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.09074521064758301s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.015758514404296875s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.41379594802856445s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0205843448638916s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0005247592926025391s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.430511474609375e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.1920928955078125e-05s
INFO | --- Analysis for A Short Biographical Dictionary of English Literature (RKBExplorer) took 2.8161840438842773s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 9.322166442871094e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 3.9722390174865723s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.3548457622528076s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.01980423927307129s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0005204677581787109s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 4.124641418457031e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 1.2159347534179688e-05s
INFO | --- Analysis for BioLOD for Protein Data Bank Japan took 15.042941331863403s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.7472476959228516s
Availability | VoID file availability check for BioModels RDF took 0.25296926498413086s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.37930822372436523s
Reputation | Calculation of the PageRank for BioModels RDF took 0.019010543823242188s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 4.935264587402344e-05s
Believability | Calculation of trust value for BioModels RDF took 1.2636184692382812e-05s
INFO | --- Analysis for BioModels RDF took 3.751720666885376s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 8.821487426757812e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 2.31655216217041s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.35594964027404785s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.01848459243774414s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0005509853363037109s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006465911865234375s
Believability | Calculation of trust value for Amphibian gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for Amphibian gross anatomy took 10.905876398086548s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 8.654594421386719e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 1.9007115364074707s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.3677065372467041s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.018819570541381836s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0005438327789306641s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0003101825714111328s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 1.0013580322265625e-05s
INFO | --- Analysis for ABA Adult Mouse Brain took 9.350571870803833s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 8.702278137207031e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 1.9137687683105469s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.45696020126342773s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.018502473831176758s
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.0005452632904052734s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015490055084228516s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 8.106231689453125e-06s
INFO | --- Analysis for Cancer Research and Management ACGT Master Ontology took 9.909384489059448s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 8.320808410644531e-05s
Availability | VoID file availability check for Animal natural history and life history took 1.918863296508789s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.3803551197052002s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.018183469772338867s
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.0005612373352050781s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003380775451660156s
Believability | Calculation of trust value for Animal natural history and life history took 9.298324584960938e-06s
INFO | --- Analysis for Animal natural history and life history took 10.382612466812134s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 1.9035913944244385s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.372999906539917s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.01906108856201172s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0005362033843994141s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.00046706199645996094s
Believability | Calculation of trust value for Anatomical Entity Ontology took 7.867813110351562e-06s
INFO | --- Analysis for Anatomical Entity Ontology took 9.804912805557251s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 1.894728183746338s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.3748924732208252s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.018369197845458984s
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.0005371570587158203s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.001020669937133789s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 8.344650268554688e-06s
INFO | --- Analysis for Adverse Event Reporting ontology took 9.15581727027893s
Availability | SPARQL endpoint availability check for AI/RHEUM took 8.416175842285156e-05s
Availability | VoID file availability check for AI/RHEUM took 1.952862024307251s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.3663771152496338s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.01832437515258789s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0005388259887695312s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0004172325134277344s
Believability | Calculation of trust value for AI/RHEUM took 8.344650268554688e-06s
INFO | --- Analysis for AI/RHEUM took 10.117417097091675s
Availability | SPARQL endpoint availability check for Amino Acid took 8.511543273925781e-05s
Availability | VoID file availability check for Amino Acid took 1.894662618637085s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.3555731773376465s
Reputation | Calculation of the PageRank for Amino Acid took 0.018778324127197266s
Interlinking | Calculation of Degree of Connection for Amino Acid took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Amino Acid took 0.0005459785461425781s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.0002636909484863281s
Believability | Calculation of trust value for Amino Acid took 8.58306884765625e-06s
INFO | --- Analysis for Amino Acid took 9.665075778961182s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 8.702278137207031e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 1.8979833126068115s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.4458141326904297s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.018238544464111328s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0005292892456054688s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.00028133392333984375s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 7.62939453125e-06s
INFO | --- Analysis for Ascomycete phenotype ontology took 9.207255601882935s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 8.654594421386719e-05s
Availability | VoID file availability check for African Traditional Medicine took 1.9012203216552734s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.4150807857513428s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.018406391143798828s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0005466938018798828s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00023865699768066406s
Believability | Calculation of trust value for African Traditional Medicine took 9.298324584960938e-06s
INFO | --- Analysis for African Traditional Medicine took 9.951247215270996s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 8.940696716308594e-05s
Availability | VoID file availability check for Amphibian taxonomy took 1.9006967544555664s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.36592602729797363s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.018465518951416016s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0005357265472412109s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 9.036064147949219e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 4.291534423828125e-06s
INFO | --- Analysis for Amphibian taxonomy took 10.599994659423828s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 9.131431579589844e-05s
Availability | VoID file availability check for BioAssay Ontology took 1.9064903259277344s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.3470935821533203s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.01842355728149414s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.00052642822265625s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013425350189208984s
Believability | Calculation of trust value for BioAssay Ontology took 5.602836608886719e-05s
INFO | --- Analysis for BioAssay Ontology took 9.65464735031128s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 4.1484832763671875e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 1.8980636596679688s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.6784791946411133s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.018798112869262695s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0005288124084472656s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0003948211669921875s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 8.821487426757812e-06s
INFO | --- Analysis for Basic Vertebrate Anatomy took 10.396708965301514s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 8.988380432128906e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 1.916428565979004s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.38747096061706543s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.0184323787689209s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0005223751068115234s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003180503845214844s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 8.821487426757812e-06s
INFO | --- Analysis for Breast Cancer Grading Ontology took 9.795385122299194s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 8.988380432128906e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 1.907576560974121s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.3799121379852295s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.01824951171875s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0005421638488769531s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.001405954360961914s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 8.821487426757812e-06s
INFO | --- Analysis for Bone Dysplasia Ontology took 11.220717668533325s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 8.821487426757812e-05s
Availability | VoID file availability check for Basic Formal Ontology took 1.8832731246948242s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.3639547824859619s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.01824498176574707s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0005238056182861328s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0004985332489013672s
Believability | Calculation of trust value for Basic Formal Ontology took 8.58306884765625e-06s
INFO | --- Analysis for Basic Formal Ontology took 10.128781795501709s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 8.630752563476562e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 1.910600185394287s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.39596104621887207s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.01823115348815918s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0005300045013427734s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007450580596923828s
Believability | Calculation of trust value for Bleeding History Phenotype took 8.821487426757812e-06s
INFO | --- Analysis for Bleeding History Phenotype took 9.987223148345947s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 8.916854858398438e-05s
Availability | VoID file availability check for Bilateria anatomy took 1.9351916313171387s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.36876893043518066s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.018172025680541992s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0005314350128173828s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.00044465065002441406s
Believability | Calculation of trust value for Bilateria anatomy took 1.0013580322265625e-05s
INFO | --- Analysis for Bilateria anatomy took 11.003693580627441s
Availability | SPARQL endpoint availability check for BIRNLex took 8.940696716308594e-05s
Availability | VoID file availability check for BIRNLex took 2.1170096397399902s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.38909363746643066s
Reputation | Calculation of the PageRank for BIRNLex took 0.018297433853149414s
Interlinking | Calculation of Degree of Connection for BIRNLex took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BIRNLex took 0.0005314350128173828s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0015494823455810547s
Believability | Calculation of trust value for BIRNLex took 7.867813110351562e-06s
INFO | --- Analysis for BIRNLex took 9.539377450942993s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 5.626678466796875e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 1.8853955268859863s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.47328972816467285s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.018278837203979492s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.000576019287109375s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007412433624267578s
Believability | Calculation of trust value for Gene Regulation Ontology took 8.58306884765625e-06s
INFO | --- Analysis for Gene Regulation Ontology took 10.72028923034668s
Availability | SPARQL endpoint availability check for BioPAX took 9.274482727050781e-05s
Availability | VoID file availability check for BioPAX took 1.8910417556762695s
Completeness | Calculation of interlinking completeness for BioPAX took 0.3570120334625244s
Reputation | Calculation of the PageRank for BioPAX took 0.018720388412475586s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0005404949188232422s
Interlinking | Calculation of Clustering coefficient for BioPAX took 0.00011110305786132812s
Believability | Calculation of trust value for BioPAX took 1.0251998901367188e-05s
INFO | --- Analysis for BioPAX took 9.469577550888062s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 1.9378385543823242s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.42296886444091797s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.018366098403930664s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0005211830139160156s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003235340118408203s
Believability | Calculation of trust value for Biomedical Resource Ontology took 9.5367431640625e-06s
INFO | --- Analysis for Biomedical Resource Ontology took 10.19201946258545s
Availability | SPARQL endpoint availability check for Spatial Ontology took 0.00010561943054199219s
Availability | VoID file availability check for Spatial Ontology took 1.9136748313903809s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.47844672203063965s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.018224716186523438s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0005249977111816406s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00021123886108398438s
Believability | Calculation of trust value for Spatial Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for Spatial Ontology took 10.050351619720459s
Availability | SPARQL endpoint availability check for BioTop took 4.2438507080078125e-05s
Availability | VoID file availability check for BioTop took 1.911590576171875s
Completeness | Calculation of interlinking completeness for BioTop took 0.9869439601898193s
Reputation | Calculation of the PageRank for BioTop took 0.018770694732666016s
Interlinking | Calculation of Degree of Connection for BioTop took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for BioTop took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006413459777832031s
Believability | Calculation of trust value for BioTop took 9.059906005859375e-06s
INFO | --- Analysis for BioTop took 10.030563354492188s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.5299530029296875e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 1.9128081798553467s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.36853885650634766s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.018529891967773438s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0005426406860351562s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0009174346923828125s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 8.821487426757812e-06s
INFO | --- Analysis for BRENDA tissue / enzyme source took 12.123172044754028s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 9.1552734375e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 1.9175422191619873s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.4235193729400635s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.018976688385009766s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018739700317382812s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 9.298324584960938e-06s
INFO | --- Analysis for Cancer Chemoprevention Ontology took 10.30337119102478s
Availability | SPARQL endpoint availability check for CAO took 8.916854858398438e-05s
Availability | VoID file availability check for CAO took 1.890681266784668s
Completeness | Calculation of interlinking completeness for CAO took 0.4192953109741211s
Reputation | Calculation of the PageRank for CAO took 0.01837325096130371s
Interlinking | Calculation of Degree of Connection for CAO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CAO took 0.0005269050598144531s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0005967617034912109s
Believability | Calculation of trust value for CAO took 9.298324584960938e-06s
INFO | --- Analysis for CAO took 9.699077844619751s
Availability | SPARQL endpoint availability check for CareLex took 0.0001246929168701172s
Availability | VoID file availability check for CareLex took 1.9354381561279297s
Completeness | Calculation of interlinking completeness for CareLex took 0.37430238723754883s
Reputation | Calculation of the PageRank for CareLex took 0.018532514572143555s
Interlinking | Calculation of Degree of Connection for CareLex took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CareLex took 0.0005855560302734375s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.078315734863281e-05s
Believability | Calculation of trust value for CareLex took 9.298324584960938e-06s
INFO | --- Analysis for CareLex took 10.006423234939575s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 1.8841021060943604s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.37094998359680176s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.018484830856323242s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0005545616149902344s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0008103847503662109s
Believability | Calculation of trust value for Cell Cycle Ontology took 9.298324584960938e-06s
INFO | --- Analysis for Cell Cycle Ontology took 10.368356704711914s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 1.9152705669403076s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.45139384269714355s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.01906108856201172s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0005266666412353516s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.0002605915069580078s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 9.059906005859375e-06s
INFO | --- Analysis for Comparative Data Analysis Ontology took 10.115909814834595s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 8.416175842285156e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 1.9702532291412354s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.4993870258331299s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.018372058868408203s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0005834102630615234s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0008802413940429688s
Believability | Calculation of trust value for Chemical entities of biological interest took 8.344650268554688e-06s
INFO | --- Analysis for Chemical entities of biological interest took 10.766994714736938s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 8.487701416015625e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 1.904289960861206s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.5284955501556396s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.018567562103271484s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0005199909210205078s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.00025391578674316406s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 8.344650268554688e-06s
INFO | --- Analysis for Systems Chemical Biology/Chemogenomics took 10.516026020050049s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 8.392333984375e-05s
Availability | VoID file availability check for Chemical Information Ontology took 1.9054794311523438s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.3796968460083008s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.018378257751464844s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0005552768707275391s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007679462432861328s
Believability | Calculation of trust value for Chemical Information Ontology took 9.059906005859375e-06s
INFO | --- Analysis for Chemical Information Ontology took 9.955972671508789s
Availability | SPARQL endpoint availability check for Cell type took 4.2438507080078125e-05s
Availability | VoID file availability check for Cell type took 1.9107646942138672s
Completeness | Calculation of interlinking completeness for Cell type took 0.41551947593688965s
Reputation | Calculation of the PageRank for Cell type took 0.018697738647460938s
Interlinking | Calculation of Degree of Connection for Cell type took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cell type took 0.0005288124084472656s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003833770751953125s
Believability | Calculation of trust value for Cell type took 9.059906005859375e-06s
INFO | --- Analysis for Cell type took 9.908779621124268s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 8.940696716308594e-05s
Availability | VoID file availability check for Cell Line Ontology took 1.9078724384307861s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.509406566619873s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.018475770950317383s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0005431175231933594s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008203983306884766s
Believability | Calculation of trust value for Cell Line Ontology took 9.059906005859375e-06s
INFO | --- Analysis for Cell Line Ontology took 10.067025661468506s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 5.435943603515625e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 1.9448440074920654s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.5527629852294922s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.01833820343017578s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0005297660827636719s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.0001671314239501953s
Believability | Calculation of trust value for Clinical Measurement Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for Clinical Measurement Ontology took 12.284221410751343s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 5.269050598144531e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 1.980713129043579s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.44008946418762207s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.018247604370117188s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0005450248718261719s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.0002086162567138672s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 5.245208740234375e-06s
INFO | --- Analysis for Computational Neuroscience Ontology took 9.978852987289429s
Availability | SPARQL endpoint availability check for Wheat trait took 4.172325134277344e-05s
Availability | VoID file availability check for Wheat trait took 1.90521240234375s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.3716585636138916s
Reputation | Calculation of the PageRank for Wheat trait took 0.018300771713256836s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0005273818969726562s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.507469177246094e-05s
Believability | Calculation of trust value for Wheat trait took 1.0013580322265625e-05s
INFO | --- Analysis for Wheat trait took 9.679931640625s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.38690185546875e-05s
Availability | VoID file availability check for Cognitive Atlas took 1.902940273284912s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.38379406929016113s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.01822352409362793s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0005979537963867188s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.00034999847412109375s
Believability | Calculation of trust value for Cognitive Atlas took 4.76837158203125e-06s
INFO | --- Analysis for Cognitive Atlas took 9.98033332824707s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 8.440017700195312e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 1.8991265296936035s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.3476588726043701s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.01825547218322754s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0005300045013427734s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007574558258056641s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for Cognitive Paradigm Ontology took 10.030917882919312s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 8.511543273925781e-05s
Availability | VoID file availability check for Current Procedural Terminology took 1.921077013015747s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.35074329376220703s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.0184781551361084s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0005583763122558594s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.00044083595275878906s
Believability | Calculation of trust value for Current Procedural Terminology took 5.7220458984375e-06s
INFO | --- Analysis for Current Procedural Terminology took 9.807644605636597s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 4.410743713378906e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 1.9164936542510986s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 2.25187349319458s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.018633365631103516s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0005228519439697266s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017819404602050781s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 5.0067901611328125e-06s
INFO | --- Analysis for CRISP Thesaurus, 2006 took 11.442192792892456s
Availability | SPARQL endpoint availability check for COSTART took 4.172325134277344e-05s
Availability | VoID file availability check for COSTART took 1.8878412246704102s
Completeness | Calculation of interlinking completeness for COSTART took 0.38353776931762695s
Reputation | Calculation of the PageRank for COSTART took 0.018294572830200195s
Interlinking | Calculation of Degree of Connection for COSTART took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for COSTART took 0.0005538463592529297s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009796619415283203s
Believability | Calculation of trust value for COSTART took 9.775161743164062e-06s
INFO | --- Analysis for COSTART took 9.404876470565796s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.4345855712890625e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 1.9002296924591064s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.43965601921081543s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.018190860748291016s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0005269050598144531s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0004935264587402344s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 5.4836273193359375e-06s
INFO | --- Analysis for Common Terminology Criteria for Adverse Events took 9.820108413696289s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 4.291534423828125e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 1.9115245342254639s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.3623678684234619s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.02109980583190918s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004534721374511719s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 9.298324584960938e-06s
INFO | --- Analysis for Cerebrotendinous xanthomatosis took 9.85540246963501s
Availability | SPARQL endpoint availability check for Dendritic cell took 9.441375732421875e-05s
Availability | VoID file availability check for Dendritic cell took 1.9044346809387207s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.41653966903686523s
Reputation | Calculation of the PageRank for Dendritic cell took 0.018258333206176758s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0005228519439697266s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.0002887248992919922s
Believability | Calculation of trust value for Dendritic cell took 7.867813110351562e-06s
INFO | --- Analysis for Dendritic cell took 9.180946350097656s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 0.00012993812561035156s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 1.9231462478637695s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.3666982650756836s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.01856064796447754s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0005321502685546875s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.940696716308594e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 8.821487426757812e-06s
INFO | --- Analysis for Dictyostelium discoideum anatomy took 9.570910453796387s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 9.34600830078125e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 1.8977851867675781s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.36756205558776855s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.01934671401977539s
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.0005450248718261719s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0010344982147216797s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 1.0013580322265625e-05s
INFO | --- Analysis for Ontology for Drug Discovery Investigations took 9.969472169876099s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Diagnostic Ontology took 1.9249372482299805s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.4944469928741455s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.019485950469970703s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0005307197570800781s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.58306884765625e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for Diagnostic Ontology took 9.900124073028564s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 9.202957153320312e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 1.8836417198181152s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.35442280769348145s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.018886804580688477s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0005402565002441406s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.0001704692840576172s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 9.059906005859375e-06s
INFO | --- Analysis for DIKB-Evidence-Ontology took 9.686297416687012s
Availability | SPARQL endpoint availability check for Human disease ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Human disease ontology took 1.9008288383483887s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.3664848804473877s
Reputation | Calculation of the PageRank for Human disease ontology took 0.02041769027709961s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0005729198455810547s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006296634674072266s
Believability | Calculation of trust value for Human disease ontology took 9.5367431640625e-06s
INFO | --- Analysis for Human disease ontology took 10.588624477386475s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 8.392333984375e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 1.9104158878326416s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.42143774032592773s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.018590688705444336s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0005259513854980469s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008215904235839844s
Believability | Calculation of trust value for Electrocardiography Ontology took 9.5367431640625e-06s
INFO | --- Analysis for Electrocardiography Ontology took 9.629941701889038s
Availability | SPARQL endpoint availability check for Evidence codes took 9.369850158691406e-05s
Availability | VoID file availability check for Evidence codes took 1.9069569110870361s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.36553955078125s
Reputation | Calculation of the PageRank for Evidence codes took 0.018395662307739258s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0005192756652832031s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 1.2636184692382812e-05s
Believability | Calculation of trust value for Evidence codes took 8.106231689453125e-06s
INFO | --- Analysis for Evidence codes took 9.320970058441162s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 1.901552677154541s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.43813061714172363s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.018172740936279297s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0005502700805664062s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017735958099365234s
Believability | Calculation of trust value for Experimental Factor Ontology took 9.298324584960938e-06s
INFO | --- Analysis for Experimental Factor Ontology took 10.047312498092651s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 8.726119995117188e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 1.9055454730987549s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.3726968765258789s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.01827692985534668s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0005400180816650391s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011730194091796875s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 9.298324584960938e-06s
INFO | --- Analysis for Human developmental anatomy, timed version took 9.321594715118408s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 8.797645568847656e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 1.8994178771972656s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.3647606372833252s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.020695924758911133s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0005304813385009766s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007326602935791016s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 1.0013580322265625e-05s
INFO | --- Analysis for Human developmental anatomy, abstract version took 8.853073120117188s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 8.749961853027344e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 1.9221575260162354s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.36582446098327637s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.020417451858520508s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005228519439697266s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 9.298324584960938e-06s
INFO | --- Analysis for Human developmental anatomy, abstract version, v2 took 9.050272941589355s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 0.0001277923583984375s
Availability | VoID file availability check for Mouse gross anatomy and development took 1.915207862854004s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.43392300605773926s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.018696308135986328s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0005245208740234375s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 1.3113021850585938e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 9.298324584960938e-06s
INFO | --- Analysis for Mouse gross anatomy and development took 10.080626249313354s
Availability | SPARQL endpoint availability check for Environment Ontology took 0.00011920928955078125s
Availability | VoID file availability check for Environment Ontology took 2.040175437927246s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.4286031723022461s
Reputation | Calculation of the PageRank for Environment Ontology took 0.018715620040893555s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0005519390106201172s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0003859996795654297s
Believability | Calculation of trust value for Environment Ontology took 1.049041748046875e-05s
INFO | --- Analysis for Environment Ontology took 11.14915156364441s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 8.654594421386719e-05s
Availability | VoID file availability check for Plant environmental conditions took 1.939229965209961s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.9045534133911133s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.021090269088745117s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0005238056182861328s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.0003025531768798828s
Believability | Calculation of trust value for Plant environmental conditions took 9.298324584960938e-06s
INFO | --- Analysis for Plant environmental conditions took 10.583859920501709s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 8.58306884765625e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 1.9281678199768066s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.4624791145324707s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.018462181091308594s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0005474090576171875s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012331008911132812s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 9.059906005859375e-06s
INFO | --- Analysis for Cardiac Electrophysiology Ontology took 11.279529809951782s
Availability | SPARQL endpoint availability check for Epilepsy took 9.751319885253906e-05s
Availability | VoID file availability check for Epilepsy took 1.9996795654296875s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.3600897789001465s
Reputation | Calculation of the PageRank for Epilepsy took 0.018228530883789062s
Interlinking | Calculation of Degree of Connection for Epilepsy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Epilepsy took 0.0005228519439697266s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.0001270771026611328s
Believability | Calculation of trust value for Epilepsy took 9.059906005859375e-06s
INFO | --- Analysis for Epilepsy took 9.829511880874634s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 0.00010633468627929688s
Availability | VoID file availability check for eagle-i research resource ontology took 1.9121861457824707s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.3556668758392334s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.01816391944885254s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0005679130554199219s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011601448059082031s
Believability | Calculation of trust value for eagle-i research resource ontology took 9.775161743164062e-06s
INFO | --- Analysis for eagle-i research resource ontology took 10.405800819396973s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 8.511543273925781e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 1.9092323780059814s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.3677976131439209s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.019271373748779297s
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.0006091594696044922s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011751651763916016s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 9.775161743164062e-06s
INFO | --- Analysis for eVOC (Expressed Sequence Annotation for Humans) took 9.795623779296875s
Availability | SPARQL endpoint availability check for ExO took 0.00010061264038085938s
Availability | VoID file availability check for ExO took 1.8984487056732178s
Completeness | Calculation of interlinking completeness for ExO took 0.3695037364959717s
Reputation | Calculation of the PageRank for ExO took 0.018712997436523438s
Interlinking | Calculation of Degree of Connection for ExO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ExO took 0.0005488395690917969s
Interlinking | Calculation of Clustering coefficient for ExO took 0.0002815723419189453s
Believability | Calculation of trust value for ExO took 5.0067901611328125e-06s
INFO | --- Analysis for ExO took 10.123583316802979s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 8.702278137207031e-05s
Availability | VoID file availability check for Fungal gross anatomy took 1.8857481479644775s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.3646399974822998s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.02022075653076172s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.00055694580078125s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.0001220703125s
Believability | Calculation of trust value for Fungal gross anatomy took 9.5367431640625e-06s
INFO | --- Analysis for Fungal gross anatomy took 10.15221357345581s
Availability | SPARQL endpoint availability check for Biological imaging methods took 8.606910705566406e-05s
Availability | VoID file availability check for Biological imaging methods took 1.9074335098266602s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.3651723861694336s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.019862651824951172s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0005500316619873047s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00022792816162109375s
Believability | Calculation of trust value for Biological imaging methods took 1.049041748046875e-05s
INFO | --- Analysis for Biological imaging methods took 9.94155740737915s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 0.00012874603271484375s
Availability | VoID file availability check for Drosophila gross anatomy took 1.930405855178833s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.4582843780517578s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.018047809600830078s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0005218982696533203s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006341934204101562s
Believability | Calculation of trust value for Drosophila gross anatomy took 1.049041748046875e-05s
INFO | --- Analysis for Drosophila gross anatomy took 10.031057357788086s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 0.00013566017150878906s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 1.9009361267089844s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.359813928604126s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.019579172134399414s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0005209445953369141s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004353523254394531s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 9.059906005859375e-06s
INFO | --- Analysis for FlyBase Controlled Vocabulary took 10.060177326202393s
Availability | SPARQL endpoint availability check for Drosophila development took 4.124641418457031e-05s
Availability | VoID file availability check for Drosophila development took 2.045175552368164s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.44942426681518555s
Reputation | Calculation of the PageRank for Drosophila development took 0.018274545669555664s
Interlinking | Calculation of Degree of Connection for Drosophila development took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Drosophila development took 0.0005221366882324219s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.315376281738281e-05s
Believability | Calculation of trust value for Drosophila development took 9.059906005859375e-06s
INFO | --- Analysis for Drosophila development took 9.892807960510254s
Availability | SPARQL endpoint availability check for Fly taxonomy took 8.654594421386719e-05s
Availability | VoID file availability check for Fly taxonomy took 1.9158272743225098s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.4286463260650635s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.019637107849121094s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0005271434783935547s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003612041473388672s
Believability | Calculation of trust value for Fly taxonomy took 9.5367431640625e-06s
INFO | --- Analysis for Fly taxonomy took 11.27573561668396s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 8.654594421386719e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 1.908846139907837s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.3629753589630127s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.018080949783325195s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0005457401275634766s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00023245811462402344s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 8.344650268554688e-06s
INFO | --- Analysis for FDA Medical Devices (2010) took 11.228313207626343s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for Family Health History Ontology took 1.9422760009765625s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.3646202087402344s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.01828765869140625s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0005295276641845703s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.00040841102600097656s
Believability | Calculation of trust value for Family Health History Ontology took 6.723403930664062e-05s
INFO | --- Analysis for Family Health History Ontology took 8.784466743469238s
Availability | SPARQL endpoint availability check for Influenza Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Influenza Ontology took 1.8915350437164307s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.36824512481689453s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.018072128295898438s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0005345344543457031s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0010306835174560547s
Believability | Calculation of trust value for Influenza Ontology took 8.344650268554688e-06s
INFO | --- Analysis for Influenza Ontology took 11.307259798049927s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 8.559226989746094e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 1.8952171802520752s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.3863191604614258s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.018175363540649414s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0005500316619873047s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.437301635742188e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 8.821487426757812e-06s
INFO | --- Analysis for Foundational Model of Anatomy took 9.525935411453247s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 8.797645568847656e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 1.928037166595459s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.5062341690063477s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.018252134323120117s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0005297660827636719s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.0001354217529296875s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 8.106231689453125e-06s
INFO | --- Analysis for Fission Yeast Phenotype Ontology took 9.385701894760132s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 8.535385131835938e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 1.893357515335083s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.49031496047973633s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.0195620059967041s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0005464553833007812s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 9.417533874511719e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 8.106231689453125e-06s
INFO | --- Analysis for GeoSpecies Ontology took 10.67930555343628s
Availability | SPARQL endpoint availability check for General Formal Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for General Formal Ontology took 1.892409086227417s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.4675941467285156s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.01811671257019043s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0005304813385009766s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00016617774963378906s
Believability | Calculation of trust value for General Formal Ontology took 8.58306884765625e-06s
INFO | --- Analysis for General Formal Ontology took 9.319122552871704s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 8.821487426757812e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 1.9109828472137451s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.3790569305419922s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.01878213882446289s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0005192756652832031s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0005891323089599609s
Believability | Calculation of trust value for General Formal Ontology: Biology took 9.298324584960938e-06s
INFO | --- Analysis for General Formal Ontology: Biology took 10.02240514755249s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.1961669921875e-05s
Availability | VoID file availability check for Gene Ontology Extension took 1.9335048198699951s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.8887948989868164s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.01841425895690918s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0008552074432373047s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0009930133819580078s
Believability | Calculation of trust value for Gene Ontology Extension took 9.298324584960938e-06s
INFO | --- Analysis for Gene Ontology Extension took 10.386065006256104s
Availability | SPARQL endpoint availability check for Gene Ontology took 0.00010371208190917969s
Availability | VoID file availability check for Gene Ontology took 1.898838996887207s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.3650064468383789s
Reputation | Calculation of the PageRank for Gene Ontology took 0.0183560848236084s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.000514984130859375s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008549690246582031s
Believability | Calculation of trust value for Gene Ontology took 8.106231689453125e-06s
INFO | --- Analysis for Gene Ontology took 9.23650312423706s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 0.00010156631469726562s
Availability | VoID file availability check for Cereal Plant Development took 1.8824985027313232s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 1.123568058013916s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.018291950225830078s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0005927085876464844s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 1.2159347534179688e-05s
Believability | Calculation of trust value for Cereal Plant Development took 7.867813110351562e-06s
INFO | --- Analysis for Cereal Plant Development took 12.966088056564331s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 8.58306884765625e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 1.9163882732391357s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.8743901252746582s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.018680572509765625s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0005197525024414062s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004374980926513672s
Believability | Calculation of trust value for Cereal plant gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for Cereal plant gross anatomy took 15.29060983657837s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 1.922804355621338s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.3469810485839844s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.018485546112060547s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0005321502685546875s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007467269897460938s
Believability | Calculation of trust value for Gene Regulation Ontology took 9.298324584960938e-06s
INFO | --- Analysis for Gene Regulation Ontology took 9.462852716445923s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 0.000125885009765625s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 1.9385600090026855s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.36051106452941895s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.018483638763427734s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0005426406860351562s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005700588226318359s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 9.5367431640625e-06s
INFO | --- Analysis for Hymenoptera Anatomy Ontology took 10.316395044326782s
Availability | SPARQL endpoint availability check for HCPCS took 8.630752563476562e-05s
Availability | VoID file availability check for HCPCS took 1.8965864181518555s
Completeness | Calculation of interlinking completeness for HCPCS took 0.439929723739624s
Reputation | Calculation of the PageRank for HCPCS took 0.019552230834960938s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0005729198455810547s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00025534629821777344s
Believability | Calculation of trust value for HCPCS took 9.775161743164062e-06s
INFO | --- Analysis for HCPCS took 11.02244520187378s
Availability | SPARQL endpoint availability check for Health Level Seven took 4.410743713378906e-05s
Availability | VoID file availability check for Health Level Seven took 1.900622844696045s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.8921551704406738s
Reputation | Calculation of the PageRank for Health Level Seven took 0.018532752990722656s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0005507469177246094s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0013225078582763672s
Believability | Calculation of trust value for Health Level Seven took 1.2636184692382812e-05s
INFO | --- Analysis for Health Level Seven took 11.335314512252808s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 8.678436279296875e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 1.9132447242736816s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.3884310722351074s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0005245208740234375s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.00034546852111816406s
Believability | Calculation of trust value for HEALTH_INDICATORS took 9.298324584960938e-06s
INFO | --- Analysis for HEALTH_INDICATORS took 9.37446141242981s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 8.606910705566406e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 1.9142322540283203s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.362438440322876s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.018139123916625977s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0005247592926025391s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 1.239776611328125e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 8.821487426757812e-06s
INFO | --- Analysis for Ontology of homology and related concepts in biology took 8.885314226150513s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 8.7738037109375e-05s
Availability | VoID file availability check for HOM-HARVARD took 1.9630632400512695s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.380643367767334s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.01872849464416504s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0005397796630859375s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 1.430511474609375e-05s
Believability | Calculation of trust value for HOM-HARVARD took 9.5367431640625e-06s
INFO | --- Analysis for HOM-HARVARD took 10.121782541275024s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 1.9163599014282227s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.5013878345489502s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.01833176612854004s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006563663482666016s
Believability | Calculation of trust value for Human Phenotype Ontology took 9.5367431640625e-06s
INFO | --- Analysis for Human Phenotype Ontology took 10.192068576812744s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 8.797645568847656e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 1.91646146774292s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.3791935443878174s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.018168210983276367s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0005259513854980469s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010330677032470703s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for Host Pathogen Interactions Ontology took 10.422921657562256s
Availability | SPARQL endpoint availability check for HUGO took 0.00010561943054199219s
Availability | VoID file availability check for HUGO took 1.8999159336090088s
Completeness | Calculation of interlinking completeness for HUGO took 0.3665616512298584s
Reputation | Calculation of the PageRank for HUGO took 0.020993709564208984s
Interlinking | Calculation of Degree of Connection for HUGO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HUGO took 0.0005362033843994141s
Interlinking | Calculation of Clustering coefficient for HUGO took 8.416175842285156e-05s
Believability | Calculation of trust value for HUGO took 9.059906005859375e-06s
INFO | --- Analysis for HUGO took 9.719706058502197s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Information Artifact Ontology took 1.8816986083984375s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.3684868812561035s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.018610715866088867s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0005245208740234375s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006635189056396484s
Believability | Calculation of trust value for Information Artifact Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for Information Artifact Ontology took 10.969441890716553s
Availability | SPARQL endpoint availability check for ICD10 took 9.036064147949219e-05s
Availability | VoID file availability check for ICD10 took 1.9143741130828857s
Completeness | Calculation of interlinking completeness for ICD10 took 0.5516040325164795s
Reputation | Calculation of the PageRank for ICD10 took 0.018970966339111328s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0005443096160888672s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0008265972137451172s
Believability | Calculation of trust value for ICD10 took 1.1444091796875e-05s
INFO | --- Analysis for ICD10 took 11.04949402809143s
Availability | SPARQL endpoint availability check for ICD10CM took 8.988380432128906e-05s
Availability | VoID file availability check for ICD10CM took 1.8909668922424316s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.4793548583984375s
Reputation | Calculation of the PageRank for ICD10CM took 0.01850605010986328s
Interlinking | Calculation of Degree of Connection for ICD10CM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ICD10CM took 0.0005366802215576172s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.00061798095703125s
Believability | Calculation of trust value for ICD10CM took 9.298324584960938e-06s
INFO | --- Analysis for ICD10CM took 10.50447678565979s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 8.559226989746094e-05s
Availability | VoID file availability check for ICD-10-PCS took 1.909740924835205s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.3673698902130127s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.01846170425415039s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0005295276641845703s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00018024444580078125s
Believability | Calculation of trust value for ICD-10-PCS took 1.0728836059570312e-05s
INFO | --- Analysis for ICD-10-PCS took 12.594075679779053s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 8.797645568847656e-05s
Availability | VoID file availability check for International Classification of Diseases took 1.8843882083892822s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.37011170387268066s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.018194198608398438s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0005359649658203125s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006392002105712891s
Believability | Calculation of trust value for International Classification of Diseases took 8.58306884765625e-06s
INFO | --- Analysis for International Classification of Diseases took 9.753763675689697s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 8.988380432128906e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 1.929567813873291s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.36428284645080566s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.01971578598022461s
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.0005323886871337891s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004680156707763672s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 8.344650268554688e-06s
INFO | --- Analysis for International Classification of Functioning, Disability and Health (ICF) took 9.98834490776062s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 8.702278137207031e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 1.906527042388916s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 1.3365042209625244s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.018961429595947266s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0005476474761962891s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012624263763427734s
Believability | Calculation of trust value for International Classification for Nursing Practice took 8.344650268554688e-06s
INFO | --- Analysis for International Classification for Nursing Practice took 11.232452869415283s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 8.726119995117188e-05s
Availability | VoID file availability check for International Classification of Primary Care took 1.8995635509490967s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 1.338017225265503s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.018652677536010742s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0005309581756591797s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0004572868347167969s
Believability | Calculation of trust value for International Classification of Primary Care took 9.5367431640625e-06s
INFO | --- Analysis for International Classification of Primary Care took 11.023389101028442s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 8.416175842285156e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 1.8986003398895264s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.36774373054504395s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.018770217895507812s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0005321502685546875s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008425712585449219s
Believability | Calculation of trust value for ICPC-2 PLUS took 5.7220458984375e-06s
INFO | --- Analysis for ICPC-2 PLUS took 10.152842998504639s
Availability | SPARQL endpoint availability check for ICPS Network took 4.8160552978515625e-05s
Availability | VoID file availability check for ICPS Network took 1.9114041328430176s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.43251729011535645s
Reputation | Calculation of the PageRank for ICPS Network took 0.018375158309936523s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0005331039428710938s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00022125244140625s
Believability | Calculation of trust value for ICPS Network took 7.62939453125e-06s
INFO | --- Analysis for ICPS Network took 11.328225135803223s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 1.9149260520935059s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.4292480945587158s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.018276214599609375s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0005323886871337891s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008473396301269531s
Believability | Calculation of trust value for Infectious Disease Ontology took 9.298324584960938e-06s
INFO | --- Analysis for Infectious Disease Ontology took 9.715153694152832s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 6.437301635742188e-05s
Availability | VoID file availability check for Brucellosis Ontology took 1.9037044048309326s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.36579346656799316s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.018476009368896484s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0005331039428710938s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011637210845947266s
Believability | Calculation of trust value for Brucellosis Ontology took 8.821487426757812e-06s
INFO | --- Analysis for Brucellosis Ontology took 9.748435497283936s
Availability | SPARQL endpoint availability check for Malaria Ontology took 8.797645568847656e-05s
Availability | VoID file availability check for Malaria Ontology took 1.9097261428833008s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.36899638175964355s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.0182647705078125s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0005197525024414062s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0013041496276855469s
Believability | Calculation of trust value for Malaria Ontology took 8.106231689453125e-06s
INFO | --- Analysis for Malaria Ontology took 9.984455108642578s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 8.893013000488281e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 3.5571489334106445s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.4126262664794922s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.01849079132080078s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0005726814270019531s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0003199577331542969s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 9.059906005859375e-06s
INFO | --- Analysis for Event (INOH pathway ontology) took 11.436557292938232s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 8.821487426757812e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 1.8819568157196045s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.3865067958831787s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.018193721771240234s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0005173683166503906s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.0001456737518310547s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 8.106231689453125e-06s
INFO | --- Analysis for IMGT-ONTOLOGY took 9.233392715454102s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 8.678436279296875e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 1.9176108837127686s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.5565524101257324s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.01816558837890625s
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.0005292892456054688s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005142688751220703s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 9.059906005859375e-06s
INFO | --- Analysis for Molecule role (INOH Protein name/family name ontology) took 9.347423076629639s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Interaction Network Ontology took 1.8949415683746338s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 1.1694080829620361s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.01871347427368164s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0005342960357666016s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0008106231689453125s
Believability | Calculation of trust value for Interaction Network Ontology took 9.775161743164062e-06s
INFO | --- Analysis for Interaction Network Ontology took 10.610004901885986s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 8.869171142578125e-05s
Availability | VoID file availability check for Hewan Invertebrata took 1.9080629348754883s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.35647082328796387s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.018617868423461914s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0005319118499755859s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 1.2636184692382812e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 1.049041748046875e-05s
INFO | --- Analysis for Hewan Invertebrata took 10.106045484542847s
Availability | SPARQL endpoint availability check for IxnO took 9.036064147949219e-05s
Availability | VoID file availability check for IxnO took 1.8952994346618652s
Completeness | Calculation of interlinking completeness for IxnO took 0.44715309143066406s
Reputation | Calculation of the PageRank for IxnO took 0.020507097244262695s
Interlinking | Calculation of Degree of Connection for IxnO took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for IxnO took 0.0005185604095458984s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00018215179443359375s
Believability | Calculation of trust value for IxnO took 9.059906005859375e-06s
INFO | --- Analysis for IxnO took 9.34819221496582s
Availability | SPARQL endpoint availability check for SysMO-JERM took 9.131431579589844e-05s
Availability | VoID file availability check for SysMO-JERM took 1.916536808013916s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.36781787872314453s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.01995563507080078s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0005197525024414062s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.00038170814514160156s
Believability | Calculation of trust value for SysMO-JERM took 8.821487426757812e-06s
INFO | --- Analysis for SysMO-JERM took 8.940115690231323s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 1.9228506088256836s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.360276460647583s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.01824355125427246s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0005123615264892578s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 1.1444091796875e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 8.106231689453125e-06s
INFO | --- Analysis for Kinetic Simulation Algorithm Ontology took 8.94032335281372s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.029273986816406e-05s
Availability | VoID file availability check for Loggerhead nesting took 1.8950867652893066s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.37705421447753906s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.020407915115356445s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0005288124084472656s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00020170211791992188s
Believability | Calculation of trust value for Loggerhead nesting took 9.059906005859375e-06s
INFO | --- Analysis for Loggerhead nesting took 9.582691431045532s
Availability | SPARQL endpoint availability check for Lipid Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Lipid Ontology took 1.8889169692993164s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.36760902404785156s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.019901514053344727s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0005254745483398438s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00020313262939453125s
Believability | Calculation of trust value for Lipid Ontology took 9.059906005859375e-06s
INFO | --- Analysis for Lipid Ontology took 9.16040825843811s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 5.340576171875e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 1.8943181037902832s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.8693692684173584s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.018272876739501953s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018672943115234375s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 1.0251998901367188e-05s
INFO | --- Analysis for Logical Observation Identifier Names and Codes took 10.854459762573242s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 8.7738037109375e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 1.9171340465545654s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.36417627334594727s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.01841568946838379s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0005500316619873047s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006835460662841797s
Believability | Calculation of trust value for Mouse adult gross anatomy took 9.059906005859375e-06s
INFO | --- Analysis for Mouse adult gross anatomy took 9.366431951522827s
Availability | SPARQL endpoint availability check for Multiple alignment took 0.0001163482666015625s
Availability | VoID file availability check for Multiple alignment took 1.8953239917755127s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.36929750442504883s
Reputation | Calculation of the PageRank for Multiple alignment took 0.018725872039794922s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0005254745483398438s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00021004676818847656s
Believability | Calculation of trust value for Multiple alignment took 9.298324584960938e-06s
INFO | --- Analysis for Multiple alignment took 10.330755472183228s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 8.988380432128906e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 1.9126548767089844s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.44333434104919434s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.018520593643188477s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0005397796630859375s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006866455078125s
Believability | Calculation of trust value for Minimal anatomical terminology took 1.0251998901367188e-05s
INFO | --- Analysis for Minimal anatomical terminology took 9.929418325424194s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 8.797645568847656e-05s
Availability | VoID file availability check for Breast tissue cell lines took 1.9169280529022217s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.34316325187683105s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.019500255584716797s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0005359649658203125s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004298686981201172s
Believability | Calculation of trust value for Breast tissue cell lines took 1.0251998901367188e-05s
INFO | --- Analysis for Breast tissue cell lines took 10.195533990859985s
Availability | SPARQL endpoint availability check for Cell line ontology took 8.797645568847656e-05s
Availability | VoID file availability check for Cell line ontology took 1.9265015125274658s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.38915300369262695s
Reputation | Calculation of the PageRank for Cell line ontology took 0.01860976219177246s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0005404949188232422s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007421970367431641s
Believability | Calculation of trust value for Cell line ontology took 9.5367431640625e-06s
INFO | --- Analysis for Cell line ontology took 10.195601224899292s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Cell line ontology took 1.9242799282073975s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.36605119705200195s
Reputation | Calculation of the PageRank for Cell line ontology took 0.018162250518798828s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0005295276641845703s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0014498233795166016s
Believability | Calculation of trust value for Cell line ontology took 4.76837158203125e-06s
INFO | --- Analysis for Cell line ontology took 9.753790616989136s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 8.559226989746094e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 1.9062378406524658s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.6621489524841309s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.019236326217651367s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0005326271057128906s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.00024008750915527344s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 9.5367431640625e-06s
INFO | --- Analysis for MIxS Controlled Vocabularies took 9.6115083694458s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 9.083747863769531e-05s
Availability | VoID file availability check for Master Drug Data Base took 1.9021832942962646s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.36346936225891113s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.01831841468811035s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0005385875701904297s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00017786026000976562s
Believability | Calculation of trust value for Master Drug Data Base took 8.344650268554688e-06s
INFO | --- Analysis for Master Drug Data Base took 10.064563751220703s
Availability | SPARQL endpoint availability check for MedDRA took 8.7738037109375e-05s
Availability | VoID file availability check for MedDRA took 1.8890430927276611s
Completeness | Calculation of interlinking completeness for MedDRA took 0.38461732864379883s
Reputation | Calculation of the PageRank for MedDRA took 0.01847362518310547s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.0006339550018310547s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.001294851303100586s
Believability | Calculation of trust value for MedDRA took 9.775161743164062e-06s
INFO | --- Analysis for MedDRA took 10.449703693389893s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 8.392333984375e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 1.9088108539581299s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.8655378818511963s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.019672393798828125s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0005841255187988281s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0010101795196533203s
Believability | Calculation of trust value for MedlinePlus Health Topics took 1.0251998901367188e-05s
INFO | --- Analysis for MedlinePlus Health Topics took 9.676133871078491s
Availability | SPARQL endpoint availability check for MeGO took 9.298324584960938e-05s
Availability | VoID file availability check for MeGO took 1.9305534362792969s
Completeness | Calculation of interlinking completeness for MeGO took 0.35625195503234863s
Reputation | Calculation of the PageRank for MeGO took 0.01873922348022461s
Interlinking | Calculation of Degree of Connection for MeGO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MeGO took 0.0005464553833007812s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00014638900756835938s
Believability | Calculation of trust value for MeGO took 9.059906005859375e-06s
INFO | --- Analysis for MeGO took 9.543654441833496s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 0.00010657310485839844s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 1.9178307056427002s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.41956210136413574s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.018201112747192383s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.001973390579223633s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 1.0728836059570312e-05s
INFO | --- Analysis for MESH Thesaurus (OWL version) took 12.367707967758179s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 8.535385131835938e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 1.9174981117248535s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.3857853412628174s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.01854681968688965s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0005457401275634766s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006139278411865234s
Believability | Calculation of trust value for Mental Functioning Ontology took 7.867813110351562e-06s
INFO | --- Analysis for Mental Functioning Ontology took 9.391286373138428s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 8.940696716308594e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 1.8930253982543945s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.36327266693115234s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.018209218978881836s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0005550384521484375s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005738735198974609s
Believability | Calculation of trust value for Medaka fish anatomy and development took 9.298324584960938e-06s
INFO | --- Analysis for Medaka fish anatomy and development took 9.923780679702759s
Availability | SPARQL endpoint availability check for Emotion Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Emotion Ontology took 1.9067423343658447s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.5176970958709717s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.01874828338623047s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0005321502685546875s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007634162902832031s
Believability | Calculation of trust value for Emotion Ontology took 8.821487426757812e-06s
INFO | --- Analysis for Emotion Ontology took 10.724882364273071s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 0.00010538101196289062s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 1.8939659595489502s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.40397214889526367s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.020296573638916016s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0006074905395507812s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00012135505676269531s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for MaHCO - An MHC Ontology took 10.090039253234863s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 8.821487426757812e-05s
Availability | VoID file availability check for Protein-protein interaction took 1.8869969844818115s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.5128443241119385s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.018091201782226562s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0005764961242675781s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006849765777587891s
Believability | Calculation of trust value for Protein-protein interaction took 8.821487426757812e-06s
INFO | --- Analysis for Protein-protein interaction took 10.07811188697815s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 8.726119995117188e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 1.9088573455810547s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.44292759895324707s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.018124818801879883s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0005266666412353516s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007336139678955078s
Believability | Calculation of trust value for Mosquito insecticide resistance took 9.059906005859375e-06s
INFO | --- Analysis for Mosquito insecticide resistance took 10.062300443649292s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Measurement Method Ontology took 1.9008653163909912s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.36609506607055664s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.018459796905517578s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.000560760498046875s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.000141143798828125s
Believability | Calculation of trust value for Measurement Method Ontology took 8.821487426757812e-06s
INFO | --- Analysis for Measurement Method Ontology took 9.850205183029175s
Availability | SPARQL endpoint availability check for MGED Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for MGED Ontology took 1.8942172527313232s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.3639559745788574s
Reputation | Calculation of the PageRank for MGED Ontology took 0.02252054214477539s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0011222362518310547s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0006012916564941406s
Believability | Calculation of trust value for MGED Ontology took 8.821487426757812e-06s
INFO | --- Analysis for MGED Ontology took 9.488276720046997s
Availability | SPARQL endpoint availability check for Protein modification took 8.797645568847656e-05s
Availability | VoID file availability check for Protein modification took 1.9143531322479248s
Completeness | Calculation of interlinking completeness for Protein modification took 0.3704535961151123s
Reputation | Calculation of the PageRank for Protein modification took 0.019960880279541016s
Interlinking | Calculation of Degree of Connection for Protein modification took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Protein modification took 0.0005323886871337891s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00021982192993164062s
Believability | Calculation of trust value for Protein modification took 8.821487426757812e-06s
INFO | --- Analysis for Protein modification took 8.687033414840698s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.363059997558594e-05s
Availability | VoID file availability check for Mammalian phenotype took 1.9067866802215576s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.37564778327941895s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.01867198944091797s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0005207061767578125s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006403923034667969s
Believability | Calculation of trust value for Mammalian phenotype took 9.059906005859375e-06s
INFO | --- Analysis for Mammalian phenotype took 10.76533842086792s
Availability | SPARQL endpoint availability check for Mouse pathology took 8.654594421386719e-05s
Availability | VoID file availability check for Mouse pathology took 1.9002900123596191s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.3795304298400879s
Reputation | Calculation of the PageRank for Mouse pathology took 0.01891303062438965s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0005285739898681641s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0004763603210449219s
Believability | Calculation of trust value for Mouse pathology took 8.58306884765625e-06s
INFO | --- Analysis for Mouse pathology took 9.82429552078247s
Availability | SPARQL endpoint availability check for Mass spectrometry took 8.678436279296875e-05s
Availability | VoID file availability check for Mass spectrometry took 2.065077781677246s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.865687370300293s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.018527507781982422s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0005199909210205078s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.000354766845703125s
Believability | Calculation of trust value for Mass spectrometry took 1.1682510375976562e-05s
INFO | --- Analysis for Mass spectrometry took 11.736271858215332s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 4.5299530029296875e-05s
Availability | VoID file availability check for Medical Subject Headings took 1.9232172966003418s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.6444954872131348s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.018711566925048828s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0005426406860351562s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018656253814697266s
Believability | Calculation of trust value for Medical Subject Headings took 8.58306884765625e-06s
INFO | --- Analysis for Medical Subject Headings took 10.109229803085327s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 8.392333984375e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 1.907766580581665s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.3764638900756836s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.0186769962310791s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0005698204040527344s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.0002090930938720703s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 9.059906005859375e-06s
INFO | --- Analysis for Metathesaurus CPT Hierarchical Terms took 9.918319463729858s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 9.584426879882812e-05s
Availability | VoID file availability check for Natural Products Ontology took 1.907179832458496s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.49642181396484375s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.01868438720703125s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0005342960357666016s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.000797271728515625s
Believability | Calculation of trust value for Natural Products Ontology took 7.62939453125e-06s
INFO | --- Analysis for Natural Products Ontology took 10.150723695755005s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 8.654594421386719e-05s
Availability | VoID file availability check for NCBI organismal classification took 1.8967881202697754s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.35791659355163574s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.018377065658569336s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0005283355712890625s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008041858673095703s
Believability | Calculation of trust value for NCBI organismal classification took 1.0013580322265625e-05s
INFO | --- Analysis for NCBI organismal classification took 11.021777629852295s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 8.678436279296875e-05s
Availability | VoID file availability check for NCI Thesaurus took 1.8866126537322998s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.5567600727081299s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.018985271453857422s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0005221366882324219s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0019812583923339844s
Believability | Calculation of trust value for NCI Thesaurus took 1.0728836059570312e-05s
INFO | --- Analysis for NCI Thesaurus took 10.06620979309082s
Availability | SPARQL endpoint availability check for National Drug Data File took 8.702278137207031e-05s
Availability | VoID file availability check for National Drug Data File took 1.9205334186553955s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.9743900299072266s
Reputation | Calculation of the PageRank for National Drug Data File took 0.018683910369873047s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0005171298980712891s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006349086761474609s
Believability | Calculation of trust value for National Drug Data File took 1.0013580322265625e-05s
INFO | --- Analysis for National Drug Data File took 10.441216468811035s
Availability | SPARQL endpoint availability check for National Drug File took 8.511543273925781e-05s
Availability | VoID file availability check for National Drug File took 1.931579828262329s
Completeness | Calculation of interlinking completeness for National Drug File took 0.37859463691711426s
Reputation | Calculation of the PageRank for National Drug File took 0.01917743682861328s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0005381107330322266s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012383460998535156s
Believability | Calculation of trust value for National Drug File took 9.5367431640625e-06s
INFO | --- Analysis for National Drug File took 8.986396312713623s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 8.749961853027344e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 1.9169108867645264s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.4717707633972168s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.01864790916442871s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0005345344543457031s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011510848999023438s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 8.344650268554688e-06s
INFO | --- Analysis for Neural ElectroMagnetic Ontologies took 10.11305856704712s
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 1.9037902355194092s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.36729860305786133s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.019113540649414062s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0005402565002441406s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006694793701171875s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 9.059906005859375e-06s
INFO | --- Analysis for Neomark Oral Cancer Ontology took 10.504444360733032s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 8.249282836914062e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 2.4713492393493652s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.44500136375427246s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.018486976623535156s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0005276203155517578s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00013065338134765625s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 8.106231689453125e-06s
INFO | --- Analysis for Neomark Oral Cancer-Centred Ontology took 10.423502683639526s
Availability | SPARQL endpoint availability check for NIFSTD took 9.107589721679688e-05s
Availability | VoID file availability check for NIFSTD took 1.9020795822143555s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.5022017955780029s
Reputation | Calculation of the PageRank for NIFSTD took 0.01824331283569336s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0005688667297363281s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.001966238021850586s
Believability | Calculation of trust value for NIFSTD took 9.059906005859375e-06s
INFO | --- Analysis for NIFSTD took 9.089141368865967s
Availability | SPARQL endpoint availability check for NIF Cell took 0.0001068115234375s
Availability | VoID file availability check for NIF Cell took 1.9156930446624756s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.5766260623931885s
Reputation | Calculation of the PageRank for NIF Cell took 0.018138647079467773s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0005345344543457031s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013375282287597656s
Believability | Calculation of trust value for NIF Cell took 8.821487426757812e-06s
INFO | --- Analysis for NIF Cell took 9.40439224243164s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 8.821487426757812e-05s
Availability | VoID file availability check for NIF Dysfunction took 1.9333460330963135s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.371443510055542s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.01828312873840332s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0005402565002441406s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.001416921615600586s
Believability | Calculation of trust value for NIF Dysfunction took 1.0013580322265625e-05s
INFO | --- Analysis for NIF Dysfunction took 11.191125392913818s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 1.9378619194030762s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.3983027935028076s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.018428564071655273s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0005388259887695312s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005600452423095703s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 9.059906005859375e-06s
INFO | --- Analysis for Neural-Immune Gene Ontology took 9.89009714126587s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 8.678436279296875e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 1.9024903774261475s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.39372968673706055s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.018520355224609375s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0005273818969726562s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005404949188232422s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 9.5367431640625e-06s
INFO | --- Analysis for NMR-instrument specific component of metabolomics investigations took 10.234860181808472s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 8.535385131835938e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 1.897228479385376s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.3436610698699951s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.01827406883239746s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0005500316619873047s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00011515617370605469s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 8.344650268554688e-06s
INFO | --- Analysis for Non Randomized Controlled Trials Ontology took 10.06140398979187s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for NanoParticle Ontology took 1.9076194763183594s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.38172245025634766s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.018215179443359375s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0005359649658203125s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0011980533599853516s
Believability | Calculation of trust value for NanoParticle Ontology took 9.059906005859375e-06s
INFO | --- Analysis for NanoParticle Ontology took 9.591273546218872s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 9.059906005859375e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 1.914048671722412s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.35387229919433594s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.019840478897094727s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0005249977111816406s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007927417755126953s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 9.5367431640625e-06s
INFO | --- Analysis for Ontology of Adverse Events (OAE) took 8.66323971748352s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 0.00010466575622558594s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 1.937225341796875s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.3716552257537842s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.0181729793548584s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0005478858947753906s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0014526844024658203s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 9.059906005859375e-06s
INFO | --- Analysis for Ontology for Biomedical Investigations took 10.185568571090698s
Availability | SPARQL endpoint availability check for OBOE took 8.58306884765625e-05s
Availability | VoID file availability check for OBOE took 1.9208872318267822s
Completeness | Calculation of interlinking completeness for OBOE took 0.4139900207519531s
Reputation | Calculation of the PageRank for OBOE took 0.017993450164794922s
Interlinking | Calculation of Degree of Connection for OBOE took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OBOE took 0.0005369186401367188s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00010800361633300781s
Believability | Calculation of trust value for OBOE took 8.344650268554688e-06s
INFO | --- Analysis for OBOE took 9.652096271514893s
Availability | SPARQL endpoint availability check for OBOE SBC took 8.606910705566406e-05s
Availability | VoID file availability check for OBOE SBC took 1.9013416767120361s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.4320068359375s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020777225494384766s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0005280971527099609s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0008301734924316406s
Believability | Calculation of trust value for OBOE SBC took 8.821487426757812e-06s
INFO | --- Analysis for OBOE SBC took 10.50173044204712s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 8.559226989746094e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 1.9070394039154053s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.3525097370147705s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.018268823623657227s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0005526542663574219s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005903244018554688s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 5.0067901611328125e-06s
INFO | --- Analysis for Ontology of Clinical Research (OCRe) took 10.81907343864441s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 0.00010776519775390625s
Availability | VoID file availability check for Ontology for disease genetic investigation took 1.9049861431121826s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.3597860336303711s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.019112825393676758s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0005555152893066406s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008714199066162109s
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.417486190795898s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 8.654594421386719e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 1.906142234802246s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.3914947509765625s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.018693923950195312s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0005311965942382812s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008711814880371094s
Believability | Calculation of trust value for Ontology for Genetic Interval took 8.344650268554688e-06s
INFO | --- Analysis for Ontology for Genetic Interval took 10.115655422210693s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 8.463859558105469e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 1.883819818496704s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.3590271472930908s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.01829218864440918s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0005400180816650391s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.0002925395965576172s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 9.775161743164062e-06s
INFO | --- Analysis for Ontology of Glucose Metabolism Disorder took 9.535470247268677s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.315376281738281e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 1.9109387397766113s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.371504545211792s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.02105093002319336s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0005517005920410156s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006704330444335938s
Believability | Calculation of trust value for Ontology for General Medical Science took 8.821487426757812e-06s
INFO | --- Analysis for Ontology for General Medical Science took 9.758771896362305s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 8.869171142578125e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 1.8875312805175781s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.34081339836120605s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.0180511474609375s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0005364418029785156s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.001125335693359375s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 9.775161743164062e-06s
INFO | --- Analysis for Online Mendelian Inheritance in Man took 9.691439151763916s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 8.821487426757812e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 1.9014766216278076s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.3772099018096924s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.018174409866333008s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0005345344543457031s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.00037741661071777344s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 1.0013580322265625e-05s
INFO | --- Analysis for Ontology for MicroRNA Target Prediction took 9.633464574813843s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 6.532669067382812e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 1.9207143783569336s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.38208603858947754s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.0194704532623291s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0005993843078613281s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0006229877471923828s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 7.62939453125e-06s
INFO | --- Analysis for Ontology of Medically Related Social Entities took 10.124308586120605s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 8.463859558105469e-05s
Availability | VoID file availability check for Ontology of Data Mining took 1.9195044040679932s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.3692049980163574s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.018494844436645508s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.000537872314453125s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007770061492919922s
Believability | Calculation of trust value for Ontology of Data Mining took 8.821487426757812e-06s
INFO | --- Analysis for Ontology of Data Mining took 9.205436706542969s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 8.893013000488281e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 1.8819398880004883s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.38478851318359375s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.018182039260864258s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0005259513854980469s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.0002472400665283203s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 7.62939453125e-06s
INFO | --- Analysis for Ontology of General Purpose Datatypes took 9.400012731552124s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 8.654594421386719e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 1.910080909729004s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.642780065536499s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020210742950439453s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0005350112915039062s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006031990051269531s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 6.9141387939453125e-06s
INFO | --- Analysis for Orphanet Ontology of Rare Diseases took 10.51271390914917s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 8.893013000488281e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 1.888880968093872s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.4637339115142822s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.018244266510009766s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0005733966827392578s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009865760803222656s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 8.106231689453125e-06s
INFO | --- Analysis for Ontology for Parasite LifeCycle took 9.34865665435791s
Availability | SPARQL endpoint availability check for Phenotypic quality took 0.00010013580322265625s
Availability | VoID file availability check for Phenotypic quality took 1.930976152420044s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.3478720188140869s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.01845526695251465s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0005431175231933594s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008826255798339844s
Believability | Calculation of trust value for Phenotypic quality took 9.298324584960938e-06s
INFO | --- Analysis for Phenotypic quality took 10.205233812332153s
Availability | SPARQL endpoint availability check for Physician Data Query took 8.559226989746094e-05s
Availability | VoID file availability check for Physician Data Query took 1.942237138748169s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.368497371673584s
Reputation | Calculation of the PageRank for Physician Data Query took 0.018080711364746094s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0005629062652587891s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008220672607421875s
Believability | Calculation of trust value for Physician Data Query took 9.059906005859375e-06s
INFO | --- Analysis for Physician Data Query took 10.083186388015747s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 8.559226989746094e-05s
Availability | VoID file availability check for Pediatric Terminology took 1.8778672218322754s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.46704792976379395s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.01817035675048828s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0005285739898681641s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0007884502410888672s
Believability | Calculation of trust value for Pediatric Terminology took 8.58306884765625e-06s
INFO | --- Analysis for Pediatric Terminology took 10.024722814559937s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 1.905371904373169s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.36618638038635254s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.018175840377807617s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0005216598510742188s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00018787384033203125s
Believability | Calculation of trust value for Parasite Experiment Ontology took 8.58306884765625e-06s
INFO | --- Analysis for Parasite Experiment Ontology took 10.610775470733643s
Availability | SPARQL endpoint availability check for PHARE took 8.749961853027344e-05s
Availability | VoID file availability check for PHARE took 2.301539897918701s
Completeness | Calculation of interlinking completeness for PHARE took 0.36686277389526367s
Reputation | Calculation of the PageRank for PHARE took 0.018776416778564453s
Interlinking | Calculation of Degree of Connection for PHARE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0005354881286621094s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006351470947265625s
Believability | Calculation of trust value for PHARE took 9.5367431640625e-06s
INFO | --- Analysis for PHARE took 11.27474069595337s
Availability | SPARQL endpoint availability check for PKO_Re took 0.00010752677917480469s
Availability | VoID file availability check for PKO_Re took 1.9515609741210938s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.5010180473327637s
Reputation | Calculation of the PageRank for PKO_Re took 0.018169403076171875s
Interlinking | Calculation of Degree of Connection for PKO_Re took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for PKO_Re took 0.0005922317504882812s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00017380714416503906s
Believability | Calculation of trust value for PKO_Re took 5.4836273193359375e-06s
INFO | --- Analysis for PKO_Re took 9.814985275268555s
Availability | SPARQL endpoint availability check for PMA 2010 took 8.487701416015625e-05s
Availability | VoID file availability check for PMA 2010 took 1.90181565284729s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.3763413429260254s
Reputation | Calculation of the PageRank for PMA 2010 took 0.019339799880981445s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0005359649658203125s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0009152889251708984s
Believability | Calculation of trust value for PMA 2010 took 5.9604644775390625e-06s
INFO | --- Analysis for PMA 2010 took 10.295894145965576s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 8.296966552734375e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 1.9370198249816895s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.35930776596069336s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.01830434799194336s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0005259513854980469s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00016427040100097656s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 4.5299530029296875e-06s
INFO | --- Analysis for Physical Medicine and Rehabilitation took 11.214976072311401s
Availability | SPARQL endpoint availability check for Plant Anatomy took 8.96453857421875e-05s
Availability | VoID file availability check for Plant Anatomy took 1.887636661529541s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.34924840927124023s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.018306732177734375s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0005352497100830078s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.00040340423583984375s
Believability | Calculation of trust value for Plant Anatomy took 8.106231689453125e-06s
INFO | --- Analysis for Plant Anatomy took 8.630195617675781s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 4.267692565917969e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 1.9103586673736572s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.34703779220581055s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.01817011833190918s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0005261898040771484s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 6.842613220214844e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 1.049041748046875e-05s
INFO | --- Analysis for Plant Growth and Development Stage took 10.520549058914185s
Availability | SPARQL endpoint availability check for Plant Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Plant Ontology took 1.9260101318359375s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.3703181743621826s
Reputation | Calculation of the PageRank for Plant Ontology took 0.01826000213623047s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0005261898040771484s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.00044035911560058594s
Believability | Calculation of trust value for Plant Ontology took 8.106231689453125e-06s
INFO | --- Analysis for Plant Ontology took 10.343904972076416s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 4.1961669921875e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 1.8967797756195068s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.35584449768066406s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.020090103149414062s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0005280971527099609s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006561279296875s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 1.049041748046875e-05s
INFO | --- Analysis for PRotein Ontology (PRO) took 10.257505416870117s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 8.511543273925781e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 1.9129407405853271s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.3558354377746582s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.0184023380279541s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0005316734313964844s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.00025725364685058594s
Believability | Calculation of trust value for Proteomics data and process provenance took 6.198883056640625e-06s
INFO | --- Analysis for Proteomics data and process provenance took 10.958099126815796s
Availability | SPARQL endpoint availability check for Pathway ontology took 8.606910705566406e-05s
Availability | VoID file availability check for Pathway ontology took 1.8958828449249268s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.3480193614959717s
Reputation | Calculation of the PageRank for Pathway ontology took 0.01828479766845703s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0005698204040527344s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.000125885009765625s
Believability | Calculation of trust value for Pathway ontology took 5.245208740234375e-06s
INFO | --- Analysis for Pathway ontology took 9.42529821395874s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 1.93229079246521s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.36701440811157227s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.01850724220275879s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0005290508270263672s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 1.2159347534179688e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for Quantitative Imaging Biomarker Ontology took 10.072406768798828s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.220008850097656e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 1.9014742374420166s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.42969799041748047s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.018802165985107422s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0005404949188232422s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.00176239013671875s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 1.0251998901367188e-05s
INFO | --- Analysis for Read Codes, Clinical Terms Version 3 (CTV3) took 9.23893666267395s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 0.00017309188842773438s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 1.8948760032653809s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.5029113292694092s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.018555879592895508s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0005502700805664062s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00014138221740722656s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 8.106231689453125e-06s
INFO | --- Analysis for Randomized Controlled Trials (RCT) Ontology took 10.534932374954224s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 1.9186663627624512s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.36882543563842773s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.018221378326416016s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0005702972412109375s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.512901306152344e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 9.775161743164062e-06s
INFO | --- Analysis for Reproductive trait and phenotype ontology took 8.662370204925537s
Availability | SPARQL endpoint availability check for Physico-chemical process took 8.940696716308594e-05s
Availability | VoID file availability check for Physico-chemical process took 1.8893556594848633s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.3497896194458008s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.018344640731811523s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0005347728729248047s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00024199485778808594s
Believability | Calculation of trust value for Physico-chemical process took 9.5367431640625e-06s
INFO | --- Analysis for Physico-chemical process took 9.985719680786133s
Availability | SPARQL endpoint availability check for RadLex took 4.267692565917969e-05s
Availability | VoID file availability check for RadLex took 1.900360107421875s
Completeness | Calculation of interlinking completeness for RadLex took 0.3509514331817627s
Reputation | Calculation of the PageRank for RadLex took 0.018184900283813477s
Interlinking | Calculation of Degree of Connection for RadLex took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RadLex took 0.0005490779876708984s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0015325546264648438s
Believability | Calculation of trust value for RadLex took 7.62939453125e-06s
INFO | --- Analysis for RadLex took 8.299100160598755s
Availability | SPARQL endpoint availability check for RNA ontology took 5.412101745605469e-05s
Availability | VoID file availability check for RNA ontology took 1.918405294418335s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.37019896507263184s
Reputation | Calculation of the PageRank for RNA ontology took 0.018326282501220703s
Interlinking | Calculation of Degree of Connection for RNA ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for RNA ontology took 0.000530242919921875s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005886554718017578s
Believability | Calculation of trust value for RNA ontology took 8.106231689453125e-06s
INFO | --- Analysis for RNA ontology took 10.109661102294922s
Availability | SPARQL endpoint availability check for Role Ontology took 9.489059448242188e-05s
Availability | VoID file availability check for Role Ontology took 1.9248666763305664s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.735682487487793s
Reputation | Calculation of the PageRank for Role Ontology took 0.0181124210357666s
Interlinking | Calculation of Degree of Connection for Role Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Role Ontology took 0.0005385875701904297s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00018906593322753906s
Believability | Calculation of trust value for Role Ontology took 6.198883056640625e-06s
INFO | --- Analysis for Role Ontology took 9.534235954284668s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Rat Strain Ontology took 1.9191269874572754s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.36064600944519043s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.018215656280517578s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0005233287811279297s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.0001735687255859375s
Believability | Calculation of trust value for Rat Strain Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for Rat Strain Ontology took 10.583725929260254s
Availability | SPARQL endpoint availability check for RxNORM took 4.172325134277344e-05s
Availability | VoID file availability check for RxNORM took 1.885223150253296s
Completeness | Calculation of interlinking completeness for RxNORM took 0.35920214653015137s
Reputation | Calculation of the PageRank for RxNORM took 0.02457284927368164s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0008070468902587891s
Believability | Calculation of trust value for RxNORM took 7.62939453125e-06s
INFO | --- Analysis for RxNORM took 10.132836103439331s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 5.173683166503906e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 1.9214282035827637s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.3522207736968994s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.018088579177856445s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0005249977111816406s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010404586791992188s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 9.059906005859375e-06s
INFO | --- Analysis for Subcellular Anatomy Ontology (SAO) took 10.355186223983765s
Availability | SPARQL endpoint availability check for Systems Biology took 0.0001239776611328125s
Availability | VoID file availability check for Systems Biology took 1.916846513748169s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.34998416900634766s
Reputation | Calculation of the PageRank for Systems Biology took 0.018196821212768555s
Interlinking | Calculation of Degree of Connection for Systems Biology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Systems Biology took 0.0005486011505126953s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004544258117675781s
Believability | Calculation of trust value for Systems Biology took 8.58306884765625e-06s
INFO | --- Analysis for Systems Biology took 9.459179878234863s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.792213439941406e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 1.9116132259368896s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.34636640548706055s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.018161296844482422s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0005462169647216797s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00011134147644042969s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 7.867813110351562e-06s
INFO | --- Analysis for Smoking Behavior Risk Ontology took 9.747394800186157s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.9591064453125e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 1.910515546798706s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.35097217559814453s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.01818108558654785s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0005526542663574219s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013782978057861328s
Believability | Calculation of trust value for Sleep Domain Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for Sleep Domain Ontology took 16.501174449920654s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.3392181396484375e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 1.8832814693450928s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.3674604892730713s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.01834273338317871s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0005388259887695312s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003414154052734375s
Believability | Calculation of trust value for Sample processing and separation techniques took 7.62939453125e-06s
INFO | --- Analysis for Sample processing and separation techniques took 11.220024585723877s
Availability | SPARQL endpoint availability check for Student Health Record took 0.00011205673217773438s
Availability | VoID file availability check for Student Health Record took 1.9002504348754883s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.40759849548339844s
Reputation | Calculation of the PageRank for Student Health Record took 0.01823902130126953s
Interlinking | Calculation of Degree of Connection for Student Health Record took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Student Health Record took 0.0005612373352050781s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004467964172363281s
Believability | Calculation of trust value for Student Health Record took 8.821487426757812e-06s
INFO | --- Analysis for Student Health Record took 9.374215126037598s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 8.463859558105469e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 1.9119007587432861s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.7203078269958496s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.018093585968017578s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0005395412445068359s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0013275146484375s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for SemanticScience Integrated Ontology took 10.22662091255188s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 8.487701416015625e-05s
Availability | VoID file availability check for Situation-Based Access Control took 1.9160382747650146s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.3670229911804199s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.018026113510131836s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0005240440368652344s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00020503997802734375s
Believability | Calculation of trust value for Situation-Based Access Control took 8.58306884765625e-06s
INFO | --- Analysis for Situation-Based Access Control took 11.979947566986084s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 8.797645568847656e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 1.923778772354126s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.5754404067993164s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.018320083618164062s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0005209445953369141s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019366741180419922s
Believability | Calculation of trust value for SNOMED Clinical Terms took 9.775161743164062e-06s
INFO | --- Analysis for SNOMED Clinical Terms took 11.439059495925903s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.792213439941406e-05s
Availability | VoID file availability check for SNP-Ontology took 1.8855922222137451s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.3381192684173584s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.018352508544921875s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0005438327789306641s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0007152557373046875s
Believability | Calculation of trust value for SNP-Ontology took 8.821487426757812e-06s
INFO | --- Analysis for SNP-Ontology took 10.211775064468384s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.1961669921875e-05s
Availability | VoID file availability check for Sequence types and features took 1.9245901107788086s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.34568190574645996s
Reputation | Calculation of the PageRank for Sequence types and features took 0.01811051368713379s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0005309581756591797s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005788803100585938s
Believability | Calculation of trust value for Sequence types and features took 8.821487426757812e-06s
INFO | --- Analysis for Sequence types and features took 10.484951734542847s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 8.463859558105469e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 1.8991799354553223s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.5809931755065918s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.01831531524658203s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0005393028259277344s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015795230865478516s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 1.049041748046875e-05s
INFO | --- Analysis for Suggested Ontology for Pharmacogenomics took 10.760516166687012s
Availability | SPARQL endpoint availability check for SoyOntology took 8.821487426757812e-05s
Availability | VoID file availability check for SoyOntology took 1.886976957321167s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.3772857189178467s
Reputation | Calculation of the PageRank for SoyOntology took 0.018231630325317383s
Interlinking | Calculation of Degree of Connection for SoyOntology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for SoyOntology took 0.0005204677581787109s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00012683868408203125s
Believability | Calculation of trust value for SoyOntology took 9.298324584960938e-06s
INFO | --- Analysis for SoyOntology took 10.212703466415405s
Availability | SPARQL endpoint availability check for Spider Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for Spider Ontology took 1.9043455123901367s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.47232604026794434s
Reputation | Calculation of the PageRank for Spider Ontology took 0.020146608352661133s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0005352497100830078s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.0003275871276855469s
Believability | Calculation of trust value for Spider Ontology took 9.059906005859375e-06s
INFO | --- Analysis for Spider Ontology took 9.915481805801392s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 8.416175842285156e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 1.8890080451965332s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.5003395080566406s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.01814413070678711s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.000518798828125s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00028252601623535156s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 4.76837158203125e-06s
INFO | --- Analysis for Solanaceae Phenotype Ontology took 10.104623317718506s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 1.907365322113037s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.4196755886077881s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.018015384674072266s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0005447864532470703s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004589557647705078s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 9.775161743164062e-06s
INFO | --- Analysis for Syndromic Surveillance Ontology took 9.929032564163208s
Availability | SPARQL endpoint availability check for Software Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Software Ontology took 1.89735746383667s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.36570191383361816s
Reputation | Calculation of the PageRank for Software Ontology took 0.020011186599731445s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0005548000335693359s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.0004265308380126953s
Believability | Calculation of trust value for Software Ontology took 8.821487426757812e-06s
INFO | --- Analysis for Software Ontology took 10.933505296707153s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 0.000102996826171875s
Availability | VoID file availability check for Tick gross anatomy took 1.9023053646087646s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.5435497760772705s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.018939733505249023s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0005540847778320312s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00024580955505371094s
Believability | Calculation of trust value for Tick gross anatomy took 9.5367431640625e-06s
INFO | --- Analysis for Tick gross anatomy took 9.93701696395874s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 8.440017700195312e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 1.9126958847045898s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.3672754764556885s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.018218278884887695s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0005261898040771484s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008869171142578125s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 9.775161743164062e-06s
INFO | --- Analysis for Teleost Anatomy Ontology took 9.796286582946777s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 8.535385131835938e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 1.89992356300354s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.37645506858825684s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.01831531524658203s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0005223751068115234s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 9.012222290039062e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 9.298324584960938e-06s
INFO | --- Analysis for Taxonomic rank vocabulary took 9.897829532623291s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 4.363059997558594e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 1.912482500076294s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.9745316505432129s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.018818378448486328s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0005233287811279297s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.2479248046875e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 9.775161743164062e-06s
INFO | --- Analysis for Terminology for the Description of Dynamics took 10.066895723342896s
Availability | SPARQL endpoint availability check for Time Event Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Time Event Ontology took 1.9152367115020752s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.39502525329589844s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.018275022506713867s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.00052642822265625s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008368492126464844s
Believability | Calculation of trust value for Time Event Ontology took 9.298324584960938e-06s
INFO | --- Analysis for Time Event Ontology took 10.057608604431152s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 8.702278137207031e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 1.9401798248291016s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.37146878242492676s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.01982903480529785s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.000568389892578125s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.00043654441833496094s
Believability | Calculation of trust value for Mosquito gross anatomy took 9.775161743164062e-06s
INFO | --- Analysis for Mosquito gross anatomy took 9.560487031936646s
Availability | SPARQL endpoint availability check for thesaurus took 8.869171142578125e-05s
Availability | VoID file availability check for thesaurus took 1.908907413482666s
Completeness | Calculation of interlinking completeness for thesaurus took 0.3521451950073242s
Reputation | Calculation of the PageRank for thesaurus took 0.018564224243164062s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0005366802215576172s
Interlinking | Calculation of Clustering coefficient for thesaurus took 7.414817810058594e-05s
Believability | Calculation of trust value for thesaurus took 9.059906005859375e-06s
INFO | --- Analysis for thesaurus took 8.616295576095581s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 8.630752563476562e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 1.9091968536376953s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.3808021545410156s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.018337249755859375s
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.0005271434783935547s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003368854522705078s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 1.1920928955078125e-05s
INFO | --- Analysis for Traditional Medicine Signs and Symptoms Value Set took 10.206703424453735s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 5.650520324707031e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 1.882920265197754s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.35622692108154297s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.01835346221923828s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0005273818969726562s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008437633514404297s
Believability | Calculation of trust value for Translational Medicine Ontology took 8.821487426757812e-06s
INFO | --- Analysis for Translational Medicine Ontology took 9.878677368164062s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 8.821487426757812e-05s
Availability | VoID file availability check for Plant Trait Ontology took 1.8883156776428223s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.3605983257293701s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.018553733825683594s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.000522613525390625s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00015425682067871094s
Believability | Calculation of trust value for Plant Trait Ontology took 9.298324584960938e-06s
INFO | --- Analysis for Plant Trait Ontology took 9.834454536437988s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.7206878662109375e-05s
Availability | VoID file availability check for TOK_Ontology took 1.9185161590576172s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.45357513427734375s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.01864790916442871s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0005369186401367188s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00018310546875s
Believability | Calculation of trust value for TOK_Ontology took 9.298324584960938e-06s
INFO | --- Analysis for TOK_Ontology took 10.188928604125977s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 9.131431579589844e-05s
Availability | VoID file availability check for Teleost taxonomy took 1.900507926940918s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.7182817459106445s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.018348217010498047s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0006318092346191406s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00020956993103027344s
Believability | Calculation of trust value for Teleost taxonomy took 9.298324584960938e-06s
INFO | --- Analysis for Teleost taxonomy took 9.98706579208374s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 8.702278137207031e-05s
Availability | VoID file availability check for Uber anatomy ontology took 1.93699049949646s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.4691457748413086s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.019839048385620117s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0005750656127929688s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0011909008026123047s
Believability | Calculation of trust value for Uber anatomy ontology took 5.650520324707031e-05s
INFO | --- Analysis for Uber anatomy ontology took 9.889564037322998s
Availability | SPARQL endpoint availability check for Units Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Units Ontology took 1.8937513828277588s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.36660146713256836s
Reputation | Calculation of the PageRank for Units Ontology took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for Units Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Units Ontology took 0.0005481243133544922s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.000232696533203125s
Believability | Calculation of trust value for Units Ontology took 9.059906005859375e-06s
INFO | --- Analysis for Units Ontology took 9.733155727386475s
Availability | SPARQL endpoint availability check for Units of measurement took 9.584426879882812e-05s
Availability | VoID file availability check for Units of measurement took 1.8931350708007812s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.37163424491882324s
Reputation | Calculation of the PageRank for Units of measurement took 0.019367218017578125s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.0005495548248291016s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.00029969215393066406s
Believability | Calculation of trust value for Units of measurement took 8.821487426757812e-06s
INFO | --- Analysis for Units of measurement took 8.778991460800171s
Availability | SPARQL endpoint availability check for VANDF took 8.821487426757812e-05s
Availability | VoID file availability check for VANDF took 1.9362473487854004s
Completeness | Calculation of interlinking completeness for VANDF took 0.3781850337982178s
Reputation | Calculation of the PageRank for VANDF took 0.0198976993560791s
Interlinking | Calculation of Degree of Connection for VANDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0005335807800292969s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0007088184356689453s
Believability | Calculation of trust value for VANDF took 9.298324584960938e-06s
INFO | --- Analysis for VANDF took 9.035740375518799s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 5.7220458984375e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 1.8834447860717773s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.3404505252838135s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.019063949584960938s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0005393028259277344s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0004756450653076172s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 9.298324584960938e-06s
INFO | --- Analysis for Vertebrate Anatomy Ontology took 9.141631364822388s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 9.942054748535156e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 1.9132184982299805s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.4480400085449219s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0005285739898681641s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006449222564697266s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 9.059906005859375e-06s
INFO | --- Analysis for vertebrate Homologous Organ Groups took 9.303000688552856s
Availability | SPARQL endpoint availability check for VIVO took 8.678436279296875e-05s
Availability | VoID file availability check for VIVO took 1.9208106994628906s
Completeness | Calculation of interlinking completeness for VIVO took 0.3659026622772217s
Reputation | Calculation of the PageRank for VIVO took 0.01837301254272461s
Interlinking | Calculation of Degree of Connection for VIVO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0005674362182617188s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.00035572052001953125s
Believability | Calculation of trust value for VIVO took 9.5367431640625e-06s
INFO | --- Analysis for VIVO took 9.991074562072754s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 8.893013000488281e-05s
Availability | VoID file availability check for Vaccine Ontology took 1.9230687618255615s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.4568350315093994s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.0181882381439209s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0005462169647216797s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012805461883544922s
Believability | Calculation of trust value for Vaccine Ontology took 9.775161743164062e-06s
INFO | --- Analysis for Vaccine Ontology took 9.061950922012329s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 8.916854858398438e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 1.9132757186889648s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.37783074378967285s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.018288612365722656s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0005631446838378906s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.0002162456512451172s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 9.059906005859375e-06s
INFO | --- Analysis for Vertebrate Trait Ontology took 9.539450883865356s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 9.012222290039062e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 1.931741714477539s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.40846991539001465s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.018547773361206055s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0005729198455810547s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0005092620849609375s
Believability | Calculation of trust value for C. elegans gross anatomy took 9.5367431640625e-06s
INFO | --- Analysis for C. elegans gross anatomy took 9.205714225769043s
Availability | SPARQL endpoint availability check for C. elegans development took 8.535385131835938e-05s
Availability | VoID file availability check for C. elegans development took 1.9115371704101562s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.45800113677978516s
Reputation | Calculation of the PageRank for C. elegans development took 0.018588781356811523s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0005280971527099609s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.649162292480469e-05s
Believability | Calculation of trust value for C. elegans development took 9.298324584960938e-06s
INFO | --- Analysis for C. elegans development took 9.315466165542603s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 9.369850158691406e-05s
Availability | VoID file availability check for C. elegans phenotype took 1.9058005809783936s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.40927577018737793s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.018645048141479492s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0005633831024169922s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 9.369850158691406e-05s
Believability | Calculation of trust value for C. elegans phenotype took 8.821487426757812e-06s
INFO | --- Analysis for C. elegans phenotype took 10.246664047241211s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 8.535385131835938e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 1.9477074146270752s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.5684456825256348s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.018305301666259766s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0005261898040771484s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0006000995635986328s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 8.821487426757812e-06s
INFO | --- Analysis for WHO Adverse Reaction Terminology took 10.829664945602417s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 8.58306884765625e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 1.9216110706329346s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.9450557231903076s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.01887989044189453s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0005342960357666016s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006780624389648438s
Believability | Calculation of trust value for Xenopus anatomy and development took 9.5367431640625e-06s
INFO | --- Analysis for Xenopus anatomy and development took 10.280482769012451s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 1.9041659832000732s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.374737024307251s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.021223783493041992s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0005278587341308594s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.0002295970916748047s
Believability | Calculation of trust value for Experimental Conditions Ontology took 9.059906005859375e-06s
INFO | --- Analysis for Experimental Conditions Ontology took 9.282477855682373s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 8.535385131835938e-05s
Availability | VoID file availability check for Yeast phenotypes took 1.9052622318267822s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.3773782253265381s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.019029617309570312s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0005300045013427734s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0002865791320800781s
Believability | Calculation of trust value for Yeast phenotypes took 8.821487426757812e-06s
INFO | --- Analysis for Yeast phenotypes took 10.014134407043457s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 0.00010442733764648438s
Availability | VoID file availability check for Zebrafish anatomy and development took 1.9205102920532227s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.36775755882263184s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.019507884979248047s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0005712509155273438s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0008456707000732422s
Believability | Calculation of trust value for Zebrafish anatomy and development took 9.298324584960938e-06s
INFO | --- Analysis for Zebrafish anatomy and development took 8.108596563339233s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.760944128036499s
Availability | VoID file availability check for BioSamples RDF took 0.24516534805297852s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.3715212345123291s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.01849985122680664s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0005259513854980469s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.8623809814453125e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.239776611328125e-05s
INFO | --- Analysis for BioSamples RDF took 3.7675297260284424s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.18394899368286133s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 9.059906005859375e-06s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.37712740898132324s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.020295143127441406s
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.00052642822265625s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011396408081054688s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for Bank for International Settlements (BIS) Linked Data took 2.6275484561920166s
Availability | SPARQL endpoint availability check for Bitzi took 8.535385131835938e-05s
Availability | VoID file availability check for Bitzi took 0.25499916076660156s
Completeness | Calculation of interlinking completeness for Bitzi took 0.354870080947876s
Reputation | Calculation of the PageRank for Bitzi took 0.019467592239379883s
Interlinking | Calculation of Degree of Connection for Bitzi took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bitzi took 0.0005180835723876953s
Interlinking | Calculation of Clustering coefficient for Bitzi took 1.3589859008789062e-05s
Believability | Calculation of trust value for Bitzi took 1.1920928955078125e-05s
INFO | --- Analysis for Bitzi took 3.206782579421997s
Availability | SPARQL endpoint availability check for BizkaiSense took 0.36948418617248535s
Availability | VoID file availability check for BizkaiSense took 0.15988397598266602s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.369736909866333s
Reputation | Calculation of the PageRank for BizkaiSense took 0.0186312198638916s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0005314350128173828s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 1.33514404296875e-05s
Believability | Calculation of trust value for BizkaiSense took 1.1444091796875e-05s
INFO | --- Analysis for BizkaiSense took 3.0809319019317627s
Availability | SPARQL endpoint availability check for blabla.itemlist took 8.845329284667969e-05s
Availability | VoID file availability check for blabla.itemlist took 20.09721088409424s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.37764430046081543s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0005323886871337891s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 1.33514404296875e-05s
Believability | Calculation of trust value for blabla.itemlist took 1.1920928955078125e-05s
INFO | --- Analysis for blabla.itemlist took 54.94151163101196s
Availability | SPARQL endpoint availability check for blabla.itemlist took 8.869171142578125e-05s
Availability | VoID file availability check for blabla.itemlist took 20.199066638946533s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.41153883934020996s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.018975019454956055s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 1.5020370483398438e-05s
Believability | Calculation of trust value for blabla.itemlist took 1.239776611328125e-05s
INFO | --- Analysis for blabla.itemlist took 52.8165283203125s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 7.700920104980469e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.7610654830932617s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.3699829578399658s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.021192073822021484s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0005366802215576172s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.172325134277344e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 9.5367431640625e-06s
INFO | --- Analysis for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.399960279464722s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 31.133676767349243s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 20.069851875305176s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.4462401866912842s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.01818060874938965s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0005173683166503906s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.67572021484375e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.1682510375976562e-05s
INFO | --- Analysis for British National Bibliography (BNB) - Linked Open Data took 141.77204012870789s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.38283658027648926s
Availability | VoID file availability check for Thesaurus BNCF took 0.24332165718078613s
Extra | Recovery of all triples for Thesaurus BNCF took 48.85662341117859s
Performance | Total latancy measurement for Thesaurus BNCF took 0.8044543266296387s
Amount of data | Number of triples check for Thesaurus BNCF took 0.8196759223937988s
Interoperability | New terms check for Thesaurus BNCF took 1.5189054012298584s
Versatility | Languages check for Thesaurus BNCF took 6.1954872608184814s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 1.0145163536071777s
Security | Check HTTPS for Thesaurus BNCF took 0.13587069511413574s
Interpretability | RDF structures check for Thesaurus BNCF took 0.1454477310180664s
Versatility | Serialization formats check for Thesaurus BNCF took 0.14654874801635742s
Availability | RDF dump link check for Thesaurus BNCF took 0.16408634185791016s
License | MR license check for Thesaurus BNCF took 0.1337583065032959s
License | HR license check for Thesaurus BNCF took 0.23183131217956543s
Amount of data | Number of property check for Thesaurus BNCF took 0.16405749320983887s
Understandability | Number of label check for Thesaurus BNCF took 0.2900371551513672s
Understandability | URI regex check for Thesaurus BNCF took 0.3376157283782959s
Understandability | Vocabs check for Thesaurus BNCF took 0.15697026252746582s
Verifiability | Authors check for Thesaurus BNCF took 0.17946553230285645s
Verifiability | Publishers check for Thesaurus BNCF took 0.13972139358520508s
Performance | Throughput check for Thesaurus BNCF took 10.96351408958435s
Amount of data | Check the number of entities for Thesaurus BNCF took 0.0005066394805908203s
Verifiability | Contribs. check for Thesaurus BNCF took 0.16782784461975098s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.1560807228088379s
Interlinking | skos check for Thesaurus BNCF took 0.2099137306213379s
Interlinking | skos check for Thesaurus BNCF took 0.20050382614135742s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.15695667266845703s
Currency | Creation date check for Thesaurus BNCF took 0.16003656387329102s
Currency | Modification date check for Thesaurus BNCF took 0.345409631729126s
Rep.Conc. | URIs length for Thesaurus BNCF took 23.96113610267639s
Interoperability | New vocabularies check for Thesaurus BNCF took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.16201233863830566s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.1560688018798828s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.1610088348388672s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 9.276238441467285s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.4854891300201416s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.707486867904663s
Consistency | Disjoint class check for Thesaurus BNCF took 0.17102932929992676s
Consistency | Check Misplaced properties for Thesaurus BNCF took 1.0070006847381592s
Consistency | Misplaced classes for Thesaurus BNCF took 6.449332237243652s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 7.027249574661255s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.4221668243408203s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.2300806045532227s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.313392400741577s
Security | Sign check for Thesaurus BNCF took 0.1792769432067871s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 18.784934043884277s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.4774479866027832s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.018667221069335938s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0005245208740234375s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 5.698204040527344e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 1.430511474609375e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 1.0728836059570312e-05s
INFO | --- Analysis for Thesaurus BNCF took 185.17513489723206s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2400648593902588s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 8.58306884765625e-06s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.3612010478973389s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5025489330291748s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.8667552471160889s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.579699754714966s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.13852643966675s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.8580806255340576s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.13633465766906738s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2130134105682373s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.21144509315490723s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.18970251083374023s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.35442519187927246s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.087522745132446s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.1547849178314209s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7153117656707764s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.21588587760925293s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.15460562705993652s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.550246000289917s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4669480323791504s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 10.695451974868774s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 8.821487426757812e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.31249117851257324s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.13199615478515625s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.15480995178222656s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.11277246475219727s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.18291187286376953s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2709383964538574s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.33382272720336914s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 14.893091440200806s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.1407482624053955s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.1502091884613037s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.08338427543640137s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5665364265441895s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030905485153198242s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03002643585205078s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.15223479270935059s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 10.901024580001831s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2244868278503418s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.3966856002807617s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.8973097801208496s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.640819311141968s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.031877756118774414s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.19930076599121094s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.08964180946350098s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.1767497062683105s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4677121639251709s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.1176612377166748s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0005457401275634766s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.9591064453125e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6689300537109375e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0013580322265625e-05s
INFO | --- Analysis for BPR ? Bibliography of the Italian Parliament and electoral studies took 317.22085881233215s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 8.726119995117188e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.2568931579589844s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.4396026134490967s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.019985675811767578s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0005426406860351562s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 7.033348083496094e-05s
Believability | Calculation of trust value for Brazilian Politicians took 1.0013580322265625e-05s
INFO | --- Analysis for Brazilian Politicians took 2.5989701747894287s
Availability | SPARQL endpoint availability check for BrazilianCities took 254.79224395751953s
Availability | VoID file availability check for BrazilianCities took 6.67572021484375e-06s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.6241004467010498s
Reputation | Calculation of the PageRank for BrazilianCities took 0.02037668228149414s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 3.0040740966796875e-05s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0005249977111816406s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 1.8596649169921875e-05s
Believability | Calculation of trust value for BrazilianCities took 1.2159347534179688e-05s
INFO | --- Analysis for BrazilianCities took 531.9175970554352s
Availability | SPARQL endpoint availability check for Bricklink took 1.2698500156402588s
Availability | VoID file availability check for Bricklink took 0.6297221183776855s
Completeness | Calculation of interlinking completeness for Bricklink took 0.39949607849121094s
Reputation | Calculation of the PageRank for Bricklink took 0.019382953643798828s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0005333423614501953s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.723403930664062e-05s
Believability | Calculation of trust value for Bricklink took 1.0728836059570312e-05s
INFO | --- Analysis for Bricklink took 7.205514669418335s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.25409722328186s
Availability | VoID file availability check for British Museum Collection took 19.99910879135132s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.44513702392578125s
Reputation | Calculation of the PageRank for British Museum Collection took 0.019886016845703125s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0005285739898681641s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 1.3828277587890625e-05s
Believability | Calculation of trust value for British Museum Collection took 1.2159347534179688e-05s
INFO | --- Analysis for British Museum Collection took 72.67610168457031s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 8.821487426757812e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 9.059906005859375e-06s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.43502020835876465s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.019063711166381836s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0005185604095458984s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 4.124641418457031e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.1920928955078125e-05s
INFO | --- Analysis for Brown Corpus in RDF/NIF took 62.2356173992157s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 60.06734108924866s
Availability | VoID file availability check for French Plant Health Bulletins took 40.09317064285278s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.4280354976654053s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.02163839340209961s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0005512237548828125s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 1.2159347534179688e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 1.1920928955078125e-05s
INFO | --- Analysis for French Plant Health Bulletins took 123.76267790794373s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 9.918212890625e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.17794132232666016s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.44399309158325195s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.019520044326782227s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0005400180816650391s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 1.4781951904296875e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 1.1682510375976562e-05s
INFO | --- Analysis for Bund Offener Haushalt took 2.5302016735076904s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 0.08311820030212402s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.3697495460510254s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.0201723575592041s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0005347728729248047s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 1.3828277587890625e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 1.3589859008789062e-05s
INFO | --- Analysis for BundestagNebeneinkuenfte took 4.686337232589722s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.4369826316833496s
Availability | VoID file availability check for business.data.gov.uk took 0.30288004875183105s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.521904468536377s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.01845550537109375s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0005822181701660156s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.125999450683594e-05s
Believability | Calculation of trust value for business.data.gov.uk took 8.344650268554688e-06s
INFO | --- Analysis for business.data.gov.uk took 3.9619321823120117s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.6656019687652588s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.7786827087402344s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 2.375720500946045s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.989063024520874s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.4878847599029541s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.7854743003845215s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 33.943702697753906s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.375042200088501s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.2800474166870117s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.3977231979370117s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.3783996105194092s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.4108598232269287s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.40048766136169434s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 12.431315660476685s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.4155538082122803s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.40917253494262695s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.8094298839569092s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.4340784549713135s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.5251245498657227s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.45024919509887695s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.91645359992981s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 9.799003601074219e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.3865518569946289s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.3925037384033203s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.43198084831237793s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.4104025363922119s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.4213597774505615s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.5847151279449463s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.4160926342010498s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 3.298614740371704s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.4099996089935303s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.5286965370178223s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.5090670585632324s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 1.1731703281402588s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.031789541244506836s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.029842853546142578s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.4692041873931885s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.5477616786956787s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.4788212776184082s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.6189959049224854s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.2998547554016113s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.4805171489715576s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.033545494079589844s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.3992905616760254s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.3835170269012451s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1724.2091207504272s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.7455348968505859s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.018669843673706055s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0005445480346679688s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 7.748603820800781e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.430511474609375e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 7.3909759521484375e-06s
INFO | --- Analysis for Biblioteca Virtual Miguel de Cervantes took 1958.1318900585175s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 4.553794860839844e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.3295001983642578s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.3690946102142334s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.01824474334716797s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0005245208740234375s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 1.1920928955078125e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 1.1682510375976562e-05s
INFO | --- Analysis for Price changes due to cabbage imports took 13.234828233718872s
Availability | SPARQL endpoint availability check for cablegate took 2.4057743549346924s
Availability | VoID file availability check for cablegate took 1.7347302436828613s
Completeness | Calculation of interlinking completeness for cablegate took 0.3917548656463623s
Reputation | Calculation of the PageRank for cablegate took 0.01811814308166504s
Interlinking | Calculation of Degree of Connection for cablegate took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for cablegate took 0.0005304813385009766s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.699562072753906e-05s
Believability | Calculation of trust value for cablegate took 1.0013580322265625e-05s
INFO | --- Analysis for cablegate took 18.72045063972473s
Availability | SPARQL endpoint availability check for Calames took 8.487701416015625e-05s
Availability | VoID file availability check for Calames took 20.09003520011902s
Completeness | Calculation of interlinking completeness for Calames took 0.34104132652282715s
Reputation | Calculation of the PageRank for Calames took 0.01822519302368164s
Interlinking | Calculation of Degree of Connection for Calames took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Calames took 0.0005216598510742188s
Interlinking | Calculation of Clustering coefficient for Calames took 3.814697265625e-05s
Believability | Calculation of trust value for Calames took 1.1205673217773438e-05s
INFO | --- Analysis for Calames took 34.63151788711548s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.2703108787536621s
Availability | VoID file availability check for CaLiGraph took 0.2564878463745117s
Extra | Recovery of all triples for CaLiGraph took 1.5893127918243408s
Performance | Total latancy measurement for CaLiGraph took 0.5750043392181396s
Amount of data | Number of triples check for CaLiGraph took 6.132355213165283s
Interoperability | New terms check for CaLiGraph took 1.9607281684875488s
Versatility | Languages check for CaLiGraph took 60.19734263420105s
Interpretability | Number of blank nodes check for CaLiGraph took 0.14461159706115723s
Interpretability | RDF structures check for CaLiGraph took 0.3499007225036621s
Versatility | Serialization formats check for CaLiGraph took 0.35384583473205566s
Availability | RDF dump link check for CaLiGraph took 0.21147465705871582s
License | MR license check for CaLiGraph took 0.8259847164154053s
License | HR license check for CaLiGraph took 60.51958632469177s
Amount of data | Number of property check for CaLiGraph took 0.1529831886291504s
Understandability | Number of label check for CaLiGraph took 3.1249797344207764s
Understandability | URI regex check for CaLiGraph took 0.3940446376800537s
Understandability | Vocabs check for CaLiGraph took 0.1795787811279297s
Verifiability | Authors check for CaLiGraph took 0.28529953956604004s
Verifiability | Publishers check for CaLiGraph took 0.1795809268951416s
Performance | Throughput check for CaLiGraph took 10.66095232963562s
Amount of data | Check the number of entities for CaLiGraph took 0.017812490463256836s
Verifiability | Contribs. check for CaLiGraph took 0.1771833896636963s
Interlinking | sameAs chians check for CaLiGraph took 0.4824047088623047s
Interlinking | skos check for CaLiGraph took 0.17509245872497559s
Interlinking | skos check for CaLiGraph took 0.11885690689086914s
Timeliness | dataset update frequency check for CaLiGraph took 0.25708651542663574s
Currency | Creation date check for CaLiGraph took 0.22919321060180664s
Currency | Modification date check for CaLiGraph took 0.14389657974243164s
Rep.Conc. | URIs length for CaLiGraph took 43.27531552314758s
Interoperability | New vocabularies check for CaLiGraph took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.1647474765777588s
Accuracy | Check Functional Property for CaLiGraph took 0.2920875549316406s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.24915099143981934s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.589977502822876s
Accuracy | Check White space in annotation for CaLiGraph took 0.028372526168823242s
Accuracy | Check Datatype consistency for CaLiGraph took 0.02887868881225586s
Consistency | Disjoint class check for CaLiGraph took 0.15970730781555176s
Consistency | Check Misplaced properties for CaLiGraph took 43.16863393783569s
Consistency | Misplaced classes for CaLiGraph took 0.4367806911468506s
Consistency | Check Ontology hijacking for CaLiGraph took 1.9250774383544922s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.274857997894287s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 43.499245166778564s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.0317845344543457s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.41751646995544434s
Security | Sign check for CaLiGraph took 0.13352656364440918s
Availability | Check URIs Dereferenciability for CaLiGraph took 3.810246706008911s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.9401938915252686s
Reputation | Calculation of the PageRank for CaLiGraph took 0.06404900550842285s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0005166530609130859s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 1.4066696166992188e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.6689300537109375e-06s
Believability | Calculation of trust value for CaLiGraph took 1.1920928955078125e-05s
INFO | --- Analysis for CaLiGraph took 1605.0892188549042s
Availability | SPARQL endpoint availability check for can-link took 1.0088999271392822s
Availability | VoID file availability check for can-link took 0.548208475112915s
Completeness | Calculation of interlinking completeness for can-link took 0.49404025077819824s
Reputation | Calculation of the PageRank for can-link took 0.020473480224609375s
Interlinking | Calculation of Degree of Connection for can-link took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for can-link took 0.000530242919921875s
Interlinking | Calculation of Clustering coefficient for can-link took 1.2159347534179688e-05s
Believability | Calculation of trust value for can-link took 7.152557373046875e-06s
INFO | --- Analysis for can-link took 16.16105318069458s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.07730722427368164s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.38031601905822754s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.019411802291870117s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0008184909820556641s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 1.5735626220703125e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 1.239776611328125e-05s
INFO | --- Analysis for Postal codes Italy (LinkedOpenData.it) took 2.574427604675293s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 8.940696716308594e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 6.4373016357421875e-06s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.3663747310638428s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.018549442291259766s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0005507469177246094s
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.2636184692382812e-05s
INFO | --- Analysis for Catalan EuroWordNet-lemon lexicon (3.0) took 3.9152169227600098s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 0.5932912826538086s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.1395275592803955s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.3637251853942871s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.018091440200805664s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0005307197570800781s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 1.3113021850585938e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 1.1444091796875e-05s
INFO | --- Analysis for Catalogus Professorum Lipsiensis took 4.399997234344482s
Availability | SPARQL endpoint availability check for Norway catch records dataset took 8.225440979003906e-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 0.38561081886291504s
Reputation | Calculation of the PageRank for Norway catch records dataset took 0.020700693130493164s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset took 0.0005166530609130859s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset took 3.790855407714844e-05s
Believability | Calculation of trust value for Norway catch records dataset took 1.2636184692382812e-05s
INFO | --- Analysis for Norway catch records dataset took 2.2135212421417236s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.601478576660156e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.27063632011413574s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.3679466247558594s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.018075942993164062s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0005285739898681641s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 9.918212890625e-05s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.2159347534179688e-05s
INFO | --- Analysis for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 22.759276866912842s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 1.0080299377441406s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3793210983276367s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.5706729888916016s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.01809382438659668s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0005214214324951172s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 3.409385681152344e-05s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 1.1920928955078125e-05s
INFO | --- Analysis for Linked Data Cultural Heritage Agency of the Netherlands took 3.894756555557251s
Availability | SPARQL endpoint availability check for Charging Stations took 8.893013000488281e-05s
Availability | VoID file availability check for Charging Stations took 5.9604644775390625e-06s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.33832311630249023s
Reputation | Calculation of the PageRank for Charging Stations took 0.01827073097229004s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.000522613525390625s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 1.2636184692382812e-05s
Believability | Calculation of trust value for Charging Stations took 8.344650268554688e-06s
INFO | --- Analysis for Charging Stations took 2.4354965686798096s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.1961669921875e-05s
Availability | VoID file availability check for Chat Game corpus took 8.344650268554688e-06s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.3399345874786377s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.018042564392089844s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0005519390106201172s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.4332275390625e-05s
Believability | Calculation of trust value for Chat Game corpus took 1.239776611328125e-05s
INFO | --- Analysis for Chat Game corpus took 12.447731256484985s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 1.67549729347229s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.6384584903717041s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.36420416831970215s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.018378496170043945s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0005562305450439453s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.719329833984375e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 1.1205673217773438e-05s
INFO | --- Analysis for Chemical Entities of Biological Interest (ChEBI) took 4.769097089767456s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.267692565917969e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.5305142402648926s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.7955646514892578s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.01840662956237793s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0005590915679931641s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.340576171875e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 1.0728836059570312e-05s
INFO | --- Analysis for Chem2Bio2RDF took 4.725218772888184s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.628251314163208s
Availability | VoID file availability check for ChEMBL RDF took 0.25111842155456543s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.4977388381958008s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.018454790115356445s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0005404949188232422s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 4.887580871582031e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.33514404296875e-05s
INFO | --- Analysis for ChEMBL RDF took 3.939239025115967s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 8.845329284667969e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.9844398498535156s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 1.3533570766448975s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.01825714111328125s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0005261898040771484s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 1.2159347534179688e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.1444091796875e-05s
INFO | --- Analysis for ChemPedia RDF took 16.093722820281982s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 8.535385131835938e-05s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 5.0067901611328125e-06s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.5060219764709473s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.019727230072021484s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0005517005920410156s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 1.3828277587890625e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 1.1444091796875e-05s
INFO | --- Analysis for Chinese Red Song Linked Data Dataset took 8.346569776535034s
Availability | SPARQL endpoint availability check for Chronicling America took 0.00012946128845214844s
Availability | VoID file availability check for Chronicling America took 0.8688724040985107s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.4418301582336426s
Reputation | Calculation of the PageRank for Chronicling America took 0.018337011337280273s
Interlinking | Calculation of Degree of Connection for Chronicling America took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Chronicling America took 0.0005314350128173828s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00010538101196289062s
Believability | Calculation of trust value for Chronicling America took 1.1682510375976562e-05s
INFO | --- Analysis for Chronicling America took 254.8931369781494s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.8171238899230957s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 1.2016973495483398s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 64.73461747169495s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.9015190601348877s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 1.3166587352752686s
Interoperability | New terms check for Cultural Heritage Thesaurus took 1.783290147781372s
Versatility | Languages check for Cultural Heritage Thesaurus took 2.990053415298462s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 1.571784496307373s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.3272123336791992s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.31431102752685547s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 6.935417175292969s
License | MR license check for Cultural Heritage Thesaurus took 0.33165502548217773s
License | HR license check for Cultural Heritage Thesaurus took 0.4751884937286377s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.3326449394226074s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.42256999015808105s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.6571934223175049s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.32253479957580566s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.4743838310241699s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.32128405570983887s
Performance | Throughput check for Cultural Heritage Thesaurus took 10.599437713623047s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 8.368492126464844e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.4642021656036377s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.34253668785095215s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.3649756908416748s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.35863661766052246s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.329059362411499s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.51017165184021s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.4518115520477295s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 21.684755563735962s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 1.0077648162841797s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.3402533531188965s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.31290745735168457s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.31236863136291504s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 5.440284967422485s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.22401165962219238s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.3284037113189697s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 4.521852731704712s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.3513355255126953s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 4.372936487197876s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 3.8028392791748047s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00013256072998046875s
Security | Sign check for Cultural Heritage Thesaurus took 0.3480057716369629s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.5492305755615234s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.018663883209228516s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0005755424499511719s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.00010061264038085938s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 0.5129120349884033s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for Cultural Heritage Thesaurus took 483.65522027015686s
Availability | SPARQL endpoint availability check for ciard-ring took 9.417533874511719e-05s
Availability | VoID file availability check for ciard-ring took 7.152557373046875e-06s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.37285685539245605s
Reputation | Calculation of the PageRank for ciard-ring took 0.01920318603515625s
Interlinking | Calculation of Degree of Connection for ciard-ring took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ciard-ring took 0.0005161762237548828s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.4345855712890625e-05s
Believability | Calculation of trust value for ciard-ring took 1.2636184692382812e-05s
INFO | --- Analysis for ciard-ring took 3.3648788928985596s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 0.7720859050750732s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 1.4223299026489258s
Extra | Recovery of all triples for Cinémathèque québécoise Linked Open Data took 21.37394380569458s
Performance | Total latancy measurement for Cinémathèque québécoise Linked Open Data took 2.166465997695923s
Amount of data | Number of triples check for Cinémathèque québécoise Linked Open Data took 7.099838972091675s
Interoperability | New terms check for Cinémathèque québécoise Linked Open Data took 1.734208583831787s
Versatility | Languages check for Cinémathèque québécoise Linked Open Data took 60.48312449455261s
Interpretability | Number of blank nodes check for Cinémathèque québécoise Linked Open Data took 4.537016868591309s
Interpretability | RDF structures check for Cinémathèque québécoise Linked Open Data took 0.45954036712646484s
Versatility | Serialization formats check for Cinémathèque québécoise Linked Open Data took 0.386075496673584s
Availability | RDF dump link check for Cinémathèque québécoise Linked Open Data took 0.41234803199768066s
License | MR license check for Cinémathèque québécoise Linked Open Data took 0.4702334403991699s
License | HR license check for Cinémathèque québécoise Linked Open Data took 23.04879665374756s
Amount of data | Number of property check for Cinémathèque québécoise Linked Open Data took 0.45226407051086426s
Understandability | Number of label check for Cinémathèque québécoise Linked Open Data took 1.6309103965759277s
Understandability | URI regex check for Cinémathèque québécoise Linked Open Data took 0.8238928318023682s
Understandability | Vocabs check for Cinémathèque québécoise Linked Open Data took 0.4625101089477539s
Verifiability | Authors check for Cinémathèque québécoise Linked Open Data took 0.43109774589538574s
Verifiability | Publishers check for Cinémathèque québécoise Linked Open Data took 0.43083810806274414s
Performance | Throughput check for Cinémathèque québécoise Linked Open Data took 13.028189420700073s
Amount of data | Check the number of entities for Cinémathèque québécoise Linked Open Data took 8.749961853027344e-05s
Verifiability | Contribs. check for Cinémathèque québécoise Linked Open Data took 0.46490049362182617s
Interlinking | sameAs chians check for Cinémathèque québécoise Linked Open Data took 0.5101463794708252s
Interlinking | skos check for Cinémathèque québécoise Linked Open Data took 0.45853328704833984s
Interlinking | skos check for Cinémathèque québécoise Linked Open Data took 0.38846564292907715s
Timeliness | dataset update frequency check for Cinémathèque québécoise Linked Open Data took 0.4323747158050537s
Currency | Creation date check for Cinémathèque québécoise Linked Open Data took 0.43340325355529785s
Currency | Modification date check for Cinémathèque québécoise Linked Open Data took 0.8701796531677246s
Rep.Conc. | URIs length for Cinémathèque québécoise Linked Open Data took 19.77860403060913s
Interoperability | New vocabularies check for Cinémathèque québécoise Linked Open Data took 13.552150011062622s
Consistency | Deprecated classes/propertiers check for Cinémathèque québécoise Linked Open Data took 0.4003472328186035s
Accuracy | Check Functional Property for Cinémathèque québécoise Linked Open Data took 0.44266843795776367s
Accuracy | Check Inverse Functional Property for Cinémathèque québécoise Linked Open Data took 0.46446943283081055s
Accuracy | Check Empty annotation labels for Cinémathèque québécoise Linked Open Data took 9.897233486175537s
Accuracy | Check White space in annotation for Cinémathèque québécoise Linked Open Data took 2.0149025917053223s
Accuracy | Check Datatype consistency for Cinémathèque québécoise Linked Open Data took 3.4835407733917236s
Consistency | Disjoint class check for Cinémathèque québécoise Linked Open Data took 0.465472936630249s
Consistency | Check Misplaced properties for Cinémathèque québécoise Linked Open Data took 0.8784375190734863s
Consistency | Misplaced classes for Cinémathèque québécoise Linked Open Data took 8.0154709815979s
Consistency | Check Ontology hijacking for Cinémathèque québécoise Linked Open Data took 18.32062864303589s
Consistency | Check Invalid usage of undefined classes for Cinémathèque québécoise Linked Open Data took 1.3472096920013428s
Consistency | Check Invalid usage of undefined properties for Cinémathèque québécoise Linked Open Data took 1.7449471950531006s
Conciseness | Check Extensional conciseness for Cinémathèque québécoise Linked Open Data took 2.8192505836486816s
Conciseness | Check Intensional conciseness for Cinémathèque québécoise Linked Open Data took 0.8482534885406494s
Security | Sign check for Cinémathèque québécoise Linked Open Data took 0.49959492683410645s
Availability | Check URIs Dereferenciability for Cinémathèque québécoise Linked Open Data took 19.469587564468384s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.46171045303344727s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.018474817276000977s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0005235671997070312s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 6.0558319091796875e-05s
Interoperability | Check the re-using of existing vocabs for Cinémathèque québécoise Linked Open Data took 12.426777839660645s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 1.9073486328125e-05s
INFO | --- Analysis for Cinémathèque québécoise Linked Open Data took 469.52310514450073s
Availability | SPARQL endpoint availability check for CIPFA took 8.726119995117188e-05s
Availability | VoID file availability check for CIPFA took 0.10472369194030762s
Completeness | Calculation of interlinking completeness for CIPFA took 0.3510115146636963s
Reputation | Calculation of the PageRank for CIPFA took 0.01851487159729004s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.000522613525390625s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.886222839355469e-05s
Believability | Calculation of trust value for CIPFA took 8.106231689453125e-06s
INFO | --- Analysis for CIPFA took 2.548544406890869s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.046740770339966s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 40.03189134597778s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.45118212699890137s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.018386363983154297s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0005667209625244141s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.00040268898010253906s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 1.1682510375976562e-05s
INFO | --- Analysis for Comprehensive Knowledge Archive Network took 262.3985629081726s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 0.8046627044677734s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.1697390079498291s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.3869647979736328s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.018329381942749023s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0005514621734619141s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 9.703636169433594e-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 4.360315561294556s
Availability | SPARQL endpoint availability check for CLLD-afbo took 8.797645568847656e-05s
Availability | VoID file availability check for CLLD-afbo took 0.3013002872467041s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.3739898204803467s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.019214868545532227s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0005524158477783203s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.748603820800781e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-afbo took 2.384185791015625e-06s
Believability | Calculation of trust value for CLLD-afbo took 1.1205673217773438e-05s
INFO | --- Analysis for CLLD-afbo took 3.905561923980713s
Availability | SPARQL endpoint availability check for CLLD-APICS took 8.940696716308594e-05s
Availability | VoID file availability check for CLLD-APICS took 0.2659885883331299s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.5093481540679932s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.018208980560302734s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0005497932434082031s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.605552673339844e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-APICS took 1.6689300537109375e-06s
Believability | Calculation of trust value for CLLD-APICS took 1.2159347534179688e-05s
INFO | --- Analysis for CLLD-APICS took 4.886549711227417s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 8.606910705566406e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.29181957244873047s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.36932969093322754s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.018227815628051758s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0005359649658203125s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.8623809814453125e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-EWAVE took 2.384185791015625e-06s
Believability | Calculation of trust value for CLLD-EWAVE took 1.1444091796875e-05s
INFO | --- Analysis for CLLD-EWAVE took 5.112346410751343s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 8.821487426757812e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.2795834541320801s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.3645741939544678s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.018169403076171875s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0005266666412353516s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 9.870529174804688e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-GLOTTOLOG took 2.1457672119140625e-06s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 1.239776611328125e-05s
INFO | --- Analysis for CLLD-GLOTTOLOG took 4.664756774902344s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 8.654594421386719e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.2771306037902832s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.38968753814697266s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.019491195678710938s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.00052642822265625s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 8.296966552734375e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-PHOIBLE took 2.1457672119140625e-06s
Believability | Calculation of trust value for CLLD-PHOIBLE took 1.0728836059570312e-05s
INFO | --- Analysis for CLLD-PHOIBLE took 4.288809537887573s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 0.00011134147644042969s
Availability | VoID file availability check for CLLD-SAILS took 0.28078532218933105s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.35321807861328125s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.018538951873779297s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0005450248718261719s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 8.702278137207031e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-SAILS took 2.86102294921875e-06s
Believability | Calculation of trust value for CLLD-SAILS took 1.2159347534179688e-05s
INFO | --- Analysis for CLLD-SAILS took 5.201298952102661s
Availability | SPARQL endpoint availability check for CLLD-WALS took 0.00010037422180175781s
Availability | VoID file availability check for CLLD-WALS took 0.2759077548980713s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.36309051513671875s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.018891334533691406s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0005385875701904297s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.535385131835938e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-WALS took 2.86102294921875e-06s
Believability | Calculation of trust value for CLLD-WALS took 7.62939453125e-06s
INFO | --- Analysis for CLLD-WALS took 4.522386312484741s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 5.936622619628906e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.2466442584991455s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.35620832443237305s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.018303394317626953s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0005288124084472656s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.653236389160156e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-WOLD took 2.384185791015625e-06s
Believability | Calculation of trust value for CLLD-WOLD took 1.3113021850585938e-05s
INFO | --- Analysis for CLLD-WOLD took 4.000607490539551s
Availability | SPARQL endpoint availability check for COD inventory took 0.2993474006652832s
Availability | VoID file availability check for COD inventory took 7.867813110351562e-06s
Completeness | Calculation of interlinking completeness for COD inventory took 0.3810582160949707s
Reputation | Calculation of the PageRank for COD inventory took 0.018827199935913086s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.0005156993865966797s
Interlinking | Calculation of Clustering coefficient for COD inventory took 1.2874603271484375e-05s
Believability | Calculation of trust value for COD inventory took 1.049041748046875e-05s
INFO | --- Analysis for COD inventory took 2.9585883617401123s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.21148133277893066s
Availability | VoID file availability check for Cooperation Databank took 0.007381439208984375s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.3981349468231201s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.01844167709350586s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0005252361297607422s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.933906555175781e-05s
Believability | Calculation of trust value for Cooperation Databank took 1.0728836059570312e-05s
INFO | --- Analysis for Cooperation Databank took 2.4159488677978516s
Availability | SPARQL endpoint availability check for CODE Endpoint took 260.44479513168335s
Availability | VoID file availability check for CODE Endpoint took 6.67572021484375e-06s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.6731655597686768s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.020414113998413086s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0005288124084472656s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 1.5020370483398438e-05s
Believability | Calculation of trust value for CODE Endpoint took 1.1920928955078125e-05s
INFO | --- Analysis for CODE Endpoint took 394.44235467910767s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 1.1858561038970947s
Availability | VoID file availability check for OpenUpLabs COINS took 1.109834909439087s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.35332202911376953s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.018868207931518555s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0005171298980712891s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 1.2636184692382812e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 1.049041748046875e-05s
INFO | --- Analysis for OpenUpLabs COINS took 4.576548337936401s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.08061432838439941s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.01564478874206543s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.478670597076416s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.019315004348754883s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0005648136138916016s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.933906555175781e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 1.1682510375976562e-05s
INFO | --- Analysis for COLINDA - Conference Linked Data took 2.3377671241760254s
Availability | SPARQL endpoint availability check for CN  2012 took 25.688355684280396s
Availability | VoID file availability check for CN  2012 took 1.6336538791656494s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.3680710792541504s
Reputation | Calculation of the PageRank for CN  2012 took 0.01830887794494629s
Interlinking | Calculation of Degree of Connection for CN  2012 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CN  2012 took 0.0005314350128173828s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 3.838539123535156e-05s
Believability | Calculation of trust value for CN  2012 took 9.059906005859375e-06s
INFO | --- Analysis for CN  2012 took 100.64752674102783s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 2.8313000202178955s
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.85234212875366s
Performance | Total latancy measurement for Comments on Literature in Literature (CoLiL) took 9.456059694290161s
Amount of data | Number of triples check for Comments on Literature in Literature (CoLiL) took 225.39690399169922s
Interoperability | New terms check for Comments on Literature in Literature (CoLiL) took 138.86750102043152s
Versatility | Languages check for Comments on Literature in Literature (CoLiL) took 301.5960030555725s
Interpretability | Number of blank nodes check for Comments on Literature in Literature (CoLiL) took 105.33732628822327s
Security | Check HTTPS for Comments on Literature in Literature (CoLiL) took 1.2139201164245605s
Interpretability | RDF structures check for Comments on Literature in Literature (CoLiL) took 1.8602087497711182s
Versatility | Serialization formats check for Comments on Literature in Literature (CoLiL) took 1.8531413078308105s
Availability | RDF dump link check for Comments on Literature in Literature (CoLiL) took 1.9000568389892578s
License | MR license check for Comments on Literature in Literature (CoLiL) took 1.8922889232635498s
License | HR license check for Comments on Literature in Literature (CoLiL) took 2.0384488105773926s
Amount of data | Number of property check for Comments on Literature in Literature (CoLiL) took 2.053356885910034s
Understandability | Number of label check for Comments on Literature in Literature (CoLiL) took 2.1515614986419678s
Understandability | URI regex check for Comments on Literature in Literature (CoLiL) took 4.117202997207642s
Understandability | Vocabs check for Comments on Literature in Literature (CoLiL) took 1.9328312873840332s
Verifiability | Authors check for Comments on Literature in Literature (CoLiL) took 1.8647167682647705s
Verifiability | Publishers check for Comments on Literature in Literature (CoLiL) took 1.8809654712677002s
Performance | Throughput check for Comments on Literature in Literature (CoLiL) took 17.735305070877075s
Amount of data | Check the number of entities for Comments on Literature in Literature (CoLiL) took 6.818771362304688e-05s
Verifiability | Contribs. check for Comments on Literature in Literature (CoLiL) took 1.7962079048156738s
Interlinking | sameAs chians check for Comments on Literature in Literature (CoLiL) took 1.8146049976348877s
Interlinking | skos check for Comments on Literature in Literature (CoLiL) took 2.23124098777771s
Interlinking | skos check for Comments on Literature in Literature (CoLiL) took 1.78375244140625s
Timeliness | dataset update frequency check for Comments on Literature in Literature (CoLiL) took 1.8062329292297363s
Currency | Creation date check for Comments on Literature in Literature (CoLiL) took 1.8408379554748535s
Currency | Modification date check for Comments on Literature in Literature (CoLiL) took 1.799987554550171s
Rep.Conc. | URIs length for Comments on Literature in Literature (CoLiL) took 476.87518978118896s
Interoperability | New vocabularies check for Comments on Literature in Literature (CoLiL) took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Comments on Literature in Literature (CoLiL) took 1.8530054092407227s
Accuracy | Check Functional Property for Comments on Literature in Literature (CoLiL) took 1.8770506381988525s
Accuracy | Check Inverse Functional Property for Comments on Literature in Literature (CoLiL) took 1.8462812900543213s
Accuracy | Check Empty annotation labels for Comments on Literature in Literature (CoLiL) took 2.4752893447875977s
Accuracy | Check White space in annotation for Comments on Literature in Literature (CoLiL) took 0.0009391307830810547s
Accuracy | Check Datatype consistency for Comments on Literature in Literature (CoLiL) took 2.7767302989959717s
Consistency | Disjoint class check for Comments on Literature in Literature (CoLiL) took 2.4137866497039795s
Consistency | Check Misplaced properties for Comments on Literature in Literature (CoLiL) took 303.4763512611389s
Consistency | Misplaced classes for Comments on Literature in Literature (CoLiL) took 11.234025239944458s
Consistency | Check Ontology hijacking for Comments on Literature in Literature (CoLiL) took 35.32268691062927s
Consistency | Check Invalid usage of undefined classes for Comments on Literature in Literature (CoLiL) took 1.2953200340270996s
Consistency | Check Invalid usage of undefined properties for Comments on Literature in Literature (CoLiL) took 303.1550853252411s
Conciseness | Check Extensional conciseness for Comments on Literature in Literature (CoLiL) took 2.708447217941284s
Conciseness | Check Intensional conciseness for Comments on Literature in Literature (CoLiL) took 2.3568615913391113s
Security | Sign check for Comments on Literature in Literature (CoLiL) took 3.4278762340545654s
Availability | Check URIs Dereferenciability for Comments on Literature in Literature (CoLiL) took 3.938812732696533s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.9471850395202637s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.018426895141601562s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.0005116462707519531s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 2.1457672119140625e-05s
Interoperability | Check the re-using of existing vocabs for Comments on Literature in Literature (CoLiL) took 1.1920928955078125e-06s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 7.3909759521484375e-06s
INFO | --- Analysis for Comments on Literature in Literature (CoLiL) took 3252.6247668266296s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 0.00010514259338378906s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.3223416805267334s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.3791391849517822s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.018186092376708984s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0005502700805664062s
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 6.67572021484375e-06s
INFO | --- Analysis for Comparative analysis of production volume by area of strawberry by period took 45.09773564338684s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 4.410743713378906e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.013549566268920898s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.4214920997619629s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.018178701400756836s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0005307197570800781s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 1.4066696166992188e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 1.0728836059570312e-05s
INFO | --- Analysis for Price competitiveness of pear by region took 12.460261821746826s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 4.1961669921875e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.01633596420288086s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.36019134521484375s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.019866943359375s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0005202293395996094s
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 1.0728836059570312e-05s
INFO | --- Analysis for Comparative analysis of production volume by area of watermelon by period took 52.918599367141724s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 4.100799560546875e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.012980937957763672s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.3715081214904785s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.01830148696899414s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0005331039428710938s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 1.3589859008789062e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 9.775161743164062e-06s
INFO | --- Analysis for Price competitiveness of grape by region took 23.861546993255615s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 0.8238539695739746s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.49348878860473633s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.7267732620239258s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.01959061622619629s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0005252361297607422s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.528594970703125e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 7.3909759521484375e-06s
INFO | --- Analysis for Requirements on the COMSODE project based on selected datasets took 6.06358528137207s
Availability | SPARQL endpoint availability check for ConceptNet took 8.320808410644531e-05s
Availability | VoID file availability check for ConceptNet took 2.4935085773468018s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.42848873138427734s
Reputation | Calculation of the PageRank for ConceptNet took 0.020144939422607422s
Interlinking | Calculation of Degree of Connection for ConceptNet took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for ConceptNet took 0.0005397796630859375s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 1.239776611328125e-05s
Believability | Calculation of trust value for ConceptNet took 1.0967254638671875e-05s
INFO | --- Analysis for ConceptNet took 7.060035943984985s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 8.821487426757812e-05s
Availability | VoID file availability check for 2011 US Congress People took 3.259136438369751s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.3546426296234131s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.018126487731933594s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0005207061767578125s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.416175842285156e-05s
Believability | Calculation of trust value for 2011 US Congress People took 1.0013580322265625e-05s
INFO | --- Analysis for 2011 US Congress People took 7.508210897445679s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 2.315481424331665s
Availability | VoID file availability check for LODsyndesis Dataset took 0.0020482540130615234s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.6467132568359375s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.01846456527709961s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0005414485931396484s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 1.430511474609375e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 1.239776611328125e-05s
INFO | --- Analysis for LODsyndesis Dataset took 29.584099531173706s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 30.445383548736572s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 20.008639097213745s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.44116854667663574s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.02100062370300293s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0005459785461425781s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.5020370483398438e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.3589859008789062e-05s
INFO | --- Analysis for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 213.22479057312012s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 8.440017700195312e-05s
Availability | VoID file availability check for CopyrightTermBank took 1.0013580322265625e-05s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.6385877132415771s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.018732309341430664s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0005314350128173828s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 7.128715515136719e-05s
Believability | Calculation of trust value for CopyrightTermBank took 1.239776611328125e-05s
INFO | --- Analysis for CopyrightTermBank took 36.417216300964355s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 1.6224431991577148s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.4864010810852051s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.37059950828552246s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.018509387969970703s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0005247592926025391s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 4.0531158447265625e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 1.239776611328125e-05s
INFO | --- Analysis for CORE - Semantic Similarity of Open Access publications took 9.348702669143677s
Availability | SPARQL endpoint availability check for Corine linked dataset took 0.00010061264038085938s
Availability | VoID file availability check for Corine linked dataset took 5.7220458984375e-06s
Completeness | Calculation of interlinking completeness for Corine linked dataset took 0.39996981620788574s
Reputation | Calculation of the PageRank for Corine linked dataset took 0.019620656967163086s
Interlinking | Calculation of Degree of Connection for Corine linked dataset took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Corine linked dataset took 0.0005445480346679688s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset took 1.2874603271484375e-05s
Believability | Calculation of trust value for Corine linked dataset took 1.1920928955078125e-05s
INFO | --- Analysis for Corine linked dataset took 2.3634352684020996s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.00010442733764648438s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.014471769332885742s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.36217212677001953s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.018558979034423828s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0005180835723876953s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.5974044799804688e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 9.775161743164062e-06s
INFO | --- Analysis for Corn's Famous mountainous district (Hongcheon) Environmental Status took 57.42345333099365s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 8.893013000488281e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.01698470115661621s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.3785898685455322s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.020844459533691406s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0005276203155517578s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 1.4066696166992188e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 1.1920928955078125e-05s
INFO | --- Analysis for Corn's Famous mountainous district (Goesan) Environmental Status took 23.917340755462646s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 8.559226989746094e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.016361713409423828s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.4549684524536133s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.019727230072021484s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0005290508270263672s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.3828277587890625e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.1920928955078125e-05s
INFO | --- Analysis for Corn's Famous mountainous district (Jeongseon) Environmental Status took 26.84758973121643s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 8.916854858398438e-05s
Availability | VoID file availability check for Cornetto1.2 took 1.330134630203247s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.7114360332489014s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.018438339233398438s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0005311965942382812s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.91278076171875e-05s
Believability | Calculation of trust value for Cornetto1.2 took 1.2159347534179688e-05s
INFO | --- Analysis for Cornetto1.2 took 9.296163558959961s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.30179476737976074s
Availability | VoID file availability check for Corporate Body Named Authority List  took 5.081692934036255s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 289.6024992465973s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.6960775852203369s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 26.922553300857544s
Interoperability | New terms check for Corporate Body Named Authority List  took 31.094496965408325s
Versatility | Languages check for Corporate Body Named Authority List  took 300.10421657562256s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 10.744582891464233s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.43668246269226074s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.5203046798706055s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 0.2502453327178955s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.2002854347229004s
License | MR license check for Corporate Body Named Authority List  took 0.2419288158416748s
License | HR license check for Corporate Body Named Authority List  took 6.025087118148804s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.12627649307250977s
Understandability | Number of label check for Corporate Body Named Authority List  took 1.2729861736297607s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.26494383811950684s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.0956418514251709s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.28938937187194824s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.18633794784545898s
Performance | Throughput check for Corporate Body Named Authority List  took 10.484183549880981s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 0.00010347366333007812s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.2172698974609375s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 5.962444067001343s
Interlinking | skos check for Corporate Body Named Authority List  took 0.33507418632507324s
Interlinking | skos check for Corporate Body Named Authority List  took 0.12586688995361328s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.25475215911865234s
Currency | Creation date check for Corporate Body Named Authority List  took 1.5126221179962158s
Currency | Modification date check for Corporate Body Named Authority List  took 0.13277244567871094s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 296.2332227230072s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.16963958740234375s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.1893303394317627s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.21146559715270996s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 61.770177125930786s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.189474582672119s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.724325180053711s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.20073294639587402s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 198.5335829257965s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.660887956619263s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 57.692094564437866s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.7702302932739258s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 197.7129406929016s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 3.0057356357574463s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.35751771926879883s
Security | Sign check for Corporate Body Named Authority List  took 0.1409282684326172s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 3.5317649841308594s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 0.7183244228363037s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.018488168716430664s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 5.745887756347656e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 2.384185791015625e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 7.62939453125e-06s
INFO | --- Analysis for Corporate Body Named Authority List  took 11299.359073400497s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.09987258911132812s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.015936851501464844s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.4340054988861084s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.020238876342773438s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0005254745483398438s
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.1682510375976562e-05s
INFO | --- Analysis for CORS Check - HTTP Header Logs for Linked Open Data took 2.239877223968506s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.0949869155883789s
Availability | VoID file availability check for Country Name Authority List took 4.828620910644531s
Extra | Recovery of all triples for Country Name Authority List took 273.55545806884766s
Performance | Total latancy measurement for Country Name Authority List took 0.6028316020965576s
Amount of data | Number of triples check for Country Name Authority List took 26.440787315368652s
Interoperability | New terms check for Country Name Authority List took 31.190804481506348s
Versatility | Languages check for Country Name Authority List took 300.10451674461365s
Interpretability | Number of blank nodes check for Country Name Authority List took 9.39845609664917s
Security | Check HTTPS for Country Name Authority List took 0.33196544647216797s
Interpretability | RDF structures check for Country Name Authority List took 0.24582910537719727s
Versatility | Serialization formats check for Country Name Authority List took 0.2975177764892578s
Availability | RDF dump link check for Country Name Authority List took 0.18840622901916504s
License | MR license check for Country Name Authority List took 0.3908510208129883s
License | HR license check for Country Name Authority List took 6.670423746109009s
Amount of data | Number of property check for Country Name Authority List took 0.13307476043701172s
Understandability | Number of label check for Country Name Authority List took 1.2307658195495605s
Understandability | URI regex check for Country Name Authority List took 0.2679319381713867s
Understandability | Vocabs check for Country Name Authority List took 0.10773372650146484s
Verifiability | Authors check for Country Name Authority List took 0.13083696365356445s
Verifiability | Publishers check for Country Name Authority List took 0.17870354652404785s
Performance | Throughput check for Country Name Authority List took 10.662526845932007s
Amount of data | Check the number of entities for Country Name Authority List took 0.00044536590576171875s
Verifiability | Contribs. check for Country Name Authority List took 0.15270686149597168s
Interlinking | sameAs chians check for Country Name Authority List took 8.009087085723877s
Interlinking | skos check for Country Name Authority List took 0.3061182498931885s
Interlinking | skos check for Country Name Authority List took 0.3079564571380615s
Timeliness | dataset update frequency check for Country Name Authority List took 0.18900084495544434s
Currency | Creation date check for Country Name Authority List took 0.9752821922302246s
Currency | Modification date check for Country Name Authority List took 0.14387249946594238s
Rep.Conc. | URIs length for Country Name Authority List took 301.69601821899414s
Interoperability | New vocabularies check for Country Name Authority List took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.1503286361694336s
Accuracy | Check Functional Property for Country Name Authority List took 0.17953062057495117s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.17338228225708008s
Accuracy | Check Empty annotation labels for Country Name Authority List took 64.80958867073059s
Accuracy | Check White space in annotation for Country Name Authority List took 3.1149260997772217s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.625775098800659s
Consistency | Disjoint class check for Country Name Authority List took 0.1543726921081543s
Consistency | Check Misplaced properties for Country Name Authority List took 201.8128695487976s
Consistency | Misplaced classes for Country Name Authority List took 8.552842855453491s
Consistency | Check Ontology hijacking for Country Name Authority List took 55.764936208724976s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.5598714351654053s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 199.9118824005127s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.02506685256958s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.3753373622894287s
Security | Sign check for Country Name Authority List took 0.19483661651611328s
Availability | Check URIs Dereferenciability for Country Name Authority List took 3.4569807052612305s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 0.7964422702789307s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.01914501190185547s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0005168914794921875s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 6.437301635742188e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 1.6689300537109375e-06s
Believability | Calculation of trust value for Country Name Authority List took 1.5020370483398438e-05s
INFO | --- Analysis for Country Name Authority List took 9438.374452829361s
Availability | SPARQL endpoint availability check for Courts thesaurus took 30.15091347694397s
Availability | VoID file availability check for Courts thesaurus took 20.095934629440308s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.3000645637512207s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.02043604850769043s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0005333423614501953s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 7.605552673339844e-05s
Believability | Calculation of trust value for Courts thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for Courts thesaurus took 92.66789388656616s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 0.3380625247955322s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.4043915271759033s
Extra | Recovery of all triples for Covid-on-the-Web Dataset took 2.337263822555542s
Performance | Total latancy measurement for Covid-on-the-Web Dataset took 0.6092724800109863s
Amount of data | Number of triples check for Covid-on-the-Web Dataset took 24.544825077056885s
Interoperability | New terms check for Covid-on-the-Web Dataset took 8.936429738998413s
Versatility | Languages check for Covid-on-the-Web Dataset took 300.11802792549133s
Interpretability | Number of blank nodes check for Covid-on-the-Web Dataset took 70.60870099067688s
Interpretability | RDF structures check for Covid-on-the-Web Dataset took 0.6472418308258057s
Versatility | Serialization formats check for Covid-on-the-Web Dataset took 0.2872591018676758s
Availability | RDF dump link check for Covid-on-the-Web Dataset took 99.74109983444214s
License | MR license check for Covid-on-the-Web Dataset took 0.17798995971679688s
License | HR license check for Covid-on-the-Web Dataset took 259.5874569416046s
Amount of data | Number of property check for Covid-on-the-Web Dataset took 0.12577342987060547s
Understandability | Number of label check for Covid-on-the-Web Dataset took 1.4400055408477783s
Understandability | URI regex check for Covid-on-the-Web Dataset took 0.533238410949707s
Understandability | Vocabs check for Covid-on-the-Web Dataset took 0.14029860496520996s
Verifiability | Authors check for Covid-on-the-Web Dataset took 0.7502691745758057s
Verifiability | Publishers check for Covid-on-the-Web Dataset took 0.13644146919250488s
Performance | Throughput check for Covid-on-the-Web Dataset took 10.608173131942749s
Amount of data | Check the number of entities for Covid-on-the-Web Dataset took 0.10773539543151855s
Verifiability | Contribs. check for Covid-on-the-Web Dataset took 0.14192795753479004s
Interlinking | sameAs chians check for Covid-on-the-Web Dataset took 0.12836098670959473s
Interlinking | skos check for Covid-on-the-Web Dataset took 0.13266587257385254s
Interlinking | skos check for Covid-on-the-Web Dataset took 0.10741496086120605s
Timeliness | dataset update frequency check for Covid-on-the-Web Dataset took 0.44167470932006836s
Currency | Creation date check for Covid-on-the-Web Dataset took 0.11850094795227051s
Currency | Modification date check for Covid-on-the-Web Dataset took 0.10716056823730469s
Rep.Conc. | URIs length for Covid-on-the-Web Dataset took 45.174702882766724s
Interoperability | New vocabularies check for Covid-on-the-Web Dataset took 16.298752784729004s
Consistency | Deprecated classes/propertiers check for Covid-on-the-Web Dataset took 0.13221979141235352s
Accuracy | Check Functional Property for Covid-on-the-Web Dataset took 0.2102065086364746s
Accuracy | Check Inverse Functional Property for Covid-on-the-Web Dataset took 0.18950104713439941s
Accuracy | Check Empty annotation labels for Covid-on-the-Web Dataset took 1.4349822998046875s
Accuracy | Check White space in annotation for Covid-on-the-Web Dataset took 0.0666048526763916s
Accuracy | Check Datatype consistency for Covid-on-the-Web Dataset took 0.082000732421875s
Consistency | Disjoint class check for Covid-on-the-Web Dataset took 0.11095261573791504s
Consistency | Check Misplaced properties for Covid-on-the-Web Dataset took 28.991987705230713s
Consistency | Misplaced classes for Covid-on-the-Web Dataset took 1.0772159099578857s
Consistency | Check Ontology hijacking for Covid-on-the-Web Dataset took 2.160240411758423s
Consistency | Check Invalid usage of undefined classes for Covid-on-the-Web Dataset took 1.2870543003082275s
Consistency | Check Invalid usage of undefined properties for Covid-on-the-Web Dataset took 30.00656032562256s
Conciseness | Check Extensional conciseness for Covid-on-the-Web Dataset took 0.08631610870361328s
Conciseness | Check Intensional conciseness for Covid-on-the-Web Dataset took 1.4026062488555908s
Security | Sign check for Covid-on-the-Web Dataset took 0.2648353576660156s
Availability | Check URIs Dereferenciability for Covid-on-the-Web Dataset took 1730.9385142326355s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.7245800495147705s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.02095198631286621s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0005548000335693359s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 9.417533874511719e-05s
Interoperability | Check the re-using of existing vocabs for Covid-on-the-Web Dataset took 12.590814113616943s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 1.1444091796875e-05s
INFO | --- Analysis for Covid-on-the-Web Dataset took 3978.1284296512604s
Availability | SPARQL endpoint availability check for CPA 2008 took 24.511346101760864s
Availability | VoID file availability check for CPA 2008 took 1.7197647094726562s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.2825479507446289s
Reputation | Calculation of the PageRank for CPA 2008 took 0.019835472106933594s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0005311965942382812s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 5.054473876953125e-05s
Believability | Calculation of trust value for CPA 2008 took 9.5367431640625e-06s
INFO | --- Analysis for CPA 2008 took 98.9847207069397s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.4472510814666748s
Availability | VoID file availability check for Cooperative Patent Classification took 0.3542912006378174s
Extra | Recovery of all triples for Cooperative Patent Classification took 65.47821140289307s
Performance | Total latancy measurement for Cooperative Patent Classification took 0.5776889324188232s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.12578105926514s
Versatility | Languages check for Cooperative Patent Classification took 120.09476518630981s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.20040464401245s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.17050909996032715s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.11558341979980469s
Availability | RDF dump link check for Cooperative Patent Classification took 0.14270734786987305s
License | MR license check for Cooperative Patent Classification took 0.1503281593322754s
License | HR license check for Cooperative Patent Classification took 90.1183750629425s
Amount of data | Number of property check for Cooperative Patent Classification took 0.131866455078125s
Understandability | Number of label check for Cooperative Patent Classification took 90.13212370872498s
Understandability | URI regex check for Cooperative Patent Classification took 0.33826756477355957s
Understandability | Vocabs check for Cooperative Patent Classification took 0.18268537521362305s
Verifiability | Authors check for Cooperative Patent Classification took 0.14661765098571777s
Verifiability | Publishers check for Cooperative Patent Classification took 0.12422585487365723s
Performance | Throughput check for Cooperative Patent Classification took 10.571685791015625s
Amount of data | Check the number of entities for Cooperative Patent Classification took 8.7738037109375e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.11608195304870605s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.11739158630371094s
Interlinking | skos check for Cooperative Patent Classification took 0.10505104064941406s
Interlinking | skos check for Cooperative Patent Classification took 0.1464989185333252s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.09725761413574219s
Currency | Creation date check for Cooperative Patent Classification took 0.12978339195251465s
Currency | Modification date check for Cooperative Patent Classification took 0.7477185726165771s
Rep.Conc. | URIs length for Cooperative Patent Classification took 170.45865035057068s
Interoperability | New vocabularies check for Cooperative Patent Classification took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.16345691680908203s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 27.141802072525024s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 3.044745445251465s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 5.068824529647827s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.10115313529968262s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 120.30503964424133s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 36.012656927108765s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.6771798133850098s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 121.62700366973877s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.8699169158935547s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.1616535186767578s
Security | Sign check for Cooperative Patent Classification took 0.11247634887695312s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 2.9867937564849854s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.7520911693572998s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.018705129623413086s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0005645751953125s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 4.982948303222656e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 1.6689300537109375e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 1.0013580322265625e-05s
INFO | --- Analysis for Cooperative Patent Classification took 1417.6078815460205s
Availability | SPARQL endpoint availability check for CPC 2008 took 24.02596402168274s
Availability | VoID file availability check for CPC 2008 took 1.9121754169464111s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.4028334617614746s
Reputation | Calculation of the PageRank for CPC 2008 took 0.01934671401977539s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0005266666412353516s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 4.839897155761719e-05s
Believability | Calculation of trust value for CPC 2008 took 9.5367431640625e-06s
INFO | --- Analysis for CPC 2008 took 103.41930341720581s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.81608486175537s
Availability | VoID file availability check for CPV  2003 took 1.5558006763458252s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.3147304058074951s
Reputation | Calculation of the PageRank for CPV  2003 took 0.018634557723999023s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.52587890625e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0005266666412353516s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 5.054473876953125e-05s
Believability | Calculation of trust value for CPV  2003 took 9.059906005859375e-06s
INFO | --- Analysis for CPV  2003 took 93.42318391799927s
Availability | SPARQL endpoint availability check for CPV 2008 took 23.435548067092896s
Availability | VoID file availability check for CPV 2008 took 1.4714751243591309s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.27516603469848633s
Reputation | Calculation of the PageRank for CPV 2008 took 0.018275976181030273s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0005314350128173828s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 5.316734313964844e-05s
Believability | Calculation of trust value for CPV 2008 took 4.76837158203125e-06s
INFO | --- Analysis for CPV 2008 took 96.67466235160828s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 261.88792085647583s
Availability | VoID file availability check for crowdsourcing-fb took 7.62939453125e-06s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.5873563289642334s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.018842697143554688s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0005304813385009766s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.8160552978515625e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 1.3113021850585938e-05s
INFO | --- Analysis for crowdsourcing-fb took 394.8578851222992s
Availability | SPARQL endpoint availability check for CRTM took 20.35252833366394s
Availability | VoID file availability check for CRTM took 8.821487426757812e-06s
Completeness | Calculation of interlinking completeness for CRTM took 0.3025641441345215s
Reputation | Calculation of the PageRank for CRTM took 0.01889657974243164s
Interlinking | Calculation of Degree of Connection for CRTM took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0005381107330322266s
Interlinking | Calculation of Clustering coefficient for CRTM took 1.9073486328125e-05s
Believability | Calculation of trust value for CRTM took 1.0728836059570312e-05s
INFO | --- Analysis for CRTM took 42.47322702407837s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 0.36815810203552246s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.21084213256835938s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.3500819206237793s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.019499778747558594s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.000518798828125s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 1.1682510375976562e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 1.0728836059570312e-05s
INFO | --- Analysis for Crystal Eye: Aggregated Crystallographic Data took 3.584272623062134s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.571305274963379s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.15185999870300293s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 1.3461270332336426s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.01802682876586914s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0005774497985839844s
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 5.0067901611328125e-06s
INFO | --- Analysis for CTIC Public Dataset Catalogs took 43.032843351364136s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 4.57763671875e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.040920257568359375s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.794694185256958s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.018239736557006836s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0005347728729248047s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 2.1457672119140625e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 6.67572021484375e-06s
INFO | --- Analysis for Cultivation status of GMO crops took 39.115100383758545s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.25655484199523926s
Availability | VoID file availability check for CulturaLinkedData took 0.2541627883911133s
Extra | Recovery of all triples for CulturaLinkedData took 4.609381437301636s
Performance | Total latancy measurement for CulturaLinkedData took 0.5183625221252441s
Amount of data | Number of triples check for CulturaLinkedData took 0.3697855472564697s
Interoperability | New terms check for CulturaLinkedData took 1.5627529621124268s
Versatility | Languages check for CulturaLinkedData took 1.2901804447174072s
Interpretability | Number of blank nodes check for CulturaLinkedData took 0.8191061019897461s
Interpretability | RDF structures check for CulturaLinkedData took 0.16007113456726074s
Versatility | Serialization formats check for CulturaLinkedData took 0.16434049606323242s
Availability | RDF dump link check for CulturaLinkedData took 0.09010601043701172s
License | MR license check for CulturaLinkedData took 0.1179051399230957s
License | HR license check for CulturaLinkedData took 0.14917278289794922s
Amount of data | Number of property check for CulturaLinkedData took 1.257134199142456s
Understandability | Number of label check for CulturaLinkedData took 0.18167757987976074s
Understandability | URI regex check for CulturaLinkedData took 0.18389105796813965s
Understandability | Vocabs check for CulturaLinkedData took 0.09245824813842773s
Verifiability | Authors check for CulturaLinkedData took 0.10364532470703125s
Verifiability | Publishers check for CulturaLinkedData took 0.09243583679199219s
Performance | Throughput check for CulturaLinkedData took 13.982224941253662s
Amount of data | Check the number of entities for CulturaLinkedData took 9.703636169433594e-05s
Verifiability | Contribs. check for CulturaLinkedData took 0.08105063438415527s
Interlinking | sameAs chians check for CulturaLinkedData took 0.1529090404510498s
Interlinking | skos check for CulturaLinkedData took 0.15592193603515625s
Interlinking | skos check for CulturaLinkedData took 0.10488414764404297s
Timeliness | dataset update frequency check for CulturaLinkedData took 0.09828066825866699s
Currency | Creation date check for CulturaLinkedData took 0.15512657165527344s
Currency | Modification date check for CulturaLinkedData took 0.1549675464630127s
Rep.Conc. | URIs length for CulturaLinkedData took 2.3704111576080322s
Interoperability | New vocabularies check for CulturaLinkedData took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 0.6741254329681396s
Accuracy | Check Functional Property for CulturaLinkedData took 0.316267728805542s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 0.08008861541748047s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 0.38684988021850586s
Accuracy | Check White space in annotation for CulturaLinkedData took 0.0061566829681396484s
Accuracy | Check Datatype consistency for CulturaLinkedData took 0.028039932250976562s
Consistency | Disjoint class check for CulturaLinkedData took 0.10253310203552246s
Consistency | Check Misplaced properties for CulturaLinkedData took 1.4752707481384277s
Consistency | Misplaced classes for CulturaLinkedData took 0.3535122871398926s
Consistency | Check Ontology hijacking for CulturaLinkedData took 2.1423864364624023s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.3097202777862549s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 2.5706000328063965s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 0.031784772872924805s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 0.4158475399017334s
Security | Sign check for CulturaLinkedData took 0.09550213813781738s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 3.4441065788269043s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.46564435958862305s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.017469406127929688s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0005197525024414062s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 1.2159347534179688e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 1.430511474609375e-06s
Believability | Calculation of trust value for CulturaLinkedData took 1.2159347534179688e-05s
INFO | --- Analysis for CulturaLinkedData took 72.24575090408325s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.14651131629943848s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0737159252166748s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.2944827079772949s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.018301010131835938s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0005233287811279297s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 3.743171691894531e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 5.7220458984375e-06s
INFO | --- Analysis for Data about business entities from the ARES system - business registry of the Czech Republic took 2.201489210128784s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.09559321403503418s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.06931662559509277s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.29734349250793457s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.018175125122070312s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0005247592926025391s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.4809112548828125e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 5.245208740234375e-06s
INFO | --- Analysis for Data about Czech business entities from the ARES system - Trade Licensing Register took 2.1775262355804443s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.11203885078430176s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0627431869506836s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.599646806716919s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.018353700637817383s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0005176067352294922s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.337860107421875e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 1.1205673217773438e-05s
INFO | --- Analysis for Chemicals reported to the Integrated register of pollution took 5.154473543167114s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.103515625s
Availability | VoID file availability check for Integrated pollution registry took 0.07484745979309082s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.5709631443023682s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.018311500549316406s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0005300045013427734s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.886222839355469e-05s
Believability | Calculation of trust value for Integrated pollution registry took 1.0967254638671875e-05s
INFO | --- Analysis for Integrated pollution registry took 4.990567207336426s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.11620879173278809s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.07885050773620605s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.8713676929473877s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.018085718154907227s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0005297660827636719s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.933906555175781e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 8.344650268554688e-06s
INFO | --- Analysis for Registry of contracts of the Czech Republic - Contracts took 3.779381036758423s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 0.07625055313110352s
Availability | VoID file availability check for List of courts of the Czech Republic took 4.5299530029296875e-06s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.40994763374328613s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.018262386322021484s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0005135536193847656s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 1.239776611328125e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 1.1444091796875e-05s
INFO | --- Analysis for List of courts of the Czech Republic took 2.74690318107605s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.10926103591918945s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.07567524909973145s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.29361581802368164s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.01946854591369629s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0005228519439697266s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 4.3392181396484375e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 4.76837158203125e-06s
INFO | --- Analysis for Bans of the Czech Trade Inspection Authority took 4.649597406387329s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.10671210289001465s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.07869625091552734s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.30665135383605957s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.01830911636352539s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0005247592926025391s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.8623809814453125e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 7.3909759521484375e-06s
INFO | --- Analysis for Confiscations of the Czech Trade Inspection Authority took 2.067783832550049s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.1172175407409668s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.07521700859069824s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.31940627098083496s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.018584251403808594s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0005390644073486328s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.981590270996094e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 8.58306884765625e-06s
INFO | --- Analysis for Focus of the Czech Trade Inspection Authority's inspections took 2.2654130458831787s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.10468292236328125s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.07519054412841797s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.32956767082214355s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.018873929977416992s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0005259513854980469s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.363059997558594e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 8.344650268554688e-06s
INFO | --- Analysis for Inspections of the Czech Trade Inspection Authority took 2.1448426246643066s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.1116793155670166s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.07094025611877441s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.30182623863220215s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.01850581169128418s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0005424022674560547s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.910064697265625e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 8.344650268554688e-06s
INFO | --- Analysis for Sanctions of the Czech Trade Inspection Authority took 4.3699867725372314s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.20501184463500977s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.07585763931274414s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.725273609161377s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.01832294464111328s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0005192756652832031s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 4.00543212890625e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 8.821487426757812e-06s
INFO | --- Analysis for Cadastre offices from Czech land registry took 3.4438271522521973s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.10806584358215332s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.07087469100952148s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.3155529499053955s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.01925802230834961s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0005719661712646484s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.5762786865234375e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 8.821487426757812e-06s
INFO | --- Analysis for Code lists of the legal relationships and documents took 2.4250946044921875s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.4993112087249756s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.5275986194610596s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.853740930557251s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.018247127532958984s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.933906555175781e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 8.58306884765625e-06s
INFO | --- Analysis for Average salaries in regions of Czech republic took 4.720709323883057s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.30571961402893066s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.40295958518981934s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.5575366020202637s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.019423484802246094s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0005388259887695312s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 4.2438507080078125e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 9.059906005859375e-06s
INFO | --- Analysis for Deaths by selected causes of death in regions of Czech Republic took 4.042185544967651s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.28850650787353516s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.3974733352661133s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.32773923873901367s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.018418550491333008s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0005340576171875s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.3392181396484375e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.0251998901367188e-05s
INFO | --- Analysis for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.8893637657165527s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.3363993167877197s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.44855165481567383s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.31377649307250977s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.0183718204498291s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0005345344543457031s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 3.910064697265625e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 8.106231689453125e-06s
INFO | --- Analysis for Job applicants in regions of Czech Republic took 4.165815114974976s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.29839491844177246s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.4235081672668457s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.37904953956604004s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.018236160278320312s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0005261898040771484s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 4.100799560546875e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 9.059906005859375e-06s
INFO | --- Analysis for Job applicants and unemployment rate in regions of Czech Republic took 4.004704475402832s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.2774477005004883s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.4559900760650635s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.2864255905151367s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.020317554473876953s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0005233287811279297s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 4.00543212890625e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 6.67572021484375e-06s
INFO | --- Analysis for Structure of regions of Czech Republic according to Czech Statistical Office took 2.9851109981536865s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.2758171558380127s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.43477320671081543s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.3070986270904541s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.018943071365356445s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0005204677581787109s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 4.315376281738281e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 9.059906005859375e-06s
INFO | --- Analysis for Selected public health indicators in regions of Czech republic took 3.6157360076904297s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.29668545722961426s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.43149280548095703s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.3261876106262207s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.018090248107910156s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0005333423614501953s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 4.100799560546875e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 5.0067901611328125e-06s
INFO | --- Analysis for Social service facilities and nursing in districts of Czech republic took 3.622187852859497s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.27986812591552734s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.42963385581970215s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.300018310546875s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.018245220184326172s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0005290508270263672s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.838539123535156e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 7.3909759521484375e-06s
INFO | --- Analysis for Unemployment rate in regions of Czech republic took 3.4947307109832764s
Availability | SPARQL endpoint availability check for ATC groups took 0.10260677337646484s
Availability | VoID file availability check for ATC groups took 0.07953143119812012s
Completeness | Calculation of interlinking completeness for ATC groups took 0.27730679512023926s
Reputation | Calculation of the PageRank for ATC groups took 0.018485069274902344s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0005431175231933594s
Interlinking | Calculation of Clustering coefficient for ATC groups took 7.176399230957031e-05s
Believability | Calculation of trust value for ATC groups took 1.0967254638671875e-05s
INFO | --- Analysis for ATC groups took 2.458040237426758s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.10316896438598633s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.06910872459411621s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.3693351745605469s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.018166780471801758s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005207061767578125s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.600120544433594e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 9.059906005859375e-06s
INFO | --- Analysis for Registry of contracts of the Czech Republic - Financial fulfillments took 2.236135959625244s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.04581022262573242s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0023183822631835938s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.4043755531311035s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.018216848373413086s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0005381107330322266s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.8160552978515625e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 9.775161743164062e-06s
INFO | --- Analysis for Czech Business Entity identification numbers and names took 2.625028133392334s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.1134331226348877s
Availability | VoID file availability check for List of Czech data boxes took 0.13169646263122559s
Extra | Recovery of all triples for List of Czech data boxes took 144.48212003707886s
Performance | Total latancy measurement for List of Czech data boxes took 0.6209249496459961s
Amount of data | Number of triples check for List of Czech data boxes took 9.219783306121826s
Interoperability | New terms check for List of Czech data boxes took 10.227078676223755s
Versatility | Languages check for List of Czech data boxes took 300.1082811355591s
Interpretability | Number of blank nodes check for List of Czech data boxes took 1.2869508266448975s
Interpretability | RDF structures check for List of Czech data boxes took 0.13661813735961914s
Versatility | Serialization formats check for List of Czech data boxes took 0.11447286605834961s
Availability | RDF dump link check for List of Czech data boxes took 15.477562665939331s
License | MR license check for List of Czech data boxes took 0.565932035446167s
License | HR license check for List of Czech data boxes took 52.389052391052246s
Amount of data | Number of property check for List of Czech data boxes took 0.11313462257385254s
Understandability | Number of label check for List of Czech data boxes took 1.7737162113189697s
Understandability | URI regex check for List of Czech data boxes took 0.44695162773132324s
Understandability | Vocabs check for List of Czech data boxes took 0.1262516975402832s
Verifiability | Authors check for List of Czech data boxes took 5.423255443572998s
Verifiability | Publishers check for List of Czech data boxes took 0.826678991317749s
Performance | Throughput check for List of Czech data boxes took 10.721446990966797s
Amount of data | Check the number of entities for List of Czech data boxes took 3.016254425048828s
Verifiability | Contribs. check for List of Czech data boxes took 0.15225648880004883s
Interlinking | sameAs chians check for List of Czech data boxes took 0.26239705085754395s
Interlinking | skos check for List of Czech data boxes took 0.20392799377441406s
Interlinking | skos check for List of Czech data boxes took 0.11797714233398438s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.23450160026550293s
Currency | Creation date check for List of Czech data boxes took 0.20144319534301758s
Currency | Modification date check for List of Czech data boxes took 0.1374678611755371s
Rep.Conc. | URIs length for List of Czech data boxes took 106.70037055015564s
Interoperability | New vocabularies check for List of Czech data boxes took 15.453243970870972s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.34194326400756836s
Accuracy | Check Functional Property for List of Czech data boxes took 0.2731051445007324s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.2536954879760742s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 31.525134563446045s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.123044967651367s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.7018344402313232s
Consistency | Disjoint class check for List of Czech data boxes took 0.12410640716552734s
Consistency | Check Misplaced properties for List of Czech data boxes took 63.901774883270264s
Consistency | Misplaced classes for List of Czech data boxes took 7.661556720733643s
Consistency | Check Ontology hijacking for List of Czech data boxes took 31.548417568206787s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.5026304721832275s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 58.48942279815674s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.65376353263855s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.44725537300109863s
Security | Sign check for List of Czech data boxes took 0.1647331714630127s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 380.69898772239685s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.77996826171875s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.01862955093383789s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 2.6702880859375e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0005342960357666016s
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 13.198786973953247s
Believability | Calculation of trust value for List of Czech data boxes took 9.775161743164062e-06s
INFO | --- Analysis for List of Czech data boxes took 2043.261516571045s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.16286182403564453s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12293338775634766s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 142.5141384601593s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5872764587402344s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.226836919784546s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.213834047317505s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.16124296188354s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.3378965854644775s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1364147663116455s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12661314010620117s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 15.06981635093689s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5531222820281982s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 52.4898567199707s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13351702690124512s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.107558012008667s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.49077343940734863s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12533116340637207s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.355286121368408s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.7932825088500977s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.753889322280884s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.2936034202575684s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1464378833770752s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.24933123588562012s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.20446228981018066s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1219947338104248s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.27564334869384766s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.18638992309570312s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.14266633987426758s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 106.57837390899658s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 13.544236183166504s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3415412902832031s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.18507981300354004s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.21555089950561523s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 31.411694288253784s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.1620290279388428s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.6666431427001953s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10651278495788574s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 64.81882929801941s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.672038793563843s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 32.27386713027954s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.4399054050445557s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 59.611650705337524s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.745903253555298s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4487612247467041s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1575319766998291s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 381.5116002559662s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.1371831893920898s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.019482135772705078s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0005347728729248047s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.2636184692382812e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 13.324594497680664s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.0013580322265625e-05s
INFO | --- Analysis for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2030.9043488502502s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.38199496269226074s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0016493797302246094s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 389.63934206962585s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.824427604675293s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.6673481464385986s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.1849608421325684s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 300.15885376930237s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.747833728790283s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5416271686553955s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3231191635131836s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2738635540008545s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5140776634216309s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5941855907440186s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1676921844482422s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.2790555953979492s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.38215065002441406s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.20043301582336426s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5092229843139648s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.39511847496032715s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.2 took 10.587604284286499s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.00011086463928222656s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1939237117767334s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15119576454162598s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.36557435989379883s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1615617275238037s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.23647785186767578s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.45565128326416016s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2363734245300293s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.2 took 88.21456241607666s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.2 took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.14755463600158691s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.39507007598876953s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.39048218727111816s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.2 took 72.82984375953674s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.6253716945648193s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.704744577407837s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2262859344482422s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 7.24724555015564s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.032838582992554s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.2 took 77.90536642074585s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.8140130043029785s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.43844199180603s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.231044292449951s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.23486876487731934s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.3091585636138916s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.2 took 1241.584311246872s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.5719611644744873s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.021205425262451172s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 7.605552673339844e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.811981201171875e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.1457672119140625e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.2874603271484375e-05s
INFO | --- Analysis for Czech National Open Data Catalog in DCAT-AP v1.2 took 14214.051887512207s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.13309025764465332s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.08877825736999512s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.29761433601379395s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.018152713775634766s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0005347728729248047s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.790855407714844e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 8.58306884765625e-06s
INFO | --- Analysis for Registry of contracts of the Czech Republic - Orders took 2.3474674224853516s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.18987131118774414s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.13035011291503906s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 141.847412109375s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.6250152587890625s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 9.330666065216064s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 10.182838678359985s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.15029287338257s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 1.2873589992523193s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.13173580169677734s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.14960575103759766s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 14.811403751373291s
License | MR license check for Institutions of public power of the Czech Republic took 0.40865564346313477s
License | HR license check for Institutions of public power of the Czech Republic took 52.636391162872314s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.12892723083496094s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 1.436800241470337s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.4511594772338867s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.12305641174316406s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 6.068108558654785s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.8002703189849854s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.770108699798584s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.17903995513916s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.12718892097473145s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.2874414920806885s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.23345446586608887s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.12412428855895996s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.26726865768432617s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.1882307529449463s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.12131881713867188s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 107.76653742790222s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 13.059136152267456s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.3772280216217041s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.23594069480895996s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.23212981224060059s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 29.95584726333618s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.0832927227020264s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.65998911857605s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.12068676948547363s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 64.43832015991211s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 7.6719300746917725s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 31.32810616493225s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.39216947555542s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 58.62475395202637s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.623716115951538s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.43874192237854004s
Security | Sign check for Institutions of public power of the Czech Republic took 0.14745187759399414s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 375.81810307502747s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.785428524017334s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.018896818161010742s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0005180835723876953s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 5.7697296142578125e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 11.915633916854858s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 1.049041748046875e-05s
INFO | --- Analysis for Institutions of public power of the Czech Republic took 2021.6653077602386s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.13774657249450684s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.07170963287353516s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.3032388687133789s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.020866870880126953s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0006439685821533203s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.790855407714844e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 9.775161743164062e-06s
INFO | --- Analysis for Agendas of institutions of public power of the Czech Republic took 2.486285448074341s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10907483100891113s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.002383708953857422s
Extra | Recovery of all triples for Registry of territorial identification, addresses and real estate of the Czech Republic took 41.65604901313782s
Performance | Total latancy measurement for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.6178205013275146s
Amount of data | Number of triples check for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.798393964767456s
Interoperability | New terms check for Registry of territorial identification, addresses and real estate of the Czech Republic took 17.749870538711548s
Versatility | Languages check for Registry of territorial identification, addresses and real estate of the Czech Republic took 300.17634773254395s
Interpretability | Number of blank nodes check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.22721171379089355s
Interpretability | RDF structures check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2863962650299072s
Versatility | Serialization formats check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11860203742980957s
Availability | RDF dump link check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.8743324279785156s
License | MR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12056994438171387s
License | HR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12655258178710938s
Amount of data | Number of property check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10717177391052246s
Understandability | Number of label check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.6674888134002686s
Understandability | URI regex check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.23170042037963867s
Understandability | Vocabs check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13921904563903809s
Verifiability | Authors check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.16183972358703613s
Verifiability | Publishers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.16910052299499512s
Performance | Throughput check for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.335247993469238s
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.11218142509460449s
Interlinking | sameAs chians check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11993956565856934s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.14269137382507324s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12297201156616211s
Timeliness | dataset update frequency check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12446832656860352s
Currency | Creation date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1253526210784912s
Currency | Modification date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12339949607849121s
Rep.Conc. | URIs length for Registry of territorial identification, addresses and real estate of the Czech Republic took 119.99850010871887s
Interoperability | New vocabularies check for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.10122990608215332s
Accuracy | Check Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1218864917755127s
Accuracy | Check Inverse Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1324772834777832s
Accuracy | Check Empty annotation labels for Registry of territorial identification, addresses and real estate of the Czech Republic took 11.117799520492554s
Accuracy | Check White space in annotation for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.2360270023345947s
Accuracy | Check Datatype consistency for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.748241662979126s
Consistency | Disjoint class check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1166231632232666s
Consistency | Check Misplaced properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 86.19170331954956s
Consistency | Misplaced classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.851255893707275s
Consistency | Check Ontology hijacking for Registry of territorial identification, addresses and real estate of the Czech Republic took 13.778939962387085s
Consistency | Check Invalid usage of undefined classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.4036939144134521s
Consistency | Check Invalid usage of undefined properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 87.30346584320068s
Conciseness | Check Extensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 3.025160074234009s
Conciseness | Check Intensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2700083255767822s
Security | Sign check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12866592407226562s
Availability | Check URIs Dereferenciability for Registry of territorial identification, addresses and real estate of the Czech Republic took 1317.6662302017212s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.104447364807129s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.019016027450561523s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0005617141723632812s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.128715515136719e-05s
Interoperability | Check the re-using of existing vocabs for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.6689300537109375e-06s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.239776611328125e-05s
INFO | --- Analysis for Registry of territorial identification, addresses and real estate of the Czech Republic took 2121.5501804351807s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.751326322555542s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.8552331924438477s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.3185422420501709s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.01893901824951172s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0005362033843994141s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.62939453125e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 8.106231689453125e-06s
INFO | --- Analysis for Audited subjects of Supreme Audit Office of the Czech Republic took 4.211656332015991s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.48453807830810547s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.8365886211395264s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.29862403869628906s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.02013683319091797s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0005323886871337891s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 4.029273986816406e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 9.059906005859375e-06s
INFO | --- Analysis for Inspections of the Supreme Audit Office of the Czech Republic took 4.10267448425293s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.4456040859222412s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.83793044090271s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.31313371658325195s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.018639087677001953s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0005280971527099609s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.123283386230469e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 8.106231689453125e-06s
INFO | --- Analysis for List of laws used in inspection reports of SAO took 4.63604998588562s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.11085915565490723s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0809626579284668s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.3437786102294922s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.019255638122558594s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0005450248718261719s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.5762786865234375e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 1.1682510375976562e-05s
INFO | --- Analysis for Active ingredients of medicinal products available in Czech Republic took 3.683236598968506s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.1059868335723877s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.07076883316040039s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.31448960304260254s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.018173933029174805s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0005195140838623047s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.647804260253906e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 8.106231689453125e-06s
INFO | --- Analysis for List of prices of reimbursed medicinal products marketed in Czech republic took 2.0342812538146973s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.12012600898742676s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.07101035118103027s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.5282690525054932s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.018158674240112305s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0005166530609130859s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.6716461181640625e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 1.3113021850585938e-05s
INFO | --- Analysis for Medicinal products marketed in Czech Republic took 3.816223382949829s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.20014548301696777s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0023365020751953125s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 142.04106950759888s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.5645267963409424s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 8.952877521514893s
Interoperability | New terms check for Summary types of Czech institutions of public power took 10.187023162841797s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.1775507926941s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 1.580467700958252s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.15909385681152344s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.12682485580444336s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 14.490341901779175s
License | MR license check for Summary types of Czech institutions of public power took 0.5933032035827637s
License | HR license check for Summary types of Czech institutions of public power took 53.52957344055176s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.12214827537536621s
Understandability | Number of label check for Summary types of Czech institutions of public power took 1.6489193439483643s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.8161306381225586s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.1090857982635498s
Verifiability | Authors check for Summary types of Czech institutions of public power took 5.3122100830078125s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.7897963523864746s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.834062576293945s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.1401138305664062s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.13443708419799805s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.2698545455932617s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.21220803260803223s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.13752508163452148s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.2423701286315918s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.18489718437194824s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.1166226863861084s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 107.164381980896s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 14.084608793258667s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.38805055618286133s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.1613461971282959s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.1772019863128662s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 31.20263910293579s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.1108036041259766s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.6783297061920166s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.12331247329711914s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 64.5259485244751s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 7.80121374130249s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 33.608656883239746s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.448716640472412s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 58.67590117454529s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.664536952972412s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.43191099166870117s
Security | Sign check for Summary types of Czech institutions of public power took 0.15431904792785645s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 385.1755361557007s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 1.2593512535095215s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.022228002548217773s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0005319118499755859s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 4.601478576660156e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 14.107261896133423s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 1.2636184692382812e-05s
INFO | --- Analysis for Summary types of Czech institutions of public power took 2040.2383279800415s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.11544132232666016s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.06980466842651367s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.2932884693145752s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.01894092559814453s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0006093978881835938s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 4.3392181396484375e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 9.5367431640625e-06s
INFO | --- Analysis for Evaluation of VaVaI results for 2013 took 5.913128137588501s
Availability | SPARQL endpoint availability check for State funding providers took 0.1202237606048584s
Availability | VoID file availability check for State funding providers took 0.08078789710998535s
Completeness | Calculation of interlinking completeness for State funding providers took 0.3133678436279297s
Reputation | Calculation of the PageRank for State funding providers took 0.018439531326293945s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0005235671997070312s
Interlinking | Calculation of Clustering coefficient for State funding providers took 4.124641418457031e-05s
Believability | Calculation of trust value for State funding providers took 8.58306884765625e-06s
INFO | --- Analysis for State funding providers took 5.430067777633667s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.11605119705200195s
Availability | VoID file availability check for Organizations active in R&D took 0.07679247856140137s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 1.6961843967437744s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.01831197738647461s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0005333423614501953s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 3.910064697265625e-05s
Believability | Calculation of trust value for Organizations active in R&D took 1.2159347534179688e-05s
INFO | --- Analysis for Organizations active in R&D took 9.012874841690063s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.09923481941223145s
Availability | VoID file availability check for R&D Programmes took 0.08102107048034668s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.9315745830535889s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020996570587158203s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0009372234344482422s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 5.269050598144531e-05s
Believability | Calculation of trust value for R&D Programmes took 9.059906005859375e-06s
INFO | --- Analysis for R&D Programmes took 5.20615029335022s
Availability | SPARQL endpoint availability check for R&D Projects took 0.09827089309692383s
Availability | VoID file availability check for R&D Projects took 0.06666326522827148s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.4487881660461426s
Reputation | Calculation of the PageRank for R&D Projects took 0.018177509307861328s
Interlinking | Calculation of Degree of Connection for R&D Projects took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for R&D Projects took 0.0005223751068115234s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 3.933906555175781e-05s
Believability | Calculation of trust value for R&D Projects took 8.821487426757812e-06s
INFO | --- Analysis for R&D Projects took 3.6102724075317383s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.10906004905700684s
Availability | VoID file availability check for Institutional research plans took 0.075927734375s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.418018102645874s
Reputation | Calculation of the PageRank for Institutional research plans took 0.01954054832458496s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Institutional research plans took 0.00052642822265625s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.076957702636719e-05s
Believability | Calculation of trust value for Institutional research plans took 8.344650268554688e-06s
INFO | --- Analysis for Institutional research plans took 5.119922876358032s
Availability | SPARQL endpoint availability check for Results of R&D took 0.1029508113861084s
Availability | VoID file availability check for Results of R&D took 0.07583928108215332s
Completeness | Calculation of interlinking completeness for Results of R&D took 2.40132737159729s
Reputation | Calculation of the PageRank for Results of R&D took 0.018266677856445312s
Interlinking | Calculation of Degree of Connection for Results of R&D took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Results of R&D took 0.0005259513854980469s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.0531158447265625e-05s
Believability | Calculation of trust value for Results of R&D took 9.059906005859375e-06s
INFO | --- Analysis for Results of R&D took 9.103764057159424s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.10525298118591309s
Availability | VoID file availability check for Tenders in R&D took 0.07134032249450684s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.2989006042480469s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.018948078155517578s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.000537872314453125s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.673004150390625e-05s
Believability | Calculation of trust value for Tenders in R&D took 9.5367431640625e-06s
INFO | --- Analysis for Tenders in R&D took 2.824639320373535s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 9.250640869140625e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.45137715339660645s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.29428982734680176s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.018192291259765625s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.3855438232421875e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 1.049041748046875e-05s
INFO | --- Analysis for Czech addresses – Adresy v České republice took 3.211014986038208s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.41210222244262695s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.9689278602600098s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 235.7655770778656s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.2728009223937988s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 9.987880945205688s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.135174989700317s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.36283540725708s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.3282439708709717s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.18359756469726562s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.442258358001709s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.2955045700073242s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.2628936767578125s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.28899621963500977s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 66.14878439903259s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.29050564765930176s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 1.2179021835327148s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.5572719573974609s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.27362537384033203s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 56.450531005859375s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 72.01110482215881s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.697057962417603s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 8.797645568847656e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 71.6768970489502s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.6042723655700684s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.6696710586547852s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 2.1620399951934814s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.26951050758361816s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 2.557004690170288s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 2.3790197372436523s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 0.365140438079834s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.18911981582641602s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.18384885787963867s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 0.18048834800720215s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 21.02927565574646s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.0001952648162841797s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.26869750022888184s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.2712569236755371s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.5130336284637451s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.02568840980529785s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0005223751068115234s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.0001392364501953125s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 1.6689300537109375e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 1.2874603271484375e-05s
INFO | --- Analysis for data.bnf.fr - Bibliothèque nationale de France took 936.6623556613922s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.3794291019439697s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.3527069091796875s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.31691741943359375s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.017976045608520508s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0005242824554443359s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 6.651878356933594e-05s
Interoperability | Check the re-using of existing vocabs for Open Data from the Italian National Research Council took 2.309180498123169s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 8.821487426757812e-06s
INFO | --- Analysis for Open Data from the Italian National Research Council took 6.5266478061676025s
Availability | SPARQL endpoint availability check for Data.gov took 1.698451280593872s
Availability | VoID file availability check for Data.gov took 1.2420933246612549s
Completeness | Calculation of interlinking completeness for Data.gov took 0.3167557716369629s
Reputation | Calculation of the PageRank for Data.gov took 0.01832723617553711s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0005059242248535156s
Interlinking | Calculation of Clustering coefficient for Data.gov took 1.3828277587890625e-05s
Believability | Calculation of trust value for Data.gov took 8.344650268554688e-06s
INFO | --- Analysis for Data.gov took 19.073105573654175s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.07775545120239258s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.014456033706665039s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.35883617401123047s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.018863439559936523s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0005240440368652344s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 7.128715515136719e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 9.298324584960938e-06s
INFO | --- Analysis for DataGovIE - Irish Government Data took 1.9159588813781738s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 8.463859558105469e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 1.3843729496002197s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.4300103187561035s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.018099546432495117s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0005278587341308594s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.200241088867188e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 8.58306884765625e-06s
INFO | --- Analysis for data.gov.uk Time Intervals took 3.5902533531188965s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 21.484715938568115s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.9058363437652588s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.613530158996582s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.018152475357055664s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 9.369850158691406e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 7.62939453125e-06s
INFO | --- Analysis for data-hnm-hu - Hungarian National Museum Datasets took 140.75873804092407s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.10113310813903809s
Availability | VoID file availability check for Climb Dataincubator took 0.01346898078918457s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.32547879219055176s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.018080949783325195s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0005156993865966797s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 6.985664367675781e-05s
Believability | Calculation of trust value for Climb Dataincubator took 1.1444091796875e-05s
INFO | --- Analysis for Climb Dataincubator took 1.9037165641784668s
Availability | SPARQL endpoint availability check for Discogs in RDF took 9.036064147949219e-05s
Availability | VoID file availability check for Discogs in RDF took 0.6301748752593994s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.2795109748840332s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.018063068389892578s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0005199909210205078s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 8.654594421386719e-05s
Believability | Calculation of trust value for Discogs in RDF took 1.1920928955078125e-05s
INFO | --- Analysis for Discogs in RDF took 3.2086832523345947s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.0622408390045166s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.016750335693359375s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.46294116973876953s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.018573760986328125s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0005316734313964844s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.340576171875e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 4.124641418457031e-05s
INFO | --- Analysis for Metoffice Weather Forecasts took 5.176474094390869s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.06340956687927246s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.015827417373657227s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.3126091957092285s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.01934027671813965s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0005247592926025391s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 9.202957153320312e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 1.2159347534179688e-05s
INFO | --- Analysis for Moseley Folk Festival Data took 3.1933319568634033s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.06974554061889648s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.015831708908081055s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.3109865188598633s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.01828145980834961s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0005259513854980469s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 8.511543273925781e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 1.1205673217773438e-05s
INFO | --- Analysis for Data Incubator: MusicBrainz took 1.8741436004638672s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.084986925125122s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.5139622688293457s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.29811549186706543s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.01851630210876465s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0005381107330322266s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.440017700195312e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 8.344650268554688e-06s
INFO | --- Analysis for NASA Space Flight & Astronaut data in RDF took 5.306931972503662s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.055669546127319336s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.01575636863708496s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.32449841499328613s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.018190860748291016s
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.0005342960357666016s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.43865966796875e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 1.1205673217773438e-05s
INFO | --- Analysis for Airport data from Our Airports published as RDF took 2.084360361099243s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.06190133094787598s
Availability | VoID file availability check for Pokedex data in RDF took 0.01643538475036621s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.31198549270629883s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.01976943016052246s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0005202293395996094s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 8.940696716308594e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 1.2159347534179688e-05s
INFO | --- Analysis for Pokedex data in RDF took 2.8078131675720215s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.05692243576049805s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.015528202056884766s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.330643892288208s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.018416404724121094s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0005242824554443359s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 9.179115295410156e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 1.0251998901367188e-05s
INFO | --- Analysis for Scottish Mountaineering Council Journals Issues 1-36 took 1.9725372791290283s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.2859156131744385s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.5432701110839844s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 44.499234199523926s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 0.5997488498687744s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 20.46500039100647s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.5990169048309326s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.17476797103882s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.149360418319702s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.21447157859802246s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.2025129795074463s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.21185946464538574s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.15773940086364746s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.25744175910949707s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.158966064453125s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.9013636112213135s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 30.16135811805725s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 0.47856998443603516s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.18286943435668945s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 8.548096179962158s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.7258896827697754s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 11.3533194065094s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 9.5367431640625e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 1.2640068531036377s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.6842615604400635s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.2964017391204834s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.22605180740356445s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.3391118049621582s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 2.457041025161743s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 3.313943386077881s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 29.804248332977295s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 80.95964455604553s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.24204111099243164s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.22286128997802734s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.14419174194335938s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 26.960608959197998s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 3.0217063426971436s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.04343318939209s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.467242956161499s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 0.6805644035339355s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 8.0785973072052s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 17.120857000350952s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.5255217552185059s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.7215371131896973s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 2.849856376647949s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.34589219093322754s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.1501023769378662s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 0.11272335052490234s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.49228525161743164s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.018683910369873047s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0005218982696533203s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 7.605552673339844e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 74.12794137001038s
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 694.8222241401672s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.8204987049102783s
Availability | VoID file availability check for Persée in RDF took 1.6036789417266846s
Extra | Recovery of all triples for Persée in RDF took 1.045475959777832s
Performance | Total latancy measurement for Persée in RDF took 0.6283748149871826s
Amount of data | Number of triples check for Persée in RDF took 2.785320997238159s
Interoperability | New terms check for Persée in RDF took 1.839090347290039s
Versatility | Languages check for Persée in RDF took 120.27195382118225s
Interpretability | Number of blank nodes check for Persée in RDF took 0.378065824508667s
Interpretability | RDF structures check for Persée in RDF took 0.6537940502166748s
Versatility | Serialization formats check for Persée in RDF took 0.781243085861206s
Availability | RDF dump link check for Persée in RDF took 0.20494508743286133s
License | MR license check for Persée in RDF took 1.4371800422668457s
License | HR license check for Persée in RDF took 25.469427824020386s
Amount of data | Number of property check for Persée in RDF took 0.14466476440429688s
Understandability | Number of label check for Persée in RDF took 1.6067206859588623s
Understandability | URI regex check for Persée in RDF took 0.7807779312133789s
Understandability | Vocabs check for Persée in RDF took 0.4519643783569336s
Verifiability | Authors check for Persée in RDF took 0.7538261413574219s
Verifiability | Publishers check for Persée in RDF took 0.49850034713745117s
Performance | Throughput check for Persée in RDF took 10.653083562850952s
Amount of data | Check the number of entities for Persée in RDF took 4.458427429199219e-05s
Verifiability | Contribs. check for Persée in RDF took 0.39436817169189453s
Interlinking | sameAs chians check for Persée in RDF took 0.18792986869812012s
Interlinking | skos check for Persée in RDF took 1.0909349918365479s
Interlinking | skos check for Persée in RDF took 0.11429762840270996s
Timeliness | dataset update frequency check for Persée in RDF took 0.8338663578033447s
Currency | Creation date check for Persée in RDF took 0.4977293014526367s
Currency | Modification date check for Persée in RDF took 0.5217268466949463s
Rep.Conc. | URIs length for Persée in RDF took 2.7996816635131836s
Interoperability | New vocabularies check for Persée in RDF took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.11990690231323242s
Accuracy | Check Functional Property for Persée in RDF took 0.16726040840148926s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.16615796089172363s
Accuracy | Check Empty annotation labels for Persée in RDF took 0.7582221031188965s
Accuracy | Check White space in annotation for Persée in RDF took 0.037970542907714844s
Accuracy | Check Datatype consistency for Persée in RDF took 0.03018641471862793s
Consistency | Disjoint class check for Persée in RDF took 0.5184323787689209s
Consistency | Check Misplaced properties for Persée in RDF took 2.1041908264160156s
Consistency | Misplaced classes for Persée in RDF took 0.20957541465759277s
Consistency | Check Ontology hijacking for Persée in RDF took 1.9385714530944824s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.4990968704223633s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.3980300426483154s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.03332328796386719s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.12442779541015625s
Security | Sign check for Persée in RDF took 0.544602632522583s
Availability | Check URIs Dereferenciability for Persée in RDF took 1417.870220899582s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.5357880592346191s
Reputation | Calculation of the PageRank for Persée in RDF took 0.021281003952026367s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 5.793571472167969e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0005285739898681641s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.000125885009765625s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 9.5367431640625e-07s
Believability | Calculation of trust value for Persée in RDF took 1.430511474609375e-05s
INFO | --- Analysis for Persée in RDF took 1693.976597070694s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 1.3985600471496582s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 7.3909759521484375e-06s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.29718804359436035s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.018154621124267578s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.00054168701171875s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 1.33514404296875e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 1.239776611328125e-05s
INFO | --- Analysis for data.southampton.ac.uk with SPARQL endpoint took 3.3387861251831055s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.2539644241333008s
Availability | VoID file availability check for data-szepmuveszeti-hu took 1.0022499561309814s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.3021223545074463s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.01827383041381836s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0005340576171875s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011301040649414062s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 1.0967254638671875e-05s
INFO | --- Analysis for data-szepmuveszeti-hu took 12.891045808792114s
Availability | SPARQL endpoint availability check for Open Data Web took 13.551925897598267s
Availability | VoID file availability check for Open Data Web took 3.8249452114105225s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.3106215000152588s
Reputation | Calculation of the PageRank for Open Data Web took 0.01873016357421875s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0005271434783935547s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 1.049041748046875e-05s
Believability | Calculation of trust value for Open Data Web took 1.1444091796875e-05s
INFO | --- Analysis for Open Data Web took 19.371971130371094s
Availability | SPARQL endpoint availability check for DataFAQs took 8.249282836914062e-05s
Availability | VoID file availability check for DataFAQs took 2.86102294921875e-06s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.5867063999176025s
Reputation | Calculation of the PageRank for DataFAQs took 0.017900943756103516s
Interlinking | Calculation of Degree of Connection for DataFAQs took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DataFAQs took 0.0005350112915039062s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 1.1444091796875e-05s
Believability | Calculation of trust value for DataFAQs took 1.1682510375976562e-05s
INFO | --- Analysis for DataFAQs took 4.142613887786865s
Availability | SPARQL endpoint availability check for datahub took 9.942054748535156e-05s
Availability | VoID file availability check for datahub took 0.9280486106872559s
Completeness | Calculation of interlinking completeness for datahub took 0.3152146339416504s
Reputation | Calculation of the PageRank for datahub took 0.0192718505859375s
Interlinking | Calculation of Degree of Connection for datahub took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for datahub took 0.0005323886871337891s
Interlinking | Calculation of Clustering coefficient for datahub took 4.482269287109375e-05s
Believability | Calculation of trust value for datahub took 1.239776611328125e-05s
INFO | --- Analysis for datahub took 4.787345886230469s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.2944214344024658s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0728836059570312e-05s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.29854273796081543s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.01895284652709961s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0005366802215576172s
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.2159347534179688e-05s
INFO | --- Analysis for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 4.244325637817383s
Availability | SPARQL endpoint availability check for datos-artium-org took 1.6123862266540527s
Availability | VoID file availability check for datos-artium-org took 0.9133315086364746s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.3617739677429199s
Reputation | Calculation of the PageRank for datos-artium-org took 0.020847082138061523s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0005242824554443359s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00010919570922851562s
Believability | Calculation of trust value for datos-artium-org took 1.1444091796875e-05s
INFO | --- Analysis for datos-artium-org took 8.078770160675049s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 2.1827611923217773s
Availability | VoID file availability check for Datos.bcn.cl took 11.14711880683899s
Extra | Recovery of all triples for Datos.bcn.cl took 898.3957033157349s
Performance | Total latancy measurement for Datos.bcn.cl took 6.654400825500488s
Amount of data | Number of triples check for Datos.bcn.cl took 4.519167423248291s
Interoperability | New terms check for Datos.bcn.cl took 5.364206552505493s
Versatility | Languages check for Datos.bcn.cl took 301.081214427948s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.930931568145752s
Security | Check HTTPS for Datos.bcn.cl took 0.7086553573608398s
Interpretability | RDF structures check for Datos.bcn.cl took 1.458939790725708s
Versatility | Serialization formats check for Datos.bcn.cl took 1.328322410583496s
Availability | RDF dump link check for Datos.bcn.cl took 1.3237919807434082s
License | MR license check for Datos.bcn.cl took 1.3962056636810303s
License | HR license check for Datos.bcn.cl took 77.75686526298523s
Amount of data | Number of property check for Datos.bcn.cl took 1.4078922271728516s
Understandability | Number of label check for Datos.bcn.cl took 1.6613929271697998s
Understandability | URI regex check for Datos.bcn.cl took 3.3808016777038574s
Understandability | Vocabs check for Datos.bcn.cl took 1.2913789749145508s
Verifiability | Authors check for Datos.bcn.cl took 1.2090628147125244s
Verifiability | Publishers check for Datos.bcn.cl took 1.3530950546264648s
Performance | Throughput check for Datos.bcn.cl took 13.692452430725098s
Amount of data | Check the number of entities for Datos.bcn.cl took 9.870529174804688e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.2371490001678467s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.3013739585876465s
Interlinking | skos check for Datos.bcn.cl took 1.2836461067199707s
Interlinking | skos check for Datos.bcn.cl took 1.7606480121612549s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.624208927154541s
Currency | Creation date check for Datos.bcn.cl took 1.4092702865600586s
Currency | Modification date check for Datos.bcn.cl took 1.2799739837646484s
Rep.Conc. | URIs length for Datos.bcn.cl took 604.4893078804016s
Interoperability | New vocabularies check for Datos.bcn.cl took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.2717533111572266s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.2831566333770752s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.3285601139068604s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 665.0978493690491s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.3279116153717041s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.28129148483276367s
Consistency | Disjoint class check for Datos.bcn.cl took 1.7539916038513184s
Consistency | Check Misplaced properties for Datos.bcn.cl took 8.644688844680786s
Consistency | Misplaced classes for Datos.bcn.cl took 2.080986738204956s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 422.5078184604645s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.3636999130249023s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 7.958315134048462s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.2921435832977295s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.7100470066070557s
Security | Sign check for Datos.bcn.cl took 1.288534164428711s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 8677.819648504257s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 0.8232333660125732s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.020527124404907227s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0005362033843994141s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 0.00010013580322265625s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 4.76837158203125e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 5.0067901611328125e-06s
INFO | --- Analysis for Datos.bcn.cl took 12085.495483160019s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.47349095344543457s
Availability | VoID file availability check for datos.bne.es took 2.9625940322875977s
Extra | Recovery of all triples for datos.bne.es took 144.2820873260498s
Performance | Total latancy measurement for datos.bne.es took 1.4570667743682861s
Amount of data | Number of triples check for datos.bne.es took 1.1871123313903809s
Interoperability | New terms check for datos.bne.es took 2.370944023132324s
Versatility | Languages check for datos.bne.es took 61.05418610572815s
Interpretability | Number of blank nodes check for datos.bne.es took 0.3217804431915283s
Security | Check HTTPS for datos.bne.es took 0.1708977222442627s
Interpretability | RDF structures check for datos.bne.es took 0.42543506622314453s
Versatility | Serialization formats check for datos.bne.es took 0.3524038791656494s
Availability | RDF dump link check for datos.bne.es took 0.33374714851379395s
License | MR license check for datos.bne.es took 0.8857271671295166s
License | HR license check for datos.bne.es took 60.71449041366577s
Amount of data | Number of property check for datos.bne.es took 0.4338810443878174s
Understandability | Number of label check for datos.bne.es took 1.9160747528076172s
Understandability | URI regex check for datos.bne.es took 0.6813359260559082s
Understandability | Vocabs check for datos.bne.es took 0.331756591796875s
Verifiability | Authors check for datos.bne.es took 0.6645925045013428s
Verifiability | Publishers check for datos.bne.es took 0.3465306758880615s
Performance | Throughput check for datos.bne.es took 11.24662446975708s
Amount of data | Check the number of entities for datos.bne.es took 0.0001423358917236328s
Verifiability | Contribs. check for datos.bne.es took 0.320314884185791s
Interlinking | sameAs chians check for datos.bne.es took 0.32089853286743164s
Interlinking | skos check for datos.bne.es took 0.8806459903717041s
Interlinking | skos check for datos.bne.es took 0.2523949146270752s
Timeliness | dataset update frequency check for datos.bne.es took 0.3609490394592285s
Currency | Creation date check for datos.bne.es took 0.3112294673919678s
Currency | Modification date check for datos.bne.es took 0.3281211853027344s
Rep.Conc. | URIs length for datos.bne.es took 67.9919023513794s
Interoperability | New vocabularies check for datos.bne.es took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for datos.bne.es took 0.2906515598297119s
Accuracy | Check Functional Property for datos.bne.es took 0.3360886573791504s
Accuracy | Check Inverse Functional Property for datos.bne.es took 0.3416428565979004s
Accuracy | Check Empty annotation labels for datos.bne.es took 49.39450168609619s
Accuracy | Check White space in annotation for datos.bne.es took 1.645491123199463s
Accuracy | Check Datatype consistency for datos.bne.es took 1.33076810836792s
Consistency | Disjoint class check for datos.bne.es took 0.3385348320007324s
Consistency | Check Misplaced properties for datos.bne.es took 8.997328281402588s
Consistency | Misplaced classes for datos.bne.es took 4.412205457687378s
Consistency | Check Ontology hijacking for datos.bne.es took 46.26232409477234s
Consistency | Check Invalid usage of undefined classes for datos.bne.es took 1.2775568962097168s
Consistency | Check Invalid usage of undefined properties for datos.bne.es took 10.151977300643921s
Conciseness | Check Extensional conciseness for datos.bne.es took 1.4061713218688965s
Conciseness | Check Intensional conciseness for datos.bne.es took 0.296414852142334s
Security | Sign check for datos.bne.es took 1.080904483795166s
Availability | Check URIs Dereferenciability for datos.bne.es took 3.201645851135254s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.32979393005371094s
Reputation | Calculation of the PageRank for datos.bne.es took 0.01882457733154297s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.000514984130859375s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00012159347534179688s
Interoperability | Check the re-using of existing vocabs for datos.bne.es took 1.9073486328125e-06s
Believability | Calculation of trust value for datos.bne.es took 1.1205673217773438e-05s
INFO | --- Analysis for datos.bne.es took 593.2058916091919s
Availability | SPARQL endpoint availability check for dbacademic took 0.0582125186920166s
Availability | VoID file availability check for dbacademic took 0.015584230422973633s
Completeness | Calculation of interlinking completeness for dbacademic took 0.32658886909484863s
Reputation | Calculation of the PageRank for dbacademic took 0.018332242965698242s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0005140304565429688s
Interlinking | Calculation of Clustering coefficient for dbacademic took 1.2874603271484375e-05s
Believability | Calculation of trust value for dbacademic took 1.1205673217773438e-05s
INFO | --- Analysis for dbacademic took 2.0019357204437256s
Availability | SPARQL endpoint availability check for DBkWik took 0.21614789962768555s
Availability | VoID file availability check for DBkWik took 0.2056741714477539s
Extra | Recovery of all triples for DBkWik took 1.3242278099060059s
Performance | Total latancy measurement for DBkWik took 0.603705644607544s
Amount of data | Number of triples check for DBkWik took 3.6996302604675293s
Interoperability | New terms check for DBkWik took 2.0353591442108154s
Versatility | Languages check for DBkWik took 60.48151969909668s
Interpretability | Number of blank nodes check for DBkWik took 0.132354736328125s
Security | Check HTTPS for DBkWik took 0.34497499465942383s
Interpretability | RDF structures check for DBkWik took 0.13329386711120605s
Versatility | Serialization formats check for DBkWik took 0.20256805419921875s
Availability | RDF dump link check for DBkWik took 2.9227354526519775s
License | MR license check for DBkWik took 0.22395658493041992s
License | HR license check for DBkWik took 61.775108337402344s
Amount of data | Number of property check for DBkWik took 0.1450188159942627s
Understandability | Number of label check for DBkWik took 2.0964624881744385s
Understandability | URI regex check for DBkWik took 0.3059215545654297s
Understandability | Vocabs check for DBkWik took 0.1203160285949707s
Verifiability | Authors check for DBkWik took 0.12607026100158691s
Verifiability | Publishers check for DBkWik took 0.09126949310302734s
Performance | Throughput check for DBkWik took 11.393606185913086s
Amount of data | Check the number of entities for DBkWik took 8.797645568847656e-05s
Verifiability | Contribs. check for DBkWik took 0.13118791580200195s
Interlinking | sameAs chians check for DBkWik took 0.3589346408843994s
Interlinking | skos check for DBkWik took 0.6456451416015625s
Interlinking | skos check for DBkWik took 0.08672475814819336s
Timeliness | dataset update frequency check for DBkWik took 0.2242884635925293s
Currency | Creation date check for DBkWik took 0.36007070541381836s
Currency | Modification date check for DBkWik took 0.11057853698730469s
Rep.Conc. | URIs length for DBkWik took 11.442612171173096s
Interoperability | New vocabularies check for DBkWik took 4.470474720001221s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.12033343315124512s
Accuracy | Check Functional Property for DBkWik took 0.5098283290863037s
Accuracy | Check Inverse Functional Property for DBkWik took 0.2541201114654541s
Accuracy | Check Empty annotation labels for DBkWik took 0.531853437423706s
Accuracy | Check White space in annotation for DBkWik took 0.023926734924316406s
Accuracy | Check Datatype consistency for DBkWik took 0.03669333457946777s
Consistency | Disjoint class check for DBkWik took 0.12244319915771484s
Consistency | Check Misplaced properties for DBkWik took 11.72026515007019s
Consistency | Misplaced classes for DBkWik took 0.6640093326568604s
Consistency | Check Ontology hijacking for DBkWik took 1.726053237915039s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.202890157699585s
Consistency | Check Invalid usage of undefined properties for DBkWik took 11.639749765396118s
Conciseness | Check Extensional conciseness for DBkWik took 0.03255867958068848s
Conciseness | Check Intensional conciseness for DBkWik took 0.7569468021392822s
Security | Sign check for DBkWik took 0.2608511447906494s
Availability | Check URIs Dereferenciability for DBkWik took 3.2369322776794434s
Completeness | Calculation of interlinking completeness for DBkWik took 0.337540864944458s
Reputation | Calculation of the PageRank for DBkWik took 0.05864429473876953s
Interlinking | Calculation of Degree of Connection for DBkWik took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBkWik took 0.0005168914794921875s
Interlinking | Calculation of Clustering coefficient for DBkWik took 6.818771362304688e-05s
Interoperability | Check the re-using of existing vocabs for DBkWik took 2.5196526050567627s
Believability | Calculation of trust value for DBkWik took 1.2636184692382812e-05s
INFO | --- Analysis for DBkWik took 1262.730000257492s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0001399517059326172s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.19215607643127441s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.3095815181732178s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.01909160614013672s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0005106925964355469s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.0001163482666015625s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 1.239776611328125e-05s
INFO | --- Analysis for DBLP Research Groups (University of Deusto-GNOSS) took 4.388019561767578s
Availability | SPARQL endpoint availability check for dbnary took 0.2794811725616455s
Availability | VoID file availability check for dbnary took 1.7661445140838623s
Extra | Recovery of all triples for dbnary took 1.2184667587280273s
Performance | Total latancy measurement for dbnary took 0.4012184143066406s
Amount of data | Number of triples check for dbnary took 1.463660478591919s
Interoperability | New terms check for dbnary took 3.490997791290283s
Versatility | Languages check for dbnary took 61.906253814697266s
Interpretability | Number of blank nodes check for dbnary took 3.510603427886963s
Security | Check HTTPS for dbnary took 0.21378278732299805s
Interpretability | RDF structures check for dbnary took 0.15184807777404785s
Versatility | Serialization formats check for dbnary took 0.10688066482543945s
Availability | RDF dump link check for dbnary took 0.07294321060180664s
License | MR license check for dbnary took 0.11018490791320801s
License | HR license check for dbnary took 55.82861113548279s
Amount of data | Number of property check for dbnary took 0.10930728912353516s
Understandability | Number of label check for dbnary took 0.40592026710510254s
Understandability | URI regex check for dbnary took 0.15299487113952637s
Understandability | Vocabs check for dbnary took 0.17544960975646973s
Verifiability | Authors check for dbnary took 0.10926127433776855s
Verifiability | Publishers check for dbnary took 0.10486912727355957s
Performance | Throughput check for dbnary took 10.38880205154419s
Amount of data | Check the number of entities for dbnary took 0.00010824203491210938s
Verifiability | Contribs. check for dbnary took 0.09560012817382812s
Interlinking | sameAs chians check for dbnary took 0.09760069847106934s
Interlinking | skos check for dbnary took 0.25908470153808594s
Interlinking | skos check for dbnary took 0.09507536888122559s
Timeliness | dataset update frequency check for dbnary took 0.10613274574279785s
Currency | Creation date check for dbnary took 0.11993789672851562s
Currency | Modification date check for dbnary took 0.36170482635498047s
Rep.Conc. | URIs length for dbnary took 10.076138019561768s
Interoperability | New vocabularies check for dbnary took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for dbnary took 0.09521126747131348s
Accuracy | Check Functional Property for dbnary took 0.12728238105773926s
Accuracy | Check Inverse Functional Property for dbnary took 0.09444093704223633s
Accuracy | Check Empty annotation labels for dbnary took 0.45817112922668457s
Accuracy | Check White space in annotation for dbnary took 0.032029151916503906s
Accuracy | Check Datatype consistency for dbnary took 0.028858423233032227s
Consistency | Disjoint class check for dbnary took 0.10698509216308594s
Consistency | Check Misplaced properties for dbnary took 8.004846334457397s
Consistency | Misplaced classes for dbnary took 0.377612829208374s
Consistency | Check Ontology hijacking for dbnary took 1.6176936626434326s
Consistency | Check Invalid usage of undefined classes for dbnary took 1.2193632125854492s
Consistency | Check Invalid usage of undefined properties for dbnary took 8.912589311599731s
Conciseness | Check Extensional conciseness for dbnary took 0.0370175838470459s
Conciseness | Check Intensional conciseness for dbnary took 0.17228198051452637s
Security | Sign check for dbnary took 0.07608699798583984s
Availability | Check URIs Dereferenciability for dbnary took 3.089772939682007s
Completeness | Calculation of interlinking completeness for dbnary took 0.3205702304840088s
Reputation | Calculation of the PageRank for dbnary took 0.018051624298095703s
Interlinking | Calculation of Degree of Connection for dbnary took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0005202293395996094s
Interlinking | Calculation of Clustering coefficient for dbnary took 5.221366882324219e-05s
Interoperability | Check the re-using of existing vocabs for dbnary took 1.430511474609375e-06s
Believability | Calculation of trust value for dbnary took 1.3589859008789062e-05s
INFO | --- Analysis for dbnary took 278.49590826034546s
Availability | SPARQL endpoint availability check for DBpedia took 0.68180251121521s
Availability | VoID file availability check for DBpedia took 1.0478622913360596s
Extra | Recovery of all triples for DBpedia took 4.042043447494507s
Performance | Total latancy measurement for DBpedia took 1.212186574935913s
Amount of data | Number of triples check for DBpedia took 3.578061819076538s
Interoperability | New terms check for DBpedia took 3.9593162536621094s
Versatility | Languages check for DBpedia took 10.773552656173706s
Interpretability | Number of blank nodes check for DBpedia took 0.2524900436401367s
Security | Check HTTPS for DBpedia took 0.17664313316345215s
Interpretability | RDF structures check for DBpedia took 0.6192543506622314s
Versatility | Serialization formats check for DBpedia took 0.280651330947876s
Availability | RDF dump link check for DBpedia took 0.27173280715942383s
License | MR license check for DBpedia took 1.0483129024505615s
License | HR license check for DBpedia took 12.223721981048584s
Amount of data | Number of property check for DBpedia took 0.2949798107147217s
Understandability | Number of label check for DBpedia took 6.592721223831177s
Understandability | URI regex check for DBpedia took 0.5563974380493164s
Understandability | Vocabs check for DBpedia took 0.3779447078704834s
Verifiability | Authors check for DBpedia took 0.6615891456604004s
Verifiability | Publishers check for DBpedia took 0.8161702156066895s
Performance | Throughput check for DBpedia took 10.807780027389526s
Amount of data | Check the number of entities for DBpedia took 0.00010371208190917969s
Verifiability | Contribs. check for DBpedia took 0.25987696647644043s
Interlinking | sameAs chians check for DBpedia took 0.2709054946899414s
Interlinking | skos check for DBpedia took 0.4041590690612793s
Interlinking | skos check for DBpedia took 0.26721787452697754s
Timeliness | dataset update frequency check for DBpedia took 0.24933600425720215s
Currency | Creation date check for DBpedia took 0.3737773895263672s
Currency | Modification date check for DBpedia took 0.2750875949859619s
Rep.Conc. | URIs length for DBpedia took 36.81068277359009s
Interoperability | New vocabularies check for DBpedia took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.2753486633300781s
Accuracy | Check Functional Property for DBpedia took 0.29177236557006836s
Accuracy | Check Inverse Functional Property for DBpedia took 0.31514549255371094s
Accuracy | Check Empty annotation labels for DBpedia took 1.296818494796753s
Accuracy | Check White space in annotation for DBpedia took 0.0442965030670166s
Accuracy | Check Datatype consistency for DBpedia took 0.028144121170043945s
Consistency | Disjoint class check for DBpedia took 0.3971529006958008s
Consistency | Check Misplaced properties for DBpedia took 12.827651262283325s
Consistency | Misplaced classes for DBpedia took 0.8202869892120361s
Consistency | Check Ontology hijacking for DBpedia took 1.9799184799194336s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.2159883975982666s
Consistency | Check Invalid usage of undefined properties for DBpedia took 1.514054775238037s
Conciseness | Check Extensional conciseness for DBpedia took 0.03270268440246582s
Conciseness | Check Intensional conciseness for DBpedia took 2.9420135021209717s
Security | Sign check for DBpedia took 0.30100584030151367s
Availability | Check URIs Dereferenciability for DBpedia took 1982.6905720233917s
Completeness | Calculation of interlinking completeness for DBpedia took 5.711911916732788s
Reputation | Calculation of the PageRank for DBpedia took 0.01871013641357422s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0005350112915039062s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0008871555328369141s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.6689300537109375e-06s
Believability | Calculation of trust value for DBpedia took 1.0013580322265625e-05s
INFO | --- Analysis for DBpedia took 3005.5506570339203s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 8.7738037109375e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 7.62939453125e-06s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.30492687225341797s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.01872396469116211s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0005712509155273438s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 8.58306884765625e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 6.4373016357421875e-06s
INFO | --- Analysis for DBpedia abstract corpus took 6.805861234664917s
Availability | SPARQL endpoint availability check for DBpedia Commons took 6.159445762634277s
Availability | VoID file availability check for DBpedia Commons took 8.58306884765625e-06s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.31429433822631836s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.022524118423461914s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0009884834289550781s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 9.918212890625e-05s
Believability | Calculation of trust value for DBpedia Commons took 1.1444091796875e-05s
INFO | --- Analysis for DBpedia Commons took 10.77071762084961s
Availability | SPARQL endpoint availability check for DBpedia in German took 309.989976644516s
Availability | VoID file availability check for DBpedia in German took 0.6910312175750732s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.3476560115814209s
Reputation | Calculation of the PageRank for DBpedia in German took 0.018299341201782227s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for DBpedia in German took 0.000530242919921875s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 7.414817810058594e-05s
Believability | Calculation of trust value for DBpedia in German took 1.1205673217773438e-05s
INFO | --- Analysis for DBpedia in German took 519.1253764629364s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 132.43472003936768s
Availability | VoID file availability check for DBpedia in Greek took 0.16706371307373047s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.5549604892730713s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.01999044418334961s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0005300045013427734s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.0002009868621826172s
Believability | Calculation of trust value for DBpedia in Greek took 5.9604644775390625e-06s
INFO | --- Analysis for DBpedia in Greek took 587.3071341514587s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.4650275707244873s
Availability | VoID file availability check for DBpedia in Spanish took 0.5019266605377197s
Extra | Recovery of all triples for DBpedia in Spanish took 3.2442171573638916s
Performance | Total latancy measurement for DBpedia in Spanish took 1.2123041152954102s
Amount of data | Number of triples check for DBpedia in Spanish took 1.2201497554779053s
Interoperability | New terms check for DBpedia in Spanish took 2.66597318649292s
Versatility | Languages check for DBpedia in Spanish took 62.653300046920776s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.36138248443603516s
Security | Check HTTPS for DBpedia in Spanish took 0.140244722366333s
Interpretability | RDF structures check for DBpedia in Spanish took 0.7388293743133545s
Versatility | Serialization formats check for DBpedia in Spanish took 0.377821683883667s
Availability | RDF dump link check for DBpedia in Spanish took 0.33811211585998535s
License | MR license check for DBpedia in Spanish took 0.6262073516845703s
License | HR license check for DBpedia in Spanish took 61.7774772644043s
Amount of data | Number of property check for DBpedia in Spanish took 0.32790184020996094s
Understandability | Number of label check for DBpedia in Spanish took 1.1439220905303955s
Understandability | URI regex check for DBpedia in Spanish took 0.7138094902038574s
Understandability | Vocabs check for DBpedia in Spanish took 0.33893895149230957s
Verifiability | Authors check for DBpedia in Spanish took 0.2905900478363037s
Verifiability | Publishers check for DBpedia in Spanish took 0.2925741672515869s
Performance | Throughput check for DBpedia in Spanish took 11.8646399974823s
Amount of data | Check the number of entities for DBpedia in Spanish took 9.441375732421875e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 0.3023386001586914s
Interlinking | sameAs chians check for DBpedia in Spanish took 0.9264333248138428s
Interlinking | skos check for DBpedia in Spanish took 0.4324524402618408s
Interlinking | skos check for DBpedia in Spanish took 0.24239110946655273s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.435396671295166s
Currency | Creation date check for DBpedia in Spanish took 0.2997722625732422s
Currency | Modification date check for DBpedia in Spanish took 0.2862555980682373s
Rep.Conc. | URIs length for DBpedia in Spanish took 7.339097738265991s
Interoperability | New vocabularies check for DBpedia in Spanish took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 0.3020811080932617s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.3833296298980713s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.40254640579223633s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 1.1502463817596436s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.03228902816772461s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.028500080108642578s
Consistency | Disjoint class check for DBpedia in Spanish took 0.27972912788391113s
Consistency | Check Misplaced properties for DBpedia in Spanish took 8.216631889343262s
Consistency | Misplaced classes for DBpedia in Spanish took 1.2495296001434326s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 2.405064821243286s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.2205779552459717s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 6.719709157943726s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.03310871124267578s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 1.698315143585205s
Security | Sign check for DBpedia in Spanish took 1.141305685043335s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 3.235565423965454s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.3585691452026367s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.018636465072631836s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0005617141723632812s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00010776519775390625s
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 9.5367431640625e-06s
INFO | --- Analysis for DBpedia in Spanish took 530.6638643741608s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.305760383605957s
Availability | VoID file availability check for DBpedia in Basque took 0.5691366195678711s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.3003978729248047s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.018793582916259766s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0005500316619873047s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 1.3828277587890625e-05s
Believability | Calculation of trust value for DBpedia in Basque took 8.106231689453125e-06s
INFO | --- Analysis for DBpedia in Basque took 4.4849326610565186s
Availability | SPARQL endpoint availability check for DBpedia in French took 0.20235490798950195s
Availability | VoID file availability check for DBpedia in French took 0.19866943359375s
Extra | Recovery of all triples for DBpedia in French took 81.03463506698608s
Performance | Total latancy measurement for DBpedia in French took 0.4318969249725342s
Amount of data | Number of triples check for DBpedia in French took 2.027042865753174s
Interoperability | New terms check for DBpedia in French took 2.0043437480926514s
Versatility | Languages check for DBpedia in French took 300.01793336868286s
Interpretability | Number of blank nodes check for DBpedia in French took 0.16107988357543945s
Security | Check HTTPS for DBpedia in French took 0.1951742172241211s
Interpretability | RDF structures check for DBpedia in French took 0.3371400833129883s
Versatility | Serialization formats check for DBpedia in French took 0.24559497833251953s
Availability | RDF dump link check for DBpedia in French took 6.754663944244385s
License | MR license check for DBpedia in French took 0.8302853107452393s
License | HR license check for DBpedia in French took 73.07737803459167s
Amount of data | Number of property check for DBpedia in French took 0.1439826488494873s
Understandability | Number of label check for DBpedia in French took 1.352536678314209s
Understandability | URI regex check for DBpedia in French took 0.33779001235961914s
Understandability | Vocabs check for DBpedia in French took 0.10627603530883789s
Verifiability | Authors check for DBpedia in French took 0.25830769538879395s
Verifiability | Publishers check for DBpedia in French took 0.38312363624572754s
Performance | Throughput check for DBpedia in French took 10.393859624862671s
Amount of data | Check the number of entities for DBpedia in French took 2.1840996742248535s
Verifiability | Contribs. check for DBpedia in French took 0.11674952507019043s
Interlinking | sameAs chians check for DBpedia in French took 0.5123531818389893s
Interlinking | skos check for DBpedia in French took 0.21886515617370605s
Interlinking | skos check for DBpedia in French took 0.07347941398620605s
Timeliness | dataset update frequency check for DBpedia in French took 0.27404189109802246s
Currency | Creation date check for DBpedia in French took 0.1385512351989746s
Currency | Modification date check for DBpedia in French took 0.13496184349060059s
Rep.Conc. | URIs length for DBpedia in French took 36.835092306137085s
Interoperability | New vocabularies check for DBpedia in French took 10.618059635162354s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 0.11524558067321777s
Accuracy | Check Functional Property for DBpedia in French took 0.12762761116027832s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.10996699333190918s
Accuracy | Check Empty annotation labels for DBpedia in French took 23.56985902786255s
Accuracy | Check White space in annotation for DBpedia in French took 3.117764472961426s
Accuracy | Check Datatype consistency for DBpedia in French took 2.7537028789520264s
Consistency | Disjoint class check for DBpedia in French took 0.15133118629455566s
Consistency | Check Misplaced properties for DBpedia in French took 7.542529821395874s
Consistency | Misplaced classes for DBpedia in French took 9.257630586624146s
Consistency | Check Ontology hijacking for DBpedia in French took 23.393701791763306s
Consistency | Check Invalid usage of undefined classes for DBpedia in French took 1.3873236179351807s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 7.82686710357666s
Conciseness | Check Extensional conciseness for DBpedia in French took 3.0055832862854004s
Conciseness | Check Intensional conciseness for DBpedia in French took 1.1193525791168213s
Security | Sign check for DBpedia in French took 0.10442972183227539s
Availability | Check URIs Dereferenciability for DBpedia in French took 1985.1659104824066s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.7219922542572021s
Reputation | Calculation of the PageRank for DBpedia in French took 0.021520137786865234s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 6.67572021484375e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0005867481231689453s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.00023603439331054688s
Interoperability | Check the re-using of existing vocabs for DBpedia in French took 7.62837815284729s
Believability | Calculation of trust value for DBpedia in French took 1.0251998901367188e-05s
INFO | --- Analysis for DBpedia in French took 2717.669563770294s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 2.6978116035461426s
Availability | VoID file availability check for DBpedia in Japanese took 3.446929693222046s
Extra | Recovery of all triples for DBpedia in Japanese took 6.444958925247192s
Performance | Total latancy measurement for DBpedia in Japanese took 8.565867900848389s
Amount of data | Number of triples check for DBpedia in Japanese took 88.63292193412781s
Interoperability | New terms check for DBpedia in Japanese took 18.135128498077393s
Versatility | Languages check for DBpedia in Japanese took 1.7011451721191406s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.716141700744629s
Security | Check HTTPS for DBpedia in Japanese took 1.179988145828247s
Interpretability | RDF structures check for DBpedia in Japanese took 1.7640597820281982s
Versatility | Serialization formats check for DBpedia in Japanese took 1.7083303928375244s
Availability | RDF dump link check for DBpedia in Japanese took 1.7475225925445557s
License | MR license check for DBpedia in Japanese took 2.2983827590942383s
License | HR license check for DBpedia in Japanese took 121.71627902984619s
Amount of data | Number of property check for DBpedia in Japanese took 1.6980767250061035s
Understandability | Number of label check for DBpedia in Japanese took 8.345301389694214s
Understandability | URI regex check for DBpedia in Japanese took 3.715604066848755s
Understandability | Vocabs check for DBpedia in Japanese took 1.8319323062896729s
Verifiability | Authors check for DBpedia in Japanese took 1.704967975616455s
Verifiability | Publishers check for DBpedia in Japanese took 3.5968759059906006s
Performance | Throughput check for DBpedia in Japanese took 17.01544713973999s
Amount of data | Check the number of entities for DBpedia in Japanese took 8.821487426757812e-05s
Verifiability | Contribs. check for DBpedia in Japanese took 1.899876594543457s
Interlinking | sameAs chians check for DBpedia in Japanese took 3.4017908573150635s
Interlinking | skos check for DBpedia in Japanese took 2.321235418319702s
Interlinking | skos check for DBpedia in Japanese took 1.7325325012207031s
Timeliness | dataset update frequency check for DBpedia in Japanese took 2.0343234539031982s
Currency | Creation date check for DBpedia in Japanese took 1.9266636371612549s
Currency | Modification date check for DBpedia in Japanese took 1.7316243648529053s
Rep.Conc. | URIs length for DBpedia in Japanese took 139.45678448677063s
Interoperability | New vocabularies check for DBpedia in Japanese took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.6880526542663574s
Accuracy | Check Functional Property for DBpedia in Japanese took 1.7631545066833496s
Accuracy | Check Inverse Functional Property for DBpedia in Japanese took 1.7682483196258545s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 3.9745471477508545s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.02607583999633789s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.030069351196289062s
Consistency | Disjoint class check for DBpedia in Japanese took 1.8363947868347168s
Consistency | Check Misplaced properties for DBpedia in Japanese took 123.3413496017456s
Consistency | Misplaced classes for DBpedia in Japanese took 3.6724512577056885s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 5.005069971084595s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.3738818168640137s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 123.05974912643433s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.0331418514251709s
Conciseness | Check Intensional conciseness for DBpedia in Japanese took 3.708803176879883s
Security | Sign check for DBpedia in Japanese took 1.7190451622009277s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 3.1743152141571045s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.34581446647644043s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.019160032272338867s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0005335807800292969s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 9.942054748535156e-05s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 1.0013580322265625e-05s
INFO | --- Analysis for DBpedia in Japanese took 1186.704645872116s
Availability | SPARQL endpoint availability check for dbpedia lite took 9.059906005859375e-05s
Availability | VoID file availability check for dbpedia lite took 5.209723472595215s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.3132133483886719s
Reputation | Calculation of the PageRank for dbpedia lite took 0.018682241439819336s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0005292892456054688s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.00010156631469726562s
Believability | Calculation of trust value for dbpedia lite took 8.58306884765625e-06s
INFO | --- Analysis for dbpedia lite took 12.913249969482422s
Availability | SPARQL endpoint availability check for DBpedia-Live took 1.0251209735870361s
Availability | VoID file availability check for DBpedia-Live took 0.4828915596008301s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.2989952564239502s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.017955780029296875s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0005114078521728516s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 1.1444091796875e-05s
Believability | Calculation of trust value for DBpedia-Live took 1.0013580322265625e-05s
INFO | --- Analysis for DBpedia-Live took 5.884326696395874s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.24931097030639648s
Availability | VoID file availability check for DBpedia in Dutch took 0.1172487735748291s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.40512990951538086s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.018334388732910156s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0005168914794921875s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.0001659393310546875s
Believability | Calculation of trust value for DBpedia in Dutch took 9.298324584960938e-06s
INFO | --- Analysis for DBpedia in Dutch took 2.7065212726593018s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 1.0530519485473633s
Availability | VoID file availability check for DBpedia in Portuguese took 0.6650264263153076s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.3076803684234619s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.018610000610351562s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0005164146423339844s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 9.202957153320312e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 1.0251998901367188e-05s
INFO | --- Analysis for DBpedia in Portuguese took 4.809016227722168s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 8.678436279296875e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.5167155265808105s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.3044469356536865s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.01826763153076172s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.000518798828125s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 1.2874603271484375e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 1.0013580322265625e-05s
INFO | --- Analysis for DBpedia Spotlight took 2.7065937519073486s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 0.00010204315185546875s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 1.049041748046875e-05s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.31421399116516113s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.018339157104492188s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0005393028259277344s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 7.081031799316406e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 4.839897155761719e-05s
INFO | --- Analysis for DBpedia Spotlight NIF NER Corpus took 3.9677927494049072s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 0.28215622901916504s
Availability | VoID file availability check for DBpedia Wikidata took 7.62939453125e-06s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.3154470920562744s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.02039623260498047s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0005197525024414062s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 1.3113021850585938e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 1.1205673217773438e-05s
INFO | --- Analysis for DBpedia Wikidata took 2.3504810333251953s
Availability | SPARQL endpoint availability check for DBpedia took 8.20159912109375e-05s
Availability | VoID file availability check for DBpedia took 5.9604644775390625e-06s
Completeness | Calculation of interlinking completeness for DBpedia took 0.6355934143066406s
Reputation | Calculation of the PageRank for DBpedia took 0.0183713436126709s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0005102157592773438s
Interlinking | Calculation of Clustering coefficient for DBpedia took 1.1205673217773438e-05s
Believability | Calculation of trust value for DBpedia took 1.2159347534179688e-05s
INFO | --- Analysis for DBpedia took 4.324005365371704s
Availability | SPARQL endpoint availability check for DBTropes took 9.489059448242188e-05s
Availability | VoID file availability check for DBTropes took 0.7639369964599609s
Completeness | Calculation of interlinking completeness for DBTropes took 0.4608631134033203s
Reputation | Calculation of the PageRank for DBTropes took 0.01830458641052246s
Interlinking | Calculation of Degree of Connection for DBTropes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTropes took 0.0005648136138916016s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.202957153320312e-05s
Believability | Calculation of trust value for DBTropes took 1.2636184692382812e-05s
INFO | --- Analysis for DBTropes took 3.640707492828369s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 9.751319885253906e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 4.76837158203125e-06s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.4710533618927002s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.018355369567871094s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0005345344543457031s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 3.886222839355469e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 1.2159347534179688e-05s
INFO | --- Analysis for DBTune – Music-Related RDF took 4.667042016983032s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 4.887580871582031e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.3022427558898926s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.41551923751831055s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.01813650131225586s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0005178451538085938s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.507469177246094e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 1.2159347534179688e-05s
INFO | --- Analysis for DBTune.org Artists: Last.fm took 2.76924991607666s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 8.845329284667969e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.17523431777954102s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.33765292167663574s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.018204450607299805s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.552436828613281e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 1.1444091796875e-05s
INFO | --- Analysis for DBTune.org AudioScrobbler RDF Service took 2.1673097610473633s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 5.596121788024902s
Availability | VoID file availability check for DBTune.org/classical took 0.2574422359466553s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.4685080051422119s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.019482135772705078s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0005190372467041016s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.462501525878906e-05s
Interoperability | Check the re-using of existing vocabs for DBTune.org/classical took 3.5762786865234375e-06s
Believability | Calculation of trust value for DBTune.org/classical took 1.2874603271484375e-05s
INFO | --- Analysis for DBTune.org/classical took 8.870462894439697s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 5.559830904006958s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.2196195125579834s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.4099009037017822s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.018246173858642578s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0005159378051757812s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 6.651878356933594e-05s
Interoperability | Check the re-using of existing vocabs for DBTune.org John Peel sessions RDF server took 3.814697265625e-06s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 1.2874603271484375e-05s
INFO | --- Analysis for DBTune.org John Peel sessions RDF server took 10.486307382583618s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 5.58152174949646s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.21432733535766602s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.3671402931213379s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.018396615982055664s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0005278587341308594s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.961822509765625e-05s
Interoperability | Check the re-using of existing vocabs for DBTune.org Magnatune RDF server took 4.76837158203125e-06s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 1.4066696166992188e-05s
INFO | --- Analysis for DBTune.org Magnatune RDF server took 9.45840334892273s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 0.1331007480621338s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.3893396854400635s
Extra | Recovery of all triples for DBTune.org Musicbrainz D2R Server took 28.73656415939331s
Performance | Total latancy measurement for DBTune.org Musicbrainz D2R Server took 0.5824794769287109s
Amount of data | Number of triples check for DBTune.org Musicbrainz D2R Server took 0.7760574817657471s
Interoperability | New terms check for DBTune.org Musicbrainz D2R Server took 1.514441967010498s
Versatility | Languages check for DBTune.org Musicbrainz D2R Server took 1.3760652542114258s
Interpretability | Number of blank nodes check for DBTune.org Musicbrainz D2R Server took 0.827178955078125s
Interpretability | RDF structures check for DBTune.org Musicbrainz D2R Server took 0.12010836601257324s
Versatility | Serialization formats check for DBTune.org Musicbrainz D2R Server took 0.11659979820251465s
Availability | RDF dump link check for DBTune.org Musicbrainz D2R Server took 0.0933232307434082s
License | MR license check for DBTune.org Musicbrainz D2R Server took 0.08414912223815918s
License | HR license check for DBTune.org Musicbrainz D2R Server took 3.879748821258545s
Amount of data | Number of property check for DBTune.org Musicbrainz D2R Server took 0.13355684280395508s
Understandability | Number of label check for DBTune.org Musicbrainz D2R Server took 0.3417930603027344s
Understandability | URI regex check for DBTune.org Musicbrainz D2R Server took 0.18785643577575684s
Understandability | Vocabs check for DBTune.org Musicbrainz D2R Server took 0.08271169662475586s
Verifiability | Authors check for DBTune.org Musicbrainz D2R Server took 0.2714986801147461s
Verifiability | Publishers check for DBTune.org Musicbrainz D2R Server took 0.08532214164733887s
Performance | Throughput check for DBTune.org Musicbrainz D2R Server took 10.671016693115234s
Amount of data | Check the number of entities for DBTune.org Musicbrainz D2R Server took 8.821487426757812e-05s
Verifiability | Contribs. check for DBTune.org Musicbrainz D2R Server took 0.09525942802429199s
Interlinking | sameAs chians check for DBTune.org Musicbrainz D2R Server took 0.3313910961151123s
Interlinking | skos check for DBTune.org Musicbrainz D2R Server took 0.08698797225952148s
Interlinking | skos check for DBTune.org Musicbrainz D2R Server took 0.09603357315063477s
Timeliness | dataset update frequency check for DBTune.org Musicbrainz D2R Server took 0.09401488304138184s
Currency | Creation date check for DBTune.org Musicbrainz D2R Server took 0.22423243522644043s
Currency | Modification date check for DBTune.org Musicbrainz D2R Server took 0.2194347381591797s
Rep.Conc. | URIs length for DBTune.org Musicbrainz D2R Server took 8.721645593643188s
Interoperability | New vocabularies check for DBTune.org Musicbrainz D2R Server took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for DBTune.org Musicbrainz D2R Server took 0.12811970710754395s
Accuracy | Check Functional Property for DBTune.org Musicbrainz D2R Server took 0.09533309936523438s
Accuracy | Check Inverse Functional Property for DBTune.org Musicbrainz D2R Server took 0.0939188003540039s
Accuracy | Check Empty annotation labels for DBTune.org Musicbrainz D2R Server took 2.4306321144104004s
Accuracy | Check White space in annotation for DBTune.org Musicbrainz D2R Server took 0.09510421752929688s
Accuracy | Check Datatype consistency for DBTune.org Musicbrainz D2R Server took 1.13545560836792s
Consistency | Disjoint class check for DBTune.org Musicbrainz D2R Server took 0.09373593330383301s
Consistency | Check Misplaced properties for DBTune.org Musicbrainz D2R Server took 1.1146361827850342s
Consistency | Check Ontology hijacking for DBTune.org Musicbrainz D2R Server took 4.052212715148926s
Consistency | Check Invalid usage of undefined classes for DBTune.org Musicbrainz D2R Server took 1.1784865856170654s
Consistency | Check Invalid usage of undefined properties for DBTune.org Musicbrainz D2R Server took 2.0513434410095215s
Conciseness | Check Extensional conciseness for DBTune.org Musicbrainz D2R Server took 0.6091034412384033s
Security | Sign check for DBTune.org Musicbrainz D2R Server took 0.08558106422424316s
Availability | Check URIs Dereferenciability for DBTune.org Musicbrainz D2R Server took 1322.0792934894562s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.5410270690917969s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.01895308494567871s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0005197525024414062s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00011396408081054688s
Interoperability | Check the re-using of existing vocabs for DBTune.org Musicbrainz D2R Server took 1.6689300537109375e-06s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 1.2874603271484375e-05s
INFO | --- Analysis for DBTune.org Musicbrainz D2R Server took 1416.6330885887146s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 0.3616983890533447s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.22115302085876465s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.41108250617980957s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.018354177474975586s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.53131103515625e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 1.4066696166992188e-05s
INFO | --- Analysis for DBTune.org MySpace RDF Service took 2.6611390113830566s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 0.9225413799285889s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.8341033458709717s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.3161332607269287s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.018227577209472656s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0005078315734863281s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 1.2159347534179688e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 1.1205673217773438e-05s
INFO | --- Analysis for OpenUpLabs DCLG took 3.522573471069336s
Availability | SPARQL endpoint availability check for data.dcs took 8.606910705566406e-05s
Availability | VoID file availability check for data.dcs took 0.01488351821899414s
Completeness | Calculation of interlinking completeness for data.dcs took 0.3153400421142578s
Reputation | Calculation of the PageRank for data.dcs took 0.020261526107788086s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0005135536193847656s
Interlinking | Calculation of Clustering coefficient for data.dcs took 7.05718994140625e-05s
Believability | Calculation of trust value for data.dcs took 1.2874603271484375e-05s
INFO | --- Analysis for data.dcs took 2.62833309173584s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 4.076486587524414s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 1.8057315349578857s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.31522583961486816s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.01963019371032715s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0005137920379638672s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 1.1682510375976562e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 1.239776611328125e-05s
INFO | --- Analysis for Germany - Bundesministerium der Finanzen - Budget took 12.292268991470337s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 8.487701416015625e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 6.4373016357421875e-06s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.2954890727996826s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.017972707748413086s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0005321502685546875s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.600120544433594e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 6.67572021484375e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 6.248976707458496s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 0.0001437664031982422s
Availability | VoID file availability check for Debian Package Tracking System took 1.8194661140441895s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.31333136558532715s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.018034934997558594s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0005202293395996094s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.744529724121094e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 1.1205673217773438e-05s
INFO | --- Analysis for Debian Package Tracking System took 4.952413558959961s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 8.58306884765625e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 6.67572021484375e-06s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.6882109642028809s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.018065690994262695s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0005130767822265625s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.33514404296875e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.049041748046875e-05s
INFO | --- Analysis for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 3.3104946613311768s
Availability | SPARQL endpoint availability check for Demografie took 8.177757263183594e-05s
Availability | VoID file availability check for Demografie took 5.9604644775390625e-06s
Completeness | Calculation of interlinking completeness for Demografie took 0.9009394645690918s
Reputation | Calculation of the PageRank for Demografie took 0.019877910614013672s
Interlinking | Calculation of Degree of Connection for Demografie took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0005245208740234375s
Interlinking | Calculation of Clustering coefficient for Demografie took 1.3113021850585938e-05s
Believability | Calculation of trust value for Demografie took 1.3828277587890625e-05s
INFO | --- Analysis for Demografie took 3.4442386627197266s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 0.3977842330932617s
Availability | VoID file availability check for Projeto Desaparecidos took 0.016333580017089844s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.32707810401916504s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.021340370178222656s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.000522613525390625s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 4.649162292480469e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 1.0967254638671875e-05s
INFO | --- Analysis for Projeto Desaparecidos took 2.3522329330444336s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 0.00010538101196289062s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.20388126373291016s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.3020203113555908s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.01799178123474121s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0005304813385009766s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 0.00010228157043457031s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 1.239776611328125e-05s
INFO | --- Analysis for Deusto Entrepreneurship: sharing business knowledge took 3.6664063930511475s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 8.749961853027344e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 1.6397664546966553s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.38614797592163086s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.019163846969604492s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0005304813385009766s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00010204315185546875s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 1.2159347534179688e-05s
INFO | --- Analysis for DeustoTech (Deusto Institute of Technology) took 6.966679096221924s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 3.778327465057373s
Availability | VoID file availability check for Deutsche Biographie took 0.4751870632171631s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.3192305564880371s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.0182647705078125s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0005180835723876953s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 3.743171691894531e-05s
Believability | Calculation of trust value for Deutsche Biographie took 1.1682510375976562e-05s
INFO | --- Analysis for Deutsche Biographie took 6.603919744491577s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 8.869171142578125e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 1.1496241092681885s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 1.0607497692108154s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.01866459846496582s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0005266666412353516s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 6.198883056640625e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 1.1444091796875e-05s
INFO | --- Analysis for Deutsche Nationalbibliografie (DNB) took 10.383568286895752s
Availability | SPARQL endpoint availability check for dev8d took 9.226799011230469e-05s
Availability | VoID file availability check for dev8d took 6.67572021484375e-06s
Completeness | Calculation of interlinking completeness for dev8d took 0.3297274112701416s
Reputation | Calculation of the PageRank for dev8d took 0.020136117935180664s
Interlinking | Calculation of Degree of Connection for dev8d took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for dev8d took 0.0005342960357666016s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.556510925292969e-05s
Believability | Calculation of trust value for dev8d took 1.1205673217773438e-05s
INFO | --- Analysis for dev8d took 3.0728347301483154s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.144340753555298s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 20.200600385665894s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.3486659526824951s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.019425630569458008s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0006189346313476562s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 7.009506225585938e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 1.239776611328125e-05s
INFO | --- Analysis for Dewey Decimal Classification (DDC) took 92.28014469146729s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 0.00012445449829101562s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 5.0067901611328125e-06s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.4369044303894043s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.021620750427246094s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0005090236663818359s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 1.33514404296875e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 1.1444091796875e-05s
INFO | --- Analysis for Diachronic Ontologies from People's Daily took 4.430926561355591s
Availability | SPARQL endpoint availability check for Diavgeia took 0.6801576614379883s
Availability | VoID file availability check for Diavgeia took 0.5559024810791016s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.29966211318969727s
Reputation | Calculation of the PageRank for Diavgeia took 0.01898813247680664s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0006051063537597656s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 9.560585021972656e-05s
Believability | Calculation of trust value for Diavgeia took 9.5367431640625e-06s
INFO | --- Analysis for Diavgeia took 7.077027082443237s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.5299530029296875e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.7617769241333008s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.0425567626953125s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.018604040145874023s
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.0005116462707519531s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011372566223144531s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.33514404296875e-05s
INFO | --- Analysis for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 11.42405652999878s
Availability | SPARQL endpoint availability check for diigo.feed took 8.749961853027344e-05s
Availability | VoID file availability check for diigo.feed took 20.099664211273193s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.3692777156829834s
Reputation | Calculation of the PageRank for diigo.feed took 0.02068018913269043s
Interlinking | Calculation of Degree of Connection for diigo.feed took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for diigo.feed took 0.0005373954772949219s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 1.2874603271484375e-05s
Believability | Calculation of trust value for diigo.feed took 1.1205673217773438e-05s
INFO | --- Analysis for diigo.feed took 53.32572793960571s
Availability | SPARQL endpoint availability check for DisGeNET took 0.34790468215942383s
Availability | VoID file availability check for DisGeNET took 1.1682510375976562e-05s
Extra | Recovery of all triples for DisGeNET took 116.00306749343872s
Performance | Total latancy measurement for DisGeNET took 0.6004886627197266s
Amount of data | Number of triples check for DisGeNET took 5.217682600021362s
Interoperability | New terms check for DisGeNET took 5.244463205337524s
Versatility | Languages check for DisGeNET took 180.51154494285583s
Interpretability | Number of blank nodes check for DisGeNET took 3.89129900932312s
Interpretability | RDF structures check for DisGeNET took 0.9474825859069824s
Versatility | Serialization formats check for DisGeNET took 0.6371138095855713s
Availability | RDF dump link check for DisGeNET took 10.043243408203125s
License | MR license check for DisGeNET took 1.5095808506011963s
License | HR license check for DisGeNET took 180.5378773212433s
Amount of data | Number of property check for DisGeNET took 0.14349985122680664s
Understandability | Number of label check for DisGeNET took 5.630697727203369s
Understandability | URI regex check for DisGeNET took 0.5607395172119141s
Understandability | Vocabs check for DisGeNET took 0.14481735229492188s
Verifiability | Authors check for DisGeNET took 0.14758944511413574s
Verifiability | Publishers check for DisGeNET took 0.25731682777404785s
Performance | Throughput check for DisGeNET took 10.669818639755249s
Amount of data | Check the number of entities for DisGeNET took 6.8318727016448975s
Verifiability | Contribs. check for DisGeNET took 0.6671197414398193s
Interlinking | sameAs chians check for DisGeNET took 0.1334226131439209s
Interlinking | skos check for DisGeNET took 0.6100976467132568s
Interlinking | skos check for DisGeNET took 0.5240778923034668s
Timeliness | dataset update frequency check for DisGeNET took 0.7268829345703125s
Currency | Creation date check for DisGeNET took 0.891139030456543s
Currency | Modification date check for DisGeNET took 0.13605380058288574s
Rep.Conc. | URIs length for DisGeNET took 56.020620346069336s
Interoperability | New vocabularies check for DisGeNET took 9.73600459098816s
Consistency | Deprecated classes/propertiers check for DisGeNET took 0.1514904499053955s
Accuracy | Check Functional Property for DisGeNET took 0.5152547359466553s
Accuracy | Check Inverse Functional Property for DisGeNET took 0.47373318672180176s
Accuracy | Check Empty annotation labels for DisGeNET took 18.632256746292114s
Accuracy | Check White space in annotation for DisGeNET took 1.868492841720581s
Accuracy | Check Datatype consistency for DisGeNET took 1.3342633247375488s
Consistency | Disjoint class check for DisGeNET took 0.18772339820861816s
Consistency | Check Misplaced properties for DisGeNET took 44.91440987586975s
Consistency | Misplaced classes for DisGeNET took 4.42563533782959s
Consistency | Check Ontology hijacking for DisGeNET took 37.77232885360718s
Consistency | Check Invalid usage of undefined classes for DisGeNET took 1.1525075435638428s
Consistency | Check Invalid usage of undefined properties for DisGeNET took 31.872788190841675s
Conciseness | Check Extensional conciseness for DisGeNET took 1.4390130043029785s
Conciseness | Check Intensional conciseness for DisGeNET took 0.2969696521759033s
Security | Sign check for DisGeNET took 2.351857900619507s
Availability | Check URIs Dereferenciability for DisGeNET took 1704.653114080429s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.8429851531982422s
Reputation | Calculation of the PageRank for DisGeNET took 0.019570589065551758s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0005393028259277344s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00021505355834960938s
Interoperability | Check the re-using of existing vocabs for DisGeNET took 7.808225154876709s
Believability | Calculation of trust value for DisGeNET took 1.239776611328125e-05s
INFO | --- Analysis for DisGeNET took 2539.661456823349s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 8.630752563476562e-05s
Availability | VoID file availability check for CAP Italia in RDF took 5.7220458984375e-06s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.7061750888824463s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.018689870834350586s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0005269050598144531s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 1.2159347534179688e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 1.1682510375976562e-05s
INFO | --- Analysis for CAP Italia in RDF took 3.2264301776885986s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 0.00013947486877441406s
Availability | VoID file availability check for Distritos de Zaragoza took 4.0531158447265625e-06s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.4965493679046631s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.018405914306640625s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0005254745483398438s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 1.239776611328125e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 1.0967254638671875e-05s
INFO | --- Analysis for Distritos de Zaragoza took 3.954226493835449s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.1961669921875e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 5.4836273193359375e-06s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.28678393363952637s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.01822519302368164s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0005319118499755859s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 1.811981201171875e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 7.152557373046875e-06s
INFO | --- Analysis for DKH (Deusto Knowledge Hub) took 6.830626487731934s
Availability | SPARQL endpoint availability check for DM2E took 4.291534423828125e-05s
Availability | VoID file availability check for DM2E took 4.5299530029296875e-06s
Completeness | Calculation of interlinking completeness for DM2E took 0.36325907707214355s
Reputation | Calculation of the PageRank for DM2E took 0.017946720123291016s
Interlinking | Calculation of Degree of Connection for DM2E took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for DM2E took 0.0005102157592773438s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00010800361633300781s
Believability | Calculation of trust value for DM2E took 7.152557373046875e-06s
INFO | --- Analysis for DM2E took 1.903432846069336s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 4.1484832763671875e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.011861085891723633s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.2930748462677002s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.01826763153076172s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0005249977111816406s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 1.5497207641601562e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 7.152557373046875e-06s
INFO | --- Analysis for DMOZ RDF Dump took 2.234673500061035s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 4.363059997558594e-05s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.37380409240722656s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.6735835075378418s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.01923513412475586s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.000518798828125s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.0001595020294189453s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 7.152557373046875e-06s
INFO | --- Analysis for Gemeinsame Normdatei (GND) took 11.570410966873169s
Availability | SPARQL endpoint availability check for DOAP Store took 4.100799560546875e-05s
Availability | VoID file availability check for DOAP Store took 20.09777283668518s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.35665011405944824s
Reputation | Calculation of the PageRank for DOAP Store took 0.018487930297851562s
Interlinking | Calculation of Degree of Connection for DOAP Store took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DOAP Store took 0.0005245208740234375s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 1.621246337890625e-05s
Believability | Calculation of trust value for DOAP Store took 1.0013580322265625e-05s
INFO | --- Analysis for DOAP Store took 42.673256158828735s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 8.654594421386719e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 1.1126689910888672s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.29029083251953125s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.017746448516845703s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0005400180816650391s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.29425048828125e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 6.4373016357421875e-06s
INFO | --- Analysis for CrossRef DOI Resolver took 8.240546226501465s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.2093639373779297s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 5.0067901611328125e-06s
Extra | Recovery of all triples for Drug Data from the Health Insurance Fund of Macedonia took 498.0310764312744s
Performance | Total latancy measurement for Drug Data from the Health Insurance Fund of Macedonia took 2.8661108016967773s
Amount of data | Number of triples check for Drug Data from the Health Insurance Fund of Macedonia took 240.26981616020203s
Interoperability | New terms check for Drug Data from the Health Insurance Fund of Macedonia took 4.444418668746948s
Versatility | Languages check for Drug Data from the Health Insurance Fund of Macedonia took 300.083548784256s
Interpretability | Number of blank nodes check for Drug Data from the Health Insurance Fund of Macedonia took 9.93808388710022s
Interpretability | RDF structures check for Drug Data from the Health Insurance Fund of Macedonia took 3.1411750316619873s
Versatility | Serialization formats check for Drug Data from the Health Insurance Fund of Macedonia took 0.7174253463745117s
Availability | RDF dump link check for Drug Data from the Health Insurance Fund of Macedonia took 0.20390558242797852s
License | MR license check for Drug Data from the Health Insurance Fund of Macedonia took 0.7916488647460938s
License | HR license check for Drug Data from the Health Insurance Fund of Macedonia took 3.1847362518310547s
Amount of data | Number of property check for Drug Data from the Health Insurance Fund of Macedonia took 0.2621891498565674s
Understandability | Number of label check for Drug Data from the Health Insurance Fund of Macedonia took 3.318310022354126s
Understandability | URI regex check for Drug Data from the Health Insurance Fund of Macedonia took 0.5609993934631348s
Understandability | Vocabs check for Drug Data from the Health Insurance Fund of Macedonia took 0.16022801399230957s
Verifiability | Authors check for Drug Data from the Health Insurance Fund of Macedonia took 0.3561835289001465s
Verifiability | Publishers check for Drug Data from the Health Insurance Fund of Macedonia took 0.3218247890472412s
Performance | Throughput check for Drug Data from the Health Insurance Fund of Macedonia took 10.63584017753601s
Amount of data | Check the number of entities for Drug Data from the Health Insurance Fund of Macedonia took 9.131431579589844e-05s
Verifiability | Contribs. check for Drug Data from the Health Insurance Fund of Macedonia took 0.14410638809204102s
Interlinking | sameAs chians check for Drug Data from the Health Insurance Fund of Macedonia took 0.15460872650146484s
Interlinking | skos check for Drug Data from the Health Insurance Fund of Macedonia took 0.47618627548217773s
Interlinking | skos check for Drug Data from the Health Insurance Fund of Macedonia took 0.08960413932800293s
Timeliness | dataset update frequency check for Drug Data from the Health Insurance Fund of Macedonia took 0.2405683994293213s
Currency | Creation date check for Drug Data from the Health Insurance Fund of Macedonia took 0.13339519500732422s
Currency | Modification date check for Drug Data from the Health Insurance Fund of Macedonia took 0.1351165771484375s
Rep.Conc. | URIs length for Drug Data from the Health Insurance Fund of Macedonia took 225.44608569145203s
Interoperability | New vocabularies check for Drug Data from the Health Insurance Fund of Macedonia took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Drug Data from the Health Insurance Fund of Macedonia took 0.18053770065307617s
Accuracy | Check Functional Property for Drug Data from the Health Insurance Fund of Macedonia took 0.20762205123901367s
Accuracy | Check Inverse Functional Property for Drug Data from the Health Insurance Fund of Macedonia took 0.11799025535583496s
Accuracy | Check Empty annotation labels for Drug Data from the Health Insurance Fund of Macedonia took 54.14942407608032s
Accuracy | Check White space in annotation for Drug Data from the Health Insurance Fund of Macedonia took 2.421097755432129s
Accuracy | Check Datatype consistency for Drug Data from the Health Insurance Fund of Macedonia took 2.6908702850341797s
Consistency | Disjoint class check for Drug Data from the Health Insurance Fund of Macedonia took 0.30423808097839355s
Consistency | Check Misplaced properties for Drug Data from the Health Insurance Fund of Macedonia took 125.46441388130188s
Consistency | Misplaced classes for Drug Data from the Health Insurance Fund of Macedonia took 6.394806385040283s
Consistency | Check Ontology hijacking for Drug Data from the Health Insurance Fund of Macedonia took 76.97787737846375s
Consistency | Check Invalid usage of undefined classes for Drug Data from the Health Insurance Fund of Macedonia took 1.2317180633544922s
Consistency | Check Invalid usage of undefined properties for Drug Data from the Health Insurance Fund of Macedonia took 126.52248525619507s
Conciseness | Check Extensional conciseness for Drug Data from the Health Insurance Fund of Macedonia took 2.304901599884033s
Conciseness | Check Intensional conciseness for Drug Data from the Health Insurance Fund of Macedonia took 0.5359258651733398s
Security | Sign check for Drug Data from the Health Insurance Fund of Macedonia took 1.0354259014129639s
Availability | Check URIs Dereferenciability for Drug Data from the Health Insurance Fund of Macedonia took 3.284942865371704s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 1.0105538368225098s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.01910853385925293s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0005476474761962891s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 4.982948303222656e-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.1444091796875e-05s
INFO | --- Analysis for Drug Data from the Health Insurance Fund of Macedonia took 3967.990519285202s
Availability | SPARQL endpoint availability check for dspace took 4.792213439941406e-05s
Availability | VoID file availability check for dspace took 5.7220458984375e-06s
Completeness | Calculation of interlinking completeness for dspace took 0.32297205924987793s
Reputation | Calculation of the PageRank for dspace took 0.018564939498901367s
Interlinking | Calculation of Degree of Connection for dspace took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for dspace took 0.00052642822265625s
Interlinking | Calculation of Clustering coefficient for dspace took 1.2159347534179688e-05s
Believability | Calculation of trust value for dspace took 6.9141387939453125e-06s
INFO | --- Analysis for dspace took 45.52743697166443s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 1.6014130115509033s
Availability | VoID file availability check for DURAARK - Linked Building Data took 1.7486093044281006s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.2908055782318115s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.01813507080078125s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0005199909210205078s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 1.2874603271484375e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 8.344650268554688e-06s
INFO | --- Analysis for DURAARK - Linked Building Data took 11.609354972839355s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 271.45745277404785s
Availability | VoID file availability check for MetaLex Document Server took 19.999180555343628s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.34980010986328125s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.01879286766052246s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0005402565002441406s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 2.09808349609375e-05s
Believability | Calculation of trust value for MetaLex Document Server took 1.1682510375976562e-05s
INFO | --- Analysis for MetaLex Document Server took 434.12346601486206s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 0.9140012264251709s
Availability | VoID file availability check for Dutch Ships and Sailors took 5.245208740234375e-06s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.3921027183532715s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.018414735794067383s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0005428791046142578s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 3.790855407714844e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 7.3909759521484375e-06s
INFO | --- Analysis for Dutch Ships and Sailors took 7.274603366851807s
Availability | SPARQL endpoint availability check for DWS-Group took 4.410743713378906e-05s
Availability | VoID file availability check for DWS-Group took 1.4014523029327393s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.289262056350708s
Reputation | Calculation of the PageRank for DWS-Group took 0.017927885055541992s
Interlinking | Calculation of Degree of Connection for DWS-Group took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DWS-Group took 0.0005161762237548828s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 9.965896606445312e-05s
Believability | Calculation of trust value for DWS-Group took 1.1444091796875e-05s
INFO | --- Analysis for DWS-Group took 3.326528549194336s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 7.62939453125e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 5.360610485076904s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.3197181224822998s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.017940282821655273s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 1.1205673217773438e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 1.239776611328125e-05s
INFO | --- Analysis for E1 - Nuvem dados took 8.852829217910767s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 1.1281111240386963s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.636629581451416s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.32420945167541504s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.018131494522094727s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.000518798828125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00011706352233886719s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i @ University of Alaska Fairbanks took 10.101484298706055s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 30.07720446586609s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 19.9957435131073s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.5122206211090088s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.019390344619750977s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0005543231964111328s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.412101745605469e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i @ Clark Atlanta University took 92.1300721168518s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 30.068819761276245s
Availability | VoID file availability check for eagle-i @ The City College of New York took 20.099172353744507s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.32224345207214355s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.01847243309020996s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0005576610565185547s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 7.43865966796875e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i @ The City College of New York took 92.39076638221741s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 30.167542457580566s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 20.09916615486145s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.32555460929870605s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.01837468147277832s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.52587890625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0005221366882324219s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 0.00010204315185546875s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i @ Charles R. Drew University took 92.33717799186707s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 30.30636978149414s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 20.08962845802307s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.4053637981414795s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.018323421478271484s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0005238056182861328s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00014209747314453125s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i @ Dartmouth College took 93.2294671535492s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 30.107316970825195s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 20.017821311950684s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.3042597770690918s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.018142223358154297s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0005195140838623047s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 9.131431579589844e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i @ Florida Agricultural and Mechanical University took 91.93485140800476s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 5.092885494232178s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.44977736473083496s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.2910013198852539s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.018255233764648438s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0005154609680175781s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00012803077697753906s
Believability | Calculation of trust value for eagle-i @ Harvard University took 1.049041748046875e-05s
INFO | --- Analysis for eagle-i @ Harvard University took 8.758521556854248s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 1.0673341751098633s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.6250958442687988s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.329547643661499s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.024583101272583008s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.0001456737518310547s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i @ University of Hawai’i at Mānoa took 132.90418672561646s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 30.098628282546997s
Availability | VoID file availability check for eagle-i @ Howard University took 20.004679918289185s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.297454833984375s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.018588781356811523s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0005545616149902344s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 7.987022399902344e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i @ Howard University took 92.03131151199341s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 30.21358895301819s
Availability | VoID file availability check for eagle-i @ Hunter College took 19.999845504760742s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.30724334716796875s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.01989006996154785s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0005218982696533203s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 7.271766662597656e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 1.0728836059570312e-05s
INFO | --- Analysis for eagle-i @ Hunter College took 92.24619650840759s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 1.0641841888427734s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.6373860836029053s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.31752705574035645s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.018833160400390625s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.00054168701171875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011730194091796875s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i @ Jackson State University took 9.817222833633423s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 30.098541498184204s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 20.10114574432373s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.29769206047058105s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.01882648468017578s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0005521774291992188s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.886222839355469e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i @ Meharry Medical College took 92.00155448913574s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 30.15587544441223s
Availability | VoID file availability check for eagle-i @ Montana State University took 20.00283455848694s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.2935175895690918s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.018163442611694336s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0005333423614501953s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 9.751319885253906e-05s
Believability | Calculation of trust value for eagle-i @ Montana State University took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i @ Montana State University took 92.07302808761597s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 1.0825896263122559s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.6618654727935791s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.3057079315185547s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.018382549285888672s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0005338191986083984s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.894371032714844e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 1.0013580322265625e-05s
INFO | --- Analysis for eagle-i @ Morehouse School of Medicine took 8.45912480354309s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 2.3245596885681152s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 6.87203311920166s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.3931262493133545s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.018735408782958984s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0005316734313964844s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.0001354217529296875s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i @ Oregon Health and Science University took 243.2737843990326s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 1.1089913845062256s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.7007548809051514s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.3014638423919678s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.018615245819091797s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0005474090576171875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.914138793945312e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i @ Ponce School of Medicine took 6.32016396522522s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 1.0704576969146729s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.6243131160736084s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.30901479721069336s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.01813340187072754s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0005176067352294922s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.365776062011719e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i @ Texas Southern University took 6.405128240585327s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 1.0904057025909424s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.7590844631195068s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.31363368034362793s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.018244504928588867s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0005559921264648438s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.985664367675781e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 7.62939453125e-06s
INFO | --- Analysis for eagle-i @ Tuskegee University took 6.487595081329346s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 1.1652400493621826s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.6667637825012207s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.29897475242614746s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.019070863723754883s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0005233287811279297s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.00010895729064941406s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i @ Universidad Central del Caribe took 10.967360258102417s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.087611436843872s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.6347506046295166s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.9524357318878174s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.019312620162963867s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0005135536193847656s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0001246929168701172s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 27.140388011932373s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 1.0744149684906006s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.6174616813659668s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.3144259452819824s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.018821239471435547s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0005199909210205078s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.413459777832031e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 1.3113021850585938e-05s
INFO | --- Analysis for eagle-i @ University of Texas at El Paso took 10.072355270385742s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 30.063262224197388s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 20.102113008499146s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.32514524459838867s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.01994633674621582s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0005288124084472656s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 8.535385131835938e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.3113021850585938e-05s
INFO | --- Analysis for eagle-i @ University of Texas at San Antonio took 93.78022861480713s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.2751615047454834s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.015578269958496094s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.3095724582672119s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.019391775131225586s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0005154609680175781s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.512901306152344e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 1.1444091796875e-05s
INFO | --- Analysis for eagle-i @ Vanderbilt University took 2.5782270431518555s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 1.1104846000671387s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.6861553192138672s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.289808988571167s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.018843650817871094s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0005161762237548828s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.891654968261719e-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 9.158261775970459s
Availability | SPARQL endpoint availability check for Emergency situation took 0.7060427665710449s
Availability | VoID file availability check for Emergency situation took 0.4644474983215332s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.3274266719818115s
Reputation | Calculation of the PageRank for Emergency situation took 0.018717050552368164s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0005135536193847656s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.792213439941406e-05s
Believability | Calculation of trust value for Emergency situation took 1.1444091796875e-05s
INFO | --- Analysis for Emergency situation took 3.5159757137298584s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.09579086303710938s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.014980077743530273s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.3172438144683838s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.018210649490356445s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0005414485931396484s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010704994201660156s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for European Central Bank (ECB) Linked Data took 1.9010155200958252s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 2.352456569671631s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 3.698333978652954s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.5652368068695068s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.018224239349365234s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0005533695220947266s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.600120544433594e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 8.58306884765625e-06s
INFO | --- Analysis for European Central Bank Statistics (PublicData.eu) took 12.006945610046387s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.1765100955963135s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.5335226058959961s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.30201292037963867s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.017945051193237305s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0005142688751220703s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.580352783203125e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 1.1920928955078125e-05s
INFO | --- Analysis for ECCO-TCP Eighteenth Century Texts Linked Data took 4.6265709400177s
Availability | SPARQL endpoint availability check for ECLAP took 6.282121419906616s
Availability | VoID file availability check for ECLAP took 8.106231689453125e-06s
Completeness | Calculation of interlinking completeness for ECLAP took 0.287583589553833s
Reputation | Calculation of the PageRank for ECLAP took 0.01803898811340332s
Interlinking | Calculation of Degree of Connection for ECLAP took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ECLAP took 0.0005645751953125s
Interlinking | Calculation of Clustering coefficient for ECLAP took 3.719329833984375e-05s
Believability | Calculation of trust value for ECLAP took 1.1205673217773438e-05s
INFO | --- Analysis for ECLAP took 10.740887641906738s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 8.702278137207031e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.057682037353515625s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.295198917388916s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.018912076950073242s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0005421638488769531s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 6.151199340820312e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.1920928955078125e-05s
INFO | --- Analysis for School of Electronics and Computer Science, University of Southampton took 2.436570882797241s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 9.369850158691406e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 4.291534423828125e-06s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.7835314273834229s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.019641637802124023s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.000629425048828125s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 1.3113021850585938e-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 4.906794548034668s
Availability | SPARQL endpoint availability check for Edublogs took 0.00012731552124023438s
Availability | VoID file availability check for Edublogs took 1.0013580322265625e-05s
Completeness | Calculation of interlinking completeness for Edublogs took 0.31888389587402344s
Reputation | Calculation of the PageRank for Edublogs took 0.01854729652404785s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0005242824554443359s
Interlinking | Calculation of Clustering coefficient for Edublogs took 9.5367431640625e-05s
Believability | Calculation of trust value for Edublogs took 1.3589859008789062e-05s
INFO | --- Analysis for Edublogs took 3.031266689300537s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.7724077701568604s
Availability | VoID file availability check for education.data.gov.uk took 0.5498509407043457s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.31285953521728516s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.018378496170043945s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0005583763122558594s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 8.845329284667969e-05s
Believability | Calculation of trust value for education.data.gov.uk took 1.0728836059570312e-05s
INFO | --- Analysis for education.data.gov.uk took 4.308489799499512s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 0.18922185897827148s
Availability | VoID file availability check for OpenUpLabs Education took 0.020460128784179688s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.27956271171569824s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.019335508346557617s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0005176067352294922s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 1.430511474609375e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 5.817413330078125e-05s
INFO | --- Analysis for OpenUpLabs Education took 2.265141010284424s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 392.52144169807434s
Availability | VoID file availability check for Educational programs - SISVU took 262.14356780052185s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.4023160934448242s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.018732070922851562s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0005359649658203125s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 5.53131103515625e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 1.2636184692382812e-05s
INFO | --- Analysis for Educational programs - SISVU took 1443.7518882751465s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 1.7784349918365479s
Availability | VoID file availability check for European Environment Agency Published Products took 2.3117854595184326s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.48124170303344727s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.01809215545654297s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0005261898040771484s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 3.552436828613281e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 8.58306884765625e-06s
INFO | --- Analysis for European Environment Agency Published Products took 9.777321577072144s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.5246400833129883s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.3091745376586914s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 1.1133513450622559s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020786523818969727s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0005290508270263672s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.316734313964844e-05s
Interoperability | Check the re-using of existing vocabs for EEA Reporting Obligations Database took 2.6162192821502686s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 8.58306884765625e-06s
INFO | --- Analysis for EEA Reporting Obligations Database took 10.755411863327026s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.23350977897644043s
Availability | VoID file availability check for EEA Vocabularies took 7.867813110351562e-06s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.31781864166259766s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.01852726936340332s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0005238056182861328s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.368492126464844e-05s
Believability | Calculation of trust value for EEA Vocabularies took 1.1682510375976562e-05s
INFO | --- Analysis for EEA Vocabularies took 7.724579811096191s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 32.76891493797302s
Availability | VoID file availability check for Ege University Linked Open Data took 20.003539323806763s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.3885815143585205s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.018506288528442383s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0005123615264892578s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 2.4557113647460938e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 1.1205673217773438e-05s
INFO | --- Analysis for Ege University Linked Open Data took 68.31917333602905s
Availability | SPARQL endpoint availability check for E-Government Ontology took 1.4056363105773926s
Availability | VoID file availability check for E-Government Ontology took 0.649925708770752s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.8713235855102539s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.018578052520751953s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0005130767822265625s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 1.4066696166992188e-05s
Believability | Calculation of trust value for E-Government Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for E-Government Ontology took 5.57579779624939s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6002740859985352s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8347480297088623s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 2.659930467605591s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1834259033203125s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6495585441589355s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.5906310081481934s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.39021110534668s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 2.2321267127990723s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4205489158630371s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23952937126159668s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24715018272399902s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3270454406738281s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 2.967128276824951s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23405241966247559s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.34946775436401367s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5774245262145996s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.25737929344177246s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6953980922698975s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.28396058082580566s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 10.93439531326294s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 6.580352783203125e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2955348491668701s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2583615779876709s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.35550546646118164s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2266371250152588s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3035764694213867s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2429640293121338s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5707790851593018s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 3.204275608062744s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2574608325958252s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2674410343170166s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.266237735748291s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8862419128417969s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.030256986618041992s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.028728246688842773s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2364051342010498s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 2.040215015411377s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5370042324066162s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.2353506088256836s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1527044773101807s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 2.7554690837860107s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.032422542572021484s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.38042736053466797s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.38323450088500977s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 3451.8371925354004s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7585537433624268s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.019303321838378906s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0005373954772949219s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 3.981590270996094e-05s
Interoperability | Check the re-using of existing vocabs for Aragon Interoperable Information Structure EI2A - aragon open data took 1.430511474609375e-06s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 9.059906005859375e-06s
INFO | --- Analysis for Aragon Interoperable Information Structure EI2A - aragon open data took 3610.409060239792s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 0.6666054725646973s
Availability | VoID file availability check for EIONET RDF Data took 0.36099743843078613s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 3.379549980163574s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.019482135772705078s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0005292892456054688s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010728836059570312s
Interoperability | Check the re-using of existing vocabs for EIONET RDF Data took 1.1920928955078125e-06s
Believability | Calculation of trust value for EIONET RDF Data took 8.58306884765625e-06s
INFO | --- Analysis for EIONET RDF Data took 11.66767692565918s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 0.21901392936706543s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.8144881725311279s
Extra | Recovery of all triples for ELTE Digital Institutional Repository (EDIT) took 28.021058082580566s
Performance | Total latancy measurement for ELTE Digital Institutional Repository (EDIT) took 0.6976790428161621s
Amount of data | Number of triples check for ELTE Digital Institutional Repository (EDIT) took 21.897534132003784s
Interoperability | New terms check for ELTE Digital Institutional Repository (EDIT) took 1.3118035793304443s
Versatility | Languages check for ELTE Digital Institutional Repository (EDIT) took 23.93557381629944s
Interpretability | Number of blank nodes check for ELTE Digital Institutional Repository (EDIT) took 3.958763360977173s
Security | Check HTTPS for ELTE Digital Institutional Repository (EDIT) took 0.09721779823303223s
Interpretability | RDF structures check for ELTE Digital Institutional Repository (EDIT) took 0.9278466701507568s
Versatility | Serialization formats check for ELTE Digital Institutional Repository (EDIT) took 0.2549293041229248s
Availability | RDF dump link check for ELTE Digital Institutional Repository (EDIT) took 0.08785057067871094s
License | MR license check for ELTE Digital Institutional Repository (EDIT) took 0.3876042366027832s
License | HR license check for ELTE Digital Institutional Repository (EDIT) took 0.5187933444976807s
Amount of data | Number of property check for ELTE Digital Institutional Repository (EDIT) took 0.19747233390808105s
Understandability | Number of label check for ELTE Digital Institutional Repository (EDIT) took 17.262367486953735s
Understandability | URI regex check for ELTE Digital Institutional Repository (EDIT) took 0.34520506858825684s
Understandability | Vocabs check for ELTE Digital Institutional Repository (EDIT) took 0.08202075958251953s
Verifiability | Authors check for ELTE Digital Institutional Repository (EDIT) took 7.9652745723724365s
Verifiability | Publishers check for ELTE Digital Institutional Repository (EDIT) took 1.061664342880249s
Performance | Throughput check for ELTE Digital Institutional Repository (EDIT) took 15.359450340270996s
Amount of data | Check the number of entities for ELTE Digital Institutional Repository (EDIT) took 8.535385131835938e-05s
Verifiability | Contribs. check for ELTE Digital Institutional Repository (EDIT) took 0.10051083564758301s
Interlinking | sameAs chians check for ELTE Digital Institutional Repository (EDIT) took 0.08398795127868652s
Interlinking | skos check for ELTE Digital Institutional Repository (EDIT) took 0.1609969139099121s
Interlinking | skos check for ELTE Digital Institutional Repository (EDIT) took 0.05964255332946777s
Timeliness | dataset update frequency check for ELTE Digital Institutional Repository (EDIT) took 0.1314697265625s
Currency | Creation date check for ELTE Digital Institutional Repository (EDIT) took 2.947800636291504s
Currency | Modification date check for ELTE Digital Institutional Repository (EDIT) took 0.6011457443237305s
Rep.Conc. | URIs length for ELTE Digital Institutional Repository (EDIT) took 86.48483633995056s
Interoperability | New vocabularies check for ELTE Digital Institutional Repository (EDIT) took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for ELTE Digital Institutional Repository (EDIT) took 0.13553428649902344s
Accuracy | Check Functional Property for ELTE Digital Institutional Repository (EDIT) took 0.17844176292419434s
Accuracy | Check Inverse Functional Property for ELTE Digital Institutional Repository (EDIT) took 0.10715818405151367s
Accuracy | Check Empty annotation labels for ELTE Digital Institutional Repository (EDIT) took 2.256052255630493s
Accuracy | Check White space in annotation for ELTE Digital Institutional Repository (EDIT) took 0.372342586517334s
Accuracy | Check Datatype consistency for ELTE Digital Institutional Repository (EDIT) took 4.757687330245972s
Consistency | Disjoint class check for ELTE Digital Institutional Repository (EDIT) took 0.16898870468139648s
Consistency | Check Misplaced properties for ELTE Digital Institutional Repository (EDIT) took 4.34895658493042s
Consistency | Check Ontology hijacking for ELTE Digital Institutional Repository (EDIT) took 1.2393677234649658s
Consistency | Check Invalid usage of undefined classes for ELTE Digital Institutional Repository (EDIT) took 1.179661512374878s
Consistency | Check Invalid usage of undefined properties for ELTE Digital Institutional Repository (EDIT) took 5.352156639099121s
Conciseness | Check Extensional conciseness for ELTE Digital Institutional Repository (EDIT) took 2.8653697967529297s
Security | Sign check for ELTE Digital Institutional Repository (EDIT) took 0.15914130210876465s
Availability | Check URIs Dereferenciability for ELTE Digital Institutional Repository (EDIT) took 952.8180205821991s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.3812839984893799s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.018517732620239258s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0005316734313964844s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 1.8835067749023438e-05s
Interoperability | Check the re-using of existing vocabs for ELTE Digital Institutional Repository (EDIT) took 1.9073486328125e-06s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 1.2636184692382812e-05s
INFO | --- Analysis for ELTE Digital Institutional Repository (EDIT) took 1404.1483693122864s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 0.3132748603820801s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.2701413631439209s
Extra | Recovery of all triples for El Viajero's tourism dataset took 5.729651212692261s
Performance | Total latancy measurement for El Viajero's tourism dataset took 0.6675500869750977s
Amount of data | Number of triples check for El Viajero's tourism dataset took 0.6462311744689941s
Interoperability | New terms check for El Viajero's tourism dataset took 1.6800808906555176s
Versatility | Languages check for El Viajero's tourism dataset took 12.216211318969727s
Interpretability | Number of blank nodes check for El Viajero's tourism dataset took 0.1938772201538086s
Interpretability | RDF structures check for El Viajero's tourism dataset took 0.19408321380615234s
Versatility | Serialization formats check for El Viajero's tourism dataset took 0.16761994361877441s
Availability | RDF dump link check for El Viajero's tourism dataset took 0.1010134220123291s
License | MR license check for El Viajero's tourism dataset took 0.11394286155700684s
License | HR license check for El Viajero's tourism dataset took 0.47670793533325195s
Amount of data | Number of property check for El Viajero's tourism dataset took 0.1796736717224121s
Understandability | Number of label check for El Viajero's tourism dataset took 0.23049044609069824s
Understandability | URI regex check for El Viajero's tourism dataset took 0.20746827125549316s
Understandability | Vocabs check for El Viajero's tourism dataset took 0.11749672889709473s
Verifiability | Authors check for El Viajero's tourism dataset took 0.17886090278625488s
Verifiability | Publishers check for El Viajero's tourism dataset took 0.1105797290802002s
Performance | Throughput check for El Viajero's tourism dataset took 10.67786979675293s
Amount of data | Check the number of entities for El Viajero's tourism dataset took 8.58306884765625e-05s
Verifiability | Contribs. check for El Viajero's tourism dataset took 0.12320089340209961s
Interlinking | sameAs chians check for El Viajero's tourism dataset took 0.18189430236816406s
Interlinking | skos check for El Viajero's tourism dataset took 0.11613798141479492s
Interlinking | skos check for El Viajero's tourism dataset took 0.10919642448425293s
Timeliness | dataset update frequency check for El Viajero's tourism dataset took 0.10802078247070312s
Currency | Creation date check for El Viajero's tourism dataset took 0.16922950744628906s
Currency | Modification date check for El Viajero's tourism dataset took 0.16866564750671387s
Rep.Conc. | URIs length for El Viajero's tourism dataset took 2.5149242877960205s
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.17173385620117188s
Accuracy | Check Functional Property for El Viajero's tourism dataset took 0.18675732612609863s
Accuracy | Check Inverse Functional Property for El Viajero's tourism dataset took 0.0992891788482666s
Accuracy | Check Empty annotation labels for El Viajero's tourism dataset took 1.1387255191802979s
Accuracy | Check White space in annotation for El Viajero's tourism dataset took 0.033040523529052734s
Accuracy | Check Datatype consistency for El Viajero's tourism dataset took 0.029575824737548828s
Consistency | Disjoint class check for El Viajero's tourism dataset took 0.1656050682067871s
Consistency | Check Misplaced properties for El Viajero's tourism dataset took 1.116610050201416s
Consistency | Misplaced classes for El Viajero's tourism dataset took 0.3192884922027588s
Consistency | Check Ontology hijacking for El Viajero's tourism dataset took 2.9044034481048584s
Consistency | Check Invalid usage of undefined classes for El Viajero's tourism dataset took 1.4241468906402588s
Consistency | Check Invalid usage of undefined properties for El Viajero's tourism dataset took 2.3575515747070312s
Conciseness | Check Extensional conciseness for El Viajero's tourism dataset took 0.03178691864013672s
Conciseness | Check Intensional conciseness for El Viajero's tourism dataset took 0.27353644371032715s
Security | Sign check for El Viajero's tourism dataset took 0.09961509704589844s
Availability | Check URIs Dereferenciability for El Viajero's tourism dataset took 1671.8019316196442s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.5759332180023193s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.020850181579589844s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0005292892456054688s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 0.0001506805419921875s
Interoperability | Check the re-using of existing vocabs for El Viajero's tourism dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for El Viajero's tourism dataset took 1.1205673217773438e-05s
INFO | --- Analysis for El Viajero's tourism dataset took 1755.272982120514s
Availability | SPARQL endpoint availability check for EMN took 8.702278137207031e-05s
Availability | VoID file availability check for EMN took 7.62939453125e-06s
Completeness | Calculation of interlinking completeness for EMN took 0.3339107036590576s
Reputation | Calculation of the PageRank for EMN took 0.01841449737548828s
Interlinking | Calculation of Degree of Connection for EMN took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for EMN took 0.0005276203155517578s
Interlinking | Calculation of Clustering coefficient for EMN took 4.744529724121094e-05s
Believability | Calculation of trust value for EMN took 1.2636184692382812e-05s
INFO | --- Analysis for EMN took 2.299787759780884s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 0.0001468658447265625s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.009251832962036133s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.2938110828399658s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.01943802833557129s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0005106925964355469s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.507469177246094e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 8.58306884765625e-06s
INFO | --- Analysis for EnAKTing CO2 Emission Dataset took 1.8367435932159424s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 5.054473876953125e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.009566068649291992s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.36470961570739746s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.018265724182128906s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0005207061767578125s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 3.981590270996094e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 5.245208740234375e-06s
INFO | --- Analysis for EnAKTing Crime Dataset took 1.925159215927124s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 8.678436279296875e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.01161646842956543s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.32263946533203125s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.01834249496459961s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0005228519439697266s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 4.00543212890625e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for EnAKTing Energy Dataset took 2.398317813873291s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 5.602836608886719e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.008559226989746094s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.39731907844543457s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.018385887145996094s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0005218982696533203s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 9.489059448242188e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 9.298324584960938e-06s
INFO | --- Analysis for EnAKTing Mortality Dataset took 1.8825101852416992s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 8.845329284667969e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.009694814682006836s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.3233358860015869s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.018167495727539062s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0005178451538085938s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.790855407714844e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 9.298324584960938e-06s
INFO | --- Analysis for EnAKTing NHS Dataset took 1.9428527355194092s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 9.608268737792969e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.010224342346191406s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.5009121894836426s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.018385887145996094s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0005123615264892578s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.5789947509765625e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 1.0013580322265625e-05s
INFO | --- Analysis for EnAKTing Population Dataset took 2.07143235206604s
Availability | SPARQL endpoint availability check for Enel Shops took 8.726119995117188e-05s
Availability | VoID file availability check for Enel Shops took 1.4066696166992188e-05s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.4322235584259033s
Reputation | Calculation of the PageRank for Enel Shops took 0.018079280853271484s
Interlinking | Calculation of Degree of Connection for Enel Shops took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Enel Shops took 0.0005309581756591797s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 1.2159347534179688e-05s
Believability | Calculation of trust value for Enel Shops took 1.1444091796875e-05s
INFO | --- Analysis for Enel Shops took 2.2451012134552s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 1.1556661128997803s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 4.5299530029296875e-06s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.2956266403198242s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.018213510513305664s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0005154609680175781s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 1.2159347534179688e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 6.9141387939453125e-06s
INFO | --- Analysis for Energy efficiency assessments and improvements took 6.370169639587402s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 0.8847386837005615s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 5.7220458984375e-06s
Extra | Recovery of all triples for English Heritage Archaeological Sciences Thesaurus took 0.4367237091064453s
Performance | Total latancy measurement for English Heritage Archaeological Sciences Thesaurus took 2.2554571628570557s
Amount of data | Number of triples check for English Heritage Archaeological Sciences Thesaurus took 0.6924166679382324s
Versatility | Languages check for English Heritage Archaeological Sciences Thesaurus took 0.289684534072876s
Interpretability | Number of blank nodes check for English Heritage Archaeological Sciences Thesaurus took 0.6283543109893799s
Security | Check HTTPS for English Heritage Archaeological Sciences Thesaurus took 0.2698018550872803s
Interpretability | RDF structures check for English Heritage Archaeological Sciences Thesaurus took 0.34765100479125977s
Versatility | Serialization formats check for English Heritage Archaeological Sciences Thesaurus took 0.4865992069244385s
Availability | RDF dump link check for English Heritage Archaeological Sciences Thesaurus took 0.4590568542480469s
License | MR license check for English Heritage Archaeological Sciences Thesaurus took 0.6978602409362793s
License | HR license check for English Heritage Archaeological Sciences Thesaurus took 0.539647102355957s
Amount of data | Number of property check for English Heritage Archaeological Sciences Thesaurus took 0.6301572322845459s
Understandability | Number of label check for English Heritage Archaeological Sciences Thesaurus took 0.6945240497589111s
Understandability | URI regex check for English Heritage Archaeological Sciences Thesaurus took 0.9737458229064941s
Understandability | Vocabs check for English Heritage Archaeological Sciences Thesaurus took 0.40825772285461426s
Verifiability | Authors check for English Heritage Archaeological Sciences Thesaurus took 0.4602227210998535s
Verifiability | Publishers check for English Heritage Archaeological Sciences Thesaurus took 0.5127134323120117s
Performance | Throughput check for English Heritage Archaeological Sciences Thesaurus took 12.093199014663696s
Amount of data | Check the number of entities for English Heritage Archaeological Sciences Thesaurus took 8.392333984375e-05s
Verifiability | Contribs. check for English Heritage Archaeological Sciences Thesaurus took 0.41232895851135254s
Interlinking | sameAs chians check for English Heritage Archaeological Sciences Thesaurus took 0.43172311782836914s
Interlinking | skos check for English Heritage Archaeological Sciences Thesaurus took 0.46489596366882324s
Interlinking | skos check for English Heritage Archaeological Sciences Thesaurus took 0.466066837310791s
Timeliness | dataset update frequency check for English Heritage Archaeological Sciences Thesaurus took 0.40613889694213867s
Currency | Creation date check for English Heritage Archaeological Sciences Thesaurus took 0.8551979064941406s
Currency | Modification date check for English Heritage Archaeological Sciences Thesaurus took 0.8122973442077637s
Rep.Conc. | URIs length for English Heritage Archaeological Sciences Thesaurus took 0.7827589511871338s
Interoperability | New vocabularies check for English Heritage Archaeological Sciences Thesaurus took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Archaeological Sciences Thesaurus took 0.5505433082580566s
Accuracy | Check Functional Property for English Heritage Archaeological Sciences Thesaurus took 0.5019702911376953s
Accuracy | Check Inverse Functional Property for English Heritage Archaeological Sciences Thesaurus took 0.43951869010925293s
Consistency | Disjoint class check for English Heritage Archaeological Sciences Thesaurus took 0.5306799411773682s
Consistency | Check Ontology hijacking for English Heritage Archaeological Sciences Thesaurus took 0.6157107353210449s
Consistency | Check Invalid usage of undefined properties for English Heritage Archaeological Sciences Thesaurus took 1.7614738941192627s
Conciseness | Check Extensional conciseness for English Heritage Archaeological Sciences Thesaurus took 0.00014472007751464844s
Security | Sign check for English Heritage Archaeological Sciences Thesaurus took 0.4380064010620117s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.32275843620300293s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.017948627471923828s
Interlinking | Calculation of Degree of Connection for English Heritage Archaeological Sciences Thesaurus took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for English Heritage Archaeological Sciences Thesaurus took 0.0005135536193847656s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 3.218650817871094e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Archaeological Sciences Thesaurus took 2.9325485229492188e-05s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 9.775161743164062e-06s
INFO | --- Analysis for English Heritage Archaeological Sciences Thesaurus took 72.10126948356628s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 0.39809131622314453s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 9.5367431640625e-06s
Extra | Recovery of all triples for English Heritage Building Materials Thesaurus took 0.4393599033355713s
Performance | Total latancy measurement for English Heritage Building Materials Thesaurus took 2.190595865249634s
Amount of data | Number of triples check for English Heritage Building Materials Thesaurus took 1.5199217796325684s
Versatility | Languages check for English Heritage Building Materials Thesaurus took 0.2915780544281006s
Interpretability | Number of blank nodes check for English Heritage Building Materials Thesaurus took 0.7189459800720215s
Security | Check HTTPS for English Heritage Building Materials Thesaurus took 0.33493947982788086s
Interpretability | RDF structures check for English Heritage Building Materials Thesaurus took 0.34655165672302246s
Versatility | Serialization formats check for English Heritage Building Materials Thesaurus took 0.3861536979675293s
Availability | RDF dump link check for English Heritage Building Materials Thesaurus took 0.41025280952453613s
License | MR license check for English Heritage Building Materials Thesaurus took 0.5465803146362305s
License | HR license check for English Heritage Building Materials Thesaurus took 0.4174327850341797s
Amount of data | Number of property check for English Heritage Building Materials Thesaurus took 0.5613059997558594s
Understandability | Number of label check for English Heritage Building Materials Thesaurus took 0.7693881988525391s
Understandability | URI regex check for English Heritage Building Materials Thesaurus took 0.8290162086486816s
Understandability | Vocabs check for English Heritage Building Materials Thesaurus took 0.5982785224914551s
Verifiability | Authors check for English Heritage Building Materials Thesaurus took 0.4587130546569824s
Verifiability | Publishers check for English Heritage Building Materials Thesaurus took 0.42647504806518555s
Performance | Throughput check for English Heritage Building Materials Thesaurus took 13.183285474777222s
Amount of data | Check the number of entities for English Heritage Building Materials Thesaurus took 3.8623809814453125e-05s
Verifiability | Contribs. check for English Heritage Building Materials Thesaurus took 0.35054707527160645s
Interlinking | sameAs chians check for English Heritage Building Materials Thesaurus took 0.4025118350982666s
Interlinking | skos check for English Heritage Building Materials Thesaurus took 0.46154284477233887s
Interlinking | skos check for English Heritage Building Materials Thesaurus took 0.4450240135192871s
Timeliness | dataset update frequency check for English Heritage Building Materials Thesaurus took 0.42235755920410156s
Currency | Creation date check for English Heritage Building Materials Thesaurus took 0.9497721195220947s
Currency | Modification date check for English Heritage Building Materials Thesaurus took 0.8071658611297607s
Rep.Conc. | URIs length for English Heritage Building Materials Thesaurus took 0.7527589797973633s
Interoperability | New vocabularies check for English Heritage Building Materials Thesaurus took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Building Materials Thesaurus took 0.5093319416046143s
Accuracy | Check Functional Property for English Heritage Building Materials Thesaurus took 0.33208322525024414s
Accuracy | Check Inverse Functional Property for English Heritage Building Materials Thesaurus took 0.40219855308532715s
Consistency | Disjoint class check for English Heritage Building Materials Thesaurus took 0.4335753917694092s
Consistency | Check Ontology hijacking for English Heritage Building Materials Thesaurus took 0.490309476852417s
Consistency | Check Invalid usage of undefined properties for English Heritage Building Materials Thesaurus took 1.5400383472442627s
Conciseness | Check Extensional conciseness for English Heritage Building Materials Thesaurus took 0.00015401840209960938s
Security | Sign check for English Heritage Building Materials Thesaurus took 1.4945461750030518s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.38658809661865234s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.018831968307495117s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0005037784576416016s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 1.3828277587890625e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Building Materials Thesaurus took 9.5367431640625e-07s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 1.0728836059570312e-05s
INFO | --- Analysis for English Heritage Building Materials Thesaurus took 72.83755874633789s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 0.3435225486755371s
Availability | VoID file availability check for English Heritage Components Thesaurus took 5.9604644775390625e-06s
Extra | Recovery of all triples for English Heritage Components Thesaurus took 0.5724334716796875s
Performance | Total latancy measurement for English Heritage Components Thesaurus took 1.8338983058929443s
Amount of data | Number of triples check for English Heritage Components Thesaurus took 0.5801742076873779s
Versatility | Languages check for English Heritage Components Thesaurus took 0.32171082496643066s
Interpretability | Number of blank nodes check for English Heritage Components Thesaurus took 0.5424280166625977s
Security | Check HTTPS for English Heritage Components Thesaurus took 0.33133578300476074s
Interpretability | RDF structures check for English Heritage Components Thesaurus took 0.3791937828063965s
Versatility | Serialization formats check for English Heritage Components Thesaurus took 0.6043567657470703s
Availability | RDF dump link check for English Heritage Components Thesaurus took 0.3976161479949951s
License | MR license check for English Heritage Components Thesaurus took 0.5618369579315186s
License | HR license check for English Heritage Components Thesaurus took 0.5199353694915771s
Amount of data | Number of property check for English Heritage Components Thesaurus took 0.5869913101196289s
Understandability | Number of label check for English Heritage Components Thesaurus took 0.6213159561157227s
Understandability | URI regex check for English Heritage Components Thesaurus took 0.7985026836395264s
Understandability | Vocabs check for English Heritage Components Thesaurus took 0.38491129875183105s
Verifiability | Authors check for English Heritage Components Thesaurus took 0.4859304428100586s
Verifiability | Publishers check for English Heritage Components Thesaurus took 0.5665910243988037s
Performance | Throughput check for English Heritage Components Thesaurus took 12.149499416351318s
Amount of data | Check the number of entities for English Heritage Components Thesaurus took 0.000125885009765625s
Verifiability | Contribs. check for English Heritage Components Thesaurus took 0.48633623123168945s
Interlinking | sameAs chians check for English Heritage Components Thesaurus took 0.4129819869995117s
Interlinking | skos check for English Heritage Components Thesaurus took 0.481367826461792s
Interlinking | skos check for English Heritage Components Thesaurus took 0.417647123336792s
Timeliness | dataset update frequency check for English Heritage Components Thesaurus took 0.43965935707092285s
Currency | Creation date check for English Heritage Components Thesaurus took 0.805922269821167s
Currency | Modification date check for English Heritage Components Thesaurus took 0.8095755577087402s
Rep.Conc. | URIs length for English Heritage Components Thesaurus took 0.9316444396972656s
Interoperability | New vocabularies check for English Heritage Components Thesaurus took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Components Thesaurus took 0.5036916732788086s
Accuracy | Check Functional Property for English Heritage Components Thesaurus took 0.4278402328491211s
Accuracy | Check Inverse Functional Property for English Heritage Components Thesaurus took 0.44417810440063477s
Consistency | Disjoint class check for English Heritage Components Thesaurus took 0.46195387840270996s
Consistency | Check Ontology hijacking for English Heritage Components Thesaurus took 0.6001565456390381s
Consistency | Check Invalid usage of undefined properties for English Heritage Components Thesaurus took 1.5871880054473877s
Conciseness | Check Extensional conciseness for English Heritage Components Thesaurus took 0.0001494884490966797s
Security | Sign check for English Heritage Components Thesaurus took 0.523043155670166s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.30016279220581055s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.018954992294311523s
Interlinking | Calculation of Degree of Connection for English Heritage Components Thesaurus took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for English Heritage Components Thesaurus took 0.0005097389221191406s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 1.52587890625e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Components Thesaurus took 1.6689300537109375e-06s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 1.2159347534179688e-05s
INFO | --- Analysis for English Heritage Components Thesaurus took 67.63745260238647s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 0.5065181255340576s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 1.049041748046875e-05s
Extra | Recovery of all triples for English Heritage Event Types Thesaurus took 0.4064664840698242s
Performance | Total latancy measurement for English Heritage Event Types Thesaurus took 2.0941431522369385s
Amount of data | Number of triples check for English Heritage Event Types Thesaurus took 0.4629323482513428s
Versatility | Languages check for English Heritage Event Types Thesaurus took 0.2981433868408203s
Interpretability | Number of blank nodes check for English Heritage Event Types Thesaurus took 0.5542898178100586s
Security | Check HTTPS for English Heritage Event Types Thesaurus took 0.31783509254455566s
Interpretability | RDF structures check for English Heritage Event Types Thesaurus took 0.3351116180419922s
Versatility | Serialization formats check for English Heritage Event Types Thesaurus took 0.38889598846435547s
Availability | RDF dump link check for English Heritage Event Types Thesaurus took 0.5391514301300049s
License | MR license check for English Heritage Event Types Thesaurus took 0.6012721061706543s
License | HR license check for English Heritage Event Types Thesaurus took 0.4988393783569336s
Amount of data | Number of property check for English Heritage Event Types Thesaurus took 0.5497677326202393s
Understandability | Number of label check for English Heritage Event Types Thesaurus took 0.8108513355255127s
Understandability | URI regex check for English Heritage Event Types Thesaurus took 0.9811270236968994s
Understandability | Vocabs check for English Heritage Event Types Thesaurus took 0.47147345542907715s
Verifiability | Authors check for English Heritage Event Types Thesaurus took 0.41809725761413574s
Verifiability | Publishers check for English Heritage Event Types Thesaurus took 0.5191974639892578s
Performance | Throughput check for English Heritage Event Types Thesaurus took 12.39071273803711s
Amount of data | Check the number of entities for English Heritage Event Types Thesaurus took 8.225440979003906e-05s
Verifiability | Contribs. check for English Heritage Event Types Thesaurus took 0.4866824150085449s
Interlinking | sameAs chians check for English Heritage Event Types Thesaurus took 0.45192861557006836s
Interlinking | skos check for English Heritage Event Types Thesaurus took 0.5774731636047363s
Interlinking | skos check for English Heritage Event Types Thesaurus took 0.5826642513275146s
Timeliness | dataset update frequency check for English Heritage Event Types Thesaurus took 0.5778210163116455s
Currency | Creation date check for English Heritage Event Types Thesaurus took 0.958831787109375s
Currency | Modification date check for English Heritage Event Types Thesaurus took 1.038830041885376s
Rep.Conc. | URIs length for English Heritage Event Types Thesaurus took 0.8344213962554932s
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.4677622318267822s
Accuracy | Check Functional Property for English Heritage Event Types Thesaurus took 0.4096658229827881s
Accuracy | Check Inverse Functional Property for English Heritage Event Types Thesaurus took 0.39646029472351074s
Consistency | Disjoint class check for English Heritage Event Types Thesaurus took 0.3873016834259033s
Consistency | Check Ontology hijacking for English Heritage Event Types Thesaurus took 0.3983123302459717s
Consistency | Check Invalid usage of undefined properties for English Heritage Event Types Thesaurus took 1.5815565586090088s
Conciseness | Check Extensional conciseness for English Heritage Event Types Thesaurus took 0.0001518726348876953s
Security | Sign check for English Heritage Event Types Thesaurus took 0.40702247619628906s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.37421226501464844s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.018511056900024414s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.000530242919921875s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 2.2411346435546875e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Event Types Thesaurus took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 1.1444091796875e-05s
INFO | --- Analysis for English Heritage Event Types Thesaurus took 67.00319409370422s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 8.487701416015625e-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.5928316116333008s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.019441604614257812s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.0005168914794921875s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 1.2874603271484375e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 1.0967254638671875e-05s
INFO | --- Analysis for English Heritage Evidence Thesaurus took 4.818716764450073s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 0.35652828216552734s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 9.775161743164062e-06s
Extra | Recovery of all triples for English Heritage Maritime Craft Thesaurus took 0.41678595542907715s
Performance | Total latancy measurement for English Heritage Maritime Craft Thesaurus took 2.002574920654297s
Amount of data | Number of triples check for English Heritage Maritime Craft Thesaurus took 0.5190286636352539s
Versatility | Languages check for English Heritage Maritime Craft Thesaurus took 0.2808098793029785s
Interpretability | Number of blank nodes check for English Heritage Maritime Craft Thesaurus took 0.5076320171356201s
Security | Check HTTPS for English Heritage Maritime Craft Thesaurus took 0.27092552185058594s
Interpretability | RDF structures check for English Heritage Maritime Craft Thesaurus took 0.402604341506958s
Versatility | Serialization formats check for English Heritage Maritime Craft Thesaurus took 0.45127272605895996s
Availability | RDF dump link check for English Heritage Maritime Craft Thesaurus took 0.3933720588684082s
License | MR license check for English Heritage Maritime Craft Thesaurus took 0.5109779834747314s
License | HR license check for English Heritage Maritime Craft Thesaurus took 0.43229103088378906s
Amount of data | Number of property check for English Heritage Maritime Craft Thesaurus took 0.48806118965148926s
Understandability | Number of label check for English Heritage Maritime Craft Thesaurus took 0.5540428161621094s
Understandability | URI regex check for English Heritage Maritime Craft Thesaurus took 0.7893514633178711s
Understandability | Vocabs check for English Heritage Maritime Craft Thesaurus took 0.385040283203125s
Verifiability | Authors check for English Heritage Maritime Craft Thesaurus took 0.4444267749786377s
Verifiability | Publishers check for English Heritage Maritime Craft Thesaurus took 0.46222972869873047s
Performance | Throughput check for English Heritage Maritime Craft Thesaurus took 12.377819538116455s
Amount of data | Check the number of entities for English Heritage Maritime Craft Thesaurus took 8.487701416015625e-05s
Verifiability | Contribs. check for English Heritage Maritime Craft Thesaurus took 0.35326147079467773s
Interlinking | sameAs chians check for English Heritage Maritime Craft Thesaurus took 0.4359395503997803s
Interlinking | skos check for English Heritage Maritime Craft Thesaurus took 0.49856066703796387s
Interlinking | skos check for English Heritage Maritime Craft Thesaurus took 0.418834924697876s
Timeliness | dataset update frequency check for English Heritage Maritime Craft Thesaurus took 0.5028417110443115s
Currency | Creation date check for English Heritage Maritime Craft Thesaurus took 0.9273686408996582s
Currency | Modification date check for English Heritage Maritime Craft Thesaurus took 0.7993755340576172s
Rep.Conc. | URIs length for English Heritage Maritime Craft Thesaurus took 0.8610353469848633s
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.39772510528564453s
Accuracy | Check Functional Property for English Heritage Maritime Craft Thesaurus took 0.3841264247894287s
Accuracy | Check Inverse Functional Property for English Heritage Maritime Craft Thesaurus took 0.41048765182495117s
Consistency | Disjoint class check for English Heritage Maritime Craft Thesaurus took 0.37574052810668945s
Consistency | Check Ontology hijacking for English Heritage Maritime Craft Thesaurus took 0.46992015838623047s
Consistency | Check Invalid usage of undefined properties for English Heritage Maritime Craft Thesaurus took 1.5881373882293701s
Conciseness | Check Extensional conciseness for English Heritage Maritime Craft Thesaurus took 0.0001761913299560547s
Security | Sign check for English Heritage Maritime Craft Thesaurus took 0.45177483558654785s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.34861326217651367s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.018303394317626953s
Interlinking | Calculation of Degree of Connection for English Heritage Maritime Craft Thesaurus took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for English Heritage Maritime Craft Thesaurus took 0.0005161762237548828s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 2.0742416381835938e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Maritime Craft Thesaurus took 1.6689300537109375e-06s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 3.0994415283203125e-05s
INFO | --- Analysis for English Heritage Maritime Craft Thesaurus took 65.85210633277893s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 0.4192790985107422s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 1.1205673217773438e-05s
Extra | Recovery of all triples for English Heritage Monument Types Thesaurus took 0.4844372272491455s
Performance | Total latancy measurement for English Heritage Monument Types Thesaurus took 3.014465093612671s
Amount of data | Number of triples check for English Heritage Monument Types Thesaurus took 1.5137548446655273s
Versatility | Languages check for English Heritage Monument Types Thesaurus took 0.4151444435119629s
Interpretability | Number of blank nodes check for English Heritage Monument Types Thesaurus took 1.302870273590088s
Security | Check HTTPS for English Heritage Monument Types Thesaurus took 0.49271059036254883s
Interpretability | RDF structures check for English Heritage Monument Types Thesaurus took 0.40860700607299805s
Versatility | Serialization formats check for English Heritage Monument Types Thesaurus took 0.5879781246185303s
Availability | RDF dump link check for English Heritage Monument Types Thesaurus took 0.6813502311706543s
License | MR license check for English Heritage Monument Types Thesaurus took 0.8830862045288086s
License | HR license check for English Heritage Monument Types Thesaurus took 0.5017974376678467s
Amount of data | Number of property check for English Heritage Monument Types Thesaurus took 0.6185717582702637s
Understandability | Number of label check for English Heritage Monument Types Thesaurus took 0.812035083770752s
Understandability | URI regex check for English Heritage Monument Types Thesaurus took 1.0156638622283936s
Understandability | Vocabs check for English Heritage Monument Types Thesaurus took 0.46621227264404297s
Verifiability | Authors check for English Heritage Monument Types Thesaurus took 0.5984828472137451s
Verifiability | Publishers check for English Heritage Monument Types Thesaurus took 0.7246882915496826s
Performance | Throughput check for English Heritage Monument Types Thesaurus took 13.347001314163208s
Amount of data | Check the number of entities for English Heritage Monument Types Thesaurus took 8.20159912109375e-05s
Verifiability | Contribs. check for English Heritage Monument Types Thesaurus took 4.789783954620361s
Interlinking | sameAs chians check for English Heritage Monument Types Thesaurus took 1.1380727291107178s
Interlinking | skos check for English Heritage Monument Types Thesaurus took 2.775343894958496s
Interlinking | skos check for English Heritage Monument Types Thesaurus took 1.235893726348877s
Timeliness | dataset update frequency check for English Heritage Monument Types Thesaurus took 3.1126554012298584s
Currency | Creation date check for English Heritage Monument Types Thesaurus took 1.1111233234405518s
Currency | Modification date check for English Heritage Monument Types Thesaurus took 1.137712001800537s
Rep.Conc. | URIs length for English Heritage Monument Types Thesaurus took 1.352945327758789s
Interoperability | New vocabularies check for English Heritage Monument Types Thesaurus took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Monument Types Thesaurus took 0.5474162101745605s
Accuracy | Check Functional Property for English Heritage Monument Types Thesaurus took 0.5461552143096924s
Accuracy | Check Inverse Functional Property for English Heritage Monument Types Thesaurus took 0.41846656799316406s
Consistency | Disjoint class check for English Heritage Monument Types Thesaurus took 0.4183518886566162s
Consistency | Check Ontology hijacking for English Heritage Monument Types Thesaurus took 0.4576864242553711s
Consistency | Check Invalid usage of undefined properties for English Heritage Monument Types Thesaurus took 1.8448622226715088s
Conciseness | Check Extensional conciseness for English Heritage Monument Types Thesaurus took 0.00015234947204589844s
Security | Sign check for English Heritage Monument Types Thesaurus took 0.505474328994751s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 1.3928234577178955s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.01805591583251953s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0005133152008056641s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 1.3113021850585938e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Monument Types Thesaurus took 9.5367431640625e-07s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for English Heritage Monument Types Thesaurus took 98.27053546905518s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.4884030818939209s
Availability | VoID file availability check for English Heritage Periods List took 1.6259045600891113s
Extra | Recovery of all triples for English Heritage Periods List took 0.5174400806427002s
Performance | Total latancy measurement for English Heritage Periods List took 2.0970683097839355s
Amount of data | Number of triples check for English Heritage Periods List took 0.7010056972503662s
Versatility | Languages check for English Heritage Periods List took 0.3107619285583496s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.6608264446258545s
Security | Check HTTPS for English Heritage Periods List took 0.29843735694885254s
Interpretability | RDF structures check for English Heritage Periods List took 0.3518092632293701s
Versatility | Serialization formats check for English Heritage Periods List took 0.5137836933135986s
Availability | RDF dump link check for English Heritage Periods List took 0.48648881912231445s
License | MR license check for English Heritage Periods List took 0.7647647857666016s
License | HR license check for English Heritage Periods List took 0.46386241912841797s
Amount of data | Number of property check for English Heritage Periods List took 0.7890939712524414s
Understandability | Number of label check for English Heritage Periods List took 0.7436387538909912s
Understandability | URI regex check for English Heritage Periods List took 0.871138334274292s
Understandability | Vocabs check for English Heritage Periods List took 0.43529582023620605s
Verifiability | Authors check for English Heritage Periods List took 0.4965190887451172s
Verifiability | Publishers check for English Heritage Periods List took 0.6250705718994141s
Performance | Throughput check for English Heritage Periods List took 13.086869716644287s
Amount of data | Check the number of entities for English Heritage Periods List took 8.702278137207031e-05s
Verifiability | Contribs. check for English Heritage Periods List took 1.42067551612854s
Interlinking | sameAs chians check for English Heritage Periods List took 0.4880523681640625s
Interlinking | skos check for English Heritage Periods List took 0.6531989574432373s
Interlinking | skos check for English Heritage Periods List took 0.4831395149230957s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.4935648441314697s
Currency | Creation date check for English Heritage Periods List took 0.9758920669555664s
Currency | Modification date check for English Heritage Periods List took 0.9932913780212402s
Rep.Conc. | URIs length for English Heritage Periods List took 1.1599440574645996s
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.6637566089630127s
Accuracy | Check Functional Property for English Heritage Periods List took 0.48511672019958496s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.4737863540649414s
Consistency | Disjoint class check for English Heritage Periods List took 0.7279238700866699s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.55153489112854s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.6366183757781982s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.0001773834228515625s
Security | Sign check for English Heritage Periods List took 0.5103273391723633s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 2.05157732963562s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.019062519073486328s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0005095005035400391s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.314018249511719e-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.3589859008789062e-05s
INFO | --- Analysis for English Heritage Periods List took 72.86436653137207s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.45081090927124023s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.4945950508117676s
Extra | Recovery of all triples for English Index of Multiple Deprivation Ranking 2010 took 1.2268612384796143s
Performance | Total latancy measurement for English Index of Multiple Deprivation Ranking 2010 took 1.0655057430267334s
Amount of data | Number of triples check for English Index of Multiple Deprivation Ranking 2010 took 0.23142528533935547s
Interoperability | New terms check for English Index of Multiple Deprivation Ranking 2010 took 1.5364866256713867s
Versatility | Languages check for English Index of Multiple Deprivation Ranking 2010 took 0.44416308403015137s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Ranking 2010 took 0.26124024391174316s
Security | Check HTTPS for English Index of Multiple Deprivation Ranking 2010 took 0.16929078102111816s
Interpretability | RDF structures check for English Index of Multiple Deprivation Ranking 2010 took 0.2997901439666748s
Versatility | Serialization formats check for English Index of Multiple Deprivation Ranking 2010 took 0.1602468490600586s
Availability | RDF dump link check for English Index of Multiple Deprivation Ranking 2010 took 59.24865102767944s
License | MR license check for English Index of Multiple Deprivation Ranking 2010 took 0.3360140323638916s
License | HR license check for English Index of Multiple Deprivation Ranking 2010 took 30.19959783554077s
Amount of data | Number of property check for English Index of Multiple Deprivation Ranking 2010 took 0.1771070957183838s
Understandability | Number of label check for English Index of Multiple Deprivation Ranking 2010 took 0.26349353790283203s
Understandability | URI regex check for English Index of Multiple Deprivation Ranking 2010 took 0.3950345516204834s
Understandability | Vocabs check for English Index of Multiple Deprivation Ranking 2010 took 0.17851018905639648s
Verifiability | Authors check for English Index of Multiple Deprivation Ranking 2010 took 0.2853562831878662s
Verifiability | Publishers check for English Index of Multiple Deprivation Ranking 2010 took 0.33939456939697266s
Performance | Throughput check for English Index of Multiple Deprivation Ranking 2010 took 12.156703233718872s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Ranking 2010 took 8.726119995117188e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Ranking 2010 took 0.2374885082244873s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Ranking 2010 took 0.3036520481109619s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.25011277198791504s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.13663792610168457s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Ranking 2010 took 0.14051198959350586s
Currency | Creation date check for English Index of Multiple Deprivation Ranking 2010 took 0.2284078598022461s
Currency | Modification date check for English Index of Multiple Deprivation Ranking 2010 took 0.3316690921783447s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Ranking 2010 took 1.4043927192687988s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Ranking 2010 took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Ranking 2010 took 0.28317856788635254s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.21179485321044922s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.14824748039245605s
Consistency | Disjoint class check for English Index of Multiple Deprivation Ranking 2010 took 0.2937967777252197s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Ranking 2010 took 0.7023694515228271s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Ranking 2010 took 0.9906411170959473s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Ranking 2010 took 1.415220022201538s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.0001952648162841797s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.3369941711425781s
Security | Sign check for English Index of Multiple Deprivation Ranking 2010 took 0.21986985206604004s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.38918304443359375s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.01893925666809082s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0005326271057128906s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 4.410743713378906e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Ranking 2010 took 1.430511474609375e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 9.059906005859375e-06s
INFO | --- Analysis for English Index of Multiple Deprivation Ranking 2010 took 902.2317078113556s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.1468183994293213s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.7044460773468018s
Extra | Recovery of all triples for English Index of Multiple Deprivation Score 2010 took 0.9519577026367188s
Performance | Total latancy measurement for English Index of Multiple Deprivation Score 2010 took 1.2278401851654053s
Amount of data | Number of triples check for English Index of Multiple Deprivation Score 2010 took 0.21209931373596191s
Interoperability | New terms check for English Index of Multiple Deprivation Score 2010 took 2.0212414264678955s
Versatility | Languages check for English Index of Multiple Deprivation Score 2010 took 0.40305399894714355s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Score 2010 took 0.2357184886932373s
Security | Check HTTPS for English Index of Multiple Deprivation Score 2010 took 0.08922290802001953s
Interpretability | RDF structures check for English Index of Multiple Deprivation Score 2010 took 0.2472670078277588s
Versatility | Serialization formats check for English Index of Multiple Deprivation Score 2010 took 0.20431828498840332s
Availability | RDF dump link check for English Index of Multiple Deprivation Score 2010 took 56.51523399353027s
License | MR license check for English Index of Multiple Deprivation Score 2010 took 0.1618175506591797s
License | HR license check for English Index of Multiple Deprivation Score 2010 took 30.300143241882324s
Amount of data | Number of property check for English Index of Multiple Deprivation Score 2010 took 0.4533805847167969s
Understandability | Number of label check for English Index of Multiple Deprivation Score 2010 took 0.2392561435699463s
Understandability | URI regex check for English Index of Multiple Deprivation Score 2010 took 0.41481947898864746s
Understandability | Vocabs check for English Index of Multiple Deprivation Score 2010 took 0.13506841659545898s
Verifiability | Authors check for English Index of Multiple Deprivation Score 2010 took 0.22152948379516602s
Verifiability | Publishers check for English Index of Multiple Deprivation Score 2010 took 0.14443159103393555s
Performance | Throughput check for English Index of Multiple Deprivation Score 2010 took 11.067241191864014s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Score 2010 took 8.940696716308594e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Score 2010 took 0.15010356903076172s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Score 2010 took 0.23836970329284668s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.15503263473510742s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.13960838317871094s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Score 2010 took 0.208327054977417s
Currency | Creation date check for English Index of Multiple Deprivation Score 2010 took 0.14085650444030762s
Currency | Modification date check for English Index of Multiple Deprivation Score 2010 took 0.46207547187805176s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Score 2010 took 1.175654649734497s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Score 2010 took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Score 2010 took 0.12241578102111816s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Score 2010 took 0.15573620796203613s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Score 2010 took 0.23909592628479004s
Consistency | Disjoint class check for English Index of Multiple Deprivation Score 2010 took 0.28534984588623047s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Score 2010 took 0.41466593742370605s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Score 2010 took 0.8815162181854248s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Score 2010 took 1.403759241104126s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.00014328956604003906s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.7583160400390625s
Security | Sign check for English Index of Multiple Deprivation Score 2010 took 0.1598985195159912s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.6045737266540527s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.018374204635620117s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0005359649658203125s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Score 2010 took 1.430511474609375e-06s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 4.76837158203125e-06s
INFO | --- Analysis for English Index of Multiple Deprivation Score 2010 took 677.1077165603638s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 0.16589951515197754s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.5903873443603516s
Extra | Recovery of all triples for English Indices of Multiple Deprivation took 0.8989782333374023s
Performance | Total latancy measurement for English Indices of Multiple Deprivation took 0.9105241298675537s
Amount of data | Number of triples check for English Indices of Multiple Deprivation took 0.5050623416900635s
Interoperability | New terms check for English Indices of Multiple Deprivation took 1.3600449562072754s
Versatility | Languages check for English Indices of Multiple Deprivation took 0.37082719802856445s
Interpretability | Number of blank nodes check for English Indices of Multiple Deprivation took 0.23602867126464844s
Security | Check HTTPS for English Indices of Multiple Deprivation took 0.11168742179870605s
Interpretability | RDF structures check for English Indices of Multiple Deprivation took 0.2885630130767822s
Versatility | Serialization formats check for English Indices of Multiple Deprivation took 0.19597291946411133s
Availability | RDF dump link check for English Indices of Multiple Deprivation took 52.62303972244263s
License | MR license check for English Indices of Multiple Deprivation took 0.5408308506011963s
License | HR license check for English Indices of Multiple Deprivation took 30.20249915122986s
Amount of data | Number of property check for English Indices of Multiple Deprivation took 0.21873068809509277s
Understandability | Number of label check for English Indices of Multiple Deprivation took 0.21411609649658203s
Understandability | URI regex check for English Indices of Multiple Deprivation took 0.3986968994140625s
Understandability | Vocabs check for English Indices of Multiple Deprivation took 0.1608588695526123s
Verifiability | Authors check for English Indices of Multiple Deprivation took 0.18844056129455566s
Verifiability | Publishers check for English Indices of Multiple Deprivation took 0.21606659889221191s
Performance | Throughput check for English Indices of Multiple Deprivation took 10.87072205543518s
Amount of data | Check the number of entities for English Indices of Multiple Deprivation took 8.58306884765625e-05s
Verifiability | Contribs. check for English Indices of Multiple Deprivation took 0.2057514190673828s
Interlinking | sameAs chians check for English Indices of Multiple Deprivation took 0.15283513069152832s
Interlinking | skos check for English Indices of Multiple Deprivation took 0.16163349151611328s
Interlinking | skos check for English Indices of Multiple Deprivation took 0.14262104034423828s
Timeliness | dataset update frequency check for English Indices of Multiple Deprivation took 0.2121574878692627s
Currency | Creation date check for English Indices of Multiple Deprivation took 0.16413521766662598s
Currency | Modification date check for English Indices of Multiple Deprivation took 0.36593151092529297s
Rep.Conc. | URIs length for English Indices of Multiple Deprivation took 1.0737273693084717s
Interoperability | New vocabularies check for English Indices of Multiple Deprivation took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for English Indices of Multiple Deprivation took 0.15250682830810547s
Accuracy | Check Functional Property for English Indices of Multiple Deprivation took 0.14707708358764648s
Accuracy | Check Inverse Functional Property for English Indices of Multiple Deprivation took 0.21568965911865234s
Consistency | Disjoint class check for English Indices of Multiple Deprivation took 0.21122074127197266s
Consistency | Check Misplaced properties for English Indices of Multiple Deprivation took 0.5086967945098877s
Consistency | Check Ontology hijacking for English Indices of Multiple Deprivation took 0.8888435363769531s
Consistency | Check Invalid usage of undefined properties for English Indices of Multiple Deprivation took 1.3590922355651855s
Conciseness | Check Extensional conciseness for English Indices of Multiple Deprivation took 0.00015020370483398438s
Conciseness | Check Intensional conciseness for English Indices of Multiple Deprivation took 0.22295498847961426s
Security | Sign check for English Indices of Multiple Deprivation took 0.18919658660888672s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 0.3773658275604248s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.019753217697143555s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.0005316734313964844s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 1.811981201171875e-05s
Interoperability | Check the re-using of existing vocabs for English Indices of Multiple Deprivation took 1.430511474609375e-06s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 1.0251998901367188e-05s
INFO | --- Analysis for English Indices of Multiple Deprivation took 661.9156286716461s
Availability | SPARQL endpoint availability check for English WordNet took 8.511543273925781e-05s
Availability | VoID file availability check for English WordNet took 0.5002095699310303s
Completeness | Calculation of interlinking completeness for English WordNet took 0.3485581874847412s
Reputation | Calculation of the PageRank for English WordNet took 0.01861429214477539s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.7670135498046875e-05s
Believability | Calculation of trust value for English WordNet took 1.1205673217773438e-05s
INFO | --- Analysis for English WordNet took 4.159278154373169s
Availability | SPARQL endpoint availability check for English Heritage Places took 1.237093448638916s
Availability | VoID file availability check for English Heritage Places took 0.5709810256958008s
Completeness | Calculation of interlinking completeness for English Heritage Places took 0.3127596378326416s
Reputation | Calculation of the PageRank for English Heritage Places took 0.018146753311157227s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 1.33514404296875e-05s
Believability | Calculation of trust value for English Heritage Places took 1.0728836059570312e-05s
INFO | --- Analysis for English Heritage Places took 5.955401182174683s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.05531787872314453s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.008693456649780273s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.3271219730377197s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.01817011833190918s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0005176067352294922s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 8.440017700195312e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 1.1205673217773438e-05s
INFO | --- Analysis for Enipedia - Energy Industry Data took 2.407064914703369s
Availability | SPARQL endpoint availability check for Entrez Gene took 8.749961853027344e-05s
Availability | VoID file availability check for Entrez Gene took 2.0631754398345947s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.6137945652008057s
Reputation | Calculation of the PageRank for Entrez Gene took 0.018312692642211914s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0005524158477783203s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.695487976074219e-05s
Believability | Calculation of trust value for Entrez Gene took 7.62939453125e-06s
INFO | --- Analysis for Entrez Gene took 29.39669132232666s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 4.2438507080078125e-05s
Availability | VoID file availability check for Entrez Gene Extract took 1.5654516220092773s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 0.3435685634613037s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.01811957359313965s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0005478858947753906s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 1.1444091796875e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 6.4373016357421875e-06s
INFO | --- Analysis for Entrez Gene Extract took 14.919670343399048s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 0.23524975776672363s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.18782567977905273s
Extra | Recovery of all triples for Environment Agency Bathing Water Quality took 19.647651195526123s
Performance | Total latancy measurement for Environment Agency Bathing Water Quality took 0.6705279350280762s
Amount of data | Number of triples check for Environment Agency Bathing Water Quality took 13.806174755096436s
Interoperability | New terms check for Environment Agency Bathing Water Quality took 2.884830951690674s
Versatility | Languages check for Environment Agency Bathing Water Quality took 46.954461336135864s
Interpretability | Number of blank nodes check for Environment Agency Bathing Water Quality took 11.238184928894043s
Security | Check HTTPS for Environment Agency Bathing Water Quality took 0.2901632785797119s
Interpretability | RDF structures check for Environment Agency Bathing Water Quality took 0.16034913063049316s
Versatility | Serialization formats check for Environment Agency Bathing Water Quality took 0.16997003555297852s
Availability | RDF dump link check for Environment Agency Bathing Water Quality took 4900.817742586136s
License | MR license check for Environment Agency Bathing Water Quality took 0.17917799949645996s
License | HR license check for Environment Agency Bathing Water Quality took 40.20117497444153s
Amount of data | Number of property check for Environment Agency Bathing Water Quality took 0.16925883293151855s
Understandability | Number of label check for Environment Agency Bathing Water Quality took 2.0667734146118164s
Understandability | URI regex check for Environment Agency Bathing Water Quality took 0.37439584732055664s
Understandability | Vocabs check for Environment Agency Bathing Water Quality took 0.29692578315734863s
Verifiability | Authors check for Environment Agency Bathing Water Quality took 0.11119747161865234s
Verifiability | Publishers check for Environment Agency Bathing Water Quality took 0.21475958824157715s
Performance | Throughput check for Environment Agency Bathing Water Quality took 10.746854782104492s
Amount of data | Check the number of entities for Environment Agency Bathing Water Quality took 27.223511695861816s
Verifiability | Contribs. check for Environment Agency Bathing Water Quality took 0.1712801456451416s
Interlinking | sameAs chians check for Environment Agency Bathing Water Quality took 0.20078086853027344s
Interlinking | skos check for Environment Agency Bathing Water Quality took 0.17368364334106445s
Interlinking | skos check for Environment Agency Bathing Water Quality took 0.1625349521636963s
Timeliness | dataset update frequency check for Environment Agency Bathing Water Quality took 0.15505433082580566s
Currency | Creation date check for Environment Agency Bathing Water Quality took 1.6078624725341797s
Currency | Modification date check for Environment Agency Bathing Water Quality took 0.2952268123626709s
Rep.Conc. | URIs length for Environment Agency Bathing Water Quality took 105.7883996963501s
Interoperability | New vocabularies check for Environment Agency Bathing Water Quality took 34.06544089317322s
Consistency | Deprecated classes/propertiers check for Environment Agency Bathing Water Quality took 0.1882319450378418s
Accuracy | Check Functional Property for Environment Agency Bathing Water Quality took 0.1546039581298828s
Accuracy | Check Inverse Functional Property for Environment Agency Bathing Water Quality took 0.14672040939331055s
Accuracy | Check Empty annotation labels for Environment Agency Bathing Water Quality took 14.79460620880127s
Accuracy | Check White space in annotation for Environment Agency Bathing Water Quality took 2.276252031326294s
Accuracy | Check Datatype consistency for Environment Agency Bathing Water Quality took 5.016374588012695s
Consistency | Disjoint class check for Environment Agency Bathing Water Quality took 0.1572716236114502s
Consistency | Check Misplaced properties for Environment Agency Bathing Water Quality took 27.756147146224976s
Consistency | Check Ontology hijacking for Environment Agency Bathing Water Quality took 24.957874298095703s
Consistency | Check Invalid usage of undefined classes for Environment Agency Bathing Water Quality took 1.3515870571136475s
Consistency | Check Invalid usage of undefined properties for Environment Agency Bathing Water Quality took 20.646066427230835s
Conciseness | Check Extensional conciseness for Environment Agency Bathing Water Quality took 3.041268825531006s
Conciseness | Check Intensional conciseness for Environment Agency Bathing Water Quality took 0.17154335975646973s
Security | Sign check for Environment Agency Bathing Water Quality took 0.11685991287231445s
Availability | Check URIs Dereferenciability for Environment Agency Bathing Water Quality took 1.4993617534637451s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.8693974018096924s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.018135786056518555s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0005252361297607422s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.0067901611328125e-05s
Interoperability | Check the re-using of existing vocabs for Environment Agency Bathing Water Quality took 33.260289907455444s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 8.344650268554688e-06s
INFO | --- Analysis for Environment Agency Bathing Water Quality took 5967.254870176315s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.1940140724182129s
Availability | VoID file availability check for environment.data.gov.uk took 0.3158533573150635s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.34627556800842285s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.018280029296875s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0005459785461425781s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.935264587402344e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 9.775161743164062e-06s
INFO | --- Analysis for environment.data.gov.uk took 5.054583549499512s
Availability | SPARQL endpoint availability check for EARTh took 271.3815088272095s
Availability | VoID file availability check for EARTh took 1.482356309890747s
Completeness | Calculation of interlinking completeness for EARTh took 0.45929646492004395s
Reputation | Calculation of the PageRank for EARTh took 0.01886272430419922s
Interlinking | Calculation of Degree of Connection for EARTh took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0005471706390380859s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.0001049041748046875s
Interoperability | Check the re-using of existing vocabs for EARTh took 1.9848246574401855s
Believability | Calculation of trust value for EARTh took 1.1205673217773438e-05s
INFO | --- Analysis for EARTh took 426.67386293411255s
Availability | SPARQL endpoint availability check for Micka (EO metadata) took 7.2479248046875e-05s
Availability | VoID file availability check for Micka (EO metadata) took 3.5762786865234375e-06s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) took 0.3081018924713135s
Reputation | Calculation of the PageRank for Micka (EO metadata) took 0.01822662353515625s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) took 0.0005309581756591797s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) took 1.2159347534179688e-05s
Believability | Calculation of trust value for Micka (EO metadata) took 1.239776611328125e-05s
INFO | --- Analysis for Micka (EO metadata) took 2.5066399574279785s
Availability | SPARQL endpoint availability check for EPA-CDR took 8.7738037109375e-05s
Availability | VoID file availability check for EPA-CDR took 1.1566941738128662s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.4729485511779785s
Reputation | Calculation of the PageRank for EPA-CDR took 0.018033504486083984s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0005216598510742188s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.5762786865234375e-05s
Believability | Calculation of trust value for EPA-CDR took 7.867813110351562e-06s
INFO | --- Analysis for EPA-CDR took 7.565681457519531s
Availability | SPARQL endpoint availability check for EPA-FRS took 8.511543273925781e-05s
Availability | VoID file availability check for EPA-FRS took 0.9865028858184814s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.33620762825012207s
Reputation | Calculation of the PageRank for EPA-FRS took 0.01800370216369629s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0005638599395751953s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.2479248046875e-05s
Believability | Calculation of trust value for EPA-FRS took 9.059906005859375e-06s
INFO | --- Analysis for EPA-FRS took 6.36208701133728s
Availability | SPARQL endpoint availability check for EPA-RCRA took 8.225440979003906e-05s
Availability | VoID file availability check for EPA-RCRA took 0.998568058013916s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.35129666328430176s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.01801323890686035s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0005366802215576172s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.361701965332031e-05s
Believability | Calculation of trust value for EPA-RCRA took 5.245208740234375e-06s
INFO | --- Analysis for EPA-RCRA took 6.437795162200928s
Availability | SPARQL endpoint availability check for EPA-SRS took 7.724761962890625e-05s
Availability | VoID file availability check for EPA-SRS took 1.030501365661621s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.3167915344238281s
Reputation | Calculation of the PageRank for EPA-SRS took 0.017922639846801758s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0005254745483398438s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.43865966796875e-05s
Believability | Calculation of trust value for EPA-SRS took 7.867813110351562e-06s
INFO | --- Analysis for EPA-SRS took 6.333218812942505s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.363059997558594e-05s
Availability | VoID file availability check for EPA-TRI took 0.9372739791870117s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.31795382499694824s
Reputation | Calculation of the PageRank for EPA-TRI took 0.017920494079589844s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for EPA-TRI took 0.000522613525390625s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.1948089599609375e-05s
Believability | Calculation of trust value for EPA-TRI took 5.245208740234375e-06s
INFO | --- Analysis for EPA-TRI took 7.211580276489258s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 2.6805288791656494s
Availability | VoID file availability check for European Patent Office (EPO) took 4.942782163619995s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 0.32128167152404785s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.018299341201782227s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.0005350112915039062s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 7.534027099609375e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 6.198883056640625e-06s
INFO | --- Analysis for European Patent Office (EPO) took 23.23438811302185s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.05995750427246094s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 5.0067901611328125e-06s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.30674266815185547s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.01818084716796875s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0005729198455810547s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.0001361370086669922s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for ePrints Harvest (RKBExplorer) took 1.8424906730651855s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.5543522834777832s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.008085489273071289s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.3898026943206787s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.018095016479492188s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0005807876586914062s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.392333984375e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 1.2159347534179688e-05s
INFO | --- Analysis for European Pollutant Release and Transfer Register (E-PRTR) took 3.5635271072387695s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.35233187675476074s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.07827973365783691s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.30561184883117676s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.018006086349487305s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0005335807800292969s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 1.2636184692382812e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 7.62939453125e-06s
INFO | --- Analysis for List of prices of medicinal products marketed in Kingdom of Spain took 3.197112560272217s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 8.654594421386719e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.6420066356658936s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.31943416595458984s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.018085002899169922s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0005228519439697266s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 9.512901306152344e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 8.58306884765625e-06s
INFO | --- Analysis for ESD Standards: Controlled lists for the UK public sector took 5.174020290374756s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 7.557868957519531e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.8153908252716064s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.31334400177001953s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.017992019653320312s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0005774497985839844s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.534027099609375e-05s
Believability | Calculation of trust value for ESD-Toolkit took 7.62939453125e-06s
INFO | --- Analysis for ESD-Toolkit took 4.016136646270752s
Availability | SPARQL endpoint availability check for Dataset Esis took 8.511543273925781e-05s
Availability | VoID file availability check for Dataset Esis took 0.16804838180541992s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.5436468124389648s
Reputation | Calculation of the PageRank for Dataset Esis took 0.018210411071777344s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0005347728729248047s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 1.1920928955078125e-05s
Believability | Calculation of trust value for Dataset Esis took 9.298324584960938e-06s
INFO | --- Analysis for Dataset Esis took 5.080756187438965s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 2.3170394897460938s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 5.148272752761841s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.28010058403015137s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.01808452606201172s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.510185241699219e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 1.3589859008789062e-05s
INFO | --- Analysis for EU Agencies and decentralized bodies (Agencies) took 16.40040683746338s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 8.225440979003906e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.10148119926452637s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.3376474380493164s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.017872095108032227s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0005626678466796875s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.1920928955078125e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.1920928955078125e-05s
INFO | --- Analysis for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.943183422088623s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 7.724761962890625e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 4.086209297180176s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.32372117042541504s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.018971920013427734s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.00052642822265625s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.82012939453125e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 5.7220458984375e-06s
INFO | --- Analysis for Institutions and Bodies of the European Union took 11.663741111755371s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 1.1750140190124512s
Availability | VoID file availability check for EU Parliament Media Library took 4.175665855407715s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.3806326389312744s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.018173933029174805s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0005223751068115234s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.3855438232421875e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 4.5299530029296875e-06s
INFO | --- Analysis for EU Parliament Media Library took 12.2351233959198s
Availability | SPARQL endpoint availability check for EU Who Is Who took 1.0545551776885986s
Availability | VoID file availability check for EU Who Is Who took 4.278989791870117s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.3208935260772705s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.018105506896972656s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0005481243133544922s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.5762786865234375e-05s
Believability | Calculation of trust value for EU Who Is Who took 8.106231689453125e-06s
INFO | --- Analysis for EU Who Is Who took 16.882779359817505s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 1.0573701858520508s
Availability | VoID file availability check for EUMIDA as Linked Data took 4.147234916687012s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.3805966377258301s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.01825881004333496s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0005295276641845703s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.124641418457031e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for EUMIDA as Linked Data took 14.026944875717163s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.5030391216278076s
Availability | VoID file availability check for European Nature Information System took 0.3082294464111328s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.363389253616333s
Reputation | Calculation of the PageRank for European Nature Information System took 0.020941495895385742s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0005352497100830078s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.0001068115234375s
Interoperability | Check the re-using of existing vocabs for European Nature Information System took 5.589978218078613s
Believability | Calculation of trust value for European Nature Information System took 7.3909759521484375e-06s
INFO | --- Analysis for European Nature Information System took 11.745556354522705s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 2.53288197517395s
Availability | VoID file availability check for EUR-Lex as Linked Data took 3.850013494491577s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.5133011341094971s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.018169879913330078s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0005240440368652344s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.295608520507812e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 1.0967254638671875e-05s
INFO | --- Analysis for EUR-Lex as Linked Data took 14.450299263000488s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 1.1404147148132324s
Availability | VoID file availability check for Standard Eurobarometer took 3.841114044189453s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.3262779712677002s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.01849532127380371s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.000537872314453125s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.57763671875e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 8.58306884765625e-06s
INFO | --- Analysis for Standard Eurobarometer took 16.24112820625305s
Availability | SPARQL endpoint availability check for EPO patents took 8.153915405273438e-05s
Availability | VoID file availability check for EPO patents took 5.9604644775390625e-06s
Completeness | Calculation of interlinking completeness for EPO patents took 0.3230161666870117s
Reputation | Calculation of the PageRank for EPO patents took 0.018640756607055664s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0005304813385009766s
Interlinking | Calculation of Clustering coefficient for EPO patents took 4.363059997558594e-05s
Believability | Calculation of trust value for EPO patents took 1.0967254638671875e-05s
INFO | --- Analysis for EPO patents took 1.9299793243408203s
Availability | SPARQL endpoint availability check for European Election Results took 1.0448472499847412s
Availability | VoID file availability check for European Election Results took 3.8660786151885986s
Completeness | Calculation of interlinking completeness for European Election Results took 0.35622358322143555s
Reputation | Calculation of the PageRank for European Election Results took 0.019435882568359375s
Interlinking | Calculation of Degree of Connection for European Election Results took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for European Election Results took 0.0005197525024414062s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.4809112548828125e-05s
Believability | Calculation of trust value for European Election Results took 1.0013580322265625e-05s
INFO | --- Analysis for European Election Results took 14.09947681427002s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 5.125999450683594e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.21526694297790527s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.3218820095062256s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.018082618713378906s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0005195140838623047s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 1.2159347534179688e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 6.4373016357421875e-06s
INFO | --- Analysis for Europeana Linked Open Data took 3.3529937267303467s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 4.863739013671875e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.1689624786376953s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.35500574111938477s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.018177509307861328s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0005135536193847656s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.179115295410156e-05s
Interoperability | Check the re-using of existing vocabs for Europeana Linked Open Data V1.0 took 16.131651878356934s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 6.9141387939453125e-06s
INFO | --- Analysis for Europeana Linked Open Data V1.0 took 26.59269666671753s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.4587225914001465s
Availability | VoID file availability check for Europeana SPARQL took 0.09052538871765137s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.37857937812805176s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.018289566040039062s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0005385875701904297s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 5.4836273193359375e-05s
Interoperability | Check the re-using of existing vocabs for Europeana SPARQL took 18.32080841064453s
Believability | Calculation of trust value for Europeana SPARQL took 1.049041748046875e-05s
INFO | --- Analysis for Europeana SPARQL took 28.32185125350952s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.08534812927246094s
Availability | VoID file availability check for EuroSentiment took 1.0967254638671875e-05s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.7874963283538818s
Reputation | Calculation of the PageRank for EuroSentiment took 0.01837325096130371s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0005314350128173828s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.933906555175781e-05s
Believability | Calculation of trust value for EuroSentiment took 7.152557373046875e-06s
INFO | --- Analysis for EuroSentiment took 6.613734006881714s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 6.437301635742188e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 1.0447463989257812s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.33718347549438477s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.018491268157958984s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0005352497100830078s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 8.130073547363281e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 7.867813110351562e-06s
INFO | --- Analysis for Eurostat RDF datasets took 7.925026178359985s
Availability | SPARQL endpoint availability check for EuroVoc took 1.0306684970855713s
Availability | VoID file availability check for EuroVoc took 4.246689796447754s
Extra | Recovery of all triples for EuroVoc took 294.1349079608917s
Performance | Total latancy measurement for EuroVoc took 1.4378929138183594s
Amount of data | Number of triples check for EuroVoc took 27.42375111579895s
Interoperability | New terms check for EuroVoc took 30.83977484703064s
Versatility | Languages check for EuroVoc took 300.10188150405884s
Interpretability | Number of blank nodes check for EuroVoc took 10.20933985710144s
Security | Check HTTPS for EuroVoc took 0.39322590827941895s
Interpretability | RDF structures check for EuroVoc took 0.48528528213500977s
Versatility | Serialization formats check for EuroVoc took 0.2721290588378906s
Availability | RDF dump link check for EuroVoc took 0.22008228302001953s
License | MR license check for EuroVoc took 0.23992037773132324s
License | HR license check for EuroVoc took 6.859088897705078s
Amount of data | Number of property check for EuroVoc took 0.13531756401062012s
Understandability | Number of label check for EuroVoc took 1.2717554569244385s
Understandability | URI regex check for EuroVoc took 0.27766895294189453s
Understandability | Vocabs check for EuroVoc took 0.10027837753295898s
Verifiability | Authors check for EuroVoc took 0.2554135322570801s
Verifiability | Publishers check for EuroVoc took 0.1992192268371582s
Performance | Throughput check for EuroVoc took 10.35057806968689s
Amount of data | Check the number of entities for EuroVoc took 0.0004405975341796875s
Verifiability | Contribs. check for EuroVoc took 0.1905677318572998s
Interlinking | sameAs chians check for EuroVoc took 6.153354644775391s
Interlinking | skos check for EuroVoc took 0.3552436828613281s
Interlinking | skos check for EuroVoc took 0.30858421325683594s
Timeliness | dataset update frequency check for EuroVoc took 0.22199416160583496s
Currency | Creation date check for EuroVoc took 0.701434850692749s
Currency | Modification date check for EuroVoc took 0.2150886058807373s
Rep.Conc. | URIs length for EuroVoc took 297.63294506073s
Interoperability | New vocabularies check for EuroVoc took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.17156291007995605s
Accuracy | Check Functional Property for EuroVoc took 0.18656444549560547s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.15668797492980957s
Accuracy | Check Empty annotation labels for EuroVoc took 62.3969407081604s
Accuracy | Check White space in annotation for EuroVoc took 3.281123399734497s
Accuracy | Check Datatype consistency for EuroVoc took 2.668151378631592s
Consistency | Disjoint class check for EuroVoc took 0.9963600635528564s
Consistency | Check Misplaced properties for EuroVoc took 195.6124622821808s
Consistency | Misplaced classes for EuroVoc took 8.735211610794067s
Consistency | Check Ontology hijacking for EuroVoc took 64.06321787834167s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.651503562927246s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 197.76861476898193s
Conciseness | Check Extensional conciseness for EuroVoc took 3.0618536472320557s
Conciseness | Check Intensional conciseness for EuroVoc took 0.39223718643188477s
Security | Sign check for EuroVoc took 0.20615005493164062s
Availability | Check URIs Dereferenciability for EuroVoc took 3.7024149894714355s
Completeness | Calculation of interlinking completeness for EuroVoc took 5.946927070617676s
Reputation | Calculation of the PageRank for EuroVoc took 0.019220352172851562s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 8.20159912109375e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 4.76837158203125e-06s
Believability | Calculation of trust value for EuroVoc took 1.1205673217773438e-05s
INFO | --- Analysis for EuroVoc took 10708.706922769547s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 30.297228813171387s
Availability | VoID file availability check for EUROVOC in SKOS took 20.088160753250122s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 0.32451391220092773s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.021987199783325195s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0005331039428710938s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 4.673004150390625e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 7.62939453125e-06s
INFO | --- Analysis for EUROVOC in SKOS took 63.091742515563965s
Availability | SPARQL endpoint availability check for European Television Heritage took 0.5156803131103516s
Availability | VoID file availability check for European Television Heritage took 0.27887749671936035s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.33495521545410156s
Reputation | Calculation of the PageRank for European Television Heritage took 0.018361568450927734s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0005207061767578125s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 1.1920928955078125e-05s
Believability | Calculation of trust value for European Television Heritage took 9.775161743164062e-06s
INFO | --- Analysis for European Television Heritage took 3.5439138412475586s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 4.3392181396484375e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 2.3992557525634766s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.3513455390930176s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.017976999282836914s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0005552768707275391s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.553794860839844e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 9.5367431640625e-06s
INFO | --- Analysis for Farmacias en Euskadi took 10.71121335029602s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.6341447830200195s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.8895974159240723s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.33197522163391113s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.018437623977661133s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0005497932434082031s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.462501525878906e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 5.9604644775390625e-06s
INFO | --- Analysis for Edinburgh University Theatre Company Productions took 8.035332202911377s
Availability | SPARQL endpoint availability check for EventMedia took 0.40883636474609375s
Availability | VoID file availability check for EventMedia took 0.17430758476257324s
Completeness | Calculation of interlinking completeness for EventMedia took 0.3551957607269287s
Reputation | Calculation of the PageRank for EventMedia took 0.018990278244018555s
Interlinking | Calculation of Degree of Connection for EventMedia took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EventMedia took 0.0005154609680175781s
Interlinking | Calculation of Clustering coefficient for EventMedia took 9.965896606445312e-05s
Believability | Calculation of trust value for EventMedia took 7.3909759521484375e-06s
INFO | --- Analysis for EventMedia took 19.15040612220764s
Availability | SPARQL endpoint availability check for EventKG took 4.4345855712890625e-05s
Availability | VoID file availability check for EventKG took 0.5091102123260498s
Completeness | Calculation of interlinking completeness for EventKG took 0.3520805835723877s
Reputation | Calculation of the PageRank for EventKG took 0.018208980560302734s
Interlinking | Calculation of Degree of Connection for EventKG took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EventKG took 0.0005178451538085938s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.034706115722656e-05s
Believability | Calculation of trust value for EventKG took 1.0251998901367188e-05s
INFO | --- Analysis for EventKG took 3.455460548400879s
Availability | SPARQL endpoint availability check for Eventseer took 1.4679172039031982s
Availability | VoID file availability check for Eventseer took 1.0941264629364014s
Completeness | Calculation of interlinking completeness for Eventseer took 0.3326237201690674s
Reputation | Calculation of the PageRank for Eventseer took 0.018003463745117188s
Interlinking | Calculation of Degree of Connection for Eventseer took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Eventseer took 0.0005166530609130859s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.38690185546875e-05s
Believability | Calculation of trust value for Eventseer took 1.2159347534179688e-05s
INFO | --- Analysis for Eventseer took 4.3927342891693115s
Availability | SPARQL endpoint availability check for Face Link took 8.177757263183594e-05s
Availability | VoID file availability check for Face Link took 5.4836273193359375e-06s
Completeness | Calculation of interlinking completeness for Face Link took 0.37039828300476074s
Reputation | Calculation of the PageRank for Face Link took 0.018242835998535156s
Interlinking | Calculation of Degree of Connection for Face Link took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Face Link took 0.0005125999450683594s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.647804260253906e-05s
Believability | Calculation of trust value for Face Link took 1.7404556274414062e-05s
INFO | --- Analysis for Face Link took 2.019376754760742s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 4.5299530029296875e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.17471981048583984s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.34938716888427734s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.01877760887145996s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.0005457401275634766s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 1.1682510375976562e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 6.198883056640625e-06s
INFO | --- Analysis for Facebook Linked Data Service took 2.540607452392578s
Availability | SPARQL endpoint availability check for Fact Forge took 0.690115213394165s
Availability | VoID file availability check for Fact Forge took 0.21082615852355957s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.35132503509521484s
Reputation | Calculation of the PageRank for Fact Forge took 0.018128395080566406s
Interlinking | Calculation of Degree of Connection for Fact Forge took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Fact Forge took 0.0005445480346679688s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 1.1682510375976562e-05s
Believability | Calculation of trust value for Fact Forge took 1.33514404296875e-05s
INFO | --- Analysis for Fact Forge took 2.779258966445923s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 took 9.274482727050781e-05s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 took 5.0067901611328125e-06s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 took 0.37781381607055664s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 took 0.017955780029296875s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 took 0.0005261898040771484s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 took 3.9577484130859375e-05s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 took 1.239776611328125e-05s
INFO | --- Analysis for Farm Accountancy Data Network (FADN) linked dataset from 2019 took 1.9678599834442139s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities took 5.364418029785156e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities took 5.9604644775390625e-06s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities took 0.34699296951293945s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities took 0.019220590591430664s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities took 0.0005130767822265625s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities took 3.719329833984375e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities took 1.0251998901367188e-05s
INFO | --- Analysis for FAO ASFIS classification of biological entities took 1.9144566059112549s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 8.559226989746094e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 2.001887321472168s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.3151886463165283s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.0179135799407959s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.000522613525390625s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 9.679794311523438e-05s
Believability | Calculation of trust value for FAO geopolitical ontology took 8.344650268554688e-06s
INFO | --- Analysis for FAO geopolitical ontology took 15.762004852294922s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.11838269233703613s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.008247613906860352s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.3597874641418457s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.018047332763671875s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0005168914794921875s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.72747802734375e-05s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.049041748046875e-05s
INFO | --- Analysis for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.9931752681732178s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 0.7939164638519287s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.37209558486938477s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.5672967433929443s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.019269704818725586s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0005354881286621094s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.9114227294921875e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 1.430511474609375e-05s
INFO | --- Analysis for ChEMBL-RDF (@ Uppsala University) took 16.631792783737183s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 8.487701416015625e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 4.76837158203125e-06s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.5155394077301025s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.018464326858520508s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.0005526542663574219s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 1.4543533325195312e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 1.1205673217773438e-05s
INFO | --- Analysis for Farmers Markets Geographic Data (United States) took 3.280076742172241s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 20.353721857070923s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 1.1444091796875e-05s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.29151082038879395s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.019280433654785156s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0005156993865966797s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 1.71661376953125e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 9.059906005859375e-06s
INFO | --- Analysis for FarolApp Streetlight Dataset took 120.85637998580933s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 9.608268737792969e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 7.867813110351562e-06s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.8395252227783203s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.020633459091186523s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0005176067352294922s
Interlinking | Calculation of Clustering coefficient for Fatal Traffic Accidents in greek roads took 1.3828277587890625e-05s
Believability | Calculation of trust value for Fatal Traffic Accidents in greek roads took 1.1682510375976562e-05s
INFO | --- Analysis for Fatal Traffic Accidents in greek roads took 3.658367395401001s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 1.2607619762420654s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.5797438621520996s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 0.33583855628967285s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.018770217895507812s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.0005235671997070312s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 1.2159347534179688e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 1.0967254638671875e-05s
INFO | --- Analysis for Federal Reserve Economic Data RDF took 4.604822635650635s
Availability | SPARQL endpoint availability check for Feed Wrapper took 8.654594421386719e-05s
Availability | VoID file availability check for Feed Wrapper took 0.010775566101074219s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 0.31890130043029785s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.018372297286987305s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.0005395412445068359s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 1.3113021850585938e-05s
Believability | Calculation of trust value for Feed Wrapper took 5.698204040527344e-05s
INFO | --- Analysis for Feed Wrapper took 1.8635215759277344s
Availability | SPARQL endpoint availability check for FHIR STU3 took 8.20159912109375e-05s
Availability | VoID file availability check for FHIR STU3 took 6.67572021484375e-06s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.3671741485595703s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.018287181854248047s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0005238056182861328s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 1.33514404296875e-05s
Believability | Calculation of trust value for FHIR STU3 took 1.1444091796875e-05s
INFO | --- Analysis for FHIR STU3 took 2.0558340549468994s
Availability | SPARQL endpoint availability check for FiESTA took 0.00012969970703125s
Availability | VoID file availability check for FiESTA took 8.344650268554688e-06s
Completeness | Calculation of interlinking completeness for FiESTA took 0.6893630027770996s
Reputation | Calculation of the PageRank for FiESTA took 0.018294334411621094s
Interlinking | Calculation of Degree of Connection for FiESTA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for FiESTA took 0.0005283355712890625s
Interlinking | Calculation of Clustering coefficient for FiESTA took 3.910064697265625e-05s
Believability | Calculation of trust value for FiESTA took 1.1444091796875e-05s
INFO | --- Analysis for FiESTA took 12.486126899719238s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 7.414817810058594e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.291534423828125e-06s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.3457062244415283s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.01828765869140625s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0005307197570800781s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.5497207641601562e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 7.152557373046875e-06s
INFO | --- Analysis for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 2.3537650108337402s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 8.726119995117188e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 60.422672271728516s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.42783451080322266s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.022907733917236328s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 3.075599670410156e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0011546611785888672s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 0.00013327598571777344s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 9.298324584960938e-06s
INFO | --- Analysis for Finnish municipalities and regional classifications took 364.3217816352844s
Availability | SPARQL endpoint availability check for firmao took 0.000133514404296875s
Availability | VoID file availability check for firmao took 8.344650268554688e-06s
Completeness | Calculation of interlinking completeness for firmao took 0.4368774890899658s
Reputation | Calculation of the PageRank for firmao took 0.018267393112182617s
Interlinking | Calculation of Degree of Connection for firmao took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for firmao took 0.0005428791046142578s
Interlinking | Calculation of Clustering coefficient for firmao took 1.239776611328125e-05s
Believability | Calculation of trust value for firmao took 1.3828277587890625e-05s
INFO | --- Analysis for firmao took 2.863633871078491s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 1.126551628112793s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 1.049041748046875e-05s
Extra | Recovery of all triples for FISH Archaeological Objects Thesaurus took 1.0112669467926025s
Performance | Total latancy measurement for FISH Archaeological Objects Thesaurus took 3.6638758182525635s
Amount of data | Number of triples check for FISH Archaeological Objects Thesaurus took 2.07326602935791s
Versatility | Languages check for FISH Archaeological Objects Thesaurus took 0.368668794631958s
Interpretability | Number of blank nodes check for FISH Archaeological Objects Thesaurus took 1.648322343826294s
Security | Check HTTPS for FISH Archaeological Objects Thesaurus took 0.5385222434997559s
Interpretability | RDF structures check for FISH Archaeological Objects Thesaurus took 0.4316372871398926s
Versatility | Serialization formats check for FISH Archaeological Objects Thesaurus took 0.786841869354248s
Availability | RDF dump link check for FISH Archaeological Objects Thesaurus took 0.8275532722473145s
License | MR license check for FISH Archaeological Objects Thesaurus took 1.6959283351898193s
License | HR license check for FISH Archaeological Objects Thesaurus took 1.1997754573822021s
Amount of data | Number of property check for FISH Archaeological Objects Thesaurus took 1.5214126110076904s
Understandability | Number of label check for FISH Archaeological Objects Thesaurus took 2.147472381591797s
Understandability | URI regex check for FISH Archaeological Objects Thesaurus took 1.9011824131011963s
Understandability | Vocabs check for FISH Archaeological Objects Thesaurus took 0.7991485595703125s
Verifiability | Authors check for FISH Archaeological Objects Thesaurus took 0.7076444625854492s
Verifiability | Publishers check for FISH Archaeological Objects Thesaurus took 1.1803381443023682s
Performance | Throughput check for FISH Archaeological Objects Thesaurus took 13.254916191101074s
Amount of data | Check the number of entities for FISH Archaeological Objects Thesaurus took 3.743171691894531e-05s
Verifiability | Contribs. check for FISH Archaeological Objects Thesaurus took 0.5915734767913818s
Interlinking | sameAs chians check for FISH Archaeological Objects Thesaurus took 0.6476225852966309s
Interlinking | skos check for FISH Archaeological Objects Thesaurus took 0.7811861038208008s
Interlinking | skos check for FISH Archaeological Objects Thesaurus took 0.8323314189910889s
Timeliness | dataset update frequency check for FISH Archaeological Objects Thesaurus took 0.7745201587677002s
Currency | Creation date check for FISH Archaeological Objects Thesaurus took 1.5579326152801514s
Currency | Modification date check for FISH Archaeological Objects Thesaurus took 1.7135353088378906s
Rep.Conc. | URIs length for FISH Archaeological Objects Thesaurus took 1.8047866821289062s
Interoperability | New vocabularies check for FISH Archaeological Objects Thesaurus took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for FISH Archaeological Objects Thesaurus took 0.7285621166229248s
Accuracy | Check Functional Property for FISH Archaeological Objects Thesaurus took 0.6883594989776611s
Accuracy | Check Inverse Functional Property for FISH Archaeological Objects Thesaurus took 0.6378145217895508s
Consistency | Disjoint class check for FISH Archaeological Objects Thesaurus took 0.6515538692474365s
Consistency | Check Ontology hijacking for FISH Archaeological Objects Thesaurus took 47.44519925117493s
Consistency | Check Invalid usage of undefined properties for FISH Archaeological Objects Thesaurus took 1.7951972484588623s
Conciseness | Check Extensional conciseness for FISH Archaeological Objects Thesaurus took 0.000156402587890625s
Security | Sign check for FISH Archaeological Objects Thesaurus took 0.8733170032501221s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.3818199634552002s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.017925739288330078s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0005276203155517578s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 2.1219253540039062e-05s
Interoperability | Check the re-using of existing vocabs for FISH Archaeological Objects Thesaurus took 1.1920928955078125e-06s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for FISH Archaeological Objects Thesaurus took 159.4333279132843s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 8.678436279296875e-05s
Availability | VoID file availability check for Norway fishery stocks dataset took 7.62939453125e-06s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.32944416999816895s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.019230127334594727s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0005249977111816406s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 1.4066696166992188e-05s
Believability | Calculation of trust value for Norway fishery stocks dataset took 1.1682510375976562e-05s
INFO | --- Analysis for Norway fishery stocks dataset took 1.8871057033538818s
Availability | SPARQL endpoint availability check for Fishes of Texas took 8.797645568847656e-05s
Availability | VoID file availability check for Fishes of Texas took 5.738017559051514s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.3159809112548828s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.01828622817993164s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0005238056182861328s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.749961853027344e-05s
Believability | Calculation of trust value for Fishes of Texas took 7.3909759521484375e-06s
INFO | --- Analysis for Fishes of Texas took 8.048939228057861s
Availability | SPARQL endpoint availability check for flickr? wrappr took 7.581710815429688e-05s
Availability | VoID file availability check for flickr? wrappr took 20.399810791015625s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.3219945430755615s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.018012046813964844s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0005316734313964844s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.369850158691406e-05s
Believability | Calculation of trust value for flickr? wrappr took 6.9141387939453125e-06s
INFO | --- Analysis for flickr? wrappr took 32.667211055755615s
Availability | SPARQL endpoint availability check for flickr.person took 4.696846008300781e-05s
Availability | VoID file availability check for flickr.person took 20.00029492378235s
Completeness | Calculation of interlinking completeness for flickr.person took 0.3750479221343994s
Reputation | Calculation of the PageRank for flickr.person took 0.021112680435180664s
Interlinking | Calculation of Degree of Connection for flickr.person took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for flickr.person took 0.0005288124084472656s
Interlinking | Calculation of Clustering coefficient for flickr.person took 1.2874603271484375e-05s
Believability | Calculation of trust value for flickr.person took 1.1920928955078125e-05s
INFO | --- Analysis for flickr.person took 62.058834075927734s
Availability | SPARQL endpoint availability check for flickr.videoobject took 8.654594421386719e-05s
Availability | VoID file availability check for flickr.videoobject took 20.000954389572144s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 0.5118727684020996s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.01857614517211914s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.0005154609680175781s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 1.2636184692382812e-05s
Believability | Calculation of trust value for flickr.videoobject took 1.049041748046875e-05s
INFO | --- Analysis for flickr.videoobject took 52.14316415786743s
Availability | SPARQL endpoint availability check for Fly-TED took 8.726119995117188e-05s
Availability | VoID file availability check for Fly-TED took 0.9444055557250977s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.30669188499450684s
Reputation | Calculation of the PageRank for Fly-TED took 0.01854562759399414s
Interlinking | Calculation of Degree of Connection for Fly-TED took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Fly-TED took 0.0005331039428710938s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 1.239776611328125e-05s
Believability | Calculation of trust value for Fly-TED took 1.1205673217773438e-05s
INFO | --- Analysis for Fly-TED took 22.692609310150146s
Availability | SPARQL endpoint availability check for FlyAtlas took 8.344650268554688e-05s
Availability | VoID file availability check for FlyAtlas took 0.7718260288238525s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.34240007400512695s
Reputation | Calculation of the PageRank for FlyAtlas took 0.019104957580566406s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0005145072937011719s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 1.2636184692382812e-05s
Believability | Calculation of trust value for FlyAtlas took 1.1444091796875e-05s
INFO | --- Analysis for FlyAtlas took 22.762868642807007s
Availability | SPARQL endpoint availability check for Flybase took 1.2377707958221436s
Availability | VoID file availability check for Flybase took 0.6841695308685303s
Completeness | Calculation of interlinking completeness for Flybase took 0.32319140434265137s
Reputation | Calculation of the PageRank for Flybase took 0.01833510398864746s
Interlinking | Calculation of Degree of Connection for Flybase took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Flybase took 0.0005245208740234375s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.5762786865234375e-05s
Believability | Calculation of trust value for Flybase took 1.3113021850585938e-05s
INFO | --- Analysis for Flybase took 4.603442192077637s
Availability | SPARQL endpoint availability check for Flyted took 1.1809422969818115s
Availability | VoID file availability check for Flyted took 0.8390903472900391s
Completeness | Calculation of interlinking completeness for Flyted took 0.3136622905731201s
Reputation | Calculation of the PageRank for Flyted took 0.018732070922851562s
Interlinking | Calculation of Degree of Connection for Flyted took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0005185604095458984s
Interlinking | Calculation of Clustering coefficient for Flyted took 1.3589859008789062e-05s
Believability | Calculation of trust value for Flyted took 1.3113021850585938e-05s
INFO | --- Analysis for Flyted took 4.97335147857666s
Availability | SPARQL endpoint availability check for Foodista took 1.1315598487854004s
Availability | VoID file availability check for Foodista took 0.703411340713501s
Completeness | Calculation of interlinking completeness for Foodista took 0.2973768711090088s
Reputation | Calculation of the PageRank for Foodista took 0.019529104232788086s
Interlinking | Calculation of Degree of Connection for Foodista took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0005316734313964844s
Interlinking | Calculation of Clustering coefficient for Foodista took 1.239776611328125e-05s
Believability | Calculation of trust value for Foodista took 8.106231689453125e-06s
INFO | --- Analysis for Foodista took 7.269160985946655s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.17888188362121582s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.009653806686401367s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.44869089126586914s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.01848888397216797s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0005269050598144531s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.295608520507812e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.0728836059570312e-05s
INFO | --- Analysis for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 2.272233486175537s
Availability | SPARQL endpoint availability check for FORGE Course information took 0.662787675857544s
Availability | VoID file availability check for FORGE Course information took 8.344650268554688e-06s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.34689879417419434s
Reputation | Calculation of the PageRank for FORGE Course information took 0.0204317569732666s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0005269050598144531s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 1.9311904907226562e-05s
Believability | Calculation of trust value for FORGE Course information took 1.2159347534179688e-05s
INFO | --- Analysis for FORGE Course information took 3.240271806716919s
Availability | SPARQL endpoint availability check for FrameBase schema took 8.678436279296875e-05s
Availability | VoID file availability check for FrameBase schema took 0.5970902442932129s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.36090612411499023s
Reputation | Calculation of the PageRank for FrameBase schema took 0.018492698669433594s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0005183219909667969s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.601478576660156e-05s
Believability | Calculation of trust value for FrameBase schema took 1.1444091796875e-05s
INFO | --- Analysis for FrameBase schema took 8.32407259941101s
Availability | SPARQL endpoint availability check for FrameNet took 0.0001518726348876953s
Availability | VoID file availability check for FrameNet took 5.9604644775390625e-06s
Completeness | Calculation of interlinking completeness for FrameNet took 0.5823397636413574s
Reputation | Calculation of the PageRank for FrameNet took 0.018548965454101562s
Interlinking | Calculation of Degree of Connection for FrameNet took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for FrameNet took 0.0005183219909667969s
Interlinking | Calculation of Clustering coefficient for FrameNet took 1.2636184692382812e-05s
Believability | Calculation of trust value for FrameNet took 1.1444091796875e-05s
INFO | --- Analysis for FrameNet took 3.983607292175293s
Availability | SPARQL endpoint availability check for Framester took 0.576566219329834s
Availability | VoID file availability check for Framester took 0.5292477607727051s
Extra | Recovery of all triples for Framester took 60.579352140426636s
Performance | Total latancy measurement for Framester took 2.1669082641601562s
Amount of data | Number of triples check for Framester took 52.70077657699585s
Versatility | Languages check for Framester took 60.50635385513306s
Interpretability | Number of blank nodes check for Framester took 0.6031441688537598s
Interpretability | RDF structures check for Framester took 1.3633036613464355s
Versatility | Serialization formats check for Framester took 1.1519625186920166s
Availability | RDF dump link check for Framester took 19.01955223083496s
License | MR license check for Framester took 2.3268256187438965s
License | HR license check for Framester took 60.633012771606445s
Amount of data | Number of property check for Framester took 0.5103790760040283s
Understandability | Number of label check for Framester took 14.523880958557129s
Understandability | URI regex check for Framester took 1.6069140434265137s
Understandability | Vocabs check for Framester took 0.7631504535675049s
Verifiability | Authors check for Framester took 1.011324405670166s
Verifiability | Publishers check for Framester took 1.1929116249084473s
Performance | Throughput check for Framester took 14.10169792175293s
Amount of data | Check the number of entities for Framester took 0.00010395050048828125s
Verifiability | Contribs. check for Framester took 0.9810490608215332s
Interlinking | sameAs chians check for Framester took 0.5636847019195557s
Interlinking | skos check for Framester took 1.8796916007995605s
Interlinking | skos check for Framester took 0.5368304252624512s
Timeliness | dataset update frequency check for Framester took 0.47832679748535156s
Currency | Creation date check for Framester took 0.914741039276123s
Currency | Modification date check for Framester took 0.6335537433624268s
Rep.Conc. | URIs length for Framester took 122.85350942611694s
Interoperability | New vocabularies check for Framester took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for Framester took 0.4842414855957031s
Accuracy | Check Functional Property for Framester took 0.7017242908477783s
Accuracy | Check Inverse Functional Property for Framester took 0.6235353946685791s
Accuracy | Check Empty annotation labels for Framester took 52.23199272155762s
Accuracy | Check White space in annotation for Framester took 3.0400633811950684s
Consistency | Disjoint class check for Framester took 0.5626757144927979s
Consistency | Check Misplaced properties for Framester took 88.09811997413635s
Consistency | Misplaced classes for Framester took 0.6428999900817871s
Consistency | Check Ontology hijacking for Framester took 37.81699991226196s
Consistency | Check Invalid usage of undefined properties for Framester took 61.75516700744629s
Conciseness | Check Extensional conciseness for Framester took 0.00018262863159179688s
Conciseness | Check Intensional conciseness for Framester took 0.7685508728027344s
Security | Sign check for Framester took 1.6323649883270264s
Completeness | Calculation of interlinking completeness for Framester took 0.5957434177398682s
Reputation | Calculation of the PageRank for Framester took 0.018330812454223633s
Interlinking | Calculation of Degree of Connection for Framester took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Framester took 0.0005354881286621094s
Interlinking | Calculation of Clustering coefficient for Framester took 8.153915405273438e-05s
Interoperability | Check the re-using of existing vocabs for Framester took 1.6689300537109375e-06s
Believability | Calculation of trust value for Framester took 1.2874603271484375e-05s
INFO | --- Analysis for Framester took 1084.6525361537933s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.1544642448425293s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 8.58306884765625e-06s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 1.7953977584838867s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.0186159610748291s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.000518798828125s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.7738037109375e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 1.1205673217773438e-05s
INFO | --- Analysis for Federal Reserve Board (FRB) Linked Data took 6.477161169052124s
Availability | SPARQL endpoint availability check for Freebase took 0.00010561943054199219s
Availability | VoID file availability check for Freebase took 0.26312708854675293s
Completeness | Calculation of interlinking completeness for Freebase took 0.27956485748291016s
Reputation | Calculation of the PageRank for Freebase took 0.018971681594848633s
Interlinking | Calculation of Degree of Connection for Freebase took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Freebase took 0.0005204677581787109s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.00027441978454589844s
Believability | Calculation of trust value for Freebase took 1.2874603271484375e-05s
INFO | --- Analysis for Freebase took 11.23091745376587s
Availability | SPARQL endpoint availability check for Freeyork took 8.630752563476562e-05s
Availability | VoID file availability check for Freeyork took 1.3542654514312744s
Completeness | Calculation of interlinking completeness for Freeyork took 0.5369629859924316s
Reputation | Calculation of the PageRank for Freeyork took 0.018724918365478516s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0005168914794921875s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010442733764648438s
Believability | Calculation of trust value for Freeyork took 1.1205673217773438e-05s
INFO | --- Analysis for Freeyork took 4.762134313583374s
Availability | SPARQL endpoint availability check for French School Program took 9.131431579589844e-05s
Availability | VoID file availability check for French School Program took 6.9141387939453125e-06s
Completeness | Calculation of interlinking completeness for French School Program took 0.3384723663330078s
Reputation | Calculation of the PageRank for French School Program took 0.017974376678466797s
Interlinking | Calculation of Degree of Connection for French School Program took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for French School Program took 0.0005459785461425781s
Interlinking | Calculation of Clustering coefficient for French School Program took 1.2159347534179688e-05s
Believability | Calculation of trust value for French School Program took 1.1444091796875e-05s
INFO | --- Analysis for French School Program took 5.5155088901519775s
Availability | SPARQL endpoint availability check for French School System took 8.96453857421875e-05s
Availability | VoID file availability check for French School System took 7.3909759521484375e-06s
Completeness | Calculation of interlinking completeness for French School System took 2.298145055770874s
Reputation | Calculation of the PageRank for French School System took 0.01922297477722168s
Interlinking | Calculation of Degree of Connection for French School System took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for French School System took 0.0005140304565429688s
Interlinking | Calculation of Clustering coefficient for French School System took 1.1682510375976562e-05s
Believability | Calculation of trust value for French School System took 1.1444091796875e-05s
INFO | --- Analysis for French School System took 5.167914867401123s
Availability | SPARQL endpoint availability check for French TimeBank took 9.202957153320312e-05s
Availability | VoID file availability check for French TimeBank took 1.789137363433838s
Completeness | Calculation of interlinking completeness for French TimeBank took 1.3489711284637451s
Reputation | Calculation of the PageRank for French TimeBank took 0.022542953491210938s
Interlinking | Calculation of Degree of Connection for French TimeBank took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for French TimeBank took 0.0005095005035400391s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 1.4543533325195312e-05s
Believability | Calculation of trust value for French TimeBank took 1.2874603271484375e-05s
INFO | --- Analysis for French TimeBank took 9.26098370552063s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 30.59375s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 20.39978337287903s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 1.083587646484375s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.018188953399658203s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0005283355712890625s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 8.440017700195312e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 9.059906005859375e-06s
INFO | --- Analysis for Community Research and Development Information Service (CORDIS) took 76.27119898796082s
Availability | SPARQL endpoint availability check for DailyMed took 30.58680486679077s
Availability | VoID file availability check for DailyMed took 20.394073009490967s
Completeness | Calculation of interlinking completeness for DailyMed took 0.5116639137268066s
Reputation | Calculation of the PageRank for DailyMed took 0.019824981689453125s
Interlinking | Calculation of Degree of Connection for DailyMed took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DailyMed took 0.0005509853363037109s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.703636169433594e-05s
Believability | Calculation of trust value for DailyMed took 1.1682510375976562e-05s
INFO | --- Analysis for DailyMed took 94.47039723396301s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 30.615696907043457s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 20.39512300491333s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.39902591705322266s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.018392562866210938s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0005338191986083984s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.511543273925781e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 1.1444091796875e-05s
INFO | --- Analysis for DBLP Bibliography Database in RDF (FU Berlin) took 73.9152398109436s
Availability | SPARQL endpoint availability check for Diseasome took 30.669288158416748s
Availability | VoID file availability check for Diseasome took 20.39275097846985s
Completeness | Calculation of interlinking completeness for Diseasome took 0.297391414642334s
Reputation | Calculation of the PageRank for Diseasome took 0.019144058227539062s
Interlinking | Calculation of Degree of Connection for Diseasome took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Diseasome took 0.0005154609680175781s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.0001266002655029297s
Believability | Calculation of trust value for Diseasome took 1.0967254638671875e-05s
INFO | --- Analysis for Diseasome took 93.49402070045471s
Availability | SPARQL endpoint availability check for DrugBank took 30.600414037704468s
Availability | VoID file availability check for DrugBank took 20.395477294921875s
Completeness | Calculation of interlinking completeness for DrugBank took 0.36521172523498535s
Reputation | Calculation of the PageRank for DrugBank took 0.018535852432250977s
Interlinking | Calculation of Degree of Connection for DrugBank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DrugBank took 0.0005402565002441406s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00012826919555664062s
Believability | Calculation of trust value for DrugBank took 1.0728836059570312e-05s
INFO | --- Analysis for DrugBank took 93.49901509284973s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 30.643755435943604s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 20.396302938461304s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.39196038246154785s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.018453598022460938s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0005321502685546875s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 1.2636184692382812e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 1.1444091796875e-05s
INFO | --- Analysis for European Commission Competition data set (FU Berlin) took 73.21801137924194s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 30.61933469772339s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 20.392417192459106s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.3254668712615967s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.01852273941040039s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0005199909210205078s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 8.058547973632812e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 9.775161743164062e-06s
INFO | --- Analysis for EURAXESS - Researchers in Motion took 73.05844044685364s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 30.63285231590271s
Availability | VoID file availability check for European Employment Services (EURES) took 20.39099383354187s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.344146728515625s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.01906728744506836s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0005252361297607422s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 8.511543273925781e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 8.58306884765625e-06s
INFO | --- Analysis for European Employment Services (EURES) took 73.23204731941223s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 30.59101366996765s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 20.397441148757935s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.34413886070251465s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.01849532127380371s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0005452632904052734s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.632110595703125e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 8.821487426757812e-06s
INFO | --- Analysis for Eurostat in RDF (FU Berlin) took 83.30524921417236s
Availability | SPARQL endpoint availability check for MediCare took 30.64993929862976s
Availability | VoID file availability check for MediCare took 20.293561697006226s
Completeness | Calculation of interlinking completeness for MediCare took 0.3703324794769287s
Reputation | Calculation of the PageRank for MediCare took 0.018388032913208008s
Interlinking | Calculation of Degree of Connection for MediCare took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MediCare took 0.0005242824554443359s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.2438507080078125e-05s
Believability | Calculation of trust value for MediCare took 1.1444091796875e-05s
INFO | --- Analysis for MediCare took 83.32786798477173s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 30.6463565826416s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 20.398504972457886s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.31352972984313965s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.018297195434570312s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0005176067352294922s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.05718994140625e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 1.3828277587890625e-05s
INFO | --- Analysis for Project Gutenberg in RDF (FU Berlin) took 73.200599193573s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 30.593113660812378s
Availability | VoID file availability check for SIDER: Side Effect Resource took 20.39901041984558s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.3690347671508789s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.018182992935180664s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0005359649658203125s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.799003601074219e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 1.0967254638671875e-05s
INFO | --- Analysis for SIDER: Side Effect Resource took 83.32334470748901s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 30.585916757583618s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 20.395389795303345s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.35410261154174805s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.018167972564697266s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0005507469177246094s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.367134094238281e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 1.2159347534179688e-05s
INFO | --- Analysis for STITCH: Chemical-Protein Interactions took 73.1068959236145s
Availability | SPARQL endpoint availability check for fvdb took 9.012222290039062e-05s
Availability | VoID file availability check for fvdb took 7.867813110351562e-06s
Completeness | Calculation of interlinking completeness for fvdb took 0.32385802268981934s
Reputation | Calculation of the PageRank for fvdb took 0.018574237823486328s
Interlinking | Calculation of Degree of Connection for fvdb took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for fvdb took 1.1682510375976562e-05s
Believability | Calculation of trust value for fvdb took 1.1682510375976562e-05s
INFO | --- Analysis for fvdb took 12.602349519729614s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 8.392333984375e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 5.663881540298462s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.3365137577056885s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.01976919174194336s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0005218982696533203s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 1.1205673217773438e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 1.1682510375976562e-05s
INFO | --- Analysis for Global Agricultural Concept Space took 8.211771249771118s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 8.630752563476562e-05s
Availability | VoID file availability check for Galen from co-ode.org took 1.9257757663726807s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.30147552490234375s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.018433332443237305s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0005433559417724609s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 1.2159347534179688e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 1.0967254638671875e-05s
INFO | --- Analysis for Galen from co-ode.org took 16.923065662384033s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 8.940696716308594e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 7.152557373046875e-06s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.34856700897216797s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.018378019332885742s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0005545616149902344s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.5299530029296875e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 4.673004150390625e-05s
INFO | --- Analysis for Galician EuroWordNet-lemon lexicon (3.0) took 5.68568754196167s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 8.7738037109375e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0077741146087646484s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.40828800201416016s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.01986241340637207s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.00011777877807617188s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 1.1920928955078125e-05s
INFO | --- Analysis for Garnica Plywood Catalogue took 3.227809429168701s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.1552734375e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.5964674949645996s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.36670899391174316s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.019356966018676758s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0005393028259277344s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.00010800361633300781s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.2159347534179688e-05s
INFO | --- Analysis for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 16.38236355781555s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.4281880855560303s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 120.4582417011261s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.5927987098693848s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.01971745491027832s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.000537872314453125s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 0.00010180473327636719s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 1.0251998901367188e-05s
INFO | --- Analysis for GEneral Multilingual Environmental Thesaurus took 250.2916898727417s
Availability | SPARQL endpoint availability check for gemet-annotated took 8.440017700195312e-05s
Availability | VoID file availability check for gemet-annotated took 6.4373016357421875e-06s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.33293700218200684s
Reputation | Calculation of the PageRank for gemet-annotated took 0.02034306526184082s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0005347728729248047s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.743171691894531e-05s
Believability | Calculation of trust value for gemet-annotated took 1.049041748046875e-05s
INFO | --- Analysis for gemet-annotated took 2.5714902877807617s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.9208760261535645s
Availability | VoID file availability check for Gene Expression Atlas RDF took 5.2237818241119385s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.44837284088134766s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.01936936378479004s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0005211830139160156s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 4.00543212890625e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 1.2874603271484375e-05s
INFO | --- Analysis for Gene Expression Atlas RDF took 9.659594774246216s
Availability | SPARQL endpoint availability check for Super Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Super Ontology took 7.62939453125e-06s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.3262033462524414s
Reputation | Calculation of the PageRank for Super Ontology took 0.01916646957397461s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0005502700805664062s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 3.933906555175781e-05s
Believability | Calculation of trust value for Super Ontology took 1.239776611328125e-05s
INFO | --- Analysis for Super Ontology took 2.353153705596924s
Availability | SPARQL endpoint availability check for geo.place took 9.5367431640625e-05s
Availability | VoID file availability check for geo.place took 20.003578186035156s
Completeness | Calculation of interlinking completeness for geo.place took 0.3214728832244873s
Reputation | Calculation of the PageRank for geo.place took 0.018580198287963867s
Interlinking | Calculation of Degree of Connection for geo.place took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for geo.place took 0.0005552768707275391s
Interlinking | Calculation of Clustering coefficient for geo.place took 1.3589859008789062e-05s
Believability | Calculation of trust value for geo.place took 1.239776611328125e-05s
INFO | --- Analysis for geo.place took 52.299307346343994s
Availability | SPARQL endpoint availability check for geodomainwn took 9.083747863769531e-05s
Availability | VoID file availability check for geodomainwn took 1.049041748046875e-05s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.7287111282348633s
Reputation | Calculation of the PageRank for geodomainwn took 0.01925492286682129s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0005223751068115234s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 4.696846008300781e-05s
Believability | Calculation of trust value for geodomainwn took 7.867813110351562e-06s
INFO | --- Analysis for geodomainwn took 6.467622518539429s
Availability | SPARQL endpoint availability check for GeoEcuador took 20.072249174118042s
Availability | VoID file availability check for GeoEcuador took 6.9141387939453125e-06s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.3640580177307129s
Reputation | Calculation of the PageRank for GeoEcuador took 0.018602609634399414s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0005605220794677734s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 7.271766662597656e-05s
Believability | Calculation of trust value for GeoEcuador took 1.2874603271484375e-05s
INFO | --- Analysis for GeoEcuador took 33.423908948898315s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 262.923451423645s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 9.5367431640625e-06s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 1.1950366497039795s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.019221782684326172s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0005474090576171875s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 7.987022399902344e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 1.239776611328125e-05s
INFO | --- Analysis for Geographic Names Information System (GNIS) took 439.7063159942627s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 0.06906318664550781s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.007896184921264648s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.33435678482055664s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.020557165145874023s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.0005261898040771484s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 1.239776611328125e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 1.1205673217773438e-05s
INFO | --- Analysis for OpenUpLabs Geographic took 3.1784281730651855s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.5132949352264404s
Availability | VoID file availability check for GeoLinkedData took 0.24343252182006836s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 2.044100046157837s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.01795339584350586s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0005350112915039062s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 8.702278137207031e-05s
Believability | Calculation of trust value for GeoLinkedData took 9.5367431640625e-06s
INFO | --- Analysis for GeoLinkedData took 6.944017648696899s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.22561907768249512s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.10520482063293457s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 6.004407644271851s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.43627262115478516s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.1338670253753662s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.3272418975830078s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.1776425838470459s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.15649700164794922s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.1968822479248047s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.11213994026184082s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.09997892379760742s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.07711672782897949s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.09987688064575195s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 2.4016528129577637s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.11928009986877441s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.12339591979980469s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.16626620292663574s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.1348555088043213s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.12307929992675781s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.12999868392944336s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.362674951553345s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 9.298324584960938e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.1186528205871582s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.08820271492004395s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.1131141185760498s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.08263993263244629s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.09118247032165527s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.1217341423034668s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.12172603607177734s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.1568782329559326s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 0.8918225765228271s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.12734317779541016s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06980609893798828s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.07855629920959473s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.35888171195983887s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.007552146911621094s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.15964508056640625s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.0861520767211914s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.22171878814697266s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.38520073890686035s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 1.5156068801879883s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.1561458110809326s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.3098008632659912s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.11639547348022461s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.0804758071899414s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 1.1066009998321533s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.3811986446380615s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.01807546615600586s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0006668567657470703s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 9.012222290039062e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 0.3882877826690674s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for Geological Survey of Austria (GBA) - Thesaurus took 114.63681840896606s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 8.726119995117188e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.22983217239379883s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 1.7626159191131592s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.020592451095581055s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0005145072937011719s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.00046253204345703125s
Believability | Calculation of trust value for GeoNames Semantic Web took 1.1205673217773438e-05s
INFO | --- Analysis for GeoNames Semantic Web took 9.184672117233276s
Availability | SPARQL endpoint availability check for Geospatial World  took 8.511543273925781e-05s
Availability | VoID file availability check for Geospatial World  took 2.387877941131592s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.48761582374572754s
Reputation | Calculation of the PageRank for Geospatial World  took 0.02130579948425293s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0005457401275634766s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00010943412780761719s
Believability | Calculation of trust value for Geospatial World  took 1.2636184692382812e-05s
INFO | --- Analysis for Geospatial World  took 6.702176809310913s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.6212015151977539s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.4310879707336426s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.33853840827941895s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.018248796463012695s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0005342960357666016s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00014472007751464844s
Interoperability | Check the re-using of existing vocabs for GeoSpecies Knowledge Base took 10.996448040008545s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 1.2636184692382812e-05s
INFO | --- Analysis for GeoSpecies Knowledge Base took 19.037514448165894s
Availability | SPARQL endpoint availability check for GeoWordNet took 8.869171142578125e-05s
Availability | VoID file availability check for GeoWordNet took 0.545426607131958s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.30726122856140137s
Reputation | Calculation of the PageRank for GeoWordNet took 0.01951909065246582s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0005421638488769531s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 5.4836273193359375e-05s
Believability | Calculation of trust value for GeoWordNet took 1.1920928955078125e-05s
INFO | --- Analysis for GeoWordNet took 12.024830341339111s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 30.24639368057251s
Availability | VoID file availability check for German labor law thesaurus took 20.001866340637207s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.38459253311157227s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.018208742141723633s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0005261898040771484s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 8.535385131835938e-05s
Believability | Calculation of trust value for German labor law thesaurus took 1.1205673217773438e-05s
INFO | --- Analysis for German labor law thesaurus took 102.90044975280762s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 8.463859558105469e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 8.106231689453125e-06s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.33965444564819336s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.019359111785888672s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0005307197570800781s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.1961669921875e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 1.3113021850585938e-05s
INFO | --- Analysis for Linked Old Germanic Dictionaries took 2.725663900375366s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.8497498035430908s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.38704824447631836s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.30881166458129883s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.018889188766479492s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0005300045013427734s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.202957153320312e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.1444091796875e-05s
INFO | --- Analysis for TheSoz Thesaurus for the Social Sciences (GESIS) took 5.777975559234619s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 1.0243258476257324s
Availability | VoID file availability check for Art & Architecture Thesaurus took 1.0299503803253174s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.6083250045776367s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.0193173885345459s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0005404949188232422s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.176399230957031e-05s
Interoperability | Check the re-using of existing vocabs for Art & Architecture Thesaurus took 4.0531158447265625e-06s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for Art & Architecture Thesaurus took 17.29118776321411s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.371070146560669s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 1.1689064502716064s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.3287687301635742s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.01861572265625s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0005612373352050781s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.340576171875e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 1.1920928955078125e-05s
INFO | --- Analysis for The Getty Thesaurus of Geographic Names took 15.886775493621826s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 6.749828577041626s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.9400222301483154s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 1.8274104595184326s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.018611669540405273s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0005316734313964844s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 1.3589859008789062e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 1.0013580322265625e-05s
INFO | --- Analysis for Gipuzkoa Demografia took 28.846741199493408s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 8.96453857421875e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.9167566299438477s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.3550601005554199s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.018699169158935547s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0005199909210205078s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 1.3589859008789062e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 1.1920928955078125e-05s
INFO | --- Analysis for Glastonbury 2011 Programme took 7.5512518882751465s
Availability | SPARQL endpoint availability check for Global Change Information System took 0.47736525535583496s
Availability | VoID file availability check for Global Change Information System took 6.67572021484375e-06s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.32593870162963867s
Reputation | Calculation of the PageRank for Global Change Information System took 0.018886566162109375s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0005304813385009766s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 1.3828277587890625e-05s
Believability | Calculation of trust value for Global Change Information System took 1.1444091796875e-05s
INFO | --- Analysis for Global Change Information System took 3.8194406032562256s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 8.821487426757812e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.13915705680847168s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.35846495628356934s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.0187222957611084s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0005409717559814453s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 4.601478576660156e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 1.1205673217773438e-05s
INFO | --- Analysis for Global Hunger Index (2011) took 2.519275188446045s
Availability | SPARQL endpoint availability check for Glottolog took 8.940696716308594e-05s
Availability | VoID file availability check for Glottolog took 0.4866490364074707s
Completeness | Calculation of interlinking completeness for Glottolog took 0.44591450691223145s
Reputation | Calculation of the PageRank for Glottolog took 0.018372774124145508s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0005469322204589844s
Interlinking | Calculation of Clustering coefficient for Glottolog took 5.1975250244140625e-05s
Believability | Calculation of trust value for Glottolog took 1.33514404296875e-05s
INFO | --- Analysis for Glottolog took 7.7829506397247314s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 8.606910705566406e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 1.0162813663482666s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.3260364532470703s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.018677949905395508s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0005261898040771484s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00011134147644042969s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 1.1444091796875e-05s
INFO | --- Analysis for GNOSS.com, a Social and Semantic Platform took 9.342653036117554s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 8.845329284667969e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.005922079086303711s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.46396636962890625s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.018614530563354492s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.0005381107330322266s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 1.33514404296875e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 1.049041748046875e-05s
INFO | --- Analysis for GNUsocial social.umeahackerspace.se took 2.195207118988037s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 9.012222290039062e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 3.337860107421875e-06s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.29584574699401855s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.020651578903198242s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0005562305450439453s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.3589859008789062e-05s
Believability | Calculation of trust value for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.239776611328125e-05s
INFO | --- Analysis for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 13.82505989074707s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 8.726119995117188e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 8.106231689453125e-06s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.3556394577026367s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.018237829208374023s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0005414485931396484s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.602836608886719e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 1.3828277587890625e-05s
INFO | --- Analysis for General Ontology of Linguistic Description took 3.7224009037017822s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 8.7738037109375e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.010408878326416016s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.4710240364074707s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.018401384353637695s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0005490779876708984s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.723403930664062e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 1.239776611328125e-05s
INFO | --- Analysis for GoogleArt wrapper took 2.303807020187378s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.10296249389648438s
Availability | VoID file availability check for GovAgriBus Denmark took 1.0728836059570312e-05s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.360156774520874s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.02036428451538086s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0005297660827636719s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.647804260253906e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 1.2636184692382812e-05s
INFO | --- Analysis for GovAgriBus Denmark took 34.68851685523987s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 0.8580436706542969s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.2565631866455078s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.3017873764038086s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.018825531005859375s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0005359649658203125s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 8.392333984375e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for GovWILD - Government Web Integration for Linked Data took 4.5681376457214355s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 3.2099146842956543s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 1.9055442810058594s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.2927372455596924s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.01833939552307129s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0005362033843994141s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 9.274482727050781e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 8.821487426757812e-06s
INFO | --- Analysis for GovTrack.us U.S Congress Legislative Data took 15.115893363952637s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 9.322166442871094e-05s
Availability | VoID file availability check for greek-administrative-geography took 9.059906005859375e-06s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 1.412292242050171s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.01842474937438965s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.000576019287109375s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 6.151199340820312e-05s
Believability | Calculation of trust value for greek-administrative-geography took 1.239776611328125e-05s
INFO | --- Analysis for greek-administrative-geography took 14.406923055648804s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.12620806694030762s
Availability | VoID file availability check for Greek Wordnet took 7.3909759521484375e-06s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.4628932476043701s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.01912379264831543s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0005331039428710938s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.291534423828125e-05s
Believability | Calculation of trust value for Greek Wordnet took 1.3828277587890625e-05s
INFO | --- Analysis for Greek Wordnet took 2.3793084621429443s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 1.3721444606781006s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.33379149436950684s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.39934563636779785s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.021632909774780273s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0005209445953369141s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.534027099609375e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.1920928955078125e-05s
INFO | --- Analysis for Greek Children Art  Museum dataset took 9.093882083892822s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 0.00011038780212402344s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 1.781557321548462s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.3497202396392822s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.018721342086791992s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0005247592926025391s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 9.608268737792969e-05s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 1.1682510375976562e-05s
INFO | --- Analysis for Green Competitiveness (GNOSS) took 8.162610054016113s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 1.5013561248779297s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 1.2983992099761963s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.36106109619140625s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.01791214942932129s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0005202293395996094s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.696846008300781e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 1.2636184692382812e-05s
INFO | --- Analysis for Accommodations in Piedmont (LinkedOpenData.it) took 4.76924729347229s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.7423884868621826s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.357017993927002s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.4793086051940918s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.02575969696044922s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0005304813385009766s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 7.605552673339844e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 8.821487426757812e-06s
INFO | --- Analysis for Accommodations in Tuscany (LinkedOpenData.it) took 4.3023457527160645s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.1438136100769043s
Availability | VoID file availability check for Geological Timescale took 0.39523816108703613s
Extra | Recovery of all triples for Geological Timescale took 12.466000318527222s
Performance | Total latancy measurement for Geological Timescale took 5.1362504959106445s
Amount of data | Number of triples check for Geological Timescale took 1.13741135597229s
Interoperability | New terms check for Geological Timescale took 2.2473878860473633s
Versatility | Languages check for Geological Timescale took 1.3094995021820068s
Interpretability | Number of blank nodes check for Geological Timescale took 1.159444808959961s
Security | Check HTTPS for Geological Timescale took 2.030407667160034s
Interpretability | RDF structures check for Geological Timescale took 1.0731122493743896s
Versatility | Serialization formats check for Geological Timescale took 1.0538883209228516s
Availability | RDF dump link check for Geological Timescale took 1.9547538757324219s
License | MR license check for Geological Timescale took 1.0655252933502197s
License | HR license check for Geological Timescale took 1.1093297004699707s
Amount of data | Number of property check for Geological Timescale took 1.0804877281188965s
Understandability | Number of label check for Geological Timescale took 1.1017849445343018s
Understandability | URI regex check for Geological Timescale took 2.1102864742279053s
Understandability | Vocabs check for Geological Timescale took 1.0616121292114258s
Verifiability | Authors check for Geological Timescale took 1.0605385303497314s
Verifiability | Publishers check for Geological Timescale took 1.0388121604919434s
Performance | Throughput check for Geological Timescale took 10.313921451568604s
Amount of data | Check the number of entities for Geological Timescale took 0.021655559539794922s
Verifiability | Contribs. check for Geological Timescale took 1.0677030086517334s
Interlinking | sameAs chians check for Geological Timescale took 1.061283826828003s
Interlinking | skos check for Geological Timescale took 1.0278172492980957s
Interlinking | skos check for Geological Timescale took 1.0512564182281494s
Timeliness | dataset update frequency check for Geological Timescale took 1.011228322982788s
Currency | Creation date check for Geological Timescale took 1.0616378784179688s
Currency | Modification date check for Geological Timescale took 1.043409824371338s
Rep.Conc. | URIs length for Geological Timescale took 5.3677978515625s
Interoperability | New vocabularies check for Geological Timescale took 1.967667579650879s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 1.0859830379486084s
Accuracy | Check Functional Property for Geological Timescale took 1.07041335105896s
Accuracy | Check Inverse Functional Property for Geological Timescale took 1.0252423286437988s
Accuracy | Check Empty annotation labels for Geological Timescale took 4.2126617431640625s
Accuracy | Check White space in annotation for Geological Timescale took 0.016223907470703125s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07323670387268066s
Consistency | Disjoint class check for Geological Timescale took 1.0390121936798096s
Consistency | Check Misplaced properties for Geological Timescale took 2.094400405883789s
Consistency | Misplaced classes for Geological Timescale took 1.2161192893981934s
Consistency | Check Ontology hijacking for Geological Timescale took 4.225740432739258s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.1385619640350342s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 2.2224068641662598s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.04872441291809082s
Conciseness | Check Intensional conciseness for Geological Timescale took 1.5657546520233154s
Security | Sign check for Geological Timescale took 1.0386056900024414s
Availability | Check URIs Dereferenciability for Geological Timescale took 3.3791446685791016s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.6007518768310547s
Reputation | Calculation of the PageRank for Geological Timescale took 0.017604827880859375s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0005095005035400391s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 6.818771362304688e-05s
Interoperability | Check the re-using of existing vocabs for Geological Timescale took 2.542802333831787s
Believability | Calculation of trust value for Geological Timescale took 1.2159347534179688e-05s
INFO | --- Analysis for Geological Timescale took 149.98711800575256s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 4.935264587402344e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.39165472984313965s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 1.1518220901489258s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.018245697021484375s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0005319118499755859s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 4.124641418457031e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 5.841255187988281e-05s
INFO | --- Analysis for Geological Timescale Ontology took 8.142985820770264s
Availability | SPARQL endpoint availability check for GUTSTOK  took 7.605552673339844e-05s
Availability | VoID file availability check for GUTSTOK  took 3.5762786865234375e-06s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 3.2325167655944824s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.01860499382019043s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 1.239776611328125e-05s
Believability | Calculation of trust value for GUTSTOK  took 7.152557373046875e-06s
INFO | --- Analysis for GUTSTOK  took 9.087440013885498s
Availability | SPARQL endpoint availability check for Project Gutenberg took 9.226799011230469e-05s
Availability | VoID file availability check for Project Gutenberg took 1.2346699237823486s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 1.6032605171203613s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.018018007278442383s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0005233287811279297s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 6.628036499023438e-05s
Believability | Calculation of trust value for Project Gutenberg took 6.9141387939453125e-06s
INFO | --- Analysis for Project Gutenberg took 14.507112741470337s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 4.315376281738281e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.38073277473449707s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.3420732021331787s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.018449783325195312s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0005152225494384766s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.337860107421875e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 1.0728836059570312e-05s
INFO | --- Analysis for Global WordNet Association Interlingual Index took 6.886190891265869s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 30.559941291809082s
Availability | VoID file availability check for HCLS Knowledge Base took 20.10399341583252s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.6843545436859131s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.01833820343017578s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0005240440368652344s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 1.811981201171875e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 1.0728836059570312e-05s
INFO | --- Analysis for HCLS Knowledge Base took 65.9721519947052s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 9.703636169433594e-05s
Availability | VoID file availability check for HealthCare Ontology took 4.76837158203125e-06s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 2.3415744304656982s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.017841577529907227s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0005350112915039062s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.790855407714844e-05s
Believability | Calculation of trust value for HealthCare Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for HealthCare Ontology took 11.318828582763672s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 0.00015807151794433594s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 7.152557373046875e-06s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.35741090774536133s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.018964529037475586s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0005233287811279297s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 6.031990051269531e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 1.0728836059570312e-05s
INFO | --- Analysis for Meriterm Heart Failure Multilingual Terminology took 2.3286802768707275s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.678475856781006s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 2.352898597717285s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.31040000915527344s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.018151283264160156s
Interlinking | Calculation of Degree of Connection for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0005180835723876953s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 3.600120544433594e-05s
Believability | Calculation of trust value for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 1.1205673217773438e-05s
INFO | --- Analysis for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 102.39529824256897s
Availability | SPARQL endpoint availability check for Hedatuz took 0.2947962284088135s
Availability | VoID file availability check for Hedatuz took 0.1111910343170166s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.31036853790283203s
Reputation | Calculation of the PageRank for Hedatuz took 0.020060062408447266s
Interlinking | Calculation of Degree of Connection for Hedatuz took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Hedatuz took 0.0005099773406982422s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 3.695487976074219e-05s
Believability | Calculation of trust value for Hedatuz took 1.0728836059570312e-05s
INFO | --- Analysis for Hedatuz took 2.6076481342315674s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 3.376105546951294s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.45485687255859375s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.3150167465209961s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.018206357955932617s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0005362033843994141s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.0001220703125s
Believability | Calculation of trust value for Hellenic Fire Brigade took 8.106231689453125e-06s
INFO | --- Analysis for Hellenic Fire Brigade took 12.002172231674194s
Availability | SPARQL endpoint availability check for Hellenic Police took 3.1051223278045654s
Availability | VoID file availability check for Hellenic Police took 0.43256378173828125s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.33815884590148926s
Reputation | Calculation of the PageRank for Hellenic Police took 0.018117904663085938s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0005161762237548828s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00012493133544921875s
Believability | Calculation of trust value for Hellenic Police took 9.059906005859375e-06s
INFO | --- Analysis for Hellenic Police took 14.577911376953125s
Availability | SPARQL endpoint availability check for Homologene took 8.845329284667969e-05s
Availability | VoID file availability check for Homologene took 3.814697265625e-06s
Completeness | Calculation of interlinking completeness for Homologene took 0.3034067153930664s
Reputation | Calculation of the PageRank for Homologene took 0.01839756965637207s
Interlinking | Calculation of Degree of Connection for Homologene took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Homologene took 0.0005168914794921875s
Interlinking | Calculation of Clustering coefficient for Homologene took 1.3113021850585938e-05s
Believability | Calculation of trust value for Homologene took 1.1444091796875e-05s
INFO | --- Analysis for Homologene took 13.827119827270508s
Availability | SPARQL endpoint availability check for gseg took 8.487701416015625e-05s
Availability | VoID file availability check for gseg took 0.5471789836883545s
Completeness | Calculation of interlinking completeness for gseg took 0.3721487522125244s
Reputation | Calculation of the PageRank for gseg took 0.018254756927490234s
Interlinking | Calculation of Degree of Connection for gseg took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for gseg took 0.0005278587341308594s
Interlinking | Calculation of Clustering coefficient for gseg took 1.0967254638671875e-05s
Believability | Calculation of trust value for gseg took 1.049041748046875e-05s
INFO | --- Analysis for gseg took 3.521784782409668s
Availability | SPARQL endpoint availability check for Noticias Universia took 0.42546725273132324s
Availability | VoID file availability check for Noticias Universia took 0.4963364601135254s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.32106518745422363s
Reputation | Calculation of the PageRank for Noticias Universia took 0.01818370819091797s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0005257129669189453s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 1.239776611328125e-05s
Believability | Calculation of trust value for Noticias Universia took 1.0013580322265625e-05s
INFO | --- Analysis for Noticias Universia took 2.898669958114624s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 4.2438507080078125e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 7.62939453125e-06s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.3336608409881592s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.018190860748291016s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0005218982696533203s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.3113021850585938e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.0967254638671875e-05s
INFO | --- Analysis for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 3.4807283878326416s
Availability | SPARQL endpoint availability check for RoadTrb took 8.058547973632812e-05s
Availability | VoID file availability check for RoadTrb took 5.0067901611328125e-06s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.3192119598388672s
Reputation | Calculation of the PageRank for RoadTrb took 0.01795673370361328s
Interlinking | Calculation of Degree of Connection for RoadTrb took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.0005168914794921875s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 1.2874603271484375e-05s
Believability | Calculation of trust value for RoadTrb took 1.0728836059570312e-05s
INFO | --- Analysis for RoadTrb took 2.538325786590576s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 9.1552734375e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 4.0531158447265625e-06s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.33783674240112305s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.018958330154418945s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0005872249603271484s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 1.2636184692382812e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for Relations for Reusing (R4R) Ontology took 2.205068349838257s
Availability | SPARQL endpoint availability check for CEDICT took 8.177757263183594e-05s
Availability | VoID file availability check for CEDICT took 5.9604644775390625e-06s
Completeness | Calculation of interlinking completeness for CEDICT took 0.40033817291259766s
Reputation | Calculation of the PageRank for CEDICT took 0.020063400268554688s
Interlinking | Calculation of Degree of Connection for CEDICT took 3.170967102050781e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.0006656646728515625s
Interlinking | Calculation of Clustering coefficient for CEDICT took 1.3589859008789062e-05s
Believability | Calculation of trust value for CEDICT took 1.1205673217773438e-05s
INFO | --- Analysis for CEDICT took 2.08945894241333s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 8.344650268554688e-05s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 5.4836273193359375e-06s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.5197522640228271s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.018095731735229492s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0006368160247802734s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.4781951904296875e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.1920928955078125e-05s
INFO | --- Analysis for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 2.508289098739624s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.082389831542969e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 5.9604644775390625e-06s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.34744834899902344s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0180966854095459s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005230903625488281s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.3589859008789062e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1444091796875e-05s
INFO | --- Analysis for Covid19 Impact on Banking ontology (Covid19-IBO) took 2.191979169845581s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 8.487701416015625e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 6.198883056640625e-06s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.3744776248931885s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.019189834594726562s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0005390644073486328s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 1.3113021850585938e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.1205673217773438e-05s
INFO | --- Analysis for Greek Children Art  Museum dataset took 3.375068187713623s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 8.440017700195312e-05s
Availability | VoID file availability check for Writer Luigi Usai took 5.0067901611328125e-06s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.4463350772857666s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.018303632736206055s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0005469322204589844s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 1.3113021850585938e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 1.1205673217773438e-05s
INFO | --- Analysis for Writer Luigi Usai took 2.487757921218872s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 4.3392181396484375e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 6.4373016357421875e-06s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.3464939594268799s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.018056392669677734s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0005156993865966797s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 1.239776611328125e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 5.888938903808594e-05s
INFO | --- Analysis for Hua Hin Health Tourism Data Set took 7.743471384048462s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 1.4833390712738037s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 1.184370756149292s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.3380587100982666s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.018410682678222656s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0005269050598144531s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 1.2636184692382812e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 1.0967254638671875e-05s
INFO | --- Analysis for University of Huddersfield -- Circulation and Recommendation Data took 5.762659549713135s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 0.5532371997833252s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.2905571460723877s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.4795806407928467s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.019495248794555664s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0005488395690917969s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00012040138244628906s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 1.1205673217773438e-05s
INFO | --- Analysis for Hungarian National Library (NSZL) catalog took 4.831275701522827s
Availability | SPARQL endpoint availability check for IATE RDF took 8.7738037109375e-05s
Availability | VoID file availability check for IATE RDF took 7.62939453125e-06s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.3092191219329834s
Reputation | Calculation of the PageRank for IATE RDF took 0.017994165420532227s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0005450248718261719s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.743171691894531e-05s
Believability | Calculation of trust value for IATE RDF took 1.1920928955078125e-05s
INFO | --- Analysis for IATE RDF took 2.9122793674468994s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 0.5322422981262207s
Availability | VoID file availability check for IATI as Linked Data took 9.059906005859375e-06s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.5081527233123779s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.018310546875s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0005192756652832031s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.96453857421875e-05s
Believability | Calculation of trust value for IATI as Linked Data took 1.1444091796875e-05s
INFO | --- Analysis for IATI as Linked Data took 6.061923027038574s
Availability | SPARQL endpoint availability check for ICANE took 2.157536745071411s
Availability | VoID file availability check for ICANE took 0.3196544647216797s
Completeness | Calculation of interlinking completeness for ICANE took 0.3375101089477539s
Reputation | Calculation of the PageRank for ICANE took 0.018083572387695312s
Interlinking | Calculation of Degree of Connection for ICANE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICANE took 0.0005438327789306641s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.440017700195312e-05s
Believability | Calculation of trust value for ICANE took 9.059906005859375e-06s
INFO | --- Analysis for ICANE took 8.848481893539429s
Availability | SPARQL endpoint availability check for ichoose took 0.1291656494140625s
Availability | VoID file availability check for ichoose took 0.33600854873657227s
Completeness | Calculation of interlinking completeness for ichoose took 0.778411865234375s
Reputation | Calculation of the PageRank for ichoose took 0.01814579963684082s
Interlinking | Calculation of Degree of Connection for ichoose took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0005183219909667969s
Interlinking | Calculation of Clustering coefficient for ichoose took 7.581710815429688e-05s
Interoperability | Check the re-using of existing vocabs for ichoose took 1.6689300537109375e-06s
Believability | Calculation of trust value for ichoose took 1.2159347534179688e-05s
INFO | --- Analysis for ichoose took 58.66360950469971s
Availability | SPARQL endpoint availability check for Identifiers.org took 0.3086965084075928s
Availability | VoID file availability check for Identifiers.org took 0.38526177406311035s
Completeness | Calculation of interlinking completeness for Identifiers.org took 0.3215177059173584s
Reputation | Calculation of the PageRank for Identifiers.org took 0.019366979598999023s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0006706714630126953s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 5.221366882324219e-05s
Believability | Calculation of trust value for Identifiers.org took 1.239776611328125e-05s
INFO | --- Analysis for Identifiers.org took 3.5281381607055664s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 8.749961853027344e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.7244453430175781s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.3680734634399414s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.018447399139404297s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0005145072937011719s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.486343383789062e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 1.1205673217773438e-05s
INFO | --- Analysis for IdRef: Sudoc authority data took 14.357152938842773s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 40.88409972190857s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.7521288394927979s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.43391895294189453s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.018137216567993164s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0005221366882324219s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 4.673004150390625e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 1.2874603271484375e-05s
INFO | --- Analysis for Intercontinental Dictionary Series took 104.70664024353027s
Availability | SPARQL endpoint availability check for ietflang took 8.797645568847656e-05s
Availability | VoID file availability check for ietflang took 1.4781951904296875e-05s
Completeness | Calculation of interlinking completeness for ietflang took 0.3335275650024414s
Reputation | Calculation of the PageRank for ietflang took 0.018200397491455078s
Interlinking | Calculation of Degree of Connection for ietflang took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ietflang took 0.0005459785461425781s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.9591064453125e-05s
Believability | Calculation of trust value for ietflang took 1.2874603271484375e-05s
INFO | --- Analysis for ietflang took 12.68531322479248s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 3.331141233444214s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 8.106231689453125e-06s
Extra | Recovery of all triples for Test Site, LOD Lab 317 took 8.186497926712036s
Performance | Total latancy measurement for Test Site, LOD Lab 317 took 9.424914598464966s
Amount of data | Number of triples check for Test Site, LOD Lab 317 took 10.8877112865448s
Interoperability | New terms check for Test Site, LOD Lab 317 took 7.822946310043335s
Versatility | Languages check for Test Site, LOD Lab 317 took 61.91456747055054s
Interpretability | Number of blank nodes check for Test Site, LOD Lab 317 took 1.96340012550354s
Security | Check HTTPS for Test Site, LOD Lab 317 took 1.26613187789917s
Interpretability | RDF structures check for Test Site, LOD Lab 317 took 2.270796060562134s
Versatility | Serialization formats check for Test Site, LOD Lab 317 took 1.903883934020996s
Availability | RDF dump link check for Test Site, LOD Lab 317 took 1.928290605545044s
License | MR license check for Test Site, LOD Lab 317 took 1.987182378768921s
License | HR license check for Test Site, LOD Lab 317 took 2.206650972366333s
Amount of data | Number of property check for Test Site, LOD Lab 317 took 1.9147956371307373s
Understandability | Number of label check for Test Site, LOD Lab 317 took 2.121765375137329s
Understandability | URI regex check for Test Site, LOD Lab 317 took 3.9251327514648438s
Understandability | Vocabs check for Test Site, LOD Lab 317 took 1.9493956565856934s
Verifiability | Authors check for Test Site, LOD Lab 317 took 4.5516111850738525s
Verifiability | Publishers check for Test Site, LOD Lab 317 took 3.8550708293914795s
Performance | Throughput check for Test Site, LOD Lab 317 took 18.886884212493896s
Amount of data | Check the number of entities for Test Site, LOD Lab 317 took 3.838539123535156e-05s
Verifiability | Contribs. check for Test Site, LOD Lab 317 took 1.9269347190856934s
Interlinking | sameAs chians check for Test Site, LOD Lab 317 took 1.900601863861084s
Interlinking | skos check for Test Site, LOD Lab 317 took 2.0270276069641113s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.8827884197235107s
Timeliness | dataset update frequency check for Test Site, LOD Lab 317 took 2.1047017574310303s
Currency | Creation date check for Test Site, LOD Lab 317 took 1.958261251449585s
Currency | Modification date check for Test Site, LOD Lab 317 took 1.9226667881011963s
Rep.Conc. | URIs length for Test Site, LOD Lab 317 took 30.841554403305054s
Interoperability | New vocabularies check for Test Site, LOD Lab 317 took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Test Site, LOD Lab 317 took 2.0132863521575928s
Accuracy | Check Functional Property for Test Site, LOD Lab 317 took 2.128638505935669s
Accuracy | Check Inverse Functional Property for Test Site, LOD Lab 317 took 2.0178093910217285s
Accuracy | Check Empty annotation labels for Test Site, LOD Lab 317 took 7.570034742355347s
Accuracy | Check White space in annotation for Test Site, LOD Lab 317 took 0.030798912048339844s
Accuracy | Check Datatype consistency for Test Site, LOD Lab 317 took 0.029855012893676758s
Consistency | Disjoint class check for Test Site, LOD Lab 317 took 1.9835867881774902s
Consistency | Check Misplaced properties for Test Site, LOD Lab 317 took 25.618298768997192s
Consistency | Misplaced classes for Test Site, LOD Lab 317 took 2.4280760288238525s
Consistency | Check Ontology hijacking for Test Site, LOD Lab 317 took 7.5742270946502686s
Consistency | Check Invalid usage of undefined classes for Test Site, LOD Lab 317 took 1.1222467422485352s
Consistency | Check Invalid usage of undefined properties for Test Site, LOD Lab 317 took 24.27685832977295s
Conciseness | Check Extensional conciseness for Test Site, LOD Lab 317 took 0.031232833862304688s
Conciseness | Check Intensional conciseness for Test Site, LOD Lab 317 took 2.633187770843506s
Security | Sign check for Test Site, LOD Lab 317 took 2.0559489727020264s
Availability | Check URIs Dereferenciability for Test Site, LOD Lab 317 took 3.7684688568115234s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.7144513130187988s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.018538951873779297s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0005533695220947266s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 2.2411346435546875e-05s
Interoperability | Check the re-using of existing vocabs for Test Site, LOD Lab 317 took 1.430511474609375e-06s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 1.4066696166992188e-05s
INFO | --- Analysis for Test Site, LOD Lab 317 took 534.6924438476562s
Availability | SPARQL endpoint availability check for im@sparql took 7.686929702758789s
Availability | VoID file availability check for im@sparql took 5.078638553619385s
Completeness | Calculation of interlinking completeness for im@sparql took 0.3166630268096924s
Reputation | Calculation of the PageRank for im@sparql took 0.018185853958129883s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0005025863647460938s
Interlinking | Calculation of Clustering coefficient for im@sparql took 2.1457672119140625e-05s
Believability | Calculation of trust value for im@sparql took 1.0013580322265625e-05s
INFO | --- Analysis for im@sparql took 15.783204555511475s
Availability | SPARQL endpoint availability check for imagery bailingniao took 4.029273986816406e-05s
Availability | VoID file availability check for imagery bailingniao took 7.152557373046875e-06s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.37053394317626953s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.018198013305664062s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0005311965942382812s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 1.2159347534179688e-05s
Believability | Calculation of trust value for imagery bailingniao took 1.1920928955078125e-05s
INFO | --- Analysis for imagery bailingniao took 2.0786216259002686s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.1929266452789307s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 1.3562185764312744s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 20.93884301185608s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.5291075706481934s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 9.85907506942749s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.179680347442627s
Versatility | Languages check for Imagesnippets Image Descriptions took 19.510040521621704s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.457394123077393s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.7177059650421143s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7346076965332031s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.7807390689849854s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7485857009887695s
License | MR license check for Imagesnippets Image Descriptions took 0.7726616859436035s
License | HR license check for Imagesnippets Image Descriptions took 30.76054048538208s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.7250337600708008s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.613128662109375s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.449906826019287s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.7282805442810059s
Verifiability | Authors check for Imagesnippets Image Descriptions took 1.6661245822906494s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.7567675113677979s
Performance | Throughput check for Imagesnippets Image Descriptions took 14.051002979278564s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 8.559226989746094e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.7387850284576416s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.7718710899353027s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.769035816192627s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7167975902557373s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.7564499378204346s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.4473786354064941s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.447303295135498s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 33.183621406555176s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.7161209583282471s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.7471301555633545s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.7157835960388184s
Accuracy | Check Empty annotation labels for Imagesnippets Image Descriptions took 12.749857902526855s
Accuracy | Check White space in annotation for Imagesnippets Image Descriptions took 2.2891392707824707s
Accuracy | Check Datatype consistency for Imagesnippets Image Descriptions took 4.311213970184326s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.7677710056304932s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.791495084762573s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 3.9138917922973633s
Consistency | Check Invalid usage of undefined classes for Imagesnippets Image Descriptions took 1.2080833911895752s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.2071692943573s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 2.844572067260742s
Security | Sign check for Imagesnippets Image Descriptions took 0.6993041038513184s
Availability | Check URIs Dereferenciability for Imagesnippets Image Descriptions took 12.36908769607544s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.3970301151275635s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.01822519302368164s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0005269050598144531s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 9.34600830078125e-05s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 1.1920928955078125e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 1.5020370483398438e-05s
INFO | --- Analysis for Imagesnippets Image Descriptions took 378.67934370040894s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.09442877769470215s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 7.867813110351562e-06s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.30216193199157715s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.018571853637695312s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0005252361297607422s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 8.940696716308594e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for International Monetary Fund (IMF) Linked Data took 2.2073397636413574s
Availability | SPARQL endpoint availability check for IMGpedia took 1.9814612865447998s
Availability | VoID file availability check for IMGpedia took 2.131892442703247s
Extra | Recovery of all triples for IMGpedia took 72.75476598739624s
Performance | Total latancy measurement for IMGpedia took 5.315739393234253s
Amount of data | Number of triples check for IMGpedia took 124.79744911193848s
Interoperability | New terms check for IMGpedia took 147.8075933456421s
Versatility | Languages check for IMGpedia took 300.97242522239685s
Interpretability | Number of blank nodes check for IMGpedia took 1.0832841396331787s
Security | Check HTTPS for IMGpedia took 0.6421451568603516s
Interpretability | RDF structures check for IMGpedia took 1.125610113143921s
Versatility | Serialization formats check for IMGpedia took 1.0983588695526123s
Availability | RDF dump link check for IMGpedia took 1.0865256786346436s
License | MR license check for IMGpedia took 1.112823486328125s
License | HR license check for IMGpedia took 300.89504408836365s
Amount of data | Number of property check for IMGpedia took 1.103107213973999s
Understandability | Number of label check for IMGpedia took 56.16908073425293s
Understandability | URI regex check for IMGpedia took 2.1934974193573s
Understandability | Vocabs check for IMGpedia took 1.0617835521697998s
Verifiability | Authors check for IMGpedia took 1.0653140544891357s
Verifiability | Publishers check for IMGpedia took 1.0903725624084473s
Performance | Throughput check for IMGpedia took 10.541719198226929s
Amount of data | Check the number of entities for IMGpedia took 3.8623809814453125e-05s
Verifiability | Contribs. check for IMGpedia took 1.0503065586090088s
Interlinking | sameAs chians check for IMGpedia took 1.7286269664764404s
Interlinking | skos check for IMGpedia took 1.0662508010864258s
Interlinking | skos check for IMGpedia took 1.0400311946868896s
Timeliness | dataset update frequency check for IMGpedia took 1.119591474533081s
Currency | Creation date check for IMGpedia took 1.0724174976348877s
Currency | Modification date check for IMGpedia took 1.0996112823486328s
Rep.Conc. | URIs length for IMGpedia took 499.89200377464294s
Interoperability | New vocabularies check for IMGpedia took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for IMGpedia took 1.0619254112243652s
Accuracy | Check Functional Property for IMGpedia took 1.0819401741027832s
Accuracy | Check Inverse Functional Property for IMGpedia took 1.0887439250946045s
Accuracy | Check Empty annotation labels for IMGpedia took 50.50504493713379s
Accuracy | Check White space in annotation for IMGpedia took 2.585622549057007s
Consistency | Disjoint class check for IMGpedia took 1.1459097862243652s
Consistency | Check Misplaced properties for IMGpedia took 303.1277139186859s
Consistency | Misplaced classes for IMGpedia took 3.0930583477020264s
Consistency | Check Ontology hijacking for IMGpedia took 28.4159152507782s
Consistency | Check Invalid usage of undefined properties for IMGpedia took 302.14363265037537s
Conciseness | Check Extensional conciseness for IMGpedia took 0.00021028518676757812s
Conciseness | Check Intensional conciseness for IMGpedia took 3.388371706008911s
Security | Sign check for IMGpedia took 1.0839285850524902s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.8380820751190186s
Reputation | Calculation of the PageRank for IMGpedia took 0.019136667251586914s
Interlinking | Calculation of Degree of Connection for IMGpedia took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for IMGpedia took 0.0005352497100830078s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 2.002716064453125e-05s
Interoperability | Check the re-using of existing vocabs for IMGpedia took 1.9073486328125e-06s
Believability | Calculation of trust value for IMGpedia took 8.106231689453125e-06s
