Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0001010894775390625s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.3552877902984619s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.6380820274353027s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.00037288665771484375s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 5.0067901611328125e-06s
INFO | --- Analysis for 0080-3626 took 6.613127708435059s
Availability | SPARQL endpoint availability check for 土地利用图 took 4.220008850097656e-05s
Availability | VoID file availability check for 土地利用图 took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.26946210861206055s
Reputation | Calculation of the PageRank for 土地利用图 took 0.0197904109954834s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 2.8848648071289062e-05s
Believability | Calculation of trust value for 土地利用图 took 9.775161743164062e-06s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 2.8619635105133057s
Availability | SPARQL endpoint availability check for 113322 took 4.291534423828125e-05s
Availability | VoID file availability check for 113322 took 0.0006532669067382812s
Completeness | Calculation of interlinking completeness for 113322 took 0.24711847305297852s
Reputation | Calculation of the PageRank for 113322 took 0.0203702449798584s
Interlinking | Calculation of Degree of Connection for 113322 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 113322 took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for 113322 took 2.9325485229492188e-05s
Believability | Calculation of trust value for 113322 took 5.245208740234375e-06s
INFO | --- Analysis for 11 took 4.714810371398926s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 4.1961669921875e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.00021076202392578125s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.25574398040771484s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.020019054412841797s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 2.7418136596679688e-05s
Believability | Calculation of trust value for Korepetycje Buki took 5.0067901611328125e-06s
INFO | --- Analysis for 12323 took 2.365373373031616s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.13765931129455566s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0003333091735839844s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.28285646438598633s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.02002692222595215s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 8.630752563476562e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 1.2636184692382812e-05s
INFO | --- Analysis for 2000-us-census-rdf took 2.543048858642578s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 1.8464839458465576s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.2469024658203125s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.02012467384338379s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 3.743171691894531e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 7.62939453125e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 5.997764587402344s
Availability | SPARQL endpoint availability check for Open Data Web took 1.0104010105133057s
Availability | VoID file availability check for Open Data Web took 0.00022149085998535156s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.2522139549255371s
Reputation | Calculation of the PageRank for Open Data Web took 0.019799470901489258s
Interlinking | Calculation of Degree of Connection for Open Data Web took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Data Web took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.24249267578125e-05s
Believability | Calculation of trust value for Open Data Web took 5.0067901611328125e-06s
INFO | --- Analysis for _data.odw.tw took 3.3951644897460938s
Availability | SPARQL endpoint availability check for 土地利用 took 4.38690185546875e-05s
Availability | VoID file availability check for 土地利用 took 0.00021529197692871094s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.2555577754974365s
Reputation | Calculation of the PageRank for 土地利用 took 0.0198516845703125s
Interlinking | Calculation of Degree of Connection for 土地利用 took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for 土地利用 took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 2.86102294921875e-05s
Believability | Calculation of trust value for 土地利用 took 5.7220458984375e-06s
INFO | --- Analysis for _data1.odw.tw took 2.3733139038085938s
Availability | SPARQL endpoint availability check for 土地利用模型 took 4.410743713378906e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.2701101303100586s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.02003765106201172s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 2.7894973754882812e-05s
Believability | Calculation of trust value for 土地利用模型 took 5.7220458984375e-06s
INFO | --- Analysis for _data2.odw.tw took 4.797649383544922s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.315376281738281e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2572345733642578s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.01995062828063965s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.7179718017578125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 5.4836273193359375e-06s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 3.7016077041625977s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.220008850097656e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.28436732292175293s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.019932270050048828s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 2.7894973754882812e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 6.9141387939453125e-06s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 3.1067111492156982s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 4.2438507080078125e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.24945735931396484s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.01997089385986328s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 7.3909759521484375e-06s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 2.8848648071289062e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 3.814697265625e-06s
INFO | --- Analysis for A1 took 2.8076930046081543s
Availability | SPARQL endpoint availability check for SummerOlympics took 13.709716320037842s
Availability | VoID file availability check for SummerOlympics took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.27159643173217773s
Reputation | Calculation of the PageRank for SummerOlympics took 0.019828319549560547s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.890296936035156e-05s
Believability | Calculation of trust value for SummerOlympics took 5.0067901611328125e-06s
INFO | --- Analysis for abc took 18.923563718795776s
Availability | SPARQL endpoint availability check for Test_m took 7.390975952148438e-05s
Availability | VoID file availability check for Test_m took 0.00022101402282714844s
Completeness | Calculation of interlinking completeness for Test_m took 0.2508277893066406s
Reputation | Calculation of the PageRank for Test_m took 0.01984572410583496s
Interlinking | Calculation of Degree of Connection for Test_m took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Test_m took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Test_m took 2.6941299438476562e-05s
Believability | Calculation of trust value for Test_m took 5.0067901611328125e-06s
INFO | --- Analysis for ABC took 2.7671804428100586s
Availability | SPARQL endpoint availability check for my intro took 4.124641418457031e-05s
Availability | VoID file availability check for my intro took 0.00021195411682128906s
Completeness | Calculation of interlinking completeness for my intro took 0.23928332328796387s
Reputation | Calculation of the PageRank for my intro took 0.019927501678466797s
Interlinking | Calculation of Degree of Connection for my intro took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for my intro took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for my intro took 2.6941299438476562e-05s
Believability | Calculation of trust value for my intro took 9.775161743164062e-06s
INFO | --- Analysis for abhay_intro took 2.3058035373687744s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.28835606575012207s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.0003273487091064453s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.26482391357421875s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.01992964744567871s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 9.775161743164062e-05s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for abs-linked-data took 2.6697843074798584s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 5.435943603515625e-05s
Availability | VoID file availability check for Academic Offer of UNL took 0.0002117156982421875s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.26295948028564453s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.01983189582824707s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 2.765655517578125e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 5.4836273193359375e-06s
INFO | --- Analysis for academic-offer-of-unl took 2.969224214553833s
Availability | SPARQL endpoint availability check for AcadOnto took 6.651878356933594e-05s
Availability | VoID file availability check for AcadOnto took 0.0002181529998779297s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.25234079360961914s
Reputation | Calculation of the PageRank for AcadOnto took 0.01991438865661621s
Interlinking | Calculation of Degree of Connection for AcadOnto took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 2.6941299438476562e-05s
Believability | Calculation of trust value for AcadOnto took 9.775161743164062e-06s
INFO | --- Analysis for acadonto took 2.8949897289276123s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.485113859176636s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.2482762336730957s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.019817590713500977s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.2901763916015625e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.5762786865234375e-06s
INFO | --- Analysis for acorn-sat took 36.50241732597351s
Availability | SPARQL endpoint availability check for Addgene took 6.413459777832031e-05s
Availability | VoID file availability check for Addgene took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for Addgene took 0.2472829818725586s
Reputation | Calculation of the PageRank for Addgene took 0.01996588706970215s
Interlinking | Calculation of Degree of Connection for Addgene took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Addgene took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Addgene took 4.0531158447265625e-05s
Believability | Calculation of trust value for Addgene took 5.4836273193359375e-06s
INFO | --- Analysis for addgene took 15.640371322631836s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.100799560546875e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.26926660537719727s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.019797086715698242s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 8.916854858398438e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.5974044799804688e-05s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 8.617479801177979s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.4538075923919678s
Availability | VoID file availability check for AEMET metereological dataset took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.24465656280517578s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.02074885368347168s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.600120544433594e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 5.4836273193359375e-06s
INFO | --- Analysis for aemet took 4.651750802993774s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 4.076957702636719e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0002193450927734375s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.27826666831970215s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.019971370697021484s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 3.0040740966796875e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 5.4836273193359375e-06s
INFO | --- Analysis for agenda-de-zaragoza took 2.933858871459961s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.03206324577331543s
Availability | VoID file availability check for AgriNepalData took 0.0002071857452392578s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.2635617256164551s
Reputation | Calculation of the PageRank for AgriNepalData took 0.02002096176147461s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 6.961822509765625e-05s
Believability | Calculation of trust value for AgriNepalData took 5.245208740234375e-06s
INFO | --- Analysis for agrinepaldata took 2.4518725872039795s
Availability | SPARQL endpoint availability check for AGRIS took 260.8928780555725s
Availability | VoID file availability check for AGRIS took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for AGRIS took 0.2598574161529541s
Reputation | Calculation of the PageRank for AGRIS took 0.019979476928710938s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for AGRIS took 7.82012939453125e-05s
Believability | Calculation of trust value for AGRIS took 5.9604644775390625e-06s
INFO | --- Analysis for agris took 554.0295541286469s
Availability | SPARQL endpoint availability check for AGROVOC took 0.1922454833984375s
Availability | VoID file availability check for AGROVOC took 0.0005846023559570312s
Extra | Recovery of all triples for AGROVOC took 36.01129627227783s
Performance | Total latancy measurement for AGROVOC took 0.4368758201599121s
Amount of data | Number of triples check for AGROVOC took 30.075721740722656s
Interoperability | New terms check for AGROVOC took 4.0094895362854s
Versatility | Languages check for AGROVOC took 30.072330713272095s
Interpretability | Number of blank nodes check for AGROVOC took 30.085638523101807s
Interpretability | RDF structures check for AGROVOC took 0.09076523780822754s
Versatility | Serialization formats check for AGROVOC took 0.08093810081481934s
Availability | RDF dump link check for AGROVOC took 0.08893489837646484s
License | MR license check for AGROVOC took 0.07731842994689941s
License | HR license check for AGROVOC took 0.5927841663360596s
Amount of data | Number of property check for AGROVOC took 0.10075831413269043s
Understandability | Number of label check for AGROVOC took 30.08652973175049s
Understandability | URI regex check for AGROVOC took 0.17924833297729492s
Understandability | Vocabs check for AGROVOC took 0.09423136711120605s
Verifiability | Authors check for AGROVOC took 0.08179092407226562s
Verifiability | Publishers check for AGROVOC took 0.08759665489196777s
Performance | Throughput check for AGROVOC took 10.417871236801147s
Amount of data | Check the number of entities for AGROVOC took 0.00010585784912109375s
Verifiability | Contribs. check for AGROVOC took 0.07839322090148926s
Interlinking | sameAs chians check for AGROVOC took 0.0894777774810791s
Interlinking | skos check for AGROVOC took 6.172948122024536s
Interlinking | skos check for AGROVOC took 3.697600841522217s
Timeliness | dataset update frequency check for AGROVOC took 0.09063363075256348s
Currency | Creation date check for AGROVOC took 0.17163681983947754s
Currency | Modification date check for AGROVOC took 0.1798403263092041s
Rep.Conc. | URIs length for AGROVOC took 47.00441527366638s
Interoperability | New vocabularies check for AGROVOC took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.07993578910827637s
Accuracy | Check Empty annotation labels for AGROVOC took 20.689236640930176s
Accuracy | Check White space in annotation for AGROVOC took 2.949747085571289s
Accuracy | Check Datatype consistency for AGROVOC took 4.438058376312256s
Consistency | Disjoint class check for AGROVOC took 0.0741279125213623s
Consistency | Check Misplaced properties for AGROVOC took 14.217798233032227s
Consistency | Check Ontology hijacking for AGROVOC took 30.10523509979248s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 15.990463018417358s
Conciseness | Check Extensional conciseness for AGROVOC took 2.5316717624664307s
Conciseness | Check Intensional conciseness for AGROVOC took 0.08878064155578613s
Security | Sign check for AGROVOC took 0.08527874946594238s
Availability | Check URIs Dereferenciability for AGROVOC took 3.125606060028076s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.7713284492492676s
Reputation | Calculation of the PageRank for AGROVOC took 0.019891738891601562s
Interlinking | Calculation of Degree of Connection for AGROVOC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.0001049041748046875s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.430511474609375e-06s
Believability | Calculation of trust value for AGROVOC took 5.245208740234375e-06s
INFO | --- Analysis for agrovoc took 400.4914164543152s
Availability | SPARQL endpoint availability check for AGROVOC took 4.2438507080078125e-05s
Availability | VoID file availability check for AGROVOC took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.23664093017578125s
Reputation | Calculation of the PageRank for AGROVOC took 0.01998114585876465s
Interlinking | Calculation of Degree of Connection for AGROVOC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 5.841255187988281e-05s
Believability | Calculation of trust value for AGROVOC took 7.867813110351562e-06s
INFO | --- Analysis for agrovoc-skos took 3.3453385829925537s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 1.0134105682373047s
Availability | VoID file availability check for Analytics India Magazine took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.7041246891021729s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.019935131072998047s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 3.0994415283203125e-05s
Believability | Calculation of trust value for Analytics India Magazine took 5.245208740234375e-06s
INFO | --- Analysis for AIM took 7.101409435272217s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 4.3392181396484375e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.25888633728027344s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.019932270050048828s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 2.9325485229492188e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 6.9141387939453125e-06s
INFO | --- Analysis for AISHE took 2.307534694671631s
Availability | SPARQL endpoint availability check for  equipment ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for  equipment ontology took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.29361844062805176s
Reputation | Calculation of the PageRank for  equipment ontology took 0.01980137825012207s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.0517578125e-05s
Believability | Calculation of trust value for  equipment ontology took 5.4836273193359375e-06s
INFO | --- Analysis for akash took 3.295393228530884s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 4.410743713378906e-05s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.26358675956726074s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.01994037628173828s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 2.9325485229492188e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 5.4836273193359375e-06s
INFO | --- Analysis for aksworg took 2.9118220806121826s
Availability | SPARQL endpoint availability check for AlchemyAPI took 3.910064697265625e-05s
Availability | VoID file availability check for AlchemyAPI took 0.0002090930938720703s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.28302526473999023s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.019994020462036133s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 2.8848648071289062e-05s
Believability | Calculation of trust value for AlchemyAPI took 6.4373016357421875e-06s
INFO | --- Analysis for alchemyapi took 2.9314301013946533s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 3.933906555175781e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.23578238487243652s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.020070552825927734s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 2.9325485229492188e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 6.67572021484375e-06s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 2.880054473876953s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.159787654876709s
Availability | VoID file availability check for aliada-scanbit-net took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.24558806419372559s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.02004075050354004s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.0001304149627685547s
Believability | Calculation of trust value for aliada-scanbit-net took 5.0067901611328125e-06s
INFO | --- Analysis for aliada-scanbit-net took 4.5650553703308105s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 3.910064697265625e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.00022554397583007812s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.2909884452819824s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.01998591423034668s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 2.8133392333984375e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 5.245208740234375e-06s
INFO | --- Analysis for allen-brain-atlas took 3.012012243270874s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 1.395583152770996s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0006046295166015625s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 146.34746026992798s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.7240073680877686s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.4691710472106934s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.8002758026123047s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.067503452301s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 3.9795219898223877s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 2.051727294921875s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.7113964557647705s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.8169448375701904s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.6734969615936279s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.5903384685516357s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 37.524455547332764s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.5731687545776367s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.8686003684997559s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.1152584552764893s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.570359468460083s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.6048574447631836s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.5640652179718018s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.79901671409607s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 6.818771362304688e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5519473552703857s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.5723955631256104s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 1.0785713195800781s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5620417594909668s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.6783723831176758s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.24635648727417s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.1013972759246826s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 58.10547089576721s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 2.3590288162231445s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5625638961791992s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6531491279602051s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6048407554626465s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 38.04534101486206s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.0105466842651367s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.6357011795043945s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.6158361434936523s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 11.414785146713257s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.766326189041138s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 34.35687232017517s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.3953101634979248s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 12.063429832458496s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.720442533493042s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8411052227020264s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 1.0970447063446045s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 12230.761405467987s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 1.072667121887207s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.02264857292175293s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 0.000179290771484375s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 9.298324584960938e-06s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 13011.89356637001s
Availability | SPARQL endpoint availability check for Alojamientos took 8.034706115722656e-05s
Availability | VoID file availability check for Alojamientos took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.27524471282958984s
Reputation | Calculation of the PageRank for Alojamientos took 0.02048349380493164s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 6.604194641113281e-05s
Believability | Calculation of trust value for Alojamientos took 1.3828277587890625e-05s
INFO | --- Analysis for alojamientos-zaragoza took 4.599221467971802s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.4019899368286133s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.2576756477355957s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.019961118698120117s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 4.0531158447265625e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 6.4373016357421875e-06s
INFO | --- Analysis for alpino-rdf took 4.089016437530518s
Availability | SPARQL endpoint availability check for AAT-atawil took 4.601478576660156e-05s
Availability | VoID file availability check for AAT-atawil took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.2606182098388672s
Reputation | Calculation of the PageRank for AAT-atawil took 0.020062923431396484s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.361701965332031e-05s
Believability | Calculation of trust value for AAT-atawil took 6.9141387939453125e-06s
INFO | --- Analysis for Altawil took 3.2895069122314453s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 4.696846008300781e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.00029015541076660156s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.2695164680480957s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 3.361701965332031e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 8.821487426757812e-06s
INFO | --- Analysis for am-collections-online took 3.4130020141601562s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.2438507080078125e-05s
Availability | VoID file availability check for Amer Nejma took 0.00022125244140625s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.26871490478515625s
Reputation | Calculation of the PageRank for Amer Nejma took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.266334533691406e-05s
Believability | Calculation of trust value for Amer Nejma took 5.7220458984375e-06s
INFO | --- Analysis for Amer_Nejma took 2.365394353866577s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.26119565963745117s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.020299673080444336s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.24249267578125e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 6.67572021484375e-06s
INFO | --- Analysis for amon took 2.9408397674560547s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.7017295360565186s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.29022836685180664s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.02028942108154297s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.465217590332031e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 7.152557373046875e-06s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 3.7191779613494873s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 3.981590270996094e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.27797985076904297s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.020287752151489258s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 3.528594970703125e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 5.9604644775390625e-06s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 2.9253790378570557s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 3.910064697265625e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.23818635940551758s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.0205080509185791s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 3.552436828613281e-05s
Believability | Calculation of trust value for Animal Diversity Web took 6.4373016357421875e-06s
INFO | --- Analysis for animal-diversity-web took 2.9416136741638184s
Availability | SPARQL endpoint availability check for Anime Dataset took 4.172325134277344e-05s
Availability | VoID file availability check for Anime Dataset took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.2429182529449463s
Reputation | Calculation of the PageRank for Anime Dataset took 0.020214557647705078s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 3.2901763916015625e-05s
Believability | Calculation of trust value for Anime Dataset took 5.9604644775390625e-06s
INFO | --- Analysis for Anime took 3.6734604835510254s
Availability | SPARQL endpoint availability check for ANNO took 5.459785461425781e-05s
Availability | VoID file availability check for ANNO took 0.0006697177886962891s
Completeness | Calculation of interlinking completeness for ANNO took 0.2497105598449707s
Reputation | Calculation of the PageRank for ANNO took 0.020136117935180664s
Interlinking | Calculation of Degree of Connection for ANNO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ANNO took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.695487976074219e-05s
Believability | Calculation of trust value for ANNO took 5.7220458984375e-06s
INFO | --- Analysis for anno took 4.6611833572387695s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 4.267692565917969e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.25354552268981934s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.020198345184326172s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 7.939338684082031e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 5.4836273193359375e-06s
INFO | --- Analysis for AntiqueCarsCollection took 3.4731714725494385s
Availability | SPARQL endpoint availability check for apache took 4.3392181396484375e-05s
Availability | VoID file availability check for apache took 0.0007059574127197266s
Completeness | Calculation of interlinking completeness for apache took 0.2639737129211426s
Reputation | Calculation of the PageRank for apache took 0.019967079162597656s
Interlinking | Calculation of Degree of Connection for apache took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for apache took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for apache took 5.53131103515625e-05s
Believability | Calculation of trust value for apache took 5.9604644775390625e-06s
INFO | --- Analysis for apache took 3.2471792697906494s
Availability | SPARQL endpoint availability check for Apertium RDF took 4.506111145019531e-05s
Availability | VoID file availability check for Apertium RDF took 0.0006074905395507812s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.2585170269012451s
Reputation | Calculation of the PageRank for Apertium RDF took 0.020369529724121094s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.9114227294921875e-05s
Believability | Calculation of trust value for Apertium RDF took 5.7220458984375e-06s
INFO | --- Analysis for apertium-rdf took 5.537748575210571s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.28307175636291504s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.020326852798461914s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.935264587402344e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-ca-it took 5.769580841064453s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 4.649162292480469e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.27271032333374023s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.020125150680541992s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.839897155761719e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-en-ca took 5.625301837921143s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0012671947479248047s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.2556180953979492s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.020195960998535156s
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.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.792213439941406e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-en-es took 5.718695640563965s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.2715916633605957s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.02004098892211914s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.744529724121094e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-en-gl took 6.008862733840942s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 4.100799560546875e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.24295735359191895s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.02016305923461914s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.7206878662109375e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.488263845443726s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 7.796287536621094e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.2527341842651367s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.02058887481689453s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.744529724121094e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 6.198883056640625e-06s
INFO | --- Analysis for apertium-rdf-eo-en took 5.491934776306152s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0008707046508789062s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.27676939964294434s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.020660877227783203s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 5.173683166503906e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 5.7220458984375e-06s
INFO | --- Analysis for apertium-rdf-eo-es took 5.600492715835571s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.26095080375671387s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.02021169662475586s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.982948303222656e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 5.7220458984375e-06s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.662020444869995s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.269756555557251s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.02030324935913086s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.839897155761719e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-es-an took 5.4339540004730225s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0006778240203857422s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.27538156509399414s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.020237207412719727s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.649162292480469e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 5.7220458984375e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 5.574151039123535s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 4.291534423828125e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0008447170257568359s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.25035810470581055s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020599842071533203s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 5.054473876953125e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 5.245208740234375e-06s
INFO | --- Analysis for apertium-rdf-es-ca took 24.85786271095276s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.27493929862976074s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.020494699478149414s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 5.173683166503906e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-es-gl took 6.070103406906128s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 4.267692565917969e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.2729916572570801s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.020209074020385742s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 5.1021575927734375e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 8.344650268554688e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 5.609377384185791s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 4.9114227294921875e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.26247262954711914s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.02025771141052246s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 5.030632019042969e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-es-ro took 5.5066001415252686s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.25579404830932617s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.02022099494934082s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.887580871582031e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-eu-en took 5.552605152130127s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.27477049827575684s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.020181655883789062s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.839897155761719e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-eu-es took 5.621236324310303s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.267692565917969e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0006265640258789062s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.26783108711242676s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.02044367790222168s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.982948303222656e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.605250358581543s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.291534423828125e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0006709098815917969s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.2707080841064453s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.02014780044555664s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.76837158203125e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.049041748046875e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 5.674813270568848s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 4.291534423828125e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0007715225219726562s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.2428133487701416s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.020221233367919922s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.7206878662109375e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 5.7220458984375e-06s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.510924339294434s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 4.506111145019531e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0005626678466796875s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.26226305961608887s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.020920753479003906s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 5.1021575927734375e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 8.58306884765625e-06s
INFO | --- Analysis for apertium-rdf-oc-es took 5.576734781265259s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.38690185546875e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0006656646728515625s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.2453441619873047s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.02030038833618164s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.8160552978515625e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-pt-ca took 5.6543192863464355s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 4.267692565917969e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0005931854248046875s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.2595193386077881s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.020320892333984375s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 5.125999450683594e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.321054935455322s
Availability | SPARQL endpoint availability check for AragoDBPedia took 0.6768677234649658s
Availability | VoID file availability check for AragoDBPedia took 0.0005953311920166016s
Extra | Recovery of all triples for AragoDBPedia took 4.849223613739014s
Performance | Total latancy measurement for AragoDBPedia took 2.02258563041687s
Amount of data | Number of triples check for AragoDBPedia took 1.1441915035247803s
Interoperability | New terms check for AragoDBPedia took 2.1216020584106445s
Versatility | Languages check for AragoDBPedia took 60.50558519363403s
Interpretability | Number of blank nodes check for AragoDBPedia took 5.061010122299194s
Security | Check HTTPS for AragoDBPedia took 0.2598254680633545s
Interpretability | RDF structures check for AragoDBPedia took 1.1828334331512451s
Versatility | Serialization formats check for AragoDBPedia took 1.1965439319610596s
Availability | RDF dump link check for AragoDBPedia took 5.4663262367248535s
License | MR license check for AragoDBPedia took 0.9254167079925537s
License | HR license check for AragoDBPedia took 7.912569999694824s
Amount of data | Number of property check for AragoDBPedia took 0.4102616310119629s
Understandability | Number of label check for AragoDBPedia took 0.8995234966278076s
Understandability | URI regex check for AragoDBPedia took 1.0245487689971924s
Understandability | Vocabs check for AragoDBPedia took 0.4435305595397949s
Verifiability | Authors check for AragoDBPedia took 0.6327774524688721s
Verifiability | Publishers check for AragoDBPedia took 0.4159092903137207s
Performance | Throughput check for AragoDBPedia took 11.53742003440857s
Amount of data | Check the number of entities for AragoDBPedia took 8.296966552734375e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.5833327770233154s
Interlinking | sameAs chians check for AragoDBPedia took 0.48473334312438965s
Interlinking | skos check for AragoDBPedia took 1.0714037418365479s
Interlinking | skos check for AragoDBPedia took 0.3955099582672119s
Timeliness | dataset update frequency check for AragoDBPedia took 1.0898144245147705s
Currency | Creation date check for AragoDBPedia took 2.0976500511169434s
Currency | Modification date check for AragoDBPedia took 0.9022245407104492s
Rep.Conc. | URIs length for AragoDBPedia took 6.683197736740112s
Interoperability | New vocabularies check for AragoDBPedia took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.39194726943969727s
Accuracy | Check Functional Property for AragoDBPedia took 0.46782994270324707s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.4660823345184326s
Accuracy | Check Empty annotation labels for AragoDBPedia took 1.2755017280578613s
Accuracy | Check White space in annotation for AragoDBPedia took 0.02960824966430664s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.028223514556884766s
Consistency | Disjoint class check for AragoDBPedia took 0.49747657775878906s
Consistency | Check Misplaced properties for AragoDBPedia took 4.567329406738281s
Consistency | Misplaced classes for AragoDBPedia took 0.6214487552642822s
Consistency | Check Ontology hijacking for AragoDBPedia took 2.625283718109131s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.3201136589050293s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 5.454487085342407s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.03422999382019043s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.5505592823028564s
Security | Sign check for AragoDBPedia took 0.5786583423614502s
Availability | Check URIs Dereferenciability for AragoDBPedia took 3251.6294252872467s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 1.513331651687622s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.020400285720825195s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 4.887580871582031e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.430511474609375e-06s
Believability | Calculation of trust value for AragoDBPedia took 2.5987625122070312e-05s
INFO | --- Analysis for aragodbpedia took 10410.50612950325s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.183868169784546s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.2709226608276367s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.02004408836364746s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.435943603515625e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for archiveshub-linkeddata took 83.95557689666748s
Availability | SPARQL endpoint availability check for Archivi ISMA took 7.510185241699219e-05s
Availability | VoID file availability check for Archivi ISMA took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.2720816135406494s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.020296812057495117s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 3.0517578125e-05s
Believability | Calculation of trust value for Archivi ISMA took 5.9604644775390625e-06s
INFO | --- Analysis for archivio-isma took 3.799858570098877s
Availability | SPARQL endpoint availability check for ARIADNE took 6.246566772460938e-05s
Availability | VoID file availability check for ARIADNE took 0.0002162456512451172s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.2717399597167969s
Reputation | Calculation of the PageRank for ARIADNE took 0.020012855529785156s
Interlinking | Calculation of Degree of Connection for ARIADNE took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ARIADNE took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 3.0279159545898438e-05s
Believability | Calculation of trust value for ARIADNE took 1.1444091796875e-05s
INFO | --- Analysis for ariadne took 3.326254367828369s
Availability | SPARQL endpoint availability check for Aristotle University took 4.029273986816406e-05s
Availability | VoID file availability check for Aristotle University took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.23895478248596191s
Reputation | Calculation of the PageRank for Aristotle University took 0.020312786102294922s
Interlinking | Calculation of Degree of Connection for Aristotle University took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Aristotle University took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 3.0040740966796875e-05s
Believability | Calculation of trust value for Aristotle University took 1.1205673217773438e-05s
INFO | --- Analysis for aristotle-university took 3.354466676712036s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 5.260554552078247s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.2682182788848877s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.020247459411621094s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 2.956390380859375e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 5.0067901611328125e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 20.56587862968445s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.00543212890625e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.2654259204864502s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.020047664642333984s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 3.075599670410156e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 5.9604644775390625e-06s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 3.3141932487487793s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.9154052734375s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.254410982131958s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.020294904708862305s
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.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.4332275390625e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 5.9604644775390625e-06s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 17.19115972518921s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 5.745887756347656e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.25438356399536133s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.02023935317993164s
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.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.989738464355469e-05s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.76837158203125e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 15.579836368560791s
Availability | SPARQL endpoint availability check for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 4.124641418457031e-05s
Availability | VoID file availability check for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.25348997116088867s
Reputation | Calculation of the PageRank for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.020241498947143555s
Interlinking | Calculation of Degree of Connection for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.0967254638671875e-05s
Believability | Calculation of trust value for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.0251998901367188e-05s
INFO | --- Analysis for Arthron took 2.3137853145599365s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.2438507080078125e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.24623966217041016s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.020111799240112305s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 9.942054748535156e-05s
Believability | Calculation of trust value for Arthroscopy community took 5.245208740234375e-06s
INFO | --- Analysis for arthroscopy took 12.236385345458984s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 1.1613943576812744s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.26311802864074707s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.02016282081604004s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.3113021850585938e-05s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 5.245208740234375e-06s
INFO | --- Analysis for artxscienceinternational-wikidata took 14.5492422580719s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.2984426021575928s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.2817370891571045s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020054340362548828s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.367134094238281e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 5.7220458984375e-06s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 12.742010354995728s
Availability | SPARQL endpoint availability check for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 2.424480676651001s
Availability | VoID file availability check for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.0006425380706787109s
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.27752208709716797s
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.02028965950012207s
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.0007462501525878906s
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.0108642578125e-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.0013580322265625e-05s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 11.290520429611206s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.4481403827667236s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.2656116485595703s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.020170211791992188s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007205009460449219s
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 5.7220458984375e-06s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 12.331791639328003s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.4522838592529297s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.2633476257324219s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.020138263702392578s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 3.886222839355469e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 5.7220458984375e-06s
INFO | --- Analysis for ASCDC-CRB took 14.568538427352905s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.4630703926086426s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.2729661464691162s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.020282983779907227s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 8.630752563476562e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 5.0067901611328125e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 11.962562322616577s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.4375157356262207s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.2593846321105957s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.020142078399658203s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.337860107421875e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 4.76837158203125e-06s
INFO | --- Analysis for ASCDC-DQOT took 12.895993709564209s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.463179111480713s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.2641775608062744s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.020250320434570312s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.702278137207031e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 5.4836273193359375e-06s
INFO | --- Analysis for ASCDC-IHP-WCD took 13.011394739151001s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 3.2347567081451416s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.28189754486083984s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.02035689353942871s
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.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 7.557868957519531e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 5.0067901611328125e-06s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 13.761188268661499s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.4512906074523926s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.27376794815063477s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.020016908645629883s
Interlinking | Calculation of Degree of Connection for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 4.982948303222656e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.9604644775390625e-06s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 11.849839448928833s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.4732367992401123s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.2888174057006836s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.020030498504638672s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 4.792213439941406e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.9604644775390625e-06s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 11.889856576919556s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 3.857666492462158s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0006551742553710938s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.28447628021240234s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.02026987075805664s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.9591064453125e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 6.4373016357421875e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 16.145283699035645s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.4504098892211914s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.27768778800964355s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.020183086395263672s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.2479248046875e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 5.7220458984375e-06s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 11.37408709526062s
Availability | SPARQL endpoint availability check for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 2.4406542778015137s
Availability | VoID file availability check for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.0005574226379394531s
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.2521669864654541s
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.020110607147216797s
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 8.106231689453125e-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.0008118152618408203s
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 7.915496826171875e-05s
Believability | Calculation of trust value for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 4.76837158203125e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 12.815483331680298s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.436169385910034s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.2848501205444336s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.020160436630249023s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.410743713378906e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 5.245208740234375e-06s
INFO | --- Analysis for ASCDC_-_DNB took 11.291336297988892s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.076957702636719e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.00028705596923828125s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.2697725296020508s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.020552873611450195s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.699562072753906e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 6.67572021484375e-06s
INFO | --- Analysis for asit took 7.702210187911987s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.3392181396484375e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.2465202808380127s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.02013373374938965s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 3.647804260253906e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 6.198883056640625e-06s
INFO | --- Analysis for asjp took 4.554490327835083s
Availability | SPARQL endpoint availability check for ASN:US took 0.09231090545654297s
Availability | VoID file availability check for ASN:US took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for ASN:US took 0.25609421730041504s
Reputation | Calculation of the PageRank for ASN:US took 0.020172119140625s
Interlinking | Calculation of Degree of Connection for ASN:US took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ASN:US took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for ASN:US took 6.699562072753906e-05s
Believability | Calculation of trust value for ASN:US took 4.76837158203125e-06s
INFO | --- Analysis for asn-us took 6.004736423492432s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.220008850097656e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.2792549133300781s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.02016901969909668s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 2.9802322387695312e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 4.291534423828125e-06s
INFO | --- Analysis for aspire-mmu took 4.350051164627075s
Availability | SPARQL endpoint availability check for associations took 4.1961669921875e-05s
Availability | VoID file availability check for associations took 0.0002872943878173828s
Completeness | Calculation of interlinking completeness for associations took 0.27520227432250977s
Reputation | Calculation of the PageRank for associations took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for associations took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for associations took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for associations took 6.628036499023438e-05s
Believability | Calculation of trust value for associations took 5.9604644775390625e-06s
INFO | --- Analysis for associations took 7.344477415084839s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 4.1961669921875e-05s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.00022935867309570312s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.2617075443267822s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.020147085189819336s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 2.9802322387695312e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 5.7220458984375e-06s
INFO | --- Analysis for atc-publikovan--s-kl took 2.9507741928100586s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 5.3882598876953125e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.2656416893005371s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.02013397216796875s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 8.726119995117188e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 6.4373016357421875e-06s
INFO | --- Analysis for athelia-rfid took 5.276220798492432s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 3.981590270996094e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.27219724655151367s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.020024776458740234s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 2.8848648071289062e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 5.7220458984375e-06s
INFO | --- Analysis for aueb-linked-open-data took 2.880293607711792s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.5675880908966064s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.2771286964416504s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.02015972137451172s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 4.696846008300781e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 1.049041748046875e-05s
INFO | --- Analysis for AugustiniConfessiones took 4.131304740905762s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.6083066463470459s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.26951169967651367s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.019983291625976562s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 8.630752563476562e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 5.4836273193359375e-06s
INFO | --- Analysis for austrian_ski_racers took 3.853445053100586s
Availability | SPARQL endpoint availability check for AVsOnto took 4.220008850097656e-05s
Availability | VoID file availability check for AVsOnto took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.2913670539855957s
Reputation | Calculation of the PageRank for AVsOnto took 0.02012038230895996s
Interlinking | Calculation of Degree of Connection for AVsOnto took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 2.8848648071289062e-05s
Believability | Calculation of trust value for AVsOnto took 5.4836273193359375e-06s
INFO | --- Analysis for AVsOnto took 3.2956297397613525s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.26228928565979004s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.000476837158203125s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 197.0439829826355s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.48726606369018555s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0375747680664s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 255.3960907459259s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0596113204956s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.08372473716736s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.21782469749450684s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.326127290725708s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14079785346984863s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10617518424987793s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 54.07241439819336s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10490560531616s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15870070457458496s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 246.52118158340454s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24979662895202637s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11428999900817871s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10817265510559082s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1073758602142334s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.619027376174927s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.176399230957031e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09500503540039062s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0230932235718s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17341279983520508s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11913156509399414s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12873578071594238s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.22045111656188965s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2794954776763916s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 392.43637681007385s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15125036239624023s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.375736713409424s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.2068614959716797s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.669857501983643s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1691138744354248s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.2038209438324s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 147.50212001800537s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.404949903488159s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.49904203414917s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.7671327590942383s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14956974983215332s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.492198705673218s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.7119872570037842s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.020869731903076172s
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.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.677078247070312e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.6689300537109375e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.5299530029296875e-06s
INFO | --- Analysis for b3kat took 4064.9416496753693s
Availability | SPARQL endpoint availability check for BabelNet took 0.5351722240447998s
Availability | VoID file availability check for BabelNet took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for BabelNet took 0.28261709213256836s
Reputation | Calculation of the PageRank for BabelNet took 0.020314931869506836s
Interlinking | Calculation of Degree of Connection for BabelNet took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BabelNet took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.0001621246337890625s
Believability | Calculation of trust value for BabelNet took 5.245208740234375e-06s
INFO | --- Analysis for babelnet took 6.1317298412323s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 4.267692565917969e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.0002243518829345703s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.2552626132965088s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.02110743522644043s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bacevicius.lt took 6.198883056640625e-06s
INFO | --- Analysis for Bacevicius.lt took 3.338013172149658s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.5186057090759277s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.26227283477783203s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.020161151885986328s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.291534423828125e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 6.67572021484375e-06s
INFO | --- Analysis for bag took 4.631571531295776s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 2.7476847171783447s
Availability | VoID file availability check for 红色经典歌曲 took 0.00020837783813476562s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2660539150238037s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020052433013916016s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.0517578125e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.152557373046875e-06s
INFO | --- Analysis for baixue took 5.546917915344238s
Availability | SPARQL endpoint availability check for baixue composer took 4.220008850097656e-05s
Availability | VoID file availability check for baixue composer took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for baixue composer took 0.280426025390625s
Reputation | Calculation of the PageRank for baixue composer took 0.020583152770996094s
Interlinking | Calculation of Degree of Connection for baixue composer took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for baixue composer took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for baixue composer took 3.075599670410156e-05s
Believability | Calculation of trust value for baixue composer took 6.67572021484375e-06s
INFO | --- Analysis for baixue_composer took 3.339770555496216s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 5.936622619628906e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2540743350982666s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.0207364559173584s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.9802322387695312e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.3909759521484375e-06s
INFO | --- Analysis for baixue_imagery took 3.1221649646759033s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.267692565917969e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.25571584701538086s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02017998695373535s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.0517578125e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 5.4836273193359375e-06s
INFO | --- Analysis for baixue_imagery1 took 3.3246562480926514s
Availability | SPARQL endpoint availability check for BAMS took 3.933906555175781e-05s
Availability | VoID file availability check for BAMS took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for BAMS took 0.264171838760376s
Reputation | Calculation of the PageRank for BAMS took 0.02016901969909668s
Interlinking | Calculation of Degree of Connection for BAMS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BAMS took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for BAMS took 2.9802322387695312e-05s
Believability | Calculation of trust value for BAMS took 7.3909759521484375e-06s
INFO | --- Analysis for bams took 2.876014471054077s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 4.172325134277344e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.2677743434906006s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.020398855209350586s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 3.981590270996094e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 7.3909759521484375e-06s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 3.0217745304107666s
Availability | SPARQL endpoint availability check for BBC Music took 0.34735536575317383s
Availability | VoID file availability check for BBC Music took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for BBC Music took 0.2535717487335205s
Reputation | Calculation of the PageRank for BBC Music took 0.02025127410888672s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00012612342834472656s
Believability | Calculation of trust value for BBC Music took 1.0013580322265625e-05s
INFO | --- Analysis for bbc-music took 3.378284454345703s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.3728337287902832s
Availability | VoID file availability check for BBC Programmes took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.28053784370422363s
Reputation | Calculation of the PageRank for BBC Programmes took 0.02051687240600586s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010514259338378906s
Believability | Calculation of trust value for BBC Programmes took 6.67572021484375e-06s
INFO | --- Analysis for bbc-programmes took 10.885469436645508s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.3279566764831543s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.2529010772705078s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.020365476608276367s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010132789611816406s
Believability | Calculation of trust value for BBC Wildlife Finder took 7.152557373046875e-06s
INFO | --- Analysis for bbc-wildlife-finder took 9.383034944534302s
Availability | SPARQL endpoint availability check for BBOP took 4.124641418457031e-05s
Availability | VoID file availability check for BBOP took 0.00021266937255859375s
Completeness | Calculation of interlinking completeness for BBOP took 0.291672945022583s
Reputation | Calculation of the PageRank for BBOP took 0.020458221435546875s
Interlinking | Calculation of Degree of Connection for BBOP took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BBOP took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.266334533691406e-05s
Believability | Calculation of trust value for BBOP took 6.4373016357421875e-06s
INFO | --- Analysis for bbop took 2.94815993309021s
Availability | SPARQL endpoint availability check for BBOP took 4.1484832763671875e-05s
Availability | VoID file availability check for BBOP took 0.0009055137634277344s
Completeness | Calculation of interlinking completeness for BBOP took 0.25603747367858887s
Reputation | Calculation of the PageRank for BBOP took 0.020168781280517578s
Interlinking | Calculation of Degree of Connection for BBOP took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BBOP took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.123283386230469e-05s
Believability | Calculation of trust value for BBOP took 6.67572021484375e-06s
INFO | --- Analysis for bbop-selected took 21.94027614593506s
Availability | SPARQL endpoint availability check for Bdgp took 1.6726758480072021s
Availability | VoID file availability check for Bdgp took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for Bdgp took 0.2838709354400635s
Reputation | Calculation of the PageRank for Bdgp took 0.02016758918762207s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.0040740966796875e-05s
Believability | Calculation of trust value for Bdgp took 9.5367431640625e-06s
INFO | --- Analysis for bdgp took 8.492817878723145s
Availability | SPARQL endpoint availability check for Bendev Junior took 4.124641418457031e-05s
Availability | VoID file availability check for Bendev Junior took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.26677894592285156s
Reputation | Calculation of the PageRank for Bendev Junior took 0.020171165466308594s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 3.0040740966796875e-05s
Believability | Calculation of trust value for Bendev Junior took 6.198883056640625e-06s
INFO | --- Analysis for bendevoficial took 7.021510362625122s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 4.12445068359375s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0005972385406494141s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.28076958656311035s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.02032327651977539s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 7.677078247070312e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 4.0531158447265625e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 11.873961448669434s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 4.076957702636719e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.00020885467529296875s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.29116296768188477s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.020226001739501953s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 2.9802322387695312e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 5.7220458984375e-06s
INFO | --- Analysis for berlin-offener-haushalt took 2.943979263305664s
Availability | SPARQL endpoint availability check for berlios took 4.1484832763671875e-05s
Availability | VoID file availability check for berlios took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for berlios took 0.27487778663635254s
Reputation | Calculation of the PageRank for berlios took 0.02034163475036621s
Interlinking | Calculation of Degree of Connection for berlios took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for berlios took 8.797645568847656e-05s
Believability | Calculation of trust value for berlios took 5.245208740234375e-06s
INFO | --- Analysis for berlios took 2.556603193283081s
Availability | SPARQL endpoint availability check for Between Our Worlds took 4.1484832763671875e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.3160109519958496s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.020253896713256836s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 6.604194641113281e-05s
Believability | Calculation of trust value for Between Our Worlds took 6.4373016357421875e-06s
INFO | --- Analysis for betweenourworlds took 9.089359045028687s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.34137868881225586s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.27232980728149414s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.020747900009155273s
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.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.059906005859375e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 4.5299530029296875e-06s
INFO | --- Analysis for bfs-linked-data took 2.9246714115142822s
Availability | SPARQL endpoint availability check for BibBase took 0.0835578441619873s
Availability | VoID file availability check for BibBase took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for BibBase took 0.264005184173584s
Reputation | Calculation of the PageRank for BibBase took 0.0206298828125s
Interlinking | Calculation of Degree of Connection for BibBase took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BibBase took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.34600830078125e-05s
Believability | Calculation of trust value for BibBase took 4.76837158203125e-06s
INFO | --- Analysis for bibbase took 2.499955177307129s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 4.0531158447265625e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.27449560165405273s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.020055532455444336s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 9.632110595703125e-05s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 5.0067901611328125e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 6.729985952377319s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 4.100799560546875e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.2733933925628662s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.020586490631103516s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 9.942054748535156e-05s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 5.9604644775390625e-06s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 8.488060474395752s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.838539123535156e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.000244140625s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.26853466033935547s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.020319461822509766s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.0040740966796875e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 5.9604644775390625e-06s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 2.8857696056365967s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 4.0531158447265625e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.2930176258087158s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.020258426666259766s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.552436828613281e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 5.7220458984375e-06s
INFO | --- Analysis for BibSonomy took 9.393633127212524s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 6.747245788574219e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.26654624938964844s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.02044224739074707s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 4.124641418457031e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 5.9604644775390625e-06s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 5.155433416366577s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 4.124641418457031e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.25177955627441406s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.02035355567932129s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 3.504753112792969e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.123283386230469e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 6.4373016357421875e-06s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.657050371170044s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 4.029273986816406e-05s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.00022459030151367188s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.26625561714172363s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.0201263427734375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 3.075599670410156e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-acfsid took 2.8923256397247314s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 1.226865291595459s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0012326240539550781s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 19.931166172027588s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.5099310874938965s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 45.395402908325195s
Interoperability | New terms check for Bio2RDF::Affymetrix took 42.64878559112549s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.111985206604004s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.13921475410461426s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.9811255931854248s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.23735499382019043s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 6.263807058334351s
License | MR license check for Bio2RDF::Affymetrix took 0.4451465606689453s
License | HR license check for Bio2RDF::Affymetrix took 60.104063272476196s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.13233399391174316s
Understandability | Number of label check for Bio2RDF::Affymetrix took 10.519192218780518s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.4078836441040039s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.12584710121154785s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.20301365852355957s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.13225412368774414s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.621156215667725s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 73.94098114967346s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.5794715881347656s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.256915807723999s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.7518951892852783s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.1956775188446045s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.11744546890258789s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.28952860832214355s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.22483205795288086s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 109.59624648094177s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 18.15272545814514s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.34389686584472656s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.16275429725646973s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.12615609169006348s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 7.145860433578491s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.8757650852203369s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.654139518737793s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.3712799549102783s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 65.10282731056213s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.249833583831787s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.6296257972717285s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.3453586101531982s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.432886600494385s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.6920576095581055s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.28415942192077637s
Security | Sign check for Bio2RDF::Affymetrix took 0.11700582504272461s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 14.057775259017944s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.8671772480010986s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.00010728836059570312s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 18.187110662460327s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-affymetrix took 1047.6258471012115s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.5030274391174316s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0005705356597900391s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 20.548393726348877s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.2539501190185547s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 44.36242389678955s
Interoperability | New terms check for Bio2RDF::Biomodels took 44.41835641860962s
Versatility | Languages check for Bio2RDF::Biomodels took 60.25429582595825s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.3335700035095215s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.1631333827972412s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 1.286191463470459s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.34922313690185547s
Availability | RDF dump link check for Bio2RDF::Biomodels took 6.416858673095703s
License | MR license check for Bio2RDF::Biomodels took 0.5632879734039307s
License | HR license check for Bio2RDF::Biomodels took 60.251067876815796s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.29261231422424316s
Understandability | Number of label check for Bio2RDF::Biomodels took 10.721141576766968s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5874810218811035s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.2661890983581543s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.23952865600585938s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.25592613220214844s
Performance | Throughput check for Bio2RDF::Biomodels took 11.667742729187012s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 74.0336549282074s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 0.6128075122833252s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.40709686279296875s
Interlinking | skos check for Bio2RDF::Biomodels took 1.0462546348571777s
Interlinking | skos check for Bio2RDF::Biomodels took 0.34279584884643555s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.28551316261291504s
Currency | Creation date check for Bio2RDF::Biomodels took 0.521432638168335s
Currency | Modification date check for Bio2RDF::Biomodels took 0.5237042903900146s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 112.71654200553894s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 19.03707194328308s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.4564366340637207s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.2913854122161865s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.29385805130004883s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 8.016906023025513s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.8918516635894775s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.661285400390625s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.5111160278320312s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.37575316429138s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.401021718978882s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 6.489782094955444s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.346616506576538s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.56032681465149s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.6955065727233887s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.4191257953643799s
Security | Sign check for Bio2RDF::Biomodels took 0.2780730724334717s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 21.08946943283081s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.966594934463501s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.0199892520904541s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00010752677917480469s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 19.624987602233887s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 6.198883056640625e-06s
INFO | --- Analysis for bio2rdf-biomodels took 1070.5323133468628s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.27404260635375977s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.170967102050781e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 4.322550058364868s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.46302080154418945s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0006022453308105469s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 19.304860591888428s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.2600536346435547s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 44.87126159667969s
Interoperability | New terms check for Bio2RDF::Bioportal took 42.668522119522095s
Versatility | Languages check for Bio2RDF::Bioportal took 60.267231941223145s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.26081395149230957s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.16827774047851562s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 1.0555086135864258s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.31850337982177734s
Availability | RDF dump link check for Bio2RDF::Bioportal took 6.281800031661987s
License | MR license check for Bio2RDF::Bioportal took 0.5295991897583008s
License | HR license check for Bio2RDF::Bioportal took 60.2599892616272s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.27758121490478516s
Understandability | Number of label check for Bio2RDF::Bioportal took 10.132760524749756s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.5793206691741943s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.25893545150756836s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.2693967819213867s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.2487337589263916s
Performance | Throughput check for Bio2RDF::Bioportal took 11.499907732009888s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 74.48526620864868s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.7566699981689453s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.3989379405975342s
Interlinking | skos check for Bio2RDF::Bioportal took 0.9052028656005859s
Interlinking | skos check for Bio2RDF::Bioportal took 0.3460066318511963s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.2791736125946045s
Currency | Creation date check for Bio2RDF::Bioportal took 0.5233244895935059s
Currency | Modification date check for Bio2RDF::Bioportal took 0.5130600929260254s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 110.9711480140686s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 71.44784331321716s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.4556882381439209s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.2761101722717285s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.26398444175720215s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 7.973945379257202s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.8756341934204102s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6679306030273438s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.4625728130340576s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 65.41651582717896s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.3871636390686035s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.719725847244263s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.3645045757293701s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.570228099823s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.6886501312255859s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.6244120597839355s
Security | Sign check for Bio2RDF::Bioportal took 0.2884819507598877s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 20.817075729370117s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.5190896987915039s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.020203590393066406s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004143714904785156s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 19.988431692123413s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-bioportal took 1129.0246427059174s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.13628101348876953s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.764254093170166s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.01992511749267578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.269050598144531e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 5.7220458984375e-06s
INFO | --- Analysis for bio2rdf-chembl took 18.440754413604736s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.4617288112640381s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0005671977996826172s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 19.522475481033325s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.264477252960205s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 43.99831247329712s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 42.09998559951782s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.24498128890991s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.28537869453430176s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.15743255615234375s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 1.1321330070495605s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.30437445640563965s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 6.357204914093018s
License | MR license check for Bio2RDF::Clinicaltrials took 0.5818960666656494s
License | HR license check for Bio2RDF::Clinicaltrials took 60.266196966171265s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.2824666500091553s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 10.000575065612793s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.5567922592163086s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.240217924118042s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.25857973098754883s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.26065993309020996s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 11.508060932159424s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 73.74902558326721s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 2.042961597442627s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.362499475479126s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.9174847602844238s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.34804773330688477s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.28550267219543457s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.5354886054992676s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.5232431888580322s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 109.5693085193634s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 22.888007402420044s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.45006585121154785s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.27820730209350586s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.28755640983581543s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 7.259467124938965s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.8843817710876465s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6608784198760986s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.42966556549072266s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 65.16284990310669s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.3715152740478516s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 6.291194200515747s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.3506884574890137s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.61386227607727s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.6925270557403564s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.45267224311828613s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.27057361602783203s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 12.793102741241455s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.5555760860443115s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.02020740509033203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 5.1975250244140625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 19.773667812347412s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1058.3923921585083s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.47712063789367676s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0005736351013183594s
Extra | Recovery of all triples for Bio2RDF::Ctd took 18.84077548980713s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.3055493831634521s
Amount of data | Number of triples check for Bio2RDF::Ctd took 44.11586284637451s
Interoperability | New terms check for Bio2RDF::Ctd took 42.11366248130798s
Versatility | Languages check for Bio2RDF::Ctd took 60.26256537437439s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.28577160835266113s
Security | Check HTTPS for Bio2RDF::Ctd took 0.1466505527496338s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.8946132659912109s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.3449108600616455s
Availability | RDF dump link check for Bio2RDF::Ctd took 6.361841917037964s
License | MR license check for Bio2RDF::Ctd took 0.43777036666870117s
License | HR license check for Bio2RDF::Ctd took 60.25809049606323s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.2526216506958008s
Understandability | Number of label check for Bio2RDF::Ctd took 9.751167297363281s
Understandability | URI regex check for Bio2RDF::Ctd took 0.596367597579956s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.27404069900512695s
Verifiability | Authors check for Bio2RDF::Ctd took 0.27120280265808105s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.2656867504119873s
Performance | Throughput check for Bio2RDF::Ctd took 11.002780675888062s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 73.36201047897339s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.5712969303131104s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.34499144554138184s
Interlinking | skos check for Bio2RDF::Ctd took 1.0343341827392578s
Interlinking | skos check for Bio2RDF::Ctd took 0.36788511276245117s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.2499990463256836s
Currency | Creation date check for Bio2RDF::Ctd took 0.5448997020721436s
Currency | Modification date check for Bio2RDF::Ctd took 0.5400471687316895s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 108.95994901657104s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 24.167701482772827s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.43244290351867676s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.285015344619751s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.2940840721130371s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 8.08336615562439s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8806614875793457s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6444606781005859s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.4097161293029785s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.15267276763916s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.412526845932007s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.365587949752808s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.3488938808441162s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.584980726242065s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.6951189041137695s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.4495110511779785s
Security | Sign check for Bio2RDF::Ctd took 0.258404016494751s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 12.787984132766724s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.948401689529419s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.02022528648376465s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 7.605552673339844e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 19.951026439666748s
Believability | Calculation of trust value for Bio2RDF::Ctd took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-ctd took 1066.3812613487244s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 5.054473876953125e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0006246566772460938s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.6822855472564697s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.020485877990722656s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 5.054473876953125e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-dataset took 3.9931607246398926s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.463972806930542s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.00054931640625s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 19.763909339904785s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.2620041370391846s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 44.672523021698s
Interoperability | New terms check for Bio2RDF::Dbsnp took 41.4413902759552s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.262938499450684s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.2695035934448242s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.1437218189239502s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.9739093780517578s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.30736541748046875s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 6.274697542190552s
License | MR license check for Bio2RDF::Dbsnp took 0.5146620273590088s
License | HR license check for Bio2RDF::Dbsnp took 60.2479043006897s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.2797048091888428s
Understandability | Number of label check for Bio2RDF::Dbsnp took 10.516404867172241s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.5866539478302002s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.25821590423583984s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.25562143325805664s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.27019691467285156s
Performance | Throughput check for Bio2RDF::Dbsnp took 11.467307567596436s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 73.79596900939941s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 2.018352508544922s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.36441564559936523s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.8262443542480469s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.33734965324401855s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.2776930332183838s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.5194792747497559s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.5151300430297852s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 108.13284230232239s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 19.72631335258484s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.4337449073791504s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.2821521759033203s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.2668449878692627s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 7.067154407501221s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.878903865814209s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6538715362548828s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.37877821922302246s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 64.89864993095398s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.39494252204895s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.292507886886597s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.361208200454712s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.594154357910156s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.6876568794250488s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.41321301460266113s
Security | Sign check for Bio2RDF::Dbsnp took 0.2751486301422119s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 18.154266119003296s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.5411319732666016s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.020224332809448242s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 6.389617919921875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 21.192119359970093s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 1061.2165603637695s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.46821165084838867s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0005631446838378906s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 18.732118844985962s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.2351877689361572s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 44.771581411361694s
Interoperability | New terms check for Bio2RDF::Drugbank took 41.239818811416626s
Versatility | Languages check for Bio2RDF::Drugbank took 60.24498987197876s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.2819540500640869s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.15718507766723633s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.6896753311157227s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.3180267810821533s
Availability | RDF dump link check for Bio2RDF::Drugbank took 6.521576881408691s
License | MR license check for Bio2RDF::Drugbank took 0.5466361045837402s
License | HR license check for Bio2RDF::Drugbank took 60.259090185165405s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.26208972930908203s
Understandability | Number of label check for Bio2RDF::Drugbank took 9.73629903793335s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.6014494895935059s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.24738764762878418s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.2726173400878906s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.2677333354949951s
Performance | Throughput check for Bio2RDF::Drugbank took 11.345328092575073s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 74.18874597549438s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.6034197807312012s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.34710025787353516s
Interlinking | skos check for Bio2RDF::Drugbank took 0.6812193393707275s
Interlinking | skos check for Bio2RDF::Drugbank took 0.34375810623168945s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.2573363780975342s
Currency | Creation date check for Bio2RDF::Drugbank took 0.5401546955108643s
Currency | Modification date check for Bio2RDF::Drugbank took 0.5165054798126221s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 109.5230233669281s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 17.498613119125366s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.4094712734222412s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.27265286445617676s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.2848243713378906s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 7.476607322692871s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.8790545463562012s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.6567060947418213s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.40284037590026855s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 65.00084328651428s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.4370217323303223s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 6.026442289352417s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.3265256881713867s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.58220863342285s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.6888635158538818s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.4382145404815674s
Security | Sign check for Bio2RDF::Drugbank took 0.2643721103668213s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 21.40564465522766s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.9743480682373047s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.020199298858642578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00011086463928222656s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 19.486695051193237s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-drugbank took 1061.0261561870575s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.4708542823791504s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0006978511810302734s
Extra | Recovery of all triples for Bio2RDF::Genage took 20.337929487228394s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.2505075931549072s
Amount of data | Number of triples check for Bio2RDF::Genage took 43.70188808441162s
Interoperability | New terms check for Bio2RDF::Genage took 44.95874881744385s
Versatility | Languages check for Bio2RDF::Genage took 60.30950736999512s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.2722342014312744s
Security | Check HTTPS for Bio2RDF::Genage took 0.1748359203338623s
Interpretability | RDF structures check for Bio2RDF::Genage took 1.2200090885162354s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.3259851932525635s
Availability | RDF dump link check for Bio2RDF::Genage took 6.291790723800659s
License | MR license check for Bio2RDF::Genage took 0.6169643402099609s
License | HR license check for Bio2RDF::Genage took 60.25470447540283s
Amount of data | Number of property check for Bio2RDF::Genage took 0.26937294006347656s
Understandability | Number of label check for Bio2RDF::Genage took 9.849340200424194s
Understandability | URI regex check for Bio2RDF::Genage took 0.593315839767456s
Understandability | Vocabs check for Bio2RDF::Genage took 0.2492680549621582s
Verifiability | Authors check for Bio2RDF::Genage took 0.2760155200958252s
Verifiability | Publishers check for Bio2RDF::Genage took 0.26877617835998535s
Performance | Throughput check for Bio2RDF::Genage took 11.632493257522583s
Amount of data | Check the number of entities for Bio2RDF::Genage took 74.57587933540344s
Verifiability | Contribs. check for Bio2RDF::Genage took 2.04508113861084s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.3472440242767334s
Interlinking | skos check for Bio2RDF::Genage took 0.7715103626251221s
Interlinking | skos check for Bio2RDF::Genage took 0.39644813537597656s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.25798702239990234s
Currency | Creation date check for Bio2RDF::Genage took 0.4927518367767334s
Currency | Modification date check for Bio2RDF::Genage took 0.5241491794586182s
Rep.Conc. | URIs length for Bio2RDF::Genage took 109.79346656799316s
Interoperability | New vocabularies check for Bio2RDF::Genage took 52.5108437538147s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.44837045669555664s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.298494815826416s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.26054906845092773s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 7.726194143295288s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.8822653293609619s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6586015224456787s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.4408838748931885s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 65.80046534538269s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.4505984783172607s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.8925697803497314s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.340505599975586s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.56206393241882s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.703406810760498s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.5883142948150635s
Security | Sign check for Bio2RDF::Genage took 0.2789790630340576s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 15.692593336105347s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.5145792961120605s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.02018141746520996s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 5.602836608886719e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 20.614195108413696s
Believability | Calculation of trust value for Bio2RDF::Genage took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-genage took 1098.874305486679s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.00022864341735839844s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.2835707664489746s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.02014613151550293s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 5.817413330078125e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-genbank took 5.151392459869385s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.4646787643432617s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0006878376007080078s
Extra | Recovery of all triples for Bio2RDF::Gendr took 20.182538986206055s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.3022778034210205s
Amount of data | Number of triples check for Bio2RDF::Gendr took 44.49382185935974s
Interoperability | New terms check for Bio2RDF::Gendr took 43.489917278289795s
Versatility | Languages check for Bio2RDF::Gendr took 60.254417419433594s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.25118160247802734s
Security | Check HTTPS for Bio2RDF::Gendr took 0.15656232833862305s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.7633085250854492s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.34890222549438477s
Availability | RDF dump link check for Bio2RDF::Gendr took 6.314793348312378s
License | MR license check for Bio2RDF::Gendr took 0.42711353302001953s
License | HR license check for Bio2RDF::Gendr took 60.24442982673645s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.2918715476989746s
Understandability | Number of label check for Bio2RDF::Gendr took 10.46763277053833s
Understandability | URI regex check for Bio2RDF::Gendr took 0.5673682689666748s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.2539536952972412s
Verifiability | Authors check for Bio2RDF::Gendr took 0.25179123878479004s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.2562227249145508s
Performance | Throughput check for Bio2RDF::Gendr took 11.458537578582764s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 74.12213444709778s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.5621676445007324s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.37636637687683105s
Interlinking | skos check for Bio2RDF::Gendr took 0.8208532333374023s
Interlinking | skos check for Bio2RDF::Gendr took 0.3933846950531006s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.26044225692749023s
Currency | Creation date check for Bio2RDF::Gendr took 0.5458898544311523s
Currency | Modification date check for Bio2RDF::Gendr took 0.5253257751464844s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 108.59694027900696s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 23.599428176879883s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.4678494930267334s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.26766014099121094s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.2691926956176758s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 7.573814153671265s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.8822228908538818s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6507041454315186s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.41359972953796387s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 65.15425372123718s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.3869469165802s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.5748021602630615s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.3534672260284424s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.59708118438721s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.6941659450531006s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.4260258674621582s
Security | Sign check for Bio2RDF::Gendr took 0.2620556354522705s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 14.714333534240723s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 1.3006114959716797s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.020514488220214844s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.984306335449219e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 20.670815229415894s
Believability | Calculation of trust value for Bio2RDF::Gendr took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-gendr took 1068.5677361488342s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.46129894256591797s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0006201267242431641s
Extra | Recovery of all triples for Bio2RDF::Goa took 19.26631212234497s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.2679333686828613s
Amount of data | Number of triples check for Bio2RDF::Goa took 43.59652328491211s
Interoperability | New terms check for Bio2RDF::Goa took 42.34648633003235s
Versatility | Languages check for Bio2RDF::Goa took 60.25814867019653s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.27376818656921387s
Security | Check HTTPS for Bio2RDF::Goa took 0.15801668167114258s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.8095605373382568s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.32523655891418457s
Availability | RDF dump link check for Bio2RDF::Goa took 6.331911563873291s
License | MR license check for Bio2RDF::Goa took 0.5263397693634033s
License | HR license check for Bio2RDF::Goa took 60.25476312637329s
Amount of data | Number of property check for Bio2RDF::Goa took 0.2693185806274414s
Understandability | Number of label check for Bio2RDF::Goa took 10.418467998504639s
Understandability | URI regex check for Bio2RDF::Goa took 0.5975091457366943s
Understandability | Vocabs check for Bio2RDF::Goa took 0.2518117427825928s
Verifiability | Authors check for Bio2RDF::Goa took 0.25205540657043457s
Verifiability | Publishers check for Bio2RDF::Goa took 0.2561314105987549s
Performance | Throughput check for Bio2RDF::Goa took 11.261640071868896s
Amount of data | Check the number of entities for Bio2RDF::Goa took 74.43205261230469s
Verifiability | Contribs. check for Bio2RDF::Goa took 2.0249080657958984s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.35546088218688965s
Interlinking | skos check for Bio2RDF::Goa took 0.7808008193969727s
Interlinking | skos check for Bio2RDF::Goa took 0.3958303928375244s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.27993035316467285s
Currency | Creation date check for Bio2RDF::Goa took 0.538623571395874s
Currency | Modification date check for Bio2RDF::Goa took 0.5122687816619873s
Rep.Conc. | URIs length for Bio2RDF::Goa took 110.57538294792175s
Interoperability | New vocabularies check for Bio2RDF::Goa took 17.601874589920044s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.4297361373901367s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.2811276912689209s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.2789905071258545s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 7.175942897796631s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.8859307765960693s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6568224430084229s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.38947439193725586s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 65.55826568603516s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.4638664722442627s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 6.144917011260986s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.3458702564239502s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.57040739059448s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.6996831893920898s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.39362406730651855s
Security | Sign check for Bio2RDF::Goa took 0.26360106468200684s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 13.347493410110474s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.9110243320465088s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.02039337158203125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 5.626678466796875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 19.460843324661255s
Believability | Calculation of trust value for Bio2RDF::Goa took 2.6941299438476562e-05s
INFO | --- Analysis for bio2rdf-goa took 1061.178883075714s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.4840707778930664s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.000583648681640625s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 20.256388902664185s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.225278377532959s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 44.24055004119873s
Interoperability | New terms check for Bio2RDF::Hgnc took 44.379852294921875s
Versatility | Languages check for Bio2RDF::Hgnc took 60.256858348846436s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.27205514907836914s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.15436506271362305s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.7528724670410156s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.29233384132385254s
Availability | RDF dump link check for Bio2RDF::Hgnc took 6.311727523803711s
License | MR license check for Bio2RDF::Hgnc took 0.44660162925720215s
License | HR license check for Bio2RDF::Hgnc took 60.24057960510254s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.2649872303009033s
Understandability | Number of label check for Bio2RDF::Hgnc took 10.199671745300293s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.5827090740203857s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.25791120529174805s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.27966976165771484s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.2705817222595215s
Performance | Throughput check for Bio2RDF::Hgnc took 11.020317792892456s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 74.59411787986755s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.5971202850341797s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.36417388916015625s
Interlinking | skos check for Bio2RDF::Hgnc took 0.8184819221496582s
Interlinking | skos check for Bio2RDF::Hgnc took 0.37119340896606445s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.26955175399780273s
Currency | Creation date check for Bio2RDF::Hgnc took 0.5134353637695312s
Currency | Modification date check for Bio2RDF::Hgnc took 0.5317823886871338s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 109.18371200561523s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 34.352407455444336s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.44847750663757324s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.2589457035064697s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.2545654773712158s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 7.779495716094971s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.8823807239532471s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6670346260070801s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.4033544063568115s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.2383542060852s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.391126871109009s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 6.344247579574585s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.351996898651123s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.59145379066467s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7134287357330322s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.4339425563812256s
Security | Sign check for Bio2RDF::Hgnc took 0.26515793800354004s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 16.793760538101196s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.9408583641052246s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.02012014389038086s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00010538101196289062s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 28.284868717193604s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-hgnc took 1083.6484231948853s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.4683847427368164s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0005292892456054688s
Extra | Recovery of all triples for Bio2RDF::Homologene took 19.279099225997925s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.2303166389465332s
Amount of data | Number of triples check for Bio2RDF::Homologene took 43.864173412323s
Interoperability | New terms check for Bio2RDF::Homologene took 41.48431897163391s
Versatility | Languages check for Bio2RDF::Homologene took 60.24526381492615s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.27501869201660156s
Security | Check HTTPS for Bio2RDF::Homologene took 0.16287684440612793s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.7171669006347656s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.3148515224456787s
Availability | RDF dump link check for Bio2RDF::Homologene took 6.333016633987427s
License | MR license check for Bio2RDF::Homologene took 0.47214198112487793s
License | HR license check for Bio2RDF::Homologene took 60.24932622909546s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.27758216857910156s
Understandability | Number of label check for Bio2RDF::Homologene took 9.816585302352905s
Understandability | URI regex check for Bio2RDF::Homologene took 0.6105155944824219s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.2681596279144287s
Verifiability | Authors check for Bio2RDF::Homologene took 0.260282039642334s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.2682197093963623s
Performance | Throughput check for Bio2RDF::Homologene took 11.137021541595459s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 74.72481894493103s
Verifiability | Contribs. check for Bio2RDF::Homologene took 1.3996758460998535s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.38687992095947266s
Interlinking | skos check for Bio2RDF::Homologene took 0.8844084739685059s
Interlinking | skos check for Bio2RDF::Homologene took 0.37926387786865234s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.2616727352142334s
Currency | Creation date check for Bio2RDF::Homologene took 0.5250375270843506s
Currency | Modification date check for Bio2RDF::Homologene took 0.5426692962646484s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 109.61966443061829s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 28.168171167373657s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.4442880153656006s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.2757837772369385s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.2896885871887207s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 7.680702447891235s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8826351165771484s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6541647911071777s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.40093350410461426s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.25993776321411s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.382669448852539s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.704819202423096s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.3318486213684082s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.56561470031738s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.6984758377075195s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.43626999855041504s
Security | Sign check for Bio2RDF::Homologene took 0.2697761058807373s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 18.358224868774414s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 1.0056836605072021s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.020206451416015625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.340576171875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 34.66779923439026s
Believability | Calculation of trust value for Bio2RDF::Homologene took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-homologene took 1083.2000274658203s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 7.963180541992188e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.24046683311462402s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 3.1948089599609375e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-inoh took 4.647894859313965s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 1.284386396408081s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0006511211395263672s
Extra | Recovery of all triples for Bio2RDF::Interpro took 20.892679452896118s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.2312321662902832s
Amount of data | Number of triples check for Bio2RDF::Interpro took 44.38579082489014s
Interoperability | New terms check for Bio2RDF::Interpro took 41.53420543670654s
Versatility | Languages check for Bio2RDF::Interpro took 60.24697494506836s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.25646162033081055s
Security | Check HTTPS for Bio2RDF::Interpro took 0.1463029384613037s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.7506639957427979s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.3220250606536865s
Availability | RDF dump link check for Bio2RDF::Interpro took 6.3534629344940186s
License | MR license check for Bio2RDF::Interpro took 0.4534027576446533s
License | HR license check for Bio2RDF::Interpro took 60.24819612503052s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.2629740238189697s
Understandability | Number of label check for Bio2RDF::Interpro took 9.914661884307861s
Understandability | URI regex check for Bio2RDF::Interpro took 0.5958969593048096s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.27816033363342285s
Verifiability | Authors check for Bio2RDF::Interpro took 0.27971863746643066s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.25457310676574707s
Performance | Throughput check for Bio2RDF::Interpro took 11.049949645996094s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 74.69589066505432s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.6105449199676514s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.3606436252593994s
Interlinking | skos check for Bio2RDF::Interpro took 0.8137791156768799s
Interlinking | skos check for Bio2RDF::Interpro took 0.40715789794921875s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.2842743396759033s
Currency | Creation date check for Bio2RDF::Interpro took 0.5052444934844971s
Currency | Modification date check for Bio2RDF::Interpro took 0.5238089561462402s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 109.80781507492065s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 21.82211422920227s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.43927884101867676s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.2924153804779053s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.2691221237182617s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 6.979011058807373s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.8818800449371338s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6529831886291504s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.3806583881378174s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.0192289352417s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.37750506401062s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.132403373718262s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.3402862548828125s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.571314096450806s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.6872129440307617s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.4031813144683838s
Security | Sign check for Bio2RDF::Interpro took 0.26317882537841797s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 19.116373777389526s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.8488571643829346s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.020254850387573242s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00010704994201660156s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 31.17075204849243s
Believability | Calculation of trust value for Bio2RDF::Interpro took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-interpro took 1075.4983236789703s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.13395023345947266s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0006339550018310547s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.32878923416137695s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.02001190185546875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.081031799316406e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 5.9604644775390625e-06s
INFO | --- Analysis for bio2rdf-iproclass took 16.850714445114136s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.4669344425201416s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0003979206085205078s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 20.668633937835693s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.3140366077423096s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 44.376508712768555s
Interoperability | New terms check for Bio2RDF::Irefindex took 42.54574275016785s
Versatility | Languages check for Bio2RDF::Irefindex took 60.25321698188782s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.26589488983154297s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.15703797340393066s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.5889122486114502s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.3169560432434082s
Availability | RDF dump link check for Bio2RDF::Irefindex took 6.360494375228882s
License | MR license check for Bio2RDF::Irefindex took 0.47445034980773926s
License | HR license check for Bio2RDF::Irefindex took 60.23947477340698s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.2536003589630127s
Understandability | Number of label check for Bio2RDF::Irefindex took 9.88711428642273s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.581397533416748s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.2516670227050781s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.26570725440979004s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.2715644836425781s
Performance | Throughput check for Bio2RDF::Irefindex took 11.261393308639526s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 74.29219579696655s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 2.059086322784424s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.3655412197113037s
Interlinking | skos check for Bio2RDF::Irefindex took 0.8410093784332275s
Interlinking | skos check for Bio2RDF::Irefindex took 0.4063229560852051s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.2663581371307373s
Currency | Creation date check for Bio2RDF::Irefindex took 0.5340259075164795s
Currency | Modification date check for Bio2RDF::Irefindex took 0.5229477882385254s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 108.83492374420166s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 23.878750562667847s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.4013190269470215s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.2703523635864258s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.28975582122802734s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 7.204748630523682s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.8815045356750488s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6510388851165771s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.48886752128601074s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 65.08649015426636s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.3669097423553467s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.5108420848846436s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.341573715209961s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.563167572021484s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7095584869384766s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.4099593162536621s
Security | Sign check for Bio2RDF::Irefindex took 0.2818171977996826s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 14.212448596954346s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 1.4139130115509033s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.02011895179748535s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 8.034706115722656e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 16.672192335128784s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 5.9604644775390625e-06s
INFO | --- Analysis for bio2rdf-irefindex took 1060.247920513153s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 3.9577484130859375e-05s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.24888920783996582s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.019801855087280273s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.246566772460938e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 5.7220458984375e-06s
INFO | --- Analysis for bio2rdf-kegg took 4.237991571426392s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 4.506111145019531e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.0002224445343017578s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.25286149978637695s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.02022385597229004s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 2.7894973754882812e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-kegg-biopax took 3.8260245323181152s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.1354062557220459s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.8285150527954102s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020112276077270508s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 2.8371810913085938e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 5.4836273193359375e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 9.675869703292847s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.4550144672393799s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0005130767822265625s
Extra | Recovery of all triples for Bio2RDF::Lsr took 19.546054363250732s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.2472097873687744s
Amount of data | Number of triples check for Bio2RDF::Lsr took 44.32603645324707s
Interoperability | New terms check for Bio2RDF::Lsr took 42.24660038948059s
Versatility | Languages check for Bio2RDF::Lsr took 60.22760343551636s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.2573721408843994s
Security | Check HTTPS for Bio2RDF::Lsr took 0.16773533821105957s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.8821225166320801s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.33229804039001465s
Availability | RDF dump link check for Bio2RDF::Lsr took 6.297628402709961s
License | MR license check for Bio2RDF::Lsr took 0.5664887428283691s
License | HR license check for Bio2RDF::Lsr took 60.264591455459595s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.2593255043029785s
Understandability | Number of label check for Bio2RDF::Lsr took 9.953266859054565s
Understandability | URI regex check for Bio2RDF::Lsr took 0.5770626068115234s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.25913405418395996s
Verifiability | Authors check for Bio2RDF::Lsr took 0.26337361335754395s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.2633786201477051s
Performance | Throughput check for Bio2RDF::Lsr took 11.473366975784302s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 74.26538038253784s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.583207368850708s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.34918904304504395s
Interlinking | skos check for Bio2RDF::Lsr took 0.8952317237854004s
Interlinking | skos check for Bio2RDF::Lsr took 0.39887142181396484s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.2680485248565674s
Currency | Creation date check for Bio2RDF::Lsr took 0.5327539443969727s
Currency | Modification date check for Bio2RDF::Lsr took 0.49163341522216797s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 110.25902915000916s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 22.7819664478302s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.4584052562713623s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.2910008430480957s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.28601884841918945s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 7.5433573722839355s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.8828122615814209s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.6561589241027832s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.5036675930023193s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 65.19424843788147s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.3893356323242188s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.295832872390747s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.354893445968628s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.600979804992676s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.7035443782806396s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.4407932758331299s
Security | Sign check for Bio2RDF::Lsr took 0.26804447174072266s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 14.490493297576904s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.5434656143188477s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.020046472549438477s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 21.588755130767822s
Believability | Calculation of trust value for Bio2RDF::Lsr took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-lsr took 1062.0566294193268s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.487729549407959s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0005931854248046875s
Extra | Recovery of all triples for Bio2RDF::Mesh took 20.150253295898438s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.2430264949798584s
Amount of data | Number of triples check for Bio2RDF::Mesh took 50.696513414382935s
Interoperability | New terms check for Bio2RDF::Mesh took 41.63238525390625s
Versatility | Languages check for Bio2RDF::Mesh took 60.25279402732849s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.25328779220581055s
Security | Check HTTPS for Bio2RDF::Mesh took 0.14409232139587402s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.766639232635498s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.3286459445953369s
Availability | RDF dump link check for Bio2RDF::Mesh took 6.335782527923584s
License | MR license check for Bio2RDF::Mesh took 0.6190440654754639s
License | HR license check for Bio2RDF::Mesh took 60.250890254974365s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.2744290828704834s
Understandability | Number of label check for Bio2RDF::Mesh took 10.357521057128906s
Understandability | URI regex check for Bio2RDF::Mesh took 0.5871102809906006s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.2501399517059326s
Verifiability | Authors check for Bio2RDF::Mesh took 0.2587568759918213s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.2701292037963867s
Performance | Throughput check for Bio2RDF::Mesh took 10.57316255569458s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 75.85955667495728s
Verifiability | Contribs. check for Bio2RDF::Mesh took 1.398303508758545s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.35822510719299316s
Interlinking | skos check for Bio2RDF::Mesh took 1.048304796218872s
Interlinking | skos check for Bio2RDF::Mesh took 0.3396425247192383s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.26950502395629883s
Currency | Creation date check for Bio2RDF::Mesh took 0.5292422771453857s
Currency | Modification date check for Bio2RDF::Mesh took 0.5255904197692871s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 112.52758932113647s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 25.50055193901062s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.4630725383758545s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.27147841453552246s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.27057933807373047s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 6.97949743270874s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.8781213760375977s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6626861095428467s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.4031393527984619s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 65.58460783958435s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.3961215019226074s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.293360233306885s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.3538711071014404s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.577950954437256s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.6883876323699951s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.4332387447357178s
Security | Sign check for Bio2RDF::Mesh took 0.2850615978240967s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 13.295172929763794s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 1.0730514526367188s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.020220518112182617s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 8.106231689453125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 24.983983278274536s
Believability | Calculation of trust value for Bio2RDF::Mesh took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-mesh took 1081.094267129898s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 1.2778639793395996s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0006570816040039062s
Extra | Recovery of all triples for Bio2RDF::Mgi took 19.592751026153564s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.2526144981384277s
Amount of data | Number of triples check for Bio2RDF::Mgi took 43.721433877944946s
Interoperability | New terms check for Bio2RDF::Mgi took 41.37745809555054s
Versatility | Languages check for Bio2RDF::Mgi took 60.244699478149414s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.2725086212158203s
Security | Check HTTPS for Bio2RDF::Mgi took 0.1453533172607422s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.8109598159790039s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.310197114944458s
Availability | RDF dump link check for Bio2RDF::Mgi took 6.366262912750244s
License | MR license check for Bio2RDF::Mgi took 0.48415470123291016s
License | HR license check for Bio2RDF::Mgi took 60.25041151046753s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.27058911323547363s
Understandability | Number of label check for Bio2RDF::Mgi took 9.750857591629028s
Understandability | URI regex check for Bio2RDF::Mgi took 0.5945641994476318s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.24858403205871582s
Verifiability | Authors check for Bio2RDF::Mgi took 0.24963927268981934s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.28557848930358887s
Performance | Throughput check for Bio2RDF::Mgi took 11.300573348999023s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 73.83398675918579s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.6222410202026367s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.34148716926574707s
Interlinking | skos check for Bio2RDF::Mgi took 0.9549071788787842s
Interlinking | skos check for Bio2RDF::Mgi took 0.34348487854003906s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.25690126419067383s
Currency | Creation date check for Bio2RDF::Mgi took 0.5388922691345215s
Currency | Modification date check for Bio2RDF::Mgi took 0.5196337699890137s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 108.85202503204346s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 23.42754888534546s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.3984348773956299s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.27433013916015625s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.28475403785705566s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 7.505187273025513s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.8778238296508789s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6527807712554932s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.42953062057495117s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.25868034362793s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.4372923374176025s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 6.319512844085693s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.336418867111206s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.56887650489807s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7129173278808594s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.4252176284790039s
Security | Sign check for Bio2RDF::Mgi took 0.2817676067352295s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 16.421433448791504s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.8690776824951172s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.02031683921813965s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 9.512901306152344e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 16.062613010406494s
Believability | Calculation of trust value for Bio2RDF::Mgi took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-mgi took 1063.6029093265533s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.4909379482269287s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0005948543548583984s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 19.50288438796997s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.2539544105529785s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 45.84943723678589s
Interoperability | New terms check for Bio2RDF::Ncbigene took 41.32729506492615s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.250345945358276s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.26125240325927734s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.1649181842803955s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.7608892917633057s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.3402435779571533s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 6.445936441421509s
License | MR license check for Bio2RDF::Ncbigene took 0.5457620620727539s
License | HR license check for Bio2RDF::Ncbigene took 60.24589157104492s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.260817289352417s
Understandability | Number of label check for Bio2RDF::Ncbigene took 10.610107421875s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.6110234260559082s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.24825620651245117s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.27670812606811523s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.27541375160217285s
Performance | Throughput check for Bio2RDF::Ncbigene took 11.527994632720947s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 73.56968760490417s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 1.410097360610962s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.3559110164642334s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.8159973621368408s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.44060754776000977s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.23989343643188477s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.5084044933319092s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.5250506401062012s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 109.0292181968689s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 34.60192346572876s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.4200279712677002s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2738468647003174s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.2590610980987549s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 7.122702121734619s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.8748087882995605s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6535427570343018s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.39679408073425293s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.22853589057922s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.411524534225464s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.1624531745910645s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.3316576480865479s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.56128716468811s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.692340612411499s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.4605131149291992s
Security | Sign check for Bio2RDF::Ncbigene took 0.27617621421813965s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 18.38261580467224s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.5634334087371826s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.019997835159301758s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00011992454528808594s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 18.95416259765625s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-ncbigene took 1081.1112408638s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.4632151126861572s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0005812644958496094s
Extra | Recovery of all triples for Bio2RDF::Ndc took 18.859325885772705s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.2559704780578613s
Amount of data | Number of triples check for Bio2RDF::Ndc took 45.55788540840149s
Interoperability | New terms check for Bio2RDF::Ndc took 42.271600008010864s
Versatility | Languages check for Bio2RDF::Ndc took 60.24750351905823s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.25643038749694824s
Security | Check HTTPS for Bio2RDF::Ndc took 0.1553354263305664s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.5553693771362305s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.31987857818603516s
Availability | RDF dump link check for Bio2RDF::Ndc took 6.270411014556885s
License | MR license check for Bio2RDF::Ndc took 0.5371909141540527s
License | HR license check for Bio2RDF::Ndc took 60.23894691467285s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.2766530513763428s
Understandability | Number of label check for Bio2RDF::Ndc took 10.755548238754272s
Understandability | URI regex check for Bio2RDF::Ndc took 0.5802481174468994s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.2439417839050293s
Verifiability | Authors check for Bio2RDF::Ndc took 0.26335620880126953s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.26071882247924805s
Performance | Throughput check for Bio2RDF::Ndc took 10.792607545852661s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 74.60496807098389s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.5859706401824951s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.34782934188842773s
Interlinking | skos check for Bio2RDF::Ndc took 0.8074486255645752s
Interlinking | skos check for Bio2RDF::Ndc took 0.35268211364746094s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.26866602897644043s
Currency | Creation date check for Bio2RDF::Ndc took 0.481231689453125s
Currency | Modification date check for Bio2RDF::Ndc took 0.5244982242584229s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 112.52651619911194s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 18.41558575630188s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.4193422794342041s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.27252650260925293s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.27236294746398926s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 7.093609809875488s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.8780388832092285s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6593425273895264s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.40701770782470703s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 65.65301966667175s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.4165561199188232s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.744661808013916s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.332479476928711s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.556203842163086s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7130064964294434s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.4288978576660156s
Security | Sign check for Bio2RDF::Ndc took 0.2644777297973633s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 12.811128616333008s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.5008656978607178s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020089149475097656s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 5.888938903808594e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 23.06538152694702s
Believability | Calculation of trust value for Bio2RDF::Ndc took 6.198883056640625e-06s
INFO | --- Analysis for bio2rdf-ndc took 1057.2991087436676s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 4.029273986816406e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.00022411346435546875s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.278580904006958s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.02030801773071289s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 5.245208740234375e-06s
INFO | --- Analysis for bio2rdf-netpath took 2.990140914916992s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.1310110092163086s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0006062984466552734s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.26614952087402344s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.020157814025878906s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 2.956390380859375e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-nextprot took 3.3301868438720703s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.46039414405822754s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0006196498870849609s
Extra | Recovery of all triples for Bio2RDF::Omim took 20.466763257980347s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.2156884670257568s
Amount of data | Number of triples check for Bio2RDF::Omim took 44.56446290016174s
Interoperability | New terms check for Bio2RDF::Omim took 44.7313027381897s
Versatility | Languages check for Bio2RDF::Omim took 60.23795485496521s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.27976560592651367s
Security | Check HTTPS for Bio2RDF::Omim took 0.15605473518371582s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.7033059597015381s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.315263032913208s
Availability | RDF dump link check for Bio2RDF::Omim took 6.439034938812256s
License | MR license check for Bio2RDF::Omim took 0.47385168075561523s
License | HR license check for Bio2RDF::Omim took 60.26029372215271s
Amount of data | Number of property check for Bio2RDF::Omim took 0.26062822341918945s
Understandability | Number of label check for Bio2RDF::Omim took 10.019375085830688s
Understandability | URI regex check for Bio2RDF::Omim took 0.5652523040771484s
Understandability | Vocabs check for Bio2RDF::Omim took 0.2717890739440918s
Verifiability | Authors check for Bio2RDF::Omim took 0.2702972888946533s
Verifiability | Publishers check for Bio2RDF::Omim took 0.25238609313964844s
Performance | Throughput check for Bio2RDF::Omim took 11.038876295089722s
Amount of data | Check the number of entities for Bio2RDF::Omim took 74.33592796325684s
Verifiability | Contribs. check for Bio2RDF::Omim took 2.0600409507751465s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.3654332160949707s
Interlinking | skos check for Bio2RDF::Omim took 0.8129456043243408s
Interlinking | skos check for Bio2RDF::Omim took 0.3406836986541748s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.28984689712524414s
Currency | Creation date check for Bio2RDF::Omim took 0.514312744140625s
Currency | Modification date check for Bio2RDF::Omim took 0.5236160755157471s
Rep.Conc. | URIs length for Bio2RDF::Omim took 110.88070678710938s
Interoperability | New vocabularies check for Bio2RDF::Omim took 20.6269109249115s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.4591667652130127s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.27785539627075195s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.29963135719299316s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 7.870311260223389s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.8775405883789062s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6568005084991455s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.4691019058227539s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 65.35969138145447s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.3864526748657227s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 6.560889720916748s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.3500475883483887s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.592920780181885s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.694549560546875s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.4367539882659912s
Security | Sign check for Bio2RDF::Omim took 0.26224732398986816s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 15.220207929611206s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.9491620063781738s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.020311594009399414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00013113021850585938s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 25.345678567886353s
Believability | Calculation of trust value for Bio2RDF::Omim took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-omim took 1068.825112104416s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 4.1484832763671875e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0003764629364013672s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.28125643730163574s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.020017147064208984s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.886222839355469e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 4.024932861328125s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.4633972644805908s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0005762577056884766s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 20.641536474227905s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.2887482643127441s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 43.56583309173584s
Interoperability | New terms check for Bio2RDF::Orphanet took 45.90950918197632s
Versatility | Languages check for Bio2RDF::Orphanet took 60.244192600250244s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.26482152938842773s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.14635729789733887s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.8202657699584961s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.3267943859100342s
Availability | RDF dump link check for Bio2RDF::Orphanet took 6.376091003417969s
License | MR license check for Bio2RDF::Orphanet took 0.4244213104248047s
License | HR license check for Bio2RDF::Orphanet took 60.25597405433655s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.2637977600097656s
Understandability | Number of label check for Bio2RDF::Orphanet took 10.026699781417847s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.5883998870849609s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.2544543743133545s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.26889634132385254s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.26681065559387207s
Performance | Throughput check for Bio2RDF::Orphanet took 11.24146318435669s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 74.83482646942139s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.5828325748443604s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.32848405838012695s
Interlinking | skos check for Bio2RDF::Orphanet took 0.8700723648071289s
Interlinking | skos check for Bio2RDF::Orphanet took 0.49685239791870117s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.27126049995422363s
Currency | Creation date check for Bio2RDF::Orphanet took 0.518078088760376s
Currency | Modification date check for Bio2RDF::Orphanet took 0.5223515033721924s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 112.13083291053772s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 29.74158024787903s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.4448261260986328s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.2887427806854248s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.27665162086486816s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 7.093810081481934s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.8855822086334229s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6582422256469727s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.4289820194244385s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 65.77232575416565s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.3483798503875732s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.8433921337127686s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.3605341911315918s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.586596965789795s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.704796552658081s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.4237501621246338s
Security | Sign check for Bio2RDF::Orphanet took 0.2577474117279053s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 12.332729578018188s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.3878657817840576s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.020656347274780273s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 8.702278137207031e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 26.279380559921265s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-orphanet took 1082.3845789432526s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.1377243995666504s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.7795629501342773s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.02013421058654785s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.62396240234375e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 10.702926874160767s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.46630191802978516s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0005707740783691406s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 20.637353897094727s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.2390453815460205s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 44.47287917137146s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 44.772780418395996s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.23291850090027s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.26319098472595215s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.15915966033935547s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 1.1461012363433838s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.31052112579345703s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 6.314044713973999s
License | MR license check for Bio2RDF::Pharmgkb took 0.47101569175720215s
License | HR license check for Bio2RDF::Pharmgkb took 60.260984897613525s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.24889826774597168s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 10.501838445663452s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5717453956604004s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.26312685012817383s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.2571423053741455s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.2659449577331543s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.637275695800781s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 74.5730037689209s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 2.0522289276123047s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.36470580101013184s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.8377223014831543s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.35705041885375977s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.27028870582580566s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.5165352821350098s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.5344321727752686s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 109.97614550590515s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 19.18291687965393s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.44325876235961914s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.2617480754852295s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.26529955863952637s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 7.936155557632446s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.8865458965301514s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6562063694000244s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.41275596618652344s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 65.04862356185913s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.4467899799346924s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 7.277700901031494s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.3568370342254639s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.59481716156006s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7100977897644043s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.43798303604125977s
Security | Sign check for Bio2RDF::Pharmgkb took 0.2967860698699951s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 12.605883598327637s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.9493129253387451s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.02022552490234375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.653236389160156e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 19.450035333633423s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-pharmgkb took 1063.3773477077484s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 3.9577484130859375e-05s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.2609272003173828s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.019911766052246094s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 4.76837158203125e-06s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 3.385533094406128s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 4.029273986816406e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.24905872344970703s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.020165205001831055s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 5.9604644775390625e-06s
INFO | --- Analysis for bio2rdf-pid took 3.842193365097046s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 3.981590270996094e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.00033545494079589844s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.25039052963256836s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.020140409469604492s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 2.956390380859375e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-pubchem-2 took 2.8957226276397705s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.456895112991333s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.00035500526428222656s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 19.45185661315918s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2871429920196533s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 43.97937488555908s
Interoperability | New terms check for Bio2RDF::Pubmed took 41.26565504074097s
Versatility | Languages check for Bio2RDF::Pubmed took 60.241363525390625s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.27952003479003906s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.15569186210632324s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.9892282485961914s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.33298635482788086s
Availability | RDF dump link check for Bio2RDF::Pubmed took 6.343758583068848s
License | MR license check for Bio2RDF::Pubmed took 0.5318999290466309s
License | HR license check for Bio2RDF::Pubmed took 60.254127740859985s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.27080273628234863s
Understandability | Number of label check for Bio2RDF::Pubmed took 11.232263803482056s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.5859968662261963s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.2665557861328125s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.2624349594116211s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.2581784725189209s
Performance | Throughput check for Bio2RDF::Pubmed took 11.40397310256958s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 75.02188181877136s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 1.1041498184204102s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.3528916835784912s
Interlinking | skos check for Bio2RDF::Pubmed took 0.9195296764373779s
Interlinking | skos check for Bio2RDF::Pubmed took 0.33531618118286133s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.27133655548095703s
Currency | Creation date check for Bio2RDF::Pubmed took 0.5340940952301025s
Currency | Modification date check for Bio2RDF::Pubmed took 0.5082128047943115s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 108.7652018070221s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 56.645392179489136s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.404543399810791s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.27615833282470703s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.2784457206726074s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 6.990131378173828s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.8842935562133789s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6521420478820801s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.4273505210876465s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.48656439781189s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.4332292079925537s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 7.199665069580078s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.36338210105896s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.60042428970337s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.7059307098388672s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.636176347732544s
Security | Sign check for Bio2RDF::Pubmed took 0.2883315086364746s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 20.567527055740356s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.5281288623809814s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.02054286003112793s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.0001366138458251953s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 18.674713611602783s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-pubmed took 1097.3133382797241s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 4.696846008300781e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.00022339820861816406s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.749582052230835s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.020000934600830078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 6.961822509765625e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-reactome took 4.215284585952759s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 4.029273986816406e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.24218344688415527s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.020024776458740234s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 5.2928924560546875e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 9.298324584960938e-06s
INFO | --- Analysis for bio2rdf-rhea took 4.233874320983887s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.13466644287109375s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.2568955421447754s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.02005934715270996s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.534027099609375e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 5.9604644775390625e-06s
INFO | --- Analysis for bio2rdf-sabiork took 8.826992750167847s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.4537224769592285s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0005207061767578125s
Extra | Recovery of all triples for Bio2RDF::Sgd took 19.287336111068726s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.2705414295196533s
Amount of data | Number of triples check for Bio2RDF::Sgd took 43.70630669593811s
Interoperability | New terms check for Bio2RDF::Sgd took 41.05008602142334s
Versatility | Languages check for Bio2RDF::Sgd took 60.274921894073486s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.2717881202697754s
Security | Check HTTPS for Bio2RDF::Sgd took 0.15614891052246094s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.8326802253723145s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.33534932136535645s
Availability | RDF dump link check for Bio2RDF::Sgd took 6.3714964389801025s
License | MR license check for Bio2RDF::Sgd took 0.6335985660552979s
License | HR license check for Bio2RDF::Sgd took 60.24810171127319s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.307659387588501s
Understandability | Number of label check for Bio2RDF::Sgd took 10.282267570495605s
Understandability | URI regex check for Bio2RDF::Sgd took 0.6020853519439697s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.26818323135375977s
Verifiability | Authors check for Bio2RDF::Sgd took 0.2772078514099121s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.26697397232055664s
Performance | Throughput check for Bio2RDF::Sgd took 11.334421873092651s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 75.12896347045898s
Verifiability | Contribs. check for Bio2RDF::Sgd took 2.016078233718872s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.33570408821105957s
Interlinking | skos check for Bio2RDF::Sgd took 0.7276554107666016s
Interlinking | skos check for Bio2RDF::Sgd took 0.3559887409210205s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.2866325378417969s
Currency | Creation date check for Bio2RDF::Sgd took 0.48617029190063477s
Currency | Modification date check for Bio2RDF::Sgd took 0.517362117767334s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 111.11963701248169s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 24.72098445892334s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.4763956069946289s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.27265477180480957s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.2704145908355713s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 6.898502826690674s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.885200023651123s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6611933708190918s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.43303751945495605s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 65.11141705513s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.3689894676208496s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 7.450809955596924s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.3594226837158203s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.59182548522949s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.6988120079040527s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.41451334953308105s
Security | Sign check for Bio2RDF::Sgd took 0.27182626724243164s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 17.148468732833862s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.9321370124816895s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020215749740600586s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00010228157043457031s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 17.028326749801636s
Believability | Calculation of trust value for Bio2RDF::Sgd took 5.9604644775390625e-06s
INFO | --- Analysis for bio2rdf-sgd took 1063.32603764534s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.1484832763671875e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.269639253616333s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.019945621490478516s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.409385681152344e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-sgd-resources took 4.531606912612915s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.4611642360687256s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0005383491516113281s
Extra | Recovery of all triples for Bio2RDF::Sider took 21.971606492996216s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.2350883483886719s
Amount of data | Number of triples check for Bio2RDF::Sider took 43.938207149505615s
Interoperability | New terms check for Bio2RDF::Sider took 40.470481395721436s
Versatility | Languages check for Bio2RDF::Sider took 60.27674746513367s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.2672271728515625s
Security | Check HTTPS for Bio2RDF::Sider took 0.17224502563476562s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.9099564552307129s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.30785465240478516s
Availability | RDF dump link check for Bio2RDF::Sider took 6.360777854919434s
License | MR license check for Bio2RDF::Sider took 0.4798271656036377s
License | HR license check for Bio2RDF::Sider took 60.259828329086304s
Amount of data | Number of property check for Bio2RDF::Sider took 0.28147268295288086s
Understandability | Number of label check for Bio2RDF::Sider took 10.828651428222656s
Understandability | URI regex check for Bio2RDF::Sider took 0.596933126449585s
Understandability | Vocabs check for Bio2RDF::Sider took 0.2599635124206543s
Verifiability | Authors check for Bio2RDF::Sider took 0.24007844924926758s
Verifiability | Publishers check for Bio2RDF::Sider took 0.23999524116516113s
Performance | Throughput check for Bio2RDF::Sider took 11.256439208984375s
Amount of data | Check the number of entities for Bio2RDF::Sider took 74.75234699249268s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.5751376152038574s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.3507564067840576s
Interlinking | skos check for Bio2RDF::Sider took 0.7427065372467041s
Interlinking | skos check for Bio2RDF::Sider took 0.37398338317871094s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.24752044677734375s
Currency | Creation date check for Bio2RDF::Sider took 0.5186984539031982s
Currency | Modification date check for Bio2RDF::Sider took 0.4957592487335205s
Rep.Conc. | URIs length for Bio2RDF::Sider took 108.69895362854004s
Interoperability | New vocabularies check for Bio2RDF::Sider took 22.36184048652649s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.4083549976348877s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.27375221252441406s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.2813758850097656s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 7.612874984741211s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.8752303123474121s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6563668251037598s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.41390180587768555s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 65.17784237861633s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.3794422149658203s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 7.374435901641846s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.3590245246887207s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.61164855957031s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7102599143981934s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.4592471122741699s
Security | Sign check for Bio2RDF::Sider took 0.2634422779083252s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 14.502055883407593s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.4218745231628418s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.020379066467285156s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 3.8623809814453125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 19.403464555740356s
Believability | Calculation of trust value for Bio2RDF::Sider took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-sider took 1062.214192867279s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 6.4849853515625e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.2805023193359375s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.01994466781616211s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 3.3855438232421875e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-spike took 5.111156225204468s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 5.53131103515625e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.2780733108520508s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.020175457000732422s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.267692565917969e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 6.198883056640625e-06s
INFO | --- Analysis for bio2rdf-taxon took 3.059473991394043s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.4616522789001465s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0005619525909423828s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 19.557836294174194s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.2819011211395264s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 43.79198455810547s
Interoperability | New terms check for Bio2RDF::Taxonomy took 41.911494970321655s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.23751711845398s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.24425292015075684s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.14532256126403809s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.805945634841919s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.3480701446533203s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 6.441660165786743s
License | MR license check for Bio2RDF::Taxonomy took 0.4590449333190918s
License | HR license check for Bio2RDF::Taxonomy took 60.236321687698364s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.25824999809265137s
Understandability | Number of label check for Bio2RDF::Taxonomy took 10.782728672027588s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.5745968818664551s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.26792383193969727s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.27352356910705566s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.2459423542022705s
Performance | Throughput check for Bio2RDF::Taxonomy took 11.432088375091553s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 73.3424141407013s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 2.0624639987945557s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.3539695739746094s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.8744039535522461s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.35414671897888184s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.2548215389251709s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.5158240795135498s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.5236246585845947s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 110.24810791015625s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 19.81763458251953s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.43143224716186523s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.2952749729156494s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.2956538200378418s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 7.300805568695068s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8810606002807617s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6498663425445557s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.4142181873321533s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 65.37542653083801s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.4140241146087646s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 6.44579553604126s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.3553767204284668s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.58044147491455s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.697685718536377s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.41106557846069336s
Security | Sign check for Bio2RDF::Taxonomy took 0.27121758460998535s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 12.013680458068848s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 1.398820400238037s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.020246505737304688s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 9.560585021972656e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 27.173597812652588s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 5.9604644775390625e-06s
INFO | --- Analysis for bio2rdf-taxonomy took 1065.1812205314636s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.13492369651794434s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0007307529449462891s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.36933183670043945s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.020059585571289062s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.337860107421875e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 18.99564218521118s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.48249316215515137s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.00028133392333984375s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 18.8395414352417s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.2278661727905273s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 44.922563791275024s
Interoperability | New terms check for Bio2RDF::Wormbase took 41.813767194747925s
Versatility | Languages check for Bio2RDF::Wormbase took 60.226375579833984s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.26144909858703613s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.15637660026550293s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.6637213230133057s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.34047627449035645s
Availability | RDF dump link check for Bio2RDF::Wormbase took 6.4503014087677s
License | MR license check for Bio2RDF::Wormbase took 0.45018649101257324s
License | HR license check for Bio2RDF::Wormbase took 60.244669914245605s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.26697659492492676s
Understandability | Number of label check for Bio2RDF::Wormbase took 9.855940341949463s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.6032145023345947s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.2714543342590332s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.26859235763549805s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.24737000465393066s
Performance | Throughput check for Bio2RDF::Wormbase took 11.446224689483643s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 75.67218232154846s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.5843136310577393s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.36114072799682617s
Interlinking | skos check for Bio2RDF::Wormbase took 0.774594783782959s
Interlinking | skos check for Bio2RDF::Wormbase took 0.3428611755371094s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.267240047454834s
Currency | Creation date check for Bio2RDF::Wormbase took 0.5103158950805664s
Currency | Modification date check for Bio2RDF::Wormbase took 0.5455913543701172s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 118.31586480140686s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 19.26276707649231s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.4434340000152588s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.2956225872039795s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.2704582214355469s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 8.284321308135986s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.879453182220459s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6610617637634277s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.4294548034667969s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 65.45070576667786s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.383850574493408s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 7.465980052947998s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.358234167098999s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.58510112762451s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7013437747955322s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.4369795322418213s
Security | Sign check for Bio2RDF::Wormbase took 0.272993803024292s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 11.398520708084106s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.9373672008514404s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.020225048065185547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.225440979003906e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 18.000702619552612s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-wormbase took 1065.805471420288s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 4.744529724121094e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.00022101402282714844s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.2753782272338867s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.019804000854492188s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.1444091796875e-05s
Believability | Calculation of trust value for Biografías y Vidas took 7.3909759521484375e-06s
INFO | --- Analysis for biografiasyvidas took 3.751551628112793s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.2529137134552002s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.00020503997802734375s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.3039436340332031s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.0202023983001709s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 9.083747863769531e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 4.76837158203125e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 3.173896312713623s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 4.3392181396484375e-05s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.27970337867736816s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.020795345306396484s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 3.075599670410156e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 5.9604644775390625e-06s
INFO | --- Analysis for biolit took 2.9702706336975098s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 0.00010800361633300781s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0006139278411865234s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.3904764652252197s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.0201876163482666s
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.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 3.8623809814453125e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 5.9604644775390625e-06s
INFO | --- Analysis for biolod-pdb took 7.6613287925720215s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.6593067646026611s
Availability | VoID file availability check for BioModels RDF took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.24676847457885742s
Reputation | Calculation of the PageRank for BioModels RDF took 0.02010202407836914s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.5762786865234375e-05s
Believability | Calculation of trust value for BioModels RDF took 5.7220458984375e-06s
INFO | --- Analysis for biomodels-rdf took 4.5946526527404785s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.72414493560791s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.2920222282409668s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020148038864135742s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.361701965332031e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 5.4836273193359375e-06s
INFO | --- Analysis for Biop took 7.040469646453857s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.076957702636719e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.279616117477417s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.02009725570678711s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.4332275390625e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 5.7220458984375e-06s
INFO | --- Analysis for Bioportal took 2.518721342086792s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 4.982948303222656e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.2575654983520508s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.020177364349365234s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006263256072998047s
Believability | Calculation of trust value for Amphibian gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-aao took 2.8246006965637207s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.2438507080078125e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.26253175735473633s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.02071690559387207s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0002846717834472656s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-aba took 2.7018446922302246s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.00042247772216796875s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.2679104804992676s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.021720409393310547s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015408992767333984s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 3.5762786865234375e-06s
INFO | --- Analysis for bioportal-acgt took 2.7047250270843506s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 5.4836273193359375e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.24386358261108398s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.02047586441040039s
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.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003209114074707031s
Believability | Calculation of trust value for Animal natural history and life history took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-adw took 2.554377794265747s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.28268003463745117s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.02126598358154297s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.00046253204345703125s
Believability | Calculation of trust value for Anatomical Entity Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-aeo took 2.6373064517974854s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.28411436080932617s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.02022719383239746s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009889602661132812s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-aero took 2.7034618854522705s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.029273986816406e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.26653218269348145s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.019945144653320312s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0004017353057861328s
Believability | Calculation of trust value for AI/RHEUM took 3.814697265625e-06s
INFO | --- Analysis for bioportal-air took 2.635244369506836s
Availability | SPARQL endpoint availability check for Amino Acid took 5.030632019042969e-05s
Availability | VoID file availability check for Amino Acid took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.2813258171081543s
Reputation | Calculation of the PageRank for Amino Acid took 0.02023911476135254s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.000247955322265625s
Believability | Calculation of trust value for Amino Acid took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-amino-acid took 2.665371894836426s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.2581520080566406s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.02005147933959961s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0002810955047607422s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-apo took 2.6733109951019287s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 4.0531158447265625e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.26419806480407715s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020210742950439453s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00023055076599121094s
Believability | Calculation of trust value for African Traditional Medicine took 3.5762786865234375e-06s
INFO | --- Analysis for bioportal-atmo took 2.7645986080169678s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.172325134277344e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0010302066802978516s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.23879432678222656s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.02046370506286621s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 8.797645568847656e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ato took 2.5822620391845703s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.2731740474700928s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.020272493362426758s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013511180877685547s
Believability | Calculation of trust value for BioAssay Ontology took 3.5762786865234375e-06s
INFO | --- Analysis for bioportal-bao took 2.632596015930176s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 4.124641418457031e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0011148452758789062s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.2547757625579834s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.02002692222595215s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.00037384033203125s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 2.5901451110839844s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.26643872261047363s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.02039647102355957s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003185272216796875s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-bcgo took 2.6469192504882812s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 5.2928924560546875e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.2630627155303955s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020184755325317383s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0013790130615234375s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-bdo took 2.613325834274292s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.2722194194793701s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.020075321197509766s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0004994869232177734s
Believability | Calculation of trust value for Basic Formal Ontology took 3.5762786865234375e-06s
INFO | --- Analysis for bioportal-bfo took 2.6135196685791016s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.172325134277344e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.3019225597381592s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.020074844360351562s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007355213165283203s
Believability | Calculation of trust value for Bleeding History Phenotype took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-bho took 2.6683013439178467s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.172325134277344e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.27796483039855957s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.019964933395385742s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004317760467529297s
Believability | Calculation of trust value for Bilateria anatomy took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-bila took 2.633070468902588s
Availability | SPARQL endpoint availability check for BIRNLex took 4.0531158447265625e-05s
Availability | VoID file availability check for BIRNLex took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.2630302906036377s
Reputation | Calculation of the PageRank for BIRNLex took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for BIRNLex took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0015001296997070312s
Believability | Calculation of trust value for BIRNLex took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-birnlex took 2.6765103340148926s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.27959108352661133s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.019982576370239258s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007529258728027344s
Believability | Calculation of trust value for Gene Regulation Ontology took 3.5762786865234375e-06s
INFO | --- Analysis for bioportal-bootstrep took 2.545088052749634s
Availability | SPARQL endpoint availability check for BioPAX took 4.315376281738281e-05s
Availability | VoID file availability check for BioPAX took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for BioPAX took 0.27807116508483887s
Reputation | Calculation of the PageRank for BioPAX took 0.02005457878112793s
Interlinking | Calculation of Degree of Connection for BioPAX took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for BioPAX took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for BioPAX took 8.988380432128906e-05s
Believability | Calculation of trust value for BioPAX took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-bp took 2.746323347091675s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 4.6253204345703125e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.2683286666870117s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.020462512969970703s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003218650817871094s
Believability | Calculation of trust value for Biomedical Resource Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-bro_x1 took 2.6162614822387695s
Availability | SPARQL endpoint availability check for Spatial Ontology took 6.437301635742188e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.269575834274292s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.020186185836791992s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.0002105236053466797s
Believability | Calculation of trust value for Spatial Ontology took 3.5762786865234375e-06s
INFO | --- Analysis for bioportal-bspo took 2.680832624435425s
Availability | SPARQL endpoint availability check for BioTop took 4.2438507080078125e-05s
Availability | VoID file availability check for BioTop took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for BioTop took 0.29156017303466797s
Reputation | Calculation of the PageRank for BioTop took 0.020776987075805664s
Interlinking | Calculation of Degree of Connection for BioTop took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BioTop took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006711483001708984s
Believability | Calculation of trust value for BioTop took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-bt took 2.7220137119293213s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.1961669921875e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.2688326835632324s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020107507705688477s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008740425109863281s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 3.814697265625e-06s
INFO | --- Analysis for bioportal-bto took 2.6538400650024414s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3359565734863281s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.020014524459838867s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018682479858398438s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-canco took 3.0991880893707275s
Availability | SPARQL endpoint availability check for CAO took 0.00011324882507324219s
Availability | VoID file availability check for CAO took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for CAO took 0.2740774154663086s
Reputation | Calculation of the PageRank for CAO took 0.020578861236572266s
Interlinking | Calculation of Degree of Connection for CAO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CAO took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0006175041198730469s
Believability | Calculation of trust value for CAO took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-cao took 2.599379539489746s
Availability | SPARQL endpoint availability check for CareLex took 4.076957702636719e-05s
Availability | VoID file availability check for CareLex took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for CareLex took 0.2806408405303955s
Reputation | Calculation of the PageRank for CareLex took 0.02027273178100586s
Interlinking | Calculation of Degree of Connection for CareLex took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CareLex took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.459785461425781e-05s
Believability | Calculation of trust value for CareLex took 3.814697265625e-06s
INFO | --- Analysis for bioportal-carelex took 2.651475667953491s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.28348565101623535s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.020199298858642578s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0008072853088378906s
Believability | Calculation of trust value for Cell Cycle Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-cco took 2.7299323081970215s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.2697734832763672s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020153284072875977s
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.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.00025725364685058594s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cdao took 2.6691031455993652s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 4.100799560546875e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.26122331619262695s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.019914865493774414s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0007753372192382812s
Believability | Calculation of trust value for Chemical entities of biological interest took 7.62939453125e-06s
INFO | --- Analysis for bioportal-chebi took 2.687249183654785s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 4.0531158447265625e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.26323556900024414s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.019960403442382812s
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.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002484321594238281s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 2.6111180782318115s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.24102401733398438s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.020054340362548828s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0008337497711181641s
Believability | Calculation of trust value for Chemical Information Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-cheminf took 2.56705641746521s
Availability | SPARQL endpoint availability check for Cell type took 4.124641418457031e-05s
Availability | VoID file availability check for Cell type took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Cell type took 0.27521204948425293s
Reputation | Calculation of the PageRank for Cell type took 0.020203828811645508s
Interlinking | Calculation of Degree of Connection for Cell type took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cell type took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003886222839355469s
Believability | Calculation of trust value for Cell type took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-cl took 2.677103042602539s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 5.1021575927734375e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.2576265335083008s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.020251035690307617s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008101463317871094s
Believability | Calculation of trust value for Cell Line Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-clo took 2.587149143218994s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 4.863739013671875e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0004253387451171875s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.25140810012817383s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.020064115524291992s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.0001678466796875s
Believability | Calculation of trust value for Clinical Measurement Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-cmo took 2.6084282398223877s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.26316380500793457s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.020089387893676758s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.0002040863037109375s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-cno took 2.6790757179260254s
Availability | SPARQL endpoint availability check for Wheat trait took 4.076957702636719e-05s
Availability | VoID file availability check for Wheat trait took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.27708935737609863s
Reputation | Calculation of the PageRank for Wheat trait took 0.020091533660888672s
Interlinking | Calculation of Degree of Connection for Wheat trait took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.0067901611328125e-05s
Believability | Calculation of trust value for Wheat trait took 3.5762786865234375e-06s
INFO | --- Analysis for bioportal-co_wheat took 2.7086448669433594s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.267692565917969e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.00042247772216796875s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.264035701751709s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.0201113224029541s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003657341003417969s
Believability | Calculation of trust value for Cognitive Atlas took 3.5762786865234375e-06s
INFO | --- Analysis for bioportal-cogat took 2.5492136478424072s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.26964449882507324s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020076990127563477s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007441043853759766s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-cogpo took 2.610250949859619s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 4.100799560546875e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0004165172576904297s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.28272128105163574s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.020827293395996094s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.00041294097900390625s
Believability | Calculation of trust value for Current Procedural Terminology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-cpt took 2.5644052028656006s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 5.459785461425781e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.3311920166015625s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020121335983276367s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017611980438232422s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-csp took 3.0855889320373535s
Availability | SPARQL endpoint availability check for COSTART took 4.220008850097656e-05s
Availability | VoID file availability check for COSTART took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for COSTART took 0.27370643615722656s
Reputation | Calculation of the PageRank for COSTART took 0.02024364471435547s
Interlinking | Calculation of Degree of Connection for COSTART took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for COSTART took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009911060333251953s
Believability | Calculation of trust value for COSTART took 3.5762786865234375e-06s
INFO | --- Analysis for bioportal-cst took 2.550205945968628s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.1484832763671875e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.24903202056884766s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.019922971725463867s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.00048828125s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 3.814697265625e-06s
INFO | --- Analysis for bioportal-ctcae took 2.606658458709717s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 4.1961669921875e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.26886653900146484s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.020183086395263672s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004475116729736328s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ctx took 2.6301357746124268s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.172325134277344e-05s
Availability | VoID file availability check for Dendritic cell took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.2642238140106201s
Reputation | Calculation of the PageRank for Dendritic cell took 0.0201261043548584s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.0002942085266113281s
Believability | Calculation of trust value for Dendritic cell took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-dc_cl took 2.594839096069336s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 5.507469177246094e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.2451033592224121s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.020885944366455078s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.893013000488281e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ddanat took 2.608722448348999s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.363059997558594e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.2435779571533203s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.020752668380737305s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009660720825195312s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ddi took 2.5528404712677s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.2451612949371338s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.02025461196899414s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.416175842285156e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-diagnosticont took 2.5641236305236816s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.2864563465118408s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.020283222198486328s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00016260147094726562s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 2.6899211406707764s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Human disease ontology took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2657124996185303s
Reputation | Calculation of the PageRank for Human disease ontology took 0.02026653289794922s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.000621795654296875s
Believability | Calculation of trust value for Human disease ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-doid took 2.706362009048462s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.673004150390625e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.2509922981262207s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.02014327049255371s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0007984638214111328s
Believability | Calculation of trust value for Electrocardiography Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ecg took 2.6496667861938477s
Availability | SPARQL endpoint availability check for Evidence codes took 4.124641418457031e-05s
Availability | VoID file availability check for Evidence codes took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.27887892723083496s
Reputation | Calculation of the PageRank for Evidence codes took 0.01985335350036621s
Interlinking | Calculation of Degree of Connection for Evidence codes took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.123283386230469e-05s
Believability | Calculation of trust value for Evidence codes took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-eco took 2.6286017894744873s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.3290228843688965s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.02057647705078125s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017092227935791016s
Believability | Calculation of trust value for Experimental Factor Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-efo took 3.0428414344787598s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.172325134277344e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.29047608375549316s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.020033597946166992s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011599063873291016s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 3.814697265625e-06s
INFO | --- Analysis for bioportal-ehda took 2.6779539585113525s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.100799560546875e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.28881335258483887s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.020045995712280273s
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.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007283687591552734s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ehdaa took 2.6022515296936035s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.00543212890625e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.26511240005493164s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.02006673812866211s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005261898040771484s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 7.62939453125e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 2.6744375228881836s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 5.4836273193359375e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.27011919021606445s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.0202634334564209s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 2.956390380859375e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-emap took 2.6140360832214355s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Environment Ontology took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.2880737781524658s
Reputation | Calculation of the PageRank for Environment Ontology took 0.021535396575927734s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0003986358642578125s
Believability | Calculation of trust value for Environment Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-envo took 2.6356587409973145s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 4.1961669921875e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.2669517993927002s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.020020484924316406s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.00030875205993652344s
Believability | Calculation of trust value for Plant environmental conditions took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-eo took 2.5520055294036865s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 5.030632019042969e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.30243468284606934s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.020259857177734375s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012073516845703125s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 3.5762786865234375e-06s
INFO | --- Analysis for bioportal-ep took 2.6437439918518066s
Availability | SPARQL endpoint availability check for Epilepsy took 4.267692565917969e-05s
Availability | VoID file availability check for Epilepsy took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.2719242572784424s
Reputation | Calculation of the PageRank for Epilepsy took 0.02013707160949707s
Interlinking | Calculation of Degree of Connection for Epilepsy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.00013113021850585938s
Believability | Calculation of trust value for Epilepsy took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-epileponto took 2.612619161605835s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 6.723403930664062e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0004248619079589844s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.26728129386901855s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020064592361450195s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011577606201171875s
Believability | Calculation of trust value for eagle-i research resource ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ero took 2.5387680530548096s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.00010585784912109375s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.26191186904907227s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020303726196289062s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011227130889892578s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ev took 2.7811105251312256s
Availability | SPARQL endpoint availability check for ExO took 4.0531158447265625e-05s
Availability | VoID file availability check for ExO took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for ExO took 0.26465630531311035s
Reputation | Calculation of the PageRank for ExO took 0.019989967346191406s
Interlinking | Calculation of Degree of Connection for ExO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ExO took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00026035308837890625s
Believability | Calculation of trust value for ExO took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-exo took 2.6372570991516113s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 4.00543212890625e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0004343986511230469s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.2671387195587158s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.02006363868713379s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0008172988891601562s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00011134147644042969s
Believability | Calculation of trust value for Fungal gross anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fao took 2.607919216156006s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.172325134277344e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.2558422088623047s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.02001643180847168s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00018215179443359375s
Believability | Calculation of trust value for Biological imaging methods took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-fbbi took 2.5957863330841064s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 4.124641418457031e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.2848374843597412s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.020084381103515625s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006678104400634766s
Believability | Calculation of trust value for Drosophila gross anatomy took 3.814697265625e-06s
INFO | --- Analysis for bioportal-fbbt took 2.6024749279022217s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 4.029273986816406e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0010225772857666016s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.2593204975128174s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.02009439468383789s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0008308887481689453s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.00043892860412597656s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fbcv took 2.720134735107422s
Availability | SPARQL endpoint availability check for Drosophila development took 4.076957702636719e-05s
Availability | VoID file availability check for Drosophila development took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.2563314437866211s
Reputation | Calculation of the PageRank for Drosophila development took 0.02011728286743164s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.363059997558594e-05s
Believability | Calculation of trust value for Drosophila development took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fbdv took 2.6422085762023926s
Availability | SPARQL endpoint availability check for Fly taxonomy took 4.744529724121094e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0004296302795410156s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.2816610336303711s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.020084857940673828s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003616809844970703s
Believability | Calculation of trust value for Fly taxonomy took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-fbsp took 2.6483817100524902s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.2438507080078125e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.2610166072845459s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.02011585235595703s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00022363662719726562s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 2.5826683044433594s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.2493305206298828s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.019903898239135742s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0003905296325683594s
Believability | Calculation of trust value for Family Health History Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-fhho took 2.651188611984253s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Influenza Ontology took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.2572214603424072s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.019964933395385742s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0010504722595214844s
Believability | Calculation of trust value for Influenza Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-flu took 2.4706313610076904s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 4.076957702636719e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.25652360916137695s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.02019047737121582s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.175041198730469e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fma took 2.589973211288452s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.2503631114959717s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.02007579803466797s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00012803077697753906s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-fypo took 2.6481947898864746s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.23867011070251465s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.02014756202697754s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 8.869171142578125e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-geospecies took 2.57560658454895s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.25899171829223633s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.02001333236694336s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00016260147094726562s
Believability | Calculation of trust value for General Formal Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-gfo took 2.63086199760437s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 5.316734313964844e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.2523171901702881s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.020230531692504883s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0006072521209716797s
Believability | Calculation of trust value for General Formal Ontology: Biology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-gfo-bio took 2.597435712814331s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.1961669921875e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.2640199661254883s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.020119190216064453s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008709430694580078s
Believability | Calculation of trust value for Gene Ontology Extension took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-go_x1 took 2.5664517879486084s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Gene Ontology took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.2422184944152832s
Reputation | Calculation of the PageRank for Gene Ontology took 0.020018577575683594s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008709430694580078s
Believability | Calculation of trust value for Gene Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-go_x2 took 2.584226369857788s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.172325134277344e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.28273630142211914s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.02034735679626465s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.0279159545898438e-05s
Believability | Calculation of trust value for Cereal Plant Development took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-gro took 2.6301798820495605s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.076957702636719e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.2760803699493408s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.0200955867767334s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.00042438507080078125s
Believability | Calculation of trust value for Cereal plant gross anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-gro_x1 took 2.614832878112793s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.283001184463501s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020188093185424805s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007517337799072266s
Believability | Calculation of trust value for Gene Regulation Ontology took 3.5762786865234375e-06s
INFO | --- Analysis for bioportal-gro_x2 took 2.7451236248016357s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.2683677673339844s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.019974708557128906s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005755424499511719s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-hao took 2.684185266494751s
Availability | SPARQL endpoint availability check for HCPCS took 4.124641418457031e-05s
Availability | VoID file availability check for HCPCS took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for HCPCS took 0.263042688369751s
Reputation | Calculation of the PageRank for HCPCS took 0.020165443420410156s
Interlinking | Calculation of Degree of Connection for HCPCS took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for HCPCS took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00023627281188964844s
Believability | Calculation of trust value for HCPCS took 3.814697265625e-06s
INFO | --- Analysis for bioportal-hcpcs took 2.5037784576416016s
Availability | SPARQL endpoint availability check for Health Level Seven took 4.100799560546875e-05s
Availability | VoID file availability check for Health Level Seven took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.24182963371276855s
Reputation | Calculation of the PageRank for Health Level Seven took 0.020212173461914062s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012636184692382812s
Believability | Calculation of trust value for Health Level Seven took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-hl7 took 2.5971357822418213s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 4.1961669921875e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.24910593032836914s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.021027326583862305s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0003380775451660156s
Believability | Calculation of trust value for HEALTH_INDICATORS took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-hlth_indics took 2.6007046699523926s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.2759983539581299s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.020378589630126953s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 2.9802322387695312e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-hom took 2.6161792278289795s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 7.534027099609375e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.26512837409973145s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.01999497413635254s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 2.9087066650390625e-05s
Believability | Calculation of trust value for HOM-HARVARD took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-hom_harvard took 2.66369366645813s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 4.9114227294921875e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.00043773651123046875s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.257138729095459s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.021787643432617188s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.000659942626953125s
Believability | Calculation of trust value for Human Phenotype Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-hp_x1 took 2.6177775859832764s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.26250243186950684s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.02026534080505371s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010344982147216797s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-hpio took 2.6005263328552246s
Availability | SPARQL endpoint availability check for HUGO took 4.2438507080078125e-05s
Availability | VoID file availability check for HUGO took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for HUGO took 0.2757260799407959s
Reputation | Calculation of the PageRank for HUGO took 0.020292997360229492s
Interlinking | Calculation of Degree of Connection for HUGO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for HUGO took 7.867813110351562e-05s
Believability | Calculation of trust value for HUGO took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-hugo took 2.667433500289917s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.2651486396789551s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.020484447479248047s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006597042083740234s
Believability | Calculation of trust value for Information Artifact Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-iao took 2.591452121734619s
Availability | SPARQL endpoint availability check for ICD10 took 7.104873657226562e-05s
Availability | VoID file availability check for ICD10 took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for ICD10 took 0.26496028900146484s
Reputation | Calculation of the PageRank for ICD10 took 0.02026534080505371s
Interlinking | Calculation of Degree of Connection for ICD10 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ICD10 took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0008251667022705078s
Believability | Calculation of trust value for ICD10 took 3.814697265625e-06s
INFO | --- Analysis for bioportal-icd10 took 2.647693634033203s
Availability | SPARQL endpoint availability check for ICD10CM took 4.1961669921875e-05s
Availability | VoID file availability check for ICD10CM took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.25232815742492676s
Reputation | Calculation of the PageRank for ICD10CM took 0.020317792892456055s
Interlinking | Calculation of Degree of Connection for ICD10CM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006036758422851562s
Believability | Calculation of trust value for ICD10CM took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-icd10cm took 2.5626370906829834s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.100799560546875e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.2656123638153076s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.020357847213745117s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00014829635620117188s
Believability | Calculation of trust value for ICD-10-PCS took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-icd10pcs took 2.5548479557037354s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 4.1484832763671875e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.26448750495910645s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020088911056518555s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006301403045654297s
Believability | Calculation of trust value for International Classification of Diseases took 7.62939453125e-06s
INFO | --- Analysis for bioportal-icd9cm took 2.5820231437683105s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 4.1961669921875e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0004329681396484375s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.24138236045837402s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.020040512084960938s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004391670227050781s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 3.814697265625e-06s
INFO | --- Analysis for bioportal-icf_x1 took 2.5936291217803955s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 4.1484832763671875e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.2787332534790039s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.02017354965209961s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012652873992919922s
Believability | Calculation of trust value for International Classification for Nursing Practice took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-icnp took 2.704375743865967s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 4.315376281738281e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.25154995918273926s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.020832538604736328s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0004818439483642578s
Believability | Calculation of trust value for International Classification of Primary Care took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-icpc took 2.5778141021728516s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 4.029273986816406e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.2563023567199707s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020036935806274414s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.000843048095703125s
Believability | Calculation of trust value for ICPC-2 PLUS took 3.814697265625e-06s
INFO | --- Analysis for bioportal-icpc2p took 2.6424758434295654s
Availability | SPARQL endpoint availability check for ICPS Network took 4.00543212890625e-05s
Availability | VoID file availability check for ICPS Network took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.2671630382537842s
Reputation | Calculation of the PageRank for ICPS Network took 0.02005910873413086s
Interlinking | Calculation of Degree of Connection for ICPS Network took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00021409988403320312s
Believability | Calculation of trust value for ICPS Network took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-icps took 2.6063625812530518s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.2635767459869385s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.020050525665283203s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008649826049804688s
Believability | Calculation of trust value for Infectious Disease Ontology took 3.5762786865234375e-06s
INFO | --- Analysis for bioportal-ido took 2.6049606800079346s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0004200935363769531s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.2531607151031494s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.02024245262145996s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011768341064453125s
Believability | Calculation of trust value for Brucellosis Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-idobru took 2.6919867992401123s
Availability | SPARQL endpoint availability check for Malaria Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.2747921943664551s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.0203855037689209s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0013234615325927734s
Believability | Calculation of trust value for Malaria Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-idomal took 2.7106075286865234s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 4.1484832763671875e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.26517295837402344s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020081520080566406s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0003008842468261719s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-iev took 2.5547502040863037s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.4345855712890625e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.2643725872039795s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.020127058029174805s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.0001518726348876953s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 3.814697265625e-06s
INFO | --- Analysis for bioportal-imgt took 2.6014673709869385s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.076957702636719e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.2710747718811035s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020214080810546875s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005078315734863281s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 3.814697265625e-06s
INFO | --- Analysis for bioportal-imr took 2.736056327819824s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.29311060905456543s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.020119190216064453s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0008034706115722656s
Believability | Calculation of trust value for Interaction Network Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-ino took 2.5992162227630615s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.076957702636719e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.2777516841888428s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.02009272575378418s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.075599670410156e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-invertebrata took 2.5902793407440186s
Availability | SPARQL endpoint availability check for IxnO took 4.124641418457031e-05s
Availability | VoID file availability check for IxnO took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for IxnO took 0.2908294200897217s
Reputation | Calculation of the PageRank for IxnO took 0.020206451416015625s
Interlinking | Calculation of Degree of Connection for IxnO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for IxnO took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00018358230590820312s
Believability | Calculation of trust value for IxnO took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ixno took 2.671400547027588s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.124641418457031e-05s
Availability | VoID file availability check for SysMO-JERM took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.26428747177124023s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.020127058029174805s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0003719329833984375s
Believability | Calculation of trust value for SysMO-JERM took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-jerm took 2.645742416381836s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.2512953281402588s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.020473957061767578s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.24249267578125e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-kisao took 2.6277554035186768s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.220008850097656e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.00048828125s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.2576117515563965s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.0202481746673584s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.0001983642578125s
Believability | Calculation of trust value for Loggerhead nesting took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-lhn took 2.553104877471924s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.2609860897064209s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.021280527114868164s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.0001971721649169922s
Believability | Calculation of trust value for Lipid Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-lipro took 2.5888335704803467s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.553794860839844e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.00040268898010253906s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.3269920349121094s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.02003645896911621s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018219947814941406s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-lnc took 3.05229115486145s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.172325134277344e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.2745788097381592s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020416259765625s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006422996520996094s
Believability | Calculation of trust value for Mouse adult gross anatomy took 3.814697265625e-06s
INFO | --- Analysis for bioportal-ma took 2.5770018100738525s
Availability | SPARQL endpoint availability check for Multiple alignment took 4.1484832763671875e-05s
Availability | VoID file availability check for Multiple alignment took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.2629406452178955s
Reputation | Calculation of the PageRank for Multiple alignment took 0.020374536514282227s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.0002079010009765625s
Believability | Calculation of trust value for Multiple alignment took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-mao took 2.6356582641601562s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.1961669921875e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.2685508728027344s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.01992321014404297s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006864070892333984s
Believability | Calculation of trust value for Minimal anatomical terminology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-mat took 2.6202268600463867s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 4.267692565917969e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.24407386779785156s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020011186599731445s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.00040793418884277344s
Believability | Calculation of trust value for Breast tissue cell lines took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mcbcc took 2.5852696895599365s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Cell line ontology took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.23892998695373535s
Reputation | Calculation of the PageRank for Cell line ontology took 0.019870519638061523s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007376670837402344s
Believability | Calculation of trust value for Cell line ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-mccl took 2.5880212783813477s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Cell line ontology took 0.00042629241943359375s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.26089930534362793s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020401477813720703s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0014028549194335938s
Believability | Calculation of trust value for Cell line ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 2.6257710456848145s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 5.340576171875e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.2779350280761719s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.02012920379638672s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.00022673606872558594s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-mcv took 2.6339797973632812s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.124641418457031e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.26589202880859375s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.020039081573486328s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.0001647472381591797s
Believability | Calculation of trust value for Master Drug Data Base took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-mddb took 2.6251120567321777s
Availability | SPARQL endpoint availability check for MedDRA took 9.703636169433594e-05s
Availability | VoID file availability check for MedDRA took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for MedDRA took 0.2786900997161865s
Reputation | Calculation of the PageRank for MedDRA took 0.020517826080322266s
Interlinking | Calculation of Degree of Connection for MedDRA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MedDRA took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011262893676757812s
Believability | Calculation of trust value for MedDRA took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mdr took 2.633373260498047s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 5.7697296142578125e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.2564966678619385s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.020446062088012695s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008931159973144531s
Believability | Calculation of trust value for MedlinePlus Health Topics took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-medlineplus took 2.5461761951446533s
Availability | SPARQL endpoint availability check for MeGO took 4.291534423828125e-05s
Availability | VoID file availability check for MeGO took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for MeGO took 0.27140307426452637s
Reputation | Calculation of the PageRank for MeGO took 0.02020120620727539s
Interlinking | Calculation of Degree of Connection for MeGO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MeGO took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00014257431030273438s
Believability | Calculation of trust value for MeGO took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mego took 2.590628147125244s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.100799560546875e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.3138577938079834s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.020092248916625977s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.001802206039428711s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-mesh-owl took 3.0862035751342773s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.25626564025878906s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.0200040340423584s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006175041198730469s
Believability | Calculation of trust value for Mental Functioning Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-mf took 2.588412046432495s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.1484832763671875e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.2640979290008545s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020018815994262695s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005557537078857422s
Believability | Calculation of trust value for Medaka fish anatomy and development took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-mfo took 2.6165854930877686s
Availability | SPARQL endpoint availability check for Emotion Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Emotion Ontology took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.26546525955200195s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.019904613494873047s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007736682891845703s
Believability | Calculation of trust value for Emotion Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-mfoem took 2.607071876525879s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 7.367134094238281e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.2691459655761719s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.020449161529541016s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00010418891906738281s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-mhc took 2.6234376430511475s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.506111145019531e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.2432699203491211s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.020325660705566406s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006647109985351562s
Believability | Calculation of trust value for Protein-protein interaction took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mi took 2.5714683532714844s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.00543212890625e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.279191255569458s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.0200192928314209s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007202625274658203s
Believability | Calculation of trust value for Mosquito insecticide resistance took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-miro took 2.5972530841827393s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 5.054473876953125e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.2662007808685303s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.0199739933013916s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.0001323223114013672s
Believability | Calculation of trust value for Measurement Method Ontology took 3.5762786865234375e-06s
INFO | --- Analysis for bioportal-mmo took 2.641793727874756s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for MGED Ontology took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.2523176670074463s
Reputation | Calculation of the PageRank for MGED Ontology took 0.020295143127441406s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.00038504600524902344s
Believability | Calculation of trust value for MGED Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mo took 2.6524159908294678s
Availability | SPARQL endpoint availability check for Protein modification took 4.291534423828125e-05s
Availability | VoID file availability check for Protein modification took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for Protein modification took 0.28045201301574707s
Reputation | Calculation of the PageRank for Protein modification took 0.02010822296142578s
Interlinking | Calculation of Degree of Connection for Protein modification took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Protein modification took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00021195411682128906s
Believability | Calculation of trust value for Protein modification took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-mod took 2.6091887950897217s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.076957702636719e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.28095221519470215s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.019949913024902344s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006434917449951172s
Believability | Calculation of trust value for Mammalian phenotype took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-mp took 2.6401116847991943s
Availability | SPARQL endpoint availability check for Mouse pathology took 8.654594421386719e-05s
Availability | VoID file availability check for Mouse pathology took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.2427968978881836s
Reputation | Calculation of the PageRank for Mouse pathology took 0.020428180694580078s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0004649162292480469s
Believability | Calculation of trust value for Mouse pathology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-mpath took 2.752204656600952s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.1961669921875e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0005698204040527344s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.25687122344970703s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.02031993865966797s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.00035309791564941406s
Believability | Calculation of trust value for Mass spectrometry took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ms took 2.677899122238159s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 8.511543273925781e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.298328161239624s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020332813262939453s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.001859426498413086s
Believability | Calculation of trust value for Medical Subject Headings took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-msh took 3.061663866043091s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.172325134277344e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.27604031562805176s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.020114660263061523s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00016641616821289062s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-mthch took 2.6040914058685303s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.25621461868286133s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.019979476928710938s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0007710456848144531s
Believability | Calculation of trust value for Natural Products Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-natpro took 2.649033308029175s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 4.172325134277344e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.26807260513305664s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.02144145965576172s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008373260498046875s
Believability | Calculation of trust value for NCBI organismal classification took 7.62939453125e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 2.6497316360473633s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.1484832763671875e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.31099915504455566s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02021503448486328s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0019741058349609375s
Believability | Calculation of trust value for NCI Thesaurus took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ncit took 3.1067442893981934s
Availability | SPARQL endpoint availability check for National Drug Data File took 5.14984130859375e-05s
Availability | VoID file availability check for National Drug Data File took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.2793006896972656s
Reputation | Calculation of the PageRank for National Drug Data File took 0.02037811279296875s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006330013275146484s
Believability | Calculation of trust value for National Drug Data File took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-nddf took 2.6373372077941895s
Availability | SPARQL endpoint availability check for National Drug File took 8.249282836914062e-05s
Availability | VoID file availability check for National Drug File took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for National Drug File took 0.2706477642059326s
Reputation | Calculation of the PageRank for National Drug File took 0.020555973052978516s
Interlinking | Calculation of Degree of Connection for National Drug File took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for National Drug File took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012595653533935547s
Believability | Calculation of trust value for National Drug File took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ndfrt took 2.6622772216796875s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.1961669921875e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.27388525009155273s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.02035975456237793s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011644363403320312s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 3.814697265625e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 2.647827386856079s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.25316619873046875s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020730257034301758s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006649494171142578s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 3.5762786865234375e-06s
INFO | --- Analysis for bioportal-neomark took 2.604248523712158s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.278491735458374s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.020261049270629883s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00011754035949707031s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-neomarkontology took 2.5724270343780518s
Availability | SPARQL endpoint availability check for NIFSTD took 4.2438507080078125e-05s
Availability | VoID file availability check for NIFSTD took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.30277180671691895s
Reputation | Calculation of the PageRank for NIFSTD took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for NIFSTD took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0018732547760009766s
Believability | Calculation of trust value for NIFSTD took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-nif took 3.0737664699554443s
Availability | SPARQL endpoint availability check for NIF Cell took 5.2928924560546875e-05s
Availability | VoID file availability check for NIF Cell took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.26781630516052246s
Reputation | Calculation of the PageRank for NIF Cell took 0.019980907440185547s
Interlinking | Calculation of Degree of Connection for NIF Cell took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013666152954101562s
Believability | Calculation of trust value for NIF Cell took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-nif_cell took 2.5058605670928955s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.601478576660156e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.25734591484069824s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020167112350463867s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0014071464538574219s
Believability | Calculation of trust value for NIF Dysfunction took 3.5762786865234375e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 2.569155216217041s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.25256872177124023s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.02060413360595703s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005421638488769531s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nigo took 2.58258318901062s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 4.3392181396484375e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.26805758476257324s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.021120786666870117s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005393028259277344s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-nmr took 2.581879138946533s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 3.9577484130859375e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.2626206874847412s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.02006697654724121s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00010418891906738281s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-nonrctontology took 2.6548264026641846s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.25458383560180664s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020052433013916016s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0011980533599853516s
Believability | Calculation of trust value for NanoParticle Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-npo took 2.593417167663574s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.100799560546875e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.2670633792877197s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.020370960235595703s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007491111755371094s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-oae took 2.566424608230591s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 4.267692565917969e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.24805879592895508s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.020774364471435547s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0014598369598388672s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-obi took 2.584354877471924s
Availability | SPARQL endpoint availability check for OBOE took 4.267692565917969e-05s
Availability | VoID file availability check for OBOE took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for OBOE took 0.2569746971130371s
Reputation | Calculation of the PageRank for OBOE took 0.01990365982055664s
Interlinking | Calculation of Degree of Connection for OBOE took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OBOE took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00010657310485839844s
Believability | Calculation of trust value for OBOE took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-oboe took 2.580906867980957s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.9114227294921875e-05s
Availability | VoID file availability check for OBOE SBC took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.2678873538970947s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020328760147094727s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007808208465576172s
Believability | Calculation of trust value for OBOE SBC took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 2.5866520404815674s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 5.173683166503906e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.00041484832763671875s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.2641782760620117s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020086288452148438s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005810260772705078s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ocre took 2.6598479747772217s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 4.458427429199219e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.2907717227935791s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.0200042724609375s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008475780487060547s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-odgi took 2.649143934249878s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 4.1961669921875e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.2673335075378418s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.0199737548828125s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008661746978759766s
Believability | Calculation of trust value for Ontology for Genetic Interval took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ogi took 2.643939733505249s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 6.937980651855469e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.2807610034942627s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.02039480209350586s
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.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.0002865791320800781s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ogmd took 2.715928316116333s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.7206878662109375e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.29395437240600586s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.02010369300842285s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006670951843261719s
Believability | Calculation of trust value for Ontology for General Medical Science took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ogms took 2.707963466644287s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.1484832763671875e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.2520771026611328s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020004987716674805s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011153221130371094s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-omim took 2.60396409034729s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.267692565917969e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.28029513359069824s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020320415496826172s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003635883331298828s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-omit took 2.55667781829834s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.0531158447265625e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.00021791458129882812s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.2900867462158203s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.020238876342773438s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0005941390991210938s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-omrse took 2.404609203338623s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.220008850097656e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.246415376663208s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.020844697952270508s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007796287536621094s
Believability | Calculation of trust value for Ontology of Data Mining took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ontodm took 2.6265180110931396s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.220008850097656e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.2643008232116699s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.02170109748840332s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.0002505779266357422s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ontodt took 2.6958765983581543s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 6.747245788574219e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.250093936920166s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020058870315551758s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0005917549133300781s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ontoorpha took 2.5518059730529785s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 7.176399230957031e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.2701869010925293s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.020041465759277344s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009284019470214844s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 3.814697265625e-06s
INFO | --- Analysis for bioportal-opl took 2.6229748725891113s
Availability | SPARQL endpoint availability check for Phenotypic quality took 5.14984130859375e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.2840576171875s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.02004861831665039s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.000873565673828125s
Believability | Calculation of trust value for Phenotypic quality took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-pato took 2.605462074279785s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.124641418457031e-05s
Availability | VoID file availability check for Physician Data Query took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.2927401065826416s
Reputation | Calculation of the PageRank for Physician Data Query took 0.020227670669555664s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008614063262939453s
Believability | Calculation of trust value for Physician Data Query took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-pdq took 2.58555269241333s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.2438507080078125e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.2665722370147705s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.020075321197509766s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0007817745208740234s
Believability | Calculation of trust value for Pediatric Terminology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pedterm took 2.6432933807373047s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.24233198165893555s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.02008986473083496s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00019168853759765625s
Believability | Calculation of trust value for Parasite Experiment Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-peo took 2.5605716705322266s
Availability | SPARQL endpoint availability check for PHARE took 4.982948303222656e-05s
Availability | VoID file availability check for PHARE took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for PHARE took 0.25777292251586914s
Reputation | Calculation of the PageRank for PHARE took 0.019943952560424805s
Interlinking | Calculation of Degree of Connection for PHARE took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for PHARE took 0.0008108615875244141s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006377696990966797s
Believability | Calculation of trust value for PHARE took 7.62939453125e-06s
INFO | --- Analysis for bioportal-phare took 2.646733045578003s
Availability | SPARQL endpoint availability check for PKO_Re took 4.1484832763671875e-05s
Availability | VoID file availability check for PKO_Re took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.2569875717163086s
Reputation | Calculation of the PageRank for PKO_Re took 0.022638559341430664s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0013303756713867188s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.0002865791320800781s
Believability | Calculation of trust value for PKO_Re took 3.814697265625e-06s
INFO | --- Analysis for bioportal-pko took 2.5878090858459473s
Availability | SPARQL endpoint availability check for PMA 2010 took 7.724761962890625e-05s
Availability | VoID file availability check for PMA 2010 took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.2480483055114746s
Reputation | Calculation of the PageRank for PMA 2010 took 0.027788877487182617s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0009038448333740234s
Believability | Calculation of trust value for PMA 2010 took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-pma took 2.627267360687256s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 4.2438507080078125e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.29050207138061523s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.0202634334564209s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.0001633167266845703s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pmr took 2.60322642326355s
Availability | SPARQL endpoint availability check for Plant Anatomy took 5.054473876953125e-05s
Availability | VoID file availability check for Plant Anatomy took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.28997135162353516s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.02059030532836914s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.00038743019104003906s
Believability | Calculation of trust value for Plant Anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-po took 2.6815261840820312s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 8.726119995117188e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.2670552730560303s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.020331621170043945s
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.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 7.05718994140625e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-po_x1 took 2.625288724899292s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Plant Ontology took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.2716209888458252s
Reputation | Calculation of the PageRank for Plant Ontology took 0.020593881607055664s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.000431060791015625s
Believability | Calculation of trust value for Plant Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-po_x2 took 2.6421172618865967s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 5.125999450683594e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.2850937843322754s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.02001786231994629s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006875991821289062s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-pr took 2.6134636402130127s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.363059997558594e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.2765815258026123s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.02016305923461914s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.0002551078796386719s
Believability | Calculation of trust value for Proteomics data and process provenance took 3.814697265625e-06s
INFO | --- Analysis for bioportal-propreo took 2.7075531482696533s
Availability | SPARQL endpoint availability check for Pathway ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Pathway ontology took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.2599647045135498s
Reputation | Calculation of the PageRank for Pathway ontology took 0.02013373374938965s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00012302398681640625s
Believability | Calculation of trust value for Pathway ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pw took 2.666745662689209s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.2538869380950928s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.020086050033569336s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-qibo took 2.5124523639678955s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.887580871582031e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.34197402000427246s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0210115909576416s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.001745462417602539s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-rcd took 3.049696683883667s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.27028512954711914s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.020138978958129883s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00012874603271484375s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-rctontology took 2.6616382598876953s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.25165891647338867s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.020800113677978516s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 0.00010013580322265625s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-repo took 2.6603710651397705s
Availability | SPARQL endpoint availability check for Physico-chemical process took 7.843971252441406e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.2644033432006836s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020334720611572266s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00019311904907226562s
Believability | Calculation of trust value for Physico-chemical process took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-rex took 2.5993411540985107s
Availability | SPARQL endpoint availability check for RadLex took 4.2438507080078125e-05s
Availability | VoID file availability check for RadLex took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for RadLex took 0.2825489044189453s
Reputation | Calculation of the PageRank for RadLex took 0.020722389221191406s
Interlinking | Calculation of Degree of Connection for RadLex took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RadLex took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.001537322998046875s
Believability | Calculation of trust value for RadLex took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-rid took 2.6242527961730957s
Availability | SPARQL endpoint availability check for RNA ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for RNA ontology took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.2624533176422119s
Reputation | Calculation of the PageRank for RNA ontology took 0.02010798454284668s
Interlinking | Calculation of Degree of Connection for RNA ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005536079406738281s
Believability | Calculation of trust value for RNA ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-rnao took 2.6046810150146484s
Availability | SPARQL endpoint availability check for Role Ontology took 6.604194641113281e-05s
Availability | VoID file availability check for Role Ontology took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.2512643337249756s
Reputation | Calculation of the PageRank for Role Ontology took 0.020170211791992188s
Interlinking | Calculation of Degree of Connection for Role Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00018405914306640625s
Believability | Calculation of trust value for Role Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-roleo took 2.5419509410858154s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.27300453186035156s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.020180463790893555s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.0001728534698486328s
Believability | Calculation of trust value for Rat Strain Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-rs took 2.6909406185150146s
Availability | SPARQL endpoint availability check for RxNORM took 4.029273986816406e-05s
Availability | VoID file availability check for RxNORM took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for RxNORM took 0.2532823085784912s
Reputation | Calculation of the PageRank for RxNORM took 0.020101308822631836s
Interlinking | Calculation of Degree of Connection for RxNORM took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RxNORM took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0005981922149658203s
Believability | Calculation of trust value for RxNORM took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-rxnorm took 2.621894598007202s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.1484832763671875e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.2568697929382324s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.02007126808166504s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010483264923095703s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-sao took 2.6342735290527344s
Availability | SPARQL endpoint availability check for Systems Biology took 4.315376281738281e-05s
Availability | VoID file availability check for Systems Biology took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.27936267852783203s
Reputation | Calculation of the PageRank for Systems Biology took 0.020886659622192383s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004401206970214844s
Believability | Calculation of trust value for Systems Biology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sbo took 2.690484046936035s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0004458427429199219s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.25568079948425293s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.02007293701171875s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00010251998901367188s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-sbro took 2.554436445236206s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.00083160400390625s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.25606369972229004s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.02022075653076172s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013282299041748047s
Believability | Calculation of trust value for Sleep Domain Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-sdo took 2.651700496673584s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.076957702636719e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.2571072578430176s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.02000594139099121s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.00033283233642578125s
Believability | Calculation of trust value for Sample processing and separation techniques took 3.814697265625e-06s
INFO | --- Analysis for bioportal-sep took 2.57603120803833s
Availability | SPARQL endpoint availability check for Student Health Record took 5.4836273193359375e-05s
Availability | VoID file availability check for Student Health Record took 0.0011343955993652344s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.2752039432525635s
Reputation | Calculation of the PageRank for Student Health Record took 0.020122051239013672s
Interlinking | Calculation of Degree of Connection for Student Health Record took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.00043511390686035156s
Believability | Calculation of trust value for Student Health Record took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-shr took 2.5917787551879883s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.2529268264770508s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.020055055618286133s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012116432189941406s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-sio took 3.623462677001953s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 4.124641418457031e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.27341604232788086s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.020022869110107422s
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.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00019216537475585938s
Believability | Calculation of trust value for Situation-Based Access Control took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-sitbac took 2.736301898956299s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.220008850097656e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.29813289642333984s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.020494699478149414s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019278526306152344s
Believability | Calculation of trust value for SNOMED Clinical Terms took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-snomedct took 3.0110385417938232s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.2602982521057129s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.020146608352661133s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006551742553710938s
Believability | Calculation of trust value for SNP-Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-snpo took 2.6131930351257324s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.172325134277344e-05s
Availability | VoID file availability check for Sequence types and features took 0.00041103363037109375s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.2820627689361572s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020236968994140625s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0006146430969238281s
Believability | Calculation of trust value for Sequence types and features took 3.814697265625e-06s
INFO | --- Analysis for bioportal-so_x1 took 2.5915520191192627s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 4.1961669921875e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.31528687477111816s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.020275592803955078s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015888214111328125s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 3.814697265625e-06s
INFO | --- Analysis for bioportal-sopharm took 3.125169038772583s
Availability | SPARQL endpoint availability check for SoyOntology took 4.2438507080078125e-05s
Availability | VoID file availability check for SoyOntology took 0.0004258155822753906s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.25334882736206055s
Reputation | Calculation of the PageRank for SoyOntology took 0.02013993263244629s
Interlinking | Calculation of Degree of Connection for SoyOntology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.0002231597900390625s
Believability | Calculation of trust value for SoyOntology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-soy took 2.6118903160095215s
Availability | SPARQL endpoint availability check for Spider Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Spider Ontology took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.2816483974456787s
Reputation | Calculation of the PageRank for Spider Ontology took 0.019928693771362305s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00030875205993652344s
Believability | Calculation of trust value for Spider Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-spd took 2.6335036754608154s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.2788240909576416s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.02001333236694336s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.0002760887145996094s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-spto took 2.6630289554595947s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.27681493759155273s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.020210742950439453s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004298686981201172s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-sso took 2.577895164489746s
Availability | SPARQL endpoint availability check for Software Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Software Ontology took 0.00042557716369628906s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.292008638381958s
Reputation | Calculation of the PageRank for Software Ontology took 0.02010488510131836s
Interlinking | Calculation of Degree of Connection for Software Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Software Ontology took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.0004067420959472656s
Believability | Calculation of trust value for Software Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-swo took 2.639371633529663s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.172325134277344e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.26871395111083984s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.020191192626953125s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00023627281188964844s
Believability | Calculation of trust value for Tick gross anatomy took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-tads took 2.5882928371429443s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.2694988250732422s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.020044326782226562s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008821487426757812s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-tao took 2.6983447074890137s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.100799560546875e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0004162788391113281s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.2655766010284424s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.01993417739868164s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 8.58306884765625e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-taxrank took 2.624066114425659s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 4.291534423828125e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0004353523254394531s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.24153995513916016s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.020693302154541016s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 6.961822509765625e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-teddy took 2.635685443878174s
Availability | SPARQL endpoint availability check for Time Event Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.25162696838378906s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.020206212997436523s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008342266082763672s
Believability | Calculation of trust value for Time Event Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-teo took 2.6667675971984863s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 4.1961669921875e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.28336119651794434s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.020197391510009766s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0003871917724609375s
Believability | Calculation of trust value for Mosquito gross anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-tgma took 2.6266891956329346s
Availability | SPARQL endpoint availability check for thesaurus took 5.507469177246094e-05s
Availability | VoID file availability check for thesaurus took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for thesaurus took 0.23722553253173828s
Reputation | Calculation of the PageRank for thesaurus took 0.021108627319335938s
Interlinking | Calculation of Degree of Connection for thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for thesaurus took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.866455078125e-05s
Believability | Calculation of trust value for thesaurus took 7.62939453125e-06s
INFO | --- Analysis for bioportal-thesaurus took 2.600069761276245s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.1484832763671875e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.259197473526001s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.019993066787719727s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.000335693359375s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 2.6643102169036865s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 6.747245788574219e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.2851853370666504s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008199214935302734s
Believability | Calculation of trust value for Translational Medicine Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-tmo took 2.6338257789611816s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 5.650520324707031e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.27145910263061523s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.020276546478271484s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.000152587890625s
Believability | Calculation of trust value for Plant Trait Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-to took 2.6273000240325928s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for TOK_Ontology took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.270798921585083s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.02016448974609375s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.0001761913299560547s
Believability | Calculation of trust value for TOK_Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-tok took 2.6095964908599854s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 5.3882598876953125e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.000457763671875s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.2649953365325928s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.019947290420532227s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00018787384033203125s
Believability | Calculation of trust value for Teleost taxonomy took 3.814697265625e-06s
INFO | --- Analysis for bioportal-tto took 2.5487611293792725s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.2501087188720703s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.019992828369140625s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010340213775634766s
Believability | Calculation of trust value for Uber anatomy ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-uberon took 2.576388120651245s
Availability | SPARQL endpoint availability check for Units Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Units Ontology took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.2773611545562744s
Reputation | Calculation of the PageRank for Units Ontology took 0.020084857940673828s
Interlinking | Calculation of Degree of Connection for Units Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.0002262592315673828s
Believability | Calculation of trust value for Units Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-unitsontology took 2.607285737991333s
Availability | SPARQL endpoint availability check for Units of measurement took 4.2438507080078125e-05s
Availability | VoID file availability check for Units of measurement took 0.00032067298889160156s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.2541191577911377s
Reputation | Calculation of the PageRank for Units of measurement took 0.020531177520751953s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0002827644348144531s
Believability | Calculation of trust value for Units of measurement took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-uo took 2.580007314682007s
Availability | SPARQL endpoint availability check for VANDF took 4.1961669921875e-05s
Availability | VoID file availability check for VANDF took 0.0004334449768066406s
Completeness | Calculation of interlinking completeness for VANDF took 0.26068615913391113s
Reputation | Calculation of the PageRank for VANDF took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for VANDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for VANDF took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0006802082061767578s
Believability | Calculation of trust value for VANDF took 7.62939453125e-06s
INFO | --- Analysis for bioportal-vandf took 2.618278980255127s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 5.269050598144531e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.2594926357269287s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.02041935920715332s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.000423431396484375s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-vao took 2.614056348800659s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 4.482269287109375e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.2685236930847168s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.02055191993713379s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006406307220458984s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-vhog took 2.6132779121398926s
Availability | SPARQL endpoint availability check for VIVO took 4.291534423828125e-05s
Availability | VoID file availability check for VIVO took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for VIVO took 0.25986742973327637s
Reputation | Calculation of the PageRank for VIVO took 0.020331621170043945s
Interlinking | Calculation of Degree of Connection for VIVO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003516674041748047s
Believability | Calculation of trust value for VIVO took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-vivo took 2.6611034870147705s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.25719380378723145s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.02070784568786621s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012497901916503906s
Believability | Calculation of trust value for Vaccine Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-vo took 2.554755926132202s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.2612495422363281s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.020908594131469727s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00020647048950195312s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-vt took 2.564666509628296s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.076957702636719e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.2612936496734619s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020229339599609375s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0005259513854980469s
Believability | Calculation of trust value for C. elegans gross anatomy took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-wbbt took 2.6216559410095215s
Availability | SPARQL endpoint availability check for C. elegans development took 4.0531158447265625e-05s
Availability | VoID file availability check for C. elegans development took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.2540714740753174s
Reputation | Calculation of the PageRank for C. elegans development took 0.02015066146850586s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.601478576660156e-05s
Believability | Calculation of trust value for C. elegans development took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-wbls took 2.6279056072235107s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 4.172325134277344e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.2717719078063965s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.020179033279418945s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.606910705566406e-05s
Believability | Calculation of trust value for C. elegans phenotype took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-wbphenotype took 2.576141119003296s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 4.1961669921875e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.27282190322875977s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.020304203033447266s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0006427764892578125s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-who took 2.6290736198425293s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 4.124641418457031e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.2648954391479492s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020175457000732422s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0007016658782958984s
Believability | Calculation of trust value for Xenopus anatomy and development took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-xao took 2.6596784591674805s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.24569916725158691s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.02013564109802246s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.0002281665802001953s
Believability | Calculation of trust value for Experimental Conditions Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-xco took 2.6509785652160645s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 4.124641418457031e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.26564693450927734s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020116806030273438s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.00026154518127441406s
Believability | Calculation of trust value for Yeast phenotypes took 3.814697265625e-06s
INFO | --- Analysis for bioportal-ypo took 2.5724263191223145s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 4.1961669921875e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.26332974433898926s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.02047562599182129s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.00077056884765625s
Believability | Calculation of trust value for Zebrafish anatomy and development took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-zfa took 2.584981918334961s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 4.267692565917969e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.28150320053100586s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.020191431045532227s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 2.956390380859375e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 5.245208740234375e-06s
INFO | --- Analysis for Bioportal_link took 3.866814613342285s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.4419994354248047s
Availability | VoID file availability check for BioSamples RDF took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.2661116123199463s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.020582199096679688s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.552436828613281e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.1205673217773438e-05s
INFO | --- Analysis for biosamples-rdf took 3.4504783153533936s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.2116563320159912s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.2627542018890381s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.0204007625579834s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00016021728515625s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 6.198883056640625e-06s
INFO | --- Analysis for bis-linked-data took 2.564409017562866s
Availability | SPARQL endpoint availability check for Bitzi took 0.00010728836059570312s
Availability | VoID file availability check for Bitzi took 0.00020575523376464844s
Completeness | Calculation of interlinking completeness for Bitzi took 0.27610325813293457s
Reputation | Calculation of the PageRank for Bitzi took 0.02016758918762207s
Interlinking | Calculation of Degree of Connection for Bitzi took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bitzi took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Bitzi took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bitzi took 5.4836273193359375e-06s
INFO | --- Analysis for bitzi took 2.997236728668213s
Availability | SPARQL endpoint availability check for BizkaiSense took 4.029273986816406e-05s
Availability | VoID file availability check for BizkaiSense took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.2513766288757324s
Reputation | Calculation of the PageRank for BizkaiSense took 0.02022719383239746s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 2.956390380859375e-05s
Believability | Calculation of trust value for BizkaiSense took 5.7220458984375e-06s
INFO | --- Analysis for bizkaisense took 2.9273808002471924s
Availability | SPARQL endpoint availability check for blabla.itemlist took 3.910064697265625e-05s
Availability | VoID file availability check for blabla.itemlist took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.25669097900390625s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020053386688232422s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.0040740966796875e-05s
Believability | Calculation of trust value for blabla.itemlist took 1.3828277587890625e-05s
INFO | --- Analysis for blabla-itemlist took 2.8524911403656006s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.00543212890625e-05s
Availability | VoID file availability check for blabla.itemlist took 0.00022077560424804688s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.2765974998474121s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.02022576332092285s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 3.0279159545898438e-05s
Believability | Calculation of trust value for blabla.itemlist took 5.4836273193359375e-06s
INFO | --- Analysis for blabla_itemlist took 2.9398646354675293s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.315376281738281e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.2814791202545166s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.020096302032470703s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.0531158447265625e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 6.198883056640625e-06s
INFO | --- Analysis for bll-thesaurus took 3.575838804244995s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.370246171951294s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.2525334358215332s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.020177602767944336s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.437301635742188e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 5.4836273193359375e-06s
INFO | --- Analysis for bluk-bnb took 11.3833589553833s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.22025203704833984s
Availability | VoID file availability check for Thesaurus BNCF took 0.0005960464477539062s
Extra | Recovery of all triples for Thesaurus BNCF took 60.86406850814819s
Performance | Total latancy measurement for Thesaurus BNCF took 0.5303530693054199s
Amount of data | Number of triples check for Thesaurus BNCF took 0.8626973628997803s
Interoperability | New terms check for Thesaurus BNCF took 1.5437719821929932s
Versatility | Languages check for Thesaurus BNCF took 9.52586317062378s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 1.3068668842315674s
Security | Check HTTPS for Thesaurus BNCF took 0.06807971000671387s
Interpretability | RDF structures check for Thesaurus BNCF took 0.11136150360107422s
Versatility | Serialization formats check for Thesaurus BNCF took 0.11447262763977051s
Availability | RDF dump link check for Thesaurus BNCF took 0.11793780326843262s
License | MR license check for Thesaurus BNCF took 0.11232304573059082s
License | HR license check for Thesaurus BNCF took 0.2875406742095947s
Amount of data | Number of property check for Thesaurus BNCF took 0.11390137672424316s
Understandability | Number of label check for Thesaurus BNCF took 0.26610660552978516s
Understandability | URI regex check for Thesaurus BNCF took 0.21755242347717285s
Understandability | Vocabs check for Thesaurus BNCF took 0.11864972114562988s
Verifiability | Authors check for Thesaurus BNCF took 0.12024569511413574s
Verifiability | Publishers check for Thesaurus BNCF took 0.11019015312194824s
Performance | Throughput check for Thesaurus BNCF took 10.551166296005249s
Amount of data | Check the number of entities for Thesaurus BNCF took 0.000102996826171875s
Verifiability | Contribs. check for Thesaurus BNCF took 0.12058806419372559s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.10522818565368652s
Interlinking | skos check for Thesaurus BNCF took 0.2076585292816162s
Interlinking | skos check for Thesaurus BNCF took 0.1869969367980957s
Timeliness | dataset update frequency check for Thesaurus BNCF took 1.0812304019927979s
Currency | Creation date check for Thesaurus BNCF took 0.9690780639648438s
Currency | Modification date check for Thesaurus BNCF took 0.23040032386779785s
Rep.Conc. | URIs length for Thesaurus BNCF took 26.82012391090393s
Interoperability | New vocabularies check for Thesaurus BNCF took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.11009812355041504s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.10790252685546875s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.10532999038696289s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 11.519210815429688s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.5028433799743652s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.9322431087493896s
Consistency | Disjoint class check for Thesaurus BNCF took 0.10357141494750977s
Consistency | Check Misplaced properties for Thesaurus BNCF took 1.080829381942749s
Consistency | Misplaced classes for Thesaurus BNCF took 6.866278171539307s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 8.666964292526245s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.477545976638794s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.5375566482543945s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.3900606632232666s
Security | Sign check for Thesaurus BNCF took 0.13081097602844238s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 21.94771671295166s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.3474299907684326s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.02022242546081543s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 6.842613220214844e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 1.6689300537109375e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 7.867813110351562e-06s
INFO | --- Analysis for bncf-ns took 211.0849323272705s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4490220546722412s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0006940364837646484s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.5275883674621582s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6829142570495605s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.438828706741333s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.3232104778289795s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.335161209106445s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.0206298828125s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3020210266113281s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.009974241256714s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5353279113769531s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4668397903442383s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5316946506500244s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.25171422958374s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.35172247886657715s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7103512287139893s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6433184146881104s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.44987034797668457s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5217363834381104s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.35825109481811523s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.356247186660767s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.343292236328125e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.39626002311706543s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.28206300735473633s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.35942792892456055s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.34616541862487793s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4224684238433838s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9627366065979004s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3390834331512451s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 17.672635555267334s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3422079086303711s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.2315690517425537s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9703502655029297s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.67344331741333s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02343130111694336s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.028524160385131836s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.32212257385253906s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.741620302200317s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.42418551445007324s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.690162181854248s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6113314628601074s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 14.688698768615723s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.030936479568481445s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5532629489898682s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.34523487091064453s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.91129994392395s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.35321879386901855s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.020609617233276367s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.100799560546875e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.430511474609375e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 9.298324584960938e-06s
INFO | --- Analysis for bpr took 435.8958444595337s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 4.220008850097656e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.27997517585754395s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.020315885543823242s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 6.747245788574219e-05s
Believability | Calculation of trust value for Brazilian Politicians took 8.106231689453125e-06s
INFO | --- Analysis for brazilian-politicians took 3.9019784927368164s
Availability | SPARQL endpoint availability check for BrazilianCities took 4.76837158203125e-05s
Availability | VoID file availability check for BrazilianCities took 0.00022220611572265625s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.7268455028533936s
Reputation | Calculation of the PageRank for BrazilianCities took 0.020255327224731445s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 4.839897155761719e-05s
Believability | Calculation of trust value for BrazilianCities took 6.67572021484375e-06s
INFO | --- Analysis for braziliancities took 3.8040990829467773s
Availability | SPARQL endpoint availability check for Bricklink took 1.5608844757080078s
Availability | VoID file availability check for Bricklink took 0.00037980079650878906s
Completeness | Calculation of interlinking completeness for Bricklink took 0.6865746974945068s
Reputation | Calculation of the PageRank for Bricklink took 0.020043611526489258s
Interlinking | Calculation of Degree of Connection for Bricklink took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bricklink took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.628036499023438e-05s
Believability | Calculation of trust value for Bricklink took 1.049041748046875e-05s
INFO | --- Analysis for bricklink took 10.969292640686035s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.0824978351593s
Availability | VoID file availability check for British Museum Collection took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.26979875564575195s
Reputation | Calculation of the PageRank for British Museum Collection took 0.020055294036865234s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 2.956390380859375e-05s
Believability | Calculation of trust value for British Museum Collection took 6.198883056640625e-06s
INFO | --- Analysis for british-museum-collection took 72.71051216125488s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 4.649162292480469e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.7213315963745117s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.022715330123901367s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 4.673004150390625e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.33514404296875e-05s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 3.415604591369629s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 3.886222839355469e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.2680232524871826s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.02001810073852539s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 2.956390380859375e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 5.245208740234375e-06s
INFO | --- Analysis for bsv took 2.9576706886291504s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.765620708465576s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.7034554481506348s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.020217180252075195s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.3589859008789062e-05s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 6.4373016357421875e-06s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 7.543712615966797s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 4.172325134277344e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.25288820266723633s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.023879528045654297s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 2.956390380859375e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 5.7220458984375e-06s
INFO | --- Analysis for bund-offener-haushalt took 3.332338809967041s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 8.654594421386719e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.23810672760009766s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.020112037658691406s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 2.9325485229492188e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 6.198883056640625e-06s
INFO | --- Analysis for bundestagnebeneinkuenfte took 2.8517041206359863s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.5917689800262451s
Availability | VoID file availability check for business.data.gov.uk took 0.0002167224884033203s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.2740285396575928s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.020111799240112305s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 4.76837158203125e-05s
Believability | Calculation of trust value for business.data.gov.uk took 3.814697265625e-06s
INFO | --- Analysis for business-data-gov-uk took 3.065899133682251s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.48101162910461426s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0002701282501220703s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 2.266394853591919s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.9125359058380127s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.41012048721313477s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.739344835281372s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 41.04092621803284s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.373244047164917s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.21967124938964844s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.5288021564483643s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.3736295700073242s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.33015918731689453s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.43741464614868164s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 19.70357346534729s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.41335558891296387s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.8621339797973633s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.7097697257995605s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.35722994804382324s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.5889620780944824s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.3803977966308594s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.481249332427979s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 8.273124694824219e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.3745284080505371s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.3715081214904785s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.40687131881713867s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.34792494773864746s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.35888099670410156s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.8239161968231201s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.6603245735168457s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 3.241474151611328s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.3420741558074951s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.4924795627593994s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.5196046829223633s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 1.2338836193084717s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.03320884704589844s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.027530670166015625s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.4201996326446533s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.4663522243499756s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.44304895401000977s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.0515623092651367s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.2977993488311768s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.5094351768493652s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.03207850456237793s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.3500175476074219s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.353243350982666s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 10071.483036518097s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 1.5772314071655273s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.020951271057128906s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 6.604194641113281e-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 6.4373016357421875e-06s
INFO | --- Analysis for BVMC took 10297.508442401886s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 4.076957702636719e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.25885796546936035s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.020299673080444336s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 2.86102294921875e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 6.67572021484375e-06s
INFO | --- Analysis for cabbage took 3.442554235458374s
Availability | SPARQL endpoint availability check for cablegate took 1.5015287399291992s
Availability | VoID file availability check for cablegate took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for cablegate took 0.2750680446624756s
Reputation | Calculation of the PageRank for cablegate took 0.020160198211669922s
Interlinking | Calculation of Degree of Connection for cablegate took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.723403930664062e-05s
Believability | Calculation of trust value for cablegate took 5.4836273193359375e-06s
INFO | --- Analysis for cablegate took 16.69178819656372s
Availability | SPARQL endpoint availability check for Calames took 4.38690185546875e-05s
Availability | VoID file availability check for Calames took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for Calames took 0.2529740333557129s
Reputation | Calculation of the PageRank for Calames took 0.02117443084716797s
Interlinking | Calculation of Degree of Connection for Calames took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Calames took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Calames took 3.743171691894531e-05s
Believability | Calculation of trust value for Calames took 5.245208740234375e-06s
INFO | --- Analysis for calames took 4.847597599029541s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.39801979064941406s
Availability | VoID file availability check for CaLiGraph took 0.0002486705780029297s
Extra | Recovery of all triples for CaLiGraph took 1.7524549961090088s
Performance | Total latancy measurement for CaLiGraph took 1.251094102859497s
Amount of data | Number of triples check for CaLiGraph took 12.501919507980347s
Interoperability | New terms check for CaLiGraph took 1.934701919555664s
Versatility | Languages check for CaLiGraph took 60.35290837287903s
Interpretability | Number of blank nodes check for CaLiGraph took 0.2413651943206787s
Security | Check HTTPS for CaLiGraph took 0.13968825340270996s
Interpretability | RDF structures check for CaLiGraph took 0.28867197036743164s
Versatility | Serialization formats check for CaLiGraph took 0.34085941314697266s
Availability | RDF dump link check for CaLiGraph took 0.2605020999908447s
License | MR license check for CaLiGraph took 0.35132527351379395s
License | HR license check for CaLiGraph took 60.33282113075256s
Amount of data | Number of property check for CaLiGraph took 0.29362034797668457s
Understandability | Number of label check for CaLiGraph took 3.3251664638519287s
Understandability | URI regex check for CaLiGraph took 0.5157678127288818s
Understandability | Vocabs check for CaLiGraph took 0.3230769634246826s
Verifiability | Authors check for CaLiGraph took 0.3042120933532715s
Verifiability | Publishers check for CaLiGraph took 0.24785065650939941s
Performance | Throughput check for CaLiGraph took 11.032564640045166s
Amount of data | Check the number of entities for CaLiGraph took 0.012955188751220703s
Verifiability | Contribs. check for CaLiGraph took 0.2901332378387451s
Interlinking | sameAs chians check for CaLiGraph took 0.7237851619720459s
Interlinking | skos check for CaLiGraph took 0.3950200080871582s
Interlinking | skos check for CaLiGraph took 0.2760326862335205s
Timeliness | dataset update frequency check for CaLiGraph took 0.36986494064331055s
Currency | Creation date check for CaLiGraph took 0.5832521915435791s
Currency | Modification date check for CaLiGraph took 0.5837266445159912s
Rep.Conc. | URIs length for CaLiGraph took 61.021506786346436s
Interoperability | New vocabularies check for CaLiGraph took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.27387499809265137s
Accuracy | Check Functional Property for CaLiGraph took 0.3166372776031494s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.3041708469390869s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.6216475963592529s
Accuracy | Check White space in annotation for CaLiGraph took 0.02634882926940918s
Accuracy | Check Datatype consistency for CaLiGraph took 0.04937314987182617s
Consistency | Disjoint class check for CaLiGraph took 0.26470398902893066s
Consistency | Check Misplaced properties for CaLiGraph took 60.955161333084106s
Consistency | Misplaced classes for CaLiGraph took 0.5280263423919678s
Consistency | Check Ontology hijacking for CaLiGraph took 1.973193883895874s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.298306941986084s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.635515213012695s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.0338132381439209s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.47382044792175293s
Security | Sign check for CaLiGraph took 0.3758814334869385s
Availability | Check URIs Dereferenciability for CaLiGraph took 18.239112377166748s
Completeness | Calculation of interlinking completeness for CaLiGraph took 1.2181787490844727s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020284175872802734s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 2.9325485229492188e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.430511474609375e-06s
Believability | Calculation of trust value for CaLiGraph took 6.4373016357421875e-06s
INFO | --- Analysis for CaLiGraph took 1497.6976368427277s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.2531576156616211s
Availability | VoID file availability check for CaLiGraph took 0.0005385875701904297s
Extra | Recovery of all triples for CaLiGraph took 1.212571620941162s
Performance | Total latancy measurement for CaLiGraph took 1.1477935314178467s
Amount of data | Number of triples check for CaLiGraph took 12.69904637336731s
Interoperability | New terms check for CaLiGraph took 1.897871971130371s
Versatility | Languages check for CaLiGraph took 60.31277346611023s
Interpretability | Number of blank nodes check for CaLiGraph took 0.29121875762939453s
Security | Check HTTPS for CaLiGraph took 0.17064452171325684s
Interpretability | RDF structures check for CaLiGraph took 0.2871100902557373s
Versatility | Serialization formats check for CaLiGraph took 0.2900211811065674s
Availability | RDF dump link check for CaLiGraph took 0.26166582107543945s
License | MR license check for CaLiGraph took 0.25417256355285645s
License | HR license check for CaLiGraph took 60.29344439506531s
Amount of data | Number of property check for CaLiGraph took 0.3122982978820801s
Understandability | Number of label check for CaLiGraph took 3.109790802001953s
Understandability | URI regex check for CaLiGraph took 0.5104138851165771s
Understandability | Vocabs check for CaLiGraph took 0.2683718204498291s
Verifiability | Authors check for CaLiGraph took 0.3239262104034424s
Verifiability | Publishers check for CaLiGraph took 0.30594301223754883s
Performance | Throughput check for CaLiGraph took 10.91112995147705s
Amount of data | Check the number of entities for CaLiGraph took 0.014989376068115234s
Verifiability | Contribs. check for CaLiGraph took 0.2594609260559082s
Interlinking | sameAs chians check for CaLiGraph took 0.6886959075927734s
Interlinking | skos check for CaLiGraph took 0.26728034019470215s
Interlinking | skos check for CaLiGraph took 0.2561805248260498s
Timeliness | dataset update frequency check for CaLiGraph took 0.2828636169433594s
Currency | Creation date check for CaLiGraph took 0.5786941051483154s
Currency | Modification date check for CaLiGraph took 0.5412089824676514s
Rep.Conc. | URIs length for CaLiGraph took 61.051257848739624s
Interoperability | New vocabularies check for CaLiGraph took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.2576735019683838s
Accuracy | Check Functional Property for CaLiGraph took 0.2567780017852783s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2646610736846924s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5535578727722168s
Accuracy | Check White space in annotation for CaLiGraph took 0.025938749313354492s
Accuracy | Check Datatype consistency for CaLiGraph took 0.049874305725097656s
Consistency | Disjoint class check for CaLiGraph took 0.2603645324707031s
Consistency | Check Misplaced properties for CaLiGraph took 60.98792028427124s
Consistency | Misplaced classes for CaLiGraph took 0.6133015155792236s
Consistency | Check Ontology hijacking for CaLiGraph took 2.0114188194274902s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.327345848083496s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.66944146156311s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.02956080436706543s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.4748215675354004s
Security | Sign check for CaLiGraph took 0.27581119537353516s
Availability | Check URIs Dereferenciability for CaLiGraph took 22.325968980789185s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.4270455837249756s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02023935317993164s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 7.390975952148438e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.1920928955078125e-06s
Believability | Calculation of trust value for CaLiGraph took 5.4836273193359375e-06s
INFO | --- Analysis for caligraph took 1501.2377498149872s
Availability | SPARQL endpoint availability check for can-link took 4.0531158447265625e-05s
Availability | VoID file availability check for can-link took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for can-link took 0.25489044189453125s
Reputation | Calculation of the PageRank for can-link took 0.020337581634521484s
Interlinking | Calculation of Degree of Connection for can-link took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for can-link took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for can-link took 3.075599670410156e-05s
Believability | Calculation of trust value for can-link took 7.62939453125e-06s
INFO | --- Analysis for can-link took 3.374199867248535s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.07393217086791992s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.00042438507080078125s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.2715282440185547s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.02041006088256836s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.147125244140625e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 1.2159347534179688e-05s
INFO | --- Analysis for cap-italy-rdf took 2.553649425506592s
Availability | SPARQL endpoint availability check for person took 4.1484832763671875e-05s
Availability | VoID file availability check for person took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for person took 0.2677440643310547s
Reputation | Calculation of the PageRank for person took 0.020170927047729492s
Interlinking | Calculation of Degree of Connection for person took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for person took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for person took 3.147125244140625e-05s
Believability | Calculation of trust value for person took 6.9141387939453125e-06s
INFO | --- Analysis for card took 2.4125726222991943s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 4.100799560546875e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0003523826599121094s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.7052011489868164s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020230531692504883s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 4.1484832763671875e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 6.67572021484375e-06s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 4.444978475570679s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 8.821487426757812e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.00022292137145996094s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.26514410972595215s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.020334959030151367s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 3.147125244140625e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 3.218650817871094e-05s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 2.9256434440612793s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 392.0181097984314s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.27498650550842285s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.020264387130737305s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 4.38690185546875e-05s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 5.245208740234375e-06s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 666.9740517139435s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.887580871582031e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.2727799415588379s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.020550966262817383s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00010275840759277344s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.3113021850585938e-05s
INFO | --- Analysis for ce4r took 19.488701820373535s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4049103260040283s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.00026535987854003906s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.1739435195922852s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.8647730350494385s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3192613124847412s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6747000217437744s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.15223836898804s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15938138961791992s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.38805174827575684s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14363622665405273s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.12969160079956055s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.25998687744140625s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3309926986694336s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15718483924865723s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3026871681213379s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2931220531463623s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16915082931518555s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.21345186233520508s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.19656634330749512s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.698474884033203s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.414817810058594e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15762639045715332s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.21077179908752441s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2724602222442627s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15623879432678223s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16399359703063965s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.47407031059265137s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.20031952857971191s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.135610580444336s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17575502395629883s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.18754935264587402s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.2067708969116211s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.5539395809173584s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.027904272079467773s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.02746272087097168s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.19632506370544434s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.202864408493042s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 2.0041732788085938s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.3265724182128906s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.477437973022461s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.02991032600402832s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.18177127838134766s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15749645233154297s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 1948.5681631565094s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 1.3832547664642334s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.02028179168701172s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.3392181396484375e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.6689300537109375e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 6.9141387939453125e-06s
INFO | --- Analysis for ceo took 2073.7329983711243s
Availability | SPARQL endpoint availability check for Charging Stations took 7.677078247070312e-05s
Availability | VoID file availability check for Charging Stations took 0.0002243518829345703s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.27248120307922363s
Reputation | Calculation of the PageRank for Charging Stations took 0.020063161849975586s
Interlinking | Calculation of Degree of Connection for Charging Stations took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Charging Stations took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 3.170967102050781e-05s
Believability | Calculation of trust value for Charging Stations took 5.7220458984375e-06s
INFO | --- Analysis for charging-stations took 4.233119964599609s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.2438507080078125e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.2553369998931885s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.02015972137451172s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.3855438232421875e-05s
Believability | Calculation of trust value for Chat Game corpus took 6.67572021484375e-06s
INFO | --- Analysis for chat-game-corpus took 13.464775085449219s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 4.029273986816406e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.00021886825561523438s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.26561474800109863s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.020454883575439453s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.409385681152344e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 1.3589859008789062e-05s
INFO | --- Analysis for chebi took 2.942819595336914s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.124641418457031e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.000942230224609375s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.28075122833251953s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.02065753936767578s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.7697296142578125e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 6.67572021484375e-06s
INFO | --- Analysis for chem2bio2rdf took 136.86776971817017s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.6232752799987793s
Availability | VoID file availability check for ChEMBL RDF took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.7118492126464844s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.020392417907714844s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.1021575927734375e-05s
Believability | Calculation of trust value for ChEMBL RDF took 9.298324584960938e-06s
INFO | --- Analysis for chembl-rdf took 4.364570617675781s
Availability | SPARQL endpoint availability check for chemdb  dataset took 0.879885196685791s
Availability | VoID file availability check for chemdb  dataset took 0.0002694129943847656s
Extra | Recovery of all triples for chemdb  dataset took 4.9984400272369385s
Performance | Total latancy measurement for chemdb  dataset took 2.48602294921875s
Amount of data | Number of triples check for chemdb  dataset took 0.5503139495849609s
Interoperability | New terms check for chemdb  dataset took 3.488323450088501s
Versatility | Languages check for chemdb  dataset took 29.490309953689575s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5373845100402832s
Interpretability | RDF structures check for chemdb  dataset took 2.136277198791504s
Versatility | Serialization formats check for chemdb  dataset took 1.4811689853668213s
Availability | RDF dump link check for chemdb  dataset took 0.8303537368774414s
License | MR license check for chemdb  dataset took 2.9804799556732178s
License | HR license check for chemdb  dataset took 4.0772011280059814s
Amount of data | Number of property check for chemdb  dataset took 0.5299735069274902s
Understandability | Number of label check for chemdb  dataset took 5.057567358016968s
Understandability | URI regex check for chemdb  dataset took 1.9118659496307373s
Understandability | Vocabs check for chemdb  dataset took 0.829115629196167s
Verifiability | Authors check for chemdb  dataset took 1.1296615600585938s
Verifiability | Publishers check for chemdb  dataset took 0.8381199836730957s
Performance | Throughput check for chemdb  dataset took 15.486253261566162s
Amount of data | Check the number of entities for chemdb  dataset took 6.604194641113281e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.8167886734008789s
Interlinking | sameAs chians check for chemdb  dataset took 1.1666898727416992s
Interlinking | skos check for chemdb  dataset took 3.1269123554229736s
Interlinking | skos check for chemdb  dataset took 0.5021979808807373s
Timeliness | dataset update frequency check for chemdb  dataset took 1.0959043502807617s
Currency | Creation date check for chemdb  dataset took 1.3425266742706299s
Currency | Modification date check for chemdb  dataset took 1.0225775241851807s
Rep.Conc. | URIs length for chemdb  dataset took 2.9344122409820557s
Interoperability | New vocabularies check for chemdb  dataset took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5284609794616699s
Accuracy | Check Functional Property for chemdb  dataset took 0.8207321166992188s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.7674660682678223s
Accuracy | Check Empty annotation labels for chemdb  dataset took 2.3270325660705566s
Accuracy | Check White space in annotation for chemdb  dataset took 0.02983832359313965s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.03348064422607422s
Consistency | Disjoint class check for chemdb  dataset took 0.8090529441833496s
Consistency | Check Misplaced properties for chemdb  dataset took 1.2243988513946533s
Consistency | Misplaced classes for chemdb  dataset took 0.6584835052490234s
Consistency | Check Ontology hijacking for chemdb  dataset took 3.605903387069702s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.3225607872009277s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 2.0151405334472656s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.03402352333068848s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.522381067276001s
Security | Sign check for chemdb  dataset took 2.182996988296509s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2674.018028497696s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 1.077301025390625s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.021045446395874023s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 7.677078247070312e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 9.5367431640625e-07s
Believability | Calculation of trust value for chemdb  dataset took 5.4836273193359375e-06s
INFO | --- Analysis for chemdb-basicInfo took 3740.081959247589s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.5261209011077881s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.00024962425231933594s
Extra | Recovery of all triples for chemdb estimated properties dataset took 13.305417776107788s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.5070717334747314s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.5534272193908691s
Interoperability | New terms check for chemdb estimated properties dataset took 3.9235851764678955s
Versatility | Languages check for chemdb estimated properties dataset took 28.73847723007202s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.5266468524932861s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.5228173732757568s
Versatility | Serialization formats check for chemdb estimated properties dataset took 1.5701301097869873s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.8373253345489502s
License | MR license check for chemdb estimated properties dataset took 3.2330074310302734s
License | HR license check for chemdb estimated properties dataset took 4.083735466003418s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5224487781524658s
Understandability | Number of label check for chemdb estimated properties dataset took 5.570791721343994s
Understandability | URI regex check for chemdb estimated properties dataset took 2.1404428482055664s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.870866060256958s
Verifiability | Authors check for chemdb estimated properties dataset took 1.2328393459320068s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.8928239345550537s
Performance | Throughput check for chemdb estimated properties dataset took 13.446422338485718s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 7.033348083496094e-05s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.8567380905151367s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 1.1976561546325684s
Interlinking | skos check for chemdb estimated properties dataset took 2.175976514816284s
Interlinking | skos check for chemdb estimated properties dataset took 0.6272189617156982s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 1.1690294742584229s
Currency | Creation date check for chemdb estimated properties dataset took 1.3335018157958984s
Currency | Modification date check for chemdb estimated properties dataset took 1.0149497985839844s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 3.4100754261016846s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.49994754791259766s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.8641047477722168s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.786776065826416s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 3.0961949825286865s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.029565811157226562s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.03342437744140625s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.8848795890808105s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.203042984008789s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.6101841926574707s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 3.9711873531341553s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.3092381954193115s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 2.0274555683135986s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.0343317985534668s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.6123073101043701s
Security | Sign check for chemdb estimated properties dataset took 2.3860325813293457s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 2671.9066922664642s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 1.073293924331665s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.020826339721679688s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 4.553794860839844e-05s
Interoperability | Check the re-using of existing vocabs for chemdb estimated properties dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb estimated properties dataset took 7.867813110351562e-06s
INFO | --- Analysis for chemdb-estimatedProperties took 3737.5166857242584s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5200369358062744s
Availability | VoID file availability check for chemdb phase transition dataset took 0.00021529197692871094s
Extra | Recovery of all triples for chemdb phase transition dataset took 9.316429138183594s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.503612518310547s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.5507147312164307s
Interoperability | New terms check for chemdb phase transition dataset took 3.9363086223602295s
Versatility | Languages check for chemdb phase transition dataset took 27.322720527648926s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.5299584865570068s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.526432991027832s
Versatility | Serialization formats check for chemdb phase transition dataset took 1.543736457824707s
Availability | RDF dump link check for chemdb phase transition dataset took 0.8509666919708252s
License | MR license check for chemdb phase transition dataset took 2.7537472248077393s
License | HR license check for chemdb phase transition dataset took 4.141422986984253s
Amount of data | Number of property check for chemdb phase transition dataset took 0.5266284942626953s
Understandability | Number of label check for chemdb phase transition dataset took 5.380066394805908s
Understandability | URI regex check for chemdb phase transition dataset took 1.7979652881622314s
Understandability | Vocabs check for chemdb phase transition dataset took 0.867215633392334s
Verifiability | Authors check for chemdb phase transition dataset took 1.20522141456604s
Verifiability | Publishers check for chemdb phase transition dataset took 0.8297891616821289s
Performance | Throughput check for chemdb phase transition dataset took 11.554458856582642s
Amount of data | Check the number of entities for chemdb phase transition dataset took 7.081031799316406e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.8365530967712402s
Interlinking | sameAs chians check for chemdb phase transition dataset took 1.0096690654754639s
Interlinking | skos check for chemdb phase transition dataset took 2.363621711730957s
Interlinking | skos check for chemdb phase transition dataset took 0.4956963062286377s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 1.2201814651489258s
Currency | Creation date check for chemdb phase transition dataset took 1.3531274795532227s
Currency | Modification date check for chemdb phase transition dataset took 1.0065457820892334s
Rep.Conc. | URIs length for chemdb phase transition dataset took 3.489138603210449s
Interoperability | New vocabularies check for chemdb phase transition dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.49285078048706055s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.7834100723266602s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.8048000335693359s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 3.0423266887664795s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.02978992462158203s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.03260445594787598s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.858712911605835s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.2430963516235352s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.6194262504577637s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 3.974040985107422s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.3069837093353271s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 2.0067663192749023s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.03243684768676758s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.5276908874511719s
Security | Sign check for chemdb phase transition dataset took 2.3682072162628174s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2663.469288110733s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 1.49153733253479s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.020830392837524414s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 5.1021575927734375e-05s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for chemdb phase transition dataset took 7.867813110351562e-06s
INFO | --- Analysis for chemdb-phaseTransition took 3716.4823520183563s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.536160945892334s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.00022840499877929688s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 13.248481750488281s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.5355358123779297s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.5536139011383057s
Interoperability | New terms check for chemdb thermochemistry dataset took 3.959970474243164s
Versatility | Languages check for chemdb thermochemistry dataset took 28.71055293083191s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.5416429042816162s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.5250964164733887s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 1.3077504634857178s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.8060264587402344s
License | MR license check for chemdb thermochemistry dataset took 2.6831212043762207s
License | HR license check for chemdb thermochemistry dataset took 4.0663652420043945s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.5220992565155029s
Understandability | Number of label check for chemdb thermochemistry dataset took 4.715127468109131s
Understandability | URI regex check for chemdb thermochemistry dataset took 1.918335199356079s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.8282256126403809s
Verifiability | Authors check for chemdb thermochemistry dataset took 1.138106346130371s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.8105266094207764s
Performance | Throughput check for chemdb thermochemistry dataset took 12.022647619247437s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 7.748603820800781e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.8235805034637451s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 0.9731476306915283s
Interlinking | skos check for chemdb thermochemistry dataset took 2.0752177238464355s
Interlinking | skos check for chemdb thermochemistry dataset took 0.4960942268371582s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 1.1446681022644043s
Currency | Creation date check for chemdb thermochemistry dataset took 1.3226690292358398s
Currency | Modification date check for chemdb thermochemistry dataset took 1.0264384746551514s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 3.4214913845062256s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.4937114715576172s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.8072822093963623s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.7790446281433105s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 3.1611850261688232s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.02988457679748535s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.03428077697753906s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.8369066715240479s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.2482469081878662s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.6055026054382324s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 3.9525768756866455s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.3215887546539307s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 2.023674488067627s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.03549957275390625s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.5343728065490723s
Security | Sign check for chemdb thermochemistry dataset took 2.1128458976745605s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2730.066771507263s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 1.061112880706787s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.02041316032409668s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 5.984306335449219e-05s
Interoperability | Check the re-using of existing vocabs for chemdb thermochemistry dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 6.198883056640625e-06s
INFO | --- Analysis for chemdb-thermochemistry took 3782.617125272751s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 4.076957702636719e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0005867481231689453s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.2814977169036865s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.02008986473083496s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.075599670410156e-05s
Believability | Calculation of trust value for ChemPedia RDF took 5.9604644775390625e-06s
INFO | --- Analysis for chempedia-rdf took 9.87834882736206s
Availability | SPARQL endpoint availability check for Chiman Maru took 4.1484832763671875e-05s
Availability | VoID file availability check for Chiman Maru took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.29879140853881836s
Reputation | Calculation of the PageRank for Chiman Maru took 0.020229816436767578s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.24249267578125e-05s
Believability | Calculation of trust value for Chiman Maru took 5.7220458984375e-06s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 3.275120973587036s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 392.29336500167847s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.27190685272216797s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.020226478576660156s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 3.6716461181640625e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 6.198883056640625e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 798.341150522232s
Availability | SPARQL endpoint availability check for Chronicling America took 4.553794860839844e-05s
Availability | VoID file availability check for Chronicling America took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.28139352798461914s
Reputation | Calculation of the PageRank for Chronicling America took 0.020048141479492188s
Interlinking | Calculation of Degree of Connection for Chronicling America took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00010228157043457031s
Believability | Calculation of trust value for Chronicling America took 5.9604644775390625e-06s
INFO | --- Analysis for chronicling-america took 17.767131328582764s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.689842939376831s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0006458759307861328s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 83.31130719184875s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.692411184310913s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.6563031673431396s
Interoperability | New terms check for Cultural Heritage Thesaurus took 3.367370128631592s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.3582265377044678s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.5519571304321289s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.3065166473388672s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.27244019508361816s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 10.312652587890625s
License | MR license check for Cultural Heritage Thesaurus took 0.2644309997558594s
License | HR license check for Cultural Heritage Thesaurus took 0.35854077339172363s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.31191563606262207s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.33675384521484375s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.5448818206787109s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.3017430305480957s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.33228135108947754s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.3041670322418213s
Performance | Throughput check for Cultural Heritage Thesaurus took 11.979077339172363s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 8.940696716308594e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.3168027400970459s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.3121457099914551s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.31212282180786133s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.32803940773010254s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.3182213306427002s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.6615121364593506s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.6039702892303467s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 9.947162628173828s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 1.581322431564331s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.35373783111572266s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.2886509895324707s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.31135988235473633s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 3.398315906524658s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.21920251846313477s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.2994067668914795s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.0764551162719727s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.2981994152069092s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 5.544859886169434s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.379896402359009s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00022029876708984375s
Security | Sign check for Cultural Heritage Thesaurus took 0.3034493923187256s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 270.21855878829956s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.947420597076416s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.1446676254272461s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 3.2901763916015625e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.001577138900756836s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.00022554397583007812s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 0.9502465724945068s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for cht took 442.1499238014221s
Availability | SPARQL endpoint availability check for ciard-ring took 9.965896606445312e-05s
Availability | VoID file availability check for ciard-ring took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.6808052062988281s
Reputation | Calculation of the PageRank for ciard-ring took 0.021346569061279297s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 6.008148193359375e-05s
Believability | Calculation of trust value for ciard-ring took 1.2159347534179688e-05s
INFO | --- Analysis for ciard-ring took 6.246890306472778s
Availability | SPARQL endpoint availability check for Cine Figure took 4.649162292480469e-05s
Availability | VoID file availability check for Cine Figure took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.2684612274169922s
Reputation | Calculation of the PageRank for Cine Figure took 0.021244049072265625s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 6.0558319091796875e-05s
Believability | Calculation of trust value for Cine Figure took 1.049041748046875e-05s
INFO | --- Analysis for Cine_Figure took 2.3829448223114014s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 21.19500494003296s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.27658653259277344s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.020943880081176758s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 5.555152893066406e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 6.198883056640625e-06s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 175.4927396774292s
Availability | SPARQL endpoint availability check for CIPFA took 4.1484832763671875e-05s
Availability | VoID file availability check for CIPFA took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for CIPFA took 0.2693314552307129s
Reputation | Calculation of the PageRank for CIPFA took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.8623809814453125e-05s
Believability | Calculation of trust value for CIPFA took 4.291534423828125e-06s
INFO | --- Analysis for cipfa took 3.468501091003418s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 0.2756001949310303s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.2617623805999756s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.020865440368652344s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.0003972053527832031s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 6.198883056640625e-06s
INFO | --- Analysis for ckan took 2.8355774879455566s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.561631441116333s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0006539821624755859s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.2670712471008301s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.020411014556884766s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 4.482269287109375e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 5.245208740234375e-06s
INFO | --- Analysis for CLaSSES took 4.51111912727356s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.267692565917969e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.26374030113220215s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.020409107208251953s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.409385681152344e-05s
Believability | Calculation of trust value for Temples of the Classical World took 1.2159347534179688e-05s
INFO | --- Analysis for classical_temples took 3.424821138381958s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 2.2628746032714844s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.2709503173828125s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.020427465438842773s
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.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.654594421386719e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 5.245208740234375e-06s
INFO | --- Analysis for clean-energy-data-reegle took 13.126384973526001s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.38690185546875e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.26616597175598145s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.020375967025756836s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 8.0108642578125e-05s
Believability | Calculation of trust value for CLLD-afbo took 6.67572021484375e-06s
INFO | --- Analysis for clld-afbo took 3.439805746078491s
Availability | SPARQL endpoint availability check for CLLD-APICS took 4.1961669921875e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.2515745162963867s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.02034592628479004s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 8.153915405273438e-05s
Believability | Calculation of trust value for CLLD-APICS took 5.245208740234375e-06s
INFO | --- Analysis for clld-apics took 3.4750587940216064s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 5.078315734863281e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.28248047828674316s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.02054882049560547s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 4.363059997558594e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 5.245208740234375e-06s
INFO | --- Analysis for clld-ewave took 3.869636058807373s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 6.914138793945312e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.2784585952758789s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.021831035614013672s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00011134147644042969s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 6.198883056640625e-06s
INFO | --- Analysis for clld-glottolog took 3.4890429973602295s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 0.00020837783813476562s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.28072452545166016s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.020694971084594727s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 8.463859558105469e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 1.1682510375976562e-05s
INFO | --- Analysis for clld-phoible took 3.4819693565368652s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 4.291534423828125e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0006165504455566406s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.2521815299987793s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.020430803298950195s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 8.177757263183594e-05s
Believability | Calculation of trust value for CLLD-SAILS took 8.344650268554688e-06s
INFO | --- Analysis for clld-sails took 3.6517221927642822s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.291534423828125e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.26793599128723145s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.02057361602783203s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.559226989746094e-05s
Believability | Calculation of trust value for CLLD-WALS took 6.67572021484375e-06s
INFO | --- Analysis for clld-wals took 3.5206449031829834s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.410743713378906e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.2690420150756836s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.020702123641967773s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 8.0108642578125e-05s
Believability | Calculation of trust value for CLLD-WOLD took 1.239776611328125e-05s
INFO | --- Analysis for clld-wold took 3.5489249229431152s
Availability | SPARQL endpoint availability check for COD inventory took 8.320808410644531e-05s
Availability | VoID file availability check for COD inventory took 0.0003337860107421875s
Completeness | Calculation of interlinking completeness for COD inventory took 0.28392767906188965s
Reputation | Calculation of the PageRank for COD inventory took 0.020586490631103516s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for COD inventory took 3.409385681152344e-05s
Believability | Calculation of trust value for COD inventory took 1.3589859008789062e-05s
INFO | --- Analysis for cod-inventory took 2.9293429851531982s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.1833808422088623s
Availability | VoID file availability check for Cooperation Databank took 0.00020837783813476562s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.26624369621276855s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.020349979400634766s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.8623809814453125e-05s
Believability | Calculation of trust value for Cooperation Databank took 8.344650268554688e-06s
INFO | --- Analysis for CoDa took 2.588456392288208s
Availability | SPARQL endpoint availability check for CODE Endpoint took 4.267692565917969e-05s
Availability | VoID file availability check for CODE Endpoint took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.2550342082977295s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.020665407180786133s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 3.361701965332031e-05s
Believability | Calculation of trust value for CODE Endpoint took 7.152557373046875e-06s
INFO | --- Analysis for code-endpoint took 3.125814437866211s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 0.4919772148132324s
Availability | VoID file availability check for OpenUpLabs COINS took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.27866101264953613s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.266334533691406e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 5.245208740234375e-06s
INFO | --- Analysis for coins-openuplabs took 3.03332781791687s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 2.9563820362091064s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.28640151023864746s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.02053093910217285s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.559226989746094e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 1.0251998901367188e-05s
INFO | --- Analysis for CoLChina_sp2000 took 6.8066582679748535s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.056539297103881836s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0004353523254394531s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.2677474021911621s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 4.00543212890625e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for colinda took 2.5700230598449707s
Availability | SPARQL endpoint availability check for CN  2012 took 27.061575651168823s
Availability | VoID file availability check for CN  2012 took 0.0008702278137207031s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.28192949295043945s
Reputation | Calculation of the PageRank for CN  2012 took 0.020444631576538086s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 3.981590270996094e-05s
Believability | Calculation of trust value for CN  2012 took 5.7220458984375e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 126.04353523254395s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 4.00543212890625e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.0002205371856689453s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.26389122009277344s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.020101308822631836s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 3.170967102050781e-05s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 7.152557373046875e-06s
INFO | --- Analysis for comments-on-literature-in-literature took 3.2890288829803467s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 4.076957702636719e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.2790851593017578s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.020270347595214844s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 3.123283386230469e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 7.152557373046875e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 2.99660062789917s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 4.029273986816406e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.00022125244140625s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.2616391181945801s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.02017521858215332s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 3.24249267578125e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 6.9141387939453125e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 2.948237657546997s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 4.2438507080078125e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.00021982192993164062s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.2795722484588623s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.020366430282592773s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 2.9087066650390625e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 7.152557373046875e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 2.863356828689575s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 5.91278076171875e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.00020813941955566406s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.27941274642944336s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.02011394500732422s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 2.9325485229492188e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 7.62939453125e-06s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 2.85530686378479s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.37408018112182617s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.29288792610168457s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.02028036117553711s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 3.743171691894531e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for CompHistSem took 3.704251289367676s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 2.1772212982177734s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.27892303466796875s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.020084619522094727s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.4809112548828125e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 8.106231689453125e-06s
INFO | --- Analysis for comsode-d3-2 took 8.251155614852905s
Availability | SPARQL endpoint availability check for ConceptNet took 3.9577484130859375e-05s
Availability | VoID file availability check for ConceptNet took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.2791099548339844s
Reputation | Calculation of the PageRank for ConceptNet took 0.020147085189819336s
Interlinking | Calculation of Degree of Connection for ConceptNet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ConceptNet took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 2.7894973754882812e-05s
Believability | Calculation of trust value for ConceptNet took 7.867813110351562e-06s
INFO | --- Analysis for conceptnet took 2.9763498306274414s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 4.220008850097656e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.264024019241333s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.020051240921020508s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.535385131835938e-05s
Believability | Calculation of trust value for 2011 US Congress People took 5.4836273193359375e-06s
INFO | --- Analysis for congresspeople took 3.0419890880584717s
Availability | SPARQL endpoint availability check for MIMO took 0.23967742919921875s
Availability | VoID file availability check for MIMO took 0.0006945133209228516s
Completeness | Calculation of interlinking completeness for MIMO took 0.25209975242614746s
Reputation | Calculation of the PageRank for MIMO took 0.02010631561279297s
Interlinking | Calculation of Degree of Connection for MIMO took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.0967254638671875e-05s
Believability | Calculation of trust value for MIMO took 7.867813110351562e-06s
INFO | --- Analysis for CONNECTED took 3.624948501586914s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 4.1484832763671875e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.2699458599090576s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.02003312110900879s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 3.0517578125e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 6.198883056640625e-06s
INFO | --- Analysis for connectivity-of-lod-datasets took 2.9248366355895996s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 4.029273986816406e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.2559695243835449s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.020344018936157227s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 3.9577484130859375e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.1205673217773438e-05s
INFO | --- Analysis for copac-library-catalogue took 2.9013843536376953s
Availability | SPARQL endpoint availability check for Copyright Free Music took 4.9114227294921875e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.2604389190673828s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.020131349563598633s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 2.8848648071289062e-05s
Believability | Calculation of trust value for Copyright Free Music took 6.9141387939453125e-06s
INFO | --- Analysis for Copyright_Free_Music took 3.5670599937438965s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 4.1484832763671875e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.25423550605773926s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.020269393920898438s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 7.534027099609375e-05s
Believability | Calculation of trust value for CopyrightTermBank took 7.62939453125e-06s
INFO | --- Analysis for copyrighttermbank took 34.02938675880432s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 2.115910768508911s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.28162217140197754s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020250558853149414s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.719329833984375e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 6.198883056640625e-06s
INFO | --- Analysis for core took 6.8780176639556885s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 392.5732271671295s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 0.27793073654174805s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.020544052124023438s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 8.869171142578125e-05s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 6.67572021484375e-06s
INFO | --- Analysis for Corine_linked_dataset took 667.5345873832703s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 4.100799560546875e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0002887248992919922s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.2686958312988281s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.02065134048461914s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 3.0279159545898438e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.1682510375976562e-05s
INFO | --- Analysis for corn took 3.870933771133423s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 5.435943603515625e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.000213623046875s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.25621652603149414s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.020076751708984375s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 2.9087066650390625e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 6.198883056640625e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 3.4978747367858887s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 4.0531158447265625e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.00021266937255859375s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.2568790912628174s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0203702449798584s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 2.7179718017578125e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 5.7220458984375e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 2.977133274078369s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 4.220008850097656e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.24657893180847168s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.020104408264160156s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 7.009506225585938e-05s
Believability | Calculation of trust value for Cornetto1.2 took 6.9141387939453125e-06s
INFO | --- Analysis for cornetto took 13.551315307617188s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.2795565128326416s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.00044465065002441406s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 66.67996072769165s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.6490206718444824s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 0.6811587810516357s
Interoperability | New terms check for Corporate Body Named Authority List  took 13.05362844467163s
Versatility | Languages check for Corporate Body Named Authority List  took 300.105180978775s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 2.4231042861938477s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.36081933975219727s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 1.0024197101593018s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 2.4478759765625s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.26165223121643066s
License | MR license check for Corporate Body Named Authority List  took 0.16338419914245605s
License | HR license check for Corporate Body Named Authority List  took 300.09515380859375s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.19590163230895996s
Understandability | Number of label check for Corporate Body Named Authority List  took 1.3038139343261719s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.2512638568878174s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.1144711971282959s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.27564525604248047s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.1925029754638672s
Performance | Throughput check for Corporate Body Named Authority List  took 10.5919508934021s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 7.128715515136719e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.181121826171875s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 1.0423839092254639s
Interlinking | skos check for Corporate Body Named Authority List  took 0.23764276504516602s
Interlinking | skos check for Corporate Body Named Authority List  took 0.12085771560668945s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.2669517993927002s
Currency | Creation date check for Corporate Body Named Authority List  took 0.4955110549926758s
Currency | Modification date check for Corporate Body Named Authority List  took 0.19682979583740234s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 95.18014240264893s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.16326379776000977s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.1495685577392578s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.1043539047241211s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 19.13775134086609s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.0365288257598877s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.6638331413269043s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.21685361862182617s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 53.39866232872009s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.370859146118164s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 18.03796124458313s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.6411993503570557s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 54.28752875328064s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 2.957615375518799s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.3791232109069824s
Security | Sign check for Corporate Body Named Authority List  took 0.11864542961120605s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 10.686142206192017s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 1.0927860736846924s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 4.839897155761719e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 1.430511474609375e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 5.4836273193359375e-06s
INFO | --- Analysis for corporate-body took 13664.263777256012s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.4975125789642334s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.2773258686065674s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.020354747772216797s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 3.647804260253906e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 5.7220458984375e-06s
INFO | --- Analysis for CorpusFibonacci took 5.362572193145752s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 4.076957702636719e-05s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.00022530555725097656s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.28136539459228516s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.020258188247680664s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 2.9087066650390625e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 6.67572021484375e-06s
INFO | --- Analysis for corscheck took 3.055321455001831s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.1540086269378662s
Availability | VoID file availability check for Country Name Authority List took 0.0007205009460449219s
Extra | Recovery of all triples for Country Name Authority List took 64.36280941963196s
Performance | Total latancy measurement for Country Name Authority List took 0.6197023391723633s
Amount of data | Number of triples check for Country Name Authority List took 0.654202938079834s
Interoperability | New terms check for Country Name Authority List took 13.682040452957153s
Versatility | Languages check for Country Name Authority List took 300.03588938713074s
Interpretability | Number of blank nodes check for Country Name Authority List took 2.6470134258270264s
Security | Check HTTPS for Country Name Authority List took 0.28575944900512695s
Interpretability | RDF structures check for Country Name Authority List took 1.0065255165100098s
Versatility | Serialization formats check for Country Name Authority List took 3.0507731437683105s
Availability | RDF dump link check for Country Name Authority List took 0.21123743057250977s
License | MR license check for Country Name Authority List took 0.18752217292785645s
License | HR license check for Country Name Authority List took 300.1022665500641s
Amount of data | Number of property check for Country Name Authority List took 0.18367791175842285s
Understandability | Number of label check for Country Name Authority List took 0.8277809619903564s
Understandability | URI regex check for Country Name Authority List took 0.22209835052490234s
Understandability | Vocabs check for Country Name Authority List took 0.12395954132080078s
Verifiability | Authors check for Country Name Authority List took 0.11084580421447754s
Verifiability | Publishers check for Country Name Authority List took 0.19356799125671387s
Performance | Throughput check for Country Name Authority List took 10.665505647659302s
Amount of data | Check the number of entities for Country Name Authority List took 6.651878356933594e-05s
Verifiability | Contribs. check for Country Name Authority List took 0.2738773822784424s
Interlinking | sameAs chians check for Country Name Authority List took 1.3606946468353271s
Interlinking | skos check for Country Name Authority List took 0.3387727737426758s
Interlinking | skos check for Country Name Authority List took 0.18949103355407715s
Timeliness | dataset update frequency check for Country Name Authority List took 0.33542871475219727s
Currency | Creation date check for Country Name Authority List took 0.563190221786499s
Currency | Modification date check for Country Name Authority List took 0.1743783950805664s
Rep.Conc. | URIs length for Country Name Authority List took 97.2846930027008s
Interoperability | New vocabularies check for Country Name Authority List took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.14395737648010254s
Accuracy | Check Functional Property for Country Name Authority List took 0.17937850952148438s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.18366789817810059s
Accuracy | Check Empty annotation labels for Country Name Authority List took 33.06291341781616s
Accuracy | Check White space in annotation for Country Name Authority List took 3.135828733444214s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.6186089515686035s
Consistency | Disjoint class check for Country Name Authority List took 0.18671751022338867s
Consistency | Check Misplaced properties for Country Name Authority List took 55.156436920166016s
Consistency | Misplaced classes for Country Name Authority List took 8.44233751296997s
Consistency | Check Ontology hijacking for Country Name Authority List took 46.360515832901s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.7493877410888672s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 56.07929801940918s
Conciseness | Check Extensional conciseness for Country Name Authority List took 2.98824143409729s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.5783481597900391s
Security | Sign check for Country Name Authority List took 0.10217738151550293s
Availability | Check URIs Dereferenciability for Country Name Authority List took 9.32226848602295s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 1.1786468029022217s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.020549774169921875s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 6.222724914550781e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 1.9073486328125e-06s
Believability | Calculation of trust value for Country Name Authority List took 7.152557373046875e-06s
INFO | --- Analysis for country-authority-list took 14128.157032728195s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.08439517021179199s
Availability | VoID file availability check for Courts thesaurus took 0.000457763671875s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.6888318061828613s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.020923852920532227s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 3.600120544433594e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 7.081031799316406e-05s
Believability | Calculation of trust value for Courts thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for courts-thesaurus took 3.9253768920898438s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 0.645108699798584s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0007166862487792969s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.2900686264038086s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.021316051483154297s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 8.797645568847656e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 1.6689300537109375e-05s
INFO | --- Analysis for Covid-on-the-Web took 6.328111410140991s
Availability | SPARQL endpoint availability check for CPA 2008 took 25.78193163871765s
Availability | VoID file availability check for CPA 2008 took 0.0008225440979003906s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.30495309829711914s
Reputation | Calculation of the PageRank for CPA 2008 took 0.02044200897216797s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 4.291534423828125e-05s
Believability | Calculation of trust value for CPA 2008 took 5.245208740234375e-06s
INFO | --- Analysis for cpa-2008 took 124.92782306671143s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.39852213859558105s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0005693435668945312s
Extra | Recovery of all triples for Cooperative Patent Classification took 53.43484902381897s
Performance | Total latancy measurement for Cooperative Patent Classification took 0.9800231456756592s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.15229606628418s
Versatility | Languages check for Cooperative Patent Classification took 120.09532523155212s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.19264650344849s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.27873659133911133s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.2288064956665039s
Availability | RDF dump link check for Cooperative Patent Classification took 0.2061469554901123s
License | MR license check for Cooperative Patent Classification took 0.2563021183013916s
License | HR license check for Cooperative Patent Classification took 90.22538352012634s
Amount of data | Number of property check for Cooperative Patent Classification took 0.18604421615600586s
Understandability | Number of label check for Cooperative Patent Classification took 90.20436954498291s
Understandability | URI regex check for Cooperative Patent Classification took 0.4164254665374756s
Understandability | Vocabs check for Cooperative Patent Classification took 0.23100972175598145s
Verifiability | Authors check for Cooperative Patent Classification took 0.2404651641845703s
Verifiability | Publishers check for Cooperative Patent Classification took 0.21129822731018066s
Performance | Throughput check for Cooperative Patent Classification took 10.758847951889038s
Amount of data | Check the number of entities for Cooperative Patent Classification took 3.266334533691406e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.20201849937438965s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.20324325561523438s
Interlinking | skos check for Cooperative Patent Classification took 0.1926717758178711s
Interlinking | skos check for Cooperative Patent Classification took 0.20636534690856934s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.17539286613464355s
Currency | Creation date check for Cooperative Patent Classification took 0.3329200744628906s
Currency | Modification date check for Cooperative Patent Classification took 0.4912223815917969s
Rep.Conc. | URIs length for Cooperative Patent Classification took 156.07473349571228s
Interoperability | New vocabularies check for Cooperative Patent Classification took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.24131298065185547s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 18.021586894989014s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.982182741165161s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.909348964691162s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.15070271492004395s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 120.25928616523743s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 24.55159068107605s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.7530903816223145s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 121.5920181274414s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.8116300106048584s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.30333805084228516s
Security | Sign check for Cooperative Patent Classification took 0.19405627250671387s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 1.3301808834075928s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.9108352661132812s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.020714282989501953s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 3.886222839355469e-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.71661376953125e-05s
INFO | --- Analysis for CPC took 1324.2095866203308s
Availability | SPARQL endpoint availability check for CPC 2008 took 25.76825785636902s
Availability | VoID file availability check for CPC 2008 took 0.0008080005645751953s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.2616887092590332s
Reputation | Calculation of the PageRank for CPC 2008 took 0.020546913146972656s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 4.673004150390625e-05s
Believability | Calculation of trust value for CPC 2008 took 5.0067901611328125e-06s
INFO | --- Analysis for cpc-2008 took 126.51715540885925s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.4238121509552s
Availability | VoID file availability check for CPV  2003 took 0.0007417201995849609s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.8571896553039551s
Reputation | Calculation of the PageRank for CPV  2003 took 0.02093672752380371s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 3.552436828613281e-05s
Believability | Calculation of trust value for CPV  2003 took 5.245208740234375e-06s
INFO | --- Analysis for cpv-2003 took 115.77590608596802s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.30361771583557s
Availability | VoID file availability check for CPV 2008 took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.27373385429382324s
Reputation | Calculation of the PageRank for CPV 2008 took 0.021079540252685547s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 5.125999450683594e-05s
Believability | Calculation of trust value for CPV 2008 took 4.76837158203125e-06s
INFO | --- Analysis for cpv-2008 took 125.11844563484192s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 260.6223871707916s
Availability | VoID file availability check for crowdsourcing-fb took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.27089905738830566s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.02053689956665039s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.220008850097656e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 6.67572021484375e-06s
INFO | --- Analysis for crowdsourcing-fb took 535.5671350955963s
Availability | SPARQL endpoint availability check for CRTM took 4.029273986816406e-05s
Availability | VoID file availability check for CRTM took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for CRTM took 0.27769970893859863s
Reputation | Calculation of the PageRank for CRTM took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for CRTM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CRTM took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for CRTM took 2.765655517578125e-05s
Believability | Calculation of trust value for CRTM took 6.67572021484375e-06s
INFO | --- Analysis for crtm took 3.5496466159820557s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 3.981590270996094e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.2489004135131836s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.020310640335083008s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 2.8848648071289062e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 1.239776611328125e-05s
INFO | --- Analysis for crystal-eye took 2.9271528720855713s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.852046966552734s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0006647109985351562s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.3064577579498291s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 4.696846008300781e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 4.76837158203125e-06s
INFO | --- Analysis for ctic-public-dataset took 44.072312355041504s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 4.124641418457031e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.27452969551086426s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.02029252052307129s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 2.8371810913085938e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 6.9141387939453125e-06s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 2.9916791915893555s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 10.590805768966675s
Availability | VoID file availability check for CulturaLinkedData took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.2474665641784668s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.020209074020385742s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 2.7894973754882812e-05s
Believability | Calculation of trust value for CulturaLinkedData took 6.9141387939453125e-06s
INFO | --- Analysis for culturalinkeddata took 30.518099308013916s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.22544121742248535s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.2803816795349121s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007441043853759766s
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 4.76837158203125e-06s
INFO | --- Analysis for cz-ares-or took 3.0020546913146973s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.10929036140441895s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.2834815979003906s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.020432710647583008s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.504753112792969e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 4.76837158203125e-06s
INFO | --- Analysis for cz-ares-rzp took 2.8157339096069336s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.1130983829498291s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.2935605049133301s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.0204012393951416s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.24249267578125e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 4.291534423828125e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 2.9609835147857666s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.10889458656311035s
Availability | VoID file availability check for Integrated pollution registry took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.2632608413696289s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.600120544433594e-05s
Believability | Calculation of trust value for Integrated pollution registry took 4.5299530029296875e-06s
INFO | --- Analysis for cz-cenia-pollution took 2.8884904384613037s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.11539530754089355s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.00035691261291503906s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.23197126388549805s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.02037787437438965s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.910064697265625e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 5.7220458984375e-06s
INFO | --- Analysis for cz-contracts took 2.7176830768585205s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 4.029273986816406e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.24789142608642578s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.02042865753173828s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 2.9802322387695312e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 7.152557373046875e-06s
INFO | --- Analysis for cz-courts took 2.909027099609375s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.11275458335876465s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.2835502624511719s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.02029561996459961s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.266334533691406e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 4.76837158203125e-06s
INFO | --- Analysis for cz-ctia-bans took 4.994871377944946s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.1095438003540039s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.291367769241333s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020270109176635742s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0008041858673095703s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.5762786865234375e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 5.245208740234375e-06s
INFO | --- Analysis for cz-ctia-confiscations took 2.808140277862549s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.11539840698242188s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.2851533889770508s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.020888328552246094s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0008544921875s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.7670135498046875e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 4.5299530029296875e-06s
INFO | --- Analysis for cz-ctia-focus took 2.788017511367798s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.12158918380737305s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.001016855239868164s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.2884349822998047s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020546674728393555s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.172325134277344e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ctia-inspections took 2.860661745071411s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.11850786209106445s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.2877998352050781s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.020804643630981445s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0008161067962646484s
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 cz-ctia-sanctions took 4.781761646270752s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.2027115821838379s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0007746219635009766s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.26497554779052734s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.0208127498626709s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 3.647804260253906e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 4.76837158203125e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 2.8924407958984375s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.11440539360046387s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.28637003898620605s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.02047133445739746s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.24249267578125e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 4.76837158203125e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 2.89115834236145s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.8009824752807617s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.2624235153198242s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.02060103416442871s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.7670135498046875e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-average-salaries took 3.672560691833496s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.4500117301940918s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0007092952728271484s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.2527174949645996s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.020464181900024414s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 3.9577484130859375e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.4011998176574707s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.41168832778930664s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.25577855110168457s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.021057844161987305s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.001018524169921875s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.506111145019531e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.76837158203125e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.3167831897735596s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.45583224296569824s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.2693054676055908s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.020333528518676758s
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.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 3.719329833984375e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-job-applicants took 3.360168218612671s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.449688196182251s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.26859140396118164s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.020369291305541992s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.647804260253906e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.4925620555877686s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.37164855003356934s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007748603820800781s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.2572593688964844s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.020354270935058594s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.504753112792969e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-regions took 3.075882911682129s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.3873586654663086s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.2675588130950928s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.021159887313842773s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0009849071502685547s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 4.9114227294921875e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.3421151638031006s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.41879725456237793s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.3318672180175781s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.02052593231201172s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 4.744529724121094e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 3.5382494926452637s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.43208932876586914s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.2887003421783447s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.02044200897216797s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.981590270996094e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 5.9604644775390625e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 3.3204104900360107s
Availability | SPARQL endpoint availability check for ATC groups took 0.13374662399291992s
Availability | VoID file availability check for ATC groups took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for ATC groups took 0.27962565422058105s
Reputation | Calculation of the PageRank for ATC groups took 0.020308256149291992s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for ATC groups took 7.009506225585938e-05s
Believability | Calculation of trust value for ATC groups took 6.67572021484375e-06s
INFO | --- Analysis for cz-eh-1-atc took 2.8560168743133545s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.11232733726501465s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.2917044162750244s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.020595073699951172s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.528594970703125e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 5.245208740234375e-06s
INFO | --- Analysis for cz-fulfillments took 2.819047212600708s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.04306387901306152s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.4090726375579834s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.020704269409179688s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0008814334869384766s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 5.245208740234375e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 5.7220458984375e-06s
INFO | --- Analysis for cz-ic took 3.343233346939087s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.1622471809387207s
Availability | VoID file availability check for List of Czech data boxes took 0.0005764961242675781s
Extra | Recovery of all triples for List of Czech data boxes took 299.6351544857025s
Performance | Total latancy measurement for List of Czech data boxes took 0.5787990093231201s
Amount of data | Number of triples check for List of Czech data boxes took 94.35706782341003s
Interoperability | New terms check for List of Czech data boxes took 21.43589973449707s
Versatility | Languages check for List of Czech data boxes took 300.1793999671936s
Interpretability | Number of blank nodes check for List of Czech data boxes took 3.013861894607544s
Interpretability | RDF structures check for List of Czech data boxes took 0.4428691864013672s
Versatility | Serialization formats check for List of Czech data boxes took 0.6880285739898682s
Availability | RDF dump link check for List of Czech data boxes took 16.363673210144043s
License | MR license check for List of Czech data boxes took 0.5450892448425293s
License | HR license check for List of Czech data boxes took 300.178186416626s
Amount of data | Number of property check for List of Czech data boxes took 0.281541109085083s
Understandability | Number of label check for List of Czech data boxes took 4.018675804138184s
Understandability | URI regex check for List of Czech data boxes took 0.636981725692749s
Understandability | Vocabs check for List of Czech data boxes took 0.3348524570465088s
Verifiability | Authors check for List of Czech data boxes took 0.29172468185424805s
Verifiability | Publishers check for List of Czech data boxes took 0.13690924644470215s
Performance | Throughput check for List of Czech data boxes took 10.59904408454895s
Amount of data | Check the number of entities for List of Czech data boxes took 2.9927217960357666s
Verifiability | Contribs. check for List of Czech data boxes took 0.2733800411224365s
Interlinking | sameAs chians check for List of Czech data boxes took 0.5956833362579346s
Interlinking | skos check for List of Czech data boxes took 0.24607563018798828s
Interlinking | skos check for List of Czech data boxes took 0.1242971420288086s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.2843818664550781s
Currency | Creation date check for List of Czech data boxes took 0.8774352073669434s
Currency | Modification date check for List of Czech data boxes took 0.3183307647705078s
Rep.Conc. | URIs length for List of Czech data boxes took 277.1924593448639s
Interoperability | New vocabularies check for List of Czech data boxes took 20.353451251983643s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.7288484573364258s
Accuracy | Check Functional Property for List of Czech data boxes took 0.20703649520874023s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.15593314170837402s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 122.5606460571289s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.0345780849456787s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.5585134029388428s
Consistency | Disjoint class check for List of Czech data boxes took 0.21576833724975586s
Consistency | Check Misplaced properties for List of Czech data boxes took 133.94864869117737s
Consistency | Misplaced classes for List of Czech data boxes took 7.884189128875732s
Consistency | Check Ontology hijacking for List of Czech data boxes took 86.91586375236511s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.4134161472320557s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 124.82574033737183s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.6226277351379395s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 1.3040049076080322s
Security | Sign check for List of Czech data boxes took 0.13299012184143066s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 13.97581434249878s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 1.137098789215088s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.021099090576171875s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 3.5762786865234375e-05s
Interoperability | Check the re-using of existing vocabs for List of Czech data boxes took 15.183520555496216s
Believability | Calculation of trust value for List of Czech data boxes took 5.245208740234375e-06s
INFO | --- Analysis for cz-list-of-databoxes took 2609.9493000507355s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12421679496765137s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0005867481231689453s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 305.11591124534607s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5254778861999512s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 18.035681009292603s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 25.141289949417114s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.0798273086548s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.8612565994262695s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3591578006744385s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.580670356750488s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 15.264473676681519s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11373043060302734s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.1779217720032s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3383760452270508s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.635637521743774s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.49716615676879883s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.14394116401672363s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2956383228302002s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.17681598663330078s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.520127296447754s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.119295358657837s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6725766658782959s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.8649117946624756s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.18478941917419434s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11364173889160156s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.27487826347351074s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.0315537452697754s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.33173298835754395s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 279.62891149520874s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 16.2104811668396s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5097537040710449s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11177825927734375s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1242680549621582s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 122.25951647758484s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.035639762878418s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.5980842113494873s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11449432373046875s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 145.59993267059326s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.950201511383057s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 83.21551847457886s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.4306814670562744s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 132.23748207092285s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.674426317214966s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.8503382205963135s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.144026517868042s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 13.132869005203247s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.0355894565582275s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.020850658416748047s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.504753112792969e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 13.958820343017578s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.298324584960938e-06s
INFO | --- Analysis for cz-nace took 2594.698675632477s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3292360305786133s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0006911754608154297s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 221.56096768379211s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8548202514648438s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2553572654724121s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.5478835105895996s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 25.381858825683594s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5042085647583008s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16143083572387695s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 4.690211534500122s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.28697776794433594s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4076058864593506s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.7337985038757324s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.18176531791687012s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.7872400283813477s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.36560654640197754s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2028331756591797s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.19083118438720703s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2607088088989258s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.2 took 7.963180541992188e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.15488481521606445s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.20615005493164062s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3365178108215332s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17403936386108398s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8624184131622314s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3845822811126709s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3275632858276367s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.2 took 24.915999174118042s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.19420099258422852s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1562652587890625s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1680455207824707s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.2 took 15.410258769989014s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.3862695693969727s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.6514222621917725s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1913144588470459s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8518421649932861s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.204403162002563s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.2 took 14.867924690246582s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.6335859298706055s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.4804928302764893s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.4587042331695557s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.20421218872070312s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4152851104736328s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.2 took 1033.0881764888763s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.6500623226165771s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.02281498908996582s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.910064697265625e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.2 took 4.5299530029296875e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 5.9604644775390625e-06s
INFO | --- Analysis for cz-nkod took 34315.91193842888s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.2141566276550293s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0008609294891357422s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.2626330852508545s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.020303964614868164s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.600120544433594e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 6.198883056640625e-06s
INFO | --- Analysis for cz-orders took 3.2754430770874023s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.19271326065063477s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0006101131439208984s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 232.2250039577484s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.537189245223999s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 36.18726396560669s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 21.191590309143066s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.17648816108704s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 3.1676340103149414s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.1815636157989502s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 2.31400728225708s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 14.691327571868896s
License | MR license check for Institutions of public power of the Czech Republic took 0.37138795852661133s
License | HR license check for Institutions of public power of the Czech Republic took 242.40896844863892s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.15390992164611816s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 5.768038511276245s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.44158339500427246s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.12212443351745605s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.2309565544128418s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.1365213394165039s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.543231010437012s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.06657075881958s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.47471189498901367s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.7093949317932129s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.18763232231140137s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.11238932609558105s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.3079512119293213s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.8775017261505127s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.17528581619262695s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 225.74566531181335s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 25.36553430557251s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.43115878105163574s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.12313556671142578s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.17684626579284668s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 66.40394878387451s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.0408871173858643s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.596217155456543s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.13638591766357422s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 133.90208959579468s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 7.780097484588623s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 49.69824838638306s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.2690598964691162s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 124.46593952178955s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.6444671154022217s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.7970726490020752s
Security | Sign check for Institutions of public power of the Czech Republic took 0.16456365585327148s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 16.286160230636597s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 1.0869636535644531s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.02134847640991211s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 5.364418029785156e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 28.881557941436768s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-ovm took 2281.791389942169s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.11221861839294434s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.2523372173309326s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.020550012588500977s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.337860107421875e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-ovm-agendas took 3.1757125854492188s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.22842717170715332s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0005691051483154297s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.7783908843994141s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.02099609375s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.747245788574219e-05s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-ruian took 5.373377799987793s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.708733081817627s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.2823212146759033s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.02039313316345215s
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.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.534027099609375e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 4.231323003768921s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.48775434494018555s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.28138041496276855s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.02032470703125s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.695487976074219e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-sao-check-actions took 3.6105358600616455s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.4927093982696533s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.7041323184967041s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.0517578125e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 9.775161743164062e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 4.044705867767334s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.10831594467163086s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.2543010711669922s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.020911216735839844s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0008094310760498047s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.838539123535156e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 7.3909759521484375e-06s
INFO | --- Analysis for cz-sidc-drug-ingredients took 2.727936267852783s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.10436606407165527s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007784366607666016s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.2691802978515625s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.020027637481689453s
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.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.504753112792969e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 2.7712459564208984s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.11231184005737305s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.25501132011413574s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.02074885368347168s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.719329833984375e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 8.344650268554688e-06s
INFO | --- Analysis for cz-sidc-drugs took 2.753695249557495s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.11583304405212402s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0005507469177246094s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 237.27814412117004s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.5572218894958496s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 18.029428482055664s
Interoperability | New terms check for Summary types of Czech institutions of public power took 23.053239107131958s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.10820293426514s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 2.1386618614196777s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.10737919807434082s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 2.0129315853118896s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 14.826728105545044s
License | MR license check for Summary types of Czech institutions of public power took 0.12101221084594727s
License | HR license check for Summary types of Czech institutions of public power took 296.3666191101074s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.148667573928833s
Understandability | Number of label check for Summary types of Czech institutions of public power took 7.089125633239746s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.2640805244445801s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.11621475219726562s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.3461573123931885s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.16572904586791992s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.449881076812744s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.069336414337158s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.342602014541626s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 1.2296652793884277s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.21744012832641602s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.11330842971801758s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.18740439414978027s
Currency | Creation date check for Summary types of Czech institutions of public power took 1.0662784576416016s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.2079789638519287s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 229.71578192710876s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 22.8004093170166s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.43242526054382324s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.11756396293640137s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.11291265487670898s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 78.23215675354004s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.031442642211914s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.7908546924591064s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.11316537857055664s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 132.85735821723938s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 7.999337434768677s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 48.56448841094971s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.2365152835845947s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 133.8704218864441s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.6691293716430664s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.9192423820495605s
Security | Sign check for Summary types of Czech institutions of public power took 0.11101007461547852s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 14.735949039459229s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 1.1191027164459229s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.02123403549194336s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.000957489013671875s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 6.151199340820312e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 22.674329042434692s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 5.7220458984375e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 2375.262291908264s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.10164833068847656s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.26763153076171875s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.02044534683227539s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.314018249511719e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 5.0067901611328125e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 4.91058087348938s
Availability | SPARQL endpoint availability check for State funding providers took 0.1067037582397461s
Availability | VoID file availability check for State funding providers took 0.00040078163146972656s
Completeness | Calculation of interlinking completeness for State funding providers took 0.2583580017089844s
Reputation | Calculation of the PageRank for State funding providers took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for State funding providers took 3.933906555175781e-05s
Believability | Calculation of trust value for State funding providers took 4.0531158447265625e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 3.582098960876465s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.10500168800354004s
Availability | VoID file availability check for Organizations active in R&D took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.22837495803833008s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.020550966262817383s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 4.029273986816406e-05s
Believability | Calculation of trust value for Organizations active in R&D took 5.7220458984375e-06s
INFO | --- Analysis for cz-vavai-organizations took 2.8795433044433594s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.10698294639587402s
Availability | VoID file availability check for R&D Programmes took 0.0004150867462158203s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.2565934658050537s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020358562469482422s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.0531158447265625e-05s
Believability | Calculation of trust value for R&D Programmes took 4.76837158203125e-06s
INFO | --- Analysis for cz-vavai-programmes took 2.669915199279785s
Availability | SPARQL endpoint availability check for R&D Projects took 0.1069488525390625s
Availability | VoID file availability check for R&D Projects took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.24399566650390625s
Reputation | Calculation of the PageRank for R&D Projects took 0.020328283309936523s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.4345855712890625e-05s
Believability | Calculation of trust value for R&D Projects took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-projects took 2.7471067905426025s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.11469888687133789s
Availability | VoID file availability check for Institutional research plans took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.25203871726989746s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020499467849731445s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.172325134277344e-05s
Believability | Calculation of trust value for Institutional research plans took 5.7220458984375e-06s
INFO | --- Analysis for cz-vavai-research-plans took 2.8068885803222656s
Availability | SPARQL endpoint availability check for Results of R&D took 0.11412787437438965s
Availability | VoID file availability check for Results of R&D took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.26818275451660156s
Reputation | Calculation of the PageRank for Results of R&D took 0.020517826080322266s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 3.910064697265625e-05s
Believability | Calculation of trust value for Results of R&D took 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-results took 2.7792396545410156s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.10233879089355469s
Availability | VoID file availability check for Tenders in R&D took 0.0005898475646972656s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.2653846740722656s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.0204775333404541s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.1484832763671875e-05s
Believability | Calculation of trust value for Tenders in R&D took 7.62939453125e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.6934287548065186s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 4.458427429199219e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.00029754638671875s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.24341726303100586s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.0202484130859375s
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.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.361701965332031e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 6.198883056640625e-06s
INFO | --- Analysis for czech_addresses took 4.691915988922119s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.6071872711181641s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0003228187561035156s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.2690246105194092s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.0206606388092041s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.981590270996094e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for DanteLatinLoanwords took 4.040389537811279s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.38422107696533203s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0006184577941894531s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 131.55306673049927s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.0512323379516602s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 6.4998695850372314s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 3.077908515930176s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.28074669837952s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.22185206413269043s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.12209296226501465s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.7282145023345947s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.6018340587615967s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.22304844856262207s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.23929119110107422s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 76.51079750061035s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.22722482681274414s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 1.1739857196807861s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.4487755298614502s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.22638869285583496s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.2648799419403076s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.22802138328552246s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.36783504486084s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 9.799003601074219e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.22298121452331543s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.344313383102417s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 1.266420841217041s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.22124505043029785s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.2071526050567627s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 1.1477394104003906s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 1.3728811740875244s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 84.51372218132019s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.21534276008605957s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.8332686424255371s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.39497995376586914s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 46.85149574279785s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.1990966796875s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.660626173019409s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 1.1892385482788086s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 20.207017183303833s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.584372997283936s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 54.77086114883423s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.4947257041931152s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 21.583540439605713s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.8448750972747803s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.23422527313232422s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.22624516487121582s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 12.690592050552368s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.8374791145324707s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.020905733108520508s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.0001513957977294922s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 2.1457672119140625e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 9.298324584960938e-06s
INFO | --- Analysis for data-bnf-fr took 747.0704724788666s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.12971258163452148s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0005784034729003906s
Extra | Recovery of all triples for Open Data from the Italian National Research Council took 0.6266345977783203s
Performance | Total latancy measurement for Open Data from the Italian National Research Council took 0.30524587631225586s
Amount of data | Number of triples check for Open Data from the Italian National Research Council took 5.8677825927734375s
Interoperability | New terms check for Open Data from the Italian National Research Council took 2.158661127090454s
Versatility | Languages check for Open Data from the Italian National Research Council took 0.07795858383178711s
Interpretability | Number of blank nodes check for Open Data from the Italian National Research Council took 0.819446325302124s
Security | Check HTTPS for Open Data from the Italian National Research Council took 0.03795576095581055s
Interpretability | RDF structures check for Open Data from the Italian National Research Council took 0.10221266746520996s
Versatility | Serialization formats check for Open Data from the Italian National Research Council took 0.08861732482910156s
Availability | RDF dump link check for Open Data from the Italian National Research Council took 0.08037447929382324s
License | MR license check for Open Data from the Italian National Research Council took 0.0891120433807373s
License | HR license check for Open Data from the Italian National Research Council took 11.916855335235596s
Amount of data | Number of property check for Open Data from the Italian National Research Council took 0.09673261642456055s
Understandability | Number of label check for Open Data from the Italian National Research Council took 3.8469653129577637s
Understandability | URI regex check for Open Data from the Italian National Research Council took 0.1701211929321289s
Understandability | Vocabs check for Open Data from the Italian National Research Council took 0.08390283584594727s
Verifiability | Authors check for Open Data from the Italian National Research Council took 0.0843193531036377s
Verifiability | Publishers check for Open Data from the Italian National Research Council took 0.08651185035705566s
Performance | Throughput check for Open Data from the Italian National Research Council took 10.226341485977173s
Amount of data | Check the number of entities for Open Data from the Italian National Research Council took 3.266334533691406e-05s
Verifiability | Contribs. check for Open Data from the Italian National Research Council took 0.07802653312683105s
Interlinking | sameAs chians check for Open Data from the Italian National Research Council took 0.0845954418182373s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.08002996444702148s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.051081180572509766s
Timeliness | dataset update frequency check for Open Data from the Italian National Research Council took 0.08229565620422363s
Currency | Creation date check for Open Data from the Italian National Research Council took 0.16465187072753906s
Currency | Modification date check for Open Data from the Italian National Research Council took 0.16918492317199707s
Rep.Conc. | URIs length for Open Data from the Italian National Research Council took 12.984537601470947s
Interoperability | New vocabularies check for Open Data from the Italian National Research Council took 6.700616121292114s
Consistency | Deprecated classes/propertiers check for Open Data from the Italian National Research Council took 0.08348655700683594s
Accuracy | Check Functional Property for Open Data from the Italian National Research Council took 0.07975196838378906s
Accuracy | Check Inverse Functional Property for Open Data from the Italian National Research Council took 0.08043074607849121s
Accuracy | Check Empty annotation labels for Open Data from the Italian National Research Council took 0.34737110137939453s
Accuracy | Check White space in annotation for Open Data from the Italian National Research Council took 0.03197216987609863s
Accuracy | Check Datatype consistency for Open Data from the Italian National Research Council took 0.028164148330688477s
Consistency | Disjoint class check for Open Data from the Italian National Research Council took 0.07998132705688477s
Consistency | Check Misplaced properties for Open Data from the Italian National Research Council took 10.923878908157349s
Consistency | Misplaced classes for Open Data from the Italian National Research Council took 0.20409655570983887s
Consistency | Check Ontology hijacking for Open Data from the Italian National Research Council took 1.5834946632385254s
Consistency | Check Invalid usage of undefined classes for Open Data from the Italian National Research Council took 1.2971487045288086s
Consistency | Check Invalid usage of undefined properties for Open Data from the Italian National Research Council took 11.44678020477295s
Conciseness | Check Extensional conciseness for Open Data from the Italian National Research Council took 0.03229522705078125s
Conciseness | Check Intensional conciseness for Open Data from the Italian National Research Council took 0.10439300537109375s
Security | Sign check for Open Data from the Italian National Research Council took 0.08005809783935547s
Availability | Check URIs Dereferenciability for Open Data from the Italian National Research Council took 615.7179548740387s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.8811013698577881s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.0212399959564209s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 7.557868957519531e-05s
Interoperability | Check the re-using of existing vocabs for Open Data from the Italian National Research Council took 6.37194561958313s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 5.9604644775390625e-06s
INFO | --- Analysis for data-cnr-it took 730.9320981502533s
Availability | SPARQL endpoint availability check for Data.gov took 1.6567959785461426s
Availability | VoID file availability check for Data.gov took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for Data.gov took 0.7188985347747803s
Reputation | Calculation of the PageRank for Data.gov took 0.020703554153442383s
Interlinking | Calculation of Degree of Connection for Data.gov took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Data.gov took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.0279159545898438e-05s
Believability | Calculation of trust value for Data.gov took 1.239776611328125e-05s
INFO | --- Analysis for data-gov took 20.34843373298645s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.44394826889038086s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.6944999694824219s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.0204620361328125s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 6.985664367675781e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 5.0067901611328125e-06s
INFO | --- Analysis for data-gov-ie took 3.901155948638916s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 4.172325134277344e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.2766852378845215s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.020470619201660156s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007560253143310547s
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 5.4836273193359375e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.5119731426239014s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 21.801271438598633s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0009253025054931641s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.27118921279907227s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.02070903778076172s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.0558319091796875e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 7.62939453125e-06s
INFO | --- Analysis for data-hnm-hu took 167.85551285743713s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.6954412460327148s
Availability | VoID file availability check for Climb Dataincubator took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.24782872200012207s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.020302295684814453s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 8.249282836914062e-05s
Believability | Calculation of trust value for Climb Dataincubator took 7.867813110351562e-06s
INFO | --- Analysis for data-incubator-climb took 3.931706428527832s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.4345855712890625e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0005972385406494141s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.2673463821411133s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.0199887752532959s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 8.916854858398438e-05s
Believability | Calculation of trust value for Discogs in RDF took 7.152557373046875e-06s
INFO | --- Analysis for data-incubator-discogs took 8.50859808921814s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.05849719047546387s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.28444766998291016s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.1975250244140625e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 4.291534423828125e-06s
INFO | --- Analysis for data-incubator-metoffice took 5.4242424964904785s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.06212115287780762s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0006315708160400391s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.2506096363067627s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.020313262939453125s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.559226989746094e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 1.0728836059570312e-05s
INFO | --- Analysis for data-incubator-moseley took 12.134157657623291s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.10975289344787598s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.26584911346435547s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.02028799057006836s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 8.058547973632812e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 6.4373016357421875e-06s
INFO | --- Analysis for data-incubator-musicbrainz took 2.6105217933654785s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.8053882122039795s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0006022453308105469s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.2952563762664795s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.020068645477294922s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.058547973632812e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 5.245208740234375e-06s
INFO | --- Analysis for data-incubator-nasa took 7.7889487743377686s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.06404924392700195s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.00035452842712402344s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.24822139739990234s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.020134925842285156s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.104873657226562e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 6.67572021484375e-06s
INFO | --- Analysis for data-incubator-our-airports took 2.466820240020752s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.05814814567565918s
Availability | VoID file availability check for Pokedex data in RDF took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.2784898281097412s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.020251035690307617s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.5367431640625e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 6.9141387939453125e-06s
INFO | --- Analysis for data-incubator-pokedex took 4.624751567840576s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.058806419372558594s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.2678358554840088s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.02091670036315918s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 9.512901306152344e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 7.867813110351562e-06s
INFO | --- Analysis for data-incubator-smcjournals took 2.51694655418396s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.7322432994842529s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0002675056457519531s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 14.630513668060303s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 1.3880882263183594s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 23.884976625442505s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.5208895206451416s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.29995632171631s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.311442375183105s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.2666192054748535s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.5261919498443604s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.4447510242462158s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.36282873153686523s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.48159360885620117s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.32919454574585s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 1.867974042892456s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 21.734985828399658s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 1.7611477375030518s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.7535285949707031s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.7292311191558838s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 1.1024575233459473s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 23.65719175338745s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 6.985664367675781e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.33612918853759766s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 1.354341745376587s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.49257564544677734s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.6323809623718262s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.6287317276000977s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 1.087167739868164s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.7513222694396973s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 35.10446500778198s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.4791562557220459s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.41547369956970215s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.4280378818511963s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 36.10616636276245s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 2.986778736114502s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.053182125091553s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.646228551864624s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 1.1577882766723633s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 8.035103559494019s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 25.245441198349s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.2609035968780518s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.8374309539794922s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 2.827681541442871s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.5921363830566406s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.3127298355102539s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 4.909455060958862s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.3679769039154053s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.02080988883972168s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 6.818771362304688e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 2.1457672119140625e-06s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 7.867813110351562e-06s
INFO | --- Analysis for data-open-ac-uk took 614.1231346130371s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.7924606800079346s
Availability | VoID file availability check for Persée in RDF took 0.0008106231689453125s
Extra | Recovery of all triples for Persée in RDF took 1.177940845489502s
Performance | Total latancy measurement for Persée in RDF took 0.6778688430786133s
Amount of data | Number of triples check for Persée in RDF took 0.719235897064209s
Interoperability | New terms check for Persée in RDF took 1.9635980129241943s
Versatility | Languages check for Persée in RDF took 121.69335889816284s
Interpretability | Number of blank nodes check for Persée in RDF took 0.37799715995788574s
Interpretability | RDF structures check for Persée in RDF took 0.734830379486084s
Versatility | Serialization formats check for Persée in RDF took 0.8305344581604004s
Availability | RDF dump link check for Persée in RDF took 0.2670297622680664s
License | MR license check for Persée in RDF took 1.3383326530456543s
License | HR license check for Persée in RDF took 37.073158502578735s
Amount of data | Number of property check for Persée in RDF took 0.13832950592041016s
Understandability | Number of label check for Persée in RDF took 1.57590913772583s
Understandability | URI regex check for Persée in RDF took 0.7395789623260498s
Understandability | Vocabs check for Persée in RDF took 0.3555750846862793s
Verifiability | Authors check for Persée in RDF took 0.15785837173461914s
Verifiability | Publishers check for Persée in RDF took 0.11768913269042969s
Performance | Throughput check for Persée in RDF took 10.649136066436768s
Amount of data | Check the number of entities for Persée in RDF took 7.748603820800781e-05s
Verifiability | Contribs. check for Persée in RDF took 0.133986234664917s
Interlinking | sameAs chians check for Persée in RDF took 0.31443190574645996s
Interlinking | skos check for Persée in RDF took 0.5859947204589844s
Interlinking | skos check for Persée in RDF took 0.11628079414367676s
Timeliness | dataset update frequency check for Persée in RDF took 0.6051535606384277s
Currency | Creation date check for Persée in RDF took 0.5296509265899658s
Currency | Modification date check for Persée in RDF took 0.272780179977417s
Rep.Conc. | URIs length for Persée in RDF took 3.6825129985809326s
Interoperability | New vocabularies check for Persée in RDF took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.14467883110046387s
Accuracy | Check Functional Property for Persée in RDF took 0.159088134765625s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.12904930114746094s
Accuracy | Check Empty annotation labels for Persée in RDF took 0.7348456382751465s
Accuracy | Check White space in annotation for Persée in RDF took 0.03808736801147461s
Accuracy | Check Datatype consistency for Persée in RDF took 0.02718210220336914s
Consistency | Disjoint class check for Persée in RDF took 0.2467656135559082s
Consistency | Check Misplaced properties for Persée in RDF took 2.6389966011047363s
Consistency | Misplaced classes for Persée in RDF took 0.22628211975097656s
Consistency | Check Ontology hijacking for Persée in RDF took 1.8375089168548584s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.2517468929290771s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.8684439659118652s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.03158068656921387s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.11590576171875s
Security | Sign check for Persée in RDF took 0.8123934268951416s
Availability | Check URIs Dereferenciability for Persée in RDF took 1331.3468890190125s
Completeness | Calculation of interlinking completeness for Persée in RDF took 1.1875982284545898s
Reputation | Calculation of the PageRank for Persée in RDF took 0.021098613739013672s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00011301040649414062s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 1.430511474609375e-06s
Believability | Calculation of trust value for Persée in RDF took 6.9141387939453125e-06s
INFO | --- Analysis for data-persee-fr took 1573.8878283500671s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 4.7206878662109375e-05s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.7150211334228516s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.02021932601928711s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 2.8848648071289062e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 8.344650268554688e-06s
INFO | --- Analysis for data-southampton-ac-uk took 3.841460943222046s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 0.7562847137451172s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0006163120269775391s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.24790072441101074s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.020383596420288086s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011134147644042969s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 7.152557373046875e-06s
INFO | --- Analysis for data-szepmuveszeti-hu took 9.397386312484741s
Availability | SPARQL endpoint availability check for Open Data Web took 2.47627592086792s
Availability | VoID file availability check for Open Data Web took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.28249621391296387s
Reputation | Calculation of the PageRank for Open Data Web took 0.020520448684692383s
Interlinking | Calculation of Degree of Connection for Open Data Web took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.0040740966796875e-05s
Believability | Calculation of trust value for Open Data Web took 7.62939453125e-06s
INFO | --- Analysis for data.odw.tw took 5.412038803100586s
Availability | SPARQL endpoint availability check for DataFAQs took 4.1961669921875e-05s
Availability | VoID file availability check for DataFAQs took 0.0003211498260498047s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.27281737327575684s
Reputation | Calculation of the PageRank for DataFAQs took 0.020454883575439453s
Interlinking | Calculation of Degree of Connection for DataFAQs took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DataFAQs took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 2.8848648071289062e-05s
Believability | Calculation of trust value for DataFAQs took 8.106231689453125e-06s
INFO | --- Analysis for datafaqs took 3.408705472946167s
Availability | SPARQL endpoint availability check for datahub took 4.267692565917969e-05s
Availability | VoID file availability check for datahub took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for datahub took 0.28116941452026367s
Reputation | Calculation of the PageRank for datahub took 0.020639657974243164s
Interlinking | Calculation of Degree of Connection for datahub took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for datahub took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for datahub took 4.744529724121094e-05s
Believability | Calculation of trust value for datahub took 7.3909759521484375e-06s
INFO | --- Analysis for datahub took 4.370871305465698s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 5.910459280014038s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.24138188362121582s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.02040886878967285s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.170967102050781e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 8.106231689453125e-06s
INFO | --- Analysis for datahub-kr-datamap took 15.786232471466064s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.32477331161499023s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.2832350730895996s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.02010941505432129s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.963180541992188e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 8.106231689453125e-06s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 4.9707019329071045s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.558327198028564s
Availability | VoID file availability check for datos-artium-org took 0.0006895065307617188s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.6968855857849121s
Reputation | Calculation of the PageRank for datos-artium-org took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00011324882507324219s
Believability | Calculation of trust value for datos-artium-org took 7.3909759521484375e-06s
INFO | --- Analysis for datos-artium-org took 166.64242029190063s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.8748679161071777s
Availability | VoID file availability check for Datos.bcn.cl took 0.0003974437713623047s
Extra | Recovery of all triples for Datos.bcn.cl took 128.93071579933167s
Performance | Total latancy measurement for Datos.bcn.cl took 298.5223503112793s
Amount of data | Number of triples check for Datos.bcn.cl took 64.82976222038269s
Interoperability | New terms check for Datos.bcn.cl took 62.61716318130493s
Versatility | Languages check for Datos.bcn.cl took 301.05544233322144s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.2879981994628906s
Security | Check HTTPS for Datos.bcn.cl took 62.48242712020874s
Interpretability | RDF structures check for Datos.bcn.cl took 62.6614146232605s
Versatility | Serialization formats check for Datos.bcn.cl took 62.4365439414978s
Availability | RDF dump link check for Datos.bcn.cl took 62.50680446624756s
License | MR license check for Datos.bcn.cl took 62.52946376800537s
License | HR license check for Datos.bcn.cl took 92.2342140674591s
Amount of data | Number of property check for Datos.bcn.cl took 1.2078745365142822s
Understandability | Number of label check for Datos.bcn.cl took 62.874732971191406s
Understandability | URI regex check for Datos.bcn.cl took 124.71487951278687s
Understandability | Vocabs check for Datos.bcn.cl took 62.54876136779785s
Verifiability | Authors check for Datos.bcn.cl took 62.536051511764526s
Verifiability | Publishers check for Datos.bcn.cl took 62.52297520637512s
Performance | Throughput check for Datos.bcn.cl took 625.2627999782562s
Amount of data | Check the number of entities for Datos.bcn.cl took 7.104873657226562e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 62.53456115722656s
Interlinking | sameAs chians check for Datos.bcn.cl took 62.55692100524902s
Interlinking | skos check for Datos.bcn.cl took 62.53853750228882s
Interlinking | skos check for Datos.bcn.cl took 62.58279776573181s
Timeliness | dataset update frequency check for Datos.bcn.cl took 62.47029519081116s
Currency | Creation date check for Datos.bcn.cl took 125.0647029876709s
Currency | Modification date check for Datos.bcn.cl took 62.52362871170044s
Rep.Conc. | URIs length for Datos.bcn.cl took 137.15953993797302s
Interoperability | New vocabularies check for Datos.bcn.cl took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 50.39185619354248s
Accuracy | Check Functional Property for Datos.bcn.cl took 62.52833390235901s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 62.559542179107666s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 87.0884838104248s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.2365713119506836s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.2788999080657959s
Consistency | Disjoint class check for Datos.bcn.cl took 37.47097444534302s
Consistency | Check Misplaced properties for Datos.bcn.cl took 128.85165691375732s
Consistency | Misplaced classes for Datos.bcn.cl took 59.57342886924744s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 81.86519384384155s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.240396499633789s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 46.4676947593689s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.29603099822998047s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 57.180432081222534s
Security | Sign check for Datos.bcn.cl took 62.33139634132385s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 12.638804912567139s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 1.553542137145996s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.02097177505493164s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 7.486343383789062e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.9073486328125e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 9.298324584960938e-06s
INFO | --- Analysis for datos-bcn-cl took 5921.080471277237s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.305495023727417s
Availability | VoID file availability check for datos.bne.es took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.2757124900817871s
Reputation | Calculation of the PageRank for datos.bne.es took 0.02042675018310547s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011277198791503906s
Believability | Calculation of trust value for datos.bne.es took 7.62939453125e-06s
INFO | --- Analysis for datos-bne-es took 5.662850379943848s
Availability | SPARQL endpoint availability check for dbacademic took 0.16955947875976562s
Availability | VoID file availability check for dbacademic took 0.0003592967987060547s
Completeness | Calculation of interlinking completeness for dbacademic took 0.28828859329223633s
Reputation | Calculation of the PageRank for dbacademic took 0.020066499710083008s
Interlinking | Calculation of Degree of Connection for dbacademic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for dbacademic took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for dbacademic took 2.9802322387695312e-05s
Believability | Calculation of trust value for dbacademic took 5.245208740234375e-06s
INFO | --- Analysis for dbacademic took 3.029304265975952s
Availability | SPARQL endpoint availability check for DBkWik took 25.74454641342163s
Availability | VoID file availability check for DBkWik took 0.0007214546203613281s
Extra | Recovery of all triples for DBkWik took 11.67943549156189s
Performance | Total latancy measurement for DBkWik took 29.2840576171875s
Amount of data | Number of triples check for DBkWik took 12.928818702697754s
Versatility | Languages check for DBkWik took 10.095996856689453s
Interpretability | Number of blank nodes check for DBkWik took 35.33959770202637s
Interpretability | RDF structures check for DBkWik took 0.5855708122253418s
Versatility | Serialization formats check for DBkWik took 4.822070360183716s
Availability | RDF dump link check for DBkWik took 2.909836769104004s
License | MR license check for DBkWik took 9.874894142150879s
License | HR license check for DBkWik took 61.79139828681946s
Amount of data | Number of property check for DBkWik took 11.291811227798462s
Understandability | Number of label check for DBkWik took 13.675511121749878s
Understandability | URI regex check for DBkWik took 22.48654270172119s
Understandability | Vocabs check for DBkWik took 0.134385347366333s
Verifiability | Authors check for DBkWik took 0.20022034645080566s
Verifiability | Publishers check for DBkWik took 0.08880972862243652s
Performance | Throughput check for DBkWik took 64.56299138069153s
Amount of data | Check the number of entities for DBkWik took 6.914138793945312e-05s
Verifiability | Contribs. check for DBkWik took 0.5860793590545654s
Interlinking | sameAs chians check for DBkWik took 12.091568231582642s
Interlinking | skos check for DBkWik took 10.750842332839966s
Interlinking | skos check for DBkWik took 16.943840503692627s
Timeliness | dataset update frequency check for DBkWik took 0.25911426544189453s
Currency | Creation date check for DBkWik took 6.408712148666382s
Currency | Modification date check for DBkWik took 12.477254390716553s
Rep.Conc. | URIs length for DBkWik took 13.280733823776245s
Interoperability | New vocabularies check for DBkWik took 4.131841659545898s
Consistency | Deprecated classes/propertiers check for DBkWik took 27.813327074050903s
Accuracy | Check Functional Property for DBkWik took 12.099122285842896s
Accuracy | Check Inverse Functional Property for DBkWik took 31.189738512039185s
Accuracy | Check Empty annotation labels for DBkWik took 1.7539446353912354s
Accuracy | Check White space in annotation for DBkWik took 0.023250102996826172s
Accuracy | Check Datatype consistency for DBkWik took 0.027529478073120117s
Consistency | Disjoint class check for DBkWik took 16.113784551620483s
Consistency | Check Misplaced properties for DBkWik took 16.83784818649292s
Consistency | Misplaced classes for DBkWik took 30.143847703933716s
Consistency | Check Ontology hijacking for DBkWik took 1.6433262825012207s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.1725986003875732s
Consistency | Check Invalid usage of undefined properties for DBkWik took 24.917957544326782s
Conciseness | Check Extensional conciseness for DBkWik took 0.03273725509643555s
Conciseness | Check Intensional conciseness for DBkWik took 6.104250192642212s
Security | Sign check for DBkWik took 5.072427272796631s
Availability | Check URIs Dereferenciability for DBkWik took 13.198442459106445s
Completeness | Calculation of interlinking completeness for DBkWik took 0.9502830505371094s
Reputation | Calculation of the PageRank for DBkWik took 0.021067142486572266s
Interlinking | Calculation of Degree of Connection for DBkWik took 2.4318695068359375e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for DBkWik took 7.534027099609375e-05s
Interoperability | Check the re-using of existing vocabs for DBkWik took 3.8257791996002197s
Believability | Calculation of trust value for DBkWik took 9.059906005859375e-06s
INFO | --- Analysis for dbkwik took 922.1371147632599s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 4.887580871582031e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0006875991821289062s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.7061257362365723s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.020538806915283203s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007996559143066406s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00010776519775390625s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 8.821487426757812e-06s
INFO | --- Analysis for dblp-deusto-gnoss took 16.675044536590576s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.33293676376342773s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0006215572357177734s
Extra | Recovery of all triples for dblp Knowledge Graph took 8.051316976547241s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.7768588066101074s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.12283754348754883s
Interoperability | New terms check for dblp Knowledge Graph took 1.7788236141204834s
Versatility | Languages check for dblp Knowledge Graph took 33.08402395248413s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 2.225778818130493s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.1775200366973877s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.20031476020812988s
Availability | RDF dump link check for dblp Knowledge Graph took 0.12936186790466309s
License | MR license check for dblp Knowledge Graph took 0.1717066764831543s
License | HR license check for dblp Knowledge Graph took 30.15007448196411s
Amount of data | Number of property check for dblp Knowledge Graph took 0.12839651107788086s
Understandability | Number of label check for dblp Knowledge Graph took 0.5433528423309326s
Understandability | URI regex check for dblp Knowledge Graph took 0.2959280014038086s
Understandability | Vocabs check for dblp Knowledge Graph took 0.18314814567565918s
Verifiability | Authors check for dblp Knowledge Graph took 0.14232635498046875s
Verifiability | Publishers check for dblp Knowledge Graph took 0.12684345245361328s
Performance | Throughput check for dblp Knowledge Graph took 10.714601278305054s
Amount of data | Check the number of entities for dblp Knowledge Graph took 6.008148193359375e-05s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.15644025802612305s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.2504119873046875s
Interlinking | skos check for dblp Knowledge Graph took 0.17061948776245117s
Interlinking | skos check for dblp Knowledge Graph took 0.14502215385437012s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.13949322700500488s
Currency | Creation date check for dblp Knowledge Graph took 0.33591508865356445s
Currency | Modification date check for dblp Knowledge Graph took 0.2964639663696289s
Rep.Conc. | URIs length for dblp Knowledge Graph took 18.740111112594604s
Interoperability | New vocabularies check for dblp Knowledge Graph took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.17755603790283203s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.12917780876159668s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.12761688232421875s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 7.130110025405884s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.072343349456787s
Accuracy | Check Datatype consistency for dblp Knowledge Graph took 6.148987293243408s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.14752864837646484s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.27551794052124023s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 6.13350772857666s
Consistency | Check Invalid usage of undefined classes for dblp Knowledge Graph took 18058.059542179108s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 4.231705665588379s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 2.728715658187866s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.19169187545776367s
Security | Sign check for dblp Knowledge Graph took 0.15837669372558594s
Availability | Check URIs Dereferenciability for dblp Knowledge Graph took 2.3934502601623535s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 1.1175718307495117s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.020806312561035156s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 1.6689300537109375e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 2.1457672119140625e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 1.2874603271484375e-05s
INFO | --- Analysis for dblp-kg took 18265.79781484604s
Availability | SPARQL endpoint availability check for dbnary took 0.28687453269958496s
Availability | VoID file availability check for dbnary took 0.0005540847778320312s
Extra | Recovery of all triples for dbnary took 1.1226484775543213s
Performance | Total latancy measurement for dbnary took 0.42584681510925293s
Amount of data | Number of triples check for dbnary took 1.1988611221313477s
Interoperability | New terms check for dbnary took 3.6519534587860107s
Versatility | Languages check for dbnary took 61.009981870651245s
Interpretability | Number of blank nodes check for dbnary took 3.567686080932617s
Security | Check HTTPS for dbnary took 0.1772477626800537s
Interpretability | RDF structures check for dbnary took 0.25925302505493164s
Versatility | Serialization formats check for dbnary took 0.7691922187805176s
Availability | RDF dump link check for dbnary took 0.07592415809631348s
License | MR license check for dbnary took 0.5835082530975342s
License | HR license check for dbnary took 62.70445156097412s
Amount of data | Number of property check for dbnary took 0.10898542404174805s
Understandability | Number of label check for dbnary took 2.5211703777313232s
Understandability | URI regex check for dbnary took 0.13776397705078125s
Understandability | Vocabs check for dbnary took 0.9358615875244141s
Verifiability | Authors check for dbnary took 1.5744884014129639s
Verifiability | Publishers check for dbnary took 0.16814517974853516s
Performance | Throughput check for dbnary took 10.404841661453247s
Amount of data | Check the number of entities for dbnary took 5.269050598144531e-05s
Verifiability | Contribs. check for dbnary took 0.2172527313232422s
Interlinking | sameAs chians check for dbnary took 0.13689780235290527s
Interlinking | skos check for dbnary took 0.8895237445831299s
Interlinking | skos check for dbnary took 1.1365270614624023s
Timeliness | dataset update frequency check for dbnary took 0.19965505599975586s
Currency | Creation date check for dbnary took 0.37165260314941406s
Currency | Modification date check for dbnary took 0.25898003578186035s
Rep.Conc. | URIs length for dbnary took 11.361231088638306s
Interoperability | New vocabularies check for dbnary took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for dbnary took 0.12866783142089844s
Accuracy | Check Functional Property for dbnary took 0.18094086647033691s
Accuracy | Check Inverse Functional Property for dbnary took 0.1165776252746582s
Accuracy | Check Empty annotation labels for dbnary took 1.1220719814300537s
Accuracy | Check White space in annotation for dbnary took 0.025272130966186523s
Accuracy | Check Datatype consistency for dbnary took 0.027423381805419922s
Consistency | Disjoint class check for dbnary took 0.2320854663848877s
Consistency | Check Misplaced properties for dbnary took 8.91874885559082s
Consistency | Misplaced classes for dbnary took 0.21939635276794434s
Consistency | Check Ontology hijacking for dbnary took 1.8900926113128662s
Consistency | Check Invalid usage of undefined classes for dbnary took 1.3753807544708252s
Consistency | Check Invalid usage of undefined properties for dbnary took 9.931326150894165s
Conciseness | Check Extensional conciseness for dbnary took 0.03167271614074707s
Conciseness | Check Intensional conciseness for dbnary took 0.18682432174682617s
Security | Sign check for dbnary took 0.08532023429870605s
Availability | Check URIs Dereferenciability for dbnary took 12.708786964416504s
Completeness | Calculation of interlinking completeness for dbnary took 0.28102946281433105s
Reputation | Calculation of the PageRank for dbnary took 0.02089095115661621s
Interlinking | Calculation of Degree of Connection for dbnary took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for dbnary took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for dbnary took 6.67572021484375e-05s
Interoperability | Check the re-using of existing vocabs for dbnary took 1.430511474609375e-06s
Believability | Calculation of trust value for dbnary took 1.1444091796875e-05s
INFO | --- Analysis for dbnary took 315.39971256256104s
Availability | SPARQL endpoint availability check for DBpedia took 0.4126303195953369s
Availability | VoID file availability check for DBpedia took 0.0006365776062011719s
Extra | Recovery of all triples for DBpedia took 2.3278353214263916s
Performance | Total latancy measurement for DBpedia took 0.8889815807342529s
Amount of data | Number of triples check for DBpedia took 2.7901010513305664s
Interoperability | New terms check for DBpedia took 13.215705633163452s
Versatility | Languages check for DBpedia took 31.4411883354187s
Interpretability | Number of blank nodes check for DBpedia took 0.1776714324951172s
Security | Check HTTPS for DBpedia took 0.09945106506347656s
Interpretability | RDF structures check for DBpedia took 0.6807339191436768s
Versatility | Serialization formats check for DBpedia took 0.595369815826416s
Availability | RDF dump link check for DBpedia took 2.877852201461792s
License | MR license check for DBpedia took 11.645954132080078s
License | HR license check for DBpedia took 36.53759407997131s
Amount of data | Number of property check for DBpedia took 0.22422456741333008s
Understandability | Number of label check for DBpedia took 18.32961654663086s
Understandability | URI regex check for DBpedia took 0.7359280586242676s
Understandability | Vocabs check for DBpedia took 1.0388565063476562s
Verifiability | Authors check for DBpedia took 1.0244114398956299s
Verifiability | Publishers check for DBpedia took 1.07212233543396s
Performance | Throughput check for DBpedia took 17.809309244155884s
Amount of data | Check the number of entities for DBpedia took 3.1948089599609375e-05s
Verifiability | Contribs. check for DBpedia took 0.3185000419616699s
Interlinking | sameAs chians check for DBpedia took 5.705335855484009s
Interlinking | skos check for DBpedia took 4.466081380844116s
Interlinking | skos check for DBpedia took 0.20810484886169434s
Timeliness | dataset update frequency check for DBpedia took 0.2716941833496094s
Currency | Creation date check for DBpedia took 2.555492401123047s
Currency | Modification date check for DBpedia took 1.9157531261444092s
Rep.Conc. | URIs length for DBpedia took 68.16495370864868s
Interoperability | New vocabularies check for DBpedia took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 11.81855583190918s
Accuracy | Check Functional Property for DBpedia took 6.228643894195557s
Accuracy | Check Inverse Functional Property for DBpedia took 3.2638349533081055s
Accuracy | Check Empty annotation labels for DBpedia took 10.560324668884277s
Accuracy | Check White space in annotation for DBpedia took 0.03066873550415039s
Accuracy | Check Datatype consistency for DBpedia took 0.027184486389160156s
Consistency | Disjoint class check for DBpedia took 0.431260347366333s
Consistency | Check Misplaced properties for DBpedia took 32.52824902534485s
Consistency | Misplaced classes for DBpedia took 3.5078418254852295s
Consistency | Check Ontology hijacking for DBpedia took 4.682036638259888s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.1544747352600098s
Consistency | Check Invalid usage of undefined properties for DBpedia took 6.395378589630127s
Conciseness | Check Extensional conciseness for DBpedia took 0.03143572807312012s
Conciseness | Check Intensional conciseness for DBpedia took 9.841158628463745s
Security | Sign check for DBpedia took 0.20088529586791992s
Availability | Check URIs Dereferenciability for DBpedia took 10284.274520397186s
Completeness | Calculation of interlinking completeness for DBpedia took 1.5594489574432373s
Reputation | Calculation of the PageRank for DBpedia took 0.02169632911682129s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0008995532989501953s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.6689300537109375e-06s
Believability | Calculation of trust value for DBpedia took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia took 10938.947259187698s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 4.4345855712890625e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.29660654067993164s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.020462989807128906s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 6.532669067382812e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-abstract-corpus took 8.478768825531006s
Availability | SPARQL endpoint availability check for DBpedia Commons took 6.219195127487183s
Availability | VoID file availability check for DBpedia Commons took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.7598686218261719s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.02016615867614746s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 6.556510925292969e-05s
Believability | Calculation of trust value for DBpedia Commons took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-commons took 16.493192195892334s
Availability | SPARQL endpoint availability check for DBpedia in German took 4.00543212890625e-05s
Availability | VoID file availability check for DBpedia in German took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.26848363876342773s
Reputation | Calculation of the PageRank for DBpedia in German took 0.02008533477783203s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 6.127357482910156e-05s
Believability | Calculation of trust value for DBpedia in German took 6.9141387939453125e-06s
INFO | --- Analysis for dbpedia-de took 3.475898504257202s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 11.044281005859375s
Availability | VoID file availability check for DBpedia in Greek took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.2785451412200928s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.020433664321899414s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.0001957416534423828s
Believability | Calculation of trust value for DBpedia in Greek took 8.58306884765625e-06s
INFO | --- Analysis for dbpedia-el took 46.863014221191406s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 1.026893138885498s
Availability | VoID file availability check for DBpedia in Spanish took 0.0006449222564697266s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.291187047958374s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.020132780075073242s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00010061264038085938s
Believability | Calculation of trust value for DBpedia in Spanish took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-es took 6.47773551940918s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.3780009746551514s
Availability | VoID file availability check for DBpedia in Basque took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.27384209632873535s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.020320653915405273s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.0994415283203125e-05s
Believability | Calculation of trust value for DBpedia in Basque took 5.245208740234375e-06s
INFO | --- Analysis for dbpedia-eu took 7.076571226119995s
Availability | SPARQL endpoint availability check for DBpedia in French took 1710.807511806488s
Availability | VoID file availability check for DBpedia in French took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.2651240825653076s
Reputation | Calculation of the PageRank for DBpedia in French took 0.02066826820373535s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 9.059906005859375e-05s
Believability | Calculation of trust value for DBpedia in French took 5.245208740234375e-06s
INFO | --- Analysis for dbpedia-fr took 2266.256130695343s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 4.608152151107788s
Availability | VoID file availability check for DBpedia in Japanese took 4.145732402801514s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.6979241371154785s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.020720481872558594s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00010466575622558594s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 1.6689300537109375e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 5.7220458984375e-06s
INFO | --- Analysis for dbpedia-ja took 41.33915734291077s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.1961669921875e-05s
Availability | VoID file availability check for dbpedia lite took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.2690427303314209s
Reputation | Calculation of the PageRank for dbpedia lite took 0.020387649536132812s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 9.703636169433594e-05s
Believability | Calculation of trust value for dbpedia lite took 1.0013580322265625e-05s
INFO | --- Analysis for dbpedia-lite took 23.83108639717102s
Availability | SPARQL endpoint availability check for DBpedia-Live took 3.981590270996094e-05s
Availability | VoID file availability check for DBpedia-Live took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.24964213371276855s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.020288705825805664s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 3.1948089599609375e-05s
Believability | Calculation of trust value for DBpedia-Live took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-live took 3.8996968269348145s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.3245058059692383s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.30504345893859863s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.020376205444335938s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00016236305236816406s
Believability | Calculation of trust value for DBpedia in Dutch took 5.7220458984375e-06s
INFO | --- Analysis for dbpedia-nl took 3.8911030292510986s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 0.5758266448974609s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.27008986473083496s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.020173072814941406s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.058547973632812e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 7.152557373046875e-06s
INFO | --- Analysis for dbpedia-pt took 4.03850531578064s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 3.933906555175781e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.27073097229003906s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.021406173706054688s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 4.696846008300781e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 7.867813110351562e-06s
INFO | --- Analysis for dbpedia-spotlight took 3.3359785079956055s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.363059997558594e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.000701904296875s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.2803821563720703s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.02161431312561035s
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.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 7.653236389160156e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 13.648204565048218s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 4.3392181396484375e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.0002949237823486328s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.25911855697631836s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.020772457122802734s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 3.337860107421875e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia-wikidata took 2.9834141731262207s
Availability | SPARQL endpoint availability check for DBpedia took 4.00543212890625e-05s
Availability | VoID file availability check for DBpedia took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for DBpedia took 0.25616025924682617s
Reputation | Calculation of the PageRank for DBpedia took 0.020374298095703125s
Interlinking | Calculation of Degree of Connection for DBpedia took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for DBpedia took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for DBpedia took 3.0517578125e-05s
Believability | Calculation of trust value for DBpedia took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia_ took 2.959139108657837s
Availability | SPARQL endpoint availability check for DBTropes took 4.100799560546875e-05s
Availability | VoID file availability check for DBTropes took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for DBTropes took 0.2881324291229248s
Reputation | Calculation of the PageRank for DBTropes took 0.020531415939331055s
Interlinking | Calculation of Degree of Connection for DBTropes took 3.552436828613281e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for DBTropes took 0.00010156631469726562s
Believability | Calculation of trust value for DBTropes took 7.3909759521484375e-06s
INFO | --- Analysis for dbtropes took 3.4390151500701904s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 6.29425048828125e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.2732217311859131s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.020330190658569336s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 3.8623809814453125e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 8.106231689453125e-06s
INFO | --- Analysis for dbtune took 2.9252145290374756s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 4.220008850097656e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.26932334899902344s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.020488977432250977s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 7.390975952148438e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 7.152557373046875e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 5.851584434509277s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 4.172325134277344e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.28810739517211914s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.020406484603881836s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0008533000946044922s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.8623809814453125e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 6.67572021484375e-06s
INFO | --- Analysis for dbtune-audioscrobbler took 5.806344985961914s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 6.862821578979492s
Availability | VoID file availability check for DBTune.org/classical took 0.0005841255187988281s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.2976500988006592s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.020175695419311523s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.319450378417969e-05s
Believability | Calculation of trust value for DBTune.org/classical took 7.867813110351562e-06s
INFO | --- Analysis for dbtune-classical took 22.435648202896118s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 8.342579364776611s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.2896239757537842s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.020381689071655273s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 7.009506225585938e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 26.91258478164673s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 8.344485998153687s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0007359981536865234s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.2738831043243408s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.02024102210998535s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.794929504394531e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-magnatune took 23.899141788482666s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 8.338436365127563s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.27678608894348145s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.02039504051208496s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.0001068115234375s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 6.67572021484375e-06s
INFO | --- Analysis for dbtune-musicbrainz took 23.89751696586609s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 8.362829208374023s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.2582850456237793s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.02049422264099121s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.14984130859375e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 6.67572021484375e-06s
INFO | --- Analysis for dbtune-myspace took 17.892548322677612s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 4.124641418457031e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.28142786026000977s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.020405054092407227s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 3.218650817871094e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 6.9141387939453125e-06s
INFO | --- Analysis for dclg-openuplabs took 2.9743709564208984s
Availability | SPARQL endpoint availability check for data.dcs took 4.220008850097656e-05s
Availability | VoID file availability check for data.dcs took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for data.dcs took 0.26868557929992676s
Reputation | Calculation of the PageRank for data.dcs took 0.020264863967895508s
Interlinking | Calculation of Degree of Connection for data.dcs took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for data.dcs took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.29425048828125e-05s
Believability | Calculation of trust value for data.dcs took 6.198883056640625e-06s
INFO | --- Analysis for dcs-sheffield took 3.469308853149414s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 4.4345855712890625e-05s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.0003733634948730469s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.24029898643493652s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.021010637283325195s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 3.552436828613281e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 7.3909759521484375e-06s
INFO | --- Analysis for de-budget took 2.914424419403076s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 4.5299530029296875e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.2644929885864258s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.020269393920898438s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.552436828613281e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 8.106231689453125e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.31719970703125s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 6.628036499023438e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.27431631088256836s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.02035808563232422s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 6.198883056640625e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 5.4836273193359375e-06s
INFO | --- Analysis for debian-package-tracking-system took 4.726296424865723s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 4.267692565917969e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0008752346038818359s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.2515389919281006s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.02051091194152832s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0007927417755126953s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 3.075599670410156e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 7.152557373046875e-06s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 2.8958635330200195s
Availability | SPARQL endpoint availability check for Demografie took 4.1961669921875e-05s
Availability | VoID file availability check for Demografie took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for Demografie took 0.27120518684387207s
Reputation | Calculation of the PageRank for Demografie took 0.02020740509033203s
Interlinking | Calculation of Degree of Connection for Demografie took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Demografie took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Demografie took 3.147125244140625e-05s
Believability | Calculation of trust value for Demografie took 6.9141387939453125e-06s
INFO | --- Analysis for demografie took 3.0388617515563965s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 4.1484832763671875e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.28944969177246094s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.020560503005981445s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.5762786865234375e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 8.106231689453125e-06s
INFO | --- Analysis for desaparecidos took 3.083784818649292s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 5.0067901611328125e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.2689695358276367s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.02815389633178711s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0008237361907958984s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 0.0001266002655029297s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 7.152557373046875e-06s
INFO | --- Analysis for deustoentrepreneurship took 4.558786153793335s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 5.054473876953125e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.26431822776794434s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.02027106285095215s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00010561943054199219s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 7.867813110351562e-06s
INFO | --- Analysis for deustotech took 5.431055068969727s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.4873859882354736s
Availability | VoID file availability check for Deutsche Biographie took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.27530860900878906s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.020266294479370117s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 3.552436828613281e-05s
Believability | Calculation of trust value for Deutsche Biographie took 6.9141387939453125e-06s
INFO | --- Analysis for deutsche-biographie took 4.338287353515625s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 8.988380432128906e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.2783091068267822s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.020362138748168945s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.316734313964844e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 7.3909759521484375e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 7.703059911727905s
Availability | SPARQL endpoint availability check for dev8d took 4.076957702636719e-05s
Availability | VoID file availability check for dev8d took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for dev8d took 0.2730536460876465s
Reputation | Calculation of the PageRank for dev8d took 0.020200729370117188s
Interlinking | Calculation of Degree of Connection for dev8d took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for dev8d took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.651878356933594e-05s
Believability | Calculation of trust value for dev8d took 6.9141387939453125e-06s
INFO | --- Analysis for dev8d took 3.0941083431243896s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.220317363739014s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0007543563842773438s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.28664350509643555s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.020534038543701172s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 5.340576171875e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 1.0967254638671875e-05s
INFO | --- Analysis for dewey_decimal_classification took 92.88505244255066s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 4.1961669921875e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.00037980079650878906s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.2721829414367676s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.020430564880371094s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 2.9087066650390625e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 6.4373016357421875e-06s
INFO | --- Analysis for DHSVM took 16.62417435646057s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 3.981590270996094e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.2703559398651123s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.02024078369140625s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 2.956390380859375e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 7.152557373046875e-06s
INFO | --- Analysis for diachronic-ontologies-peoples-daily took 3.068784236907959s
Availability | SPARQL endpoint availability check for Diavgeia took 4.76837158203125e-05s
Availability | VoID file availability check for Diavgeia took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.2930867671966553s
Reputation | Calculation of the PageRank for Diavgeia took 0.020084857940673828s
Interlinking | Calculation of Degree of Connection for Diavgeia took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.821487426757812e-05s
Believability | Calculation of trust value for Diavgeia took 5.0067901611328125e-06s
INFO | --- Analysis for diavgeia took 5.782188653945923s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.220008850097656e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007183551788330078s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.25371456146240234s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.019916057586669922s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011444091796875s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for didactalia took 12.121037483215332s
Availability | SPARQL endpoint availability check for diigo.feed took 4.1484832763671875e-05s
Availability | VoID file availability check for diigo.feed took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.2815837860107422s
Reputation | Calculation of the PageRank for diigo.feed took 0.020145893096923828s
Interlinking | Calculation of Degree of Connection for diigo.feed took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 3.0279159545898438e-05s
Believability | Calculation of trust value for diigo.feed took 7.152557373046875e-06s
INFO | --- Analysis for diigo-feed took 2.865030527114868s
Availability | SPARQL endpoint availability check for DisGeNET took 0.9198150634765625s
Availability | VoID file availability check for DisGeNET took 0.0005338191986083984s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.29419445991516113s
Reputation | Calculation of the PageRank for DisGeNET took 0.020235538482666016s
Interlinking | Calculation of Degree of Connection for DisGeNET took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00016880035400390625s
Believability | Calculation of trust value for DisGeNET took 5.7220458984375e-06s
INFO | --- Analysis for disgenet took 8.725524425506592s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 4.029273986816406e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.2684798240661621s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.020230770111083984s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 2.8371810913085938e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 6.4373016357421875e-06s
INFO | --- Analysis for disk took 2.943939208984375s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 4.1961669921875e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.00039505958557128906s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.2824215888977051s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.0259091854095459s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0012428760528564453s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 4.6253204345703125e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 8.106231689453125e-06s
INFO | --- Analysis for distritos-zaragoza took 2.966437339782715s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.220008850097656e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0006618499755859375s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.25584959983825684s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.020619869232177734s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.123283386230469e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 7.152557373046875e-06s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 7.5217180252075195s
Availability | SPARQL endpoint availability check for DM2E took 4.220008850097656e-05s
Availability | VoID file availability check for DM2E took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for DM2E took 0.2465219497680664s
Reputation | Calculation of the PageRank for DM2E took 0.020552873611450195s
Interlinking | Calculation of Degree of Connection for DM2E took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00011086463928222656s
Believability | Calculation of trust value for DM2E took 7.3909759521484375e-06s
INFO | --- Analysis for dm2e took 3.1243255138397217s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 4.0531158447265625e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.27909135818481445s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.020542144775390625s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 3.218650817871094e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 7.3909759521484375e-06s
INFO | --- Analysis for dmoz_rdf_dump took 3.000434637069702s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 2.0822582244873047s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.31688451766967773s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.02022695541381836s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00017547607421875s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 7.3909759521484375e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 11.953901052474976s
Availability | SPARQL endpoint availability check for DOAP Store took 3.981590270996094e-05s
Availability | VoID file availability check for DOAP Store took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.26694822311401367s
Reputation | Calculation of the PageRank for DOAP Store took 0.02040863037109375s
Interlinking | Calculation of Degree of Connection for DOAP Store took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DOAP Store took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 4.100799560546875e-05s
Believability | Calculation of trust value for DOAP Store took 2.0503997802734375e-05s
INFO | --- Analysis for doap_store took 2.9711596965789795s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 4.267692565917969e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.30086612701416016s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.020621776580810547s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.341934204101562e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 5.4836273193359375e-06s
INFO | --- Analysis for doi took 7.984708547592163s
Availability | SPARQL endpoint availability check for Driggu Florentino took 4.291534423828125e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0006787776947021484s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.2664651870727539s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.020209550857543945s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 3.0994415283203125e-05s
Believability | Calculation of trust value for Driggu Florentino took 1.239776611328125e-05s
INFO | --- Analysis for Driggu took 3.318326234817505s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 7.0827155113220215s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0006449222564697266s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.28371524810791016s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.02044367790222168s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.528594970703125e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 7.3909759521484375e-06s
INFO | --- Analysis for drug-data-hifm took 36.68419051170349s
Availability | SPARQL endpoint availability check for dspace took 3.886222839355469e-05s
Availability | VoID file availability check for dspace took 0.0003256797790527344s
Completeness | Calculation of interlinking completeness for dspace took 0.265744686126709s
Reputation | Calculation of the PageRank for dspace took 0.021045684814453125s
Interlinking | Calculation of Degree of Connection for dspace took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for dspace took 0.0010161399841308594s
Interlinking | Calculation of Clustering coefficient for dspace took 3.886222839355469e-05s
Believability | Calculation of trust value for dspace took 7.152557373046875e-06s
INFO | --- Analysis for dspace took 2.9525349140167236s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 7.653236389160156e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.2823829650878906s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.020273447036743164s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 2.956390380859375e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 8.106231689453125e-06s
INFO | --- Analysis for duraark-linked-building-data took 3.0615084171295166s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 271.7201347351074s
Availability | VoID file availability check for MetaLex Document Server took 0.0006916522979736328s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.2596435546875s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.021120548248291016s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 3.5762786865234375e-05s
Believability | Calculation of trust value for MetaLex Document Server took 7.62939453125e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 555.0266757011414s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 1.3822996616363525s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0007700920104980469s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.5970103740692139s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020409822463989258s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 4.5299530029296875e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 9.5367431640625e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 1243.2136993408203s
Availability | SPARQL endpoint availability check for DWS-Group took 4.291534423828125e-05s
Availability | VoID file availability check for DWS-Group took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.7018430233001709s
Reputation | Calculation of the PageRank for DWS-Group took 0.020185232162475586s
Interlinking | Calculation of Degree of Connection for DWS-Group took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010251998901367188s
Believability | Calculation of trust value for DWS-Group took 7.152557373046875e-06s
INFO | --- Analysis for dws-group took 3.004253387451172s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 8.511543273925781e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0007588863372802734s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.2836298942565918s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.02052474021911621s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 3.0517578125e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 7.152557373046875e-06s
INFO | --- Analysis for E1 took 5.939486742019653s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.06299042701721191s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0003466606140136719s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.27278566360473633s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.020364761352539062s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00011777877807617188s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-alaska took 3.411898612976074s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.043493032455444336s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.7219667434692383s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.02038121223449707s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 6.008148193359375e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-cau took 3.837266683578491s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.044731855392456055s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.00021386146545410156s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.28576111793518066s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.020456552505493164s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.580352783203125e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.918571710586548s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.03339385986328125s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.267148494720459s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.02054595947265625s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.608268737792969e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-cdrewu took 2.5317747592926025s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.050684213638305664s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.2518656253814697s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.02038288116455078s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00013327598571777344s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-dartmouth took 2.4640612602233887s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0336456298828125s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.27941179275512695s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.020334482192993164s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.893013000488281e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-famu took 2.56852126121521s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.043770551681518555s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.280733585357666s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.020260334014892578s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00012946128845214844s
Believability | Calculation of trust value for eagle-i @ Harvard University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-harvard took 3.012795925140381s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.044153690338134766s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.2688107490539551s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.02009725570678711s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.0001304149627685547s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-hawaii took 2.485541820526123s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.042517662048339844s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.28246092796325684s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.022895336151123047s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0011091232299804688s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 8.487701416015625e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-howard took 2.525636672973633s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.05104947090148926s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.2942211627960205s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020394325256347656s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.341934204101562e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.4998862743377686s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.04573488235473633s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.24498772621154785s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.020159482955932617s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.0001125335693359375s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-jsu took 2.48655104637146s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.045530080795288086s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.2772836685180664s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.02052927017211914s
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.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.790855407714844e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-meharry took 2.5235049724578857s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.03931570053100586s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.24744224548339844s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.020124435424804688s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 9.775161743164062e-05s
Believability | Calculation of trust value for eagle-i @ Montana State University took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-montana took 2.547161817550659s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.05612444877624512s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0004343986511230469s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.2821667194366455s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.020111799240112305s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.1552734375e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-msm took 2.4854423999786377s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.04585695266723633s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.00034117698669433594s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.2583911418914795s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.02064681053161621s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00012826919555664062s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-ohsu took 2.5355803966522217s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.04504203796386719s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.000377655029296875s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.2523367404937744s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020406484603881836s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.67572021484375e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-psm took 2.4824583530426025s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.03877115249633789s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.25276708602905273s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020449399948120117s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.532669067382812e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-tsu took 2.3728530406951904s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.042693376541137695s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0009114742279052734s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.2791171073913574s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.020390033721923828s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.341934204101562e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 1.0013580322265625e-05s
INFO | --- Analysis for eagle-i-tuskegee took 2.4032838344573975s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.03814697265625s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.30605053901672363s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.020002126693725586s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 9.751319885253906e-05s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-uccaribe took 2.515812873840332s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.042304277420043945s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.001140594482421875s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.26444554328918457s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.02049708366394043s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00012373924255371094s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-upr took 2.4473187923431396s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.042191267013549805s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.25853729248046875s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.02088165283203125s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007970333099365234s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 7.987022399902344e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-utep took 2.518308162689209s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.03097987174987793s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0009887218475341797s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.26793408393859863s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.020654916763305664s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 7.05718994140625e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 8.58306884765625e-06s
INFO | --- Analysis for eagle-i-utsa took 2.4189844131469727s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.18177032470703125s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.001893758773803711s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.259502649307251s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.0206601619720459s
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.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.5367431640625e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-vanderbilt took 2.704324245452881s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.046525001525878906s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.27895498275756836s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.020634174346923828s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.915496826171875e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-xula took 2.5236356258392334s
Availability | SPARQL endpoint availability check for Emergency situation took 0.5213463306427002s
Availability | VoID file availability check for Emergency situation took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.2687649726867676s
Reputation | Calculation of the PageRank for Emergency situation took 0.020542621612548828s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.9114227294921875e-05s
Believability | Calculation of trust value for Emergency situation took 6.198883056640625e-06s
INFO | --- Analysis for Earthquake took 3.7790451049804688s
Availability | SPARQL endpoint availability check for ESO took 0.44793033599853516s
Availability | VoID file availability check for ESO took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for ESO took 0.2545013427734375s
Reputation | Calculation of the PageRank for ESO took 0.020678997039794922s
Interlinking | Calculation of Degree of Connection for ESO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for ESO took 8.320808410644531e-05s
Believability | Calculation of trust value for ESO took 3.0994415283203125e-05s
INFO | --- Analysis for Earthquake_case took 4.003679037094116s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.9397873878479004s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.2641716003417969s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.020476341247558594s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.0001068115234375s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for ecb-linked-data took 3.364647388458252s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 4.2717461585998535s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.000736236572265625s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.2680048942565918s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.020650148391723633s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.6716461181640625e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 5.7220458984375e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 10.96390676498413s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.8304624557495117s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0006663799285888672s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.2731819152832031s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.020479679107666016s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.985664367675781e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for ecco-tcp-linked-data took 6.160355806350708s
Availability | SPARQL endpoint availability check for ECLAP took 20.63931179046631s
Availability | VoID file availability check for ECLAP took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for ECLAP took 0.29122447967529297s
Reputation | Calculation of the PageRank for ECLAP took 0.020449399948120117s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for ECLAP took 4.458427429199219e-05s
Believability | Calculation of trust value for ECLAP took 7.152557373046875e-06s
INFO | --- Analysis for eclap took 53.06934309005737s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 4.1961669921875e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0006339550018310547s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.29125332832336426s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.020551681518554688s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.2874603271484375e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 1.0967254638671875e-05s
INFO | --- Analysis for ECNU-GISer took 35.1861526966095s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.1961669921875e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0004203319549560547s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.24363470077514648s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02052783966064453s
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.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.364418029785156e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 5.9604644775390625e-06s
INFO | --- Analysis for ecs took 2.468595504760742s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 4.3392181396484375e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.2719540596008301s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.020648717880249023s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 3.24249267578125e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 7.3909759521484375e-06s
INFO | --- Analysis for edificios-historicos-zaragoza took 2.9528958797454834s
Availability | SPARQL endpoint availability check for Edublogs took 4.482269287109375e-05s
Availability | VoID file availability check for Edublogs took 0.000637054443359375s
Completeness | Calculation of interlinking completeness for Edublogs took 0.2560231685638428s
Reputation | Calculation of the PageRank for Edublogs took 0.020392656326293945s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Edublogs took 9.870529174804688e-05s
Believability | Calculation of trust value for Edublogs took 5.245208740234375e-06s
INFO | --- Analysis for edublogs took 3.4498112201690674s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.5422255992889404s
Availability | VoID file availability check for education.data.gov.uk took 0.0006718635559082031s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.2772552967071533s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.02044081687927246s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 8.869171142578125e-05s
Believability | Calculation of trust value for education.data.gov.uk took 5.7220458984375e-06s
INFO | --- Analysis for education-data-gov-uk took 4.8332602977752686s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 6.413459777832031e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.2886006832122803s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.020691871643066406s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 3.147125244140625e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 1.0728836059570312e-05s
INFO | --- Analysis for education-openuplabs took 3.00142502784729s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 392.00112771987915s
Availability | VoID file availability check for Educational programs - SISVU took 0.0007662773132324219s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.8401250839233398s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.02650594711303711s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 5.3882598876953125e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 7.867813110351562e-06s
INFO | --- Analysis for educationalprograms_sisvu took 1322.316572189331s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 0.781113862991333s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.6908478736877441s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.02072596549987793s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 4.00543212890625e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 5.7220458984375e-06s
INFO | --- Analysis for eea took 10.88523244857788s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.525078296661377s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.24578380584716797s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020519495010375977s
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.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.173683166503906e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 5.0067901611328125e-06s
INFO | --- Analysis for eea-rod took 6.6536524295806885s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.18448448181152344s
Availability | VoID file availability check for EEA Vocabularies took 0.0003554821014404297s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.2578916549682617s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.082389831542969e-05s
Believability | Calculation of trust value for EEA Vocabularies took 7.62939453125e-06s
INFO | --- Analysis for eea-vocabularies took 6.136925458908081s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 4.100799560546875e-05s
Availability | VoID file availability check for Ege University Linked Open Data took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.28116846084594727s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.020691394805908203s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 3.170967102050781e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 6.9141387939453125e-06s
INFO | --- Analysis for ege-university-linked-open-data took 4.700662851333618s
Availability | SPARQL endpoint availability check for E-Government Ontology took 0.42389655113220215s
Availability | VoID file availability check for E-Government Ontology took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.2480325698852539s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.020310640335083008s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 3.0040740966796875e-05s
Believability | Calculation of trust value for E-Government Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for EGovOntology took 3.233579158782959s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5912728309631348s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007038116455078125s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 3.7035253047943115s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.285729169845581s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6178207397460938s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.845017671585083s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.33629584312439s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 4.345363140106201s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5670061111450195s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.0910093784332275s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24158859252929688s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5354795455932617s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 6.29876446723938s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2612628936767578s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.47226381301879883s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6141538619995117s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.27245068550109863s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.36783885955810547s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2415320873260498s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 10.863467931747437s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 7.963180541992188e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.310793399810791s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3069803714752197s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4564082622528076s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.27712583541870117s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8240022659301758s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.6426405906677246s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.609668493270874s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 5.914612054824829s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23470044136047363s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.340224027633667s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2901618480682373s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 1.3926260471343994s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.02979445457458496s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.02759242057800293s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3287391662597656s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.435304403305054s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4698643684387207s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.4996681213378906s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1429142951965332s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.36317777633667s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03496551513671875s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5324320793151855s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4328923225402832s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 3454.2833111286163s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1826798915863037s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.020503520965576172s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 4.7206878662109375e-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 8.106231689453125e-06s
INFO | --- Analysis for ei2a took 11043.955704689026s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 4.291534423828125e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0005342960357666016s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.2810230255126953s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010657310485839844s
Believability | Calculation of trust value for EIONET RDF Data took 5.4836273193359375e-06s
INFO | --- Analysis for eionet-rdf took 4.780681371688843s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 4.267692565917969e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.2884676456451416s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.020643949508666992s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.266334533691406e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 9.5367431640625e-06s
INFO | --- Analysis for ElgooG_ took 3.763181209564209s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 4.220008850097656e-05s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.25993824005126953s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.020465850830078125s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 2.9802322387695312e-05s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 6.67572021484375e-06s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 3.5719103813171387s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 9.240270376205444s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.25248026847839355s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.020095348358154297s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 7.271766662597656e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 7.62939453125e-06s
INFO | --- Analysis for elviajero took 23.045265436172485s
Availability | SPARQL endpoint availability check for EMN took 4.1484832763671875e-05s
Availability | VoID file availability check for EMN took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for EMN took 0.28518152236938477s
Reputation | Calculation of the PageRank for EMN took 0.02074885368347168s
Interlinking | Calculation of Degree of Connection for EMN took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for EMN took 4.172325134277344e-05s
Believability | Calculation of trust value for EMN took 8.58306884765625e-06s
INFO | --- Analysis for emn took 2.8499629497528076s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 4.291534423828125e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.3143608570098877s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.020282745361328125s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.5789947509765625e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 5.245208740234375e-06s
INFO | --- Analysis for enakting-co2emission took 2.999844551086426s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 4.100799560546875e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.2807018756866455s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.02099609375s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 4.076957702636719e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 5.4836273193359375e-06s
INFO | --- Analysis for enakting-crime took 2.812748670578003s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 6.961822509765625e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.0007283687591552734s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.300060510635376s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.02062392234802246s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 4.172325134277344e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 1.0013580322265625e-05s
INFO | --- Analysis for enakting-energy took 2.558061361312866s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.2754788398742676s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.02074122428894043s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 9.226799011230469e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 3.147125244140625e-05s
INFO | --- Analysis for enakting-mortality took 2.5550968647003174s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.172325134277344e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.2979085445404053s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.0203704833984375s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.743171691894531e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 5.0067901611328125e-06s
INFO | --- Analysis for enakting-nhs took 2.574880599975586s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 5.53131103515625e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.000982522964477539s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.27672386169433594s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.020307540893554688s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.269050598144531e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 4.76837158203125e-06s
INFO | --- Analysis for enakting-population took 2.522246837615967s
Availability | SPARQL endpoint availability check for Enel Shops took 4.00543212890625e-05s
Availability | VoID file availability check for Enel Shops took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.27475571632385254s
Reputation | Calculation of the PageRank for Enel Shops took 0.020194053649902344s
Interlinking | Calculation of Degree of Connection for Enel Shops took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Enel Shops took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 3.075599670410156e-05s
Believability | Calculation of trust value for Enel Shops took 7.3909759521484375e-06s
INFO | --- Analysis for enel-shops took 3.1166927814483643s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 5.245208740234375e-05s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.26050806045532227s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.020250320434570312s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 2.956390380859375e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 6.9141387939453125e-06s
INFO | --- Analysis for energy-efficiency took 3.0530216693878174s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 4.124641418457031e-05s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.0002219676971435547s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.25420093536376953s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.020128965377807617s
Interlinking | Calculation of Degree of Connection for English Heritage Archaeological Sciences Thesaurus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for English Heritage Archaeological Sciences Thesaurus took 0.0007925033569335938s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 3.075599670410156e-05s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 8.58306884765625e-06s
INFO | --- Analysis for english-heritage-archaeological-sciences-thesaurus took 3.4201748371124268s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 4.0531158447265625e-05s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 0.00022649765014648438s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.26369643211364746s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.020353078842163086s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 3.0517578125e-05s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for english-heritage-building-materials-thesaurus took 3.0008716583251953s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 3.981590270996094e-05s
Availability | VoID file availability check for English Heritage Components Thesaurus took 0.00032019615173339844s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.29542040824890137s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.020418167114257812s
Interlinking | Calculation of Degree of Connection for English Heritage Components Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Heritage Components Thesaurus took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 3.3855438232421875e-05s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for english-heritage-components-thesaurus took 3.1156907081604004s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 3.910064697265625e-05s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.00030422210693359375s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.27255916595458984s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.020479679107666016s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 3.2901763916015625e-05s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 3.076641082763672s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 4.029273986816406e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 0.28112173080444336s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.02055954933166504s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 3.528594970703125e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 3.091543197631836s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 4.0531158447265625e-05s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.29480552673339844s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.02159881591796875s
Interlinking | Calculation of Degree of Connection for English Heritage Maritime Craft Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for English Heritage Maritime Craft Thesaurus took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 3.0994415283203125e-05s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for english-heritage-maritime-craft-thesaurus took 2.9849822521209717s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.2814009189605713s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.020366430282592773s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 3.075599670410156e-05s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for english-heritage-monument-types-thesaurus took 3.080117702484131s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.7273733615875244s
Availability | VoID file availability check for English Heritage Periods List took 0.0004413127899169922s
Extra | Recovery of all triples for English Heritage Periods List took 0.460615873336792s
Performance | Total latancy measurement for English Heritage Periods List took 2.2121243476867676s
Amount of data | Number of triples check for English Heritage Periods List took 0.5918807983398438s
Versatility | Languages check for English Heritage Periods List took 0.35769224166870117s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.5512986183166504s
Security | Check HTTPS for English Heritage Periods List took 0.2584507465362549s
Interpretability | RDF structures check for English Heritage Periods List took 0.3426065444946289s
Versatility | Serialization formats check for English Heritage Periods List took 0.6066157817840576s
Availability | RDF dump link check for English Heritage Periods List took 0.38615942001342773s
License | MR license check for English Heritage Periods List took 0.5184319019317627s
License | HR license check for English Heritage Periods List took 0.4224979877471924s
Amount of data | Number of property check for English Heritage Periods List took 0.4318559169769287s
Understandability | Number of label check for English Heritage Periods List took 0.5568547248840332s
Understandability | URI regex check for English Heritage Periods List took 0.8216104507446289s
Understandability | Vocabs check for English Heritage Periods List took 0.46657323837280273s
Verifiability | Authors check for English Heritage Periods List took 0.47630977630615234s
Verifiability | Publishers check for English Heritage Periods List took 0.43935132026672363s
Performance | Throughput check for English Heritage Periods List took 12.192432165145874s
Amount of data | Check the number of entities for English Heritage Periods List took 6.747245788574219e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.4194772243499756s
Interlinking | sameAs chians check for English Heritage Periods List took 0.38925600051879883s
Interlinking | skos check for English Heritage Periods List took 0.40213584899902344s
Interlinking | skos check for English Heritage Periods List took 0.41333770751953125s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.534355640411377s
Currency | Creation date check for English Heritage Periods List took 0.8376696109771729s
Currency | Modification date check for English Heritage Periods List took 0.8772203922271729s
Rep.Conc. | URIs length for English Heritage Periods List took 0.8091421127319336s
Interoperability | New vocabularies check for English Heritage Periods List took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.45305466651916504s
Accuracy | Check Functional Property for English Heritage Periods List took 0.49597859382629395s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.45253920555114746s
Consistency | Disjoint class check for English Heritage Periods List took 0.4098012447357178s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.46187472343444824s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.5867135524749756s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.0001423358917236328s
Security | Sign check for English Heritage Periods List took 0.4088711738586426s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.2765169143676758s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.020421504974365234s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.910064697265625e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Heritage Periods List took 6.198883056640625e-06s
INFO | --- Analysis for english-heritage-periods-list took 60.79105186462402s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 1.0719735622406006s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.6773078441619873s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.2841756343841553s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.02016139030456543s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.170967102050781e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 5.245208740234375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 9.010722875595093s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.8458549976348877s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.5877864360809326s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.2924964427947998s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.02009892463684082s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.170967102050781e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 4.291534423828125e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 7.534937381744385s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 4.792213439941406e-05s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 0.27693796157836914s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.02030158042907715s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 2.956390380859375e-05s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 6.9141387939453125e-06s
INFO | --- Analysis for english-indices-of-multiple-deprivation took 3.0940043926239014s
Availability | SPARQL endpoint availability check for English WordNet took 4.172325134277344e-05s
Availability | VoID file availability check for English WordNet took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for English WordNet took 0.2649564743041992s
Reputation | Calculation of the PageRank for English WordNet took 0.020186662673950195s
Interlinking | Calculation of Degree of Connection for English WordNet took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for English WordNet took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.0517578125e-05s
Believability | Calculation of trust value for English WordNet took 6.67572021484375e-06s
INFO | --- Analysis for english-wordnet took 3.1028378009796143s
Availability | SPARQL endpoint availability check for English Heritage Places took 4.1961669921875e-05s
Availability | VoID file availability check for English Heritage Places took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for English Heritage Places took 0.29601335525512695s
Reputation | Calculation of the PageRank for English Heritage Places took 0.020402908325195312s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 2.8133392333984375e-05s
Believability | Calculation of trust value for English Heritage Places took 7.62939453125e-06s
INFO | --- Analysis for englishheritage_places took 3.394977331161499s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.179351806640625s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.0004220008850097656s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.28658223152160645s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.02025294303894043s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 9.250640869140625e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 6.4373016357421875e-06s
INFO | --- Analysis for enipedia took 2.705418825149536s
Availability | SPARQL endpoint availability check for Enslaved.org took 4.315376281738281e-05s
Availability | VoID file availability check for Enslaved.org took 0.0005834102630615234s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.2713620662689209s
Reputation | Calculation of the PageRank for Enslaved.org took 0.020205974578857422s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 2.9087066650390625e-05s
Believability | Calculation of trust value for Enslaved.org took 7.152557373046875e-06s
INFO | --- Analysis for enslaved.org took 4.764194488525391s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.06607723236083984s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.00021839141845703125s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.2994692325592041s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.020313262939453125s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 5.936622619628906e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 7.3909759521484375e-06s
INFO | --- Analysis for entice-graph took 2.562974691390991s
Availability | SPARQL endpoint availability check for Entrez Gene took 4.267692565917969e-05s
Availability | VoID file availability check for Entrez Gene took 0.0008106231689453125s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.2688429355621338s
Reputation | Calculation of the PageRank for Entrez Gene took 0.020447492599487305s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.6716461181640625e-05s
Believability | Calculation of trust value for Entrez Gene took 6.9141387939453125e-06s
INFO | --- Analysis for entrez_gene took 27.03154945373535s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 4.172325134277344e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 0.27239131927490234s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.020247697830200195s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 3.075599670410156e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 7.62939453125e-06s
INFO | --- Analysis for entrez_gene_extract took 2.9129281044006348s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.167935848236084s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.2707996368408203s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.020468473434448242s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0008215904235839844s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.125999450683594e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 5.0067901611328125e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 12.387216806411743s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.3511838912963867s
Availability | VoID file availability check for environment.data.gov.uk took 0.0006339550018310547s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.261059045791626s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.02030777931213379s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.696846008300781e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 4.5299530029296875e-06s
INFO | --- Analysis for environment-data-gov-uk took 10.12807011604309s
Availability | SPARQL endpoint availability check for EARTh took 271.90969944000244s
Availability | VoID file availability check for EARTh took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for EARTh took 0.29062819480895996s
Reputation | Calculation of the PageRank for EARTh took 0.02057623863220215s
Interlinking | Calculation of Degree of Connection for EARTh took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for EARTh took 9.608268737792969e-05s
Believability | Calculation of trust value for EARTh took 1.3828277587890625e-05s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 565.4350056648254s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 352.83366417884827s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 0.7370917797088623s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.020716428756713867s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 3.24249267578125e-05s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 6.4373016357421875e-06s
INFO | --- Analysis for EO_metadata took 630.1865720748901s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 4.1961669921875e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0004322528839111328s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.2605292797088623s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.020821571350097656s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.266334533691406e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 7.62939453125e-06s
INFO | --- Analysis for EOKP-Datasets took 6.211341381072998s
Availability | SPARQL endpoint availability check for EPA-CDR took 4.1961669921875e-05s
Availability | VoID file availability check for EPA-CDR took 0.0007107257843017578s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.28992533683776855s
Reputation | Calculation of the PageRank for EPA-CDR took 0.020422697067260742s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EPA-CDR took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.4809112548828125e-05s
Believability | Calculation of trust value for EPA-CDR took 5.4836273193359375e-06s
INFO | --- Analysis for epa-cdr took 7.65177321434021s
Availability | SPARQL endpoint availability check for EPA-FRS took 4.076957702636719e-05s
Availability | VoID file availability check for EPA-FRS took 0.0006740093231201172s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.2747776508331299s
Reputation | Calculation of the PageRank for EPA-FRS took 0.0200655460357666s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.128715515136719e-05s
Believability | Calculation of trust value for EPA-FRS took 4.5299530029296875e-06s
INFO | --- Analysis for epa-frs took 6.386910438537598s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.172325134277344e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0006699562072753906s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.3451499938964844s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020127534866333008s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.0517578125e-05s
Believability | Calculation of trust value for EPA-RCRA took 5.0067901611328125e-06s
INFO | --- Analysis for epa-rcra took 6.744607448577881s
Availability | SPARQL endpoint availability check for EPA-SRS took 4.291534423828125e-05s
Availability | VoID file availability check for EPA-SRS took 0.0007250308990478516s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.26860547065734863s
Reputation | Calculation of the PageRank for EPA-SRS took 0.020094871520996094s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 8.20159912109375e-05s
Believability | Calculation of trust value for EPA-SRS took 5.0067901611328125e-06s
INFO | --- Analysis for epa-srs took 6.374000072479248s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.124641418457031e-05s
Availability | VoID file availability check for EPA-TRI took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.26763033866882324s
Reputation | Calculation of the PageRank for EPA-TRI took 0.02058577537536621s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.5762786865234375e-05s
Believability | Calculation of trust value for EPA-TRI took 4.76837158203125e-06s
INFO | --- Analysis for epa-tri took 6.198528528213501s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 4.124641418457031e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 0.28542494773864746s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.02034306526184082s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 7.677078247070312e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 1.1920928955078125e-05s
INFO | --- Analysis for epo took 3.472628355026245s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.040334463119506836s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.24340343475341797s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.020297527313232422s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00012922286987304688s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.994244337081909s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.47435665130615234s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.28111815452575684s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.020837783813476562s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.225440979003906e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 6.9141387939453125e-06s
INFO | --- Analysis for eprtr took 3.684448719024658s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.864412784576416s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.28461503982543945s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.020682811737060547s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 2.956390380859375e-05s
Believability | Calculation of trust value for Railway Infrastructure KG took 6.9141387939453125e-06s
INFO | --- Analysis for ERAKG took 3.3998305797576904s
Availability | SPARQL endpoint availability check for reg took 4.291534423828125e-05s
Availability | VoID file availability check for reg took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for reg took 0.24991631507873535s
Reputation | Calculation of the PageRank for reg took 0.020571231842041016s
Interlinking | Calculation of Degree of Connection for reg took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for reg took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for reg took 1.2159347534179688e-05s
Believability | Calculation of trust value for reg took 7.62939453125e-06s
INFO | --- Analysis for erg took 2.362870931625366s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.541325569152832s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.2806978225708008s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.020267248153686523s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.0279159545898438e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 5.245208740234375e-06s
INFO | --- Analysis for es-msssi-drug-prices took 3.243727684020996s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 5.340576171875e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.25737714767456055s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 8.7738037109375e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 5.0067901611328125e-06s
INFO | --- Analysis for esd-standards took 4.038456439971924s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 4.220008850097656e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0007045269012451172s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.2807633876800537s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.02056884765625s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.534027099609375e-05s
Believability | Calculation of trust value for ESD-Toolkit took 2.8133392333984375e-05s
INFO | --- Analysis for esd-toolkit took 3.425884962081909s
Availability | SPARQL endpoint availability check for Dataset Esis took 4.1961669921875e-05s
Availability | VoID file availability check for Dataset Esis took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.2813730239868164s
Reputation | Calculation of the PageRank for Dataset Esis took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.0994415283203125e-05s
Believability | Calculation of trust value for Dataset Esis took 6.9141387939453125e-06s
INFO | --- Analysis for esislearning took 2.8989434242248535s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 4.649162292480469e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.28859496116638184s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.020709514617919922s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 3.4332275390625e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 9.059906005859375e-06s
INFO | --- Analysis for ESV took 24.73441457748413s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.6018071174621582s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.28055500984191895s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.020338058471679688s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 7.62939453125e-06s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 4.342974662780762s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 4.720319032669067s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.2852292060852051s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.02066326141357422s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.43865966796875e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 7.152557373046875e-06s
INFO | --- Analysis for eu-agencies-bodies took 13.041130304336548s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 4.2438507080078125e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.27347588539123535s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.020470619201660156s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 3.170967102050781e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 6.9141387939453125e-06s
INFO | --- Analysis for eu-dgt-tm took 3.059248924255371s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 4.363059997558594e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.2603766918182373s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.02046370506286621s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.510185241699219e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 5.245208740234375e-06s
INFO | --- Analysis for eu-institutions took 5.600122451782227s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 0.7475965023040771s
Availability | VoID file availability check for EU Parliament Media Library took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.2758610248565674s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.02015995979309082s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.457069396972656e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 5.9604644775390625e-06s
INFO | --- Analysis for eu-parliament-media took 6.32822322845459s
Availability | SPARQL endpoint availability check for EU Who Is Who took 0.7274067401885986s
Availability | VoID file availability check for EU Who Is Who took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.2580223083496094s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020299911499023438s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.504753112792969e-05s
Believability | Calculation of trust value for EU Who Is Who took 5.0067901611328125e-06s
INFO | --- Analysis for eu-who-is-who took 8.36151933670044s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 0.7769596576690674s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.2564380168914795s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.020299196243286133s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 3.933906555175781e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for eumida-linked-data took 7.120371341705322s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.3705885410308838s
Availability | VoID file availability check for European Nature Information System took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.258023738861084s
Reputation | Calculation of the PageRank for European Nature Information System took 0.02007603645324707s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00011229515075683594s
Believability | Calculation of trust value for European Nature Information System took 7.867813110351562e-06s
INFO | --- Analysis for eunis took 5.85058856010437s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 4.40928316116333s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.2765014171600342s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.020058155059814453s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 6.961822509765625e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for eur-lex-rdf took 11.88894271850586s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 0.7316994667053223s
Availability | VoID file availability check for Standard Eurobarometer took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.2818105220794678s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.020013093948364258s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.100799560546875e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 6.67572021484375e-06s
INFO | --- Analysis for eurobarometer-standard took 7.721010446548462s
Availability | SPARQL endpoint availability check for European Election Results took 0.7065198421478271s
Availability | VoID file availability check for European Election Results took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for European Election Results took 0.2705872058868408s
Reputation | Calculation of the PageRank for European Election Results took 0.020249605178833008s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.62396240234375e-05s
Believability | Calculation of trust value for European Election Results took 5.245208740234375e-06s
INFO | --- Analysis for european-election-results took 7.00652813911438s
Availability | SPARQL endpoint availability check for EPO patents took 0.42923665046691895s
Availability | VoID file availability check for EPO patents took 0.0006461143493652344s
Extra | Recovery of all triples for EPO patents took 46.63317608833313s
Performance | Total latancy measurement for EPO patents took 1.2276160717010498s
Amount of data | Number of triples check for EPO patents took 90.20457339286804s
Versatility | Languages check for EPO patents took 120.13903450965881s
Interpretability | Number of blank nodes check for EPO patents took 90.28612899780273s
Interpretability | RDF structures check for EPO patents took 0.23257136344909668s
Versatility | Serialization formats check for EPO patents took 0.20416665077209473s
Availability | RDF dump link check for EPO patents took 0.18317008018493652s
License | MR license check for EPO patents took 0.20393157005310059s
License | HR license check for EPO patents took 90.23975801467896s
Amount of data | Number of property check for EPO patents took 0.2423872947692871s
Understandability | Number of label check for EPO patents took 90.18879556655884s
Understandability | URI regex check for EPO patents took 0.4437136650085449s
Understandability | Vocabs check for EPO patents took 0.20931124687194824s
Verifiability | Authors check for EPO patents took 0.4266531467437744s
Verifiability | Publishers check for EPO patents took 0.21676206588745117s
Performance | Throughput check for EPO patents took 10.721129894256592s
Amount of data | Check the number of entities for EPO patents took 8.296966552734375e-05s
Verifiability | Contribs. check for EPO patents took 0.1766960620880127s
Interlinking | sameAs chians check for EPO patents took 0.149216890335083s
Interlinking | skos check for EPO patents took 0.18996977806091309s
Interlinking | skos check for EPO patents took 0.2020251750946045s
Timeliness | dataset update frequency check for EPO patents took 0.16968178749084473s
Currency | Creation date check for EPO patents took 0.37010908126831055s
Currency | Modification date check for EPO patents took 0.479461669921875s
Rep.Conc. | URIs length for EPO patents took 155.0108151435852s
Interoperability | New vocabularies check for EPO patents took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.2668795585632324s
Accuracy | Check Empty annotation labels for EPO patents took 17.524481534957886s
Accuracy | Check White space in annotation for EPO patents took 2.9544520378112793s
Accuracy | Check Datatype consistency for EPO patents took 4.88997745513916s
Consistency | Disjoint class check for EPO patents took 0.1891012191772461s
Consistency | Check Misplaced properties for EPO patents took 120.3620548248291s
Consistency | Check Ontology hijacking for EPO patents took 20.815689086914062s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.492924690246582s
Consistency | Check Invalid usage of undefined properties for EPO patents took 121.49256300926208s
Conciseness | Check Extensional conciseness for EPO patents took 2.83209228515625s
Conciseness | Check Intensional conciseness for EPO patents took 0.33661460876464844s
Security | Sign check for EPO patents took 0.1409316062927246s
Availability | Check URIs Dereferenciability for EPO patents took 1.6259710788726807s
Completeness | Calculation of interlinking completeness for EPO patents took 1.4618480205535889s
Reputation | Calculation of the PageRank for EPO patents took 0.02072882652282715s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for EPO patents took 5.245208740234375e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 1.9073486328125e-06s
Believability | Calculation of trust value for EPO patents took 7.867813110351562e-06s
INFO | --- Analysis for European_Patent_Information took 1312.9013712406158s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 5.5789947509765625e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.7399506568908691s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.020704269409179688s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 3.314018249511719e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 8.821487426757812e-06s
INFO | --- Analysis for europeana-lod took 4.267959117889404s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 4.315376281738281e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.3289196491241455s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.02038860321044922s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.72747802734375e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 6.4373016357421875e-06s
INFO | --- Analysis for europeana-lod-v1 took 8.651512384414673s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.059233665466308594s
Availability | VoID file availability check for Europeana SPARQL took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.7362070083618164s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 5.1021575927734375e-05s
Believability | Calculation of trust value for Europeana SPARQL took 7.62939453125e-06s
INFO | --- Analysis for europeana-sparql took 3.5523338317871094s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.07863235473632812s
Availability | VoID file availability check for EuroSentiment took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.31316184997558594s
Reputation | Calculation of the PageRank for EuroSentiment took 0.02242302894592285s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0010426044464111328s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 4.935264587402344e-05s
Believability | Calculation of trust value for EuroSentiment took 7.3909759521484375e-06s
INFO | --- Analysis for eurosentiment took 3.256603717803955s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 6.341934204101562e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.2558920383453369s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.02033257484436035s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 8.177757263183594e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 5.4836273193359375e-06s
INFO | --- Analysis for eurostat-rdf took 16.086514234542847s
Availability | SPARQL endpoint availability check for EuroVoc took 0.3513820171356201s
Availability | VoID file availability check for EuroVoc took 0.0005972385406494141s
Extra | Recovery of all triples for EuroVoc took 124.02702832221985s
Performance | Total latancy measurement for EuroVoc took 0.5785977840423584s
Amount of data | Number of triples check for EuroVoc took 0.7289412021636963s
Interoperability | New terms check for EuroVoc took 12.0176682472229s
Versatility | Languages check for EuroVoc took 300.05042815208435s
Interpretability | Number of blank nodes check for EuroVoc took 2.025616407394409s
Security | Check HTTPS for EuroVoc took 0.32700586318969727s
Interpretability | RDF structures check for EuroVoc took 0.597733736038208s
Versatility | Serialization formats check for EuroVoc took 2.969792366027832s
Availability | RDF dump link check for EuroVoc took 0.31183815002441406s
License | MR license check for EuroVoc took 0.1910996437072754s
License | HR license check for EuroVoc took 300.0898196697235s
Amount of data | Number of property check for EuroVoc took 0.1695249080657959s
Understandability | Number of label check for EuroVoc took 0.9224047660827637s
Understandability | URI regex check for EuroVoc took 0.2503478527069092s
Understandability | Vocabs check for EuroVoc took 0.09252667427062988s
Verifiability | Authors check for EuroVoc took 0.11989974975585938s
Verifiability | Publishers check for EuroVoc took 0.1619884967803955s
Performance | Throughput check for EuroVoc took 10.534902811050415s
Amount of data | Check the number of entities for EuroVoc took 7.081031799316406e-05s
Verifiability | Contribs. check for EuroVoc took 0.11771845817565918s
Interlinking | sameAs chians check for EuroVoc took 2.183684825897217s
Interlinking | skos check for EuroVoc took 0.647348165512085s
Interlinking | skos check for EuroVoc took 0.14175653457641602s
Timeliness | dataset update frequency check for EuroVoc took 0.20396924018859863s
Currency | Creation date check for EuroVoc took 0.9647560119628906s
Currency | Modification date check for EuroVoc took 0.27623534202575684s
Rep.Conc. | URIs length for EuroVoc took 93.62881207466125s
Interoperability | New vocabularies check for EuroVoc took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.12925171852111816s
Accuracy | Check Functional Property for EuroVoc took 0.23143386840820312s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.18492674827575684s
Accuracy | Check Empty annotation labels for EuroVoc took 36.901013135910034s
Accuracy | Check White space in annotation for EuroVoc took 3.092420816421509s
Accuracy | Check Datatype consistency for EuroVoc took 2.608562707901001s
Consistency | Disjoint class check for EuroVoc took 0.2147688865661621s
Consistency | Check Misplaced properties for EuroVoc took 58.92194199562073s
Consistency | Misplaced classes for EuroVoc took 8.2959566116333s
Consistency | Check Ontology hijacking for EuroVoc took 18.023587942123413s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.3605914115905762s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 57.44232201576233s
Conciseness | Check Extensional conciseness for EuroVoc took 2.9828362464904785s
Conciseness | Check Intensional conciseness for EuroVoc took 0.38597607612609863s
Security | Sign check for EuroVoc took 0.1259448528289795s
Availability | Check URIs Dereferenciability for EuroVoc took 11.138569355010986s
Completeness | Calculation of interlinking completeness for EuroVoc took 1.1120526790618896s
Reputation | Calculation of the PageRank for EuroVoc took 0.02079033851623535s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 8.249282836914062e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 1.6689300537109375e-06s
Believability | Calculation of trust value for EuroVoc took 7.152557373046875e-06s
INFO | --- Analysis for eurovoc took 14055.24972486496s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 4.029273986816406e-05s
Availability | VoID file availability check for EUROVOC in SKOS took 0.0003230571746826172s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 0.28193235397338867s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.020512819290161133s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0010404586791992188s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 4.863739013671875e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 7.3909759521484375e-06s
INFO | --- Analysis for eurovoc-in-skos took 3.9310925006866455s
Availability | SPARQL endpoint availability check for European Television Heritage took 4.267692565917969e-05s
Availability | VoID file availability check for European Television Heritage took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.2697932720184326s
Reputation | Calculation of the PageRank for European Television Heritage took 0.02037835121154785s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0008037090301513672s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 3.3855438232421875e-05s
Believability | Calculation of trust value for European Television Heritage took 7.867813110351562e-06s
INFO | --- Analysis for euscreen took 3.3554024696350098s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 4.267692565917969e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.7014756202697754s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.02036285400390625s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.839897155761719e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 5.4836273193359375e-06s
INFO | --- Analysis for euskadi-farmacias took 6.202006101608276s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.9618277549743652s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0012814998626708984s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.2621755599975586s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.020294904708862305s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.0040740966796875e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 8.106231689453125e-06s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 5.467865705490112s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.34372377395629883s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0007665157318115234s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.2552196979522705s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.02027750015258789s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 9.489059448242188e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 7.62939453125e-06s
INFO | --- Analysis for eutc-productions took 6.852307081222534s
Availability | SPARQL endpoint availability check for EventMedia took 0.3778069019317627s
Availability | VoID file availability check for EventMedia took 0.0006928443908691406s
Completeness | Calculation of interlinking completeness for EventMedia took 0.2821362018585205s
Reputation | Calculation of the PageRank for EventMedia took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00010967254638671875s
Believability | Calculation of trust value for EventMedia took 7.3909759521484375e-06s
INFO | --- Analysis for event-media took 10.550551176071167s
Availability | SPARQL endpoint availability check for EventKG took 0.00010323524475097656s
Availability | VoID file availability check for EventKG took 0.0006575584411621094s
Completeness | Calculation of interlinking completeness for EventKG took 0.25402283668518066s
Reputation | Calculation of the PageRank for EventKG took 0.020496845245361328s
Interlinking | Calculation of Degree of Connection for EventKG took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.726119995117188e-05s
Believability | Calculation of trust value for EventKG took 6.9141387939453125e-06s
INFO | --- Analysis for eventkg took 4.7617809772491455s
Availability | SPARQL endpoint availability check for Eventseer took 3.213209867477417s
Availability | VoID file availability check for Eventseer took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for Eventseer took 0.24125409126281738s
Reputation | Calculation of the PageRank for Eventseer took 0.020311355590820312s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.57763671875e-05s
Believability | Calculation of trust value for Eventseer took 7.62939453125e-06s
INFO | --- Analysis for eventseer took 5.6736836433410645s
Availability | SPARQL endpoint availability check for Face Link took 4.124641418457031e-05s
Availability | VoID file availability check for Face Link took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for Face Link took 0.2726602554321289s
Reputation | Calculation of the PageRank for Face Link took 0.021108388900756836s
Interlinking | Calculation of Degree of Connection for Face Link took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.504753112792969e-05s
Believability | Calculation of trust value for Face Link took 1.1920928955078125e-05s
INFO | --- Analysis for Face_Link took 2.3590235710144043s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 4.220008850097656e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.2665994167327881s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 3.0994415283203125e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 7.152557373046875e-06s
INFO | --- Analysis for facebook-lids took 3.024122714996338s
Availability | SPARQL endpoint availability check for Fact Forge took 4.029273986816406e-05s
Availability | VoID file availability check for Fact Forge took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.27881550788879395s
Reputation | Calculation of the PageRank for Fact Forge took 0.02040266990661621s
Interlinking | Calculation of Degree of Connection for Fact Forge took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fact Forge took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 3.170967102050781e-05s
Believability | Calculation of trust value for Fact Forge took 7.3909759521484375e-06s
INFO | --- Analysis for fact-forge took 2.9486806392669678s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 393.05887961387634s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0002951622009277344s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.27606701850891113s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.020843982696533203s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 4.38690185546875e-05s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.2159347534179688e-05s
INFO | --- Analysis for FADN_(2019) took 668.0277376174927s
Availability | SPARQL endpoint availability check for FAMEData took 4.5299530029296875e-05s
Availability | VoID file availability check for FAMEData took 0.0006487369537353516s
Completeness | Calculation of interlinking completeness for FAMEData took 0.2749505043029785s
Reputation | Calculation of the PageRank for FAMEData took 0.020613431930541992s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0008330345153808594s
Interlinking | Calculation of Clustering coefficient for FAMEData took 3.075599670410156e-05s
Believability | Calculation of trust value for FAMEData took 6.67572021484375e-06s
INFO | --- Analysis for famedata took 4.5987536907196045s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 0.00011086463928222656s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0007252693176269531s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.6997661590576172s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.02004218101501465s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 9.274482727050781e-05s
Believability | Calculation of trust value for FAO geopolitical ontology took 5.4836273193359375e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 10.742225646972656s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.2674860954284668s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.25543832778930664s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.020179271697998047s
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.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00010061264038085938s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for fao-linked-data took 2.7368035316467285s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 4.2438507080078125e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.27873849868774414s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.020078420639038086s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 2.9325485229492188e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 6.9141387939453125e-06s
INFO | --- Analysis for FAO_species took 2.831470489501953s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.612984895706177s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.26242661476135254s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.020218610763549805s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.124641418457031e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 6.9141387939453125e-06s
INFO | --- Analysis for farmbio-chembl took 65.01748442649841s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 5.030632019042969e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.7894458770751953s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.020551204681396484s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 3.24249267578125e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 7.62939453125e-06s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 4.423322916030884s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 4.076957702636719e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.00032138824462890625s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.27370619773864746s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.020038604736328125s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 2.765655517578125e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for farolapp-dataset took 3.3538808822631836s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 4.0531158447265625e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.2587897777557373s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.02070331573486328s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Fatal Traffic Accidents in greek roads took 2.7418136596679688e-05s
Believability | Calculation of trust value for Fatal Traffic Accidents in greek roads took 6.9141387939453125e-06s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 2.973731756210327s
Availability | SPARQL endpoint availability check for I4.0-Onto took 4.100799560546875e-05s
Availability | VoID file availability check for I4.0-Onto took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.26357293128967285s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.020273923873901367s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 2.86102294921875e-05s
Believability | Calculation of trust value for I4.0-Onto took 6.4373016357421875e-06s
INFO | --- Analysis for fatimazahra took 2.41120982170105s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 4.0531158447265625e-05s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 0.269268274307251s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.020094871520996094s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 2.8848648071289062e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 7.62939453125e-06s
INFO | --- Analysis for federal-economic-rdf took 3.357220411300659s
Availability | SPARQL endpoint availability check for Feed Wrapper took 5.030632019042969e-05s
Availability | VoID file availability check for Feed Wrapper took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 0.2834200859069824s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.020077228546142578s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 2.765655517578125e-05s
Believability | Calculation of trust value for Feed Wrapper took 1.1444091796875e-05s
INFO | --- Analysis for feedwrapper-lids took 3.4165713787078857s
Availability | SPARQL endpoint availability check for FHIR STU3 took 4.2438507080078125e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.24275660514831543s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.020185232162475586s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 2.7418136596679688e-05s
Believability | Calculation of trust value for FHIR STU3 took 1.1682510375976562e-05s
INFO | --- Analysis for FHIR_STU3 took 3.131701946258545s
Availability | SPARQL endpoint availability check for FiESTA took 4.291534423828125e-05s
Availability | VoID file availability check for FiESTA took 0.0006265640258789062s
Completeness | Calculation of interlinking completeness for FiESTA took 0.28896570205688477s
Reputation | Calculation of the PageRank for FiESTA took 0.02016925811767578s
Interlinking | Calculation of Degree of Connection for FiESTA took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for FiESTA took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for FiESTA took 3.647804260253906e-05s
Believability | Calculation of trust value for FiESTA took 6.9141387939453125e-06s
INFO | --- Analysis for fiesta took 12.584516286849976s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.267692565917969e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.25224924087524414s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.020168304443359375s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 2.9802322387695312e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 7.3909759521484375e-06s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 2.375718355178833s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 4.3392181396484375e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.2764613628387451s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.020146608352661133s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 7.009506225585938e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 5.245208740234375e-06s
INFO | --- Analysis for finnish-municipalities took 5.307304620742798s
Availability | SPARQL endpoint availability check for firmao took 4.0531158447265625e-05s
Availability | VoID file availability check for firmao took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for firmao took 0.26421380043029785s
Reputation | Calculation of the PageRank for firmao took 0.02024364471435547s
Interlinking | Calculation of Degree of Connection for firmao took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for firmao took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for firmao took 2.956390380859375e-05s
Believability | Calculation of trust value for firmao took 8.344650268554688e-06s
INFO | --- Analysis for firmao took 2.914846658706665s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.27211618423461914s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.020251750946044922s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 2.8371810913085938e-05s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 8.58306884765625e-06s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 2.865816116333008s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 392.5494029521942s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 0.27506351470947266s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.02091217041015625s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 4.124641418457031e-05s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 8.106231689453125e-06s
INFO | --- Analysis for Fishery_Stock_Dataset took 667.5196759700775s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.291534423828125e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.7000002861022949s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.020625591278076172s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.726119995117188e-05s
Believability | Calculation of trust value for Fishes of Texas took 8.106231689453125e-06s
INFO | --- Analysis for fishes-of-texas took 4.560054063796997s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.172325134277344e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.6727776527404785s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.020687580108642578s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007941722869873047s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 0.00011324882507324219s
Believability | Calculation of trust value for flickr? wrappr took 7.62939453125e-06s
INFO | --- Analysis for flickr-wrappr took 4.889130592346191s
Availability | SPARQL endpoint availability check for flickr.person took 4.0531158447265625e-05s
Availability | VoID file availability check for flickr.person took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for flickr.person took 0.2797505855560303s
Reputation | Calculation of the PageRank for flickr.person took 0.020361661911010742s
Interlinking | Calculation of Degree of Connection for flickr.person took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for flickr.person took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for flickr.person took 3.075599670410156e-05s
Believability | Calculation of trust value for flickr.person took 8.106231689453125e-06s
INFO | --- Analysis for flickr_person took 3.398456573486328s
Availability | SPARQL endpoint availability check for flickr.videoobject took 3.886222839355469e-05s
Availability | VoID file availability check for flickr.videoobject took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 0.6923606395721436s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.020430326461791992s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 3.1948089599609375e-05s
Believability | Calculation of trust value for flickr.videoobject took 8.106231689453125e-06s
INFO | --- Analysis for flickr_videoobject took 3.372281074523926s
Availability | SPARQL endpoint availability check for Future land use simulation model took 4.029273986816406e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.7206437587738037s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 2.8848648071289062e-05s
Believability | Calculation of trust value for Future land use simulation model took 6.198883056640625e-06s
INFO | --- Analysis for FLUS took 129.36952757835388s
Availability | SPARQL endpoint availability check for Fly-TED took 4.0531158447265625e-05s
Availability | VoID file availability check for Fly-TED took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.705359697341919s
Reputation | Calculation of the PageRank for Fly-TED took 0.020313739776611328s
Interlinking | Calculation of Degree of Connection for Fly-TED took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Fly-TED took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 2.956390380859375e-05s
Believability | Calculation of trust value for Fly-TED took 6.4373016357421875e-06s
INFO | --- Analysis for fly-ted took 3.7412986755371094s
Availability | SPARQL endpoint availability check for FlyAtlas took 3.8623809814453125e-05s
Availability | VoID file availability check for FlyAtlas took 0.0002219676971435547s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.26972532272338867s
Reputation | Calculation of the PageRank for FlyAtlas took 0.02039337158203125s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 2.8848648071289062e-05s
Believability | Calculation of trust value for FlyAtlas took 6.9141387939453125e-06s
INFO | --- Analysis for flyatlas took 3.48942232131958s
Availability | SPARQL endpoint availability check for Flybase took 1.7546606063842773s
Availability | VoID file availability check for Flybase took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for Flybase took 0.7339975833892822s
Reputation | Calculation of the PageRank for Flybase took 0.020336389541625977s
Interlinking | Calculation of Degree of Connection for Flybase took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.409385681152344e-05s
Believability | Calculation of trust value for Flybase took 6.198883056640625e-06s
INFO | --- Analysis for flybase took 10.887721300125122s
Availability | SPARQL endpoint availability check for Flyted took 1.4722521305084229s
Availability | VoID file availability check for Flyted took 0.0006256103515625s
Completeness | Calculation of interlinking completeness for Flyted took 0.24426627159118652s
Reputation | Calculation of the PageRank for Flyted took 0.02040839195251465s
Interlinking | Calculation of Degree of Connection for Flyted took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.170967102050781e-05s
Believability | Calculation of trust value for Flyted took 7.62939453125e-06s
INFO | --- Analysis for flyted took 11.529720783233643s
Availability | SPARQL endpoint availability check for Foodista took 1.0659401416778564s
Availability | VoID file availability check for Foodista took 0.00041484832763671875s
Completeness | Calculation of interlinking completeness for Foodista took 0.2543773651123047s
Reputation | Calculation of the PageRank for Foodista took 0.020581722259521484s
Interlinking | Calculation of Degree of Connection for Foodista took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Foodista took 2.9325485229492188e-05s
Believability | Calculation of trust value for Foodista took 6.67572021484375e-06s
INFO | --- Analysis for foodista took 9.97283148765564s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.19104838371276855s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.2804136276245117s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.020318269729614258s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.867813110351562e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.152557373046875e-06s
INFO | --- Analysis for foodpedia took 3.1091184616088867s
Availability | SPARQL endpoint availability check for FORGE Course information took 4.076957702636719e-05s
Availability | VoID file availability check for FORGE Course information took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.27228307723999023s
Reputation | Calculation of the PageRank for FORGE Course information took 0.020148754119873047s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 2.86102294921875e-05s
Believability | Calculation of trust value for FORGE Course information took 7.62939453125e-06s
INFO | --- Analysis for forge-course-information took 3.4907171726226807s
Availability | SPARQL endpoint availability check for FrameBase schema took 4.172325134277344e-05s
Availability | VoID file availability check for FrameBase schema took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.25812816619873047s
Reputation | Calculation of the PageRank for FrameBase schema took 0.020503759384155273s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0008249282836914062s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.553794860839844e-05s
Believability | Calculation of trust value for FrameBase schema took 7.62939453125e-06s
INFO | --- Analysis for framebase-schema took 3.0666511058807373s
Availability | SPARQL endpoint availability check for FrameNet took 4.00543212890625e-05s
Availability | VoID file availability check for FrameNet took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for FrameNet took 0.26036953926086426s
Reputation | Calculation of the PageRank for FrameNet took 0.020285606384277344s
Interlinking | Calculation of Degree of Connection for FrameNet took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for FrameNet took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for FrameNet took 2.8371810913085938e-05s
Believability | Calculation of trust value for FrameNet took 8.58306884765625e-06s
INFO | --- Analysis for framenet took 2.9601380825042725s
Availability | SPARQL endpoint availability check for Framester took 8.7738037109375e-05s
Availability | VoID file availability check for Framester took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Framester took 0.26570725440979004s
Reputation | Calculation of the PageRank for Framester took 0.02012491226196289s
Interlinking | Calculation of Degree of Connection for Framester took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Framester took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Framester took 7.343292236328125e-05s
Believability | Calculation of trust value for Framester took 7.152557373046875e-06s
INFO | --- Analysis for framester took 3.400392532348633s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.1587967872619629s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.2637209892272949s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.020114660263061523s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.559226989746094e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 6.4373016357421875e-06s
INFO | --- Analysis for frb-linked-data took 2.620389461517334s
Availability | SPARQL endpoint availability check for Freebase took 4.124641418457031e-05s
Availability | VoID file availability check for Freebase took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for Freebase took 0.28133106231689453s
Reputation | Calculation of the PageRank for Freebase took 0.020157575607299805s
Interlinking | Calculation of Degree of Connection for Freebase took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Freebase took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.00026917457580566406s
Believability | Calculation of trust value for Freebase took 8.58306884765625e-06s
INFO | --- Analysis for freebase took 3.933321952819824s
Availability | SPARQL endpoint availability check for Freeyork took 4.7206878662109375e-05s
Availability | VoID file availability check for Freeyork took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Freeyork took 0.24801421165466309s
Reputation | Calculation of the PageRank for Freeyork took 0.020430326461791992s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010395050048828125s
Believability | Calculation of trust value for Freeyork took 6.4373016357421875e-06s
INFO | --- Analysis for freeyork-org took 3.0078344345092773s
Availability | SPARQL endpoint availability check for French School Program took 5.2928924560546875e-05s
Availability | VoID file availability check for French School Program took 0.0003871917724609375s
Completeness | Calculation of interlinking completeness for French School Program took 0.23410391807556152s
Reputation | Calculation of the PageRank for French School Program took 0.020710229873657227s
Interlinking | Calculation of Degree of Connection for French School Program took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for French School Program took 0.0009062290191650391s
Interlinking | Calculation of Clustering coefficient for French School Program took 3.504753112792969e-05s
Believability | Calculation of trust value for French School Program took 7.152557373046875e-06s
INFO | --- Analysis for french-school-program took 2.905707836151123s
Availability | SPARQL endpoint availability check for French School System took 3.9577484130859375e-05s
Availability | VoID file availability check for French School System took 0.00022339820861816406s
Completeness | Calculation of interlinking completeness for French School System took 0.2857985496520996s
Reputation | Calculation of the PageRank for French School System took 0.02017068862915039s
Interlinking | Calculation of Degree of Connection for French School System took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for French School System took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for French School System took 3.24249267578125e-05s
Believability | Calculation of trust value for French School System took 6.4373016357421875e-06s
INFO | --- Analysis for french-school-system took 2.9446427822113037s
Availability | SPARQL endpoint availability check for French TimeBank took 5.316734313964844e-05s
Availability | VoID file availability check for French TimeBank took 0.0002162456512451172s
Completeness | Calculation of interlinking completeness for French TimeBank took 0.3179457187652588s
Reputation | Calculation of the PageRank for French TimeBank took 0.02054309844970703s
Interlinking | Calculation of Degree of Connection for French TimeBank took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for French TimeBank took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 2.9802322387695312e-05s
Believability | Calculation of trust value for French TimeBank took 6.67572021484375e-06s
INFO | --- Analysis for french-timebank took 2.9402360916137695s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.7658371925354004s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.25024843215942383s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.020181655883789062s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.319450378417969e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 4.76837158203125e-06s
INFO | --- Analysis for fu-berlin-cordis took 4.536450624465942s
Availability | SPARQL endpoint availability check for DailyMed took 0.7433249950408936s
Availability | VoID file availability check for DailyMed took 0.0006093978881835938s
Completeness | Calculation of interlinking completeness for DailyMed took 0.29329872131347656s
Reputation | Calculation of the PageRank for DailyMed took 0.020068645477294922s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.417533874511719e-05s
Believability | Calculation of trust value for DailyMed took 5.9604644775390625e-06s
INFO | --- Analysis for fu-berlin-dailymed took 5.756010293960571s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.7110500335693359s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.2691066265106201s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.02050614356994629s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.630752563476562e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 1.0251998901367188e-05s
INFO | --- Analysis for fu-berlin-dblp took 4.381222486495972s
Availability | SPARQL endpoint availability check for Diseasome took 0.7130410671234131s
Availability | VoID file availability check for Diseasome took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Diseasome took 0.31714963912963867s
Reputation | Calculation of the PageRank for Diseasome took 0.020157575607299805s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.0001068115234375s
Believability | Calculation of trust value for Diseasome took 6.4373016357421875e-06s
INFO | --- Analysis for fu-berlin-diseasome took 5.78990364074707s
Availability | SPARQL endpoint availability check for DrugBank took 0.6933155059814453s
Availability | VoID file availability check for DrugBank took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for DrugBank took 0.23523950576782227s
Reputation | Calculation of the PageRank for DrugBank took 0.020366191864013672s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011444091796875s
Believability | Calculation of trust value for DrugBank took 6.67572021484375e-06s
INFO | --- Analysis for fu-berlin-drugbank took 5.537217617034912s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.7176187038421631s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.2600574493408203s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.020196199417114258s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 3.123283386230469e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 6.67572021484375e-06s
INFO | --- Analysis for fu-berlin-ec-competition took 4.465829133987427s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.7467513084411621s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0007266998291015625s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.2670567035675049s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.020146608352661133s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.414817810058594e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 5.4836273193359375e-06s
INFO | --- Analysis for fu-berlin-euraxess took 4.508966445922852s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.707056999206543s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.25479793548583984s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.020134925842285156s
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.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.200241088867188e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 4.76837158203125e-06s
INFO | --- Analysis for fu-berlin-eures took 4.453293800354004s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.7426495552062988s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0005898475646972656s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.24746179580688477s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.021136999130249023s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.584426879882812e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 4.76837158203125e-06s
INFO | --- Analysis for fu-berlin-eurostat took 5.101520299911499s
Availability | SPARQL endpoint availability check for MediCare took 0.7627241611480713s
Availability | VoID file availability check for MediCare took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for MediCare took 0.2635934352874756s
Reputation | Calculation of the PageRank for MediCare took 0.02051568031311035s
Interlinking | Calculation of Degree of Connection for MediCare took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for MediCare took 3.933906555175781e-05s
Believability | Calculation of trust value for MediCare took 5.4836273193359375e-06s
INFO | --- Analysis for fu-berlin-medicare took 5.180881977081299s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.7446613311767578s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.2908174991607666s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.02037334442138672s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.319450378417969e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 9.298324584960938e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 4.5297532081604s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.7135753631591797s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.24912548065185547s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.02030467987060547s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.179115295410156e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-sider took 5.0657899379730225s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.75588059425354s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.26082324981689453s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020256519317626953s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.843971252441406e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-stitch took 4.477414608001709s
Availability | SPARQL endpoint availability check for fvdb took 4.220008850097656e-05s
Availability | VoID file availability check for fvdb took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for fvdb took 0.26831579208374023s
Reputation | Calculation of the PageRank for fvdb took 0.020218372344970703s
Interlinking | Calculation of Degree of Connection for fvdb took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for fvdb took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for fvdb took 2.9802322387695312e-05s
Believability | Calculation of trust value for fvdb took 6.198883056640625e-06s
INFO | --- Analysis for fv took 12.509698390960693s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 4.315376281738281e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.24072790145874023s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.020548343658447266s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 2.8848648071289062e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 6.9141387939453125e-06s
INFO | --- Analysis for GACS took 3.076653242111206s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 4.100799560546875e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.26963114738464355s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.020537614822387695s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 3.0517578125e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 7.62939453125e-06s
INFO | --- Analysis for galen_from_co-odeorg took 3.065950393676758s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 4.172325134277344e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007140636444091797s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.27094578742980957s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.02044081687927246s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 3.886222839355469e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 1.049041748046875e-05s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 5.288228750228882s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 4.124641418457031e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0003674030303955078s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.26726579666137695s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.020951032638549805s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0010616779327392578s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.00011587142944335938s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 7.3909759521484375e-06s
INFO | --- Analysis for garnicaplywood took 3.3767409324645996s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 4.220008850097656e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.28438758850097656s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.020182371139526367s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.274482727050781e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 7.62939453125e-06s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 7.252872705459595s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.402925968170166s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0003552436828613281s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.2629721164703369s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.020267248153686523s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 9.274482727050781e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for gemet took 4.921226501464844s
Availability | SPARQL endpoint availability check for gemet-annotated took 4.220008850097656e-05s
Availability | VoID file availability check for gemet-annotated took 0.0004260540008544922s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.272174596786499s
Reputation | Calculation of the PageRank for gemet-annotated took 0.020890235900878906s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0009050369262695312s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.9577484130859375e-05s
Believability | Calculation of trust value for gemet-annotated took 7.62939453125e-06s
INFO | --- Analysis for gemet-annotated took 2.959365129470825s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.7681314945220947s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.2654533386230469s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.020072460174560547s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 3.62396240234375e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 7.867813110351562e-06s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.148158073425293s
Availability | SPARQL endpoint availability check for Super Ontology took 1.0944483280181885s
Availability | VoID file availability check for Super Ontology took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.26878905296325684s
Reputation | Calculation of the PageRank for Super Ontology took 0.020092487335205078s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 2.7179718017578125e-05s
Believability | Calculation of trust value for Super Ontology took 1.239776611328125e-05s
INFO | --- Analysis for Generalized_Super_Ontology took 5.589146852493286s
Availability | SPARQL endpoint availability check for geo.place took 3.981590270996094e-05s
Availability | VoID file availability check for geo.place took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for geo.place took 0.2798287868499756s
Reputation | Calculation of the PageRank for geo.place took 0.020125389099121094s
Interlinking | Calculation of Degree of Connection for geo.place took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for geo.place took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for geo.place took 2.6941299438476562e-05s
Believability | Calculation of trust value for geo.place took 7.3909759521484375e-06s
INFO | --- Analysis for geo_place took 2.8710861206054688s
Availability | SPARQL endpoint availability check for Geographic detector model took 4.172325134277344e-05s
Availability | VoID file availability check for Geographic detector model took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.26622438430786133s
Reputation | Calculation of the PageRank for Geographic detector model took 0.020837783813476562s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 2.765655517578125e-05s
Believability | Calculation of trust value for Geographic detector model took 6.67572021484375e-06s
INFO | --- Analysis for GeoDetector took 12.024456262588501s
Availability | SPARQL endpoint availability check for geodomainwn took 4.100799560546875e-05s
Availability | VoID file availability check for geodomainwn took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.28359198570251465s
Reputation | Calculation of the PageRank for geodomainwn took 0.02008962631225586s
Interlinking | Calculation of Degree of Connection for geodomainwn took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for geodomainwn took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 4.38690185546875e-05s
Believability | Calculation of trust value for geodomainwn took 6.198883056640625e-06s
INFO | --- Analysis for geodomainwn took 6.7832770347595215s
Availability | SPARQL endpoint availability check for GeoEcuador took 4.124641418457031e-05s
Availability | VoID file availability check for GeoEcuador took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.272136926651001s
Reputation | Calculation of the PageRank for GeoEcuador took 0.020391225814819336s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 7.2479248046875e-05s
Believability | Calculation of trust value for GeoEcuador took 7.62939453125e-06s
INFO | --- Analysis for geoecuador took 12.489003896713257s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.076443910598755s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0006146430969238281s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.2718935012817383s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.020016908645629883s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 6.508827209472656e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 6.67572021484375e-06s
INFO | --- Analysis for geographic-names-information-system-gnis took 47.50671124458313s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 4.00543212890625e-05s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.2593376636505127s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.02027583122253418s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 2.8133392333984375e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 7.62939453125e-06s
INFO | --- Analysis for geographic-openuplabs took 2.8924474716186523s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.527524471282959s
Availability | VoID file availability check for GeoLinkedData took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.24303817749023438s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.020078182220458984s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 8.58306884765625e-05s
Believability | Calculation of trust value for GeoLinkedData took 4.76837158203125e-06s
INFO | --- Analysis for geolinkeddata took 3.870699167251587s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.25716519355773926s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0005266666412353516s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 8.562416076660156s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.3718068599700928s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.14928078651428223s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.3118274211883545s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.20584845542907715s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.15967655181884766s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.20070576667785645s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.09199166297912598s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.09920644760131836s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.06108665466308594s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.09888625144958496s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 2.062490940093994s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.11002850532531738s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.09755754470825195s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.14528608322143555s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.09675765037536621s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.06197190284729004s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.10472440719604492s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.33509612083435s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 7.2479248046875e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.0627894401550293s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.06858634948730469s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.1033475399017334s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.0692751407623291s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.06955838203430176s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.160630464553833s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.16900062561035156s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.3072309494018555s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 1.9830961227416992s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.10427975654602051s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06100773811340332s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06909608840942383s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.2956399917602539s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.0073583126068115234s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.22693109512329102s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.07741999626159668s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.2023918628692627s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5280165672302246s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 2.721482276916504s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.334594488143921s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.4698750972747803s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.17627954483032227s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.06850147247314453s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 1.0503292083740234s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.3656301498413086s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.02008676528930664s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 9.179115295410156e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 2.402278423309326s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 114.70637607574463s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 4.5299530029296875e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.2896709442138672s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.020343303680419922s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0004703998565673828s
Believability | Calculation of trust value for GeoNames Semantic Web took 9.059906005859375e-06s
INFO | --- Analysis for geonames-semantic-web took 3.264901638031006s
Availability | SPARQL endpoint availability check for Geospatial World  took 4.1961669921875e-05s
Availability | VoID file availability check for Geospatial World  took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.2893562316894531s
Reputation | Calculation of the PageRank for Geospatial World  took 0.020799875259399414s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0009481906890869141s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.000125885009765625s
Believability | Calculation of trust value for Geospatial World  took 8.106231689453125e-06s
INFO | --- Analysis for geospatialworld-net took 3.0116097927093506s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.5844132900238037s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0006289482116699219s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.2832939624786377s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.020450353622436523s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.0001442432403564453s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 7.867813110351562e-06s
INFO | --- Analysis for geospecies took 5.967442274093628s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.2438507080078125e-05s
Availability | VoID file availability check for GeoWordNet took 0.0007641315460205078s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.2725224494934082s
Reputation | Calculation of the PageRank for GeoWordNet took 0.02022695541381836s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 5.2928924560546875e-05s
Believability | Calculation of trust value for GeoWordNet took 6.9141387939453125e-06s
INFO | --- Analysis for geowordnet took 7.512585878372192s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.0837092399597168s
Availability | VoID file availability check for German labor law thesaurus took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.25720715522766113s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.021244525909423828s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 0.00013375282287597656s
Believability | Calculation of trust value for German labor law thesaurus took 7.62939453125e-06s
INFO | --- Analysis for german-labor-law-thesaurus took 2.526160717010498s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.291534423828125e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.28786540031433105s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.02066659927368164s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.172325134277344e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 7.3909759521484375e-06s
INFO | --- Analysis for germlex took 2.818922519683838s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 2.26806378364563s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.2668945789337158s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020392417907714844s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 8.96453857421875e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 7.867813110351562e-06s
INFO | --- Analysis for gesis-thesoz took 7.370445251464844s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.8425533771514893s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.2737879753112793s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.020456790924072266s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.700920104980469e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for getty-aat took 15.080120325088501s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.2204184532165527s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.2750833034515381s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.02046823501586914s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.316734313964844e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 6.67572021484375e-06s
INFO | --- Analysis for getty-tgn took 11.448806285858154s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 0.35236454010009766s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.2601637840270996s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.020943641662597656s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0008330345153808594s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.719329833984375e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 5.7220458984375e-06s
INFO | --- Analysis for gipuzkoademografia took 2.898916244506836s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 4.3392181396484375e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0006000995635986328s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.24746346473693848s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.020156383514404297s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 2.9325485229492188e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 6.9141387939453125e-06s
INFO | --- Analysis for glastonbury-2011 took 5.5998430252075195s
Availability | SPARQL endpoint availability check for Global Change Information System took 3.981590270996094e-05s
Availability | VoID file availability check for Global Change Information System took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.26375579833984375s
Reputation | Calculation of the PageRank for Global Change Information System took 0.02105569839477539s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 3.123283386230469e-05s
Believability | Calculation of trust value for Global Change Information System took 6.67572021484375e-06s
INFO | --- Analysis for global-change-information-system took 2.882094621658325s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 4.220008850097656e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.24792098999023438s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.020521163940429688s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 7.104873657226562e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 6.198883056640625e-06s
INFO | --- Analysis for global-hunger-index-2011 took 2.916290044784546s
Availability | SPARQL endpoint availability check for Glottolog took 4.458427429199219e-05s
Availability | VoID file availability check for Glottolog took 0.0006020069122314453s
Completeness | Calculation of interlinking completeness for Glottolog took 0.2909057140350342s
Reputation | Calculation of the PageRank for Glottolog took 0.020355224609375s
Interlinking | Calculation of Degree of Connection for Glottolog took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Glottolog took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Glottolog took 5.1975250244140625e-05s
Believability | Calculation of trust value for Glottolog took 6.198883056640625e-06s
INFO | --- Analysis for glottolog took 6.628232955932617s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 4.220008850097656e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.2811300754547119s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.020373106002807617s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00010514259338378906s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 6.9141387939453125e-06s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 9.174444913864136s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 4.1484832763671875e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.24240446090698242s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.020148038864135742s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 2.9087066650390625e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 7.62939453125e-06s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 2.8956410884857178s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 4.076957702636719e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.34107279777526855s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.020400047302246094s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 3.075599670410156e-05s
Believability | Calculation of trust value for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 7.62939453125e-06s
INFO | --- Analysis for go_annotations_from_ncbi_and_ebi took 3.0267281532287598s
Availability | SPARQL endpoint availability check for 1121 took 4.2438507080078125e-05s
Availability | VoID file availability check for 1121 took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for 1121 took 0.2631411552429199s
Reputation | Calculation of the PageRank for 1121 took 0.020371437072753906s
Interlinking | Calculation of Degree of Connection for 1121 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 1121 took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for 1121 took 2.9325485229492188e-05s
Believability | Calculation of trust value for 1121 took 6.9141387939453125e-06s
INFO | --- Analysis for God_ took 3.203709363937378s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 4.220008850097656e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.25704073905944824s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020163774490356445s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.0067901611328125e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 9.298324584960938e-06s
INFO | --- Analysis for gold took 4.074986934661865s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 4.363059997558594e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.25282883644104004s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.651878356933594e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 6.9141387939453125e-06s
INFO | --- Analysis for googleart-wrapper took 2.6785101890563965s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.0968923568725586s
Availability | VoID file availability check for GovAgriBus Denmark took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.25231099128723145s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.02027130126953125s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.910064697265625e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 8.106231689453125e-06s
INFO | --- Analysis for govagribus-denmark took 34.73953676223755s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.407870292663574s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.000667572021484375s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.26755857467651367s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020652055740356445s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 8.630752563476562e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 23.984012842178345s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.645728349685669s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0006625652313232422s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.2847602367401123s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.020315885543823242s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 9.489059448242188e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 5.9604644775390625e-06s
INFO | --- Analysis for govtrack took 35.79880332946777s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 4.291534423828125e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.28058719635009766s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.02025747299194336s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 5.9604644775390625e-05s
Believability | Calculation of trust value for greek-administrative-geography took 7.867813110351562e-06s
INFO | --- Analysis for greek-administrative-geography took 2.6973867416381836s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.3048994541168213s
Availability | VoID file availability check for Greek Wordnet took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.281282901763916s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.020346879959106445s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 3.933906555175781e-05s
Believability | Calculation of trust value for Greek Wordnet took 7.152557373046875e-06s
INFO | --- Analysis for greek-wordnet took 2.731208086013794s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 2.8784642219543457s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0006115436553955078s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.2613511085510254s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.02018284797668457s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.239776611328125e-05s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 7.867813110351562e-06s
INFO | --- Analysis for greek_prisons_releases took 7.022862672805786s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.8324711322784424s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.2914092540740967s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020056486129760742s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.414817810058594e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 7.152557373046875e-06s
INFO | --- Analysis for greekchildrensartmuseum took 4.3988354206085205s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 5.555152893066406e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0007364749908447266s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.26874303817749023s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.020018815994262695s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 9.989738464355469e-05s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 6.9141387939453125e-06s
INFO | --- Analysis for green-competitiveness-gnoss took 6.5242955684661865s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 2.0521557331085205s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.2863643169403076s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.02032470703125s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.5299530029296875e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 2.193450927734375e-05s
INFO | --- Analysis for grrp took 4.542459487915039s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.1348116397857666s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.2555124759674072s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.020132064819335938s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.699562072753906e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 5.0067901611328125e-06s
INFO | --- Analysis for grrt took 3.506063938140869s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.1614315509796143s
Availability | VoID file availability check for Geological Timescale took 0.0006501674652099609s
Extra | Recovery of all triples for Geological Timescale took 5.1665520668029785s
Performance | Total latancy measurement for Geological Timescale took 3.345510244369507s
Amount of data | Number of triples check for Geological Timescale took 0.9520168304443359s
Interoperability | New terms check for Geological Timescale took 2.181866407394409s
Versatility | Languages check for Geological Timescale took 1.0738070011138916s
Interpretability | Number of blank nodes check for Geological Timescale took 0.9990413188934326s
Security | Check HTTPS for Geological Timescale took 0.8986995220184326s
Interpretability | RDF structures check for Geological Timescale took 0.9541630744934082s
Versatility | Serialization formats check for Geological Timescale took 0.7155907154083252s
Availability | RDF dump link check for Geological Timescale took 1.1230862140655518s
License | MR license check for Geological Timescale took 0.935335636138916s
License | HR license check for Geological Timescale took 0.9863433837890625s
Amount of data | Number of property check for Geological Timescale took 0.4226651191711426s
Understandability | Number of label check for Geological Timescale took 0.40612030029296875s
Understandability | URI regex check for Geological Timescale took 0.7643513679504395s
Understandability | Vocabs check for Geological Timescale took 0.34784531593322754s
Verifiability | Authors check for Geological Timescale took 0.9112687110900879s
Verifiability | Publishers check for Geological Timescale took 0.3922243118286133s
Performance | Throughput check for Geological Timescale took 17.952304363250732s
Amount of data | Check the number of entities for Geological Timescale took 0.017743349075317383s
Verifiability | Contribs. check for Geological Timescale took 0.9972324371337891s
Interlinking | sameAs chians check for Geological Timescale took 1.859750509262085s
Interlinking | skos check for Geological Timescale took 2.0216240882873535s
Interlinking | skos check for Geological Timescale took 0.42211222648620605s
Timeliness | dataset update frequency check for Geological Timescale took 0.7298831939697266s
Currency | Creation date check for Geological Timescale took 2.985712766647339s
Currency | Modification date check for Geological Timescale took 0.932734489440918s
Rep.Conc. | URIs length for Geological Timescale took 1.4961810111999512s
Interoperability | New vocabularies check for Geological Timescale took 3.052922248840332s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 0.40910983085632324s
Accuracy | Check Functional Property for Geological Timescale took 0.9314689636230469s
Accuracy | Check Inverse Functional Property for Geological Timescale took 0.4014604091644287s
Accuracy | Check Empty annotation labels for Geological Timescale took 0.7190265655517578s
Accuracy | Check White space in annotation for Geological Timescale took 0.019321680068969727s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07301115989685059s
Consistency | Disjoint class check for Geological Timescale took 0.9213356971740723s
Consistency | Check Misplaced properties for Geological Timescale took 1.375946044921875s
Consistency | Misplaced classes for Geological Timescale took 1.4439492225646973s
Consistency | Check Ontology hijacking for Geological Timescale took 2.1824469566345215s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.1562395095825195s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 2.144606828689575s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.04998898506164551s
Conciseness | Check Intensional conciseness for Geological Timescale took 0.9248640537261963s
Security | Sign check for Geological Timescale took 4.060950517654419s
Availability | Check URIs Dereferenciability for Geological Timescale took 2.8588063716888428s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.3168792724609375s
Reputation | Calculation of the PageRank for Geological Timescale took 0.02134227752685547s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0009632110595703125s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 9.393692016601562e-05s
Interoperability | Check the re-using of existing vocabs for Geological Timescale took 2.2420902252197266s
Believability | Calculation of trust value for Geological Timescale took 6.9141387939453125e-06s
INFO | --- Analysis for GTS took 127.61637473106384s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 5.125999450683594e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0005815029144287109s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.2734870910644531s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.020443439483642578s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.361701965332031e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 8.106231689453125e-06s
INFO | --- Analysis for GTS-ont took 2.5413777828216553s
Availability | SPARQL endpoint availability check for GUTSTOK  took 4.100799560546875e-05s
Availability | VoID file availability check for GUTSTOK  took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.2731454372406006s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.02004837989807129s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 2.8133392333984375e-05s
Believability | Calculation of trust value for GUTSTOK  took 6.9141387939453125e-06s
INFO | --- Analysis for Guillaume_Forget took 2.3620541095733643s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.1961669921875e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.2772383689880371s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.020212411880493164s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 6.67572021484375e-05s
Believability | Calculation of trust value for Project Gutenberg took 1.621246337890625e-05s
INFO | --- Analysis for gutenberg took 10.56898832321167s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 4.3392181396484375e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0007543563842773438s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.24777746200561523s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.0203244686126709s
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.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 4.482269287109375e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 7.152557373046875e-06s
INFO | --- Analysis for gwa-ili took 66.2573127746582s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 7.104873657226562e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.27932286262512207s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.020447969436645508s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 3.1948089599609375e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 6.9141387939453125e-06s
INFO | --- Analysis for GWR took 15.071359157562256s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 4.172325134277344e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.26549625396728516s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 3.0040740966796875e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 7.152557373046875e-06s
INFO | --- Analysis for HASM took 8.576855897903442s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 4.076957702636719e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.27585864067077637s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.02044677734375s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 3.170967102050781e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 6.9141387939453125e-06s
INFO | --- Analysis for hcls-knowledge-base took 2.947540044784546s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 1.840348243713379s
Availability | VoID file availability check for HealthCare Ontology took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.2773745059967041s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.02052450180053711s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.910064697265625e-05s
Believability | Calculation of trust value for HealthCare Ontology took 6.198883056640625e-06s
INFO | --- Analysis for HealthCare_Ontology took 4.7577009201049805s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 4.1961669921875e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.25519466400146484s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.020380020141601562s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 6.079673767089844e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 5.4836273193359375e-06s
INFO | --- Analysis for heartfailure took 3.0253612995147705s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.703129768371582s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0006625652313232422s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.3358604907989502s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.02052021026611328s
Interlinking | Calculation of Degree of Connection for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.001039266586303711s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 5.817413330078125e-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.2636184692382812e-05s
INFO | --- Analysis for hebis-bibliographic-resources took 121.02841258049011s
Availability | SPARQL endpoint availability check for Hedatuz took 0.236236572265625s
Availability | VoID file availability check for Hedatuz took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.28026580810546875s
Reputation | Calculation of the PageRank for Hedatuz took 0.02036142349243164s
Interlinking | Calculation of Degree of Connection for Hedatuz took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 4.410743713378906e-05s
Believability | Calculation of trust value for Hedatuz took 7.867813110351562e-06s
INFO | --- Analysis for hedatuz took 2.957221508026123s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.11691522598266602s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.23590493202209473s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.020160913467407227s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00012755393981933594s
Believability | Calculation of trust value for Hellenic Fire Brigade took 5.4836273193359375e-06s
INFO | --- Analysis for hellenic-fire-brigade took 2.5391948223114014s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.021975994110107422s
Availability | VoID file availability check for Hellenic Police took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.2887687683105469s
Reputation | Calculation of the PageRank for Hellenic Police took 0.02052927017211914s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00013256072998046875s
Believability | Calculation of trust value for Hellenic Police took 5.7220458984375e-06s
INFO | --- Analysis for hellenic-police took 2.5099937915802s
Availability | SPARQL endpoint availability check for Hermos took 5.602836608886719e-05s
Availability | VoID file availability check for Hermos took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for Hermos took 0.27216005325317383s
Reputation | Calculation of the PageRank for Hermos took 0.020435333251953125s
Interlinking | Calculation of Degree of Connection for Hermos took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hermos took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Hermos took 3.123283386230469e-05s
Believability | Calculation of trust value for Hermos took 8.821487426757812e-06s
INFO | --- Analysis for Hermos took 3.658766984939575s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 4.220008850097656e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.26926708221435547s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.020522356033325195s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 3.0994415283203125e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 8.106231689453125e-06s
INFO | --- Analysis for Himanshu_Mahawar took 2.4215097427368164s
Availability | SPARQL endpoint availability check for HITO took 0.47581958770751953s
Availability | VoID file availability check for HITO took 0.00072479248046875s
Extra | Recovery of all triples for HITO took 1.5337803363800049s
Performance | Total latancy measurement for HITO took 1.0021677017211914s
Amount of data | Number of triples check for HITO took 0.2090315818786621s
Interoperability | New terms check for HITO took 1.4416396617889404s
Versatility | Languages check for HITO took 0.22288751602172852s
Interpretability | Number of blank nodes check for HITO took 0.19681000709533691s
Interpretability | RDF structures check for HITO took 0.21094465255737305s
Versatility | Serialization formats check for HITO took 0.21426796913146973s
Availability | RDF dump link check for HITO took 0.1854259967803955s
License | MR license check for HITO took 0.18925094604492188s
License | HR license check for HITO took 0.21137690544128418s
Amount of data | Number of property check for HITO took 0.18738818168640137s
Understandability | Number of label check for HITO took 0.20264077186584473s
Understandability | URI regex check for HITO took 0.40476369857788086s
Understandability | Vocabs check for HITO took 0.19719362258911133s
Verifiability | Authors check for HITO took 0.19802474975585938s
Verifiability | Publishers check for HITO took 0.19913935661315918s
Performance | Throughput check for HITO took 11.759668111801147s
Amount of data | Check the number of entities for HITO took 6.985664367675781e-05s
Verifiability | Contribs. check for HITO took 0.19890522956848145s
Interlinking | sameAs chians check for HITO took 0.18738484382629395s
Interlinking | skos check for HITO took 0.19830989837646484s
Interlinking | skos check for HITO took 0.1978304386138916s
Timeliness | dataset update frequency check for HITO took 0.19875597953796387s
Currency | Creation date check for HITO took 0.3967890739440918s
Currency | Modification date check for HITO took 0.4109680652618408s
Rep.Conc. | URIs length for HITO took 0.9888153076171875s
Interoperability | New vocabularies check for HITO took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.2090766429901123s
Accuracy | Check Functional Property for HITO took 0.18766260147094727s
Accuracy | Check Inverse Functional Property for HITO took 0.19828200340270996s
Accuracy | Check Empty annotation labels for HITO took 0.5003912448883057s
Accuracy | Check White space in annotation for HITO took 0.01332545280456543s
Accuracy | Check Datatype consistency for HITO took 0.06815481185913086s
Consistency | Disjoint class check for HITO took 0.19814467430114746s
Consistency | Check Misplaced properties for HITO took 0.5374548435211182s
Consistency | Misplaced classes for HITO took 0.37933945655822754s
Consistency | Check Ontology hijacking for HITO took 1.6458687782287598s
Consistency | Check Invalid usage of undefined classes for HITO took 1.210740089416504s
Consistency | Check Invalid usage of undefined properties for HITO took 1.4994184970855713s
Conciseness | Check Extensional conciseness for HITO took 0.0651404857635498s
Conciseness | Check Intensional conciseness for HITO took 0.19779586791992188s
Security | Sign check for HITO took 0.19789457321166992s
Availability | Check URIs Dereferenciability for HITO took 2436.188683986664s
Completeness | Calculation of interlinking completeness for HITO took 0.7245352268218994s
Reputation | Calculation of the PageRank for HITO took 0.020564794540405273s
Interlinking | Calculation of Degree of Connection for HITO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for HITO took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for HITO took 8.225440979003906e-05s
Interoperability | Check the re-using of existing vocabs for HITO took 1.6689300537109375e-06s
Believability | Calculation of trust value for HITO took 9.059906005859375e-06s
INFO | --- Analysis for hito took 2490.694397211075s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 13.376978635787964s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.7133843898773193s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.02041149139404297s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 3.552436828613281e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 6.67572021484375e-06s
INFO | --- Analysis for Hoa_Thinh_Phat took 25.39937996864319s
Availability | SPARQL endpoint availability check for Homologene took 4.172325134277344e-05s
Availability | VoID file availability check for Homologene took 0.0002942085266113281s
Completeness | Calculation of interlinking completeness for Homologene took 0.2776932716369629s
Reputation | Calculation of the PageRank for Homologene took 0.021559715270996094s
Interlinking | Calculation of Degree of Connection for Homologene took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Homologene took 0.0008254051208496094s
Interlinking | Calculation of Clustering coefficient for Homologene took 3.62396240234375e-05s
Believability | Calculation of trust value for Homologene took 6.9141387939453125e-06s
INFO | --- Analysis for homologene took 3.4360530376434326s
Availability | SPARQL endpoint availability check for gseg took 5.316734313964844e-05s
Availability | VoID file availability check for gseg took 0.0007154941558837891s
Completeness | Calculation of interlinking completeness for gseg took 0.25574302673339844s
Reputation | Calculation of the PageRank for gseg took 0.020188331604003906s
Interlinking | Calculation of Degree of Connection for gseg took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for gseg took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for gseg took 3.0517578125e-05s
Believability | Calculation of trust value for gseg took 7.62939453125e-06s
INFO | --- Analysis for hongse took 2.8792941570281982s
Availability | SPARQL endpoint availability check for Noticias Universia took 4.1484832763671875e-05s
Availability | VoID file availability check for Noticias Universia took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.68851637840271s
Reputation | Calculation of the PageRank for Noticias Universia took 0.020117759704589844s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 2.86102294921875e-05s
Believability | Calculation of trust value for Noticias Universia took 7.62939453125e-06s
INFO | --- Analysis for http-data-noticias-universia-net took 3.3732705116271973s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 4.076957702636719e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.2555539608001709s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.020171642303466797s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 3.0517578125e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 7.867813110351562e-06s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 2.910825252532959s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.490846872329712s
Availability | VoID file availability check for COURAGE Dataset took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.2681746482849121s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.02024364471435547s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 3.075599670410156e-05s
Believability | Calculation of trust value for COURAGE Dataset took 7.152557373046875e-06s
INFO | --- Analysis for http:cultural-opposition.eu took 5.161483287811279s
Availability | SPARQL endpoint availability check for RoadTrb took 4.291534423828125e-05s
Availability | VoID file availability check for RoadTrb took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.2669191360473633s
Reputation | Calculation of the PageRank for RoadTrb took 0.020255088806152344s
Interlinking | Calculation of Degree of Connection for RoadTrb took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 3.24249267578125e-05s
Believability | Calculation of trust value for RoadTrb took 6.9141387939453125e-06s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 2.3822903633117676s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.25594019889831543s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020139217376708984s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 2.8371810913085938e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 7.152557373046875e-06s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 25.111626625061035s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 4.267692565917969e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.2611396312713623s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.020217180252075195s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 2.8133392333984375e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 6.9141387939453125e-06s
INFO | --- Analysis for http:pakistan.com took 2.3546762466430664s
Availability | SPARQL endpoint availability check for CEDICT took 4.267692565917969e-05s
Availability | VoID file availability check for CEDICT took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for CEDICT took 0.254758358001709s
Reputation | Calculation of the PageRank for CEDICT took 0.019999980926513672s
Interlinking | Calculation of Degree of Connection for CEDICT took 1.52587890625e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for CEDICT took 2.7418136596679688e-05s
Believability | Calculation of trust value for CEDICT took 7.62939453125e-06s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 4.605060815811157s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.5456047058105469s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.24470853805541992s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020255327224731445s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.009506225585938e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.3909759521484375e-06s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 4.64392614364624s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 4.172325134277344e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0008327960968017578s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.2525031566619873s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.020251989364624023s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 4.696846008300781e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 7.62939453125e-06s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 2.926421642303467s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 4.220008850097656e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.2647721767425537s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.02028369903564453s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0010128021240234375s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 3.528594970703125e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 7.62939453125e-06s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.417515516281128s
Availability | SPARQL endpoint availability check for Soccer Dataset took 8.7738037109375e-05s
Availability | VoID file availability check for Soccer Dataset took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.2901291847229004s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.02029585838317871s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 3.0517578125e-05s
Believability | Calculation of trust value for Soccer Dataset took 1.2636184692382812e-05s
INFO | --- Analysis for http:www.msm.com took 2.844663143157959s
Availability | SPARQL endpoint availability check for Game Ontology took 4.9591064453125e-05s
Availability | VoID file availability check for Game Ontology took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.26692938804626465s
Reputation | Calculation of the PageRank for Game Ontology took 0.020307540893554688s
Interlinking | Calculation of Degree of Connection for Game Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 2.9802322387695312e-05s
Believability | Calculation of trust value for Game Ontology took 7.62939453125e-06s
INFO | --- Analysis for http:www.RAG.comgameonto# took 2.9373624324798584s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.1961669921875e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005946159362792969s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.2706005573272705s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020151853561401367s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 6.9141387939453125e-06s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 3.2148563861846924s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 4.935264587402344e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.2821493148803711s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020260095596313477s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 7.62939453125e-06s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 2.4068849086761475s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.267692565917969e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.25824642181396484s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020299196243286133s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.9802322387695312e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.152557373046875e-06s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.3700928688049316s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.220008850097656e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.26249241828918457s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.019990205764770508s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.9325485229492188e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.67572021484375e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.36242938041687s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 5.2928924560546875e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.24691557884216309s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.0201873779296875s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.7894973754882812e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.9141387939453125e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 2.3934285640716553s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 5.459785461425781e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.26196789741516113s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020296573638916016s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0279159545898438e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.867813110351562e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 4.426608085632324s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.57763671875e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2971827983856201s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020404577255249023s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0279159545898438e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.9141387939453125e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.454303741455078s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 4.482269287109375e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.2795379161834717s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.020680904388427734s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 3.075599670410156e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 6.9141387939453125e-06s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 4.203625917434692s
Availability | SPARQL endpoint availability check for Bookkeeping took 1.0588390827178955s
Availability | VoID file availability check for Bookkeeping took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.25292158126831055s
Reputation | Calculation of the PageRank for Bookkeeping took 0.02035975456237793s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 3.0517578125e-05s
Believability | Calculation of trust value for Bookkeeping took 5.4836273193359375e-06s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 3.95180344581604s
Availability | SPARQL endpoint availability check for Legal Ontology took 3.9577484130859375e-05s
Availability | VoID file availability check for Legal Ontology took 0.0002162456512451172s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.26335811614990234s
Reputation | Calculation of the PageRank for Legal Ontology took 0.020513534545898438s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.5762786865234375e-05s
Believability | Calculation of trust value for Legal Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 2.969564914703369s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 4.172325134277344e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.29134297370910645s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020325660705566406s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.772445678710938e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 5.245208740234375e-06s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 2.6365559101104736s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 5.2928924560546875e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.2918095588684082s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.020269155502319336s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 3.147125244140625e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 5.245208740234375e-06s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 2.7044453620910645s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 3.9577484130859375e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.2542111873626709s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.02040696144104004s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 3.147125244140625e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 5.9604644775390625e-06s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 2.8884317874908447s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 4.0531158447265625e-05s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.00021910667419433594s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.2808234691619873s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.02058267593383789s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 3.147125244140625e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 1.1444091796875e-05s
INFO | --- Analysis for hud-library-usagedata took 2.9342403411865234s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.373004674911499s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.25547003746032715s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.020448923110961914s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.000102996826171875s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 6.4373016357421875e-06s
INFO | --- Analysis for hungarian-national-library-catalog took 4.064662218093872s
Availability | SPARQL endpoint availability check for IATE RDF took 4.267692565917969e-05s
Availability | VoID file availability check for IATE RDF took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.26900529861450195s
Reputation | Calculation of the PageRank for IATE RDF took 0.02042841911315918s
Interlinking | Calculation of Degree of Connection for IATE RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.409385681152344e-05s
Believability | Calculation of trust value for IATE RDF took 1.0728836059570312e-05s
INFO | --- Analysis for iate-rdf took 2.8100996017456055s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.128388404846191s
Availability | VoID file availability check for IATI as Linked Data took 0.0006933212280273438s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.2711203098297119s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.020643949508666992s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.320808410644531e-05s
Believability | Calculation of trust value for IATI as Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for iati-as-linked-data took 13.348934888839722s
Availability | SPARQL endpoint availability check for ICANE took 0.34607982635498047s
Availability | VoID file availability check for ICANE took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for ICANE took 0.2712130546569824s
Reputation | Calculation of the PageRank for ICANE took 0.020406723022460938s
Interlinking | Calculation of Degree of Connection for ICANE took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ICANE took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for ICANE took 0.00010418891906738281s
Believability | Calculation of trust value for ICANE took 5.0067901611328125e-06s
INFO | --- Analysis for icane took 3.7086637020111084s
Availability | SPARQL endpoint availability check for ichoose took 0.1332554817199707s
Availability | VoID file availability check for ichoose took 0.0002892017364501953s
Completeness | Calculation of interlinking completeness for ichoose took 0.27520751953125s
Reputation | Calculation of the PageRank for ichoose took 0.020836353302001953s
Interlinking | Calculation of Degree of Connection for ichoose took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ichoose took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for ichoose took 7.62939453125e-05s
Believability | Calculation of trust value for ichoose took 8.106231689453125e-06s
INFO | --- Analysis for ichoose took 57.119932889938354s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 1.5641846656799316s
Availability | VoID file availability check for The Iconology Dataset took 0.0006647109985351562s
Extra | Recovery of all triples for The Iconology Dataset took 4.361921072006226s
Performance | Total latancy measurement for The Iconology Dataset took 0.5145859718322754s
Amount of data | Number of triples check for The Iconology Dataset took 0.334169864654541s
Interoperability | New terms check for The Iconology Dataset took 1.357313871383667s
Versatility | Languages check for The Iconology Dataset took 0.555309534072876s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.2074899673461914s
Interpretability | RDF structures check for The Iconology Dataset took 0.17347431182861328s
Versatility | Serialization formats check for The Iconology Dataset took 0.11217379570007324s
Availability | RDF dump link check for The Iconology Dataset took 0.08983755111694336s
License | MR license check for The Iconology Dataset took 0.12239384651184082s
License | HR license check for The Iconology Dataset took 0.2585172653198242s
Amount of data | Number of property check for The Iconology Dataset took 0.11052656173706055s
Understandability | Number of label check for The Iconology Dataset took 0.14650750160217285s
Understandability | URI regex check for The Iconology Dataset took 0.2044062614440918s
Understandability | Vocabs check for The Iconology Dataset took 0.0923924446105957s
Verifiability | Authors check for The Iconology Dataset took 0.10506224632263184s
Verifiability | Publishers check for The Iconology Dataset took 0.0946497917175293s
Performance | Throughput check for The Iconology Dataset took 10.509346723556519s
Amount of data | Check the number of entities for The Iconology Dataset took 9.822845458984375e-05s
Verifiability | Contribs. check for The Iconology Dataset took 0.09151935577392578s
Interlinking | sameAs chians check for The Iconology Dataset took 0.0933387279510498s
Interlinking | skos check for The Iconology Dataset took 0.0896906852722168s
Interlinking | skos check for The Iconology Dataset took 0.09197211265563965s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.09628605842590332s
Currency | Creation date check for The Iconology Dataset took 0.1909632682800293s
Currency | Modification date check for The Iconology Dataset took 0.2002723217010498s
Rep.Conc. | URIs length for The Iconology Dataset took 1.1917898654937744s
Interoperability | New vocabularies check for The Iconology Dataset took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.08149576187133789s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.25545358657836914s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.016295433044433594s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.42299938201904297s
Consistency | Disjoint class check for The Iconology Dataset took 0.07528138160705566s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.15547490119934082s
Consistency | Misplaced classes for The Iconology Dataset took 0.8629550933837891s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.4787266254425049s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.169945478439331s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.249229907989502s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.2909400463104248s
Security | Sign check for The Iconology Dataset took 0.08458757400512695s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2510.2533724308014s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 1.4174187183380127s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.020529747009277344s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 1.7642974853515625e-05s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 9.5367431640625e-07s
Believability | Calculation of trust value for The Iconology Dataset took 2.7894973754882812e-05s
INFO | --- Analysis for iconology-dataset took 2569.8505487442017s
Availability | SPARQL endpoint availability check for Identifiers.org took 4.124641418457031e-05s
Availability | VoID file availability check for Identifiers.org took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Identifiers.org took 0.2881894111633301s
Reputation | Calculation of the PageRank for Identifiers.org took 0.020430803298950195s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 3.886222839355469e-05s
Believability | Calculation of trust value for Identifiers.org took 7.867813110351562e-06s
INFO | --- Analysis for identifiers-org took 3.387091636657715s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 4.363059997558594e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0006737709045410156s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.2829859256744385s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.019983530044555664s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.772445678710938e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 6.9141387939453125e-06s
INFO | --- Analysis for idreffr took 4.5124781131744385s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.7569553852081299s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.2733137607574463s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.020168542861938477s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 4.935264587402344e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 7.867813110351562e-06s
INFO | --- Analysis for ids took 3.6933443546295166s
Availability | SPARQL endpoint availability check for ietflang took 4.1961669921875e-05s
Availability | VoID file availability check for ietflang took 0.0006864070892333984s
Completeness | Calculation of interlinking completeness for ietflang took 0.7218897342681885s
Reputation | Calculation of the PageRank for ietflang took 0.020111560821533203s
Interlinking | Calculation of Degree of Connection for ietflang took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ietflang took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.553794860839844e-05s
Believability | Calculation of trust value for ietflang took 9.298324584960938e-06s
INFO | --- Analysis for ietflang took 13.039205312728882s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.565253734588623s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.27103257179260254s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for IGVLL took 4.002938270568848s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.4285087585449219s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0005824565887451172s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.1568772792816162s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 0.9928829669952393s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.18630218505859375s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.414639949798584s
Versatility | Languages check for 3LGM² IHE Ontology took 0.21288514137268066s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.1849980354309082s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.2112729549407959s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.2102186679840088s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.19889116287231445s
License | MR license check for 3LGM² IHE Ontology took 0.19762849807739258s
License | HR license check for 3LGM² IHE Ontology took 0.20329570770263672s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.2094440460205078s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.19139790534973145s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.4030778408050537s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.18600940704345703s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.2104957103729248s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.197113037109375s
Performance | Throughput check for 3LGM² IHE Ontology took 11.475335836410522s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 6.961822509765625e-05s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.19739699363708496s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.2079463005065918s
Interlinking | skos check for 3LGM² IHE Ontology took 0.21016883850097656s
Interlinking | skos check for 3LGM² IHE Ontology took 0.20044302940368652s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.20969390869140625s
Currency | Creation date check for 3LGM² IHE Ontology took 0.38776159286499023s
Currency | Modification date check for 3LGM² IHE Ontology took 0.40869808197021484s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.8272318840026855s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.2033839225769043s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.20871543884277344s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.19786882400512695s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.32595062255859375s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.002051115036010742s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.05079340934753418s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.19973134994506836s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.4481348991394043s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.279754638671875s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.5114550590515137s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.1938252449035645s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.4481914043426514s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.030823230743408203s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.1960279941558838s
Security | Sign check for 3LGM² IHE Ontology took 0.1844780445098877s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 408.55649304389954s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.8107717037200928s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.020697593688964844s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 3.719329833984375e-05s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.430511474609375e-06s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for IHE took 454.46426916122437s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 0.06837916374206543s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.2764103412628174s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.020226478576660156s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 2.7418136596679688e-05s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 7.152557373046875e-06s
INFO | --- Analysis for iislod-test took 3.422365665435791s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 6.604194641113281e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.0006840229034423828s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.2826230525970459s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.0203399658203125s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.0279159545898438e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 6.67572021484375e-06s
INFO | --- Analysis for ILUSOC took 12.965726613998413s
Availability | SPARQL endpoint availability check for im@sparql took 6.799317836761475s
Availability | VoID file availability check for im@sparql took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for im@sparql took 0.26529836654663086s
Reputation | Calculation of the PageRank for im@sparql took 0.020247936248779297s
Interlinking | Calculation of Degree of Connection for im@sparql took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for im@sparql took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for im@sparql took 2.8848648071289062e-05s
Believability | Calculation of trust value for im@sparql took 7.62939453125e-06s
INFO | --- Analysis for im@sparql took 13.783727884292603s
Availability | SPARQL endpoint availability check for imagery bailingniao took 4.792213439941406e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0003299713134765625s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.2520463466644287s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.020432233810424805s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 2.9802322387695312e-05s
Believability | Calculation of trust value for imagery bailingniao took 7.152557373046875e-06s
INFO | --- Analysis for imagery_bailingniao took 3.0850322246551514s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.1435368061065674s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0007238388061523438s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 15.436537981033325s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.435396432876587s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 9.905417680740356s
Interoperability | New terms check for Imagesnippets Image Descriptions took 2.6968605518341064s
Versatility | Languages check for Imagesnippets Image Descriptions took 10.705487489700317s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.103814125061035s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.6936612129211426s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7444865703582764s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.738511323928833s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7247586250305176s
License | MR license check for Imagesnippets Image Descriptions took 0.6821174621582031s
License | HR license check for Imagesnippets Image Descriptions took 10.730243682861328s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.7487366199493408s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.7489542961120605s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.4526362419128418s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.6917212009429932s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.6766560077667236s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.6746025085449219s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.928149938583374s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 7.390975952148438e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.7441840171813965s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.7407405376434326s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7427473068237305s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.659583568572998s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.6935775279998779s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.3740079402923584s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.463266134262085s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 19.773123502731323s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.6898794174194336s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.6823937892913818s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.672698974609375s
Accuracy | Check Empty annotation labels for Imagesnippets Image Descriptions took 10.633703708648682s
Accuracy | Check White space in annotation for Imagesnippets Image Descriptions took 2.2459030151367188s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.7354996204376221s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.884684085845947s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 3.9841742515563965s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.394254207611084s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 0.00014519691467285156s
Security | Sign check for Imagesnippets Image Descriptions took 0.7747163772583008s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.26336169242858887s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.18656706809997559s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 8.988380432128906e-05s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 1.6689300537109375e-06s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 7.3909759521484375e-06s
INFO | --- Analysis for imagesnippets took 217.19151186943054s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.751284122467041s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.26422667503356934s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.0204617977142334s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0009312629699707031s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 0.00010180473327636719s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for imf-linked-data took 3.605268716812134s
Availability | SPARQL endpoint availability check for IMGpedia took 4.124641418457031e-05s
Availability | VoID file availability check for IMGpedia took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.25437474250793457s
Reputation | Calculation of the PageRank for IMGpedia took 0.020540952682495117s
Interlinking | Calculation of Degree of Connection for IMGpedia took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for IMGpedia took 0.0009942054748535156s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 3.4809112548828125e-05s
Believability | Calculation of trust value for IMGpedia took 7.62939453125e-06s
INFO | --- Analysis for imgpedia took 3.829486131668091s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 4.100799560546875e-05s
Availability | VoID file availability check for Import Status of GMO Crops took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 0.2725512981414795s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.020342350006103516s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 2.9325485229492188e-05s
Believability | Calculation of trust value for Import Status of GMO Crops took 7.62939453125e-06s
INFO | --- Analysis for import-status-of-gmo-crops took 2.9638381004333496s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 4.0531158447265625e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.26238489151000977s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.02165699005126953s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.0967254638671875e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 7.867813110351562e-06s
INFO | --- Analysis for Imtiaz took 2.413252115249634s
Availability | SPARQL endpoint availability check for Royalty Free Music took 4.3392181396484375e-05s
Availability | VoID file availability check for Royalty Free Music took 0.00038743019104003906s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.25203871726989746s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.02006053924560547s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 2.7418136596679688e-05s
Believability | Calculation of trust value for Royalty Free Music took 6.9141387939453125e-06s
INFO | --- Analysis for inaudio.org took 3.8284640312194824s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 4.076957702636719e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 0.24089717864990234s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.020120620727539062s
Interlinking | Calculation of Degree of Connection for Income and production cost of grape by year took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Income and production cost of grape by year took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 2.7418136596679688e-05s
Believability | Calculation of trust value for Income and production cost of grape by year took 7.152557373046875e-06s
INFO | --- Analysis for income-and-production-cost-of-grape-by-year took 2.9212088584899902s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 4.1961669921875e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.27512407302856445s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.021965980529785156s
Interlinking | Calculation of Degree of Connection for Income and production cost of pear by year took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Income and production cost of pear by year took 0.0009319782257080078s
Interlinking | Calculation of Clustering coefficient for Income and production cost of pear by year took 3.24249267578125e-05s
Believability | Calculation of trust value for Income and production cost of pear by year took 1.5497207641601562e-05s
INFO | --- Analysis for income-and-production-cost-of-pear-by-year took 2.9352681636810303s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.48921895027160645s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0006778240203857422s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.26189589500427246s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.020145177841186523s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 3.528594970703125e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for IndexThomisticusTreebank took 3.9041907787323s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 3.933906555175781e-05s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0003223419189453125s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.2659437656402588s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.02009749412536621s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0008475780487060547s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 3.814697265625e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 6.9141387939453125e-06s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 2.824089527130127s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 4.2438507080078125e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0006520748138427734s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.2975456714630127s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.02008819580078125s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.0001125335693359375s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 7.3909759521484375e-06s
INFO | --- Analysis for ineverycrea took 13.429081678390503s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 4.172325134277344e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.24280667304992676s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.020142555236816406s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.00011157989501953125s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 7.867813110351562e-06s
INFO | --- Analysis for ineverycrea-argentina took 7.039023160934448s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 0.04985213279724121s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.38581180572509766s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.020565271377563477s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 6.985664367675781e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 7.62939453125e-06s
INFO | --- Analysis for influence-tracker-dataset took 13.159130334854126s
Availability | SPARQL endpoint availability check for INSEMTIVES took 4.57763671875e-05s
Availability | VoID file availability check for INSEMTIVES took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.2785921096801758s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.0202333927154541s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 3.0279159545898438e-05s
Believability | Calculation of trust value for INSEMTIVES took 7.3909759521484375e-06s
INFO | --- Analysis for insemtives took 3.024447441101074s
Availability | SPARQL endpoint availability check for instagram.person took 4.1961669921875e-05s
Availability | VoID file availability check for instagram.person took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for instagram.person took 0.27617311477661133s
Reputation | Calculation of the PageRank for instagram.person took 0.020246267318725586s
Interlinking | Calculation of Degree of Connection for instagram.person took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for instagram.person took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for instagram.person took 3.0279159545898438e-05s
Believability | Calculation of trust value for instagram.person took 7.152557373046875e-06s
INFO | --- Analysis for instagram_person took 2.9450466632843018s
Availability | SPARQL endpoint availability check for instagram.videoobject took 3.933906555175781e-05s
Availability | VoID file availability check for instagram.videoobject took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 0.2688636779785156s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.020333051681518555s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 3.123283386230469e-05s
Believability | Calculation of trust value for instagram.videoobject took 8.58306884765625e-06s
INFO | --- Analysis for instagram_videoobject took 2.915311574935913s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 3.933906555175781e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.000457763671875s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.26303625106811523s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.02020716667175293s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 2.9087066650390625e-05s
Believability | Calculation of trust value for Instance Hub Countries took 7.62939453125e-06s
INFO | --- Analysis for instance-hub-countries took 2.7833261489868164s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.267692565917969e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0002868175506591797s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.2679574489593506s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.020303964614868164s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 2.8133392333984375e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 2.401972770690918s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 4.887580871582031e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.2498157024383545s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.020479202270507812s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0009405612945556641s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 3.4809112548828125e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 6.9141387939453125e-06s
INFO | --- Analysis for instance-hub-organizations took 2.8289592266082764s
Availability | SPARQL endpoint availability check for Instance Hub People took 4.076957702636719e-05s
Availability | VoID file availability check for Instance Hub People took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.25756168365478516s
Reputation | Calculation of the PageRank for Instance Hub People took 0.020639419555664062s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 3.0279159545898438e-05s
Believability | Calculation of trust value for Instance Hub People took 7.867813110351562e-06s
INFO | --- Analysis for instance-hub-people took 2.859598398208618s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 4.100799560546875e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.26549530029296875s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.020272016525268555s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 2.9087066650390625e-05s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 7.62939453125e-06s
INFO | --- Analysis for instance-hub-us-civil-servants took 2.919222354888916s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 4.0531158447265625e-05s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.27718615531921387s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.020292282104492188s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 2.9087066650390625e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 6.9141387939453125e-06s
INFO | --- Analysis for instance-hub-us-congressional-committees took 2.911652088165283s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 4.172325134277344e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.00022125244140625s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.2781343460083008s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.020226716995239258s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 4.76837158203125e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-us-congressional-districts took 2.866598129272461s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 4.7206878662109375e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.2794361114501953s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.020269155502319336s
Interlinking | Calculation of Degree of Connection for Instance Hub US Crops took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Instance Hub US Crops took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 3.0994415283203125e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-us-crops took 2.967406988143921s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 4.029273986816406e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.2863469123840332s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.020354270935058594s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 3.0279159545898438e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 3.719329833984375e-05s
INFO | --- Analysis for instance-hub-us-federal-agencies took 2.8987362384796143s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 4.506111145019531e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.2782735824584961s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.020247697830200195s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 3.0279159545898438e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-us-states-and-territories took 2.991124391555786s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 4.029273986816406e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.00021982192993164062s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.247053861618042s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.020311832427978516s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 3.0517578125e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 6.9141387939453125e-06s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 2.8294825553894043s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 3.9577484130859375e-05s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.276749849319458s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.020233869552612305s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0008380413055419922s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 3.075599670410156e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 7.152557373046875e-06s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 2.958857536315918s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 5.14984130859375e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.270214319229126s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.02046370506286621s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00010991096496582031s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 6.198883056640625e-06s
INFO | --- Analysis for interactivemaps-gnoss took 8.555586099624634s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 4.6253204345703125e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.2503058910369873s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 3.0040740966796875e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 6.9141387939453125e-06s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 2.9450204372406006s
Availability | SPARQL endpoint availability check for intervalue took 0.2636685371398926s
Availability | VoID file availability check for intervalue took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for intervalue took 0.27004456520080566s
Reputation | Calculation of the PageRank for intervalue took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for intervalue took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.771087646484375e-05s
Believability | Calculation of trust value for intervalue took 1.0728836059570312e-05s
INFO | --- Analysis for intervalue took 2.676650285720825s
Availability | SPARQL endpoint availability check for Inztrow took 5.53131103515625e-05s
Availability | VoID file availability check for Inztrow took 0.0005445480346679688s
Completeness | Calculation of interlinking completeness for Inztrow took 0.23586678504943848s
Reputation | Calculation of the PageRank for Inztrow took 0.020430326461791992s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Inztrow took 3.123283386230469e-05s
Believability | Calculation of trust value for Inztrow took 6.4373016357421875e-06s
INFO | --- Analysis for Inztrow took 3.680698871612549s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.2635953426361084s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.020525455474853516s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 3.147125244140625e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for ipbes took 3.8529434204101562s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.363059997558594e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.244950532913208s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.020320653915405273s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.315376281738281e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 6.4373016357421875e-06s
INFO | --- Analysis for iptc-newscodes took 3.2918035984039307s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 4.267692565917969e-05s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.2777392864227295s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.02050304412841797s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 3.123283386230469e-05s
Believability | Calculation of trust value for Irstea Weather Dataset of the Montoldre Experimental Farm took 7.62939453125e-06s
INFO | --- Analysis for irstea-weather-dataset-of-the-montoldre-experimental-farm took 2.966275453567505s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 2.2381508350372314s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.276015043258667s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020360946655273438s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.894371032714844e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 8.344650268554688e-06s
INFO | --- Analysis for iserve took 8.647550821304321s
Availability | SPARQL endpoint availability check for ISIC V4 took 21.041605710983276s
Availability | VoID file availability check for ISIC V4 took 0.0008544921875s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.28334498405456543s
Reputation | Calculation of the PageRank for ISIC V4 took 0.020476579666137695s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 4.124641418457031e-05s
Believability | Calculation of trust value for ISIC V4 took 5.7220458984375e-06s
INFO | --- Analysis for isic-v4 took 114.63405966758728s
Availability | SPARQL endpoint availability check for Isidore took 4.315376281738281e-05s
Availability | VoID file availability check for Isidore took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for Isidore took 0.2593870162963867s
Reputation | Calculation of the PageRank for Isidore took 0.02003765106201172s
Interlinking | Calculation of Degree of Connection for Isidore took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Isidore took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Isidore took 2.9325485229492188e-05s
Believability | Calculation of trust value for Isidore took 7.867813110351562e-06s
INFO | --- Analysis for isidore took 3.4774715900421143s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 4.2438507080078125e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.2848381996154785s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.020292997360229492s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 7.486343383789062e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 5.4836273193359375e-06s
INFO | --- Analysis for isil-dbpedia took 4.465703964233398s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 3.981590270996094e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.2580220699310303s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.020322561264038086s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 3.0517578125e-05s
Believability | Calculation of trust value for Linked ISO 3166-2 Data took 1.4781951904296875e-05s
INFO | --- Analysis for iso-3166-2-data took 2.892174482345581s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 4.363059997558594e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.2572145462036133s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.020439863204956055s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.337860107421875e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 8.344650268554688e-06s
INFO | --- Analysis for iso-639-oasis took 2.845487356185913s
Availability | SPARQL endpoint availability check for ISOcat took 7.200241088867188e-05s
Availability | VoID file availability check for ISOcat took 0.0007352828979492188s
Completeness | Calculation of interlinking completeness for ISOcat took 0.2677600383758545s
Reputation | Calculation of the PageRank for ISOcat took 0.020232200622558594s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0008637905120849609s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.413459777832031e-05s
Believability | Calculation of trust value for ISOcat took 6.198883056640625e-06s
INFO | --- Analysis for isocat took 33.18284344673157s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 4.172325134277344e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0006628036499023438s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.2779421806335449s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.02019643783569336s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.600120544433594e-05s
Believability | Calculation of trust value for ISOcat-metadata took 7.62939453125e-06s
INFO | --- Analysis for isocat-metadata took 5.729536771774292s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 4.172325134277344e-05s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 0.2551841735839844s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.021404266357421875s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 3.24249267578125e-05s
Believability | Calculation of trust value for ISPRA - Mitigation measures in Italy for national soil protection took 8.106231689453125e-06s
INFO | --- Analysis for ispra-lod-ihi took 2.8353328704833984s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.29500746726989746s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0005867481231689453s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 5.9788291454315186s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.7985062599182129s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.22019433975219727s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.954512357711792s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.92856001853943s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2250504493713379s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.11110949516296387s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.19526028633117676s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18129777908325195s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1664581298828125s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.27690911293029785s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 92.97802448272705s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1779189109802246s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.2159321308135986s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.4637570381164551s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.21452832221984863s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.21735525131225586s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15709304809570312s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.667906999588013s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.2479248046875e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2103264331817627s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.28285646438598633s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.5114636421203613s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.5455644130706787s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2136368751525879s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3031198978424072s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.16502761840820312s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 14.003233909606934s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 6.198883056640625e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18187689781188965s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1508491039276123s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1675422191619873s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.8458616733551025s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.30872416496276855s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.27033090591430664s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14522957801818848s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.743969440460205s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9872119426727295s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 3.1148104667663574s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.2274277210235596s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.775375127792358s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2942628860473633s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1986989974975586s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.16822504997253418s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.934240818023682s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.7890024185180664s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.020764827728271484s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00010967254638671875s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.6689300537109375e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.3909759521484375e-06s
INFO | --- Analysis for ispra-lod-place took 457.98149704933167s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 4.410743713378906e-05s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.25483179092407227s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.020666837692260742s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0008573532104492188s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 3.457069396972656e-05s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 5.9604644775390625e-06s
INFO | --- Analysis for ispra-lod-rmn took 3.822068214416504s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.15720558166503906s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.00034737586975097656s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 5.926312685012817s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.7701199054718018s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.23293328285217285s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 2.9116616249084473s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 90.19508695602417s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.19300079345703125s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.10816645622253418s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.17282438278198242s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.15090608596801758s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.17263150215148926s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.1975879669189453s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 90.52530312538147s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.22539544105529785s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.1036157608032227s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.43836522102355957s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.21398234367370605s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.17558526992797852s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.16996479034423828s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.581197738647461s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 7.414817810058594e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.20324206352233887s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.2537510395050049s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.44864439964294434s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.48921775817871094s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.21721982955932617s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.3229987621307373s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.14261841773986816s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 13.899155378341675s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 6.67572021484375e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.20151710510253906s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.1762089729309082s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.15728211402893066s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 2.73439884185791s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.306964635848999s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.27043747901916504s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.15294241905212402s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 9.86305546760559s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.9892797470092773s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 2.903294086456299s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.1983764171600342s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.81599473953247s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.2831456661224365s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.21923255920410156s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.1812744140625s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 2788.845614671707s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 1.1421666145324707s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.024318933486938477s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 4.863739013671875e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian Data Buoy Network (RON) took 1.1920928955078125e-06s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 8.106231689453125e-06s
INFO | --- Analysis for ispra-lod-ron took 3122.8425028324127s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 4.291534423828125e-05s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 0.7023911476135254s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.020801067352294922s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 2.8848648071289062e-05s
Believability | Calculation of trust value for ISPRA - Soil Consumption Indicators in Italy took 7.3909759521484375e-06s
INFO | --- Analysis for ispra-lod-sc took 3.8944597244262695s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.6814019680023193s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.2625558376312256s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.02161407470703125s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 9.226799011230469e-05s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for issa-agritrop took 6.092687129974365s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.315376281738281e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.27733659744262695s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.02010631561279297s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 2.7418136596679688e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 6.9141387939453125e-06s
INFO | --- Analysis for ISSN:0080-3626 took 3.2499852180480957s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.291534423828125e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.25571489334106445s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020501375198364258s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 2.8371810913085938e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 6.9141387939453125e-06s
INFO | --- Analysis for ISSN:_0080-3626 took 3.1640710830688477s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 4.2438507080078125e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.28435468673706055s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.021500110626220703s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0012352466583251953s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 4.76837158203125e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 7.62939453125e-06s
INFO | --- Analysis for ISSN:_0080-3626. took 2.6033546924591064s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 1.6865997314453125s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.26682186126708984s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.020165681838989258s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.320808410644531e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 5.245208740234375e-06s
INFO | --- Analysis for istat-immigration took 4.139451742172241s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 4.00543212890625e-05s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 0.24616456031799316s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.020281076431274414s
Interlinking | Calculation of Degree of Connection for ISTAT Immigrazione (Linkedopendata.it) took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for ISTAT Immigrazione (Linkedopendata.it) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 2.7418136596679688e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 7.867813110351562e-06s
INFO | --- Analysis for istat-immigrazione took 3.3870561122894287s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.14432311058044434s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.26845693588256836s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.02029895782470703s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 2.86102294921875e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 5.245208740234375e-06s
INFO | --- Analysis for it-aifa-drug-prices took 2.7506959438323975s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.0797438621520996s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0008022785186767578s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.26177549362182617s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.020308256149291992s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.319450378417969e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 8.106231689453125e-06s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 3.4537911415100098s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 4.267692565917969e-05s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.287351131439209s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.02058720588684082s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 3.0994415283203125e-05s
Believability | Calculation of trust value for Academic Bibliography data available from Acta Cryst E took 8.821487426757812e-06s
INFO | --- Analysis for iucr-acta-cryst-e took 2.942301034927368s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 4.0531158447265625e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.25016045570373535s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 2.9325485229492188e-05s
Believability | Calculation of trust value for IWMI Research Reports took 6.67572021484375e-06s
INFO | --- Analysis for iwmi-research-reports took 2.934943914413452s
Availability | SPARQL endpoint availability check for IWN took 4.2438507080078125e-05s
Availability | VoID file availability check for IWN took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for IWN took 0.28146958351135254s
Reputation | Calculation of the PageRank for IWN took 0.020427703857421875s
Interlinking | Calculation of Degree of Connection for IWN took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IWN took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for IWN took 3.6716461181640625e-05s
Believability | Calculation of trust value for IWN took 7.3909759521484375e-06s
INFO | --- Analysis for iwn took 5.925593614578247s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 3.981590270996094e-05s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.2800133228302002s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.02044391632080078s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 3.0040740966796875e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 1.3113021850585938e-05s
INFO | --- Analysis for j-global-knowledge took 2.907658100128174s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 4.124641418457031e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.28923583030700684s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.020519733428955078s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 2.956390380859375e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 6.67572021484375e-06s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 2.881584644317627s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 9.260139226913452s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0007369518280029297s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.2820281982421875s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.020427227020263672s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 5.793571472167969e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 6.67572021484375e-06s
INFO | --- Analysis for jamendo-dbtune took 41.01001167297363s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 4.7206878662109375e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.24668312072753906s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.0202028751373291s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 6.0558319091796875e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for japan-radioactivity-stat took 4.281843423843384s
Availability | SPARQL endpoint availability check for JEL Classification took 5.078315734863281e-05s
Availability | VoID file availability check for JEL Classification took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.2853379249572754s
Reputation | Calculation of the PageRank for JEL Classification took 0.020311355590820312s
Interlinking | Calculation of Degree of Connection for JEL Classification took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 2.86102294921875e-05s
Believability | Calculation of trust value for JEL Classification took 7.3909759521484375e-06s
INFO | --- Analysis for jel-classification took 5.295757055282593s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.2032279968261719s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.30557680130004883s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.020019054412841797s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 2.765655517578125e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 1.2636184692382812e-05s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 7.498725652694702s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.3127875328064s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0006651878356933594s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.3374366760253906s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.020464420318603516s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 7.653236389160156e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 7.152557373046875e-06s
INFO | --- Analysis for jita took 540.1260585784912s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 4.839897155761719e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.6923608779907227s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.020413875579833984s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 2.9087066650390625e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 7.3909759521484375e-06s
INFO | --- Analysis for jmdict took 5.519119501113892s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.07615637779236s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.00040221214294433594s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.7228715419769287s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.020048856735229492s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 8.249282836914062e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 7.152557373046875e-06s
INFO | --- Analysis for john-goodwins-family-tree took 64.32723474502563s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 4.267692565917969e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.25616025924682617s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.020422697067260742s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 3.4332275390625e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 7.3909759521484375e-06s
INFO | --- Analysis for jp-cos took 6.530935049057007s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 4.506111145019531e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.26526618003845215s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.020283937454223633s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 3.6716461181640625e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 7.152557373046875e-06s
INFO | --- Analysis for jp-textbook took 4.658207654953003s
Availability | SPARQL endpoint availability check for JRC-Names took 5.626678466796875e-05s
Availability | VoID file availability check for JRC-Names took 0.0002887248992919922s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.2554209232330322s
Reputation | Calculation of the PageRank for JRC-Names took 0.020303010940551758s
Interlinking | Calculation of Degree of Connection for JRC-Names took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.147125244140625e-05s
Believability | Calculation of trust value for JRC-Names took 6.9141387939453125e-06s
INFO | --- Analysis for jrc-names-ec took 5.236623525619507s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 1.2011864185333252s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.28550267219543457s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.020653724670410156s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.890296936035156e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 1.3113021850585938e-05s
INFO | --- Analysis for jrc-names-mlode took 3.7839291095733643s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.792213439941406e-05s
Availability | VoID file availability check for JudaicaLink took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.2471928596496582s
Reputation | Calculation of the PageRank for JudaicaLink took 0.020343780517578125s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 9.775161743164062e-05s
Believability | Calculation of trust value for JudaicaLink took 6.9141387939453125e-06s
INFO | --- Analysis for judaicalink took 22.528116703033447s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 5.3882598876953125e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.27791595458984375s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.020348548889160156s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 3.1948089599609375e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 6.9141387939453125e-06s
INFO | --- Analysis for kaist-silver-standard-corpus took 2.940152883529663s
Availability | SPARQL endpoint availability check for KAKEN took 4.1484832763671875e-05s
Availability | VoID file availability check for KAKEN took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for KAKEN took 0.27097034454345703s
Reputation | Calculation of the PageRank for KAKEN took 0.020613431930541992s
Interlinking | Calculation of Degree of Connection for KAKEN took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for KAKEN took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for KAKEN took 3.0994415283203125e-05s
Believability | Calculation of trust value for KAKEN took 7.3909759521484375e-06s
INFO | --- Analysis for kaken took 2.972365140914917s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.07203984260559082s
Availability | VoID file availability check for Kallikratis municipalities took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.27066588401794434s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.020549297332763672s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.250640869140625e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 5.7220458984375e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.4280896186828613s
Availability | SPARQL endpoint availability check for Openflights Routes took 4.291534423828125e-05s
Availability | VoID file availability check for Openflights Routes took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Openflights Routes took 0.2604532241821289s
Reputation | Calculation of the PageRank for Openflights Routes took 0.02060222625732422s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 3.266334533691406e-05s
Believability | Calculation of trust value for Openflights Routes took 7.3909759521484375e-06s
INFO | --- Analysis for kasabi-openflights-routes took 2.93072247505188s
Availability | SPARQL endpoint availability check for EU Soccer League took 4.410743713378906e-05s
Availability | VoID file availability check for EU Soccer League took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.27235889434814453s
Reputation | Calculation of the PageRank for EU Soccer League took 0.020204544067382812s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 2.956390380859375e-05s
Believability | Calculation of trust value for EU Soccer League took 8.344650268554688e-06s
INFO | --- Analysis for KG:Course_Submission took 3.5699892044067383s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 4.315376281738281e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0006783008575439453s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.24527835845947266s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.02033376693725586s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.1444091796875e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 7.62939453125e-06s
INFO | --- Analysis for KING took 2.5813100337982178s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 4.38690185546875e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.24907135963439941s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.020399808883666992s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.532669067382812e-05s
Believability | Calculation of trust value for Klappstuhlclub took 7.62939453125e-06s
INFO | --- Analysis for klappstuhlclub took 12.428584575653076s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.940035581588745s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.2543792724609375s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 7.295608520507812e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 8.344650268554688e-06s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.41329860687256s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.1484832763671875e-05s
Availability | VoID file availability check for Knowledge Forest took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.2855875492095947s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020340681076049805s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.123283386230469e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.3589859008789062e-05s
INFO | --- Analysis for knowledge-map took 2.9957048892974854s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.3392181396484375e-05s
Availability | VoID file availability check for Knowledge Forest took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.2644484043121338s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.02048516273498535s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.9325485229492188e-05s
Believability | Calculation of trust value for Knowledge Forest took 7.3909759521484375e-06s
INFO | --- Analysis for KnowledgeFusion took 2.4151012897491455s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 4.3392181396484375e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.2680935859680176s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.556510925292969e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 6.67572021484375e-06s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.052024602890015s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 3.981590270996094e-05s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.0002205371856689453s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.2681872844696045s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.02005743980407715s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 6.9141387939453125e-06s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 2.950974702835083s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 4.458427429199219e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.2907567024230957s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.020473480224609375s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 3.0517578125e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 7.62939453125e-06s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.379634380340576s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 3.9577484130859375e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.2536311149597168s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.02042841911315918s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 3.123283386230469e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 6.67572021484375e-06s
INFO | --- Analysis for ktr took 2.865499496459961s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.458427429199219e-05s
Availability | VoID file availability check for Informatics Studies took 0.0003647804260253906s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.2537109851837158s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020290851593017578s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0008044242858886719s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 3.123283386230469e-05s
Believability | Calculation of trust value for Informatics Studies took 6.9141387939453125e-06s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 2.9855237007141113s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.0880274772644043s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.0003323554992675781s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.2572031021118164s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.02013230323791504s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.2901763916015625e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 7.152557373046875e-06s
INFO | --- Analysis for kupkb took 9.362292528152466s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 5.602836608886719e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.24490070343017578s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.020473003387451172s
Interlinking | Calculation of Degree of Connection for Léčivé přípravky ze SÚKL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Léčivé přípravky ze SÚKL took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 3.147125244140625e-05s
Believability | Calculation of trust value for Léčivé přípravky ze SÚKL took 7.3909759521484375e-06s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 2.839963436126709s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 8.11455512046814s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.2715139389038086s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.020580530166625977s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 7.104873657226562e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 7.867813110351562e-06s
INFO | --- Analysis for l3s-dblp took 53.37089514732361s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 23.448448419570923s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.28751635551452637s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.02052164077758789s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 6.651878356933594e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 1.239776611328125e-05s
INFO | --- Analysis for lak-dataset took 82.54828929901123s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.295363187789917s
Availability | VoID file availability check for  Language Name Authority List  took 0.0005011558532714844s
Extra | Recovery of all triples for  Language Name Authority List  took 62.14651036262512s
Performance | Total latancy measurement for  Language Name Authority List  took 0.5922853946685791s
Amount of data | Number of triples check for  Language Name Authority List  took 0.6978707313537598s
Interoperability | New terms check for  Language Name Authority List  took 12.003551006317139s
Versatility | Languages check for  Language Name Authority List  took 300.08950877189636s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 1.8066225051879883s
Security | Check HTTPS for  Language Name Authority List  took 0.39104390144348145s
Interpretability | RDF structures check for  Language Name Authority List  took 0.708054780960083s
Versatility | Serialization formats check for  Language Name Authority List  took 2.3133888244628906s
Availability | RDF dump link check for  Language Name Authority List  took 0.36219191551208496s
License | MR license check for  Language Name Authority List  took 0.17805218696594238s
License | HR license check for  Language Name Authority List  took 300.1034667491913s
Amount of data | Number of property check for  Language Name Authority List  took 0.18358826637268066s
Understandability | Number of label check for  Language Name Authority List  took 1.5434441566467285s
Understandability | URI regex check for  Language Name Authority List  took 0.3878214359283447s
Understandability | Vocabs check for  Language Name Authority List  took 0.09654951095581055s
Verifiability | Authors check for  Language Name Authority List  took 0.27293992042541504s
Verifiability | Publishers check for  Language Name Authority List  took 0.29119324684143066s
Performance | Throughput check for  Language Name Authority List  took 10.665778636932373s
Amount of data | Check the number of entities for  Language Name Authority List  took 6.985664367675781e-05s
Verifiability | Contribs. check for  Language Name Authority List  took 0.09439778327941895s
Interlinking | sameAs chians check for  Language Name Authority List  took 1.3831486701965332s
Interlinking | skos check for  Language Name Authority List  took 0.5595376491546631s
Interlinking | skos check for  Language Name Authority List  took 0.23879265785217285s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.2346208095550537s
Currency | Creation date check for  Language Name Authority List  took 0.29553985595703125s
Currency | Modification date check for  Language Name Authority List  took 0.20662426948547363s
Rep.Conc. | URIs length for  Language Name Authority List  took 106.55478692054749s
Interoperability | New vocabularies check for  Language Name Authority List  took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.1727592945098877s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.14529824256896973s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.18950223922729492s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 17.952046632766724s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.059555768966675s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.664644479751587s
Consistency | Disjoint class check for  Language Name Authority List  took 0.15091156959533691s
Consistency | Check Misplaced properties for  Language Name Authority List  took 62.18739986419678s
Consistency | Misplaced classes for  Language Name Authority List  took 8.431909322738647s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 22.606473445892334s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 1.3905794620513916s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 57.31006217002869s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 2.981764554977417s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.40256762504577637s
Security | Sign check for  Language Name Authority List  took 0.09504580497741699s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 8.992456912994385s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 1.1780812740325928s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.02097606658935547s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 8.726119995117188e-05s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 1.9073486328125e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 7.62939453125e-06s
INFO | --- Analysis for language-authority-list took 13677.007691144943s
Availability | SPARQL endpoint availability check for Lark took 391.41607642173767s
Availability | VoID file availability check for Lark took 0.0016436576843261719s
Completeness | Calculation of interlinking completeness for Lark took 0.9340426921844482s
Reputation | Calculation of the PageRank for Lark took 0.02221822738647461s
Interlinking | Calculation of Degree of Connection for Lark took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Lark took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Lark took 8.20159912109375e-05s
Believability | Calculation of trust value for Lark took 7.867813110351562e-06s
INFO | --- Analysis for LARK took 1685.5062639713287s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.5885276794433594s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.2805967330932617s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.029881715774536133s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 4.935264587402344e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for LASLA took 5.4975972175598145s
Availability | SPARQL endpoint availability check for LATC Linksets took 4.0531158447265625e-05s
Availability | VoID file availability check for LATC Linksets took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for LATC Linksets took 0.2547118663787842s
Reputation | Calculation of the PageRank for LATC Linksets took 0.020505428314208984s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 3.0040740966796875e-05s
Believability | Calculation of trust value for LATC Linksets took 3.504753112792969e-05s
INFO | --- Analysis for latc-linksets took 3.8742659091949463s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.47098374366760254s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.25139737129211426s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.019994020462036133s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 3.9577484130859375e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for Latin_Vallex2.0 took 4.887821435928345s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.48058557510375977s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.29485416412353516s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.020566701889038086s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 3.7670135498046875e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 9.059906005859375e-06s
INFO | --- Analysis for LatinAffectus took 4.0327653884887695s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.41562771797180176s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.27211475372314453s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 3.838539123535156e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for LatinWordnetLiLa took 4.354204893112183s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 4.792213439941406e-05s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 0.250046968460083s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.020918607711791992s
Interlinking | Calculation of Degree of Connection for Leipzig Corpora Collection (LCC) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Leipzig Corpora Collection (LCC) took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 3.075599670410156e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 7.867813110351562e-06s
INFO | --- Analysis for lcc took 3.0639760494232178s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 5.3882598876953125e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0007205009460449219s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.3444998264312744s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.02036452293395996s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00011491775512695312s
Believability | Calculation of trust value for Library of Congress Subject Headings took 8.106231689453125e-06s
INFO | --- Analysis for lcsh took 6.073961019515991s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 4.38690185546875e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.26915645599365234s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.020843982696533203s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0009922981262207031s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 9.989738464355469e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 7.867813110351562e-06s
INFO | --- Analysis for lcsubjects took 3.024850606918335s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 4.124641418457031e-05s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 0.27542805671691895s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for LDQM - Accessibility of DBpedia resources took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LDQM - Accessibility of DBpedia resources took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 3.0279159545898438e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 8.344650268554688e-06s
INFO | --- Analysis for ldqm-dbpedia-2016 took 2.8990259170532227s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.975290298461914s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.000606536865234375s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.2551534175872803s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.02036261558532715s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.3392181396484375e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 1.0728836059570312e-05s
INFO | --- Analysis for ldt@library took 36.49257850646973s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 4.1484832763671875e-05s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.0002257823944091797s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 0.2550981044769287s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.020203351974487305s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Eng took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Learned Genre Ontology Eng took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Eng took 2.8133392333984375e-05s
Believability | Calculation of trust value for Learned Genre Ontology Eng took 7.3909759521484375e-06s
INFO | --- Analysis for learned-genre-ontology-eng took 2.883599042892456s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 4.506111145019531e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.26218366622924805s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.020000696182250977s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Intl took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Learned Genre Ontology Intl took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 2.6941299438476562e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 8.58306884765625e-06s
INFO | --- Analysis for learned-genre-ontology-intl took 2.8481106758117676s
Availability | SPARQL endpoint availability check for U ime Legije took 4.649162292480469e-05s
Availability | VoID file availability check for U ime Legije took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.27515745162963867s
Reputation | Calculation of the PageRank for U ime Legije took 0.0212249755859375s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 3.266334533691406e-05s
Believability | Calculation of trust value for U ime Legije took 7.867813110351562e-06s
INFO | --- Analysis for LEGIJA_STRANACA took 2.368468999862671s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 4.9591064453125e-05s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.269681453704834s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.020200014114379883s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 3.0279159545898438e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 6.9141387939453125e-06s
INFO | --- Analysis for legislation-openuplabs took 2.8506031036376953s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.45037269592285156s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0004210472106933594s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.263380765914917s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.02019977569580078s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.104873657226562e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 7.62939453125e-06s
INFO | --- Analysis for LemmaBank took 4.257503509521484s
Availability | SPARQL endpoint availability check for lemonUby took 4.291534423828125e-05s
Availability | VoID file availability check for lemonUby took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for lemonUby took 0.2661879062652588s
Reputation | Calculation of the PageRank for lemonUby took 0.020151376724243164s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.4849853515625e-05s
Believability | Calculation of trust value for lemonUby took 7.152557373046875e-06s
INFO | --- Analysis for lemonuby took 3.460235118865967s
Availability | SPARQL endpoint availability check for LemonWiktionary took 8.487701416015625e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.263702392578125s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.020259380340576172s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.2901763916015625e-05s
Believability | Calculation of trust value for LemonWiktionary took 8.821487426757812e-06s
INFO | --- Analysis for lemonwiktionary took 4.61073899269104s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.45949840545654297s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0007040500640869141s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.27242493629455566s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.02017807960510254s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 3.528594970703125e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 8.106231689453125e-06s
INFO | --- Analysis for LewisShort took 3.834416627883911s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.1523966789245605s
Availability | VoID file availability check for LEXIN-RDF took 0.0006189346313476562s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.255810022354126s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.022141456604003906s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 3.0517578125e-05s
Believability | Calculation of trust value for LEXIN-RDF took 7.867813110351562e-06s
INFO | --- Analysis for lexin-rdf took 5.772655248641968s
Availability | SPARQL endpoint availability check for lexinfo took 4.267692565917969e-05s
Availability | VoID file availability check for lexinfo took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for lexinfo took 0.2449800968170166s
Reputation | Calculation of the PageRank for lexinfo took 0.02076888084411621s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0010085105895996094s
Interlinking | Calculation of Clustering coefficient for lexinfo took 9.489059448242188e-05s
Believability | Calculation of trust value for lexinfo took 6.9141387939453125e-06s
INFO | --- Analysis for lexinfo took 2.8320882320404053s
Availability | SPARQL endpoint availability check for Lexvo took 4.1484832763671875e-05s
Availability | VoID file availability check for Lexvo took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for Lexvo took 0.2705872058868408s
Reputation | Calculation of the PageRank for Lexvo took 0.020159244537353516s
Interlinking | Calculation of Degree of Connection for Lexvo took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Lexvo took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00017762184143066406s
Believability | Calculation of trust value for Lexvo took 6.9141387939453125e-06s
INFO | --- Analysis for lexvo took 42.66456842422485s
Availability | SPARQL endpoint availability check for Lexvo.org took 4.172325134277344e-05s
Availability | VoID file availability check for Lexvo.org took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.265852689743042s
Reputation | Calculation of the PageRank for Lexvo.org took 0.020221948623657227s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.05718994140625e-05s
Believability | Calculation of trust value for Lexvo.org took 7.152557373046875e-06s
INFO | --- Analysis for lexvo-org took 22.500582695007324s
Availability | SPARQL endpoint availability check for LIBRIS took 0.3179488182067871s
Availability | VoID file availability check for LIBRIS took 0.0006105899810791016s
Extra | Recovery of all triples for LIBRIS took 6.75460410118103s
Performance | Total latancy measurement for LIBRIS took 0.7651867866516113s
Amount of data | Number of triples check for LIBRIS took 21.341907739639282s
Interoperability | New terms check for LIBRIS took 15.393313646316528s
Versatility | Languages check for LIBRIS took 0.1918189525604248s
Interpretability | Number of blank nodes check for LIBRIS took 300.1028206348419s
Security | Check HTTPS for LIBRIS took 0.36524176597595215s
Interpretability | RDF structures check for LIBRIS took 0.3864560127258301s
Versatility | Serialization formats check for LIBRIS took 0.2511153221130371s
Availability | RDF dump link check for LIBRIS took 0.14751935005187988s
License | MR license check for LIBRIS took 0.25977420806884766s
License | HR license check for LIBRIS took 0.23204874992370605s
Amount of data | Number of property check for LIBRIS took 0.19759297370910645s
Understandability | Number of label check for LIBRIS took 0.5759024620056152s
Understandability | URI regex check for LIBRIS took 0.38220858573913574s
Understandability | Vocabs check for LIBRIS took 0.15745210647583008s
Verifiability | Authors check for LIBRIS took 0.17821812629699707s
Verifiability | Publishers check for LIBRIS took 0.16863226890563965s
Performance | Throughput check for LIBRIS took 11.122193574905396s
Amount of data | Check the number of entities for LIBRIS took 6.461143493652344e-05s
Verifiability | Contribs. check for LIBRIS took 0.16724729537963867s
Interlinking | sameAs chians check for LIBRIS took 0.2187960147857666s
Interlinking | skos check for LIBRIS took 0.31791257858276367s
Interlinking | skos check for LIBRIS took 0.13867592811584473s
Timeliness | dataset update frequency check for LIBRIS took 0.1642894744873047s
Currency | Creation date check for LIBRIS took 0.38127636909484863s
Currency | Modification date check for LIBRIS took 0.6196718215942383s
Rep.Conc. | URIs length for LIBRIS took 80.11307144165039s
Interoperability | New vocabularies check for LIBRIS took 5.7220458984375e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.18047237396240234s
Accuracy | Check Functional Property for LIBRIS took 0.19957399368286133s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.1360158920288086s
Accuracy | Check Datatype consistency for LIBRIS took 0.2642226219177246s
Consistency | Disjoint class check for LIBRIS took 0.23307418823242188s
Consistency | Check Misplaced properties for LIBRIS took 60.47514772415161s
Consistency | Misplaced classes for LIBRIS took 1.098048448562622s
Consistency | Check Ontology hijacking for LIBRIS took 3.529855251312256s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.1935033798217773s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 61.45575928688049s
Conciseness | Check Extensional conciseness for LIBRIS took 0.2760169506072998s
Conciseness | Check Intensional conciseness for LIBRIS took 0.4171183109283447s
Security | Sign check for LIBRIS took 0.35245418548583984s
Availability | Check URIs Dereferenciability for LIBRIS took 9.38345456123352s
Completeness | Calculation of interlinking completeness for LIBRIS took 0.39118480682373047s
Reputation | Calculation of the PageRank for LIBRIS took 0.020198345184326172s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 9.512901306152344e-05s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.1920928955078125e-06s
Believability | Calculation of trust value for LIBRIS took 1.3589859008789062e-05s
INFO | --- Analysis for libris took 1064.7877666950226s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.06412458419799805s
Availability | VoID file availability check for Public Library of Veroia took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.2587909698486328s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.021209001541137695s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 8.511543273925781e-05s
Believability | Calculation of trust value for Public Library of Veroia took 6.67572021484375e-06s
INFO | --- Analysis for libver took 4.8387017250061035s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.1557605266571045s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.994760274887085s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.020232200622558594s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 7.891654968261719e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 5.245208740234375e-06s
INFO | --- Analysis for lichfield-spending took 3.214890480041504s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 4.1961669921875e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0007412433624267578s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.6778194904327393s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.3855438232421875e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 6.9141387939453125e-06s
INFO | --- Analysis for lime took 6.902658462524414s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0006172657012939453s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.26807188987731934s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.02048802375793457s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00011181831359863281s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 7.3909759521484375e-06s
INFO | --- Analysis for lingvoj took 7.842170000076294s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 4.1961669921875e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0004353523254394531s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.252732515335083s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.020226001739501953s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 7.700920104980469e-05s
Believability | Calculation of trust value for Linked Crunchbase took 7.62939453125e-06s
INFO | --- Analysis for linked-crunchbase took 2.67911696434021s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 6.261898994445801s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007727146148681641s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.2645742893218994s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.020425081253051758s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.987022399902344e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 8.106231689453125e-06s
INFO | --- Analysis for linked-drugs took 21.16191792488098s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.291534423828125e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.26677966117858887s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.020183801651000977s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.5367431640625e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 6.198883056640625e-06s
INFO | --- Analysis for linked-edgar took 4.252899885177612s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 4.315376281738281e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.00042247772216796875s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.25293445587158203s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.846687316894531e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 7.867813110351562e-06s
INFO | --- Analysis for linked-eurostat took 4.047344923019409s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.410743713378906e-05s
Availability | VoID file availability check for linked hypernyms took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.2630891799926758s
Reputation | Calculation of the PageRank for linked hypernyms took 0.02052783966064453s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.581710815429688e-05s
Believability | Calculation of trust value for linked hypernyms took 8.821487426757812e-06s
INFO | --- Analysis for linked-hypernyms took 3.500856399536133s
Availability | SPARQL endpoint availability check for Linked Life Data took 208.08418464660645s
Availability | VoID file availability check for Linked Life Data took 0.0003757476806640625s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.614607572555542s
Reputation | Calculation of the PageRank for Linked Life Data took 0.020776987075805664s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 4.76837158203125e-05s
Believability | Calculation of trust value for Linked Life Data took 6.9141387939453125e-06s
INFO | --- Analysis for linked-life-data took 668.7238531112671s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.46979665756225586s
Availability | VoID file availability check for Linked Logainm took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.2604341506958008s
Reputation | Calculation of the PageRank for Linked Logainm took 0.020358800888061523s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 7.653236389160156e-05s
Believability | Calculation of trust value for Linked Logainm took 8.58306884765625e-06s
INFO | --- Analysis for linked-logainm took 5.085890531539917s
Availability | SPARQL endpoint availability check for Linked NUTS took 4.220008850097656e-05s
Availability | VoID file availability check for Linked NUTS took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.25483107566833496s
Reputation | Calculation of the PageRank for Linked NUTS took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.269050598144531e-05s
Believability | Calculation of trust value for Linked NUTS took 5.0067901611328125e-06s
INFO | --- Analysis for linked-nuts took 2.9122960567474365s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 4.029273986816406e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.26416468620300293s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.02010178565979004s
Interlinking | Calculation of Degree of Connection for Linked Open Aalto Data Service took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Linked Open Aalto Data Service took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Linked Open Aalto Data Service took 2.8371810913085938e-05s
Believability | Calculation of trust value for Linked Open Aalto Data Service took 7.3909759521484375e-06s
INFO | --- Analysis for linked-open-aalto-data-service took 2.936891794204712s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 2.0856881141662598s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.6801424026489258s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020374774932861328s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.4809112548828125e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 5.7220458984375e-06s
INFO | --- Analysis for linked-open-camera took 4.964188814163208s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 3.6119961738586426s
Availability | VoID file availability check for Linked Open Commerce took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.2695472240447998s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.02071356773376465s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0008540153503417969s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 3.123283386230469e-05s
Believability | Calculation of trust value for Linked Open Commerce took 7.152557373046875e-06s
INFO | --- Analysis for linked-open-commerce took 13.918909788131714s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 0.9741289615631104s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.2877488136291504s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.020041942596435547s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00010061264038085938s
Believability | Calculation of trust value for Linked Open Data of Ecology took 7.3909759521484375e-06s
INFO | --- Analysis for linked-open-data-of-ecology took 3.4555795192718506s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 0.0005750656127929688s
Availability | VoID file availability check for Linked Open Numbers took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.2504284381866455s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.020457029342651367s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 9.274482727050781e-05s
Believability | Calculation of trust value for Linked Open Numbers took 6.67572021484375e-06s
INFO | --- Analysis for linked-open-numbers took 2.5478949546813965s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 5.91278076171875e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.27292847633361816s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.020050525665283203s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 2.6941299438476562e-05s
Believability | Calculation of trust value for Linked Open Piracy took 4.76837158203125e-06s
INFO | --- Analysis for linked-open-piracy took 7.050996780395508s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 4.8160552978515625e-05s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 0.2519514560699463s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.020066499710083008s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 2.7894973754882812e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 7.3909759521484375e-06s
INFO | --- Analysis for linked-open-senate took 2.9139456748962402s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 2.009185791015625s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.26693105697631836s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.0200803279876709s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 4.6253204345703125e-05s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 7.3909759521484375e-06s
INFO | --- Analysis for linked-open-vocabularies-lov took 10.337378025054932s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 7.43865966796875e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.25980496406555176s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.02063298225402832s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.552436828613281e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 5.0067901611328125e-06s
INFO | --- Analysis for linked-periodicals took 2.522080183029175s
Availability | SPARQL endpoint availability check for Linked Index took 4.172325134277344e-05s
Availability | VoID file availability check for Linked Index took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Linked Index took 0.2639036178588867s
Reputation | Calculation of the PageRank for Linked Index took 0.020174503326416016s
Interlinking | Calculation of Degree of Connection for Linked Index took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Index took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Linked Index took 9.584426879882812e-05s
Believability | Calculation of trust value for Linked Index took 7.3909759521484375e-06s
INFO | --- Analysis for linked-stockindex took 2.4902992248535156s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 4.724489450454712s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.27254271507263184s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.02039647102355957s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 3.695487976074219e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 7.152557373046875e-06s
INFO | --- Analysis for linked-structured-product-labels took 12.832247018814087s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.9843485355377197s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.2536318302154541s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.020215511322021484s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.0517578125e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 7.152557373046875e-06s
INFO | --- Analysis for linked-taiwan-geo-names took 4.852864027023315s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.24726152420044s
Availability | VoID file availability check for Linked TCGA took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.2780420780181885s
Reputation | Calculation of the PageRank for Linked TCGA took 0.02018594741821289s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 8.273124694824219e-05s
Believability | Calculation of trust value for Linked TCGA took 7.3909759521484375e-06s
INFO | --- Analysis for linked-tcga took 62.78501653671265s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.0927591323852539s
Availability | VoID file availability check for Linked User Feedback took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.24478864669799805s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.02013087272644043s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.457069396972656e-05s
Believability | Calculation of trust value for Linked User Feedback took 7.867813110351562e-06s
INFO | --- Analysis for linked-user-feedback took 2.5597946643829346s
Availability | SPARQL endpoint availability check for USPTO Patent data took 5.555152893066406e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0012044906616210938s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.2894096374511719s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.02033853530883789s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 8.058547973632812e-05s
Believability | Calculation of trust value for USPTO Patent data took 6.4373016357421875e-06s
INFO | --- Analysis for linked-uspto-patent-data took 53.567275524139404s
Availability | SPARQL endpoint availability check for Linked Web APIs dataset took 4.220008850097656e-05s
Availability | VoID file availability check for Linked Web APIs dataset took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.275954008102417s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.020449399948120117s
Interlinking | Calculation of Degree of Connection for Linked Web APIs dataset took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Linked Web APIs dataset took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Linked Web APIs dataset took 2.7418136596679688e-05s
Believability | Calculation of trust value for Linked Web APIs dataset took 1.239776611328125e-05s
INFO | --- Analysis for linked-web-apis took 2.960667371749878s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 5.2928924560546875e-05s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.2745683193206787s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 2.9087066650390625e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 8.106231689453125e-06s
INFO | --- Analysis for linkedarc took 2.9111287593841553s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.07202482223510742s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.24933362007141113s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.020164012908935547s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.0517578125e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 7.62939453125e-06s
INFO | --- Analysis for linkedcrowdsourceddata took 2.659759759902954s
Availability | SPARQL endpoint availability check for LinkedCT took 1.291548728942871s
Availability | VoID file availability check for LinkedCT took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.23664188385009766s
Reputation | Calculation of the PageRank for LinkedCT took 0.020205974578857422s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 9.584426879882812e-05s
Believability | Calculation of trust value for LinkedCT took 7.62939453125e-06s
INFO | --- Analysis for linkedct took 4.678564786911011s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.27573108673095703s
Availability | VoID file availability check for LinkedGeoData took 0.0005269050598144531s
Extra | Recovery of all triples for LinkedGeoData took 6.717899560928345s
Performance | Total latancy measurement for LinkedGeoData took 0.698051929473877s
Amount of data | Number of triples check for LinkedGeoData took 65.79954409599304s
Interoperability | New terms check for LinkedGeoData took 94.3711678981781s
Versatility | Languages check for LinkedGeoData took 180.39613699913025s
Interpretability | Number of blank nodes check for LinkedGeoData took 0.23865270614624023s
Security | Check HTTPS for LinkedGeoData took 0.34322476387023926s
Interpretability | RDF structures check for LinkedGeoData took 0.8646976947784424s
Versatility | Serialization formats check for LinkedGeoData took 0.36691761016845703s
Availability | RDF dump link check for LinkedGeoData took 0.1620771884918213s
License | MR license check for LinkedGeoData took 0.5818145275115967s
License | HR license check for LinkedGeoData took 91.33464527130127s
Amount of data | Number of property check for LinkedGeoData took 0.1821277141571045s
Understandability | Number of label check for LinkedGeoData took 2.3900601863861084s
Understandability | URI regex check for LinkedGeoData took 0.3988378047943115s
Understandability | Vocabs check for LinkedGeoData took 0.17766523361206055s
Verifiability | Authors check for LinkedGeoData took 0.1631162166595459s
Verifiability | Publishers check for LinkedGeoData took 0.13718295097351074s
Performance | Throughput check for LinkedGeoData took 10.642740964889526s
Amount of data | Check the number of entities for LinkedGeoData took 0.07561755180358887s
Verifiability | Contribs. check for LinkedGeoData took 2.057849645614624s
Interlinking | sameAs chians check for LinkedGeoData took 0.3016831874847412s
Interlinking | skos check for LinkedGeoData took 0.37538647651672363s
Interlinking | skos check for LinkedGeoData took 0.1380295753479004s
Timeliness | dataset update frequency check for LinkedGeoData took 0.3483402729034424s
Currency | Creation date check for LinkedGeoData took 0.47504353523254395s
Currency | Modification date check for LinkedGeoData took 2.739248275756836s
Rep.Conc. | URIs length for LinkedGeoData took 272.4509742259979s
Interoperability | New vocabularies check for LinkedGeoData took 94.60167169570923s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.1681520938873291s
Accuracy | Check Functional Property for LinkedGeoData took 0.21717453002929688s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.18553566932678223s
Accuracy | Check Empty annotation labels for LinkedGeoData took 1.8026478290557861s
Accuracy | Check White space in annotation for LinkedGeoData took 0.15684819221496582s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.13420653343200684s
Consistency | Disjoint class check for LinkedGeoData took 0.2627265453338623s
Consistency | Check Misplaced properties for LinkedGeoData took 180.7807400226593s
Consistency | Misplaced classes for LinkedGeoData took 0.6403927803039551s
Consistency | Check Ontology hijacking for LinkedGeoData took 3.305279493331909s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.1885075569152832s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 181.93740487098694s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.1523890495300293s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.25695204734802246s
Security | Sign check for LinkedGeoData took 0.7434999942779541s
Availability | Check URIs Dereferenciability for LinkedGeoData took 12.043832302093506s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 1.4055676460266113s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.020727872848510742s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00012230873107910156s
Interoperability | Check the re-using of existing vocabs for LinkedGeoData took 26.40820288658142s
Believability | Calculation of trust value for LinkedGeoData took 7.152557373046875e-06s
INFO | --- Analysis for linkedgeodata took 2315.0070192813873s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 4.57763671875e-05s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.262423038482666s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.021049022674560547s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007960796356201172s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 3.0994415283203125e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 8.344650268554688e-06s
INFO | --- Analysis for linkedgeodata-aerodromes took 4.163906574249268s
Availability | SPARQL endpoint availability check for LinkedLCCN took 1.129274606704712s
Availability | VoID file availability check for LinkedLCCN took 0.0003495216369628906s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.25904059410095215s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.02018880844116211s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00010466575622558594s
Believability | Calculation of trust value for LinkedLCCN took 6.67572021484375e-06s
INFO | --- Analysis for linkedlccn took 14.34568738937378s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 4.220008850097656e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.27432703971862793s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.020645618438720703s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.647804260253906e-05s
Believability | Calculation of trust value for LinkedMarkMail took 7.867813110351562e-06s
INFO | --- Analysis for linkedmarkmail took 3.471576690673828s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.628878116607666s
Availability | VoID file availability check for Linked Movie DataBase took 0.0007421970367431641s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.27686524391174316s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.020684480667114258s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00013971328735351562s
Believability | Calculation of trust value for Linked Movie DataBase took 6.9141387939453125e-06s
INFO | --- Analysis for linkedmdb took 133.4003381729126s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.4823176860809326s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 0.2496180534362793s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.020690441131591797s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0009522438049316406s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 8.487701416015625e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for linkedspending took 4.826861619949341s
Availability | SPARQL endpoint availability check for LinkedStats took 4.9591064453125e-05s
Availability | VoID file availability check for LinkedStats took 0.0006146430969238281s
Completeness | Calculation of interlinking completeness for LinkedStats took 0.7047901153564453s
Reputation | Calculation of the PageRank for LinkedStats took 0.020834922790527344s
Interlinking | Calculation of Degree of Connection for LinkedStats took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LinkedStats took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 3.24249267578125e-05s
Believability | Calculation of trust value for LinkedStats took 8.106231689453125e-06s
INFO | --- Analysis for linkedstats took 3.759906053543091s
Availability | SPARQL endpoint availability check for LinkedUp Catalogue of Educational Datasets took 4.172325134277344e-05s
Availability | VoID file availability check for LinkedUp Catalogue of Educational Datasets took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 0.26181864738464355s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.020357847213745117s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for LinkedUp Catalogue of Educational Datasets took 3.123283386230469e-05s
Believability | Calculation of trust value for LinkedUp Catalogue of Educational Datasets took 7.867813110351562e-06s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 2.9585611820220947s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 4.220008850097656e-05s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 0.24075865745544434s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.020528793334960938s
Interlinking | Calculation of Degree of Connection for Linking Open Drug Data (LODD) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linking Open Drug Data (LODD) took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Linking Open Drug Data (LODD) took 3.314018249511719e-05s
Believability | Calculation of trust value for Linking Open Drug Data (LODD) took 7.867813110351562e-06s
INFO | --- Analysis for linking-open-drug-data took 2.9015119075775146s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.05316638946533203s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.29091978073120117s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.02041935920715332s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0008149147033691406s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00011038780212402344s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 8.106231689453125e-06s
INFO | --- Analysis for linklion took 2.9250166416168213s
Availability | SPARQL endpoint availability check for Lion's Den took 3.981590270996094e-05s
Availability | VoID file availability check for Lion's Den took 0.0003020763397216797s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.25252294540405273s
Reputation | Calculation of the PageRank for Lion's Den took 0.020416259765625s
Interlinking | Calculation of Degree of Connection for Lion's Den took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Lion's Den took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 2.956390380859375e-05s
Believability | Calculation of trust value for Lion's Den took 8.106231689453125e-06s
INFO | --- Analysis for lionsden took 2.892723321914673s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 36.496309995651245s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.2500944137573242s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.020265817642211914s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 5.626678466796875e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for lista-encabezamientos-materia took 43.97936987876892s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 4.076957702636719e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 0.2818460464477539s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.020234107971191406s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 3.123283386230469e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 7.3909759521484375e-06s
INFO | --- Analysis for livtdm took 2.966118335723877s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 4.124641418457031e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.0003025531768798828s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.27303290367126465s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.0206758975982666s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 3.0994415283203125e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 8.106231689453125e-06s
INFO | --- Analysis for livtdm2017 took 2.9731342792510986s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 4.0531158447265625e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.27492713928222656s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.020492076873779297s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 3.0040740966796875e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 8.821487426757812e-06s
INFO | --- Analysis for lobi took 2.929262399673462s
Availability | SPARQL endpoint availability check for lobid-organisations took 1.1396512985229492s
Availability | VoID file availability check for lobid-organisations took 0.0007221698760986328s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.27199244499206543s
Reputation | Calculation of the PageRank for lobid-organisations took 0.0209653377532959s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.942054748535156e-05s
Believability | Calculation of trust value for lobid-organisations took 7.152557373046875e-06s
INFO | --- Analysis for lobid-organisations took 5.7684056758880615s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.9136080741882324s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0006597042083740234s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.2680490016937256s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.020461559295654297s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 9.989738464355469e-05s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 6.9141387939453125e-06s
INFO | --- Analysis for lobid-resources took 8.275240659713745s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.1961669921875e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.2733025550842285s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.020328044891357422s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 8.845329284667969e-05s
Believability | Calculation of trust value for Linked Open Colors took 7.152557373046875e-06s
INFO | --- Analysis for loc took 6.833439588546753s
Availability | SPARQL endpoint availability check for Location Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Location Ontology took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.2695784568786621s
Reputation | Calculation of the PageRank for Location Ontology took 0.0201113224029541s
Interlinking | Calculation of Degree of Connection for Location Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 2.7894973754882812e-05s
Believability | Calculation of trust value for Location Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for Location_Ontology took 4.426770448684692s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 4.315376281738281e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.2825887203216553s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.020241737365722656s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 2.7418136596679688e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 7.62939453125e-06s
INFO | --- Analysis for locv took 33.857491970062256s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.7578940391540527s
Availability | VoID file availability check for LOD-a-lot took 0.0007669925689697266s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.35870933532714844s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.020343303680419922s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 3.0279159545898438e-05s
Believability | Calculation of trust value for LOD-a-lot took 1.7642974853515625e-05s
INFO | --- Analysis for lod-a-lot took 14.13838815689087s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 4.1961669921875e-05s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.26912975311279297s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.020473241806030273s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0009710788726806641s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 4.029273986816406e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 1.2874603271484375e-05s
INFO | --- Analysis for lod-it_scuole-italiane took 3.424427032470703s
Availability | SPARQL endpoint availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 4.076957702636719e-05s
Availability | VoID file availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.2781999111175537s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.02022552490234375s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Open Data Web - a CKAN based linked open data repository in Taiwan took 2.9802322387695312e-05s
Believability | Calculation of trust value for Open Data Web - a CKAN based linked open data repository in Taiwan took 9.298324584960938e-06s
INFO | --- Analysis for lod-taiwan took 2.90840482711792s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.291534423828125e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.2650454044342041s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.02051234245300293s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 9.012222290039062e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 6.9141387939453125e-06s
INFO | --- Analysis for lod2-project-wiki took 3.633554697036743s
Availability | SPARQL endpoint availability check for LODAC BDLS took 3.014331102371216s
Availability | VoID file availability check for LODAC BDLS took 0.0005807876586914062s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.24728989601135254s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.020185232162475586s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 7.009506225585938e-05s
Believability | Calculation of trust value for LODAC BDLS took 7.62939453125e-06s
INFO | --- Analysis for lodac-bdls took 14.008584260940552s
Availability | SPARQL endpoint availability check for LODRussia Math took 4.458427429199219e-05s
Availability | VoID file availability check for LODRussia Math took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for LODRussia Math took 0.27440762519836426s
Reputation | Calculation of the PageRank for LODRussia Math took 0.020493030548095703s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LODRussia Math took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 2.956390380859375e-05s
Believability | Calculation of trust value for LODRussia Math took 7.867813110351562e-06s
INFO | --- Analysis for lodrussia-math took 2.950467586517334s
Availability | SPARQL endpoint availability check for LODRussia Nano took 4.100799560546875e-05s
Availability | VoID file availability check for LODRussia Nano took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 0.2538259029388428s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.020358562469482422s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 2.956390380859375e-05s
Believability | Calculation of trust value for LODRussia Nano took 8.106231689453125e-06s
INFO | --- Analysis for lodrussia-nano took 2.883828639984131s
Availability | SPARQL endpoint availability check for LODStats took 4.5299530029296875e-05s
Availability | VoID file availability check for LODStats took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for LODStats took 0.26238274574279785s
Reputation | Calculation of the PageRank for LODStats took 0.02036309242248535s
Interlinking | Calculation of Degree of Connection for LODStats took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for LODStats took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for LODStats took 3.0517578125e-05s
Believability | Calculation of trust value for LODStats took 8.58306884765625e-06s
INFO | --- Analysis for lodstats took 2.9795262813568115s
Availability | SPARQL endpoint availability check for LODUM took 4.124641418457031e-05s
Availability | VoID file availability check for LODUM took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for LODUM took 0.2595212459564209s
Reputation | Calculation of the PageRank for LODUM took 0.020509958267211914s
Interlinking | Calculation of Degree of Connection for LODUM took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for LODUM took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for LODUM took 2.9802322387695312e-05s
Believability | Calculation of trust value for LODUM took 6.67572021484375e-06s
INFO | --- Analysis for lodum took 2.853990077972412s
Availability | SPARQL endpoint availability check for lofd took 0.1319289207458496s
Availability | VoID file availability check for lofd took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for lofd took 0.2778291702270508s
Reputation | Calculation of the PageRank for lofd took 0.020267486572265625s
Interlinking | Calculation of Degree of Connection for lofd took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for lofd took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for lofd took 4.458427429199219e-05s
Believability | Calculation of trust value for lofd took 8.58306884765625e-06s
INFO | --- Analysis for lofd took 2.469804525375366s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 270.651300907135s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0006337165832519531s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.7827961444854736s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 5.078315734863281e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 5.0067901611328125e-06s
INFO | --- Analysis for loius took 584.6801769733429s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 6.937980651855469e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.2651083469390869s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.020594120025634766s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0008895397186279297s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 3.1948089599609375e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 6.9141387939453125e-06s
INFO | --- Analysis for loius-linking-italian-university-statistics took 3.5403573513031006s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 0.7380063533782959s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0012996196746826172s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.298475980758667s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.022154569625854492s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.507469177246094e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 5.9604644775390625e-06s
INFO | --- Analysis for london-gazette took 4.5995049476623535s
Availability | SPARQL endpoint availability check for Weather Stations took 4.1484832763671875e-05s
Availability | VoID file availability check for Weather Stations took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.2712984085083008s
Reputation | Calculation of the PageRank for Weather Stations took 0.020468473434448242s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 9.679794311523438e-05s
Believability | Calculation of trust value for Weather Stations took 7.3909759521484375e-06s
INFO | --- Analysis for los_metar took 82.4173994064331s
Availability | SPARQL endpoint availability check for Lotico took 0.9400458335876465s
Availability | VoID file availability check for Lotico took 0.0013539791107177734s
Completeness | Calculation of interlinking completeness for Lotico took 0.6975085735321045s
Reputation | Calculation of the PageRank for Lotico took 0.02030658721923828s
Interlinking | Calculation of Degree of Connection for Lotico took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0008556842803955078s
Interlinking | Calculation of Clustering coefficient for Lotico took 8.893013000488281e-05s
Believability | Calculation of trust value for Lotico took 7.867813110351562e-06s
INFO | --- Analysis for lotico took 7.2640135288238525s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 1.2395572662353516s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.26590776443481445s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.020237207412719727s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 2.9325485229492188e-05s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 6.4373016357421875e-06s
INFO | --- Analysis for lower-layer-super-output-areas took 8.562483787536621s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 393.5412871837616s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2508890628814697s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.020766258239746094s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0008883476257324219s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.743171691894531e-05s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.58306884765625e-06s
INFO | --- Analysis for LPIS_(Poland) took 668.5120177268982s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 393.7169682979584s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2586345672607422s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.020987987518310547s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 3.933906555175781e-05s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 7.152557373046875e-06s
INFO | --- Analysis for LPIS_Czech_Republic took 679.779536485672s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 4.172325134277344e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.24725794792175293s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.020800352096557617s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.0040740966796875e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 7.152557373046875e-06s
INFO | --- Analysis for lremap-auth took 5.453582763671875s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 4.1484832763671875e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.722205638885498s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.020328760147094727s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.0279159545898438e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 1.2159347534179688e-05s
INFO | --- Analysis for lremap-conf took 4.0116188526153564s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 4.172325134277344e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.00044035911560058594s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.7939572334289551s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.02015972137451172s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 2.9325485229492188e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 1.2636184692382812e-05s
INFO | --- Analysis for lremap-ri took 3.643395185470581s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 4.267692565917969e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.24933981895446777s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.020277738571166992s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 2.7894973754882812e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 7.3909759521484375e-06s
INFO | --- Analysis for lremap-sub took 2.6939735412597656s
Availability | SPARQL endpoint availability check for LSQ took 4.267692565917969e-05s
Availability | VoID file availability check for LSQ took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for LSQ took 0.2674062252044678s
Reputation | Calculation of the PageRank for LSQ took 0.020345211029052734s
Interlinking | Calculation of Degree of Connection for LSQ took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for LSQ took 2.9802322387695312e-05s
Believability | Calculation of trust value for LSQ took 7.152557373046875e-06s
INFO | --- Analysis for lsq took 3.502964496612549s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.5915231704711914s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.28243041038513184s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.020295381546020508s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 4.935264587402344e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for LucaniPharsalia took 4.087489366531372s
Availability | SPARQL endpoint availability check for Linked rules took 4.291534423828125e-05s
Availability | VoID file availability check for Linked rules took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for Linked rules took 0.2720143795013428s
Reputation | Calculation of the PageRank for Linked rules took 0.021941423416137695s
Interlinking | Calculation of Degree of Connection for Linked rules took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked rules took 0.0009243488311767578s
Interlinking | Calculation of Clustering coefficient for Linked rules took 3.743171691894531e-05s
Believability | Calculation of trust value for Linked rules took 6.9141387939453125e-06s
INFO | --- Analysis for Luminaires_senlis took 2.37947940826416s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 5.602836608886719e-05s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.24046826362609863s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.020386457443237305s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 3.24249267578125e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 7.62939453125e-06s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 2.8891875743865967s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.32920503616333s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0006995201110839844s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.26899194717407227s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.020445585250854492s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 3.838539123535156e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 7.3909759521484375e-06s
INFO | --- Analysis for makg took 98.55272793769836s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 4.3392181396484375e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.24671006202697754s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.020399093627929688s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.504753112792969e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 7.62939453125e-06s
INFO | --- Analysis for manchester-university-reading-lists took 3.419800043106079s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 5.7220458984375e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.2771115303039551s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020184755325317383s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.123283386230469e-05s
Believability | Calculation of trust value for engineering equipment ontology took 7.62939453125e-06s
INFO | --- Analysis for manish took 2.420552968978882s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá, Distrito Capital took 4.6253204345703125e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.29187798500061035s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.020391225814819336s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 3.0279159545898438e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 7.867813110351562e-06s
INFO | --- Analysis for mapa-referencia-bogota took 2.875270128250122s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá D.C took 4.2438507080078125e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá D.C took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.24814915657043457s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.020316362380981445s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 3.2901763916015625e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 6.67572021484375e-06s
INFO | --- Analysis for mapa-referencia-bogota-dc took 2.90097713470459s
Availability | SPARQL endpoint availability check for MARC Codes List took 4.863739013671875e-05s
Availability | VoID file availability check for MARC Codes List took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.2517411708831787s
Reputation | Calculation of the PageRank for MARC Codes List took 0.020180940628051758s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00011944770812988281s
Believability | Calculation of trust value for MARC Codes List took 7.3909759521484375e-06s
INFO | --- Analysis for marc-codes took 14.060050010681152s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.172325134277344e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.24958038330078125s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.020099401473999023s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 3.814697265625e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 9.775161743164062e-06s
INFO | --- Analysis for masc took 5.865369081497192s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 4.220008850097656e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.2542836666107178s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.020127534866333008s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.552436828613281e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 6.67572021484375e-06s
INFO | --- Analysis for masc-bn-nif took 2.3878800868988037s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.2904984951019287s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.26624417304992676s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.020430803298950195s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 2.956390380859375e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 7.3909759521484375e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 3.8099353313446045s
Availability | SPARQL endpoint availability check for medline took 4.267692565917969e-05s
Availability | VoID file availability check for medline took 0.0003559589385986328s
Completeness | Calculation of interlinking completeness for medline took 0.26661062240600586s
Reputation | Calculation of the PageRank for medline took 0.020313262939453125s
Interlinking | Calculation of Degree of Connection for medline took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for medline took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for medline took 3.4809112548828125e-05s
Believability | Calculation of trust value for medline took 7.62939453125e-06s
INFO | --- Analysis for medline took 6.970327138900757s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 3.4664406776428223s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.28012633323669434s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.02016139030456543s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 6.699562072753906e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 6.67572021484375e-06s
INFO | --- Analysis for meducator took 15.93324589729309s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 4.38690185546875e-05s
Availability | VoID file availability check for Finnish translation of mesh took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.29977989196777344s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.02014017105102539s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 2.7894973754882812e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 6.9141387939453125e-06s
INFO | --- Analysis for mesh-finnish took 2.9525883197784424s
Availability | SPARQL endpoint availability check for MeSH headings took 4.00543212890625e-05s
Availability | VoID file availability check for MeSH headings took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for MeSH headings took 0.2652702331542969s
Reputation | Calculation of the PageRank for MeSH headings took 0.02064967155456543s
Interlinking | Calculation of Degree of Connection for MeSH headings took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MeSH headings took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 2.9087066650390625e-05s
Believability | Calculation of trust value for MeSH headings took 7.3909759521484375e-06s
INFO | --- Analysis for mesh_headings took 2.953141212463379s
Availability | SPARQL endpoint availability check for MeSH, IPSV - SKOS RDF took 4.124641418457031e-05s
Availability | VoID file availability check for MeSH, IPSV - SKOS RDF took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 0.2687389850616455s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for MeSH, IPSV - SKOS RDF took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for MeSH, IPSV - SKOS RDF took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 2.9325485229492188e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 6.9141387939453125e-06s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 2.95123553276062s
Availability | SPARQL endpoint availability check for MeSH pairs took 3.9577484130859375e-05s
Availability | VoID file availability check for MeSH pairs took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for MeSH pairs took 0.2680344581604004s
Reputation | Calculation of the PageRank for MeSH pairs took 0.020088911056518555s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MeSH pairs took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 2.7179718017578125e-05s
Believability | Calculation of trust value for MeSH pairs took 1.239776611328125e-05s
INFO | --- Analysis for mesh_pairs took 2.9272074699401855s
Availability | SPARQL endpoint availability check for MeSH titles took 3.933906555175781e-05s
Availability | VoID file availability check for MeSH titles took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.23938846588134766s
Reputation | Calculation of the PageRank for MeSH titles took 0.02039933204650879s
Interlinking | Calculation of Degree of Connection for MeSH titles took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MeSH titles took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 2.956390380859375e-05s
Believability | Calculation of trust value for MeSH titles took 7.3909759521484375e-06s
INFO | --- Analysis for mesh_titles took 2.875397205352783s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 4.863739013671875e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.2918720245361328s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.020195960998535156s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.0008149147033691406s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 3.266334533691406e-05s
Believability | Calculation of trust value for Metadata k zákonům z psp.cz took 7.3909759521484375e-06s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 2.9478297233581543s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 4.267692565917969e-05s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.2717318534851074s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.020243406295776367s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 3.0040740966796875e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 8.344650268554688e-06s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 2.943519353866577s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 4.863739013671875e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.26919102668762207s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.02019810676574707s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 6.866455078125e-05s
Believability | Calculation of trust value for MetaShare metadata model took 1.0728836059570312e-05s
INFO | --- Analysis for metashare took 2.5903093814849854s
Availability | SPARQL endpoint availability check for MExiCo took 4.220008850097656e-05s
Availability | VoID file availability check for MExiCo took 0.0007715225219726562s
Completeness | Calculation of interlinking completeness for MExiCo took 0.2774159908294678s
Reputation | Calculation of the PageRank for MExiCo took 0.020374059677124023s
Interlinking | Calculation of Degree of Connection for MExiCo took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MExiCo took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for MExiCo took 4.9591064453125e-05s
Believability | Calculation of trust value for MExiCo took 7.152557373046875e-06s
INFO | --- Analysis for mexico took 22.484076499938965s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.1058151721954346s
Availability | VoID file availability check for Coronavirus dataset took 0.00025534629821777344s
Extra | Recovery of all triples for Coronavirus dataset took 5.919557809829712s
Performance | Total latancy measurement for Coronavirus dataset took 2.4863269329071045s
Amount of data | Number of triples check for Coronavirus dataset took 1.2016878128051758s
Interoperability | New terms check for Coronavirus dataset took 2.4423086643218994s
Versatility | Languages check for Coronavirus dataset took 60.52119302749634s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.945431709289551s
Interpretability | RDF structures check for Coronavirus dataset took 0.5537407398223877s
Versatility | Serialization formats check for Coronavirus dataset took 0.5480382442474365s
Availability | RDF dump link check for Coronavirus dataset took 0.4965949058532715s
License | MR license check for Coronavirus dataset took 0.568584680557251s
License | HR license check for Coronavirus dataset took 41.39068007469177s
Amount of data | Number of property check for Coronavirus dataset took 0.5418260097503662s
Understandability | Number of label check for Coronavirus dataset took 1.5401639938354492s
Understandability | URI regex check for Coronavirus dataset took 1.0060434341430664s
Understandability | Vocabs check for Coronavirus dataset took 0.4922752380371094s
Verifiability | Authors check for Coronavirus dataset took 0.5543961524963379s
Verifiability | Publishers check for Coronavirus dataset took 0.5073835849761963s
Performance | Throughput check for Coronavirus dataset took 14.294692277908325s
Amount of data | Check the number of entities for Coronavirus dataset took 8.392333984375e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.5031335353851318s
Interlinking | sameAs chians check for Coronavirus dataset took 0.5269582271575928s
Interlinking | skos check for Coronavirus dataset took 0.5543055534362793s
Interlinking | skos check for Coronavirus dataset took 0.4946169853210449s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.5121324062347412s
Currency | Creation date check for Coronavirus dataset took 1.0486690998077393s
Currency | Modification date check for Coronavirus dataset took 1.0194287300109863s
Rep.Conc. | URIs length for Coronavirus dataset took 8.739170789718628s
Interoperability | New vocabularies check for Coronavirus dataset took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.5367262363433838s
Accuracy | Check Functional Property for Coronavirus dataset took 0.6947569847106934s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.6682529449462891s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.144585609436035s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.022514820098876953s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.02768111228942871s
Consistency | Disjoint class check for Coronavirus dataset took 0.9267265796661377s
Consistency | Check Misplaced properties for Coronavirus dataset took 7.582243919372559s
Consistency | Misplaced classes for Coronavirus dataset took 0.6052401065826416s
Consistency | Check Ontology hijacking for Coronavirus dataset took 3.26037859916687s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.1625080108642578s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 6.542634010314941s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.03170323371887207s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.5414443016052246s
Security | Sign check for Coronavirus dataset took 0.5202193260192871s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 3133.6866495609283s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 1.1858117580413818s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.02396678924560547s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 7.224082946777344e-05s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for Coronavirus dataset took 1.1682510375976562e-05s
INFO | --- Analysis for micro-coronavirus took 3366.9997940063477s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 5.2928924560546875e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.7325935363769531s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.020151376724243164s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00010776519775390625s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 7.3909759521484375e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 6.209365129470825s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 4.4345855712890625e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0006246566772460938s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.2720513343811035s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.020524978637695312s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00011014938354492188s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 6.198883056640625e-06s
INFO | --- Analysis for mismuseos-gnoss took 7.756411790847778s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.10654997825622559s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.2810978889465332s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.020197629928588867s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.458427429199219e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 7.867813110351562e-06s
INFO | --- Analysis for mlsa took 2.8940513134002686s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 4.291534423828125e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.24088096618652344s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.020060300827026367s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 2.765655517578125e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 7.3909759521484375e-06s
INFO | --- Analysis for model took 31.039358854293823s
Availability | SPARQL endpoint availability check for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 4.267692565917969e-05s
Availability | VoID file availability check for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.271012544631958s
Reputation | Calculation of the PageRank for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.020275115966796875s
Interlinking | Calculation of Degree of Connection for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 2.9087066650390625e-05s
Believability | Calculation of trust value for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 6.9141387939453125e-06s
INFO | --- Analysis for model1 took 17.794397830963135s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 4.124641418457031e-05s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.2791907787322998s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.02026677131652832s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 2.8133392333984375e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 7.3909759521484375e-06s
INFO | --- Analysis for mond took 3.5936944484710693s
Availability | SPARQL endpoint availability check for MONDIS took 4.0531158447265625e-05s
Availability | VoID file availability check for MONDIS took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for MONDIS took 0.2725553512573242s
Reputation | Calculation of the PageRank for MONDIS took 0.020351886749267578s
Interlinking | Calculation of Degree of Connection for MONDIS took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for MONDIS took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for MONDIS took 2.86102294921875e-05s
Believability | Calculation of trust value for MONDIS took 7.867813110351562e-06s
INFO | --- Analysis for mondis took 3.0243632793426514s
Availability | SPARQL endpoint availability check for Monumentos took 4.029273986816406e-05s
Availability | VoID file availability check for Monumentos took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Monumentos took 0.2523825168609619s
Reputation | Calculation of the PageRank for Monumentos took 0.020848512649536133s
Interlinking | Calculation of Degree of Connection for Monumentos took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Monumentos took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Monumentos took 2.8133392333984375e-05s
Believability | Calculation of trust value for Monumentos took 7.3909759521484375e-06s
INFO | --- Analysis for monumentos-zaragoza took 3.0113186836242676s
Availability | SPARQL endpoint availability check for MORElab took 1.7603161334991455s
Availability | VoID file availability check for MORElab took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for MORElab took 0.2635219097137451s
Reputation | Calculation of the PageRank for MORElab took 0.02029109001159668s
Interlinking | Calculation of Degree of Connection for MORElab took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MORElab took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for MORElab took 8.797645568847656e-05s
Believability | Calculation of trust value for MORElab took 7.152557373046875e-06s
INFO | --- Analysis for morelab took 5.45792293548584s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 1.8371264934539795s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.31635093688964844s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.020063161849975586s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.654594421386719e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 6.9141387939453125e-06s
INFO | --- Analysis for msc took 6.265951156616211s
Availability | SPARQL endpoint availability check for Multext-East took 4.506111145019531e-05s
Availability | VoID file availability check for Multext-East took 0.0003399848937988281s
Completeness | Calculation of interlinking completeness for Multext-East took 0.2881464958190918s
Reputation | Calculation of the PageRank for Multext-East took 0.021451711654663086s
Interlinking | Calculation of Degree of Connection for Multext-East took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Multext-East took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.361701965332031e-05s
Believability | Calculation of trust value for Multext-East took 7.152557373046875e-06s
INFO | --- Analysis for multext-east took 2.510063409805298s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 4.649162292480469e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.30306291580200195s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.020079374313354492s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 2.8371810913085938e-05s
Believability | Calculation of trust value for The DGT Multilingual Translation Memory of the Acquis Communautaire took 7.62939453125e-06s
INFO | --- Analysis for multilingualeulaw took 2.90499210357666s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.220008850097656e-05s
Availability | VoID file availability check for Multimedia Lab took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.2799525260925293s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.02022075653076172s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.314018249511719e-05s
Believability | Calculation of trust value for Multimedia Lab took 8.106231689453125e-06s
INFO | --- Analysis for multimedia-lab took 2.513476610183716s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 4.124641418457031e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.26007819175720215s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.02051377296447754s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 2.9802322387695312e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 6.9141387939453125e-06s
INFO | --- Analysis for munich-offener-haushalt took 2.9622082710266113s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.5925452709197998s
Availability | VoID file availability check for Muninn World War I took 0.0011436939239501953s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.25379300117492676s
Reputation | Calculation of the PageRank for Muninn World War I took 0.02025580406188965s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.130073547363281e-05s
Believability | Calculation of trust value for Muninn World War I took 1.0013580322265625e-05s
INFO | --- Analysis for muninn-world-war-i took 10.443154573440552s
Availability | SPARQL endpoint availability check for Musei Italiani took 4.124641418457031e-05s
Availability | VoID file availability check for Musei Italiani took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.2575345039367676s
Reputation | Calculation of the PageRank for Musei Italiani took 0.0204317569732666s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Musei Italiani took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 2.956390380859375e-05s
Believability | Calculation of trust value for Musei Italiani took 7.152557373046875e-06s
INFO | --- Analysis for musei-italiani took 2.9421916007995605s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 4.363059997558594e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.2748713493347168s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.020366907119750977s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00011801719665527344s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for museosespania-gnoss took 67.11570477485657s
Availability | SPARQL endpoint availability check for Italian Museums took 1.6869690418243408s
Availability | VoID file availability check for Italian Museums took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.26464200019836426s
Reputation | Calculation of the PageRank for Italian Museums took 0.020586013793945312s
Interlinking | Calculation of Degree of Connection for Italian Museums took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 8.0108642578125e-05s
Believability | Calculation of trust value for Italian Museums took 6.67572021484375e-06s
INFO | --- Analysis for museums-in-italy took 4.174534559249878s
Availability | SPARQL endpoint availability check for MusicBrainz took 4.00543212890625e-05s
Availability | VoID file availability check for MusicBrainz took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.2689225673675537s
Reputation | Calculation of the PageRank for MusicBrainz took 0.020433425903320312s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MusicBrainz took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 2.9087066650390625e-05s
Believability | Calculation of trust value for MusicBrainz took 8.106231689453125e-06s
INFO | --- Analysis for musicbrainz_ took 2.97147274017334s
Availability | SPARQL endpoint availability check for MusicNet Codex took 5.435943603515625e-05s
Availability | VoID file availability check for MusicNet Codex took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.25466299057006836s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.020388364791870117s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 3.0994415283203125e-05s
Believability | Calculation of trust value for MusicNet Codex took 7.62939453125e-06s
INFO | --- Analysis for musicnet_codex took 3.418703317642212s
Availability | SPARQL endpoint availability check for Muziekweb took 0.6783778667449951s
Availability | VoID file availability check for Muziekweb took 0.0006458759307861328s
Extra | Recovery of all triples for Muziekweb took 2.026728630065918s
Performance | Total latancy measurement for Muziekweb took 1.4010159969329834s
Amount of data | Number of triples check for Muziekweb took 0.3790156841278076s
Interoperability | New terms check for Muziekweb took 1.6263971328735352s
Versatility | Languages check for Muziekweb took 57.853843450546265s
Interpretability | Number of blank nodes check for Muziekweb took 0.31066060066223145s
Interpretability | RDF structures check for Muziekweb took 0.7740120887756348s
Versatility | Serialization formats check for Muziekweb took 0.2866249084472656s
Availability | RDF dump link check for Muziekweb took 0.2857332229614258s
License | MR license check for Muziekweb took 0.6003010272979736s
License | HR license check for Muziekweb took 15.351937532424927s
Amount of data | Number of property check for Muziekweb took 0.26990365982055664s
Understandability | Number of label check for Muziekweb took 0.3181467056274414s
Understandability | URI regex check for Muziekweb took 0.5802068710327148s
Understandability | Vocabs check for Muziekweb took 0.25455141067504883s
Verifiability | Authors check for Muziekweb took 0.26685214042663574s
Verifiability | Publishers check for Muziekweb took 0.2861030101776123s
Performance | Throughput check for Muziekweb took 11.202882766723633s
Amount of data | Check the number of entities for Muziekweb took 6.866455078125e-05s
Verifiability | Contribs. check for Muziekweb took 0.28957200050354004s
Interlinking | sameAs chians check for Muziekweb took 0.3250882625579834s
Interlinking | skos check for Muziekweb took 0.2998478412628174s
Interlinking | skos check for Muziekweb took 0.2957749366760254s
Timeliness | dataset update frequency check for Muziekweb took 0.2973141670227051s
Currency | Creation date check for Muziekweb took 0.8281834125518799s
Currency | Modification date check for Muziekweb took 0.7356891632080078s
Rep.Conc. | URIs length for Muziekweb took 1.8951687812805176s
Interoperability | New vocabularies check for Muziekweb took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.2926323413848877s
Accuracy | Check Functional Property for Muziekweb took 0.41701221466064453s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.44003963470458984s
Accuracy | Check Empty annotation labels for Muziekweb took 0.8658416271209717s
Accuracy | Check White space in annotation for Muziekweb took 0.033394813537597656s
Accuracy | Check Datatype consistency for Muziekweb took 0.028789520263671875s
Consistency | Disjoint class check for Muziekweb took 0.5134341716766357s
Consistency | Check Misplaced properties for Muziekweb took 1.1657295227050781s
Consistency | Check Ontology hijacking for Muziekweb took 2.10530424118042s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 2.0713627338409424s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.45351243019104s
Conciseness | Check Extensional conciseness for Muziekweb took 0.032590627670288086s
Conciseness | Check Intensional conciseness for Muziekweb took 0.2718043327331543s
Security | Sign check for Muziekweb took 0.2769291400909424s
Availability | Check URIs Dereferenciability for Muziekweb took 1755.273256778717s
Completeness | Calculation of interlinking completeness for Muziekweb took 0.5786752700805664s
Reputation | Calculation of the PageRank for Muziekweb took 0.02058696746826172s
Interlinking | Calculation of Degree of Connection for Muziekweb took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 6.318092346191406e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.6689300537109375e-06s
Believability | Calculation of trust value for Muziekweb took 6.9141387939453125e-06s
INFO | --- Analysis for muziekweb took 1889.3316042423248s
Availability | SPARQL endpoint availability check for myExperiment took 0.25234007835388184s
Availability | VoID file availability check for myExperiment took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for myExperiment took 0.2644474506378174s
Reputation | Calculation of the PageRank for myExperiment took 0.0202176570892334s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for myExperiment took 9.369850158691406e-05s
Believability | Calculation of trust value for myExperiment took 7.3909759521484375e-06s
INFO | --- Analysis for my-experiment took 4.830349683761597s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.09354448318481445s
Availability | VoID file availability check for My Family Lineage took 0.0006315708160400391s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.2593839168548584s
Reputation | Calculation of the PageRank for My Family Lineage took 0.020518779754638672s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.845329284667969e-05s
Believability | Calculation of trust value for My Family Lineage took 7.152557373046875e-06s
INFO | --- Analysis for my-family-lineage took 4.94187068939209s
Availability | SPARQL endpoint availability check for My ontology test took 0.45810675621032715s
Availability | VoID file availability check for My ontology test took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for My ontology test took 0.2559030055999756s
Reputation | Calculation of the PageRank for My ontology test took 0.020833492279052734s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0009772777557373047s
Interlinking | Calculation of Clustering coefficient for My ontology test took 3.4809112548828125e-05s
Believability | Calculation of trust value for My ontology test took 7.867813110351562e-06s
INFO | --- Analysis for myontologytest took 4.056888580322266s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 4.291534423828125e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.29050636291503906s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.020183324813842773s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 9.918212890625e-05s
Believability | Calculation of trust value for myopenlink dataspaces took 8.344650268554688e-06s
INFO | --- Analysis for myopenlink-dataspaces took 2.8192286491394043s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 4.10073447227478s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0007252693176269531s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.25736570358276367s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.020177841186523438s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 6.890296936035156e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for n-lex-as-linked-data took 10.986689805984497s
Availability | SPARQL endpoint availability check for NAICS 2007 took 25.83886694908142s
Availability | VoID file availability check for NAICS 2007 took 0.0009162425994873047s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.26923608779907227s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.020716190338134766s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 4.38690185546875e-05s
Believability | Calculation of trust value for NAICS 2007 took 6.4373016357421875e-06s
INFO | --- Analysis for naics-2007 took 125.21158957481384s
Availability | SPARQL endpoint availability check for NAICS 2012 took 24.34803533554077s
Availability | VoID file availability check for NAICS 2012 took 0.0015361309051513672s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.7259101867675781s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.020676851272583008s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 5.626678466796875e-05s
Believability | Calculation of trust value for NAICS 2012 took 6.4373016357421875e-06s
INFO | --- Analysis for naics-2012 took 124.06591749191284s
Availability | SPARQL endpoint availability check for National Agricultural Library Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for National Agricultural Library Thesaurus took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 0.2830054759979248s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.020265817642211914s
Interlinking | Calculation of Degree of Connection for National Agricultural Library Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for National Agricultural Library Thesaurus took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 5.125999450683594e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for nalt took 4.061825752258301s
Availability | SPARQL endpoint availability check for Usernames  took 4.220008850097656e-05s
Availability | VoID file availability check for Usernames  took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Usernames  took 0.25585365295410156s
Reputation | Calculation of the PageRank for Usernames  took 0.020444869995117188s
Interlinking | Calculation of Degree of Connection for Usernames  took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Usernames  took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Usernames  took 3.0040740966796875e-05s
Believability | Calculation of trust value for Usernames  took 7.62939453125e-06s
INFO | --- Analysis for Names took 2.3586270809173584s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 1.2186074256896973s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0008025169372558594s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 2.153944492340088s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 1.9251682758331299s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 12.144471168518066s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 29.895904302597046s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.3743321895599365s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.962121725082397s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.845304012298584s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.38779211044311523s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.4027223587036133s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.40211963653564453s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.37105250358581543s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.79383492469788s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.8826718330383301s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 8.072824001312256s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 0.7514150142669678s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.41994190216064453s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.36044764518737793s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.34335756301879883s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 11.45271897315979s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 8.58306884765625e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.32708120346069336s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.5268123149871826s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.8455801010131836s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.0506958961486816s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.3785672187805176s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.1209685802459717s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 0.7687690258026123s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 0.9800360202789307s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.3716278076171875s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.36670422554016113s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.3746795654296875s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.4430708885192871s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0007951259613037109s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0010111331939697266s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.38758087158203125s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.7031683921813965s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.41053056716918945s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.5615062713623047s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.2019257545471191s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.5823638439178467s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0006124973297119141s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.3390069007873535s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 3.662553071975708s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.7550094127655029s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.02067112922668457s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 6.461143493652344e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.430511474609375e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 8.821487426757812e-06s
INFO | --- Analysis for national-diet-library-authorities took 244.35189938545227s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.3868110179901123s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.00067138671875s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 0.8328378200531006s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 7.196280002593994s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.973868370056152s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.8611629009246826s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 19.19391632080078s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.35549354553222656s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.3875162601470947s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.4204895496368408s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.3301577568054199s
License | MR license check for National Diet Library of Japan subject headings took 0.3912322521209717s
License | HR license check for National Diet Library of Japan subject headings took 91.84804272651672s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.8622832298278809s
Understandability | Number of label check for National Diet Library of Japan subject headings took 5.567306756973267s
Understandability | URI regex check for National Diet Library of Japan subject headings took 0.7413849830627441s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.3887143135070801s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.3546416759490967s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.43808913230895996s
Performance | Throughput check for National Diet Library of Japan subject headings took 11.415234804153442s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 0.0001480579376220703s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.36414408683776855s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.5774049758911133s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.6204416751861572s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.4025120735168457s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.33524131774902344s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.088045358657837s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.7696719169616699s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 0.9956562519073486s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.3762390613555908s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.32774949073791504s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.38628506660461426s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.40757203102111816s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0007653236389160156s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0010802745819091797s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.37584471702575684s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.7739565372467041s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.37322187423706055s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.6189243793487549s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.1855475902557373s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.5508606433868408s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0005891323089599609s
Security | Sign check for National Diet Library of Japan subject headings took 0.3883183002471924s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 3.5467681884765625s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 1.2211380004882812s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.02054286003112793s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 6.651878356933594e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.430511474609375e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 7.62939453125e-06s
INFO | --- Analysis for national-diet-library-subject-headings took 310.07674765586853s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 0.8768770694732666s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0007336139678955078s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.2737855911254883s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.020375967025756836s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.267692565917969e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 6.9141387939453125e-06s
INFO | --- Analysis for national-library-of-greece-authority-records took 6.4776997566223145s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 4.291534423828125e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2593820095062256s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020239591598510742s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0009429454803466797s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 8.058547973632812e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 9.775161743164062e-06s
INFO | --- Analysis for Naturopathy took 3.4215214252471924s
Availability | SPARQL endpoint availability check for Naturopathy took 4.124641418457031e-05s
Availability | VoID file availability check for Naturopathy took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for Naturopathy took 0.26380467414855957s
Reputation | Calculation of the PageRank for Naturopathy took 0.02059173583984375s
Interlinking | Calculation of Degree of Connection for Naturopathy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Naturopathy took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 2.7894973754882812e-05s
Believability | Calculation of trust value for Naturopathy took 9.059906005859375e-06s
INFO | --- Analysis for naturopathy2 took 2.98762845993042s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.0531158447265625e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.25261425971984863s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020082712173461914s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 2.86102294921875e-05s
Believability | Calculation of trust value for NCI Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for nci-thesaurus took 3.37430739402771s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.445613384246826s
Availability | VoID file availability check for COVID-19 Data took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.25990843772888184s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.02053523063659668s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 2.956390380859375e-05s
Believability | Calculation of trust value for COVID-19 Data took 6.4373016357421875e-06s
INFO | --- Analysis for NCMI-COVID-19 took 7.359474182128906s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.4084930419921875s
Availability | VoID file availability check for NCMI-COVID-19 took 0.00030684471130371094s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.27112412452697754s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.020390033721923828s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.239776611328125e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 7.3909759521484375e-06s
INFO | --- Analysis for NCMICOVID-19 took 6.7199718952178955s
Availability | SPARQL endpoint availability check for NDF-RT took 4.1961669921875e-05s
Availability | VoID file availability check for NDF-RT took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.24912023544311523s
Reputation | Calculation of the PageRank for NDF-RT took 0.020357131958007812s
Interlinking | Calculation of Degree of Connection for NDF-RT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NDF-RT took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 3.0279159545898438e-05s
Believability | Calculation of trust value for NDF-RT took 8.344650268554688e-06s
INFO | --- Analysis for ndf-rt took 3.334524393081665s
Availability | SPARQL endpoint availability check for Near took 0.00011873245239257812s
Availability | VoID file availability check for Near took 0.0007307529449462891s
Completeness | Calculation of interlinking completeness for Near took 0.3070409297943115s
Reputation | Calculation of the PageRank for Near took 0.020303964614868164s
Interlinking | Calculation of Degree of Connection for Near took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Near took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Near took 8.988380432128906e-05s
Believability | Calculation of trust value for Near took 7.867813110351562e-06s
INFO | --- Analysis for near took 9.239622831344604s
Availability | SPARQL endpoint availability check for Neel took 4.100799560546875e-05s
Availability | VoID file availability check for Neel took 0.000244140625s
Completeness | Calculation of interlinking completeness for Neel took 0.2710578441619873s
Reputation | Calculation of the PageRank for Neel took 0.02043747901916504s
Interlinking | Calculation of Degree of Connection for Neel took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Neel took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for Neel took 3.0040740966796875e-05s
Believability | Calculation of trust value for Neel took 1.2874603271484375e-05s
INFO | --- Analysis for neel took 2.9895665645599365s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 4.00543212890625e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.24035072326660156s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.02022099494934082s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 3.0040740966796875e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 7.152557373046875e-06s
INFO | --- Analysis for neurocommons_text_mining_pilot took 2.890989065170288s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 4.267692565917969e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.2920351028442383s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.020252227783203125s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 2.9802322387695312e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 7.62939453125e-06s
INFO | --- Analysis for neurolex-wiki took 2.4372143745422363s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 4.315376281738281e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.000640869140625s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.2743651866912842s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.02064061164855957s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.410743713378906e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 8.106231689453125e-06s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 3.4666199684143066s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 4.220008850097656e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.2656240463256836s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.02018284797668457s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 6.651878356933594e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 1.2159347534179688e-05s
INFO | --- Analysis for news-100-nif-ner-corpus took 4.15134596824646s
Availability | SPARQL endpoint availability check for Newsweek took 5.078315734863281e-05s
Availability | VoID file availability check for Newsweek took 0.000244140625s
Completeness | Calculation of interlinking completeness for Newsweek took 0.2859923839569092s
Reputation | Calculation of the PageRank for Newsweek took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for Newsweek took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Newsweek took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Newsweek took 3.0517578125e-05s
Believability | Calculation of trust value for Newsweek took 7.867813110351562e-06s
INFO | --- Analysis for newsweek took 2.9782533645629883s
Availability | SPARQL endpoint availability check for neXtProt took 1.7633423805236816s
Availability | VoID file availability check for neXtProt took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for neXtProt took 0.26924562454223633s
Reputation | Calculation of the PageRank for neXtProt took 0.020212650299072266s
Interlinking | Calculation of Degree of Connection for neXtProt took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for neXtProt took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for neXtProt took 3.552436828613281e-05s
Believability | Calculation of trust value for neXtProt took 7.62939453125e-06s
INFO | --- Analysis for nextprot took 4.816978216171265s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 4.38690185546875e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007336139678955078s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.28132128715515137s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.02064347267150879s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00010037422180175781s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 6.9141387939453125e-06s
INFO | --- Analysis for nextweb-gnoss took 8.092024564743042s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 4.291534423828125e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.00038623809814453125s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.262235164642334s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.02034926414489746s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 7.915496826171875e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 4.5299530029296875e-06s
INFO | --- Analysis for nhs-jargon took 5.087095737457275s
Availability | SPARQL endpoint availability check for NIT Patna took 4.363059997558594e-05s
Availability | VoID file availability check for NIT Patna took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.2739899158477783s
Reputation | Calculation of the PageRank for NIT Patna took 0.02047896385192871s
Interlinking | Calculation of Degree of Connection for NIT Patna took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 7.82012939453125e-05s
Believability | Calculation of trust value for NIT Patna took 1.0967254638671875e-05s
INFO | --- Analysis for NITP took 3.39404034614563s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 4.172325134277344e-05s
Availability | VoID file availability check for NLM 2007 MeSH took 0.00022029876708984375s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.2861366271972656s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.020299434661865234s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 3.361701965332031e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 6.9141387939453125e-06s
INFO | --- Analysis for nlm_2007_mesh took 3.0280964374542236s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 4.267692565917969e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.2539985179901123s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.0203855037689209s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 2.8848648071289062e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 7.867813110351562e-06s
INFO | --- Analysis for nlr-dataset-mod took 4.071805238723755s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.6293377876281738s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0007512569427490234s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.2791423797607422s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.021924257278442383s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0008130073547363281s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 4.673004150390625e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for NLW took 4.136002063751221s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.7636642456054688s
Availability | VoID file availability check for Nobel Prizes took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.28290581703186035s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.020199298858642578s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.179115295410156e-05s
Believability | Calculation of trust value for Nobel Prizes took 7.867813110351562e-06s
INFO | --- Analysis for nobelprizes took 8.752366542816162s
Availability | SPARQL endpoint availability check for NoiPA took 0.42780399322509766s
Availability | VoID file availability check for NoiPA took 0.00032448768615722656s
Extra | Recovery of all triples for NoiPA took 73.82980036735535s
Performance | Total latancy measurement for NoiPA took 0.9805300235748291s
Amount of data | Number of triples check for NoiPA took 1.7341454029083252s
Interoperability | New terms check for NoiPA took 2.949251890182495s
Versatility | Languages check for NoiPA took 0.19613337516784668s
Interpretability | Number of blank nodes check for NoiPA took 0.17538022994995117s
Interpretability | RDF structures check for NoiPA took 0.6358983516693115s
Versatility | Serialization formats check for NoiPA took 0.6966736316680908s
Availability | RDF dump link check for NoiPA took 0.226318359375s
License | MR license check for NoiPA took 1.4613523483276367s
License | HR license check for NoiPA took 60.21579837799072s
Amount of data | Number of property check for NoiPA took 0.19846081733703613s
Understandability | Number of label check for NoiPA took 2.2040605545043945s
Understandability | URI regex check for NoiPA took 0.748589277267456s
Understandability | Vocabs check for NoiPA took 0.18848729133605957s
Verifiability | Authors check for NoiPA took 0.632843017578125s
Verifiability | Publishers check for NoiPA took 0.6656265258789062s
Performance | Throughput check for NoiPA took 10.625375747680664s
Amount of data | Check the number of entities for NoiPA took 7.200241088867188e-05s
Verifiability | Contribs. check for NoiPA took 0.1585097312927246s
Interlinking | sameAs chians check for NoiPA took 0.13129973411560059s
Interlinking | skos check for NoiPA took 1.574084758758545s
Interlinking | skos check for NoiPA took 0.15114355087280273s
Timeliness | dataset update frequency check for NoiPA took 0.6392457485198975s
Currency | Creation date check for NoiPA took 0.955374002456665s
Currency | Modification date check for NoiPA took 0.1777646541595459s
Rep.Conc. | URIs length for NoiPA took 58.216492891311646s
Interoperability | New vocabularies check for NoiPA took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.169447660446167s
Accuracy | Check Functional Property for NoiPA took 0.2469942569732666s
Accuracy | Check Inverse Functional Property for NoiPA took 0.2700045108795166s
Accuracy | Check Empty annotation labels for NoiPA took 28.7214834690094s
Accuracy | Check White space in annotation for NoiPA took 2.206373453140259s
Accuracy | Check Datatype consistency for NoiPA took 2.0273945331573486s
Consistency | Disjoint class check for NoiPA took 0.3098156452178955s
Consistency | Check Misplaced properties for NoiPA took 18.370933055877686s
Consistency | Misplaced classes for NoiPA took 6.3489463329315186s
Consistency | Check Ontology hijacking for NoiPA took 26.208815813064575s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.505465030670166s
Consistency | Check Invalid usage of undefined properties for NoiPA took 20.520789623260498s
Conciseness | Check Extensional conciseness for NoiPA took 2.1731972694396973s
Conciseness | Check Intensional conciseness for NoiPA took 0.1575167179107666s
Security | Sign check for NoiPA took 0.22907495498657227s
Availability | Check URIs Dereferenciability for NoiPA took 11.863107681274414s
Completeness | Calculation of interlinking completeness for NoiPA took 0.3078749179840088s
Reputation | Calculation of the PageRank for NoiPA took 0.021061420440673828s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for NoiPA took 3.3855438232421875e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 2.1457672119140625e-06s
Believability | Calculation of trust value for NoiPA took 8.821487426757812e-06s
INFO | --- Analysis for NoiPA took 481.38493275642395s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 6.5765769481658936s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0006628036499023438s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.2742736339569092s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.02026987075805664s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 8.630752563476562e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 7.152557373046875e-06s
INFO | --- Analysis for nom took 23.47273015975952s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 24.859962940216064s
Availability | VoID file availability check for Nomenclator Asturias took 0.0009443759918212891s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.4112086296081543s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.02078557014465332s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 8.106231689453125e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 1.8835067749023438e-05s
INFO | --- Analysis for nomenclator-asturias took 137.49281120300293s
Availability | SPARQL endpoint availability check for nomisma took 5.4836273193359375e-05s
Availability | VoID file availability check for nomisma took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for nomisma took 0.2957496643066406s
Reputation | Calculation of the PageRank for nomisma took 0.020585298538208008s
Interlinking | Calculation of Degree of Connection for nomisma took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for nomisma took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for nomisma took 3.170967102050781e-05s
Believability | Calculation of trust value for nomisma took 8.821487426757812e-06s
INFO | --- Analysis for nomisma took 4.49449348449707s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.4445366859436035s
Availability | VoID file availability check for Nomisma.org  took 0.0007193088531494141s
Extra | Recovery of all triples for Nomisma.org  took 444.227445602417s
Performance | Total latancy measurement for Nomisma.org  took 2.5077075958251953s
Amount of data | Number of triples check for Nomisma.org  took 33.910765409469604s
Interoperability | New terms check for Nomisma.org  took 8.625030279159546s
Versatility | Languages check for Nomisma.org  took 105.41759610176086s
Interpretability | Number of blank nodes check for Nomisma.org  took 41.24906611442566s
Security | Check HTTPS for Nomisma.org  took 0.7933406829833984s
Interpretability | RDF structures check for Nomisma.org  took 0.4251224994659424s
Versatility | Serialization formats check for Nomisma.org  took 0.9643456935882568s
Availability | RDF dump link check for Nomisma.org  took 972.7203214168549s
License | MR license check for Nomisma.org  took 0.4580116271972656s
License | HR license check for Nomisma.org  took 58.98555040359497s
Amount of data | Number of property check for Nomisma.org  took 0.4004342555999756s
Understandability | Number of label check for Nomisma.org  took 7.294180870056152s
Understandability | URI regex check for Nomisma.org  took 1.0486061573028564s
Understandability | Vocabs check for Nomisma.org  took 0.344714879989624s
Verifiability | Authors check for Nomisma.org  took 0.4033970832824707s
Verifiability | Publishers check for Nomisma.org  took 0.4329061508178711s
Performance | Throughput check for Nomisma.org  took 10.664209127426147s
Amount of data | Check the number of entities for Nomisma.org  took 0.0004956722259521484s
Verifiability | Contribs. check for Nomisma.org  took 0.4192788600921631s
Interlinking | sameAs chians check for Nomisma.org  took 0.36371827125549316s
Interlinking | skos check for Nomisma.org  took 1.1116023063659668s
Interlinking | skos check for Nomisma.org  took 0.5476841926574707s
Timeliness | dataset update frequency check for Nomisma.org  took 0.35253167152404785s
Currency | Creation date check for Nomisma.org  took 0.7027804851531982s
Currency | Modification date check for Nomisma.org  took 0.3745718002319336s
Rep.Conc. | URIs length for Nomisma.org  took 408.9200220108032s
Interoperability | New vocabularies check for Nomisma.org  took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.37552547454833984s
Accuracy | Check Functional Property for Nomisma.org  took 0.3594527244567871s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.3338603973388672s
Consistency | Disjoint class check for Nomisma.org  took 0.39922261238098145s
Consistency | Check Misplaced properties for Nomisma.org  took 30.03747272491455s
Consistency | Check Ontology hijacking for Nomisma.org  took 443.11539816856384s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 29.25814986228943s
Conciseness | Check Extensional conciseness for Nomisma.org  took 0.0001404285430908203s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.4022374153137207s
Security | Sign check for Nomisma.org  took 0.4852449893951416s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 0.7217752933502197s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.023986339569091797s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 4.744529724121094e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 1.6689300537109375e-06s
Believability | Calculation of trust value for Nomisma.org  took 6.9141387939453125e-06s
INFO | --- Analysis for nomisma_org took 6586.560743331909s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.6171779632568359s
Availability | VoID file availability check for Curriculum Vitae took 0.0002636909484863281s
Extra | Recovery of all triples for Curriculum Vitae took 0.7174856662750244s
Performance | Total latancy measurement for Curriculum Vitae took 0.7929298877716064s
Amount of data | Number of triples check for Curriculum Vitae took 0.11370635032653809s
Interoperability | New terms check for Curriculum Vitae took 1.3275816440582275s
Versatility | Languages check for Curriculum Vitae took 0.14919209480285645s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.13321232795715332s
Interpretability | RDF structures check for Curriculum Vitae took 0.3288547992706299s
Versatility | Serialization formats check for Curriculum Vitae took 0.30371785163879395s
Availability | RDF dump link check for Curriculum Vitae took 0.13901662826538086s
License | MR license check for Curriculum Vitae took 0.11212992668151855s
License | HR license check for Curriculum Vitae took 0.12585663795471191s
Amount of data | Number of property check for Curriculum Vitae took 0.17074966430664062s
Understandability | Number of label check for Curriculum Vitae took 0.12874484062194824s
Understandability | URI regex check for Curriculum Vitae took 0.29606151580810547s
Understandability | Vocabs check for Curriculum Vitae took 0.12041616439819336s
Verifiability | Authors check for Curriculum Vitae took 0.11925101280212402s
Verifiability | Publishers check for Curriculum Vitae took 0.16206741333007812s
Performance | Throughput check for Curriculum Vitae took 10.740673303604126s
Amount of data | Check the number of entities for Curriculum Vitae took 7.724761962890625e-05s
Verifiability | Contribs. check for Curriculum Vitae took 0.12967252731323242s
Interlinking | sameAs chians check for Curriculum Vitae took 0.14621543884277344s
Interlinking | skos check for Curriculum Vitae took 0.12852096557617188s
Interlinking | skos check for Curriculum Vitae took 0.14737796783447266s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.14137625694274902s
Currency | Creation date check for Curriculum Vitae took 0.2569108009338379s
Currency | Modification date check for Curriculum Vitae took 0.29973459243774414s
Rep.Conc. | URIs length for Curriculum Vitae took 0.34331274032592773s
Interoperability | New vocabularies check for Curriculum Vitae took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.1317121982574463s
Accuracy | Check Functional Property for Curriculum Vitae took 0.13998103141784668s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.12295818328857422s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.14641189575195312s
Accuracy | Check White space in annotation for Curriculum Vitae took 0.00011157989501953125s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.0031135082244873047s
Consistency | Disjoint class check for Curriculum Vitae took 0.14370250701904297s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.26212143898010254s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.3167924880981445s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.1790528297424316s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.2949225902557373s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.0014073848724365234s
Security | Sign check for Curriculum Vitae took 0.1283564567565918s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 19.136521577835083s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.27838683128356934s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.02020859718322754s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 3.910064697265625e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 1.1920928955078125e-06s
Believability | Calculation of trust value for Curriculum Vitae took 1.239776611328125e-05s
INFO | --- Analysis for Nordine_Bittich took 52.86519122123718s
Availability | SPARQL endpoint availability check for NorPark took 1.077467441558838s
Availability | VoID file availability check for NorPark took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for NorPark took 0.7604036331176758s
Reputation | Calculation of the PageRank for NorPark took 0.020526647567749023s
Interlinking | Calculation of Degree of Connection for NorPark took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for NorPark took 5.435943603515625e-05s
Believability | Calculation of trust value for NorPark took 6.9141387939453125e-06s
INFO | --- Analysis for norpark took 4.967586040496826s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.021740436553955078s
Availability | VoID file availability check for Parking Dataset took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.2680671215057373s
Reputation | Calculation of the PageRank for Parking Dataset took 0.020148038864135742s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.482269287109375e-05s
Believability | Calculation of trust value for Parking Dataset took 7.62939453125e-06s
INFO | --- Analysis for norpark2 took 2.9009950160980225s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 0.9833359718322754s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.7131004333496094s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.02044081687927246s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 2.956390380859375e-05s
Believability | Calculation of trust value for Norway fishery stocks dataset took 6.67572021484375e-06s
INFO | --- Analysis for Norway_Fishery_ took 4.8831627368927s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.3432145118713379s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.2919039726257324s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.020139217376708984s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 4.5299530029296875e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 6.4373016357421875e-06s
INFO | --- Analysis for norwegian-geo-divisions took 7.294722557067871s
Availability | SPARQL endpoint availability check for NorwegianSoE took 0.0004520416259765625s
Availability | VoID file availability check for NorwegianSoE took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 0.2781064510345459s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.02033519744873047s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 2.9802322387695312e-05s
Believability | Calculation of trust value for NorwegianSoE took 2.0742416381835938e-05s
INFO | --- Analysis for norwegiansoe took 3.447005033493042s
Availability | SPARQL endpoint availability check for NITP took 5.1021575927734375e-05s
Availability | VoID file availability check for NITP took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for NITP took 0.296234130859375s
Reputation | Calculation of the PageRank for NITP took 0.020091772079467773s
Interlinking | Calculation of Degree of Connection for NITP took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NITP took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for NITP took 6.604194641113281e-05s
Believability | Calculation of trust value for NITP took 5.7220458984375e-06s
INFO | --- Analysis for notIdentifier took 3.090174436569214s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.267692565917969e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0005426406860351562s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.3249399662017822s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.02033376693725586s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.552436828613281e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 7.152557373046875e-06s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 3.3241732120513916s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 4.291534423828125e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.2538619041442871s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.020310163497924805s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 2.9802322387695312e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 7.152557373046875e-06s
INFO | --- Analysis for npg took 3.3492939472198486s
Availability | SPARQL endpoint availability check for NPM took 4.2438507080078125e-05s
Availability | VoID file availability check for NPM took 0.0006551742553710938s
Completeness | Calculation of interlinking completeness for NPM took 0.28319764137268066s
Reputation | Calculation of the PageRank for NPM took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for NPM took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NPM took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for NPM took 3.314018249511719e-05s
Believability | Calculation of trust value for NPM took 7.867813110351562e-06s
INFO | --- Analysis for npm took 3.208033800125122s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.04556131362915039s
Availability | VoID file availability check for NTNU special collections took 0.0005869865417480469s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.27201128005981445s
Reputation | Calculation of the PageRank for NTNU special collections took 0.020385026931762695s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.888938903808594e-05s
Believability | Calculation of trust value for NTNU special collections took 7.3909759521484375e-06s
INFO | --- Analysis for ntnusc took 5.366283893585205s
Availability | SPARQL endpoint availability check for links took 4.1484832763671875e-05s
Availability | VoID file availability check for links took 0.00029754638671875s
Completeness | Calculation of interlinking completeness for links took 0.2801938056945801s
Reputation | Calculation of the PageRank for links took 0.020650148391723633s
Interlinking | Calculation of Degree of Connection for links took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for links took 0.0009965896606445312s
Interlinking | Calculation of Clustering coefficient for links took 1.239776611328125e-05s
Believability | Calculation of trust value for links took 7.62939453125e-06s
INFO | --- Analysis for nugmyanmar took 2.401416540145874s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 5.4836273193359375e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.25667262077331543s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.02008676528930664s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 9.489059448242188e-05s
Believability | Calculation of trust value for NUTS (GeoVocab) took 4.76837158203125e-06s
INFO | --- Analysis for nuts-geovocab took 2.487797975540161s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.4351499080657959s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.2483367919921875s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.020121097564697266s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 6.914138793945312e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 7.62939453125e-06s
INFO | --- Analysis for nvd took 4.060393810272217s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.8374118804931641s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0006978511810302734s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.2546272277832031s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.020336627960205078s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 8.225440979003906e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 1.3113021850585938e-05s
INFO | --- Analysis for nvs took 8.068261861801147s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 4.506111145019531e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.2629542350769043s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.020726680755615234s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.0001862049102783203s
Believability | Calculation of trust value for New York Times - Linked Open Data took 8.58306884765625e-06s
INFO | --- Analysis for nytimes-linked-open-data took 2.514629602432251s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 4.00543212890625e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.269179105758667s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.020308971405029297s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 3.0279159545898438e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 8.344650268554688e-06s
INFO | --- Analysis for o-anc took 2.966336965560913s
Availability | SPARQL endpoint availability check for OANetzwerk took 5.245208740234375e-05s
Availability | VoID file availability check for OANetzwerk took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for OANetzwerk took 0.2771005630493164s
Reputation | Calculation of the PageRank for OANetzwerk took 0.02034926414489746s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OANetzwerk took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 3.123283386230469e-05s
Believability | Calculation of trust value for OANetzwerk took 7.3909759521484375e-06s
INFO | --- Analysis for oanetzwerk took 2.9578683376312256s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 4.1961669921875e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.24868130683898926s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.020208358764648438s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 3.0279159545898438e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 7.62939453125e-06s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 2.8758702278137207s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.5329647064208984s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0005719661712646484s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 1.9871058464050293s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 1.7982125282287598s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 2.780026912689209s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.8501434326171875s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 60.3382306098938s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 2.358055591583252s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 1.7981247901916504s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.36809682846069336s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.4813802242279053s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.4384925365447998s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.3514430522918701s
License | HR license check for Italian Chamber of Deputies - official dataset took 60.209691286087036s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 3.2395083904266357s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 1.1090528964996338s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 1.2702665328979492s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 1.7593345642089844s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 1.6480600833892822s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 1.9694712162017822s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 11.29455852508545s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 3.24249267578125e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.3860750198364258s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.3721189498901367s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.38391852378845215s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.348419189453125s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.40703439712524414s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.6458563804626465s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.3482170104980469s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 17.790125370025635s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 1.150451898574829s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 0.367326021194458s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.38231682777404785s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 1.038231611251831s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.0300447940826416s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.028615474700927734s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.3687629699707031s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 13.512683391571045s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.4396505355834961s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 2.256465196609497s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.1761362552642822s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 14.203561782836914s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.03534746170043945s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.4068424701690674s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.33531904220581055s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 11.425240516662598s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.40529727935791016s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.033762454986572266s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 3.0279159545898438e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.001239776611328125s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.00012826919555664062s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 7.152557373046875e-06s
INFO | --- Analysis for ocd took 419.68626046180725s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 4.291534423828125e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0006821155548095703s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.2953183650970459s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.020138025283813477s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 4.1484832763671875e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 7.152557373046875e-06s
INFO | --- Analysis for oceandrilling-borehole took 3.723674774169922s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 1.3257477283477783s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0006937980651855469s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.2673952579498291s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.020114898681640625s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 8.058547973632812e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 7.152557373046875e-06s
INFO | --- Analysis for oceandrilling-codices took 7.105223178863525s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 1.2741327285766602s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.3060436248779297s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.020359516143798828s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.1948089599609375e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 7.3909759521484375e-06s
INFO | --- Analysis for oceandrilling-dbseabed took 6.130248546600342s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 1.2844510078430176s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0007481575012207031s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.2693181037902832s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.020328283309936523s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.24249267578125e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 9.298324584960938e-06s
INFO | --- Analysis for oceandrilling-forams took 6.04979944229126s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 1.150787115097046s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0008053779602050781s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.2839059829711914s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.020435094833374023s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.361701965332031e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 7.867813110351562e-06s
INFO | --- Analysis for oceandrilling-janus took 5.754796504974365s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 11.00440526008606s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.24846339225769043s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.02031850814819336s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.4809112548828125e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 6.67572021484375e-06s
INFO | --- Analysis for oceandrilling-janusamp took 15.735649824142456s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.1851427555084229s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007174015045166016s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.2642507553100586s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.020290613174438477s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.956390380859375e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 6.67572021484375e-06s
INFO | --- Analysis for oceandrilling-ldeo took 5.723794221878052s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 4.410743713378906e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.2899320125579834s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.0201413631439209s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.340576171875e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 1.1444091796875e-05s
INFO | --- Analysis for oclc-fast took 10.409376382827759s
Availability | SPARQL endpoint availability check for Open Data Communities took 6.556510925292969e-05s
Availability | VoID file availability check for Open Data Communities took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.27256107330322266s
Reputation | Calculation of the PageRank for Open Data Communities took 0.020059585571289062s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Open Data Communities took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 2.9087066650390625e-05s
Believability | Calculation of trust value for Open Data Communities took 6.67572021484375e-06s
INFO | --- Analysis for odc took 3.0261478424072266s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.38690185546875e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.5108191967010498s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.27724647521972656s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.020267486572265625s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 2.86102294921875e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 5.4836273193359375e-06s
INFO | --- Analysis for odc-imd-environment-score took 4.78574275970459s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 4.076957702636719e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.2741541862487793s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.020215988159179688s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation Ranking, 2007 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation Ranking, 2007 took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 2.9087066650390625e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 8.106231689453125e-06s
INFO | --- Analysis for odc-imd-rank-2007 took 2.9167487621307373s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 1.3706316947937012s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.8575611114501953s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.26760125160217285s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.020257234573364258s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 4.839897155761719e-05s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 5.245208740234375e-06s
INFO | --- Analysis for odc-lsoa took 7.535619735717773s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 4.124641418457031e-05s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.2658541202545166s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.02070331573486328s
Interlinking | Calculation of Degree of Connection for Estimated mid-year population 2005 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Estimated mid-year population 2005 took 0.0010175704956054688s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 3.3855438232421875e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 6.9141387939453125e-06s
INFO | --- Analysis for odc-population-2005 took 2.970348834991455s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 4.076957702636719e-05s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.2648963928222656s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.020183086395263672s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 7.152557373046875e-06s
INFO | --- Analysis for ods took 3.0152316093444824s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.3345656394958496s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0005166530609130859s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.2667567729949951s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.020585298538208008s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.00012421607971191406s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for oecd-linked-data took 2.797436475753784s
Availability | SPARQL endpoint availability check for Offener Haushalt took 4.029273986816406e-05s
Availability | VoID file availability check for Offener Haushalt took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 0.26947474479675293s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.02040243148803711s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 3.0994415283203125e-05s
Believability | Calculation of trust value for Offener Haushalt took 7.152557373046875e-06s
INFO | --- Analysis for offener-haushalt took 3.014214277267456s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.16628408432007s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.2609870433807373s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.020843505859375s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.1961669921875e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 8.106231689453125e-06s
INFO | --- Analysis for ogolod took 102.67102146148682s
Availability | SPARQL endpoint availability check for OLAC Metadata took 7.43865966796875e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.2847776412963867s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.020465373992919922s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 3.600120544433594e-05s
Believability | Calculation of trust value for OLAC Metadata took 7.152557373046875e-06s
INFO | --- Analysis for olac took 22.75611114501953s
Availability | SPARQL endpoint availability check for OLiA took 4.1961669921875e-05s
Availability | VoID file availability check for OLiA took 0.0007371902465820312s
Completeness | Calculation of interlinking completeness for OLiA took 0.25612854957580566s
Reputation | Calculation of the PageRank for OLiA took 0.020726680755615234s
Interlinking | Calculation of Degree of Connection for OLiA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0008368492126464844s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.0001270771026611328s
Believability | Calculation of trust value for OLiA took 6.67572021484375e-06s
INFO | --- Analysis for olia took 12.903640985488892s
Availability | SPARQL endpoint availability check for OLiA Discourse took 4.124641418457031e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0007662773132324219s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.24497413635253906s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.020133256912231445s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 3.886222839355469e-05s
Believability | Calculation of trust value for OLiA Discourse took 7.62939453125e-06s
INFO | --- Analysis for olia-discourse took 7.511814117431641s
Availability | SPARQL endpoint availability check for Open Land Use took 0.2913496494293213s
Availability | VoID file availability check for Open Land Use took 0.00024247169494628906s
Extra | Recovery of all triples for Open Land Use took 114.5594117641449s
Performance | Total latancy measurement for Open Land Use took 0.9007489681243896s
Amount of data | Number of triples check for Open Land Use took 20.39895486831665s
Interoperability | New terms check for Open Land Use took 13.674517393112183s
Versatility | Languages check for Open Land Use took 300.164265871048s
Interpretability | Number of blank nodes check for Open Land Use took 3.085442304611206s
Interpretability | RDF structures check for Open Land Use took 1.6332266330718994s
Versatility | Serialization formats check for Open Land Use took 9.94456934928894s
Availability | RDF dump link check for Open Land Use took 0.2137305736541748s
License | MR license check for Open Land Use took 1.1640284061431885s
License | HR license check for Open Land Use took 300.1498112678528s
Amount of data | Number of property check for Open Land Use took 0.40792012214660645s
Understandability | Number of label check for Open Land Use took 3.4313344955444336s
Understandability | URI regex check for Open Land Use took 0.5555670261383057s
Understandability | Vocabs check for Open Land Use took 0.2541487216949463s
Verifiability | Authors check for Open Land Use took 0.4281501770019531s
Verifiability | Publishers check for Open Land Use took 0.6370940208435059s
Performance | Throughput check for Open Land Use took 10.81292176246643s
Amount of data | Check the number of entities for Open Land Use took 6.67572021484375e-05s
Verifiability | Contribs. check for Open Land Use took 0.2589104175567627s
Interlinking | sameAs chians check for Open Land Use took 0.24672818183898926s
Interlinking | skos check for Open Land Use took 1.2304537296295166s
Interlinking | skos check for Open Land Use took 0.4466285705566406s
Timeliness | dataset update frequency check for Open Land Use took 5.152061700820923s
Currency | Creation date check for Open Land Use took 2.6284019947052s
Currency | Modification date check for Open Land Use took 0.4353923797607422s
Rep.Conc. | URIs length for Open Land Use took 158.42677760124207s
Interoperability | New vocabularies check for Open Land Use took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Open Land Use took 0.19596171379089355s
Accuracy | Check Functional Property for Open Land Use took 0.2465965747833252s
Accuracy | Check Inverse Functional Property for Open Land Use took 0.24710988998413086s
Accuracy | Check Empty annotation labels for Open Land Use took 41.821030616760254s
Accuracy | Check White space in annotation for Open Land Use took 2.654407024383545s
Accuracy | Check Datatype consistency for Open Land Use took 2.68581223487854s
Consistency | Disjoint class check for Open Land Use took 0.36354923248291016s
Consistency | Check Misplaced properties for Open Land Use took 82.72381019592285s
Consistency | Misplaced classes for Open Land Use took 8.74720811843872s
Consistency | Check Ontology hijacking for Open Land Use took 42.04414772987366s
Consistency | Check Invalid usage of undefined classes for Open Land Use took 1.2473247051239014s
Consistency | Check Invalid usage of undefined properties for Open Land Use took 85.5545244216919s
Conciseness | Check Extensional conciseness for Open Land Use took 2.754929542541504s
Conciseness | Check Intensional conciseness for Open Land Use took 0.5615074634552002s
Security | Sign check for Open Land Use took 0.803544282913208s
Availability | Check URIs Dereferenciability for Open Land Use took 9.914446353912354s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.6505236625671387s
Reputation | Calculation of the PageRank for Open Land Use took 0.020695924758911133s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0009064674377441406s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use took 1.9073486328125e-06s
Believability | Calculation of trust value for Open Land Use took 7.152557373046875e-06s
INFO | --- Analysis for OLU took 2272.5775706768036s
Availability | SPARQL endpoint availability check for OmegaWiki took 4.172325134277344e-05s
Availability | VoID file availability check for OmegaWiki took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for OmegaWiki took 0.2532780170440674s
Reputation | Calculation of the PageRank for OmegaWiki took 0.020420312881469727s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OmegaWiki took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 2.9802322387695312e-05s
Believability | Calculation of trust value for OmegaWiki took 7.3909759521484375e-06s
INFO | --- Analysis for omegawiki took 4.898404121398926s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.5849008560180664s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0002224445343017578s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.7056684494018555s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.02024984359741211s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-als took 4.150467395782471s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.19846343994140625s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.2458019256591797s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.020142555236816406s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-arb took 2.797020435333252s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.19187474250793457s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0004222393035888672s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.26391100883483887s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.02017974853515625s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 6.4373016357421875e-06s
INFO | --- Analysis for omwn-bul took 3.738095760345459s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.19665765762329102s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.23901081085205078s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020245790481567383s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-cow took 2.811577081680298s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.23323297500610352s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2608494758605957s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020084381103515625s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
INFO | --- Analysis for omwn-cwn took 2.773806571960449s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.1989736557006836s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.2554957866668701s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.020224571228027344s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 4.2438507080078125e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-dan took 3.151987075805664s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.20220136642456055s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.00021004676818847656s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.23391222953796387s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.020120859146118164s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 3.552436828613281e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-ell took 2.718655586242676s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.22188258171081543s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.2526214122772217s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.02042984962463379s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-eng took 2.77653169631958s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.18823480606079102s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.00021648406982421875s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.2653694152832031s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.020227909088134766s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-fas took 2.729552984237671s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.19091796875s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.27420735359191895s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.020283937454223633s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 7.843971252441406e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-fin took 2.8460893630981445s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.19446897506713867s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.27100610733032227s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.02018880844116211s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 3.62396240234375e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 6.4373016357421875e-06s
INFO | --- Analysis for omwn-fra took 2.813751697540283s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.24683356285095215s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.00041866302490234375s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.26691412925720215s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.020215272903442383s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 3.7670135498046875e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 6.198883056640625e-06s
INFO | --- Analysis for omwn-heb took 2.893580436706543s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.2713186740875244s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.253389835357666s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.020232439041137695s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 6.4373016357421875e-06s
INFO | --- Analysis for omwn-hrv took 2.859177350997925s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.18936967849731445s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.000209808349609375s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.27519702911376953s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.02026081085205078s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.5497207641601562e-05s
INFO | --- Analysis for omwn-isl took 2.737985610961914s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.2050318717956543s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.2498030662536621s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.020214557647705078s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-ita took 2.8035213947296143s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.23214221000671387s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.259505033493042s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.02025461196899414s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 3.600120544433594e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 6.4373016357421875e-06s
INFO | --- Analysis for omwn-iwn took 2.8110570907592773s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.18953943252563477s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.24261999130249023s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.020129919052124023s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-jpn took 2.8042075634002686s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.17314982414245605s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.00022935867309570312s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.26233458518981934s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.020184755325317383s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 3.552436828613281e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-mcr took 2.721721649169922s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.17931652069091797s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2537822723388672s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0206911563873291s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.3589859008789062e-05s
INFO | --- Analysis for omwn-msa took 2.8410837650299072s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.17800617218017578s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.25482821464538574s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.02039027214050293s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-nld took 2.718442440032959s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.18868517875671387s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.000400543212890625s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.2635490894317627s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.020154476165771484s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 4.315376281738281e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 6.4373016357421875e-06s
INFO | --- Analysis for omwn-nor took 2.7545509338378906s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.19817304611206055s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.00021696090698242188s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.24909329414367676s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.020537376403808594s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-pol took 3.767151355743408s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.20062851905822754s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2600548267364502s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.020237445831298828s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-por took 2.707428216934204s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.18875646591186523s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.286022424697876s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.020224571228027344s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-ron took 2.9185919761657715s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.17473077774047852s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.24222779273986816s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.020266294479370117s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-slk took 2.675344705581665s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.20057916641235352s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.2703275680541992s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.020546674728393555s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-slv took 2.737208843231201s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.20754766464233398s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0002167224884033203s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.25523829460144043s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0203094482421875s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-swe took 3.743208646774292s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.22046852111816406s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.0002181529998779297s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.2444007396697998s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.020174264907836914s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-tha took 2.879812717437744s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 4.701833009719849s
Availability | VoID file availability check for OntoBeef Domain took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.27330756187438965s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.02024364471435547s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.5299530029296875e-05s
Believability | Calculation of trust value for OntoBeef Domain took 7.867813110351562e-06s
INFO | --- Analysis for ontobeef-domain took 31.579344034194946s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.172325134277344e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.2623405456542969s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.020255327224731445s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 9.632110595703125e-05s
Believability | Calculation of trust value for Ontos News Portal took 7.62939453125e-06s
INFO | --- Analysis for ontos-news-portal took 6.052778005599976s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 4.363059997558594e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.2314302921295166s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.020429372787475586s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 2.956390380859375e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 7.152557373046875e-06s
INFO | --- Analysis for ookaboo-rdf-dump took 2.403794288635254s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 4.1961669921875e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0007407665252685547s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.2762258052825928s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.0205535888671875s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 4.553794860839844e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 8.344650268554688e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 13.060096979141235s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 4.100799560546875e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.2652885913848877s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.020355939865112305s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 3.0994415283203125e-05s
Believability | Calculation of trust value for Open Courseware Consortium metadata in RDF took 7.3909759521484375e-06s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 2.770658254623413s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 0.0006191730499267578s
Availability | VoID file availability check for Open Data Euskadi took 0.0006945133209228516s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.24092674255371094s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.020421266555786133s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 4.8160552978515625e-05s
Believability | Calculation of trust value for Open Data Euskadi took 5.245208740234375e-06s
INFO | --- Analysis for open-data-euskadi took 9.063889980316162s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 4.2438507080078125e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.2578580379486084s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.020129919052124023s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.0001049041748046875s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 7.3909759521484375e-06s
INFO | --- Analysis for open-data-risp took 6.600985527038574s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.28911375999450684s
Availability | VoID file availability check for Open Data Thesaurus took 0.0006301403045654297s
Extra | Recovery of all triples for Open Data Thesaurus took 1.8008081912994385s
Performance | Total latancy measurement for Open Data Thesaurus took 0.4730567932128906s
Amount of data | Number of triples check for Open Data Thesaurus took 0.12552213668823242s
Interoperability | New terms check for Open Data Thesaurus took 1.2768471240997314s
Versatility | Languages check for Open Data Thesaurus took 0.1091606616973877s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.1046593189239502s
Security | Check HTTPS for Open Data Thesaurus took 0.356522798538208s
Interpretability | RDF structures check for Open Data Thesaurus took 0.11612319946289062s
Versatility | Serialization formats check for Open Data Thesaurus took 0.133955717086792s
Availability | RDF dump link check for Open Data Thesaurus took 1.1054413318634033s
License | MR license check for Open Data Thesaurus took 0.10956740379333496s
License | HR license check for Open Data Thesaurus took 0.0939483642578125s
Amount of data | Number of property check for Open Data Thesaurus took 0.12773370742797852s
Understandability | Number of label check for Open Data Thesaurus took 0.11928367614746094s
Understandability | URI regex check for Open Data Thesaurus took 0.17388296127319336s
Understandability | Vocabs check for Open Data Thesaurus took 0.11700081825256348s
Verifiability | Authors check for Open Data Thesaurus took 0.1313619613647461s
Verifiability | Publishers check for Open Data Thesaurus took 0.12058353424072266s
Performance | Throughput check for Open Data Thesaurus took 10.413395881652832s
Amount of data | Check the number of entities for Open Data Thesaurus took 6.985664367675781e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.13297677040100098s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.12720966339111328s
Interlinking | skos check for Open Data Thesaurus took 0.12915277481079102s
Interlinking | skos check for Open Data Thesaurus took 0.08922338485717773s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.09328818321228027s
Currency | Creation date check for Open Data Thesaurus took 0.19178295135498047s
Currency | Modification date check for Open Data Thesaurus took 0.21188950538635254s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.5575723648071289s
Interoperability | New vocabularies check for Open Data Thesaurus took 3.4800198078155518s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.13016748428344727s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.10784387588500977s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.08882665634155273s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.1575634479522705s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011289119720458984s
Consistency | Disjoint class check for Open Data Thesaurus took 0.07828736305236816s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.20512723922729492s
Consistency | Misplaced classes for Open Data Thesaurus took 0.08881044387817383s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.3691484928131104s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.2736454010009766s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.00013899803161621094s
Security | Sign check for Open Data Thesaurus took 0.1109323501586914s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.27199435234069824s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.019908666610717773s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 9.036064147949219e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Thesaurus took 2.981541633605957s
Believability | Calculation of trust value for Open Data Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for open-data-thesaurus took 67.95585060119629s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 4.1961669921875e-05s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.2774026393890381s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.020290136337280273s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 2.8848648071289062e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 7.867813110351562e-06s
INFO | --- Analysis for open-data-tor-vergata took 2.8666365146636963s
Availability | SPARQL endpoint availability check for Open Election Data Project took 4.220008850097656e-05s
Availability | VoID file availability check for Open Election Data Project took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.23927521705627441s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.020264863967895508s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.985664367675781e-05s
Believability | Calculation of trust value for Open Election Data Project took 4.5299530029296875e-06s
INFO | --- Analysis for open-election-data-project took 2.352576971054077s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 3.7741503715515137s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0007050037384033203s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.2413933277130127s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.02044057846069336s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.001001119613647461s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 0.00010275840759277344s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 5.245208740234375e-06s
INFO | --- Analysis for open-energy-info-wiki took 10.37189245223999s
Availability | SPARQL endpoint availability check for Open Library took 4.172325134277344e-05s
Availability | VoID file availability check for Open Library took 0.0007688999176025391s
Completeness | Calculation of interlinking completeness for Open Library took 0.25698113441467285s
Reputation | Calculation of the PageRank for Open Library took 0.020217180252075195s
Interlinking | Calculation of Degree of Connection for Open Library took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open Library took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Open Library took 6.628036499023438e-05s
Believability | Calculation of trust value for Open Library took 7.3909759521484375e-06s
INFO | --- Analysis for open-library took 9.9509859085083s
Availability | SPARQL endpoint availability check for Open Directory took 4.076957702636719e-05s
Availability | VoID file availability check for Open Directory took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Open Directory took 0.24118685722351074s
Reputation | Calculation of the PageRank for Open Directory took 0.020149946212768555s
Interlinking | Calculation of Degree of Connection for Open Directory took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open Directory took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Open Directory took 3.0040740966796875e-05s
Believability | Calculation of trust value for Open Directory took 7.62939453125e-06s
INFO | --- Analysis for open_directory took 2.7841596603393555s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.18021202087402344s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0002665519714355469s
Extra | Recovery of all triples for Open Land Use @PSNC took 110.98499870300293s
Performance | Total latancy measurement for Open Land Use @PSNC took 0.905463695526123s
Amount of data | Number of triples check for Open Land Use @PSNC took 7.815040826797485s
Interoperability | New terms check for Open Land Use @PSNC took 13.910253524780273s
Versatility | Languages check for Open Land Use @PSNC took 300.23286962509155s
Interpretability | Number of blank nodes check for Open Land Use @PSNC took 2.4994852542877197s
Interpretability | RDF structures check for Open Land Use @PSNC took 0.20463180541992188s
Versatility | Serialization formats check for Open Land Use @PSNC took 11.072152137756348s
Availability | RDF dump link check for Open Land Use @PSNC took 0.2181987762451172s
License | MR license check for Open Land Use @PSNC took 0.3348257541656494s
License | HR license check for Open Land Use @PSNC took 300.23913621902466s
Amount of data | Number of property check for Open Land Use @PSNC took 0.18549203872680664s
Understandability | Number of label check for Open Land Use @PSNC took 1.8284082412719727s
Understandability | URI regex check for Open Land Use @PSNC took 0.5083343982696533s
Understandability | Vocabs check for Open Land Use @PSNC took 0.2554774284362793s
Verifiability | Authors check for Open Land Use @PSNC took 0.17892026901245117s
Verifiability | Publishers check for Open Land Use @PSNC took 0.2376248836517334s
Performance | Throughput check for Open Land Use @PSNC took 10.97757077217102s
Amount of data | Check the number of entities for Open Land Use @PSNC took 0.00010609626770019531s
Verifiability | Contribs. check for Open Land Use @PSNC took 0.19263935089111328s
Interlinking | sameAs chians check for Open Land Use @PSNC took 0.17885661125183105s
Interlinking | skos check for Open Land Use @PSNC took 0.43700671195983887s
Interlinking | skos check for Open Land Use @PSNC took 0.44028258323669434s
Timeliness | dataset update frequency check for Open Land Use @PSNC took 6.09163761138916s
Currency | Creation date check for Open Land Use @PSNC took 0.4592926502227783s
Currency | Modification date check for Open Land Use @PSNC took 0.20488810539245605s
Rep.Conc. | URIs length for Open Land Use @PSNC took 147.5170431137085s
Interoperability | New vocabularies check for Open Land Use @PSNC took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use @PSNC took 0.18405675888061523s
Accuracy | Check Functional Property for Open Land Use @PSNC took 0.2393808364868164s
Accuracy | Check Inverse Functional Property for Open Land Use @PSNC took 0.194472074508667s
Accuracy | Check Empty annotation labels for Open Land Use @PSNC took 44.00696015357971s
Accuracy | Check White space in annotation for Open Land Use @PSNC took 2.6528637409210205s
Accuracy | Check Datatype consistency for Open Land Use @PSNC took 2.70979905128479s
Consistency | Disjoint class check for Open Land Use @PSNC took 0.19295358657836914s
Consistency | Check Misplaced properties for Open Land Use @PSNC took 85.57483863830566s
Consistency | Misplaced classes for Open Land Use @PSNC took 8.573709964752197s
Consistency | Check Ontology hijacking for Open Land Use @PSNC took 36.24711585044861s
Consistency | Check Invalid usage of undefined classes for Open Land Use @PSNC took 1.2907652854919434s
Consistency | Check Invalid usage of undefined properties for Open Land Use @PSNC took 82.96286964416504s
Conciseness | Check Extensional conciseness for Open Land Use @PSNC took 2.7328927516937256s
Conciseness | Check Intensional conciseness for Open Land Use @PSNC took 0.5147264003753662s
Security | Sign check for Open Land Use @PSNC took 0.6599233150482178s
Availability | Check URIs Dereferenciability for Open Land Use @PSNC took 10.46233868598938s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 1.5296719074249268s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.020868301391601562s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 4.172325134277344e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Open Land Use @PSNC took 8.344650268554688e-06s
INFO | --- Analysis for Open_Land_Use took 2235.590477705002s
Availability | SPARQL endpoint availability check for flyatlas took 1.7611441612243652s
Availability | VoID file availability check for flyatlas took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for flyatlas took 0.30028247833251953s
Reputation | Calculation of the PageRank for flyatlas took 0.020399808883666992s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.62396240234375e-05s
Believability | Calculation of trust value for flyatlas took 7.3909759521484375e-06s
INFO | --- Analysis for openbiomed-flyatlas took 11.604586124420166s
Availability | SPARQL endpoint availability check for OpenCalais took 4.315376281738281e-05s
Availability | VoID file availability check for OpenCalais took 0.0005869865417480469s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.2590656280517578s
Reputation | Calculation of the PageRank for OpenCalais took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00011992454528808594s
Believability | Calculation of trust value for OpenCalais took 8.344650268554688e-06s
INFO | --- Analysis for opencalais took 4.817750930786133s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 7.486343383789062e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.3033432960510254s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.020972251892089844s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.462501525878906e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 9.059906005859375e-06s
INFO | --- Analysis for opencorporates took 4.358410596847534s
Availability | SPARQL endpoint availability check for OpenCyc took 4.267692565917969e-05s
Availability | VoID file availability check for OpenCyc took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.7086737155914307s
Reputation | Calculation of the PageRank for OpenCyc took 0.02056884765625s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00010752677917480469s
Believability | Calculation of trust value for OpenCyc took 7.62939453125e-06s
INFO | --- Analysis for opencyc took 2.867227792739868s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 4.673004150390625e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0007078647613525391s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.25517964363098145s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.020207881927490234s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.6716461181640625e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 4.397081136703491s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007655620574951172s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.26700329780578613s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.020257949829101562s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 2.961104393005371s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.29792022705078125s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.02017664909362793s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.5762786865234375e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 6.198883056640625e-06s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.0676581859588623s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 4.100799560546875e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.26520848274230957s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.02028656005859375s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007965564727783203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.414492607116699s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0003516674041748047s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.2744889259338379s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.020404577255249023s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0008149147033691406s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 2.991042375564575s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 0.0005533695220947266s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.28200578689575195s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.022215843200683594s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007970333099365234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-households-projections-population took 2.9190335273742676s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 5.221366882324219e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0004208087921142578s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.2843751907348633s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.02054119110107422s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 6.198883056640625e-06s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 3.037909746170044s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.26065778732299805s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.020228147506713867s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.3537793159484863s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0006783008575439453s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.2902817726135254s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.020231008529663086s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.2421979904174805s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 4.100799560546875e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.00038123130798339844s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.26419949531555176s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.020207643508911133s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 3.62396240234375e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-housing-market took 3.0672526359558105s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 5.4836273193359375e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.2832670211791992s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.673004150390625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 3.134876012802124s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0007123947143554688s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.2809135913848877s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.019968748092651367s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 3.0088934898376465s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.2595691680908203s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.02155470848083496s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 3.015188455581665s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.291851282119751s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.020197629928588867s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.459268093109131s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.28093671798706055s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.020301103591918945s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 2.939227342605591s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.2667522430419922s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.020227432250976562s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 2.947169780731201s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007054805755615234s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.27750277519226074s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.020239830017089844s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 2.9600160121917725s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 4.601478576660156e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0007462501525878906s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.26895999908447266s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.02009129524230957s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 3.072129487991333s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 4.124641418457031e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.2546725273132324s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.020175695419311523s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.429307699203491s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.982948303222656e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007417201995849609s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.29308390617370605s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.020278453826904297s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.8160552978515625e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 2.961674213409424s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 8.797645568847656e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0007357597351074219s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.2916266918182373s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.020181655883789062s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 3.209836959838867s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.00038933753967285156s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.2686748504638672s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.02009415626525879s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-service-expenditure took 3.0293216705322266s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0003523826599121094s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.24517226219177246s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020050525665283203s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 7.271766662597656e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 2.840864658355713s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.00035500526428222656s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.26952433586120605s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.02001047134399414s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 2.9546217918395996s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.2568778991699219s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.02027273178100586s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 2.8864893913269043s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0006947517395019531s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.29628491401672363s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.57763671875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 3.0657219886779785s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0006864070892333984s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.2844855785369873s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.020654916763305664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 5.4836273193359375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 2.9692282676696777s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.25272583961486816s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.020801305770874023s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 2.8956871032714844s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007762908935546875s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.2686638832092285s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.02052164077758789s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 5.14984130859375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 3.2057275772094727s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 5.6743621826171875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007147789001464844s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.2824399471282959s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.020587682723999023s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 2.9769458770751953s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.2711198329925537s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.02015829086303711s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 2.9992213249206543s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.696846008300781e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.00042319297790527344s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.2656691074371338s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.020435810089111328s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 3.0586748123168945s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007731914520263672s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.24140143394470215s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.020502090454101562s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.8160552978515625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 2.9912362098693848s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.2540278434753418s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.744529724121094e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 8.821487426757812e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.372236728668213s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.2541468143463135s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.02048468589782715s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.0728836059570312e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.3160643577575684s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0008099079132080078s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.2845733165740967s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.02003192901611328s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 5.14984130859375e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 3.0437867641448975s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007579326629638672s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.26691770553588867s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.02039957046508789s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 2.9937052726745605s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 5.5789947509765625e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007836818695068359s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.28211116790771484s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.020122289657592773s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 6.580352783203125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 2.9191672801971436s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.601478576660156e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007741451263427734s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.2637357711791992s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0204620361328125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 2.8723037242889404s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007493495941162109s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.2621281147003174s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.020492076873779297s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.982948303222656e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 2.9318909645080566s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.291534423828125e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007417201995849609s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.27845072746276855s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.020085573196411133s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.130918025970459s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0006859302520751953s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.2709178924560547s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.02032637596130371s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.070845365524292s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.26693058013916016s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.020376205444335938s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 3.02685809135437s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 5.864259958267212s
Availability | VoID file availability check for Open Data of Ecuador took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.26871418952941895s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.02038288116455078s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.845329284667969e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 1.2636184692382812e-05s
INFO | --- Analysis for opendataec took 11.013254165649414s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 8.630752563476562e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.27190446853637695s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.020400524139404297s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 6.67572021484375e-06s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.2956702709198s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 4.38690185546875e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0007746219635009766s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.2878406047821045s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.02041482925415039s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 3.0472590923309326s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 4.5299530029296875e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.2721133232116699s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020578861236572266s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 6.67572021484375e-06s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 2.816509246826172s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 4.363059997558594e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.2700827121734619s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.020481586456298828s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 8.58306884765625e-06s
INFO | --- Analysis for opendatascotland-simd-education-rank took 2.829704761505127s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.38690185546875e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.28150486946105957s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.020244359970092773s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 7.867813110351562e-06s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 2.774044990539551s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.26783108711242676s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.020930767059326172s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 3.814697265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 2.763519287109375s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 4.363059997558594e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.27679920196533203s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.020412206649780273s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.814697265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 7.867813110351562e-06s
INFO | --- Analysis for opendatascotland-simd-health-rank took 2.7896454334259033s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 4.291534423828125e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.2859523296356201s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.020199298858642578s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 8.106231689453125e-06s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 2.8297841548919678s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 5.626678466796875e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.2692868709564209s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.02077174186706543s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 1.2636184692382812e-05s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.404991626739502s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.410801887512207s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.2827911376953125s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.020239830017089844s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.0040740966796875e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 6.4373016357421875e-06s
INFO | --- Analysis for openlink-lod-cache took 62.866700887680054s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 4.267692565917969e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.2822401523590088s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.0202791690826416s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 4.6253204345703125e-05s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.655952453613281e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 8.344650268554688e-06s
INFO | --- Analysis for openlinksw-dataspaces took 2.6255128383636475s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 4.315376281738281e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.2669994831085205s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.0204010009765625s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0008437633514404297s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 0.00010347366333007812s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 5.4836273193359375e-06s
INFO | --- Analysis for openlylocal took 6.014414310455322s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 0.8738484382629395s
Availability | VoID file availability check for OpenMobileNetwork took 0.00032711029052734375s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.28875207901000977s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.02039504051208496s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.295608520507812e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 7.3909759521484375e-06s
INFO | --- Analysis for openmobilenetwork took 3.853370428085327s
Availability | SPARQL endpoint availability check for OpenTox took 4.124641418457031e-05s
Availability | VoID file availability check for OpenTox took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for OpenTox took 0.2598392963409424s
Reputation | Calculation of the PageRank for OpenTox took 0.020372629165649414s
Interlinking | Calculation of Degree of Connection for OpenTox took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenTox took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for OpenTox took 2.956390380859375e-05s
Believability | Calculation of trust value for OpenTox took 7.62939453125e-06s
INFO | --- Analysis for opentox took 2.915341377258301s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 4.1484832763671875e-05s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.28145718574523926s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.020227432250976562s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 2.9802322387695312e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 8.821487426757812e-06s
INFO | --- Analysis for openuplabs took 2.950629711151123s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 4.124641418457031e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.26985955238342285s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.020308732986450195s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 2.9802322387695312e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 7.867813110351562e-06s
INFO | --- Analysis for opus took 2.973302125930786s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 5.435943603515625e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.2394716739654541s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.020602703094482422s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 3.600120544433594e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 7.867813110351562e-06s
INFO | --- Analysis for orcid took 2.953627347946167s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 1.0092506408691406s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0007197856903076172s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.27989935874938965s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.020341873168945312s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 0.00010180473327636719s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for ordnance-survey-linked-data took 5.480648040771484s
Availability | SPARQL endpoint availability check for oreilly took 4.363059997558594e-05s
Availability | VoID file availability check for oreilly took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for oreilly took 0.24847865104675293s
Reputation | Calculation of the PageRank for oreilly took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for oreilly took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for oreilly took 5.0067901611328125e-05s
Believability | Calculation of trust value for oreilly took 6.67572021484375e-06s
INFO | --- Analysis for oreilly took 3.9126312732696533s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.4353809356689453s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.28203773498535156s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.0206449031829834s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.314018249511719e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 7.62939453125e-06s
INFO | --- Analysis for Organchem-Data took 7.525987386703491s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.0747532844543457s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.2662639617919922s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.02042365074157715s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 6.723403930664062e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 8.106231689453125e-06s
INFO | --- Analysis for organic-edunet took 9.5101957321167s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.3669090270996094s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0005860328674316406s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 14.167684555053711s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.7472896575927734s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.2006392478942871s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.5170624256134033s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 6.649774074554443s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.19484758377075195s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.4282207489013672s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.16552114486694336s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.16076207160949707s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.13760042190551758s
License | HR license check for Open Research Knowledge Graph (ORKG) took 3.826737880706787s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.14839816093444824s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.1785438060760498s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.31862401962280273s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.15329456329345703s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.17421388626098633s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.15320563316345215s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.786993741989136s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 7.009506225585938e-05s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.15252900123596191s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.15594077110290527s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.16286158561706543s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.1860039234161377s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.15898537635803223s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.40563511848449707s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.35053181648254395s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 7.903832912445068s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.15182065963745117s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.19646215438842773s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.20276784896850586s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 6.1260457038879395s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.1472640037536621s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.2674121856689453s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.24767851829528809s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.540013074874878s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.9470973014831543s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 5.463582754135132s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.282590389251709s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 2.046010971069336s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.2837369441986084s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.14633941650390625s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.15609192848205566s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 2017.9972851276398s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 0.5918042659759521s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.020424842834472656s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 1.1444091796875e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 1.430511474609375e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 6.4373016357421875e-06s
INFO | --- Analysis for orkg took 2302.230203151703s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 3.1275181770324707s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.252147912979126s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.020487308502197266s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 8.678436279296875e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 6.4373016357421875e-06s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 30.213568925857544s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.5298972129821777s
Availability | VoID file availability check for OSM Semantic Network took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.7169694900512695s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.019924640655517578s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.24249267578125e-05s
Believability | Calculation of trust value for OSM Semantic Network took 8.344650268554688e-06s
INFO | --- Analysis for osm-semantic-network took 9.5842764377594s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.4864315986633301s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.0010271072387695312s
Extra | Recovery of all triples for Open Transport Map @PSNC took 127.38467526435852s
Performance | Total latancy measurement for Open Transport Map @PSNC took 0.9817328453063965s
Amount of data | Number of triples check for Open Transport Map @PSNC took 8.334340572357178s
Interoperability | New terms check for Open Transport Map @PSNC took 13.64835238456726s
Versatility | Languages check for Open Transport Map @PSNC took 300.20070338249207s
Interpretability | Number of blank nodes check for Open Transport Map @PSNC took 3.3045687675476074s
Interpretability | RDF structures check for Open Transport Map @PSNC took 0.22930598258972168s
Versatility | Serialization formats check for Open Transport Map @PSNC took 9.836939573287964s
Availability | RDF dump link check for Open Transport Map @PSNC took 0.23102688789367676s
License | MR license check for Open Transport Map @PSNC took 0.5252163410186768s
License | HR license check for Open Transport Map @PSNC took 300.18711519241333s
Amount of data | Number of property check for Open Transport Map @PSNC took 0.31279897689819336s
Understandability | Number of label check for Open Transport Map @PSNC took 2.234349489212036s
Understandability | URI regex check for Open Transport Map @PSNC took 0.6284005641937256s
Understandability | Vocabs check for Open Transport Map @PSNC took 0.27797508239746094s
Verifiability | Authors check for Open Transport Map @PSNC took 0.1997525691986084s
Verifiability | Publishers check for Open Transport Map @PSNC took 0.272017240524292s
Performance | Throughput check for Open Transport Map @PSNC took 11.541312456130981s
Amount of data | Check the number of entities for Open Transport Map @PSNC took 7.653236389160156e-05s
Verifiability | Contribs. check for Open Transport Map @PSNC took 0.24554967880249023s
Interlinking | sameAs chians check for Open Transport Map @PSNC took 0.2693030834197998s
Interlinking | skos check for Open Transport Map @PSNC took 0.46050167083740234s
Interlinking | skos check for Open Transport Map @PSNC took 0.4459812641143799s
Timeliness | dataset update frequency check for Open Transport Map @PSNC took 6.624053955078125s
Currency | Creation date check for Open Transport Map @PSNC took 0.49547696113586426s
Currency | Modification date check for Open Transport Map @PSNC took 0.2331690788269043s
Rep.Conc. | URIs length for Open Transport Map @PSNC took 159.18563508987427s
Interoperability | New vocabularies check for Open Transport Map @PSNC took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Open Transport Map @PSNC took 0.19086670875549316s
Accuracy | Check Functional Property for Open Transport Map @PSNC took 0.38582634925842285s
Accuracy | Check Inverse Functional Property for Open Transport Map @PSNC took 0.4310300350189209s
Accuracy | Check Empty annotation labels for Open Transport Map @PSNC took 44.8627724647522s
Accuracy | Check White space in annotation for Open Transport Map @PSNC took 2.6526856422424316s
Accuracy | Check Datatype consistency for Open Transport Map @PSNC took 2.611910581588745s
Consistency | Disjoint class check for Open Transport Map @PSNC took 0.19126558303833008s
Consistency | Check Misplaced properties for Open Transport Map @PSNC took 79.68628025054932s
Consistency | Misplaced classes for Open Transport Map @PSNC took 8.463938236236572s
Consistency | Check Ontology hijacking for Open Transport Map @PSNC took 34.1425347328186s
Consistency | Check Invalid usage of undefined classes for Open Transport Map @PSNC took 1.2843108177185059s
Consistency | Check Invalid usage of undefined properties for Open Transport Map @PSNC took 81.54202961921692s
Conciseness | Check Extensional conciseness for Open Transport Map @PSNC took 2.7180044651031494s
Conciseness | Check Intensional conciseness for Open Transport Map @PSNC took 0.5463035106658936s
Security | Sign check for Open Transport Map @PSNC took 1.0519351959228516s
Availability | Check URIs Dereferenciability for Open Transport Map @PSNC took 17.51805830001831s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 1.0294740200042725s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.020486116409301758s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 5.5789947509765625e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 3.886222839355469e-05s
Interoperability | Check the re-using of existing vocabs for Open Transport Map @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Open Transport Map @PSNC took 6.9141387939453125e-06s
INFO | --- Analysis for OTM took 2290.7029950618744s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 4.2438507080078125e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.2617499828338623s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.020684242248535156s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0008192062377929688s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 3.170967102050781e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 7.62939453125e-06s
INFO | --- Analysis for ounl-dspace-in-rdf took 3.867304563522339s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.0531158447265625e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.7160389423370361s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020168066024780273s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.765655517578125e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 7.867813110351562e-06s
INFO | --- Analysis for ox-ac-uk-catalogue took 3.4613678455352783s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 5.626678466796875e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.24274539947509766s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.02014636993408203s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.7418136596679688e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 7.62939453125e-06s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 3.392158269882202s
Availability | SPARQL endpoint availability check for OpenMeters (University of Oxford) took 4.0531158447265625e-05s
Availability | VoID file availability check for OpenMeters (University of Oxford) took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.6973738670349121s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.020418405532836914s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 2.8371810913085938e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 7.152557373046875e-06s
INFO | --- Analysis for ox-ac-uk-openmeters took 3.4443764686584473s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 5.4836273193359375e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.276439905166626s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.020177364349365234s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 2.8133392333984375e-05s
Believability | Calculation of trust value for Time-series metadata (University of Oxford) took 7.62939453125e-06s
INFO | --- Analysis for ox-ac-uk-timeseries took 2.9084677696228027s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 4.124641418457031e-05s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.6904141902923584s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.02037358283996582s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.0006844997406005859s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 2.8133392333984375e-05s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 7.3909759521484375e-06s
INFO | --- Analysis for ox-ac-uk-vacancies took 3.3331339359283447s
Availability | SPARQL endpoint availability check for Events calendar for the University (University of Oxford) took 4.029273986816406e-05s
Availability | VoID file availability check for Events calendar for the University (University of Oxford) took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.2649543285369873s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.020151615142822266s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Events calendar for the University (University of Oxford) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Events calendar for the University (University of Oxford) took 6.4373016357421875e-06s
INFO | --- Analysis for ox-ac-uk-www-ox-ac-uk-events took 3.4766387939453125s
Availability | SPARQL endpoint availability check for OxPoints (University of Oxford) took 3.981590270996094e-05s
Availability | VoID file availability check for OxPoints (University of Oxford) took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.2920496463775635s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.02036905288696289s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 3.838539123535156e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 7.152557373046875e-06s
INFO | --- Analysis for oxpoints took 3.3916423320770264s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.777292013168335s
Availability | VoID file availability check for Pali English Lexicon took 0.0007045269012451172s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.26235461235046387s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.02015852928161621s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 2.7418136596679688e-05s
Believability | Calculation of trust value for Pali English Lexicon took 6.198883056640625e-06s
INFO | --- Analysis for pali-english-lexicon took 7.4624574184417725s
Availability | SPARQL endpoint availability check for PanLex took 0.5069332122802734s
Availability | VoID file availability check for PanLex took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for PanLex took 0.2517578601837158s
Reputation | Calculation of the PageRank for PanLex took 0.02018117904663086s
Interlinking | Calculation of Degree of Connection for PanLex took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for PanLex took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.796287536621094e-05s
Believability | Calculation of trust value for PanLex took 7.3909759521484375e-06s
INFO | --- Analysis for panlex took 2.9190831184387207s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 4.315376281738281e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.25121021270751953s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.020145416259765625s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 3.647804260253906e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 6.9141387939453125e-06s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 5.675914764404297s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.1300830841064453s
Availability | VoID file availability check for patents.data.gov.uk took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.26970791816711426s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.020218610763549805s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 4.5299530029296875e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 5.245208740234375e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.6060593128204346s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 4.220008850097656e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.29210424423217773s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.020061731338500977s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 3.552436828613281e-05s
Believability | Calculation of trust value for PDEV-Lemon took 7.867813110351562e-06s
INFO | --- Analysis for pdev-lemon took 4.0016937255859375s
Availability | SPARQL endpoint availability check for pdevlemon took 4.220008850097656e-05s
Availability | VoID file availability check for pdevlemon took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.251422643661499s
Reputation | Calculation of the PageRank for pdevlemon took 0.020394325256347656s
Interlinking | Calculation of Degree of Connection for pdevlemon took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 2.9325485229492188e-05s
Believability | Calculation of trust value for pdevlemon took 1.2636184692382812e-05s
INFO | --- Analysis for pdevlemon took 3.1861143112182617s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 5.626678466796875e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0008380413055419922s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.2496945858001709s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.020346879959106445s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 8.153915405273438e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 7.867813110351562e-06s
INFO | --- Analysis for periodo took 19.029491186141968s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.291534423828125e-05s
Availability | VoID file availability check for Personal_Homepages took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.25486254692077637s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020020723342895508s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.0003845691680908203s
Believability | Calculation of trust value for Personal_Homepages took 7.3909759521484375e-06s
INFO | --- Analysis for personal-homepages took 2.39453125s
Availability | SPARQL endpoint availability check for Ontology of University People took 4.315376281738281e-05s
Availability | VoID file availability check for Ontology of University People took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.2598233222961426s
Reputation | Calculation of the PageRank for Ontology of University People took 0.02008843421936035s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 2.8371810913085938e-05s
Believability | Calculation of trust value for Ontology of University People took 6.67572021484375e-06s
INFO | --- Analysis for PersonOnto took 2.331052780151367s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 6.187072038650513s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.27252984046936035s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.02043890953063965s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.4781951904296875e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 9.059906005859375e-06s
INFO | --- Analysis for PFKHS took 18.55623769760132s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 4.132396697998047s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.2761261463165283s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020141124725341797s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.0728836059570312e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 7.3909759521484375e-06s
INFO | --- Analysis for PFRPPH took 12.563921928405762s
Availability | SPARQL endpoint availability check for PGxLOD took 0.4320504665374756s
Availability | VoID file availability check for PGxLOD took 0.0006215572357177734s
Extra | Recovery of all triples for PGxLOD took 2.278268575668335s
Performance | Total latancy measurement for PGxLOD took 0.8824648857116699s
Amount of data | Number of triples check for PGxLOD took 5.535407781600952s
Interoperability | New terms check for PGxLOD took 1.9235577583312988s
Versatility | Languages check for PGxLOD took 60.851186752319336s
Interpretability | Number of blank nodes check for PGxLOD took 1.6264805793762207s
Interpretability | RDF structures check for PGxLOD took 0.553983211517334s
Versatility | Serialization formats check for PGxLOD took 0.5568633079528809s
Availability | RDF dump link check for PGxLOD took 55.55008316040039s
License | MR license check for PGxLOD took 0.8176910877227783s
License | HR license check for PGxLOD took 64.67936897277832s
Amount of data | Number of property check for PGxLOD took 0.1924147605895996s
Understandability | Number of label check for PGxLOD took 3.612525224685669s
Understandability | URI regex check for PGxLOD took 0.47225499153137207s
Understandability | Vocabs check for PGxLOD took 0.3374440670013428s
Verifiability | Authors check for PGxLOD took 0.3362917900085449s
Verifiability | Publishers check for PGxLOD took 0.3213164806365967s
Performance | Throughput check for PGxLOD took 10.863240957260132s
Amount of data | Check the number of entities for PGxLOD took 0.11943292617797852s
Verifiability | Contribs. check for PGxLOD took 0.1923990249633789s
Interlinking | sameAs chians check for PGxLOD took 0.2865450382232666s
Interlinking | skos check for PGxLOD took 1.409191608428955s
Interlinking | skos check for PGxLOD took 0.23952150344848633s
Timeliness | dataset update frequency check for PGxLOD took 0.3766195774078369s
Currency | Creation date check for PGxLOD took 0.574713945388794s
Currency | Modification date check for PGxLOD took 0.34998083114624023s
Rep.Conc. | URIs length for PGxLOD took 6.766175270080566s
Interoperability | New vocabularies check for PGxLOD took 10.311501026153564s
Consistency | Deprecated classes/propertiers check for PGxLOD took 0.1540980339050293s
Accuracy | Check Functional Property for PGxLOD took 0.20346355438232422s
Accuracy | Check Inverse Functional Property for PGxLOD took 0.21871352195739746s
Accuracy | Check Empty annotation labels for PGxLOD took 0.9194729328155518s
Accuracy | Check White space in annotation for PGxLOD took 0.03729104995727539s
Accuracy | Check Datatype consistency for PGxLOD took 0.027926206588745117s
Consistency | Disjoint class check for PGxLOD took 0.3226182460784912s
Consistency | Check Misplaced properties for PGxLOD took 6.642505168914795s
Consistency | Misplaced classes for PGxLOD took 0.320462703704834s
Consistency | Check Ontology hijacking for PGxLOD took 2.113272190093994s
Consistency | Check Invalid usage of undefined classes for PGxLOD took 1.1584174633026123s
Consistency | Check Invalid usage of undefined properties for PGxLOD took 7.110762119293213s
Conciseness | Check Extensional conciseness for PGxLOD took 0.03409695625305176s
Conciseness | Check Intensional conciseness for PGxLOD took 0.32149481773376465s
Security | Sign check for PGxLOD took 0.188063383102417s
Availability | Check URIs Dereferenciability for PGxLOD took 1719.8984870910645s
Completeness | Calculation of interlinking completeness for PGxLOD took 1.0001235008239746s
Reputation | Calculation of the PageRank for PGxLOD took 0.02078533172607422s
Interlinking | Calculation of Degree of Connection for PGxLOD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 5.793571472167969e-05s
Interoperability | Check the re-using of existing vocabs for PGxLOD took 32.224870920181274s
Believability | Calculation of trust value for PGxLOD took 7.152557373046875e-06s
INFO | --- Analysis for PGxLOD took 3107.8050434589386s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 1.1627473831176758s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0006241798400878906s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.7087206840515137s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.020303964614868164s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.314018249511719e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 7.152557373046875e-06s
INFO | --- Analysis for phoible took 6.6973350048065186s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 4.267692565917969e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.6985583305358887s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.020159006118774414s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 2.7894973754882812e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 6.4373016357421875e-06s
INFO | --- Analysis for PISM took 11.8361976146698s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.220008850097656e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.28060388565063477s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.020363330841064453s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.273124694824219e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 6.4373016357421875e-06s
INFO | --- Analysis for planetdata-project-wiki took 2.91121506690979s
Availability | SPARQL endpoint availability check for digitized plant specimen took 1.2230217456817627s
Availability | VoID file availability check for digitized plant specimen took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.2999446392059326s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.02023768424987793s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 6.914138793945312e-05s
Believability | Calculation of trust value for digitized plant specimen took 7.3909759521484375e-06s
INFO | --- Analysis for plant-specimen took 4.16736626625061s
Availability | SPARQL endpoint availability check for Pleiades took 4.220008850097656e-05s
Availability | VoID file availability check for Pleiades took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for Pleiades took 0.28882503509521484s
Reputation | Calculation of the PageRank for Pleiades took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.249282836914062e-05s
Believability | Calculation of trust value for Pleiades took 6.67572021484375e-06s
INFO | --- Analysis for pleiades took 13.994078636169434s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 4.482269287109375e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0007238388061523438s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.267240047454834s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.020373821258544922s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 3.0040740966796875e-05s
Believability | Calculation of trust value for podorozhnyk.com took 7.3909759521484375e-06s
INFO | --- Analysis for podorozhnyk took 4.232754707336426s
Availability | SPARQL endpoint availability check for Poképédia took 4.38690185546875e-05s
Availability | VoID file availability check for Poképédia took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Poképédia took 0.2773001194000244s
Reputation | Calculation of the PageRank for Poképédia took 0.020135164260864258s
Interlinking | Calculation of Degree of Connection for Poképédia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Poképédia took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Poképédia took 7.128715515136719e-05s
Believability | Calculation of trust value for Poképédia took 6.9141387939453125e-06s
INFO | --- Analysis for pokepedia-fr took 2.7267656326293945s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 4.5299530029296875e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.28318285942077637s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.020662307739257812s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 8.916854858398438e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.3909759521484375e-06s
INFO | --- Analysis for polymath-virtual-library took 5.876232862472534s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.9966228008270264s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007011890411376953s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.25316953659057617s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.020176410675048828s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.1920928955078125e-05s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 6.9141387939453125e-06s
INFO | --- Analysis for portuguese_prisons_releases took 7.642986297607422s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 4.124641418457031e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.2640390396118164s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.020365476608276367s
Interlinking | Calculation of Degree of Connection for Barley trading volume and wholesale prices took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Barley trading volume and wholesale prices took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 2.9325485229492188e-05s
Believability | Calculation of trust value for Barley trading volume and wholesale prices took 6.67572021484375e-06s
INFO | --- Analysis for predicting-barley-volume-and-wholesale-prices took 2.948214292526245s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 4.363059997558594e-05s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.7039058208465576s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.020446062088012695s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Corn trading volume and wholesale prices took 2.9802322387695312e-05s
Believability | Calculation of trust value for Corn trading volume and wholesale prices took 9.059906005859375e-06s
INFO | --- Analysis for predicting-corn-trading-volume-and-wholesale-prices took 3.2605035305023193s
Availability | SPARQL endpoint availability check for Onion trading volume and wholesale prices took 7.081031799316406e-05s
Availability | VoID file availability check for Onion trading volume and wholesale prices took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.26785826683044434s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.02024531364440918s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 2.9325485229492188e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 6.67572021484375e-06s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 2.9123613834381104s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 4.1484832763671875e-05s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.25283217430114746s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.020180225372314453s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Potato trading volume and wholesale price took 2.86102294921875e-05s
Believability | Calculation of trust value for Potato trading volume and wholesale price took 6.4373016357421875e-06s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 2.9529614448547363s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 4.124641418457031e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.26587438583374023s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.020241498947143555s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of apples took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of apples took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 2.8848648071289062e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of apples took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-apples took 2.9071204662323s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 4.0531158447265625e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.26938962936401367s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.02055954933166504s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of barley took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of barley took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of barley took 2.9087066650390625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of barley took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 2.960705518722534s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of bean took 6.532669067382812e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of bean took 0.00030922889709472656s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.2570929527282715s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.020346879959106445s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of bean took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of bean took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of bean took 3.6716461181640625e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of bean took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 2.93066143989563s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 4.2438507080078125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.00028967857360839844s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.27582383155822754s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.02027583122253418s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 2.8133392333984375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 3.0155065059661865s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of corn took 4.029273986816406e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of corn took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.26611328125s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.020233869552612305s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 2.86102294921875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of corn took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-corn took 3.0557503700256348s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of crab took 4.1961669921875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of crab took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.2693357467651367s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.020479440689086914s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of crab took 3.0040740966796875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of crab took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 2.803778648376465s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cucumber took 4.2438507080078125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cucumber took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.25760936737060547s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.020580768585205078s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.0007987022399902344s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 3.0279159545898438e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 2.9847543239593506s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 4.38690185546875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.27817535400390625s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.020329713821411133s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of lettuce took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of lettuce took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 2.956390380859375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 7.867813110351562e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 2.9420366287231445s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 4.2438507080078125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.0002892017364501953s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 0.2881748676300049s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.020369768142700195s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 3.0279159545898438e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of onion took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-onion took 3.0232174396514893s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of oyster mushroom took 4.172325134277344e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of oyster mushroom took 0.00048828125s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.2623436450958252s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.020265579223632812s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.001046895980834961s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 3.743171691894531e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of oyster mushroom took 1.2874603271484375e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-oyster-mushroom took 2.9359326362609863s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 4.124641418457031e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.2995750904083252s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.020326852798461914s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of potato took 3.0040740966796875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of potato took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-potato took 3.025203227996826s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of radish took 7.534027099609375e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of radish took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.2513563632965088s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.0208590030670166s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of radish took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of radish took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 2.9802322387695312e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 2.98586368560791s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 4.982948303222656e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.27935028076171875s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.020470857620239258s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of rice plant took 3.075599670410156e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of rice plant took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 2.9654526710510254s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 4.315376281738281e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.26404428482055664s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.02066802978515625s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 3.218650817871094e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of watermelon took 7.867813110351562e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-watermelon took 2.9349520206451416s
Availability | SPARQL endpoint availability check for prefix.cc took 6.246566772460938e-05s
Availability | VoID file availability check for prefix.cc took 0.0006532669067382812s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.26807522773742676s
Reputation | Calculation of the PageRank for prefix.cc took 0.020454883575439453s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 3.743171691894531e-05s
Believability | Calculation of trust value for prefix.cc took 7.152557373046875e-06s
INFO | --- Analysis for prefix-cc took 3.3017935752868652s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 2.2095906734466553s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.2915792465209961s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.02016448974609375s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.9591064453125e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 7.62939453125e-06s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 9.833868265151978s
Availability | SPARQL endpoint availability check for PreLex took 4.425902843475342s
Availability | VoID file availability check for PreLex took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for PreLex took 0.29361629486083984s
Reputation | Calculation of the PageRank for PreLex took 0.020840167999267578s
Interlinking | Calculation of Degree of Connection for PreLex took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0011210441589355469s
Interlinking | Calculation of Clustering coefficient for PreLex took 9.298324584960938e-05s
Believability | Calculation of trust value for PreLex took 6.9141387939453125e-06s
INFO | --- Analysis for prelex took 13.468148708343506s
Availability | SPARQL endpoint availability check for Prelinger Archives took 2.2567591667175293s
Availability | VoID file availability check for Prelinger Archives took 0.0007746219635009766s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.2624824047088623s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.020033597946166992s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 2.7894973754882812e-05s
Believability | Calculation of trust value for Prelinger Archives took 6.9141387939453125e-06s
INFO | --- Analysis for prelinger_archives took 11.372358798980713s
Availability | SPARQL endpoint availability check for PreMOn (Predicate Model for Ontologies) took 0.4007246494293213s
Availability | VoID file availability check for PreMOn (Predicate Model for Ontologies) took 0.0006492137908935547s
Extra | Recovery of all triples for PreMOn (Predicate Model for Ontologies) took 5.442815780639648s
Performance | Total latancy measurement for PreMOn (Predicate Model for Ontologies) took 1.2389838695526123s
Amount of data | Number of triples check for PreMOn (Predicate Model for Ontologies) took 0.10616874694824219s
Interoperability | New terms check for PreMOn (Predicate Model for Ontologies) took 2.0326132774353027s
Versatility | Languages check for PreMOn (Predicate Model for Ontologies) took 58.770718574523926s
Interpretability | Number of blank nodes check for PreMOn (Predicate Model for Ontologies) took 0.16978788375854492s
Security | Check HTTPS for PreMOn (Predicate Model for Ontologies) took 0.09677004814147949s
Interpretability | RDF structures check for PreMOn (Predicate Model for Ontologies) took 0.2592315673828125s
Versatility | Serialization formats check for PreMOn (Predicate Model for Ontologies) took 0.2929704189300537s
Availability | RDF dump link check for PreMOn (Predicate Model for Ontologies) took 0.3158597946166992s
License | MR license check for PreMOn (Predicate Model for Ontologies) took 0.443662166595459s
License | HR license check for PreMOn (Predicate Model for Ontologies) took 1.0195891857147217s
Amount of data | Number of property check for PreMOn (Predicate Model for Ontologies) took 0.25182032585144043s
Understandability | Number of label check for PreMOn (Predicate Model for Ontologies) took 0.13715624809265137s
Understandability | URI regex check for PreMOn (Predicate Model for Ontologies) took 0.48547816276550293s
Understandability | Vocabs check for PreMOn (Predicate Model for Ontologies) took 0.31284475326538086s
Verifiability | Authors check for PreMOn (Predicate Model for Ontologies) took 0.24307465553283691s
Verifiability | Publishers check for PreMOn (Predicate Model for Ontologies) took 0.35150957107543945s
Performance | Throughput check for PreMOn (Predicate Model for Ontologies) took 11.75079345703125s
Amount of data | Check the number of entities for PreMOn (Predicate Model for Ontologies) took 0.00010156631469726562s
Verifiability | Contribs. check for PreMOn (Predicate Model for Ontologies) took 0.23478245735168457s
Interlinking | sameAs chians check for PreMOn (Predicate Model for Ontologies) took 0.09308505058288574s
Interlinking | skos check for PreMOn (Predicate Model for Ontologies) took 0.11658287048339844s
Interlinking | skos check for PreMOn (Predicate Model for Ontologies) took 0.15920662879943848s
Timeliness | dataset update frequency check for PreMOn (Predicate Model for Ontologies) took 0.2662327289581299s
Currency | Creation date check for PreMOn (Predicate Model for Ontologies) took 0.5536572933197021s
Currency | Modification date check for PreMOn (Predicate Model for Ontologies) took 0.7448811531066895s
Rep.Conc. | URIs length for PreMOn (Predicate Model for Ontologies) took 4.648461103439331s
Interoperability | New vocabularies check for PreMOn (Predicate Model for Ontologies) took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for PreMOn (Predicate Model for Ontologies) took 0.29111814498901367s
Accuracy | Check Empty annotation labels for PreMOn (Predicate Model for Ontologies) took 2.0474588871002197s
Accuracy | Check White space in annotation for PreMOn (Predicate Model for Ontologies) took 0.08215665817260742s
Accuracy | Check Datatype consistency for PreMOn (Predicate Model for Ontologies) took 0.08176851272583008s
Consistency | Disjoint class check for PreMOn (Predicate Model for Ontologies) took 0.29341912269592285s
Consistency | Check Misplaced properties for PreMOn (Predicate Model for Ontologies) took 2.193796157836914s
Consistency | Misplaced classes for PreMOn (Predicate Model for Ontologies) took 0.5385940074920654s
Consistency | Check Ontology hijacking for PreMOn (Predicate Model for Ontologies) took 2.6977603435516357s
Consistency | Check Invalid usage of undefined classes for PreMOn (Predicate Model for Ontologies) took 1.1576941013336182s
Consistency | Check Invalid usage of undefined properties for PreMOn (Predicate Model for Ontologies) took 3.080127716064453s
Conciseness | Check Extensional conciseness for PreMOn (Predicate Model for Ontologies) took 0.08734941482543945s
Conciseness | Check Intensional conciseness for PreMOn (Predicate Model for Ontologies) took 0.31885838508605957s
Security | Sign check for PreMOn (Predicate Model for Ontologies) took 0.23157167434692383s
Availability | Check URIs Dereferenciability for PreMOn (Predicate Model for Ontologies) took 1260.1954746246338s
Completeness | Calculation of interlinking completeness for PreMOn (Predicate Model for Ontologies) took 1.3653512001037598s
Reputation | Calculation of the PageRank for PreMOn (Predicate Model for Ontologies) took 0.020532846450805664s
Interlinking | Calculation of Degree of Connection for PreMOn (Predicate Model for Ontologies) took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for PreMOn (Predicate Model for Ontologies) took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for PreMOn (Predicate Model for Ontologies) took 6.651878356933594e-05s
Interoperability | Check the re-using of existing vocabs for PreMOn (Predicate Model for Ontologies) took 1.6689300537109375e-06s
Believability | Calculation of trust value for PreMOn (Predicate Model for Ontologies) took 7.62939453125e-06s
INFO | --- Analysis for premon took 1391.9401717185974s
Availability | SPARQL endpoint availability check for Previsible took 4.220008850097656e-05s
Availability | VoID file availability check for Previsible took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Previsible took 0.7000839710235596s
Reputation | Calculation of the PageRank for Previsible took 0.0204007625579834s
Interlinking | Calculation of Degree of Connection for Previsible took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Previsible took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Previsible took 1.6450881958007812e-05s
Believability | Calculation of trust value for Previsible took 6.4373016357421875e-06s
INFO | --- Analysis for Previsible took 3.2633121013641357s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 5.507469177246094e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.2622818946838379s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.020226001739501953s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.459785461425781e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 1.1920928955078125e-05s
INFO | --- Analysis for princeton-library-findingaids took 4.128491163253784s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.5887680053710938s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.24433445930480957s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.020002365112304688s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 3.4809112548828125e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for PrinParLat took 4.913965940475464s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.26310062408447266s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.27940869331359863s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.020274639129638672s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.0108642578125e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 6.9141387939453125e-06s
INFO | --- Analysis for printed-book-auction-catalogues took 3.507906436920166s
Availability | SPARQL endpoint availability check for Prior Panel took 8.940696716308594e-05s
Availability | VoID file availability check for Prior Panel took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.2675309181213379s
Reputation | Calculation of the PageRank for Prior Panel took 0.020441055297851562s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 4.2438507080078125e-05s
Believability | Calculation of trust value for Prior Panel took 8.106231689453125e-06s
INFO | --- Analysis for Prior_Panel took 2.976867437362671s
Availability | SPARQL endpoint availability check for Procedimientos, trámites y servicios took 4.291534423828125e-05s
Availability | VoID file availability check for Procedimientos, trámites y servicios took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.2645695209503174s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.020223140716552734s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 3.218650817871094e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 8.344650268554688e-06s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 3.0000455379486084s
Availability | SPARQL endpoint availability check for Procomún SPARQL took 4.1961669921875e-05s
Availability | VoID file availability check for Procomún SPARQL took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Procomún SPARQL took 0.27245306968688965s
Reputation | Calculation of the PageRank for Procomún SPARQL took 0.020061731338500977s
Interlinking | Calculation of Degree of Connection for Procomún SPARQL took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Procomún SPARQL took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Procomún SPARQL took 2.8848648071289062e-05s
Believability | Calculation of trust value for Procomún SPARQL took 1.239776611328125e-05s
INFO | --- Analysis for procomun-sparql took 2.994894027709961s
Availability | SPARQL endpoint availability check for PROD - JISC Project Directory in RDF took 4.1484832763671875e-05s
Availability | VoID file availability check for PROD - JISC Project Directory in RDF took 0.00029730796813964844s
Completeness | Calculation of interlinking completeness for PROD - JISC Project Directory in RDF took 0.26915454864501953s
Reputation | Calculation of the PageRank for PROD - JISC Project Directory in RDF took 0.02017045021057129s
Interlinking | Calculation of Degree of Connection for PROD - JISC Project Directory in RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PROD - JISC Project Directory in RDF took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for PROD - JISC Project Directory in RDF took 3.0517578125e-05s
Believability | Calculation of trust value for PROD - JISC Project Directory in RDF took 8.106231689453125e-06s
INFO | --- Analysis for prod-jisc-project-directory-in-rdf took 2.9143147468566895s
Availability | SPARQL endpoint availability check for ProductDB took 3.635502815246582s
Availability | VoID file availability check for ProductDB took 0.0006132125854492188s
Completeness | Calculation of interlinking completeness for ProductDB took 0.25690770149230957s
Reputation | Calculation of the PageRank for ProductDB took 0.020243167877197266s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.343292236328125e-05s
Believability | Calculation of trust value for ProductDB took 7.152557373046875e-06s
INFO | --- Analysis for productdb took 8.089863538742065s
Availability | SPARQL endpoint availability check for Product Types Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.2578907012939453s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.020406246185302734s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 7.748603820800781e-05s
Believability | Calculation of trust value for Product Types Ontology took 1.8835067749023438e-05s
INFO | --- Analysis for productontology took 3.3814027309417725s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 4.1961669921875e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.25640416145324707s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.02023458480834961s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.00010013580322265625s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 1.1682510375976562e-05s
INFO | --- Analysis for prospects-and-trends-gnoss took 8.550480604171753s
Availability | SPARQL endpoint availability check for provenanceweb took 0.04690098762512207s
Availability | VoID file availability check for provenanceweb took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.29598259925842285s
Reputation | Calculation of the PageRank for provenanceweb took 0.021126508712768555s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 7.748603820800781e-05s
Believability | Calculation of trust value for provenanceweb took 8.821487426757812e-06s
INFO | --- Analysis for provenanceweb took 47.499077796936035s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 4.291534423828125e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.2715115547180176s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.020089149475097656s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 9.799003601074219e-05s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 7.62939453125e-06s
INFO | --- Analysis for proyectoapadrina took 8.286822319030762s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 25.43710160255432s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0008218288421630859s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.25539708137512207s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.02058267593383789s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 3.3855438232421875e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 4.76837158203125e-06s
INFO | --- Analysis for pscs-catalogue took 124.61230158805847s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 5.1021575927734375e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.7554802894592285s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.486343383789062e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 7.62939453125e-06s
INFO | --- Analysis for psh-subject-headings took 5.427362442016602s
Availability | SPARQL endpoint availability check for Depression took 0.3015933036804199s
Availability | VoID file availability check for Depression took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Depression took 0.25247812271118164s
Reputation | Calculation of the PageRank for Depression took 0.020139455795288086s
Interlinking | Calculation of Degree of Connection for Depression took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Depression took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Depression took 3.24249267578125e-05s
Believability | Calculation of trust value for Depression took 6.9141387939453125e-06s
INFO | --- Analysis for Psychology took 2.789637804031372s
Availability | SPARQL endpoint availability check for PubChem RDF took 4.220008850097656e-05s
Availability | VoID file availability check for PubChem RDF took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.276073694229126s
Reputation | Calculation of the PageRank for PubChem RDF took 0.020682573318481445s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0009624958038330078s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 4.57763671875e-05s
Believability | Calculation of trust value for PubChem RDF took 6.9141387939453125e-06s
INFO | --- Analysis for PubChem_RDF took 5.268982172012329s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 4.124641418457031e-05s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.2672443389892578s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.020007610321044922s
Interlinking | Calculation of Degree of Connection for Public Record Office Victoria Semantic Wiki took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Public Record Office Victoria Semantic Wiki took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 2.765655517578125e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 7.62939453125e-06s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 2.9473345279693604s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 0.5338060855865479s
Availability | VoID file availability check for Public Spending in Greece took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.254375696182251s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.02105116844177246s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 8.130073547363281e-05s
Believability | Calculation of trust value for Public Spending in Greece took 7.152557373046875e-06s
INFO | --- Analysis for public-spending-in-greece took 8.489272356033325s
Availability | SPARQL endpoint availability check for Publications of Charles University in Prague took 5.054473876953125e-05s
Availability | VoID file availability check for Publications of Charles University in Prague took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.2606937885284424s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.02021479606628418s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 2.8848648071289062e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 7.152557373046875e-06s
INFO | --- Analysis for publications-of-charles-university-in-prague took 2.9401888847351074s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.2702360153198242s
Availability | VoID file availability check for Publications Office Authority tables took 0.0009083747863769531s
Extra | Recovery of all triples for Publications Office Authority tables took 122.837899684906s
Performance | Total latancy measurement for Publications Office Authority tables took 0.6034893989562988s
Amount of data | Number of triples check for Publications Office Authority tables took 0.6550407409667969s
Interoperability | New terms check for Publications Office Authority tables took 12.113132953643799s
Versatility | Languages check for Publications Office Authority tables took 300.0365493297577s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 2.231337547302246s
Security | Check HTTPS for Publications Office Authority tables took 0.34421658515930176s
Interpretability | RDF structures check for Publications Office Authority tables took 0.36821818351745605s
Versatility | Serialization formats check for Publications Office Authority tables took 4.218778133392334s
Availability | RDF dump link check for Publications Office Authority tables took 0.2025158405303955s
License | MR license check for Publications Office Authority tables took 0.2391963005065918s
License | HR license check for Publications Office Authority tables took 300.09731554985046s
Amount of data | Number of property check for Publications Office Authority tables took 0.18683218955993652s
Understandability | Number of label check for Publications Office Authority tables took 0.8581967353820801s
Understandability | URI regex check for Publications Office Authority tables took 0.21818256378173828s
Understandability | Vocabs check for Publications Office Authority tables took 0.11776494979858398s
Verifiability | Authors check for Publications Office Authority tables took 0.18920683860778809s
Verifiability | Publishers check for Publications Office Authority tables took 0.2881190776824951s
Performance | Throughput check for Publications Office Authority tables took 10.437520980834961s
Amount of data | Check the number of entities for Publications Office Authority tables took 7.939338684082031e-05s
Verifiability | Contribs. check for Publications Office Authority tables took 0.18033623695373535s
Interlinking | sameAs chians check for Publications Office Authority tables took 1.0570621490478516s
Interlinking | skos check for Publications Office Authority tables took 0.24680781364440918s
Interlinking | skos check for Publications Office Authority tables took 0.1588757038116455s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.24686145782470703s
Currency | Creation date check for Publications Office Authority tables took 0.3030111789703369s
Currency | Modification date check for Publications Office Authority tables took 0.17230010032653809s
Rep.Conc. | URIs length for Publications Office Authority tables took 106.31686520576477s
Interoperability | New vocabularies check for Publications Office Authority tables took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.12610626220703125s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.18254780769348145s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.15141916275024414s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 31.565263032913208s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.0948054790496826s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.6417253017425537s
Consistency | Disjoint class check for Publications Office Authority tables took 0.19538187980651855s
Consistency | Check Misplaced properties for Publications Office Authority tables took 55.73701310157776s
Consistency | Misplaced classes for Publications Office Authority tables took 8.366002798080444s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 30.414599657058716s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 1.3422911167144775s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 55.974440813064575s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 2.99173903465271s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.42082929611206055s
Security | Sign check for Publications Office Authority tables took 0.10163116455078125s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 8.445241212844849s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 1.1653187274932861s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.020813703536987305s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 4.5299530029296875e-05s
Interoperability | Check the re-using of existing vocabs for Publications Office Authority tables took 1.6689300537109375e-06s
Believability | Calculation of trust value for Publications Office Authority tables took 4.76837158203125e-06s
INFO | --- Analysis for publications_office_authority_tables took 14351.409079313278s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 4.1961669921875e-05s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.7235424518585205s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.020619869232177734s
Interlinking | Calculation of Degree of Connection for Publikace Univerzity Karlovy v Praze took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Publikace Univerzity Karlovy v Praze took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 3.123283386230469e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 7.867813110351562e-06s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 4.714466094970703s
Availability | SPARQL endpoint availability check for QBOAirbase took 5.14984130859375e-05s
Availability | VoID file availability check for QBOAirbase took 0.0007441043853759766s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.7506849765777588s
Reputation | Calculation of the PageRank for QBOAirbase took 0.020217180252075195s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 7.295608520507812e-05s
Believability | Calculation of trust value for QBOAirbase took 7.62939453125e-06s
INFO | --- Analysis for qboairbase took 137.7581627368927s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 4.0531158447265625e-05s
Availability | VoID file availability check for qualitywebdata.org took 0.0002868175506591797s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 0.2483053207397461s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.020407438278198242s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 2.86102294921875e-05s
Believability | Calculation of trust value for qualitywebdata.org took 7.867813110351562e-06s
INFO | --- Analysis for qualitywebdata-org took 4.249694108963013s
Availability | SPARQL endpoint availability check for Qualité de l'air took 4.363059997558594e-05s
Availability | VoID file availability check for Qualité de l'air took 0.0005967617034912109s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.28102540969848633s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.02033400535583496s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0008683204650878906s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 2.9802322387695312e-05s
Believability | Calculation of trust value for Qualité de l'air took 7.3909759521484375e-06s
INFO | --- Analysis for Qualité_de_l'air took 2.8201656341552734s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 4.506111145019531e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0005815029144287109s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.3612380027770996s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.02033257484436035s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 3.5762786865234375e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 8.106231689453125e-06s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 55.829535484313965s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.5486836433410645s
Availability | VoID file availability check for Querolus in LiLa took 0.00040078163146972656s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.27818799018859863s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.02017831802368164s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.62396240234375e-05s
Believability | Calculation of trust value for Querolus in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for Querolus took 4.840633392333984s
Availability | SPARQL endpoint availability check for Quotations Book took 4.100799560546875e-05s
Availability | VoID file availability check for Quotations Book took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Quotations Book took 0.23929548263549805s
Reputation | Calculation of the PageRank for Quotations Book took 0.020168542861938477s
Interlinking | Calculation of Degree of Connection for Quotations Book took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Quotations Book took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 2.8133392333984375e-05s
Believability | Calculation of trust value for Quotations Book took 6.9141387939453125e-06s
INFO | --- Analysis for quotations_book took 2.88326358795166s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.26158690452575684s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020447969436645508s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 7.152557373046875e-06s
INFO | --- Analysis for r4r took 2.918881893157959s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.4413011074066162s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0003795623779296875s
Extra | Recovery of all triples for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 73.15555477142334s
Performance | Total latancy measurement for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.7471048831939697s
Amount of data | Number of triples check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.294060468673706s
Interoperability | New terms check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.7844533920288086s
Versatility | Languages check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 10.463550806045532s
Interpretability | Number of blank nodes check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.6944992542266846s
Interpretability | RDF structures check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14331674575805664s
Versatility | Serialization formats check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14344024658203125s
Availability | RDF dump link check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14147067070007324s
License | MR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15373730659484863s
License | HR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14240455627441406s
Amount of data | Number of property check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14159655570983887s
Understandability | Number of label check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14370155334472656s
Understandability | URI regex check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2952151298522949s
Understandability | Vocabs check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14257025718688965s
Verifiability | Authors check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15328145027160645s
Verifiability | Publishers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1432640552520752s
Performance | Throughput check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 10.736091136932373s
Amount of data | Check the number of entities for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.05718994140625e-05s
Verifiability | Contribs. check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1532888412475586s
Interlinking | sameAs chians check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1311476230621338s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1431262493133545s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14253020286560059s
Timeliness | dataset update frequency check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14149856567382812s
Currency | Creation date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2953205108642578s
Currency | Modification date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.28434157371520996s
Rep.Conc. | URIs length for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 17.548185110092163s
Interoperability | New vocabularies check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.37766051292419434s
Accuracy | Check Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.24043059349060059s
Accuracy | Check Inverse Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.16321778297424316s
Accuracy | Check Empty annotation labels for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.19532394409179688s
Accuracy | Check White space in annotation for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.410743713378906e-05s
Consistency | Disjoint class check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.17592167854309082s
Consistency | Check Misplaced properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.547338247299194s
Consistency | Check Ontology hijacking for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 16.688822984695435s
Consistency | Check Invalid usage of undefined properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 6.77085542678833s
Conciseness | Check Extensional conciseness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.00014066696166992188s
Security | Sign check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.20068645477294922s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.6940770149230957s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.887580871582031e-05s
Interoperability | Check the re-using of existing vocabs for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.9073486328125e-06s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.867813110351562e-06s
INFO | --- Analysis for racai-legalnero took 189.90063071250916s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 4.267692565917969e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.2760200500488281s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.02060103416442871s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 3.0517578125e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 8.58306884765625e-06s
INFO | --- Analysis for racai-llod-corola-we took 3.233271598815918s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 0.13053655624389648s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0005848407745361328s
Extra | Recovery of all triples for PARSEME-Ro corpus took 81.0959312915802s
Performance | Total latancy measurement for PARSEME-Ro corpus took 0.8607590198516846s
Amount of data | Number of triples check for PARSEME-Ro corpus took 7.313082933425903s
Interoperability | New terms check for PARSEME-Ro corpus took 2.647894859313965s
Versatility | Languages check for PARSEME-Ro corpus took 19.621371030807495s
Interpretability | Number of blank nodes check for PARSEME-Ro corpus took 5.279094219207764s
Interpretability | RDF structures check for PARSEME-Ro corpus took 0.13199734687805176s
Versatility | Serialization formats check for PARSEME-Ro corpus took 0.15308737754821777s
Availability | RDF dump link check for PARSEME-Ro corpus took 0.1420879364013672s
License | MR license check for PARSEME-Ro corpus took 0.14243412017822266s
License | HR license check for PARSEME-Ro corpus took 10.18579649925232s
Amount of data | Number of property check for PARSEME-Ro corpus took 0.14214277267456055s
Understandability | Number of label check for PARSEME-Ro corpus took 0.17572736740112305s
Understandability | URI regex check for PARSEME-Ro corpus took 0.28182172775268555s
Understandability | Vocabs check for PARSEME-Ro corpus took 0.15280890464782715s
Verifiability | Authors check for PARSEME-Ro corpus took 0.14952492713928223s
Verifiability | Publishers check for PARSEME-Ro corpus took 0.1418473720550537s
Performance | Throughput check for PARSEME-Ro corpus took 10.471904277801514s
Amount of data | Check the number of entities for PARSEME-Ro corpus took 0.00012063980102539062s
Verifiability | Contribs. check for PARSEME-Ro corpus took 0.14300274848937988s
Interlinking | sameAs chians check for PARSEME-Ro corpus took 0.14111900329589844s
Interlinking | skos check for PARSEME-Ro corpus took 0.15444421768188477s
Interlinking | skos check for PARSEME-Ro corpus took 0.14788079261779785s
Timeliness | dataset update frequency check for PARSEME-Ro corpus took 0.15899443626403809s
Currency | Creation date check for PARSEME-Ro corpus took 0.2932312488555908s
Currency | Modification date check for PARSEME-Ro corpus took 0.2947354316711426s
Rep.Conc. | URIs length for PARSEME-Ro corpus took 76.26508331298828s
Interoperability | New vocabularies check for PARSEME-Ro corpus took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for PARSEME-Ro corpus took 0.13228273391723633s
Accuracy | Check Functional Property for PARSEME-Ro corpus took 0.13007903099060059s
Accuracy | Check Inverse Functional Property for PARSEME-Ro corpus took 0.15285396575927734s
Accuracy | Check Empty annotation labels for PARSEME-Ro corpus took 3.830165147781372s
Accuracy | Check White space in annotation for PARSEME-Ro corpus took 0.23242425918579102s
Consistency | Disjoint class check for PARSEME-Ro corpus took 0.14106059074401855s
Consistency | Check Misplaced properties for PARSEME-Ro corpus took 11.222641706466675s
Consistency | Check Ontology hijacking for PARSEME-Ro corpus took 39.55980563163757s
Consistency | Check Invalid usage of undefined properties for PARSEME-Ro corpus took 13.213990926742554s
Conciseness | Check Extensional conciseness for PARSEME-Ro corpus took 0.0001556873321533203s
Security | Sign check for PARSEME-Ro corpus took 0.12940692901611328s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.8502061367034912s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.02057337760925293s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 3.123283386230469e-05s
Interoperability | Check the re-using of existing vocabs for PARSEME-Ro corpus took 1.6689300537109375e-06s
Believability | Calculation of trust value for PARSEME-Ro corpus took 1.239776611328125e-05s
INFO | --- Analysis for racai-llod-parseme-ro took 323.1288175582886s
Availability | SPARQL endpoint availability check for RoLEX took 0.14101648330688477s
Availability | VoID file availability check for RoLEX took 0.0005862712860107422s
Extra | Recovery of all triples for RoLEX took 68.38996171951294s
Performance | Total latancy measurement for RoLEX took 0.7396976947784424s
Amount of data | Number of triples check for RoLEX took 1.5637726783752441s
Interoperability | New terms check for RoLEX took 1.5608091354370117s
Versatility | Languages check for RoLEX took 4.4329962730407715s
Interpretability | Number of blank nodes check for RoLEX took 1.412963628768921s
Interpretability | RDF structures check for RoLEX took 0.14270830154418945s
Versatility | Serialization formats check for RoLEX took 0.1312999725341797s
Availability | RDF dump link check for RoLEX took 0.14003634452819824s
License | MR license check for RoLEX took 0.14207077026367188s
License | HR license check for RoLEX took 0.12951159477233887s
Amount of data | Number of property check for RoLEX took 0.14098000526428223s
Understandability | Number of label check for RoLEX took 0.1425621509552002s
Understandability | URI regex check for RoLEX took 0.3034498691558838s
Understandability | Vocabs check for RoLEX took 0.12937545776367188s
Verifiability | Authors check for RoLEX took 0.15365004539489746s
Verifiability | Publishers check for RoLEX took 0.13045954704284668s
Performance | Throughput check for RoLEX took 10.818028211593628s
Amount of data | Check the number of entities for RoLEX took 0.00010633468627929688s
Verifiability | Contribs. check for RoLEX took 0.14316630363464355s
Interlinking | sameAs chians check for RoLEX took 0.14059925079345703s
Interlinking | skos check for RoLEX took 0.1430668830871582s
Interlinking | skos check for RoLEX took 0.1528310775756836s
Timeliness | dataset update frequency check for RoLEX took 0.14166259765625s
Currency | Creation date check for RoLEX took 0.2834193706512451s
Currency | Modification date check for RoLEX took 0.2952725887298584s
Rep.Conc. | URIs length for RoLEX took 56.6852011680603s
Interoperability | New vocabularies check for RoLEX took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for RoLEX took 0.14255833625793457s
Accuracy | Check Functional Property for RoLEX took 0.14122772216796875s
Accuracy | Check Inverse Functional Property for RoLEX took 0.14067530632019043s
Consistency | Disjoint class check for RoLEX took 0.15521621704101562s
Consistency | Check Misplaced properties for RoLEX took 2.546299695968628s
Consistency | Check Ontology hijacking for RoLEX took 18.204278230667114s
Consistency | Check Invalid usage of undefined properties for RoLEX took 3.753857374191284s
Conciseness | Check Extensional conciseness for RoLEX took 0.00012993812561035156s
Security | Sign check for RoLEX took 0.15006422996520996s
Completeness | Calculation of interlinking completeness for RoLEX took 0.29836153984069824s
Reputation | Calculation of the PageRank for RoLEX took 0.02050185203552246s
Interlinking | Calculation of Degree of Connection for RoLEX took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for RoLEX took 2.9325485229492188e-05s
Interoperability | Check the re-using of existing vocabs for RoLEX took 1.9073486328125e-06s
Believability | Calculation of trust value for RoLEX took 6.9141387939453125e-06s
INFO | --- Analysis for racai-llod-rolex took 200.6665015220642s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0005986690521240234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.6949584484100342s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020035743713378906s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 2.8848648071289062e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 6.67572021484375e-06s
INFO | --- Analysis for racai-llod-romanian-treebank took 3.9683408737182617s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 4.1961669921875e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.24378657341003418s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.020150423049926758s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 2.8371810913085938e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 6.9141387939453125e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 3.589928150177002s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 4.124641418457031e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.253767728805542s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.020205259323120117s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 3.409385681152344e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 7.152557373046875e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 2.563084840774536s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 5.3882598876953125e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.23828673362731934s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.020360231399536133s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 2.7179718017578125e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 7.152557373046875e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 3.372398853302002s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.14150428771972656s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.00043964385986328125s
Extra | Recovery of all triples for ROBIN Technical Acquisition Speech Corpus took 25.45289444923401s
Performance | Total latancy measurement for ROBIN Technical Acquisition Speech Corpus took 0.7297594547271729s
Amount of data | Number of triples check for ROBIN Technical Acquisition Speech Corpus took 0.32588672637939453s
Interoperability | New terms check for ROBIN Technical Acquisition Speech Corpus took 1.399714708328247s
Versatility | Languages check for ROBIN Technical Acquisition Speech Corpus took 0.6710224151611328s
Interpretability | Number of blank nodes check for ROBIN Technical Acquisition Speech Corpus took 0.2645101547241211s
Interpretability | RDF structures check for ROBIN Technical Acquisition Speech Corpus took 0.1410832405090332s
Versatility | Serialization formats check for ROBIN Technical Acquisition Speech Corpus took 0.14197325706481934s
Availability | RDF dump link check for ROBIN Technical Acquisition Speech Corpus took 0.15154314041137695s
License | MR license check for ROBIN Technical Acquisition Speech Corpus took 0.1396329402923584s
License | HR license check for ROBIN Technical Acquisition Speech Corpus took 0.14757966995239258s
Amount of data | Number of property check for ROBIN Technical Acquisition Speech Corpus took 0.1505134105682373s
Understandability | Number of label check for ROBIN Technical Acquisition Speech Corpus took 0.14126086235046387s
Understandability | URI regex check for ROBIN Technical Acquisition Speech Corpus took 0.30270862579345703s
Understandability | Vocabs check for ROBIN Technical Acquisition Speech Corpus took 0.15065693855285645s
Verifiability | Authors check for ROBIN Technical Acquisition Speech Corpus took 0.14077281951904297s
Verifiability | Publishers check for ROBIN Technical Acquisition Speech Corpus took 0.15195703506469727s
Performance | Throughput check for ROBIN Technical Acquisition Speech Corpus took 10.78931474685669s
Amount of data | Check the number of entities for ROBIN Technical Acquisition Speech Corpus took 3.361701965332031e-05s
Verifiability | Contribs. check for ROBIN Technical Acquisition Speech Corpus took 0.15069222450256348s
Interlinking | sameAs chians check for ROBIN Technical Acquisition Speech Corpus took 0.1480100154876709s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.15514540672302246s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.13031435012817383s
Timeliness | dataset update frequency check for ROBIN Technical Acquisition Speech Corpus took 0.142136812210083s
Currency | Creation date check for ROBIN Technical Acquisition Speech Corpus took 0.30592846870422363s
Currency | Modification date check for ROBIN Technical Acquisition Speech Corpus took 0.27193260192871094s
Rep.Conc. | URIs length for ROBIN Technical Acquisition Speech Corpus took 2.9627180099487305s
Interoperability | New vocabularies check for ROBIN Technical Acquisition Speech Corpus took 6.198883056640625e-06s
Consistency | Deprecated classes/propertiers check for ROBIN Technical Acquisition Speech Corpus took 0.14993929862976074s
Accuracy | Check Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.13890695571899414s
Accuracy | Check Inverse Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.12846946716308594s
Accuracy | Check Empty annotation labels for ROBIN Technical Acquisition Speech Corpus took 0.41956591606140137s
Accuracy | Check White space in annotation for ROBIN Technical Acquisition Speech Corpus took 0.009571075439453125s
Accuracy | Check Datatype consistency for ROBIN Technical Acquisition Speech Corpus took 1.2053568363189697s
Consistency | Disjoint class check for ROBIN Technical Acquisition Speech Corpus took 0.13987994194030762s
Consistency | Check Misplaced properties for ROBIN Technical Acquisition Speech Corpus took 0.5350372791290283s
Consistency | Check Ontology hijacking for ROBIN Technical Acquisition Speech Corpus took 2.267158031463623s
Consistency | Check Invalid usage of undefined classes for ROBIN Technical Acquisition Speech Corpus took 1.167743444442749s
Consistency | Check Invalid usage of undefined properties for ROBIN Technical Acquisition Speech Corpus took 1.5362341403961182s
Conciseness | Check Extensional conciseness for ROBIN Technical Acquisition Speech Corpus took 0.8208658695220947s
Security | Sign check for ROBIN Technical Acquisition Speech Corpus took 0.14243483543395996s
Availability | Check URIs Dereferenciability for ROBIN Technical Acquisition Speech Corpus took 9597.215478658676s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 1.227020263671875s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.020819425582885742s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 2.9325485229492188e-05s
Interoperability | Check the re-using of existing vocabs for ROBIN Technical Acquisition Speech Corpus took 1.6689300537109375e-06s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 7.3909759521484375e-06s
INFO | --- Analysis for racai-llod-rtasc took 9670.816039800644s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.1290585994720459s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0006749629974365234s
Extra | Recovery of all triples for SiMoNERo - the Romanian medical treebank took 35.41244029998779s
Performance | Total latancy measurement for SiMoNERo - the Romanian medical treebank took 0.6860623359680176s
Amount of data | Number of triples check for SiMoNERo - the Romanian medical treebank took 1.0526885986328125s
Interoperability | New terms check for SiMoNERo - the Romanian medical treebank took 1.3897855281829834s
Versatility | Languages check for SiMoNERo - the Romanian medical treebank took 2.531134605407715s
Interpretability | Number of blank nodes check for SiMoNERo - the Romanian medical treebank took 0.888779878616333s
Interpretability | RDF structures check for SiMoNERo - the Romanian medical treebank took 0.1526021957397461s
Versatility | Serialization formats check for SiMoNERo - the Romanian medical treebank took 0.12845659255981445s
Availability | RDF dump link check for SiMoNERo - the Romanian medical treebank took 0.13830947875976562s
License | MR license check for SiMoNERo - the Romanian medical treebank took 0.138718843460083s
License | HR license check for SiMoNERo - the Romanian medical treebank took 4.715655565261841s
Amount of data | Number of property check for SiMoNERo - the Romanian medical treebank took 0.1297461986541748s
Understandability | Number of label check for SiMoNERo - the Romanian medical treebank took 0.14621973037719727s
Understandability | URI regex check for SiMoNERo - the Romanian medical treebank took 0.2826552391052246s
Understandability | Vocabs check for SiMoNERo - the Romanian medical treebank took 0.13052797317504883s
Verifiability | Authors check for SiMoNERo - the Romanian medical treebank took 0.14171409606933594s
Verifiability | Publishers check for SiMoNERo - the Romanian medical treebank took 0.1299428939819336s
Performance | Throughput check for SiMoNERo - the Romanian medical treebank took 10.759972095489502s
Amount of data | Check the number of entities for SiMoNERo - the Romanian medical treebank took 8.20159912109375e-05s
Verifiability | Contribs. check for SiMoNERo - the Romanian medical treebank took 0.1313788890838623s
Interlinking | sameAs chians check for SiMoNERo - the Romanian medical treebank took 0.1520397663116455s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.14250707626342773s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.15206670761108398s
Timeliness | dataset update frequency check for SiMoNERo - the Romanian medical treebank took 0.13002753257751465s
Currency | Creation date check for SiMoNERo - the Romanian medical treebank took 0.2838411331176758s
Currency | Modification date check for SiMoNERo - the Romanian medical treebank took 0.2827284336090088s
Rep.Conc. | URIs length for SiMoNERo - the Romanian medical treebank took 9.487042665481567s
Interoperability | New vocabularies check for SiMoNERo - the Romanian medical treebank took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for SiMoNERo - the Romanian medical treebank took 0.3491990566253662s
Accuracy | Check Functional Property for SiMoNERo - the Romanian medical treebank took 0.35538172721862793s
Accuracy | Check Inverse Functional Property for SiMoNERo - the Romanian medical treebank took 0.4109632968902588s
Accuracy | Check Empty annotation labels for SiMoNERo - the Romanian medical treebank took 1.4264225959777832s
Accuracy | Check White space in annotation for SiMoNERo - the Romanian medical treebank took 0.019899368286132812s
Accuracy | Check Datatype consistency for SiMoNERo - the Romanian medical treebank took 4.07176399230957s
Consistency | Disjoint class check for SiMoNERo - the Romanian medical treebank took 0.12990522384643555s
Consistency | Check Misplaced properties for SiMoNERo - the Romanian medical treebank took 1.7532463073730469s
Consistency | Check Ontology hijacking for SiMoNERo - the Romanian medical treebank took 4.751422643661499s
Consistency | Check Invalid usage of undefined classes for SiMoNERo - the Romanian medical treebank took 1.2394094467163086s
Consistency | Check Invalid usage of undefined properties for SiMoNERo - the Romanian medical treebank took 2.893592596054077s
Conciseness | Check Extensional conciseness for SiMoNERo - the Romanian medical treebank took 2.922863483428955s
Security | Sign check for SiMoNERo - the Romanian medical treebank took 0.13934850692749023s
Availability | Check URIs Dereferenciability for SiMoNERo - the Romanian medical treebank took 1759.5911734104156s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 1.4349350929260254s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.021270275115966797s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 3.647804260253906e-05s
Interoperability | Check the re-using of existing vocabs for SiMoNERo - the Romanian medical treebank took 1.6689300537109375e-06s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 7.62939453125e-06s
INFO | --- Analysis for racai-llod-simonero took 1869.8692753314972s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.22600650787353516s
Availability | VoID file availability check for Rådata nå! took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.7118334770202637s
Reputation | Calculation of the PageRank for Rådata nå! took 0.0204620361328125s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 8.034706115722656e-05s
Believability | Calculation of trust value for Rådata nå! took 6.9141387939453125e-06s
INFO | --- Analysis for radatana took 5.795736312866211s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 4.315376281738281e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0008282661437988281s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.70937180519104s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.02031421661376953s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 3.6716461181640625e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 7.3909759521484375e-06s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 17.42972731590271s
Availability | SPARQL endpoint availability check for Raphael Research Resource took 4.100799560546875e-05s
Availability | VoID file availability check for Raphael Research Resource took 0.0002999305725097656s
Completeness | Calculation of interlinking completeness for Raphael Research Resource took 0.31469082832336426s
Reputation | Calculation of the PageRank for Raphael Research Resource took 0.032743215560913086s
Interlinking | Calculation of Degree of Connection for Raphael Research Resource took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Raphael Research Resource took 0.0015063285827636719s
Interlinking | Calculation of Clustering coefficient for Raphael Research Resource took 4.649162292480469e-05s
Believability | Calculation of trust value for Raphael Research Resource took 8.344650268554688e-06s
INFO | --- Analysis for raphaelresearchresource took 2.931673288345337s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 12.385298490524292s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.2662315368652344s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.02060699462890625s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.314018249511719e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 8.106231689453125e-06s
INFO | --- Analysis for ravensburg-local-shopping-graph took 28.19112515449524s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 392.23653411865234s
Availability | VoID file availability check for Polish LGU financial statements took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.3290867805480957s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.026842832565307617s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 2.8848648071289062e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 7.152557373046875e-06s
INFO | --- Analysis for Rb_PL_LGU took 667.2085864543915s
Availability | SPARQL endpoint availability check for RCAHMS Archaeological Objects Thesaurus took 4.363059997558594e-05s
Availability | VoID file availability check for RCAHMS Archaeological Objects Thesaurus took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for RCAHMS Archaeological Objects Thesaurus took 0.7168481349945068s
Reputation | Calculation of the PageRank for RCAHMS Archaeological Objects Thesaurus took 0.020335912704467773s
Interlinking | Calculation of Degree of Connection for RCAHMS Archaeological Objects Thesaurus took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for RCAHMS Archaeological Objects Thesaurus took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for RCAHMS Archaeological Objects Thesaurus took 2.765655517578125e-05s
Believability | Calculation of trust value for RCAHMS Archaeological Objects Thesaurus took 1.239776611328125e-05s
INFO | --- Analysis for rcahms-archaeological-objects-thesaurus took 5.935714244842529s
Availability | SPARQL endpoint availability check for RCAHMS Maritime Craft Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for RCAHMS Maritime Craft Thesaurus took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for RCAHMS Maritime Craft Thesaurus took 0.2684972286224365s
Reputation | Calculation of the PageRank for RCAHMS Maritime Craft Thesaurus took 0.0227663516998291s
Interlinking | Calculation of Degree of Connection for RCAHMS Maritime Craft Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RCAHMS Maritime Craft Thesaurus took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for RCAHMS Maritime Craft Thesaurus took 2.8848648071289062e-05s
Believability | Calculation of trust value for RCAHMS Maritime Craft Thesaurus took 6.198883056640625e-06s
INFO | --- Analysis for rcahms-maritime-craft-thesaurus took 3.7868950366973877s
Availability | SPARQL endpoint availability check for RCAHMS Monument Types Thesaurus took 4.00543212890625e-05s
Availability | VoID file availability check for RCAHMS Monument Types Thesaurus took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for RCAHMS Monument Types Thesaurus took 0.26481080055236816s
Reputation | Calculation of the PageRank for RCAHMS Monument Types Thesaurus took 0.020343542098999023s
Interlinking | Calculation of Degree of Connection for RCAHMS Monument Types Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RCAHMS Monument Types Thesaurus took 0.0009894371032714844s
Interlinking | Calculation of Clustering coefficient for RCAHMS Monument Types Thesaurus took 3.0279159545898438e-05s
Believability | Calculation of trust value for RCAHMS Monument Types Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for rcahms-monument-types-thesaurus took 3.441344738006592s
Availability | SPARQL endpoint availability check for RCAHMW Monument Types Thesaurus took 4.0531158447265625e-05s
Availability | VoID file availability check for RCAHMW Monument Types Thesaurus took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for RCAHMW Monument Types Thesaurus took 0.7083518505096436s
Reputation | Calculation of the PageRank for RCAHMW Monument Types Thesaurus took 0.02007460594177246s
Interlinking | Calculation of Degree of Connection for RCAHMW Monument Types Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RCAHMW Monument Types Thesaurus took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for RCAHMW Monument Types Thesaurus took 2.7418136596679688e-05s
Believability | Calculation of trust value for RCAHMW Monument Types Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for rcahmw-monument-types-thesaurus took 3.8337345123291016s
Availability | SPARQL endpoint availability check for RCAHMW Periods List took 4.076957702636719e-05s
Availability | VoID file availability check for RCAHMW Periods List took 0.0002987384796142578s
Completeness | Calculation of interlinking completeness for RCAHMW Periods List took 0.2657768726348877s
Reputation | Calculation of the PageRank for RCAHMW Periods List took 0.020871400833129883s
Interlinking | Calculation of Degree of Connection for RCAHMW Periods List took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RCAHMW Periods List took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for RCAHMW Periods List took 3.0517578125e-05s
Believability | Calculation of trust value for RCAHMW Periods List took 7.152557373046875e-06s
INFO | --- Analysis for rcahmw-periods-list took 2.864809036254883s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 4.172325134277344e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.2477097511291504s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.020521879196166992s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.58306884765625e-05s
Believability | Calculation of trust value for RDF Book Mashup took 5.9604644775390625e-06s
INFO | --- Analysis for rdf-book-mashup took 3.394404649734497s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 4.267692565917969e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.26745176315307617s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 9.822845458984375e-05s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 6.198883056640625e-06s
INFO | --- Analysis for rdfize-lastfm took 2.5928080081939697s
Availability | SPARQL endpoint availability check for RDFLicense took 261.278799533844s
Availability | VoID file availability check for RDFLicense took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.27416300773620605s
Reputation | Calculation of the PageRank for RDFLicense took 0.020757436752319336s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 4.673004150390625e-05s
Believability | Calculation of trust value for RDFLicense took 1.239776611328125e-05s
INFO | --- Analysis for rdflicense took 536.2204451560974s
Availability | SPARQL endpoint availability check for RDFohloh took 4.1961669921875e-05s
Availability | VoID file availability check for RDFohloh took 0.0003960132598876953s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.6833319664001465s
Reputation | Calculation of the PageRank for RDFohloh took 0.02053689956665039s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 9.655952453613281e-05s
Believability | Calculation of trust value for RDFohloh took 9.059906005859375e-06s
INFO | --- Analysis for rdfohloh took 7.546630620956421s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.6762998104095459s
Availability | VoID file availability check for Reactome RDF took 0.00042629241943359375s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.27211761474609375s
Reputation | Calculation of the PageRank for Reactome RDF took 0.02134227752685547s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.62396240234375e-05s
Believability | Calculation of trust value for Reactome RDF took 7.152557373046875e-06s
INFO | --- Analysis for reactome-rdf took 4.29067850112915s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 0.13136911392211914s
Availability | VoID file availability check for Rechtspraak.nl took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.26136112213134766s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.020578861236572266s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 9.417533874511719e-05s
Believability | Calculation of trust value for Rechtspraak.nl took 4.5299530029296875e-06s
INFO | --- Analysis for rechtspraak took 2.538160800933838s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 4.553794860839844e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.25896739959716797s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.02116084098815918s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 9.059906005859375e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 6.67572021484375e-06s
INFO | --- Analysis for red-uno-internacional-santillana took 8.929256677627563s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.12128996849060059s
Availability | VoID file availability check for reference.data.gov.uk took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.2648322582244873s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.02025604248046875s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.0001723766326904297s
Believability | Calculation of trust value for reference.data.gov.uk took 5.0067901611328125e-06s
INFO | --- Analysis for reference-data-gov-uk took 2.6346969604492188s
Availability | SPARQL endpoint availability check for Regiony took 3.9577484130859375e-05s
Availability | VoID file availability check for Regiony took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Regiony took 0.2672150135040283s
Reputation | Calculation of the PageRank for Regiony took 0.020366430282592773s
Interlinking | Calculation of Degree of Connection for Regiony took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Regiony took 0.0007808208465576172s
Interlinking | Calculation of Clustering coefficient for Regiony took 3.2901763916015625e-05s
Believability | Calculation of trust value for Regiony took 9.298324584960938e-06s
INFO | --- Analysis for regiony took 2.9940083026885986s
Availability | SPARQL endpoint availability check for RELD took 262.7198793888092s
Availability | VoID file availability check for RELD took 0.00032448768615722656s
Completeness | Calculation of interlinking completeness for RELD took 0.28432750701904297s
Reputation | Calculation of the PageRank for RELD took 0.020917654037475586s
Interlinking | Calculation of Degree of Connection for RELD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RELD took 0.0009710788726806641s
Interlinking | Calculation of Clustering coefficient for RELD took 4.553794860839844e-05s
Believability | Calculation of trust value for RELD took 7.152557373046875e-06s
INFO | --- Analysis for RELD took 537.453512430191s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.365938663482666s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.00029778480529785156s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 1.29537034034729s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 0.5903429985046387s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.3859806060791016s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.5013542175292969s
Versatility | Languages check for Repository for Linked Open Archival Data took 6.084229946136475s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 2.3340907096862793s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.1911606788635254s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.5122048854827881s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.3918581008911133s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.16735291481018066s
License | MR license check for Repository for Linked Open Archival Data took 0.5535826683044434s
License | HR license check for Repository for Linked Open Archival Data took 8.282692193984985s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.2927877902984619s
Understandability | Number of label check for Repository for Linked Open Archival Data took 1.6410207748413086s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.5902750492095947s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.19488286972045898s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.2203373908996582s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.19041919708251953s
Performance | Throughput check for Repository for Linked Open Archival Data took 10.654618740081787s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 4.839897155761719e-05s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.07422304153442383s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.36864447593688965s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.3052973747253418s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.13155174255371094s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.39280056953430176s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.44151878356933594s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.2426166534423828s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 3.0270073413848877s
Interoperability | New vocabularies check for Repository for Linked Open Archival Data took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Repository for Linked Open Archival Data took 0.19002032279968262s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.17707204818725586s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.14138555526733398s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 1.810513973236084s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.028753995895385742s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.028097867965698242s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.27723050117492676s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 2.0653610229492188s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.19539880752563477s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.5580847263336182s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.1788873672485352s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 3.0407111644744873s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.029735565185546875s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.1330738067626953s
Security | Sign check for Repository for Linked Open Archival Data took 0.6911296844482422s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 1152.184241771698s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.9821529388427734s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.020776033401489258s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 4.1484832763671875e-05s
Interoperability | Check the re-using of existing vocabs for Repository for Linked Open Archival Data took 1.1920928955078125e-06s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 6.4373016357421875e-06s
INFO | --- Analysis for reload took 1279.70236992836s
Availability | SPARQL endpoint availability check for Land use merced dataset took 4.267692565917969e-05s
Availability | VoID file availability check for Land use merced dataset took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.27631688117980957s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.020258665084838867s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 2.8848648071289062e-05s
Believability | Calculation of trust value for Land use merced dataset took 6.9141387939453125e-06s
INFO | --- Analysis for remote_Sensing took 13.688291788101196s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 1.8636655807495117s
Availability | VoID file availability check for Renewable Energy Generators took 0.0006079673767089844s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.29247260093688965s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.020081281661987305s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.267692565917969e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 5.245208740234375e-06s
INFO | --- Analysis for renewable_energy_generators took 11.447270154953003s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.05540132522583008s
Availability | VoID file availability check for research.data.gov.uk took 0.00022459030151367188s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.26761531829833984s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.020102500915527344s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 8.749961853027344e-05s
Believability | Calculation of trust value for research.data.gov.uk took 5.4836273193359375e-06s
INFO | --- Analysis for research-data-gov-uk took 2.963636875152588s
Availability | SPARQL endpoint availability check for Research object in Agricolture and Food of the University of Naples took 6.198883056640625e-05s
Availability | VoID file availability check for Research object in Agricolture and Food of the University of Naples took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Research object in Agricolture and Food of the University of Naples took 0.2593088150024414s
Reputation | Calculation of the PageRank for Research object in Agricolture and Food of the University of Naples took 0.02649068832397461s
Interlinking | Calculation of Degree of Connection for Research object in Agricolture and Food of the University of Naples took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Research object in Agricolture and Food of the University of Naples took 0.0008082389831542969s
Interlinking | Calculation of Clustering coefficient for Research object in Agricolture and Food of the University of Naples took 3.528594970703125e-05s
Believability | Calculation of trust value for Research object in Agricolture and Food of the University of Naples took 6.4373016357421875e-06s
INFO | --- Analysis for research-object-in-agricolture-and-food-of-the-university-of-naples took 2.9245288372039795s
Availability | SPARQL endpoint availability check for Restaurantes took 4.076957702636719e-05s
Availability | VoID file availability check for Restaurantes took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for Restaurantes took 0.2539229393005371s
Reputation | Calculation of the PageRank for Restaurantes took 0.02090740203857422s
Interlinking | Calculation of Degree of Connection for Restaurantes took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Restaurantes took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Restaurantes took 2.956390380859375e-05s
Believability | Calculation of trust value for Restaurantes took 6.67572021484375e-06s
INFO | --- Analysis for restaurantes-zaragoza took 2.9520888328552246s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 4.220008850097656e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0006113052368164062s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.27179455757141113s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.020247936248779297s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 6.699562072753906e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 6.9141387939453125e-06s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 3.98040509223938s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 0.04818987846374512s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.0003414154052734375s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.2493605613708496s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.020178794860839844s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 2.8133392333984375e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 6.9141387939453125e-06s
INFO | --- Analysis for revistas_turismo took 2.4631333351135254s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.28790903091430664s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.00022554397583007812s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.28947925567626953s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.020042896270751953s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00011301040649414062s
Believability | Calculation of trust value for Revyu.com - Review Anything took 6.9141387939453125e-06s
INFO | --- Analysis for revyu took 2.681807279586792s
Availability | SPARQL endpoint availability check for sdafsadf took 0.4235954284667969s
Availability | VoID file availability check for sdafsadf took 0.00033545494079589844s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.26378321647644043s
Reputation | Calculation of the PageRank for sdafsadf took 0.02003645896911621s
Interlinking | Calculation of Degree of Connection for sdafsadf took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 2.7179718017578125e-05s
Believability | Calculation of trust value for sdafsadf took 7.3909759521484375e-06s
INFO | --- Analysis for rgsdfg took 3.193758964538574s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 4.1484832763671875e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.2645082473754883s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.020110607147216797s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 4.506111145019531e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 6.9141387939453125e-06s
INFO | --- Analysis for riese took 2.471487045288086s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection Data took 4.0531158447265625e-05s
Availability | VoID file availability check for Rijksmuseum Collection Data took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection Data took 0.26482605934143066s
Reputation | Calculation of the PageRank for Rijksmuseum Collection Data took 0.0203402042388916s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Rijksmuseum Collection Data took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection Data took 3.24249267578125e-05s
Believability | Calculation of trust value for Rijksmuseum Collection Data took 7.867813110351562e-06s
INFO | --- Analysis for rijksmuseum took 2.918104887008667s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.6364264488220215s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.2576289176940918s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.020260095596313477s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 4.267692565917969e-05s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 6.4373016357421875e-06s
INFO | --- Analysis for rism took 3.5856502056121826s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.1894547939300537s
Availability | VoID file availability check for RISM Authority data took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.2429523468017578s
Reputation | Calculation of the PageRank for RISM Authority data took 0.020132064819335938s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 4.124641418457031e-05s
Believability | Calculation of trust value for RISM Authority data took 7.152557373046875e-06s
INFO | --- Analysis for rism-authorities took 3.184767246246338s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.172325134277344e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.26604533195495605s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.02021336555480957s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 2.765655517578125e-05s
Believability | Calculation of trust value for engineering equipment ontology took 7.152557373046875e-06s
INFO | --- Analysis for rk took 2.4065916538238525s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.034147024154663086s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.25298380851745605s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.020099878311157227s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0002224445343017578s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-acm took 2.405052900314331s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.05244636535644531s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.26856040954589844s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.020237207412719727s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.0001361370086669922s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-budapest took 2.510300397872925s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.03980851173400879s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.2534916400909424s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.0205690860748291s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.0002052783966064453s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-citeseer took 2.3617806434631348s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.042349815368652344s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.23078656196594238s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.020187854766845703s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00017023086547851562s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-cordis took 2.3605377674102783s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.04205918312072754s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.25881004333496094s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.020493030548095703s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.00016069412231445312s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-courseware took 2.3833720684051514s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.039641380310058594s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.2538301944732666s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.020331382751464844s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 3.933906555175781e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 5.7220458984375e-06s
INFO | --- Analysis for rkb-explorer-crime took 2.4062087535858154s
Availability | SPARQL endpoint availability check for crm took 4.1484832763671875e-05s
Availability | VoID file availability check for crm took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for crm took 0.26442980766296387s
Reputation | Calculation of the PageRank for crm took 0.020289897918701172s
Interlinking | Calculation of Degree of Connection for crm took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for crm took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for crm took 3.0994415283203125e-05s
Believability | Calculation of trust value for crm took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-crm took 2.748821258544922s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.044695377349853516s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.254209041595459s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.020424842834472656s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00012254714965820312s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-curriculum took 2.449089765548706s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.045560359954833984s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.29578161239624023s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.0203702449798584s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.125999450683594e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.404576301574707s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.04349040985107422s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.2413780689239502s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.020311355590820312s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.0002396106719970703s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 2.193450927734375e-05s
INFO | --- Analysis for rkb-explorer-dblp took 2.348985195159912s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.04119229316711426s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.25124096870422363s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.02057361602783203s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.414817810058594e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-deepblue took 2.399224281311035s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.04389691352844238s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.26045894622802734s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.020201444625854492s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.417533874511719e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-deploy took 2.3951828479766846s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.0512392520904541s
Availability | VoID file availability check for digitaleconomy took 0.0003542900085449219s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.2811908721923828s
Reputation | Calculation of the PageRank for digitaleconomy took 0.020339250564575195s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 2.9325485229492188e-05s
Believability | Calculation of trust value for digitaleconomy took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.5362541675567627s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.04537200927734375s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.2737271785736084s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.02036309242248535s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.00014853477478027344s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-dotac took 2.448171854019165s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.03690600395202637s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2707364559173584s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020328760147094727s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.38690185546875e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-ecs took 2.7323431968688965s
Availability | SPARQL endpoint availability check for enaktingpsi took 4.2438507080078125e-05s
Availability | VoID file availability check for enaktingpsi took 0.0003497600555419922s
Completeness | Calculation of interlinking completeness for enaktingpsi took 0.25683093070983887s
Reputation | Calculation of the PageRank for enaktingpsi took 0.020461320877075195s
Interlinking | Calculation of Degree of Connection for enaktingpsi took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for enaktingpsi took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for enaktingpsi took 2.8133392333984375e-05s
Believability | Calculation of trust value for enaktingpsi took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-enaktingpsi took 2.8490543365478516s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.048265933990478516s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.25876808166503906s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.020239830017089844s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.000179290771484375s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-eprints took 2.448190212249756s
Availability | SPARQL endpoint availability check for epsrc took 0.048248291015625s
Availability | VoID file availability check for epsrc took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for epsrc took 0.28259873390197754s
Reputation | Calculation of the PageRank for epsrc took 0.020092487335205078s
Interlinking | Calculation of Degree of Connection for epsrc took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for epsrc took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.650520324707031e-05s
Believability | Calculation of trust value for epsrc took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-epsrc took 2.5351696014404297s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.04261898994445801s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.27412915229797363s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.020082950592041016s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 8.082389831542969e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-era took 2.4485042095184326s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.05064034461975098s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.263202428817749s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.020193099975585938s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00010013580322265625s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-eurecom took 2.521064281463623s
Availability | SPARQL endpoint availability check for rkb-explorer-foreign took 4.887580871582031e-05s
Availability | VoID file availability check for rkb-explorer-foreign took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for rkb-explorer-foreign took 0.2574954032897949s
Reputation | Calculation of the PageRank for rkb-explorer-foreign took 0.020166397094726562s
Interlinking | Calculation of Degree of Connection for rkb-explorer-foreign took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for rkb-explorer-foreign took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for rkb-explorer-foreign took 2.8133392333984375e-05s
Believability | Calculation of trust value for rkb-explorer-foreign took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-foreign took 3.0175182819366455s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0348968505859375s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.268435001373291s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.020201683044433594s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 8.726119995117188e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-ft took 2.5192513465881348s
Availability | SPARQL endpoint availability check for fun took 0.043890953063964844s
Availability | VoID file availability check for fun took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for fun took 0.28051018714904785s
Reputation | Calculation of the PageRank for fun took 0.019989013671875s
Interlinking | Calculation of Degree of Connection for fun took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for fun took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for fun took 7.081031799316406e-05s
Believability | Calculation of trust value for fun took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-fun took 2.553828477859497s
Availability | SPARQL endpoint availability check for gdlc took 0.043601036071777344s
Availability | VoID file availability check for gdlc took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for gdlc took 0.2882575988769531s
Reputation | Calculation of the PageRank for gdlc took 0.020534276962280273s
Interlinking | Calculation of Degree of Connection for gdlc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for gdlc took 7.033348083496094e-05s
Believability | Calculation of trust value for gdlc took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-gdlc took 2.547454595565796s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.04086112976074219s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.27884435653686523s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.020228147506713867s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00011563301086425781s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-ibm took 2.567218780517578s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.046114444732666016s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.28026676177978516s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.02025294303894043s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.0001316070556640625s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-ieee took 2.549973964691162s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.041672468185424805s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0003707408905029297s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.24277186393737793s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.02024984359741211s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00017189979553222656s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-irit took 2.4855191707611084s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.03447580337524414s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.00022554397583007812s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.25404906272888184s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.020222902297973633s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.246566772460938e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.198883056640625e-06s
INFO | --- Analysis for rkb-explorer-italy took 2.488274335861206s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.045564889907836914s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.26198577880859375s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.020329713821411133s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.700920104980469e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 3.1948089599609375e-05s
INFO | --- Analysis for rkb-explorer-jisc took 2.5930182933807373s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.047945261001586914s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.2849555015563965s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.02007603645324707s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.076957702636719e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-kaunas took 2.5431129932403564s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.041289329528808594s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0003578662872314453s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.26798272132873535s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.020115375518798828s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00016355514526367188s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-kisti took 2.486938953399658s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.05230975151062012s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.283841609954834s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.020334959030151367s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.0001518726348876953s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-laas took 2.5188815593719482s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.04420638084411621s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0004200935363769531s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.273040771484375s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.02038860321044922s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.437301635742188e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-lisbon took 2.4462366104125977s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.050139427185058594s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.00041985511779785156s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.2839949131011963s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020276308059692383s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.0001552104949951172s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 2.5232865810394287s
Availability | SPARQL endpoint availability check for notube took 0.04929924011230469s
Availability | VoID file availability check for notube took 0.00036907196044921875s
Completeness | Calculation of interlinking completeness for notube took 0.25482797622680664s
Reputation | Calculation of the PageRank for notube took 0.020609617233276367s
Interlinking | Calculation of Degree of Connection for notube took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for notube took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for notube took 4.220008850097656e-05s
Believability | Calculation of trust value for notube took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-notube took 2.3850035667419434s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.04420113563537598s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.00042724609375s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.2815737724304199s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.021415233612060547s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.001275777816772461s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00019168853759765625s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-nsf took 2.45892596244812s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.049555301666259766s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.27944445610046387s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.020350933074951172s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00015544891357421875s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-oai took 2.5158238410949707s
Availability | SPARQL endpoint availability check for OpenCyc (RKBExplorer) took 3.981590270996094e-05s
Availability | VoID file availability check for OpenCyc (RKBExplorer) took 0.0002846717834472656s
Completeness | Calculation of interlinking completeness for OpenCyc (RKBExplorer) took 0.2891833782196045s
Reputation | Calculation of the PageRank for OpenCyc (RKBExplorer) took 0.02021050453186035s
Interlinking | Calculation of Degree of Connection for OpenCyc (RKBExplorer) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for OpenCyc (RKBExplorer) took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for OpenCyc (RKBExplorer) took 2.7894973754882812e-05s
Believability | Calculation of trust value for OpenCyc (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-opencyc took 3.06463885307312s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.0469512939453125s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.6684250831604004s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.02026510238647461s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.843971252441406e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-os took 3.3787331581115723s
Availability | SPARQL endpoint availability check for photos took 0.044498443603515625s
Availability | VoID file availability check for photos took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for photos took 0.2780609130859375s
Reputation | Calculation of the PageRank for photos took 0.019835710525512695s
Interlinking | Calculation of Degree of Connection for photos took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for photos took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for photos took 6.961822509765625e-05s
Believability | Calculation of trust value for photos took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-photos took 2.499512195587158s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.04524970054626465s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.0010449886322021484s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.2613515853881836s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.020059585571289062s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00011110305786132812s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-pisa took 2.5142483711242676s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.043849945068359375s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.2692568302154541s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.020217418670654297s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00019812583923339844s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.451019048690796s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.041579484939575195s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0011055469512939453s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.28929758071899414s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.020176410675048828s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00014328956604003906s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-resex took 2.5141475200653076s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.05250215530395508s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.27451109886169434s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020166635513305664s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 8.96453857421875e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-risks took 2.4997196197509766s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.03578448295593262s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0008695125579833984s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.2653384208679199s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0201108455657959s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00012540817260742188s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-roma took 2.4912381172180176s
Availability | SPARQL endpoint availability check for roni took 0.04173707962036133s
Availability | VoID file availability check for roni took 0.00021529197692871094s
Completeness | Calculation of interlinking completeness for roni took 0.27022361755371094s
Reputation | Calculation of the PageRank for roni took 0.020223379135131836s
Interlinking | Calculation of Degree of Connection for roni took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for roni took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for roni took 2.6702880859375e-05s
Believability | Calculation of trust value for roni took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-roni took 2.5043411254882812s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.05240058898925781s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00040268898010253906s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.26714372634887695s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.02015399932861328s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00022864341735839844s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-southampton took 2.542963743209839s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.04550290107727051s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.2618751525878906s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.02012038230895996s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00010752677917480469s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-ulm took 2.5034711360931396s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.04619884490966797s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.2713611125946045s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.020033836364746094s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 9.799003601074219e-05s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-unlocode took 2.4861888885498047s
Availability | SPARQL endpoint availability check for webconf took 0.05504417419433594s
Availability | VoID file availability check for webconf took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for webconf took 0.28362154960632324s
Reputation | Calculation of the PageRank for webconf took 0.0204620361328125s
Interlinking | Calculation of Degree of Connection for webconf took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for webconf took 0.0001068115234375s
Believability | Calculation of trust value for webconf took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-webconf took 12.822693824768066s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.043736934661865234s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.0004260540008544922s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.25434207916259766s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.02023005485534668s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 7.128715515136719e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-webscience took 2.514866352081299s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.04831051826477051s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.2602858543395996s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.00021028518676757812s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-wiki took 2.4688949584960938s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.04884648323059082s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.26915669441223145s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.02075672149658203s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0010662078857421875s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 0.00011467933654785156s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-wordnet took 2.491504430770874s
Availability | SPARQL endpoint availability check for RKB Explorer Data took 4.100799560546875e-05s
Availability | VoID file availability check for RKB Explorer Data took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for RKB Explorer Data took 0.2878868579864502s
Reputation | Calculation of the PageRank for RKB Explorer Data took 0.02028203010559082s
Interlinking | Calculation of Degree of Connection for RKB Explorer Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RKB Explorer Data took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for RKB Explorer Data took 2.9325485229492188e-05s
Believability | Calculation of trust value for RKB Explorer Data took 8.106231689453125e-06s
INFO | --- Analysis for rkb_explorer_data took 2.929520606994629s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.5501208305358887s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.2749600410461426s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.02002239227294922s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 8.320808410644531e-05s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 7.3909759521484375e-06s
INFO | --- Analysis for roceeh-road took 3.70387864112854s
Availability | SPARQL endpoint availability check for The Rosetta Project took 4.172325134277344e-05s
Availability | VoID file availability check for The Rosetta Project took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for The Rosetta Project took 0.2705059051513672s
Reputation | Calculation of the PageRank for The Rosetta Project took 0.02032923698425293s
Interlinking | Calculation of Degree of Connection for The Rosetta Project took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Rosetta Project took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for The Rosetta Project took 2.86102294921875e-05s
Believability | Calculation of trust value for The Rosetta Project took 8.344650268554688e-06s
INFO | --- Analysis for rosetta-project took 2.93205189704895s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 4.172325134277344e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.0006117820739746094s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.25955986976623535s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.02040839195251465s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 2.9325485229492188e-05s
Believability | Calculation of trust value for ontology terrorist attack took 7.62939453125e-06s
INFO | --- Analysis for ROSHANI took 3.554872989654541s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 4.363059997558594e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.2748301029205322s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.02030324935913086s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.719329833984375e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 7.152557373046875e-06s
INFO | --- Analysis for ROSHANI_SAHU took 2.331165313720703s
Availability | SPARQL endpoint availability check for x took 4.410743713378906e-05s
Availability | VoID file availability check for x took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for x took 0.26702165603637695s
Reputation | Calculation of the PageRank for x took 0.020621538162231445s
Interlinking | Calculation of Degree of Connection for x took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for x took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for x took 6.222724914550781e-05s
Believability | Calculation of trust value for x took 7.152557373046875e-06s
INFO | --- Analysis for Rozprawa,_artykuł took 2.406601905822754s
Availability | SPARQL endpoint availability check for Rpm Find took 4.0531158447265625e-05s
Availability | VoID file availability check for Rpm Find took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for Rpm Find took 0.26547861099243164s
Reputation | Calculation of the PageRank for Rpm Find took 0.02034902572631836s
Interlinking | Calculation of Degree of Connection for Rpm Find took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Rpm Find took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Rpm Find took 2.8371810913085938e-05s
Believability | Calculation of trust value for Rpm Find took 7.152557373046875e-06s
INFO | --- Analysis for rpm_find took 2.8782825469970703s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 4.410743713378906e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.26030993461608887s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.020212411880493164s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 6.556510925292969e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 6.9141387939453125e-06s
INFO | --- Analysis for rss-500-nif-ner-corpus took 3.75885272026062s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 5.340576171875e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.2935018539428711s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.01999950408935547s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 7.176399230957031e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 6.9141387939453125e-06s
INFO | --- Analysis for rubentaelman took 2.8435704708099365s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 4.220008850097656e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.2654399871826172s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.020123958587646484s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.559226989746094e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 8.58306884765625e-06s
INFO | --- Analysis for rubenverborgh took 3.5160906314849854s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 392.063547372818s
Availability | VoID file availability check for Russian Universities Specialities took 0.0007736682891845703s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.2721526622772217s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.021326065063476562s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 3.409385681152344e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 8.58306884765625e-06s
INFO | --- Analysis for russian-universities-specialities took 677.2683141231537s
Availability | SPARQL endpoint availability check for RuThes Cloud took 4.029273986816406e-05s
Availability | VoID file availability check for RuThes Cloud took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for RuThes Cloud took 0.2708628177642822s
Reputation | Calculation of the PageRank for RuThes Cloud took 0.020547866821289062s
Interlinking | Calculation of Degree of Connection for RuThes Cloud took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for RuThes Cloud took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for RuThes Cloud took 2.9325485229492188e-05s
Believability | Calculation of trust value for RuThes Cloud took 1.1444091796875e-05s
INFO | --- Analysis for ruthes took 5.200114965438843s
Availability | SPARQL endpoint availability check for RxNorm took 4.100799560546875e-05s
Availability | VoID file availability check for RxNorm took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for RxNorm took 0.2769782543182373s
Reputation | Calculation of the PageRank for RxNorm took 0.020638704299926758s
Interlinking | Calculation of Degree of Connection for RxNorm took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RxNorm took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for RxNorm took 3.7670135498046875e-05s
Believability | Calculation of trust value for RxNorm took 7.62939453125e-06s
INFO | --- Analysis for rxnorm took 4.1230528354644775s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 3.6366078853607178s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.2783067226409912s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.02084636688232422s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 3.4332275390625e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 7.3909759521484375e-06s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 9.057784795761108s
Availability | SPARQL endpoint availability check for SALDO took 4.124641418457031e-05s
Availability | VoID file availability check for SALDO took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for SALDO took 0.268862247467041s
Reputation | Calculation of the PageRank for SALDO took 0.020304203033447266s
Interlinking | Calculation of Degree of Connection for SALDO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SALDO took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for SALDO took 4.00543212890625e-05s
Believability | Calculation of trust value for SALDO took 6.67572021484375e-06s
INFO | --- Analysis for saldo took 3.5472495555877686s
Availability | SPARQL endpoint availability check for SALDO-RDF took 1.3064677715301514s
Availability | VoID file availability check for SALDO-RDF took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.27893924713134766s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.020461082458496094s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.719329833984375e-05s
Believability | Calculation of trust value for SALDO-RDF took 7.62939453125e-06s
INFO | --- Analysis for saldo-rdf took 5.836360931396484s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.6432116031646729s
Availability | VoID file availability check for SALDOM-RDF took 0.0006306171417236328s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.2714245319366455s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.020432233810424805s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.5762786865234375e-05s
Believability | Calculation of trust value for SALDOM-RDF took 8.106231689453125e-06s
INFO | --- Analysis for saldom-rdf took 4.7882773876190186s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 4.4345855712890625e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.2653331756591797s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.0203707218170166s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00010323524475097656s
Believability | Calculation of trust value for Salzburgerland DE took 7.867813110351562e-06s
INFO | --- Analysis for salzburgerland-com-de took 3.023024797439575s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 4.363059997558594e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.2788372039794922s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.020376920700073242s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.00012183189392089844s
Believability | Calculation of trust value for Salzburgerland EN took 7.152557373046875e-06s
INFO | --- Analysis for salzburgerland-com-en took 2.863893985748291s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.315376281738281e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.25312328338623047s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.020275592803955078s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00010418891906738281s
Believability | Calculation of trust value for Salzburgerland IT took 7.152557373046875e-06s
INFO | --- Analysis for salzburgerland-com-it took 2.8639333248138428s
Availability | SPARQL endpoint availability check for sameAs.org took 4.076957702636719e-05s
Availability | VoID file availability check for sameAs.org took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for sameAs.org took 0.2668883800506592s
Reputation | Calculation of the PageRank for sameAs.org took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for sameAs.org took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for sameAs.org took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for sameAs.org took 2.86102294921875e-05s
Believability | Calculation of trust value for sameAs.org took 7.62939453125e-06s
INFO | --- Analysis for sameas-org took 2.908879041671753s
Availability | SPARQL endpoint availability check for sandrart.net took 4.2438507080078125e-05s
Availability | VoID file availability check for sandrart.net took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.286480188369751s
Reputation | Calculation of the PageRank for sandrart.net took 0.020415782928466797s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.723403930664062e-05s
Believability | Calculation of trust value for sandrart.net took 7.62939453125e-06s
INFO | --- Analysis for sandrart-net took 3.561009168624878s
Availability | SPARQL endpoint availability check for Taxons  took 0.31108689308166504s
Availability | VoID file availability check for Taxons  took 0.0004665851593017578s
Extra | Recovery of all triples for Taxons  took 23.212244749069214s
Performance | Total latancy measurement for Taxons  took 0.4414346218109131s
Amount of data | Number of triples check for Taxons  took 2.2233293056488037s
Interoperability | New terms check for Taxons  took 1.7841858863830566s
Versatility | Languages check for Taxons  took 53.89308524131775s
Interpretability | Number of blank nodes check for Taxons  took 3.69476318359375s
Security | Check HTTPS for Taxons  took 0.19275236129760742s
Interpretability | RDF structures check for Taxons  took 1.2506334781646729s
Versatility | Serialization formats check for Taxons  took 0.6462182998657227s
Availability | RDF dump link check for Taxons  took 0.3755526542663574s
License | MR license check for Taxons  took 2.412269353866577s
License | HR license check for Taxons  took 2.2585623264312744s
Amount of data | Number of property check for Taxons  took 0.16997170448303223s
Understandability | Number of label check for Taxons  took 7.388257741928101s
Understandability | URI regex check for Taxons  took 1.1838135719299316s
Understandability | Vocabs check for Taxons  took 0.29122018814086914s
Verifiability | Authors check for Taxons  took 0.10975265502929688s
Verifiability | Publishers check for Taxons  took 0.07977581024169922s
Performance | Throughput check for Taxons  took 10.526877880096436s
Amount of data | Check the number of entities for Taxons  took 7.343292236328125e-05s
Verifiability | Contribs. check for Taxons  took 0.09145283699035645s
Interlinking | sameAs chians check for Taxons  took 0.14709138870239258s
Interlinking | skos check for Taxons  took 0.16277813911437988s
Interlinking | skos check for Taxons  took 0.08745789527893066s
Timeliness | dataset update frequency check for Taxons  took 0.5929574966430664s
Currency | Creation date check for Taxons  took 0.19384169578552246s
Currency | Modification date check for Taxons  took 0.20615720748901367s
Rep.Conc. | URIs length for Taxons  took 10.984719038009644s
Interoperability | New vocabularies check for Taxons  took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for Taxons  took 0.1094200611114502s
Accuracy | Check Functional Property for Taxons  took 0.43901705741882324s
Accuracy | Check Inverse Functional Property for Taxons  took 0.38902759552001953s
Accuracy | Check Empty annotation labels for Taxons  took 3.8194150924682617s
Accuracy | Check White space in annotation for Taxons  took 0.30172133445739746s
Accuracy | Check Datatype consistency for Taxons  took 0.2706127166748047s
Consistency | Disjoint class check for Taxons  took 0.13261771202087402s
Consistency | Check Misplaced properties for Taxons  took 3.9482080936431885s
Consistency | Misplaced classes for Taxons  took 0.9543962478637695s
Consistency | Check Ontology hijacking for Taxons  took 5.986040830612183s
Consistency | Check Invalid usage of undefined classes for Taxons  took 1.2124266624450684s
Consistency | Check Invalid usage of undefined properties for Taxons  took 5.678105115890503s
Conciseness | Check Extensional conciseness for Taxons  took 0.2855665683746338s
Conciseness | Check Intensional conciseness for Taxons  took 0.20082592964172363s
Security | Sign check for Taxons  took 1.4354090690612793s
Availability | Check URIs Dereferenciability for Taxons  took 1780.0838634967804s
Completeness | Calculation of interlinking completeness for Taxons  took 1.18764066696167s
Reputation | Calculation of the PageRank for Taxons  took 0.020905017852783203s
Interlinking | Calculation of Degree of Connection for Taxons  took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Taxons  took 8.058547973632812e-05s
Interoperability | Check the re-using of existing vocabs for Taxons  took 2.3126602172851562e-05s
Believability | Calculation of trust value for Taxons  took 8.58306884765625e-06s
INFO | --- Analysis for sandre took 1997.480566740036s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 1.8852739334106445s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0006663799285888672s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.6979637145996094s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.020398378372192383s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 3.24249267578125e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 8.106231689453125e-06s
INFO | --- Analysis for sanskrit-english-lexicon took 8.034547090530396s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 262.59033012390137s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0008137226104736328s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.755650520324707s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.021100997924804688s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 3.695487976074219e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 7.152557373046875e-06s
INFO | --- Analysis for santillana_guide_dataset took 670.3792700767517s
Availability | SPARQL endpoint availability check for SATAR test  took 4.649162292480469e-05s
Availability | VoID file availability check for SATAR test  took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.2720050811767578s
Reputation | Calculation of the PageRank for SATAR test  took 0.020277976989746094s
Interlinking | Calculation of Degree of Connection for SATAR test  took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 3.075599670410156e-05s
Believability | Calculation of trust value for SATAR test  took 8.344650268554688e-06s
INFO | --- Analysis for SATAR_test took 5.1794116497039795s
Availability | SPARQL endpoint availability check for SCBG Data took 23.11458444595337s
Availability | VoID file availability check for SCBG Data took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.7126755714416504s
Reputation | Calculation of the PageRank for SCBG Data took 0.020090341567993164s
Interlinking | Calculation of Degree of Connection for SCBG Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SCBG Data took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 8.368492126464844e-05s
Believability | Calculation of trust value for SCBG Data took 7.152557373046875e-06s
INFO | --- Analysis for SCBG-Data took 56.1029589176178s
Availability | SPARQL endpoint availability check for schema.org took 5.173683166503906e-05s
Availability | VoID file availability check for schema.org took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for schema.org took 0.2695786952972412s
Reputation | Calculation of the PageRank for schema.org took 0.020195484161376953s
Interlinking | Calculation of Degree of Connection for schema.org took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for schema.org took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for schema.org took 3.24249267578125e-05s
Believability | Calculation of trust value for schema.org took 7.3909759521484375e-06s
INFO | --- Analysis for schema-org took 4.8062825202941895s
Availability | SPARQL endpoint availability check for Schemantra took 4.220008850097656e-05s
Availability | VoID file availability check for Schemantra took 0.00022411346435546875s
Completeness | Calculation of interlinking completeness for Schemantra took 0.7198920249938965s
Reputation | Calculation of the PageRank for Schemantra took 0.020168542861938477s
Interlinking | Calculation of Degree of Connection for Schemantra took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Schemantra took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Schemantra took 2.9325485229492188e-05s
Believability | Calculation of trust value for Schemantra took 7.3909759521484375e-06s
INFO | --- Analysis for Schemantra took 2.9206037521362305s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 2.085569381713867s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.29712486267089844s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.019947052001953125s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.147125244140625e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 7.867813110351562e-06s
INFO | --- Analysis for schemapedia took 5.00150990486145s
Availability | SPARQL endpoint availability check for scholarlydata took 3.9577484130859375e-05s
Availability | VoID file availability check for scholarlydata took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for scholarlydata took 0.2539827823638916s
Reputation | Calculation of the PageRank for scholarlydata took 0.02020716667175293s
Interlinking | Calculation of Degree of Connection for scholarlydata took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for scholarlydata took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for scholarlydata took 2.7894973754882812e-05s
Believability | Calculation of trust value for scholarlydata took 7.3909759521484375e-06s
INFO | --- Analysis for scholarlydata took 2.8956778049468994s
Availability | SPARQL endpoint availability check for Scholarometer took 4.1961669921875e-05s
Availability | VoID file availability check for Scholarometer took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.2679924964904785s
Reputation | Calculation of the PageRank for Scholarometer took 0.02051687240600586s
Interlinking | Calculation of Degree of Connection for Scholarometer took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 8.630752563476562e-05s
Believability | Calculation of trust value for Scholarometer took 7.3909759521484375e-06s
INFO | --- Analysis for scholarometer took 7.076438665390015s
Availability | SPARQL endpoint availability check for Science Commons took 5.221366882324219e-05s
Availability | VoID file availability check for Science Commons took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Science Commons took 0.24673819541931152s
Reputation | Calculation of the PageRank for Science Commons took 0.02014923095703125s
Interlinking | Calculation of Degree of Connection for Science Commons took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Science Commons took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Science Commons took 2.7894973754882812e-05s
Believability | Calculation of trust value for Science Commons took 7.867813110351562e-06s
INFO | --- Analysis for science_commons took 2.9481897354125977s
Availability | SPARQL endpoint availability check for ScienceWise took 4.1961669921875e-05s
Availability | VoID file availability check for ScienceWise took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for ScienceWise took 0.27965426445007324s
Reputation | Calculation of the PageRank for ScienceWise took 0.020242929458618164s
Interlinking | Calculation of Degree of Connection for ScienceWise took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ScienceWise took 0.0008196830749511719s
Interlinking | Calculation of Clustering coefficient for ScienceWise took 3.0279159545898438e-05s
Believability | Calculation of trust value for ScienceWise took 1.2159347534179688e-05s
INFO | --- Analysis for sciencewise took 3.083310604095459s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 4.291534423828125e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.281604528427124s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.0204775333404541s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 2.9087066650390625e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 4.291534423828125e-06s
INFO | --- Analysis for scoreboard took 4.753449201583862s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 4.172325134277344e-05s
Availability | VoID file availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007824897766113281s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.27597498893737793s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.020387649536132812s
Interlinking | Calculation of Degree of Connection for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 3.361701965332031e-05s
Believability | Calculation of trust value for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 7.62939453125e-06s
INFO | --- Analysis for SDDEC took 16.906320095062256s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 4.172325134277344e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.25875139236450195s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.020475387573242188s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 2.8133392333984375e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 7.62939453125e-06s
INFO | --- Analysis for SDG took 3.2441494464874268s
Availability | SPARQL endpoint availability check for sears.com took 4.2438507080078125e-05s
Availability | VoID file availability check for sears.com took 0.0006783008575439453s
Completeness | Calculation of interlinking completeness for sears.com took 0.26434993743896484s
Reputation | Calculation of the PageRank for sears.com took 0.020794153213500977s
Interlinking | Calculation of Degree of Connection for sears.com took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for sears.com took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for sears.com took 7.152557373046875e-05s
Believability | Calculation of trust value for sears.com took 7.867813110351562e-06s
INFO | --- Analysis for sears took 4.317232847213745s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.09990715980529785s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.27717065811157227s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.020097732543945312s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 7.796287536621094e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 5.9604644775390625e-06s
INFO | --- Analysis for sec-rdfabout took 6.5519750118255615s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.667038917541504s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0008299350738525391s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.7124347686767578s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.02042531967163086s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 8.296966552734375e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 1.0728836059570312e-05s
INFO | --- Analysis for secold took 168.2304584980011s
Availability | SPARQL endpoint availability check for SEEK-AT-WD ICT tools for education - Web-Share took 4.00543212890625e-05s
Availability | VoID file availability check for SEEK-AT-WD ICT tools for education - Web-Share took 0.00022101402282714844s
Completeness | Calculation of interlinking completeness for SEEK-AT-WD ICT tools for education - Web-Share took 0.2725963592529297s
Reputation | Calculation of the PageRank for SEEK-AT-WD ICT tools for education - Web-Share took 0.02015995979309082s
Interlinking | Calculation of Degree of Connection for SEEK-AT-WD ICT tools for education - Web-Share took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SEEK-AT-WD ICT tools for education - Web-Share took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for SEEK-AT-WD ICT tools for education - Web-Share took 2.9087066650390625e-05s
Believability | Calculation of trust value for SEEK-AT-WD ICT tools for education - Web-Share took 7.152557373046875e-06s
INFO | --- Analysis for seek-at-wd-ict-tools-for-education-web-share took 3.9263689517974854s
Availability | SPARQL endpoint availability check for semanlink took 4.1961669921875e-05s
Availability | VoID file availability check for semanlink took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for semanlink took 0.2398204803466797s
Reputation | Calculation of the PageRank for semanlink took 0.02024078369140625s
Interlinking | Calculation of Degree of Connection for semanlink took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for semanlink took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.0001621246337890625s
Believability | Calculation of trust value for semanlink took 6.9141387939453125e-06s
INFO | --- Analysis for semanlink took 13.439055919647217s
Availability | SPARQL endpoint availability check for Semantic Library took 4.744529724121094e-05s
Availability | VoID file availability check for Semantic Library took 0.0002205371856689453s
Completeness | Calculation of interlinking completeness for Semantic Library took 0.23953676223754883s
Reputation | Calculation of the PageRank for Semantic Library took 0.020029067993164062s
Interlinking | Calculation of Degree of Connection for Semantic Library took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Semantic Library took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Semantic Library took 2.8133392333984375e-05s
Believability | Calculation of trust value for Semantic Library took 6.9141387939453125e-06s
INFO | --- Analysis for semantic-library took 2.8963170051574707s
Availability | SPARQL endpoint availability check for Semantic Profiling Network took 4.363059997558594e-05s
Availability | VoID file availability check for Semantic Profiling Network took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for Semantic Profiling Network took 0.2572915554046631s
Reputation | Calculation of the PageRank for Semantic Profiling Network took 0.021199464797973633s
Interlinking | Calculation of Degree of Connection for Semantic Profiling Network took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Semantic Profiling Network took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Semantic Profiling Network took 2.7894973754882812e-05s
Believability | Calculation of trust value for Semantic Profiling Network took 7.62939453125e-06s
INFO | --- Analysis for semantic-profiling-network took 2.8449461460113525s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.07557535171508789s
Availability | VoID file availability check for Semantic Universe Data took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.2427051067352295s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.020180225372314453s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 2.765655517578125e-05s
Believability | Calculation of trust value for Semantic Universe Data took 7.867813110351562e-06s
INFO | --- Analysis for semantic-universe took 3.491413116455078s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.467334747314453s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.2796483039855957s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.020306110382080078s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.0001461505889892578s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 6.67572021484375e-06s
INFO | --- Analysis for semantic-web-dog-food took 82.94659805297852s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 4.076957702636719e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0006351470947265625s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.28460144996643066s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.020220279693603516s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.220008850097656e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 6.4373016357421875e-06s
INFO | --- Analysis for semantic-web-grundlagen took 3.112194299697876s
Availability | SPARQL endpoint availability check for semantic-web-journal took 4.00543212890625e-05s
Availability | VoID file availability check for semantic-web-journal took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for semantic-web-journal took 0.2629711627960205s
Reputation | Calculation of the PageRank for semantic-web-journal took 0.020360946655273438s
Interlinking | Calculation of Degree of Connection for semantic-web-journal took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for semantic-web-journal took 0.0009508132934570312s
Interlinking | Calculation of Clustering coefficient for semantic-web-journal took 3.552436828613281e-05s
Believability | Calculation of trust value for semantic-web-journal took 6.9141387939453125e-06s
INFO | --- Analysis for semantic-web-journal took 2.892456293106079s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 4.291534423828125e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.3007371425628662s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.020563125610351562s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 8.344650268554688e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 5.7220458984375e-06s
INFO | --- Analysis for semantic-xbrl took 3.388044595718384s
Availability | SPARQL endpoint availability check for Semantic Bible took 4.076957702636719e-05s
Availability | VoID file availability check for Semantic Bible took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for Semantic Bible took 0.26636219024658203s
Reputation | Calculation of the PageRank for Semantic Bible took 0.020741701126098633s
Interlinking | Calculation of Degree of Connection for Semantic Bible took 4.696846008300781e-05s
Interlinking | Calculation of Centrality for Semantic Bible took 0.0009093284606933594s
Interlinking | Calculation of Clustering coefficient for Semantic Bible took 3.647804260253906e-05s
Believability | Calculation of trust value for Semantic Bible took 8.58306884765625e-06s
INFO | --- Analysis for semantic_bible took 2.886669635772705s
Availability | SPARQL endpoint availability check for SemanticQuran took 7.031177282333374s
Availability | VoID file availability check for SemanticQuran took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for SemanticQuran took 0.28109216690063477s
Reputation | Calculation of the PageRank for SemanticQuran took 0.020374059677124023s
Interlinking | Calculation of Degree of Connection for SemanticQuran took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for SemanticQuran took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for SemanticQuran took 7.128715515136719e-05s
Believability | Calculation of trust value for SemanticQuran took 9.059906005859375e-06s
INFO | --- Analysis for semanticquran took 16.09572720527649s
Availability | SPARQL endpoint availability check for SemanticTweet took 4.267692565917969e-05s
Availability | VoID file availability check for SemanticTweet took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.2968902587890625s
Reputation | Calculation of the PageRank for SemanticTweet took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.3882598876953125e-05s
Believability | Calculation of trust value for SemanticTweet took 7.3909759521484375e-06s
INFO | --- Analysis for semantictweet took 2.563878297805786s
Availability | SPARQL endpoint availability check for semanticweb.org took 4.601478576660156e-05s
Availability | VoID file availability check for semanticweb.org took 0.0008020401000976562s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.2927584648132324s
Reputation | Calculation of the PageRank for semanticweb.org took 0.02060222625732422s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 7.891654968261719e-05s
Believability | Calculation of trust value for semanticweb.org took 8.344650268554688e-06s
INFO | --- Analysis for semanticweb-org took 22.83214282989502s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.0889739990234375s
Availability | VoID file availability check for Semantic CrunchBase took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.2658703327178955s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.020559072494506836s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 7.414817810058594e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 7.152557373046875e-06s
INFO | --- Analysis for semsol-crunchbase took 2.4825644493103027s
Availability | SPARQL endpoint availability check for Sensores de IntelliDomo took 4.172325134277344e-05s
Availability | VoID file availability check for Sensores de IntelliDomo took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Sensores de IntelliDomo took 0.2501358985900879s
Reputation | Calculation of the PageRank for Sensores de IntelliDomo took 0.020406723022460938s
Interlinking | Calculation of Degree of Connection for Sensores de IntelliDomo took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Sensores de IntelliDomo took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Sensores de IntelliDomo took 3.0279159545898438e-05s
Believability | Calculation of trust value for Sensores de IntelliDomo took 8.344650268554688e-06s
INFO | --- Analysis for sensores-de-intellidomo took 2.885572671890259s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.27437376976013184s
Availability | VoID file availability check for SentimentWortschatz took 0.0003879070281982422s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.2837989330291748s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.02041006088256836s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.124641418457031e-05s
Believability | Calculation of trust value for SentimentWortschatz took 7.62939453125e-06s
INFO | --- Analysis for sentiws took 3.635897636413574s
Availability | SPARQL endpoint availability check for seoul-bike-data took 30.182018995285034s
Availability | VoID file availability check for seoul-bike-data took 0.0007030963897705078s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.2697865962982178s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.02086925506591797s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 2.9325485229492188e-05s
Believability | Calculation of trust value for seoul-bike-data took 7.3909759521484375e-06s
INFO | --- Analysis for seoul-bike-data took 72.75180125236511s
Availability | SPARQL endpoint availability check for Serendipity took 8.401919603347778s
Availability | VoID file availability check for Serendipity took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for Serendipity took 0.2979004383087158s
Reputation | Calculation of the PageRank for Serendipity took 0.02053093910217285s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Serendipity took 7.581710815429688e-05s
Believability | Calculation of trust value for Serendipity took 7.62939453125e-06s
INFO | --- Analysis for serendipity took 16.629334926605225s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 4.124641418457031e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.24759721755981445s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.020491600036621094s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 3.24249267578125e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 7.62939453125e-06s
INFO | --- Analysis for Sherry_Wine took 2.535709857940674s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.1961669921875e-05s
Availability | VoID file availability check for Sherry Wine took 0.00022840499877929688s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.26621437072753906s
Reputation | Calculation of the PageRank for Sherry Wine took 0.020307064056396484s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 2.956390380859375e-05s
Believability | Calculation of trust value for Sherry Wine took 6.9141387939453125e-06s
INFO | --- Analysis for Sherry_Wine_ took 2.3300724029541016s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.3768138885498047s
Availability | VoID file availability check for Shoah victims? names took 0.0004787445068359375s
Extra | Recovery of all triples for Shoah victims? names took 1.2855026721954346s
Performance | Total latancy measurement for Shoah victims? names took 0.5951576232910156s
Amount of data | Number of triples check for Shoah victims? names took 1.4393641948699951s
Interoperability | New terms check for Shoah victims? names took 1.6521618366241455s
Versatility | Languages check for Shoah victims? names took 6.139457941055298s
Interpretability | Number of blank nodes check for Shoah victims? names took 2.359652042388916s
Security | Check HTTPS for Shoah victims? names took 0.5486917495727539s
Interpretability | RDF structures check for Shoah victims? names took 0.39955973625183105s
Versatility | Serialization formats check for Shoah victims? names took 0.3459205627441406s
Availability | RDF dump link check for Shoah victims? names took 0.18297839164733887s
License | MR license check for Shoah victims? names took 0.4299163818359375s
License | HR license check for Shoah victims? names took 8.565099716186523s
Amount of data | Number of property check for Shoah victims? names took 0.19580435752868652s
Understandability | Number of label check for Shoah victims? names took 0.8883378505706787s
Understandability | URI regex check for Shoah victims? names took 0.5826766490936279s
Understandability | Vocabs check for Shoah victims? names took 0.1912529468536377s
Verifiability | Authors check for Shoah victims? names took 0.2175586223602295s
Verifiability | Publishers check for Shoah victims? names took 0.2533118724822998s
Performance | Throughput check for Shoah victims? names took 10.435157775878906s
Amount of data | Check the number of entities for Shoah victims? names took 0.00010561943054199219s
Verifiability | Contribs. check for Shoah victims? names took 0.3001680374145508s
Interlinking | sameAs chians check for Shoah victims? names took 0.21700215339660645s
Interlinking | skos check for Shoah victims? names took 0.2600078582763672s
Interlinking | skos check for Shoah victims? names took 0.06336236000061035s
Timeliness | dataset update frequency check for Shoah victims? names took 0.23493266105651855s
Currency | Creation date check for Shoah victims? names took 0.18077707290649414s
Currency | Modification date check for Shoah victims? names took 0.3551342487335205s
Rep.Conc. | URIs length for Shoah victims? names took 2.7043609619140625s
Interoperability | New vocabularies check for Shoah victims? names took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.17230534553527832s
Accuracy | Check Functional Property for Shoah victims? names took 0.17044329643249512s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.07182931900024414s
Accuracy | Check Empty annotation labels for Shoah victims? names took 1.1007306575775146s
Accuracy | Check White space in annotation for Shoah victims? names took 0.02852797508239746s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.027556180953979492s
Consistency | Disjoint class check for Shoah victims? names took 0.21393847465515137s
Consistency | Check Misplaced properties for Shoah victims? names took 2.072794198989868s
Consistency | Misplaced classes for Shoah victims? names took 0.22339916229248047s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.5443072319030762s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.15985107421875s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.0328400135040283s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.030572175979614258s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.2915952205657959s
Security | Sign check for Shoah victims? names took 0.7018241882324219s
Availability | Check URIs Dereferenciability for Shoah victims? names took 1159.7790625095367s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 1.3795008659362793s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 4.649162292480469e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 3.337860107421875e-06s
Believability | Calculation of trust value for Shoah victims? names took 7.867813110351562e-06s
INFO | --- Analysis for shoah-victims-names took 1271.6576826572418s
Availability | SPARQL endpoint availability check for Person took 4.267692565917969e-05s
Availability | VoID file availability check for Person took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Person took 0.28263401985168457s
Reputation | Calculation of the PageRank for Person took 0.020435571670532227s
Interlinking | Calculation of Degree of Connection for Person took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Person took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Person took 3.0040740966796875e-05s
Believability | Calculation of trust value for Person took 7.152557373046875e-06s
INFO | --- Analysis for Shripriya_Dubey took 2.8373448848724365s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 6.0558319091796875e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.0003190040588378906s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.27335691452026367s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.02018141746520996s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 2.8133392333984375e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 6.67572021484375e-06s
INFO | --- Analysis for Shutterstock took 3.6854684352874756s
Availability | SPARQL endpoint availability check for SIMILE Data Collection took 4.0531158447265625e-05s
Availability | VoID file availability check for SIMILE Data Collection took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for SIMILE Data Collection took 0.2802915573120117s
Reputation | Calculation of the PageRank for SIMILE Data Collection took 0.022156953811645508s
Interlinking | Calculation of Degree of Connection for SIMILE Data Collection took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SIMILE Data Collection took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for SIMILE Data Collection took 3.1948089599609375e-05s
Believability | Calculation of trust value for SIMILE Data Collection took 6.4373016357421875e-06s
INFO | --- Analysis for simile_data_collection took 2.991109848022461s
Availability | SPARQL endpoint availability check for SIMPLE took 4.2438507080078125e-05s
Availability | VoID file availability check for SIMPLE took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.26175832748413086s
Reputation | Calculation of the PageRank for SIMPLE took 0.020578384399414062s
Interlinking | Calculation of Degree of Connection for SIMPLE took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 4.00543212890625e-05s
Believability | Calculation of trust value for SIMPLE took 6.67572021484375e-06s
INFO | --- Analysis for simple took 7.821529150009155s
Availability | SPARQL endpoint availability check for SITC-V4 took 28.179784536361694s
Availability | VoID file availability check for SITC-V4 took 0.0008471012115478516s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.2719602584838867s
Reputation | Calculation of the PageRank for SITC-V4 took 0.020448684692382812s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 4.5299530029296875e-05s
Believability | Calculation of trust value for SITC-V4 took 5.4836273193359375e-06s
INFO | --- Analysis for sitc-v4 took 128.20623016357422s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.315376281738281e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.26234960556030273s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.020186901092529297s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.315376281738281e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 7.62939453125e-06s
INFO | --- Analysis for sli_galnet_rdf took 12.589312553405762s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.220008850097656e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.2659282684326172s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.020476102828979492s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.218650817871094e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 1.1920928955078125e-05s
INFO | --- Analysis for slideshare2rdf took 2.3953652381896973s
Availability | SPARQL endpoint availability check for Slidewiki (RDF/SPARQL) took 4.4345855712890625e-05s
Availability | VoID file availability check for Slidewiki (RDF/SPARQL) took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Slidewiki (RDF/SPARQL) took 0.28351640701293945s
Reputation | Calculation of the PageRank for Slidewiki (RDF/SPARQL) took 0.020656824111938477s
Interlinking | Calculation of Degree of Connection for Slidewiki (RDF/SPARQL) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Slidewiki (RDF/SPARQL) took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Slidewiki (RDF/SPARQL) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Slidewiki (RDF/SPARQL) took 7.152557373046875e-06s
INFO | --- Analysis for slidewiki-rdf-sparql took 2.918288230895996s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.826209545135498s
Availability | VoID file availability check for Linked Stage Graph took 0.0003421306610107422s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.26722192764282227s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.02000260353088379s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 5.054473876953125e-05s
Believability | Calculation of trust value for Linked Stage Graph took 8.821487426757812e-06s
INFO | --- Analysis for slod took 4.292320728302002s
Availability | SPARQL endpoint availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 4.267692565917969e-05s
Availability | VoID file availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.25615811347961426s
Reputation | Calculation of the PageRank for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.02068924903869629s
Interlinking | Calculation of Degree of Connection for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 3.266334533691406e-05s
Believability | Calculation of trust value for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 7.152557373046875e-06s
INFO | --- Analysis for slovn-k-cpv-2008---common-procurement-vocabulary-2008 took 2.9331674575805664s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 0.8345515727996826s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.00025653839111328125s
Extra | Recovery of all triples for Smart Points Of Interest @PSNC took 101.93942189216614s
Performance | Total latancy measurement for Smart Points Of Interest @PSNC took 0.9427192211151123s
Amount of data | Number of triples check for Smart Points Of Interest @PSNC took 8.688206195831299s
Interoperability | New terms check for Smart Points Of Interest @PSNC took 13.444154739379883s
Versatility | Languages check for Smart Points Of Interest @PSNC took 300.2248122692108s
Interpretability | Number of blank nodes check for Smart Points Of Interest @PSNC took 2.9549427032470703s
Interpretability | RDF structures check for Smart Points Of Interest @PSNC took 0.2610640525817871s
Versatility | Serialization formats check for Smart Points Of Interest @PSNC took 7.580020427703857s
Availability | RDF dump link check for Smart Points Of Interest @PSNC took 0.27708983421325684s
License | MR license check for Smart Points Of Interest @PSNC took 0.5412547588348389s
License | HR license check for Smart Points Of Interest @PSNC took 300.1726574897766s
Amount of data | Number of property check for Smart Points Of Interest @PSNC took 0.3314332962036133s
Understandability | Number of label check for Smart Points Of Interest @PSNC took 2.2829768657684326s
Understandability | URI regex check for Smart Points Of Interest @PSNC took 0.5708763599395752s
Understandability | Vocabs check for Smart Points Of Interest @PSNC took 0.2727537155151367s
Verifiability | Authors check for Smart Points Of Interest @PSNC took 0.20154070854187012s
Verifiability | Publishers check for Smart Points Of Interest @PSNC took 0.25572872161865234s
Performance | Throughput check for Smart Points Of Interest @PSNC took 11.235970735549927s
Amount of data | Check the number of entities for Smart Points Of Interest @PSNC took 9.489059448242188e-05s
Verifiability | Contribs. check for Smart Points Of Interest @PSNC took 0.19559979438781738s
Interlinking | sameAs chians check for Smart Points Of Interest @PSNC took 0.1799020767211914s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.44414281845092773s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.4412095546722412s
Timeliness | dataset update frequency check for Smart Points Of Interest @PSNC took 4.972973108291626s
Currency | Creation date check for Smart Points Of Interest @PSNC took 0.47089672088623047s
Currency | Modification date check for Smart Points Of Interest @PSNC took 0.22118878364562988s
Rep.Conc. | URIs length for Smart Points Of Interest @PSNC took 146.4899537563324s
Interoperability | New vocabularies check for Smart Points Of Interest @PSNC took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Smart Points Of Interest @PSNC took 0.19159936904907227s
Accuracy | Check Functional Property for Smart Points Of Interest @PSNC took 0.345505952835083s
Accuracy | Check Inverse Functional Property for Smart Points Of Interest @PSNC took 0.3145267963409424s
Accuracy | Check Empty annotation labels for Smart Points Of Interest @PSNC took 34.5760715007782s
Accuracy | Check White space in annotation for Smart Points Of Interest @PSNC took 2.642244815826416s
Accuracy | Check Datatype consistency for Smart Points Of Interest @PSNC took 2.730245351791382s
Consistency | Disjoint class check for Smart Points Of Interest @PSNC took 0.20540165901184082s
Consistency | Check Misplaced properties for Smart Points Of Interest @PSNC took 80.60874104499817s
Consistency | Misplaced classes for Smart Points Of Interest @PSNC took 8.405299186706543s
Consistency | Check Ontology hijacking for Smart Points Of Interest @PSNC took 29.726014614105225s
Consistency | Check Invalid usage of undefined classes for Smart Points Of Interest @PSNC took 1.249826431274414s
Consistency | Check Invalid usage of undefined properties for Smart Points Of Interest @PSNC took 83.46496939659119s
Conciseness | Check Extensional conciseness for Smart Points Of Interest @PSNC took 2.7281928062438965s
Conciseness | Check Intensional conciseness for Smart Points Of Interest @PSNC took 0.5451300144195557s
Security | Sign check for Smart Points Of Interest @PSNC took 0.5182499885559082s
Availability | Check URIs Dereferenciability for Smart Points Of Interest @PSNC took 10.074833154678345s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 0.6175174713134766s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.02109384536743164s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0010068416595458984s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 0.00012564659118652344s
Interoperability | Check the re-using of existing vocabs for Smart Points Of Interest @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for Smart_POI_dataset took 2214.9358921051025s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 5.738760232925415s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0007650852203369141s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.26018333435058594s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.020537376403808594s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 4.315376281738281e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 8.58306884765625e-06s
INFO | --- Analysis for smartlink took 15.220299482345581s
Availability | SPARQL endpoint availability check for SNIK took 0.4088473320007324s
Availability | VoID file availability check for SNIK took 0.0007479190826416016s
Extra | Recovery of all triples for SNIK took 2.6737496852874756s
Performance | Total latancy measurement for SNIK took 1.0242276191711426s
Amount of data | Number of triples check for SNIK took 0.20938658714294434s
Interoperability | New terms check for SNIK took 1.3986525535583496s
Versatility | Languages check for SNIK took 0.22153925895690918s
Interpretability | Number of blank nodes check for SNIK took 0.19749069213867188s
Interpretability | RDF structures check for SNIK took 0.20254111289978027s
Versatility | Serialization formats check for SNIK took 0.20023274421691895s
Availability | RDF dump link check for SNIK took 0.19751501083374023s
License | MR license check for SNIK took 0.18785953521728516s
License | HR license check for SNIK took 0.22668766975402832s
Amount of data | Number of property check for SNIK took 0.21083927154541016s
Understandability | Number of label check for SNIK took 0.20365047454833984s
Understandability | URI regex check for SNIK took 0.4155464172363281s
Understandability | Vocabs check for SNIK took 0.19188785552978516s
Verifiability | Authors check for SNIK took 0.1875932216644287s
Verifiability | Publishers check for SNIK took 0.19863557815551758s
Performance | Throughput check for SNIK took 11.78067684173584s
Amount of data | Check the number of entities for SNIK took 7.200241088867188e-05s
Verifiability | Contribs. check for SNIK took 0.19705963134765625s
Interlinking | sameAs chians check for SNIK took 0.19827961921691895s
Interlinking | skos check for SNIK took 0.19261622428894043s
Interlinking | skos check for SNIK took 0.19770264625549316s
Timeliness | dataset update frequency check for SNIK took 0.2107095718383789s
Currency | Creation date check for SNIK took 0.38384461402893066s
Currency | Modification date check for SNIK took 0.3945930004119873s
Rep.Conc. | URIs length for SNIK took 1.3141708374023438s
Interoperability | New vocabularies check for SNIK took 4.76837158203125e-06s
Consistency | Deprecated classes/propertiers check for SNIK took 0.18441057205200195s
Accuracy | Check Functional Property for SNIK took 0.20114803314208984s
Accuracy | Check Inverse Functional Property for SNIK took 0.1914961338043213s
Accuracy | Check Empty annotation labels for SNIK took 0.6202576160430908s
Accuracy | Check White space in annotation for SNIK took 0.02688002586364746s
Accuracy | Check Datatype consistency for SNIK took 0.2156691551208496s
Consistency | Disjoint class check for SNIK took 0.1972355842590332s
Consistency | Check Misplaced properties for SNIK took 0.6784417629241943s
Consistency | Misplaced classes for SNIK took 0.7067832946777344s
Consistency | Check Ontology hijacking for SNIK took 1.7155051231384277s
Consistency | Check Invalid usage of undefined classes for SNIK took 1.1859512329101562s
Consistency | Check Invalid usage of undefined properties for SNIK took 1.4720935821533203s
Conciseness | Check Extensional conciseness for SNIK took 0.1507408618927002s
Conciseness | Check Intensional conciseness for SNIK took 0.3097043037414551s
Security | Sign check for SNIK took 0.1987912654876709s
Availability | Check URIs Dereferenciability for SNIK took 816.4108920097351s
Completeness | Calculation of interlinking completeness for SNIK took 1.2912418842315674s
Reputation | Calculation of the PageRank for SNIK took 0.020781517028808594s
Interlinking | Calculation of Degree of Connection for SNIK took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SNIK took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for SNIK took 8.7738037109375e-05s
Interoperability | Check the re-using of existing vocabs for SNIK took 1.430511474609375e-06s
Believability | Calculation of trust value for SNIK took 7.3909759521484375e-06s
INFO | --- Analysis for snik took 870.1428821086884s
Availability | SPARQL endpoint availability check for Social Networks and Archival Context Fall 2011 took 4.2438507080078125e-05s
Availability | VoID file availability check for Social Networks and Archival Context Fall 2011 took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Social Networks and Archival Context Fall 2011 took 0.2555370330810547s
Reputation | Calculation of the PageRank for Social Networks and Archival Context Fall 2011 took 0.020050525665283203s
Interlinking | Calculation of Degree of Connection for Social Networks and Archival Context Fall 2011 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Social Networks and Archival Context Fall 2011 took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Social Networks and Archival Context Fall 2011 took 2.9802322387695312e-05s
Believability | Calculation of trust value for Social Networks and Archival Context Fall 2011 took 6.9141387939453125e-06s
INFO | --- Analysis for social-networks-and-archival-context-fall-2011 took 3.9170150756835938s
Availability | SPARQL endpoint availability check for SocialLink took 1.5615646839141846s
Availability | VoID file availability check for SocialLink took 0.0008661746978759766s
Completeness | Calculation of interlinking completeness for SocialLink took 0.25376200675964355s
Reputation | Calculation of the PageRank for SocialLink took 0.021506309509277344s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for SocialLink took 9.465217590332031e-05s
Believability | Calculation of trust value for SocialLink took 7.62939453125e-06s
INFO | --- Analysis for SocialLink took 6.883525848388672s
Availability | SPARQL endpoint availability check for SocialLink took 4.124641418457031e-05s
Availability | VoID file availability check for SocialLink took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for SocialLink took 0.2619025707244873s
Reputation | Calculation of the PageRank for SocialLink took 0.02021503448486328s
Interlinking | Calculation of Degree of Connection for SocialLink took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for SocialLink took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for SocialLink took 2.6941299438476562e-05s
Believability | Calculation of trust value for SocialLink took 7.3909759521484375e-06s
INFO | --- Analysis for sociallink took 2.8439905643463135s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 4.172325134277344e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0007262229919433594s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.2661905288696289s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.020737648010253906s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0008034706115722656s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 3.0279159545898438e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 6.198883056640625e-06s
INFO | --- Analysis for SocialRoles took 11.093338966369629s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.29936957359313965s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0007486343383789062s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 15.196599960327148s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.49635791778564453s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.2735905647277832s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.4107859134674072s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.418698787689209s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.2210092544555664s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.29023313522338867s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.11540460586547852s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.1069638729095459s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.8260347843170166s
License | MR license check for Social Semantic Web Thesaurus took 0.11394238471984863s
License | HR license check for Social Semantic Web Thesaurus took 0.10523414611816406s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.12072587013244629s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.11782193183898926s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.17450308799743652s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.13959145545959473s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.13026714324951172s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.11499810218811035s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.592603206634521s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 4.1484832763671875e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.11962413787841797s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.12394142150878906s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.11482715606689453s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.09593439102172852s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.10268425941467285s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.21099424362182617s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.24097156524658203s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 1.6760246753692627s
Interoperability | New vocabularies check for Social Semantic Web Thesaurus took 1.0747053623199463s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.12218213081359863s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.09856772422790527s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.09529685974121094s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.47231292724609375s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.012172222137451172s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.0984959602355957s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.31732749938964844s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.07861948013305664s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.01700496673584s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.3460907936096191s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.00014519691467285156s
Security | Sign check for Social Semantic Web Thesaurus took 0.08551740646362305s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 115.98131656646729s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.25974225997924805s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.020307540893554688s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0006844997406005859s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 0.00010442733764648438s
Interoperability | Check the re-using of existing vocabs for Social Semantic Web Thesaurus took 0.7159929275512695s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for socialsemweb-thesaurus took 227.92404699325562s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2746891975402832s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0002753734588623047s
Extra | Recovery of all triples for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 103.69744420051575s
Performance | Total latancy measurement for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.9592125415802002s
Amount of data | Number of triples check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 7.952784538269043s
Interoperability | New terms check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 14.861955165863037s
Versatility | Languages check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.2085566520691s
Interpretability | Number of blank nodes check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.0519566535949707s
Interpretability | RDF structures check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.24634408950805664s
Versatility | Serialization formats check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.776864290237427s
Availability | RDF dump link check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2573525905609131s
License | MR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.45366382598876953s
License | HR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.1551821231842s
Amount of data | Number of property check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4301156997680664s
Understandability | Number of label check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.4068963527679443s
Understandability | URI regex check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5907497406005859s
Understandability | Vocabs check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.36495065689086914s
Verifiability | Authors check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.21066617965698242s
Verifiability | Publishers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.26803112030029297s
Performance | Throughput check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 11.429595947265625s
Amount of data | Check the number of entities for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 7.2479248046875e-05s
Verifiability | Contribs. check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19015765190124512s
Interlinking | sameAs chians check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.20763421058654785s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.44100475311279297s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4434196949005127s
Timeliness | dataset update frequency check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.3562376499176025s
Currency | Creation date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.48718762397766113s
Currency | Modification date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2169036865234375s
Rep.Conc. | URIs length for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 149.3709819316864s
Interoperability | New vocabularies check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19632291793823242s
Accuracy | Check Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.34136462211608887s
Accuracy | Check Inverse Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.323270320892334s
Accuracy | Check Empty annotation labels for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 35.45549774169922s
Accuracy | Check White space in annotation for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.6478586196899414s
Accuracy | Check Datatype consistency for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.589097023010254s
Consistency | Disjoint class check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.1918039321899414s
Consistency | Check Misplaced properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 83.81309103965759s
Consistency | Misplaced classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.25875186920166s
Consistency | Check Ontology hijacking for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 28.904934644699097s
Consistency | Check Invalid usage of undefined classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.2278149127960205s
Consistency | Check Invalid usage of undefined properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 83.28875041007996s
Conciseness | Check Extensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.7556750774383545s
Conciseness | Check Intensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5041182041168213s
Security | Sign check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5115189552307129s
Availability | Check URIs Dereferenciability for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 10.551384210586548s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.5232768058776855s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.021304607391357422s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0009987354278564453s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.5299530029296875e-05s
Interoperability | Check the re-using of existing vocabs for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.86102294921875e-06s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.3113021850585938e-05s
INFO | --- Analysis for Soil_maps took 2217.087565422058s
Availability | SPARQL endpoint availability check for terrorrist ontology took 5.7697296142578125e-05s
Availability | VoID file availability check for terrorrist ontology took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.27214503288269043s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.020219087600708008s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 2.86102294921875e-05s
Believability | Calculation of trust value for terrorrist ontology took 6.4373016357421875e-06s
INFO | --- Analysis for somya_omer took 3.7857940196990967s
Availability | SPARQL endpoint availability check for Sonclubcx took 4.291534423828125e-05s
Availability | VoID file availability check for Sonclubcx took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.294816255569458s
Reputation | Calculation of the PageRank for Sonclubcx took 0.02041339874267578s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0008995532989501953s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.1920928955078125e-05s
Believability | Calculation of trust value for Sonclubcx took 7.152557373046875e-06s
INFO | --- Analysis for sonclubcx took 4.395395994186401s
Availability | SPARQL endpoint availability check for SORS took 4.291534423828125e-05s
Availability | VoID file availability check for SORS took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for SORS took 0.26184630393981934s
Reputation | Calculation of the PageRank for SORS took 0.02045297622680664s
Interlinking | Calculation of Degree of Connection for SORS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SORS took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for SORS took 5.030632019042969e-05s
Believability | Calculation of trust value for SORS took 5.245208740234375e-06s
INFO | --- Analysis for sors took 12.902019023895264s
Availability | SPARQL endpoint availability check for Soudy České republiky took 4.172325134277344e-05s
Availability | VoID file availability check for Soudy České republiky took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Soudy České republiky took 0.25502896308898926s
Reputation | Calculation of the PageRank for Soudy České republiky took 0.02023148536682129s
Interlinking | Calculation of Degree of Connection for Soudy České republiky took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Soudy České republiky took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Soudy České republiky took 2.86102294921875e-05s
Believability | Calculation of trust value for Soudy České republiky took 7.3909759521484375e-06s
INFO | --- Analysis for soudy--esk--republiky took 2.786057949066162s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 4.315376281738281e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.00038433074951171875s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.24904274940490723s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.02027153968811035s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 9.083747863769531e-05s
Believability | Calculation of trust value for southampton-ac-uk took 7.152557373046875e-06s
INFO | --- Analysis for southampton-ac-uk took 3.608070135116577s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 3.231025457382202s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.25739455223083496s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.02041792869567871s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 6.67572021484375e-06s
INFO | --- Analysis for southampton-ac-uk-apps took 10.835042953491211s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 4.220008850097656e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.2527937889099121s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.020348072052001953s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.059906005859375e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 6.9141387939453125e-06s
INFO | --- Analysis for southampton-ecs-eprints took 4.2645182609558105s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.5666697025299072s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.00025582313537597656s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 162.93044424057007s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.257328748703003s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 2.2331697940826416s
Interoperability | New terms check for Spanish Linguistic Datasets took 2.842693328857422s
Versatility | Languages check for Spanish Linguistic Datasets took 44.407062292099s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 1.2141425609588623s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.1228325366973877s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.28923916816711426s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 0.29724764823913574s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.2981851100921631s
License | MR license check for Spanish Linguistic Datasets took 0.27652668952941895s
License | HR license check for Spanish Linguistic Datasets took 0.40570688247680664s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.2843763828277588s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.34558963775634766s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.569568395614624s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.28479528427124023s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.28977012634277344s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.273700475692749s
Performance | Throughput check for Spanish Linguistic Datasets took 11.227622509002686s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 9.584426879882812e-05s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.28807830810546875s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.27767467498779297s
Interlinking | skos check for Spanish Linguistic Datasets took 0.2707536220550537s
Interlinking | skos check for Spanish Linguistic Datasets took 0.22264814376831055s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.3157505989074707s
Currency | Creation date check for Spanish Linguistic Datasets took 0.5740151405334473s
Currency | Modification date check for Spanish Linguistic Datasets took 0.5745785236358643s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 61.3984637260437s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.2860071659088135s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.2723820209503174s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 0.27109384536743164s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 0.9074704647064209s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.009967803955078125s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.6902194023132324s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.2754802703857422s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.727703809738159s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.462998628616333s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 46.866461753845215s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.3862888813018799s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 5.653342247009277s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 2.883934736251831s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.3091471195220947s
Security | Sign check for Spanish Linguistic Datasets took 0.2844681739807129s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 11.920916318893433s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.5040581226348877s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.02053380012512207s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.0517578125e-05s
Interoperability | Check the re-using of existing vocabs for Spanish Linguistic Datasets took 1.430511474609375e-06s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 7.3909759521484375e-06s
INFO | --- Analysis for spanish-linguistic-datasets took 419.3646948337555s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.06905150413513184s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.29423999786376953s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.020540952682495117s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.696846008300781e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 1.3589859008789062e-05s
INFO | --- Analysis for sparql-endpoint-status took 2.472817897796631s
Availability | SPARQL endpoint availability check for SPC publikovaná SÚKL took 7.724761962890625e-05s
Availability | VoID file availability check for SPC publikovaná SÚKL took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for SPC publikovaná SÚKL took 0.2497882843017578s
Reputation | Calculation of the PageRank for SPC publikovaná SÚKL took 0.020087003707885742s
Interlinking | Calculation of Degree of Connection for SPC publikovaná SÚKL took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for SPC publikovaná SÚKL took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for SPC publikovaná SÚKL took 2.765655517578125e-05s
Believability | Calculation of trust value for SPC publikovaná SÚKL took 8.106231689453125e-06s
INFO | --- Analysis for spc-publikovan--s-kl took 3.4342405796051025s
Availability | SPARQL endpoint availability check for SPQR took 4.100799560546875e-05s
Availability | VoID file availability check for SPQR took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for SPQR took 0.24001216888427734s
Reputation | Calculation of the PageRank for SPQR took 0.020091533660888672s
Interlinking | Calculation of Degree of Connection for SPQR took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for SPQR took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for SPQR took 2.765655517578125e-05s
Believability | Calculation of trust value for SPQR took 8.106231689453125e-06s
INFO | --- Analysis for spqr took 2.860215425491333s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 4.1961669921875e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.2799830436706543s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.01996135711669922s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 8.130073547363281e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 7.3909759521484375e-06s
INFO | --- Analysis for springernaturescigraph took 3.4263854026794434s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.1484832763671875e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.27668070793151855s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.020108461380004883s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 2.6941299438476562e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 7.62939453125e-06s
INFO | --- Analysis for srcmf took 7.9350361824035645s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 0.8572139739990234s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.26540398597717285s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.020220041275024414s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 5.078315734863281e-05s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 7.152557373046875e-06s
INFO | --- Analysis for ssf took 4.127054214477539s
Availability | SPARQL endpoint availability check for SSF took 4.0531158447265625e-05s
Availability | VoID file availability check for SSF took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for SSF took 0.26425695419311523s
Reputation | Calculation of the PageRank for SSF took 0.020201683044433594s
Interlinking | Calculation of Degree of Connection for SSF took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for SSF took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for SSF took 2.7894973754882812e-05s
Believability | Calculation of trust value for SSF took 7.3909759521484375e-06s
INFO | --- Analysis for ssf-lexicon took 2.9756524562835693s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 4.363059997558594e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0013117790222167969s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.2773609161376953s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.02043938636779785s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.647804260253906e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 5.9604644775390625e-06s
INFO | --- Analysis for st-andrews-resource-lists took 2.742090940475464s
Availability | SPARQL endpoint availability check for STAC took 4.00543212890625e-05s
Availability | VoID file availability check for STAC took 0.0003306865692138672s
Completeness | Calculation of interlinking completeness for STAC took 0.27579379081726074s
Reputation | Calculation of the PageRank for STAC took 0.020537614822387695s
Interlinking | Calculation of Degree of Connection for STAC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for STAC took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for STAC took 3.075599670410156e-05s
Believability | Calculation of trust value for STAC took 7.62939453125e-06s
INFO | --- Analysis for stac took 2.9833037853240967s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for The Scottish Government took 5.125999450683594e-05s
Availability | VoID file availability check for Organogram and staff pay data for The Scottish Government took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for The Scottish Government took 0.2780883312225342s
Reputation | Calculation of the PageRank for Organogram and staff pay data for The Scottish Government took 0.02009105682373047s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for The Scottish Government took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Organogram and staff pay data for The Scottish Government took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for The Scottish Government took 2.6941299438476562e-05s
Believability | Calculation of trust value for Organogram and staff pay data for The Scottish Government took 8.106231689453125e-06s
INFO | --- Analysis for staff-organograms-and-pay-scottish-government took 2.9324936866760254s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.220008850097656e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.24349093437194824s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.020023107528686523s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.075599670410156e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 5.4836273193359375e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 4.11818528175354s
Availability | SPARQL endpoint availability check for Stammbuch took 4.172325134277344e-05s
Availability | VoID file availability check for Stammbuch took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.28748035430908203s
Reputation | Calculation of the PageRank for Stammbuch took 0.020102739334106445s
Interlinking | Calculation of Degree of Connection for Stammbuch took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Stammbuch took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 2.8848648071289062e-05s
Believability | Calculation of trust value for Stammbuch took 6.4373016357421875e-06s
INFO | --- Analysis for Stammbuch took 2.4211461544036865s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.243870735168457s
Availability | VoID file availability check for statistics.data.gov.uk took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.2505502700805664s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.020278453826904297s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.0001010894775390625s
Believability | Calculation of trust value for statistics.data.gov.uk took 4.76837158203125e-06s
INFO | --- Analysis for statistics-data-gov-uk took 3.8209502696990967s
Availability | SPARQL endpoint availability check for Statistics on Fatal Traffic Accidents in greek roads took 4.100799560546875e-05s
Availability | VoID file availability check for Statistics on Fatal Traffic Accidents in greek roads took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Statistics on Fatal Traffic Accidents in greek roads took 0.27389049530029297s
Reputation | Calculation of the PageRank for Statistics on Fatal Traffic Accidents in greek roads took 0.02032470703125s
Interlinking | Calculation of Degree of Connection for Statistics on Fatal Traffic Accidents in greek roads took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Statistics on Fatal Traffic Accidents in greek roads took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Statistics on Fatal Traffic Accidents in greek roads took 2.7418136596679688e-05s
Believability | Calculation of trust value for Statistics on Fatal Traffic Accidents in greek roads took 7.62939453125e-06s
INFO | --- Analysis for statistics-on-fatal-traffic-accidents-in-greek-roads took 2.8007538318634033s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.2689061164855957s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.02049875259399414s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00012135505676269531s
Believability | Calculation of trust value for statusnet-1w6-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-1w6-org took 2.9433794021606445s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 4.673004150390625e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.27211475372314453s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.020280122756958008s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 5.984306335449219e-05s
Believability | Calculation of trust value for statusnet-20100-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-20100-org took 2.418901205062866s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.00042748451232910156s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.2558894157409668s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.020204782485961914s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 6.628036499023438e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-alexandrefranke-com took 2.765625238418579s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0003066062927246094s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.26552724838256836s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.020053863525390625s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 7.724761962890625e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.505924701690674s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0007250308990478516s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.24275779724121094s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.020427465438842773s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 8.96453857421875e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-belfalas-org took 2.538867473602295s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0008721351623535156s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.2797524929046631s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00011491775512695312s
Believability | Calculation of trust value for statusnet-bka-li took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-bka-li took 183.84581446647644s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.7175540924072266s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.02044677734375s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 3.8623809814453125e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 7.62939453125e-06s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.7219083309173584s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.2686007022857666s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.020778179168701172s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 5.14984130859375e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-ced117-net took 4.062154054641724s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.26255178451538086s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 5.173683166503906e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.5925722122192383s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.277878999710083s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.020300626754760742s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00010943412780761719s
Believability | Calculation of trust value for statusnet-chromic-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-chromic-org took 3.132114887237549s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 6.0558319091796875e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.253436803817749s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.01999378204345703s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 7.891654968261719e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-cooleysekula-net took 6.012739181518555s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.29885244369506836s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.020228862762451172s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.459785461425781e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-coreyavis-com took 2.5633938312530518s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 5.316734313964844e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.2952549457550049s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.020122766494750977s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 6.365776062011719e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.217400550842285s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.25496459007263184s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.020752668380737305s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 9.584426879882812e-05s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.5484797954559326s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.001252889633178711s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.25363945960998535s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.01995682716369629s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 5.888938903808594e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.4742250442504883s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.2654738426208496s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.02018117904663086s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 4.863739013671875e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-doomicile-de took 3.308844566345215s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.24619054794311523s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.0202639102935791s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 6.628036499023438e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-dtdns-net took 22.396830797195435s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 5.6743621826171875e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.28751635551452637s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.020224332809448242s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.4809112548828125e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-equestriarp-net took 2.3912439346313477s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 4.696846008300781e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0006544589996337891s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.25701284408569336s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.02025294303894043s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.343292236328125e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-exdc-net took 12.51861310005188s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0008502006530761719s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.2934136390686035s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.020163774490356445s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.036064147949219e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-fcac-com took 22.419344902038574s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.25327134132385254s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.020424604415893555s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.3882598876953125e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-fcestrada-com took 3.0743086338043213s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.26526594161987305s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.020241975784301758s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.00018835067749023438s
Believability | Calculation of trust value for statusnet-fragdev-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-fragdev-com took 3.2457754611968994s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.2554032802581787s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.02018427848815918s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.390975952148438e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-freelish-us took 2.402641534805298s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.29425740242004395s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.020351886749267578s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00010466575622558594s
Believability | Calculation of trust value for statusnet-gegeweb-org took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-gegeweb-org took 2.6065666675567627s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.2774012088775635s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.02045917510986328s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 6.961822509765625e-05s
Believability | Calculation of trust value for statusnet-glou-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-glou-org took 2.529740333557129s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.2807745933532715s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.020391225814819336s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00012159347534179688s
Believability | Calculation of trust value for statusnet-gomertronic-com took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-gomertronic-com took 2.4734222888946533s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 5.7220458984375e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.2689685821533203s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.020363330841064453s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00010275840759277344s
Believability | Calculation of trust value for statusnet-hackerposse-com took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-hackerposse-com took 3.0220093727111816s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.2384941577911377s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.02033543586730957s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 4.982948303222656e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-hii-co-il took 3.7457470893859863s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.29157423973083496s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.02064037322998047s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 9.226799011230469e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 3.4354896545410156s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.27983546257019043s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.020403623580932617s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 6.461143493652344e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-imirhil-fr took 2.58542799949646s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.2585408687591553s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.02033519744873047s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 3.933906555175781e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-integralblue-com took 2.569455146789551s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 8.20159912109375e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.2798726558685303s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.020268678665161133s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 6.031990051269531e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.37555456161499s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0008437633514404297s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.26297688484191895s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.02058100700378418s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007979869842529297s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00011968612670898438s
Believability | Calculation of trust value for statusnet-jonkman-ca took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-jonkman-ca took 3.4043991565704346s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 5.9604644775390625e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0005466938018798828s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.25539374351501465s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.020081281661987305s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.012222290039062e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-kaimi-cc took 2.480032444000244s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.27060413360595703s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.020287275314331055s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 5.054473876953125e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-kathryl-fr took 2.460550546646118s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.2922554016113281s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.020101308822631836s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 3.743171691894531e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-kenzoid-com took 3.2939202785491943s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.2836446762084961s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.020148754119873047s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 6.914138793945312e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-keuser-fr took 2.3591537475585938s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.2558562755584717s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.020160198211669922s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 4.553794860839844e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.4870429039001465s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.27029871940612793s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.020258426666259766s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 8.392333984375e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-lebsanft-org took 2.534376621246338s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.27068543434143066s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.020385265350341797s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0009093284606933594s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 0.00010371208190917969s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.5759079456329346s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.2686493396759033s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.020148277282714844s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011587142944335938s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.409815788269043s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.2458934783935547s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.020334959030151367s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.53131103515625e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-ludost-net took 3.712161064147949s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.2665426731109619s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.020305633544921875s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 9.965896606445312e-05s
Believability | Calculation of trust value for statusnet-lydiastench-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-lydiastench-com took 2.386223554611206s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.27902674674987793s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.021503925323486328s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.316734313964844e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.4342875480651855s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.2636377811431885s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.020231246948242188s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.00014853477478027344s
Believability | Calculation of trust value for statusnet-macno-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-macno-org took 2.403150796890259s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0014541149139404297s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.25132250785827637s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.02018117904663086s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.413459777832031e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 3.0657432079315186s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0006682872772216797s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.2811703681945801s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.020186424255371094s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 7.939338684082031e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-maymay-net took 42.07214903831482s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0003905296325683594s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.24985027313232422s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.020324230194091797s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.00015735626220703125s
Believability | Calculation of trust value for statusnet-morphtown-de took 7.62939453125e-06s
INFO | --- Analysis for statusnet-morphtown-de took 2.3886260986328125s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.2817046642303467s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.020470857620239258s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 9.894371032714844e-05s
Believability | Calculation of trust value for statusnet-mrblog-nl took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-mrblog-nl took 2.518707752227783s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 5.841255187988281e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.0002243518829345703s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.24243974685668945s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.02019524574279785s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.340576171875e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-mulestable-net took 2.302273750305176s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.2702915668487549s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.020210981369018555s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.221366882324219e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 7.62939453125e-06s
INFO | --- Analysis for statusnet-my-status-tk took 2.6036229133605957s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.26175856590270996s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.020189285278320312s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00010538101196289062s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.4760613441467285s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.2677321434020996s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.020130634307861328s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007958412170410156s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 0.0001201629638671875s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.6352896690368652s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.0003592967987060547s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.25284600257873535s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.020264863967895508s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.127357482910156e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-otbm-fr took 2.5015878677368164s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.28098344802856445s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.020453929901123047s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.368492126464844e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.829033136367798s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 0.00010323524475097656s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.2722458839416504s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.021889925003051758s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0008509159088134766s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 5.5789947509765625e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-panda-id-au took 3.463677406311035s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 5.793571472167969e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0004343986511230469s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.2637627124786377s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.020104646682739258s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.775161743164062e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 7.62939453125e-06s
INFO | --- Analysis for statusnet-piana-eu took 2.4256715774536133s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 6.461143493652344e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.2561674118041992s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.020343542098999023s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.390975952148438e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-planet-libre-org took 2.462660551071167s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.26268434524536133s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.02063608169555664s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007998943328857422s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.0002288818359375s
Believability | Calculation of trust value for statusnet-postblue-info took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-postblue-info took 2.460780382156372s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.26204872131347656s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.020563602447509766s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 6.771087646484375e-05s
Believability | Calculation of trust value for statusnet-progval-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-progval-net took 2.547569513320923s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 5.2928924560546875e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.25801968574523926s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.02082037925720215s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00011444091796875s
Believability | Calculation of trust value for statusnet-qdnx-org took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-qdnx-org took 2.870305299758911s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0005605220794677734s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.28743886947631836s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.021377086639404297s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.723403930664062e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-qth-fr took 3.2539045810699463s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.26213622093200684s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.021151304244995117s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0009300708770751953s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.0002923011779785156s
Believability | Calculation of trust value for statusnet-quitter-se took 7.62939453125e-06s
INFO | --- Analysis for statusnet-quitter-se took 2.4968457221984863s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.27192187309265137s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.01998281478881836s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.000102996826171875s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.727673053741455s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0006289482116699219s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.2601308822631836s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.650520324707031e-05s
Believability | Calculation of trust value for statusnet-recit-org took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-recit-org took 4.557015657424927s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.30017733573913574s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.00014472007751464844s
Believability | Calculation of trust value for statusnet-russwurm-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-russwurm-org took 3.2303569316864014s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.26137661933898926s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.020701885223388672s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.225440979003906e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-samnoble-org took 4.878055095672607s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.24226880073547363s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.02042222023010254s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.273124694824219e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-schiessle-org took 2.663867950439453s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 0.0005061626434326172s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.2833256721496582s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.020465612411499023s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 9.608268737792969e-05s
Believability | Calculation of trust value for statusnet-scoffoni-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-scoffoni-net took 2.4869909286499023s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.2555208206176758s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.508827209472656e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-sebseb01-net took 2.5254180431365967s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 4.7206878662109375e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.2802281379699707s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.020947933197021484s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0008156299591064453s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 8.440017700195312e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-shnoulle-net took 3.3378331661224365s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 5.030632019042969e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.2831127643585205s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.020767927169799805s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00021195411682128906s
Believability | Calculation of trust value for statusnet-skilledtests-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-skilledtests-com took 2.898808717727661s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 4.7206878662109375e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.2595386505126953s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.022385120391845703s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00010967254638671875s
Believability | Calculation of trust value for statusnet-somsants-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-somsants-net took 2.410099983215332s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.76837158203125e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.2559030055999756s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.02076435089111328s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.00013399124145507812s
Believability | Calculation of trust value for statusnet-soucy-cc took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-soucy-cc took 2.3403022289276123s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0003223419189453125s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.25965428352355957s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.02047252655029297s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 6.818771362304688e-05s
Believability | Calculation of trust value for statusnet-spip-org took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-spip-org took 3.397120952606201s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.2807457447052002s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.020933151245117188s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.723403930664062e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-spraci-org took 2.482600450515747s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.2965106964111328s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.020783424377441406s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00014162063598632812s
Believability | Calculation of trust value for statusnet-ssweeny-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-ssweeny-net took 5.399106502532959s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.24446749687194824s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.02050018310546875s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00022721290588378906s
Believability | Calculation of trust value for statusnet-status-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-status-net took 3.426992416381836s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.2716505527496338s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.020305395126342773s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.555152893066406e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.409475564956665s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.24460220336914062s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.020186185836791992s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 8.821487426757812e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.469820976257324s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.26416635513305664s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.020945072174072266s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0009691715240478516s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.0001418590545654297s
Believability | Calculation of trust value for statusnet-thelovebug-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-thelovebug-org took 2.419163227081299s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0012068748474121094s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.2739996910095215s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.020386934280395508s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0008018016815185547s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 8.440017700195312e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-thornton2-com took 5.0059075355529785s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.2701597213745117s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.020076990127563477s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0008497238159179688s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00010418891906738281s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.9706075191497803s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.27186012268066406s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.023117542266845703s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.00099945068359375s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 4.601478576660156e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-tl1n-com took 3.529080629348755s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.2659800052642822s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.02023768424987793s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.556510925292969e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 7.62939453125e-06s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.644540309906006s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0005922317504882812s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.24898624420166016s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.02047133445739746s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 3.504753112792969e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-uni-siegen-de took 2.5029103755950928s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 4.291534423828125e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.00035858154296875s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.2653694152832031s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.021918296813964844s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 3.147125244140625e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for steak took 3.6988558769226074s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 4.172325134277344e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.272716760635376s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.020865678787231445s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.221366882324219e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 7.3909759521484375e-06s
INFO | --- Analysis for stitch-rameau took 4.191356182098389s
Availability | SPARQL endpoint availability check for Stone Tech Square took 0.6394410133361816s
Availability | VoID file availability check for Stone Tech Square took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.2678194046020508s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.020227909088134766s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.1682510375976562e-05s
Believability | Calculation of trust value for Stone Tech Square took 6.9141387939453125e-06s
INFO | --- Analysis for stone-tech-square-data took 4.705265283584595s
Availability | SPARQL endpoint availability check for Strukturované popisy z FDA took 4.315376281738281e-05s
Availability | VoID file availability check for Strukturované popisy z FDA took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Strukturované popisy z FDA took 0.25095653533935547s
Reputation | Calculation of the PageRank for Strukturované popisy z FDA took 0.020559310913085938s
Interlinking | Calculation of Degree of Connection for Strukturované popisy z FDA took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Strukturované popisy z FDA took 0.0007915496826171875s
Interlinking | Calculation of Clustering coefficient for Strukturované popisy z FDA took 3.361701965332031e-05s
Believability | Calculation of trust value for Strukturované popisy z FDA took 7.62939453125e-06s
INFO | --- Analysis for strukturovan--popisy-z-fda took 2.9428744316101074s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.45559072494506836s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0004868507385253906s
Extra | Recovery of all triples for STW Thesaurus for Economics took 19.000259399414062s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.11775541305542s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.6196010112762451s
Interoperability | New terms check for STW Thesaurus for Economics took 1.4374349117279053s
Versatility | Languages check for STW Thesaurus for Economics took 1.4480268955230713s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.46877241134643555s
Security | Check HTTPS for STW Thesaurus for Economics took 0.1596062183380127s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.25277161598205566s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.24225902557373047s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.2686126232147217s
License | MR license check for STW Thesaurus for Economics took 0.26400232315063477s
License | HR license check for STW Thesaurus for Economics took 2.2888810634613037s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.24587678909301758s
Understandability | Number of label check for STW Thesaurus for Economics took 0.6796054840087891s
Understandability | URI regex check for STW Thesaurus for Economics took 0.45821619033813477s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.252058744430542s
Verifiability | Authors check for STW Thesaurus for Economics took 0.25960493087768555s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.2303311824798584s
Performance | Throughput check for STW Thesaurus for Economics took 10.991036891937256s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.7073628902435303s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.24260640144348145s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.24744009971618652s
Interlinking | skos check for STW Thesaurus for Economics took 0.34748244285583496s
Interlinking | skos check for STW Thesaurus for Economics took 0.2736015319824219s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.2264106273651123s
Currency | Creation date check for STW Thesaurus for Economics took 0.5061020851135254s
Currency | Modification date check for STW Thesaurus for Economics took 0.5288832187652588s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 7.698663711547852s
Interoperability | New vocabularies check for STW Thesaurus for Economics took 5.944361686706543s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.2561485767364502s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.2708282470703125s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.25600314140319824s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 6.584749937057495s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0405614376068115s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.329352378845215s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.2733495235443115s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.2778818607330322s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 2.233341693878174s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.2378478050231934s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.2140960693359375s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.6559512615203857s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.22957587242126465s
Security | Sign check for STW Thesaurus for Economics took 0.2908453941345215s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 3.0981130599975586s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.26479411125183105s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.02088189125061035s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00011110305786132812s
Interoperability | Check the re-using of existing vocabs for STW Thesaurus for Economics took 5.252671718597412s
Believability | Calculation of trust value for STW Thesaurus for Economics took 7.62939453125e-06s
INFO | --- Analysis for stw-thesaurus-for-economics took 109.5927484035492s
Availability | SPARQL endpoint availability check for SudershanTech took 4.172325134277344e-05s
Availability | VoID file availability check for SudershanTech took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.26471614837646484s
Reputation | Calculation of the PageRank for SudershanTech took 0.02039170265197754s
Interlinking | Calculation of Degree of Connection for SudershanTech took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SudershanTech took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 2.9802322387695312e-05s
Believability | Calculation of trust value for SudershanTech took 7.62939453125e-06s
INFO | --- Analysis for SudershanTech took 2.4334845542907715s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 40.21512818336487s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0007281303405761719s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.26544189453125s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.0203554630279541s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 5.14984130859375e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 7.3909759521484375e-06s
INFO | --- Analysis for sudocfr took 46.174296617507935s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 1.0319969654083252s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0013203620910644531s
Extra | Recovery of all triples for Suface Forestière Mondiale 1990-2016 took 22.192429304122925s
Performance | Total latancy measurement for Suface Forestière Mondiale 1990-2016 took 2.715951442718506s
Amount of data | Number of triples check for Suface Forestière Mondiale 1990-2016 took 1.757753849029541s
Interoperability | New terms check for Suface Forestière Mondiale 1990-2016 took 2.8602476119995117s
Versatility | Languages check for Suface Forestière Mondiale 1990-2016 took 3.3428735733032227s
Interpretability | Number of blank nodes check for Suface Forestière Mondiale 1990-2016 took 1.2779932022094727s
Interpretability | RDF structures check for Suface Forestière Mondiale 1990-2016 took 0.5477175712585449s
Versatility | Serialization formats check for Suface Forestière Mondiale 1990-2016 took 0.523611307144165s
Availability | RDF dump link check for Suface Forestière Mondiale 1990-2016 took 0.5527787208557129s
License | MR license check for Suface Forestière Mondiale 1990-2016 took 1.1231300830841064s
License | HR license check for Suface Forestière Mondiale 1990-2016 took 9.191452026367188s
Amount of data | Number of property check for Suface Forestière Mondiale 1990-2016 took 0.5670404434204102s
Understandability | Number of label check for Suface Forestière Mondiale 1990-2016 took 0.790067195892334s
Understandability | URI regex check for Suface Forestière Mondiale 1990-2016 took 1.105255126953125s
Understandability | Vocabs check for Suface Forestière Mondiale 1990-2016 took 0.5283334255218506s
Verifiability | Authors check for Suface Forestière Mondiale 1990-2016 took 0.5274922847747803s
Verifiability | Publishers check for Suface Forestière Mondiale 1990-2016 took 0.5509843826293945s
Performance | Throughput check for Suface Forestière Mondiale 1990-2016 took 10.993012189865112s
Amount of data | Check the number of entities for Suface Forestière Mondiale 1990-2016 took 7.390975952148438e-05s
Verifiability | Contribs. check for Suface Forestière Mondiale 1990-2016 took 0.5531928539276123s
Interlinking | sameAs chians check for Suface Forestière Mondiale 1990-2016 took 0.6487698554992676s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.6196246147155762s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.6178865432739258s
Timeliness | dataset update frequency check for Suface Forestière Mondiale 1990-2016 took 0.5712308883666992s
Currency | Creation date check for Suface Forestière Mondiale 1990-2016 took 1.0724382400512695s
Currency | Modification date check for Suface Forestière Mondiale 1990-2016 took 1.169527292251587s
Rep.Conc. | URIs length for Suface Forestière Mondiale 1990-2016 took 52.90298867225647s
Interoperability | New vocabularies check for Suface Forestière Mondiale 1990-2016 took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Suface Forestière Mondiale 1990-2016 took 0.5501079559326172s
Accuracy | Check Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5085980892181396s
Accuracy | Check Inverse Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5634210109710693s
Accuracy | Check Empty annotation labels for Suface Forestière Mondiale 1990-2016 took 3.3097784519195557s
Accuracy | Check White space in annotation for Suface Forestière Mondiale 1990-2016 took 0.3770132064819336s
Consistency | Disjoint class check for Suface Forestière Mondiale 1990-2016 took 0.5415565967559814s
Consistency | Check Misplaced properties for Suface Forestière Mondiale 1990-2016 took 35.73845624923706s
Consistency | Misplaced classes for Suface Forestière Mondiale 1990-2016 took 9.434359312057495s
Consistency | Check Ontology hijacking for Suface Forestière Mondiale 1990-2016 took 300.46959829330444s
Consistency | Check Invalid usage of undefined properties for Suface Forestière Mondiale 1990-2016 took 26.048497676849365s
Conciseness | Check Extensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.9643912315368652s
Conciseness | Check Intensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.6298110485076904s
Security | Sign check for Suface Forestière Mondiale 1990-2016 took 0.5522143840789795s
Availability | Check URIs Dereferenciability for Suface Forestière Mondiale 1990-2016 took 4867.963499069214s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 1.5895867347717285s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.020832061767578125s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 8.797645568847656e-05s
Interoperability | Check the re-using of existing vocabs for Suface Forestière Mondiale 1990-2016 took 4.291534423828125e-06s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 7.152557373046875e-06s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 8493.386791706085s
Availability | SPARQL endpoint availability check for Surge Radio took 5.173683166503906e-05s
Availability | VoID file availability check for Surge Radio took 0.0006837844848632812s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.33359766006469727s
Reputation | Calculation of the PageRank for Surge Radio took 0.020321369171142578s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 9.298324584960938e-05s
Believability | Calculation of trust value for Surge Radio took 7.3909759521484375e-06s
INFO | --- Analysis for surge-radio took 5.772733926773071s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 4.267692565917969e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.00070953369140625s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.28218531608581543s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.020278215408325195s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 3.4809112548828125e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 9.775161743164062e-06s
INFO | --- Analysis for SWAT took 78.92603588104248s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 7.43865966796875e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.45203661918640137s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.708202600479126s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.020177125930786133s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 6.890296936035156e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 7.3909759521484375e-06s
INFO | --- Analysis for swedish-open-cultural-heritage took 6.482375621795654s
Availability | SPARQL endpoint availability check for SweFN-RDF took 1.106696367263794s
Availability | VoID file availability check for SweFN-RDF took 0.0006537437438964844s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.2724437713623047s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.020194530487060547s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.4809112548828125e-05s
Believability | Calculation of trust value for SweFN-RDF took 7.867813110351562e-06s
INFO | --- Analysis for swefn-rdf took 6.272174835205078s
Availability | SPARQL endpoint availability check for SwetoDblp took 4.935264587402344e-05s
Availability | VoID file availability check for SwetoDblp took 0.0006215572357177734s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.2557799816131592s
Reputation | Calculation of the PageRank for SwetoDblp took 0.02039504051208496s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.4809112548828125e-05s
Believability | Calculation of trust value for SwetoDblp took 7.62939453125e-06s
INFO | --- Analysis for sweto-dblp took 23.135775327682495s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 0.5495638847351074s
Availability | VoID file availability check for Swift Vocabulary took 0.0005667209625244141s
Extra | Recovery of all triples for Swift Vocabulary took 2.504417896270752s
Performance | Total latancy measurement for Swift Vocabulary took 0.9609754085540771s
Amount of data | Number of triples check for Swift Vocabulary took 0.17264294624328613s
Interoperability | New terms check for Swift Vocabulary took 1.3455758094787598s
Versatility | Languages check for Swift Vocabulary took 0.1684577465057373s
Interpretability | Number of blank nodes check for Swift Vocabulary took 0.15512967109680176s
Interpretability | RDF structures check for Swift Vocabulary took 0.19456124305725098s
Versatility | Serialization formats check for Swift Vocabulary took 0.18508052825927734s
Availability | RDF dump link check for Swift Vocabulary took 0.15949130058288574s
License | MR license check for Swift Vocabulary took 0.17719793319702148s
License | HR license check for Swift Vocabulary took 0.15677380561828613s
Amount of data | Number of property check for Swift Vocabulary took 0.1761326789855957s
Understandability | Number of label check for Swift Vocabulary took 0.16485881805419922s
Understandability | URI regex check for Swift Vocabulary took 0.36249876022338867s
Understandability | Vocabs check for Swift Vocabulary took 0.17284297943115234s
Verifiability | Authors check for Swift Vocabulary took 0.19019079208374023s
Verifiability | Publishers check for Swift Vocabulary took 0.1747889518737793s
Performance | Throughput check for Swift Vocabulary took 10.724971055984497s
Amount of data | Check the number of entities for Swift Vocabulary took 7.653236389160156e-05s
Verifiability | Contribs. check for Swift Vocabulary took 0.1599433422088623s
Interlinking | sameAs chians check for Swift Vocabulary took 0.17407011985778809s
Interlinking | skos check for Swift Vocabulary took 0.17479920387268066s
Interlinking | skos check for Swift Vocabulary took 0.19029855728149414s
Timeliness | dataset update frequency check for Swift Vocabulary took 0.19416260719299316s
Currency | Creation date check for Swift Vocabulary took 0.39144134521484375s
Currency | Modification date check for Swift Vocabulary took 0.3967406749725342s
Rep.Conc. | URIs length for Swift Vocabulary took 0.8350145816802979s
Interoperability | New vocabularies check for Swift Vocabulary took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Swift Vocabulary took 0.18824028968811035s
Accuracy | Check Functional Property for Swift Vocabulary took 0.21054935455322266s
Accuracy | Check Inverse Functional Property for Swift Vocabulary took 0.2124347686767578s
Accuracy | Check Empty annotation labels for Swift Vocabulary took 0.37555670738220215s
Accuracy | Check White space in annotation for Swift Vocabulary took 0.002717733383178711s
Accuracy | Check Datatype consistency for Swift Vocabulary took 0.035660743713378906s
Consistency | Disjoint class check for Swift Vocabulary took 0.19027042388916016s
Consistency | Check Misplaced properties for Swift Vocabulary took 0.44896745681762695s
Consistency | Misplaced classes for Swift Vocabulary took 0.25937676429748535s
Consistency | Check Ontology hijacking for Swift Vocabulary took 1.4331951141357422s
Consistency | Check Invalid usage of undefined classes for Swift Vocabulary took 1.213106632232666s
Consistency | Check Invalid usage of undefined properties for Swift Vocabulary took 1.3621582984924316s
Conciseness | Check Extensional conciseness for Swift Vocabulary took 0.025400161743164062s
Conciseness | Check Intensional conciseness for Swift Vocabulary took 0.19150400161743164s
Security | Sign check for Swift Vocabulary took 0.15595436096191406s
Availability | Check URIs Dereferenciability for Swift Vocabulary took 1021.6102428436279s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.6921508312225342s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 7.605552673339844e-05s
Interoperability | Check the re-using of existing vocabs for Swift Vocabulary took 1.6689300537109375e-06s
Believability | Calculation of trust value for Swift Vocabulary took 7.62939453125e-06s
INFO | --- Analysis for Swift took 1065.8517036437988s
Availability | SPARQL endpoint availability check for SymbolicData took 5.4836273193359375e-05s
Availability | VoID file availability check for SymbolicData took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for SymbolicData took 0.25665926933288574s
Reputation | Calculation of the PageRank for SymbolicData took 0.020461320877075195s
Interlinking | Calculation of Degree of Connection for SymbolicData took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for SymbolicData took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for SymbolicData took 2.7418136596679688e-05s
Believability | Calculation of trust value for SymbolicData took 7.3909759521484375e-06s
INFO | --- Analysis for symbolicdata took 2.875803232192993s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 4.172325134277344e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.00074005126953125s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.25674915313720703s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.020949840545654297s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0010769367218017578s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 3.743171691894531e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 7.62939453125e-06s
INFO | --- Analysis for symptoms-in-chinese took 53.06153059005737s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.7349240779876709s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0006358623504638672s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.5087800025939941s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.9330308437347412s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 51.58977651596069s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 20.266249179840088s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.1867079734802246s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 50.25946354866028s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.12399029731750488s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.6053409576416016s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.3647034168243408s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.19843363761901855s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.4321577548980713s
License | HR license check for National Digital Data Archive of Hungary (partial) took 52.747838735580444s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 4.3839099407196045s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 55.987293004989624s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.725438117980957s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.5969874858856201s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 1.25520658493042s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.17844104766845703s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 14.003120183944702s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 7.224082946777344e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 4.955068349838257s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 7.780008792877197s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.5671112537384033s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.3783395290374756s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.52366042137146s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 2.66947865486145s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 2.490374803543091s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 70.6129424571991s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.22800922393798828s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.29680585861206055s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0020494461059570312s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.0014998912811279297s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.17168331146240234s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 54.40610694885254s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.3047597408294678s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.4905545711517334s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.1955926418304443s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 53.666605710983276s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.0018978118896484375s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.7687952518463135s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.49361252784729004s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 13.330306768417358s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.35500240325927734s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.02022862434387207s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 8.273124694824219e-05s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 7.3909759521484375e-06s
INFO | --- Analysis for sztaki-lod took 622.3515045642853s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 5.602836608886719e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0004248619079589844s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.2725358009338379s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.020482301712036133s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.340576171875e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 7.152557373046875e-06s
INFO | --- Analysis for t4gm-info took 6.98991322517395s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.267692565917969e-05s
Availability | VoID file availability check for tags2con delicious took 0.0003840923309326172s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.8243811130523682s
Reputation | Calculation of the PageRank for tags2con delicious took 0.020679712295532227s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 5.841255187988281e-05s
Believability | Calculation of trust value for tags2con delicious took 6.67572021484375e-06s
INFO | --- Analysis for tags2con-delicious took 845.9660732746124s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 264.3961515426636s
Availability | VoID file availability check for Taiwan geographic names took 0.0007200241088867188s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 1.2295234203338623s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.020545244216918945s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 5.555152893066406e-05s
Believability | Calculation of trust value for Taiwan geographic names took 8.344650268554688e-06s
INFO | --- Analysis for taiwan-geographic-names took 670.8297383785248s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 4.601478576660156e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0003490447998046875s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.2680630683898926s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.02033686637878418s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007927417755126953s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 9.560585021972656e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 7.867813110351562e-06s
INFO | --- Analysis for talis-openlibrary took 6.545409917831421s
Availability | SPARQL endpoint availability check for TalkBank took 3.9577484130859375e-05s
Availability | VoID file availability check for TalkBank took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for TalkBank took 0.684110164642334s
Reputation | Calculation of the PageRank for TalkBank took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for TalkBank took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for TalkBank took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for TalkBank took 2.9802322387695312e-05s
Believability | Calculation of trust value for TalkBank took 7.3909759521484375e-06s
INFO | --- Analysis for talkbank took 3.7046754360198975s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 0.9285247325897217s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.258223295211792s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.020373821258544922s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.0001227855682373047s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 7.152557373046875e-06s
INFO | --- Analysis for taxonconcept took 14.357545614242554s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 4.315376281738281e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.2950279712677002s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.020464420318603516s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 8.225440979003906e-05s
Believability | Calculation of trust value for taxonconcept-assets took 7.62939453125e-06s
INFO | --- Analysis for taxonconcept-assets took 2.9503352642059326s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 4.267692565917969e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.2563762664794922s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.020355939865112305s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 5.078315734863281e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 1.239776611328125e-05s
INFO | --- Analysis for taxonconcept-occurences took 2.762922525405884s
Availability | SPARQL endpoint availability check for TAXREF-LD: Linked Data French Taxonomic Register took 1.3432426452636719s
Availability | VoID file availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.0007584095001220703s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Linked Data French Taxonomic Register took 0.25695157051086426s
Reputation | Calculation of the PageRank for TAXREF-LD: Linked Data French Taxonomic Register took 0.020374059677124023s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Linked Data French Taxonomic Register took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TAXREF-LD: Linked Data French Taxonomic Register took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Linked Data French Taxonomic Register took 4.9114227294921875e-05s
Believability | Calculation of trust value for TAXREF-LD: Linked Data French Taxonomic Register took 7.3909759521484375e-06s
INFO | --- Analysis for taxref-ld took 7.185154914855957s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 262.7757177352905s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.2861959934234619s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.02037334442138672s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 3.0279159545898438e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 6.9141387939453125e-06s
INFO | --- Analysis for tcga took 541.1961169242859s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.3729236125946045s
Availability | VoID file availability check for TCGA Roadmap took 0.0004215240478515625s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.6824209690093994s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 7.82012939453125e-05s
Believability | Calculation of trust value for TCGA Roadmap took 7.867813110351562e-06s
INFO | --- Analysis for tcga-roadmap took 7.1311094760894775s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 1.7038688659667969s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.00036835670471191406s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.26981139183044434s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.02032303810119629s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00010514259338378906s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 6.67572021484375e-06s
INFO | --- Analysis for tcmgenedit_dataset took 140.81423950195312s
Availability | SPARQL endpoint availability check for TDS took 4.267692565917969e-05s
Availability | VoID file availability check for TDS took 0.0007219314575195312s
Completeness | Calculation of interlinking completeness for TDS took 0.287825345993042s
Reputation | Calculation of the PageRank for TDS took 0.02025771141052246s
Interlinking | Calculation of Degree of Connection for TDS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for TDS took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for TDS took 3.790855407714844e-05s
Believability | Calculation of trust value for TDS took 7.3909759521484375e-06s
INFO | --- Analysis for tds took 4.671545505523682s
Availability | SPARQL endpoint availability check for TED Talks took 4.291534423828125e-05s
Availability | VoID file availability check for TED Talks took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for TED Talks took 0.2599306106567383s
Reputation | Calculation of the PageRank for TED Talks took 0.02042078971862793s
Interlinking | Calculation of Degree of Connection for TED Talks took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TED Talks took 0.0008141994476318359s
Interlinking | Calculation of Clustering coefficient for TED Talks took 3.314018249511719e-05s
Believability | Calculation of trust value for TED Talks took 7.62939453125e-06s
INFO | --- Analysis for ted-talks took 3.425459146499634s
Availability | SPARQL endpoint availability check for TEKORD took 5.412101745605469e-05s
Availability | VoID file availability check for TEKORD took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for TEKORD took 0.27214646339416504s
Reputation | Calculation of the PageRank for TEKORD took 0.02030158042907715s
Interlinking | Calculation of Degree of Connection for TEKORD took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for TEKORD took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.887580871582031e-05s
Believability | Calculation of trust value for TEKORD took 1.1444091796875e-05s
INFO | --- Analysis for tekord took 5.218034267425537s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 1.7734663486480713s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0003478527069091797s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.2598388195037842s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.02039337158203125s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00010728836059570312s
Believability | Calculation of trust value for Telegraphis Linked Data took 4.5299530029296875e-06s
INFO | --- Analysis for telegraphis took 7.612225770950317s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 4.315376281738281e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.00036978721618652344s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.26444315910339355s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.020372629165649414s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 7.510185241699219e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 7.62939453125e-06s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 14.014869451522827s
Availability | SPARQL endpoint availability check for TERENCE Reading Comprehension Dataset took 4.076957702636719e-05s
Availability | VoID file availability check for TERENCE Reading Comprehension Dataset took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for TERENCE Reading Comprehension Dataset took 0.2644176483154297s
Reputation | Calculation of the PageRank for TERENCE Reading Comprehension Dataset took 0.020447492599487305s
Interlinking | Calculation of Degree of Connection for TERENCE Reading Comprehension Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for TERENCE Reading Comprehension Dataset took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for TERENCE Reading Comprehension Dataset took 3.0994415283203125e-05s
Believability | Calculation of trust value for TERENCE Reading Comprehension Dataset took 7.62939453125e-06s
INFO | --- Analysis for terence-reading-comprehension-dataset took 2.9465177059173584s
Availability | SPARQL endpoint availability check for Terminesp Linked Data took 5.3882598876953125e-05s
Availability | VoID file availability check for Terminesp Linked Data took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Terminesp Linked Data took 0.2555887699127197s
Reputation | Calculation of the PageRank for Terminesp Linked Data took 0.020835161209106445s
Interlinking | Calculation of Degree of Connection for Terminesp Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Terminesp Linked Data took 0.0008473396301269531s
Interlinking | Calculation of Clustering coefficient for Terminesp Linked Data took 3.1948089599609375e-05s
Believability | Calculation of trust value for Terminesp Linked Data took 7.62939453125e-06s
INFO | --- Analysis for terminesp took 2.8726232051849365s
Availability | SPARQL endpoint availability check for Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology took 0.0008766651153564453s
Completeness | Calculation of interlinking completeness for Ontology took 0.2608833312988281s
Reputation | Calculation of the PageRank for Ontology took 0.020383596420288086s
Interlinking | Calculation of Degree of Connection for Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Ontology took 2.7894973754882812e-05s
Believability | Calculation of trust value for Ontology took 6.67572021484375e-06s
INFO | --- Analysis for Terrorist_attack took 3.0422933101654053s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 4.3392181396484375e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.26807379722595215s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.0201876163482666s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 2.86102294921875e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 6.67572021484375e-06s
INFO | --- Analysis for Terrorist_Attack_1 took 2.375896692276001s
Availability | SPARQL endpoint availability check for Tesauro materias BUPM took 4.410743713378906e-05s
Availability | VoID file availability check for Tesauro materias BUPM took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Tesauro materias BUPM took 0.24119997024536133s
Reputation | Calculation of the PageRank for Tesauro materias BUPM took 0.020487070083618164s
Interlinking | Calculation of Degree of Connection for Tesauro materias BUPM took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Tesauro materias BUPM took 0.0009322166442871094s
Interlinking | Calculation of Clustering coefficient for Tesauro materias BUPM took 3.0279159545898438e-05s
Believability | Calculation of trust value for Tesauro materias BUPM took 7.867813110351562e-06s
INFO | --- Analysis for tesauro-materias-bupm took 2.823796033859253s
Availability | SPARQL endpoint availability check for Teseo took 4.172325134277344e-05s
Availability | VoID file availability check for Teseo took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Teseo took 0.25439023971557617s
Reputation | Calculation of the PageRank for Teseo took 0.020259857177734375s
Interlinking | Calculation of Degree of Connection for Teseo took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Teseo took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Teseo took 2.956390380859375e-05s
Believability | Calculation of trust value for Teseo took 7.62939453125e-06s
INFO | --- Analysis for teseo took 2.9443094730377197s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 4.291534423828125e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007014274597167969s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.2788267135620117s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.020385026931762695s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 2.9325485229492188e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 7.3909759521484375e-06s
INFO | --- Analysis for Tesla_Deaths took 3.974926233291626s
Availability | SPARQL endpoint availability check for test took 4.291534423828125e-05s
Availability | VoID file availability check for test took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for test took 0.27970242500305176s
Reputation | Calculation of the PageRank for test took 0.020728111267089844s
Interlinking | Calculation of Degree of Connection for test took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for test took 0.0008914470672607422s
Interlinking | Calculation of Clustering coefficient for test took 3.409385681152344e-05s
Believability | Calculation of trust value for test took 6.67572021484375e-06s
INFO | --- Analysis for test took 2.458451747894287s
Availability | SPARQL endpoint availability check for Test took 4.220008850097656e-05s
Availability | VoID file availability check for Test took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Test took 0.3194117546081543s
Reputation | Calculation of the PageRank for Test took 0.021866321563720703s
Interlinking | Calculation of Degree of Connection for Test took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Test took 0.0008575916290283203s
Interlinking | Calculation of Clustering coefficient for Test took 3.1948089599609375e-05s
Believability | Calculation of trust value for Test took 7.62939453125e-06s
INFO | --- Analysis for Test took 2.4660158157348633s
Availability | SPARQL endpoint availability check for test-svu took 20.18816614151001s
Availability | VoID file availability check for test-svu took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for test-svu took 0.25672459602355957s
Reputation | Calculation of the PageRank for test-svu took 0.020656108856201172s
Interlinking | Calculation of Degree of Connection for test-svu took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for test-svu took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for test-svu took 2.9325485229492188e-05s
Believability | Calculation of trust value for test-svu took 7.3909759521484375e-06s
INFO | --- Analysis for test-svu took 52.61592507362366s
Availability | SPARQL endpoint availability check for Test took 4.3392181396484375e-05s
Availability | VoID file availability check for Test took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for Test took 0.2759087085723877s
Reputation | Calculation of the PageRank for Test took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for Test took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Test took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Test took 3.218650817871094e-05s
Believability | Calculation of trust value for Test took 7.3909759521484375e-06s
INFO | --- Analysis for Test_ took 2.5054125785827637s
Availability | SPARQL endpoint availability check for xxxxx took 261.3686845302582s
Availability | VoID file availability check for xxxxx took 0.0008904933929443359s
Completeness | Calculation of interlinking completeness for xxxxx took 0.8211963176727295s
Reputation | Calculation of the PageRank for xxxxx took 0.021036863327026367s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for xxxxx took 5.817413330078125e-05s
Believability | Calculation of trust value for xxxxx took 7.867813110351562e-06s
INFO | --- Analysis for testee took 798.4789414405823s
Availability | SPARQL endpoint availability check for Texai Lexicon took 4.124641418457031e-05s
Availability | VoID file availability check for Texai Lexicon took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Texai Lexicon took 0.6900022029876709s
Reputation | Calculation of the PageRank for Texai Lexicon took 0.02099442481994629s
Interlinking | Calculation of Degree of Connection for Texai Lexicon took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Texai Lexicon took 0.0009567737579345703s
Interlinking | Calculation of Clustering coefficient for Texai Lexicon took 3.24249267578125e-05s
Believability | Calculation of trust value for Texai Lexicon took 7.152557373046875e-06s
INFO | --- Analysis for texai_lexicon took 5.043316841125488s
Availability | SPARQL endpoint availability check for tharawat magazine took 4.124641418457031e-05s
Availability | VoID file availability check for tharawat magazine took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.2939434051513672s
Reputation | Calculation of the PageRank for tharawat magazine took 0.020209789276123047s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00010395050048828125s
Believability | Calculation of trust value for tharawat magazine took 6.67572021484375e-06s
INFO | --- Analysis for tharawat-magazine-com took 4.363962650299072s
Availability | SPARQL endpoint availability check for The CIARD RING took 4.029273986816406e-05s
Availability | VoID file availability check for The CIARD RING took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for The CIARD RING took 0.23783159255981445s
Reputation | Calculation of the PageRank for The CIARD RING took 0.02059459686279297s
Interlinking | Calculation of Degree of Connection for The CIARD RING took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The CIARD RING took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for The CIARD RING took 3.0994415283203125e-05s
Believability | Calculation of trust value for The CIARD RING took 7.62939453125e-06s
INFO | --- Analysis for the-ciard-ring took 3.3077802658081055s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 0.1809828281402588s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0006670951843261719s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.255908727645874s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.020319700241088867s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 3.0279159545898438e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 7.867813110351562e-06s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 3.5177814960479736s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 0.9223959445953369s
Availability | VoID file availability check for The European Library Open Dataset took 0.0006823539733886719s
Extra | Recovery of all triples for The European Library Open Dataset took 1.1360151767730713s
Performance | Total latancy measurement for The European Library Open Dataset took 1.294912576675415s
Amount of data | Number of triples check for The European Library Open Dataset took 30.205880165100098s
Versatility | Languages check for The European Library Open Dataset took 0.3636763095855713s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 30.21659231185913s
Interpretability | RDF structures check for The European Library Open Dataset took 0.26378369331359863s
Versatility | Serialization formats check for The European Library Open Dataset took 0.288236141204834s
Availability | RDF dump link check for The European Library Open Dataset took 0.23981308937072754s
License | MR license check for The European Library Open Dataset took 1.8535540103912354s
License | HR license check for The European Library Open Dataset took 0.24849987030029297s
Amount of data | Number of property check for The European Library Open Dataset took 0.2182908058166504s
Understandability | Number of label check for The European Library Open Dataset took 2.2754058837890625s
Understandability | URI regex check for The European Library Open Dataset took 0.5631065368652344s
Understandability | Vocabs check for The European Library Open Dataset took 0.23152661323547363s
Verifiability | Authors check for The European Library Open Dataset took 0.2651245594024658s
Verifiability | Publishers check for The European Library Open Dataset took 0.2875051498413086s
Performance | Throughput check for The European Library Open Dataset took 11.174985885620117s
Amount of data | Check the number of entities for The European Library Open Dataset took 8.225440979003906e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 0.23603200912475586s
Interlinking | sameAs chians check for The European Library Open Dataset took 0.3297004699707031s
Interlinking | skos check for The European Library Open Dataset took 0.395571231842041s
Interlinking | skos check for The European Library Open Dataset took 0.36061692237854004s
Timeliness | dataset update frequency check for The European Library Open Dataset took 0.29105544090270996s
Currency | Creation date check for The European Library Open Dataset took 0.4833545684814453s
Currency | Modification date check for The European Library Open Dataset took 1.5479919910430908s
Rep.Conc. | URIs length for The European Library Open Dataset took 60.478665590286255s
Interoperability | New vocabularies check for The European Library Open Dataset took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 0.2714095115661621s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 1.9821250438690186s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.02788090705871582s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.027947664260864258s
Consistency | Disjoint class check for The European Library Open Dataset took 0.357130765914917s
Consistency | Check Misplaced properties for The European Library Open Dataset took 30.49012279510498s
Consistency | Misplaced classes for The European Library Open Dataset took 0.33760523796081543s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 1.701169729232788s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.2181899547576904s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 31.386879682540894s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.03375244140625s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 0.2585880756378174s
Security | Sign check for The European Library Open Dataset took 0.20682740211486816s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 12.82693099975586s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 1.2323906421661377s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.02069687843322754s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 7.033348083496094e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for the-european-library-open-dataset took 406.3949053287506s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 60.05859565734863s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0006868839263916016s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.6881368160247803s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.020334243774414062s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00011444091796875s
Believability | Calculation of trust value for The Eurostat Linked Data took 1.049041748046875e-05s
INFO | --- Analysis for the-eurostat-linked-data took 244.96659064292908s
Availability | SPARQL endpoint availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 4.076957702636719e-05s
Availability | VoID file availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.28411388397216797s
Reputation | Calculation of the PageRank for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.02026081085205078s
Interlinking | Calculation of Degree of Connection for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 2.956390380859375e-05s
Believability | Calculation of trust value for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 7.3909759521484375e-06s
INFO | --- Analysis for the-kazan-university-museum-as-linked-open-data-in-the-europeana-data-model took 3.9488701820373535s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 4.2438507080078125e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.7105617523193359s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.02028632164001465s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 8.368492126464844e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 6.4373016357421875e-06s
INFO | --- Analysis for the-living-lod-cloud took 45.74106979370117s
Availability | SPARQL endpoint availability check for The MIDI Linked Data Cloud took 4.100799560546875e-05s
Availability | VoID file availability check for The MIDI Linked Data Cloud took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for The MIDI Linked Data Cloud took 0.274975061416626s
Reputation | Calculation of the PageRank for The MIDI Linked Data Cloud took 0.020383834838867188s
Interlinking | Calculation of Degree of Connection for The MIDI Linked Data Cloud took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for The MIDI Linked Data Cloud took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for The MIDI Linked Data Cloud took 2.8848648071289062e-05s
Believability | Calculation of trust value for The MIDI Linked Data Cloud took 1.1444091796875e-05s
INFO | --- Analysis for the-midi-linked-data-cloud took 3.808163642883301s
Availability | SPARQL endpoint availability check for The View From took 0.08039402961730957s
Availability | VoID file availability check for The View From took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for The View From took 0.23779702186584473s
Reputation | Calculation of the PageRank for The View From took 0.020305156707763672s
Interlinking | Calculation of Degree of Connection for The View From took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The View From took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for The View From took 7.796287536621094e-05s
Believability | Calculation of trust value for The View From took 8.58306884765625e-06s
INFO | --- Analysis for the-view-from took 2.4409000873565674s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.578248262405396s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.27257490158081055s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020136117935180664s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 5.269050598144531e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 7.3909759521484375e-06s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 73.49306750297546s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.124016523361206s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.30768513679504395s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.02024102210998535s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 2.7418136596679688e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 6.67572021484375e-06s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 103.86905336380005s
Availability | SPARQL endpoint availability check for The Content Wrangler took 4.649162292480469e-05s
Availability | VoID file availability check for The Content Wrangler took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.2527587413787842s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.020769357681274414s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.00010395050048828125s
Believability | Calculation of trust value for The Content Wrangler took 8.821487426757812e-06s
INFO | --- Analysis for thecontentwrangler-com took 3.802034854888916s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 4.1484832763671875e-05s
Availability | VoID file availability check for Thesaurus BNCF took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.26487064361572266s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020531177520751953s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 3.075599670410156e-05s
Believability | Calculation of trust value for Thesaurus BNCF took 7.867813110351562e-06s
INFO | --- Analysis for thesaurus-bncf took 2.939304828643799s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.1961669921875e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.27533411979675293s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.020691871643066406s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 2.956390380859375e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 7.62939453125e-06s
INFO | --- Analysis for thesaurus-datenwissen took 2.9061625003814697s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.4634115695953369s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.0006706714630126953s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.25612902641296387s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.02030658721923828s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.486343383789062e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 7.3909759521484375e-06s
INFO | --- Analysis for thesaurus-w took 4.047177791595459s
Availability | SPARQL endpoint availability check for theses.fr took 7.605552673339844e-05s
Availability | VoID file availability check for theses.fr took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for theses.fr took 0.26555824279785156s
Reputation | Calculation of the PageRank for theses.fr took 0.020333290100097656s
Interlinking | Calculation of Degree of Connection for theses.fr took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for theses.fr took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for theses.fr took 4.8160552978515625e-05s
Believability | Calculation of trust value for theses.fr took 1.1920928955078125e-05s
INFO | --- Analysis for thesesfr took 4.136430501937866s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 4.363059997558594e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.26181936264038086s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.02061605453491211s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.457069396972656e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 6.67572021484375e-06s
INFO | --- Analysis for Thinkphile took 3.320269823074341s
Availability | SPARQL endpoint availability check for ThIST took 264.29841327667236s
Availability | VoID file availability check for ThIST took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for ThIST took 0.26792454719543457s
Reputation | Calculation of the PageRank for ThIST took 0.020592927932739258s
Interlinking | Calculation of Degree of Connection for ThIST took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ThIST took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for ThIST took 9.226799011230469e-05s
Believability | Calculation of trust value for ThIST took 7.3909759521484375e-06s
INFO | --- Analysis for thist took 562.0232026576996s
Availability | SPARQL endpoint availability check for TIP took 40.03879404067993s
Availability | VoID file availability check for TIP took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for TIP took 0.7230255603790283s
Reputation | Calculation of the PageRank for TIP took 0.025435686111450195s
Interlinking | Calculation of Degree of Connection for TIP took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00010895729064941406s
Believability | Calculation of trust value for TIP took 7.62939453125e-06s
INFO | --- Analysis for tip took 105.24715304374695s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 4.315376281738281e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.725780725479126s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.020555496215820312s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 3.0994415283203125e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 7.867813110351562e-06s
INFO | --- Analysis for TOPMODEL took 24.679363489151s
Availability | SPARQL endpoint availability check for Tourpedia took 4.100799560546875e-05s
Availability | VoID file availability check for Tourpedia took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for Tourpedia took 0.288956880569458s
Reputation | Calculation of the PageRank for Tourpedia took 0.020524024963378906s
Interlinking | Calculation of Degree of Connection for Tourpedia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Tourpedia took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Tourpedia took 3.123283386230469e-05s
Believability | Calculation of trust value for Tourpedia took 8.106231689453125e-06s
INFO | --- Analysis for tourpedia took 4.2819740772247314s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 4.215497732162476s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.2756657600402832s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.020321130752563477s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 3.600120544433594e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 9.298324584960938e-06s
INFO | --- Analysis for TP-data took 7.979970693588257s
Availability | SPARQL endpoint availability check for Trackloaded Linked Open Data took 1.917992353439331s
Availability | VoID file availability check for Trackloaded Linked Open Data took 0.0005345344543457031s
Extra | Recovery of all triples for Trackloaded Linked Open Data took 1.7750725746154785s
Performance | Total latancy measurement for Trackloaded Linked Open Data took 1.914698600769043s
Amount of data | Number of triples check for Trackloaded Linked Open Data took 1.6956677436828613s
Interoperability | New terms check for Trackloaded Linked Open Data took 2.841629981994629s
Versatility | Languages check for Trackloaded Linked Open Data took 1.4439842700958252s
Interpretability | Number of blank nodes check for Trackloaded Linked Open Data took 1.5553863048553467s
Interpretability | RDF structures check for Trackloaded Linked Open Data took 1.5723075866699219s
Versatility | Serialization formats check for Trackloaded Linked Open Data took 1.4669060707092285s
Availability | RDF dump link check for Trackloaded Linked Open Data took 1.6292016506195068s
License | MR license check for Trackloaded Linked Open Data took 1.4392375946044922s
License | HR license check for Trackloaded Linked Open Data took 1.5898420810699463s
Amount of data | Number of property check for Trackloaded Linked Open Data took 1.4320831298828125s
Understandability | Number of label check for Trackloaded Linked Open Data took 1.6906461715698242s
Understandability | URI regex check for Trackloaded Linked Open Data took 4.122978687286377s
Understandability | Vocabs check for Trackloaded Linked Open Data took 1.6118695735931396s
Verifiability | Authors check for Trackloaded Linked Open Data took 1.5566890239715576s
Verifiability | Publishers check for Trackloaded Linked Open Data took 2.8528687953948975s
Performance | Throughput check for Trackloaded Linked Open Data took 23.049882411956787s
Amount of data | Check the number of entities for Trackloaded Linked Open Data took 7.367134094238281e-05s
Verifiability | Contribs. check for Trackloaded Linked Open Data took 1.8654582500457764s
Interlinking | sameAs chians check for Trackloaded Linked Open Data took 1.9999258518218994s
Interlinking | skos check for Trackloaded Linked Open Data took 1.9181849956512451s
Interlinking | skos check for Trackloaded Linked Open Data took 0.11065816879272461s
Timeliness | dataset update frequency check for Trackloaded Linked Open Data took 2.0982770919799805s
Currency | Creation date check for Trackloaded Linked Open Data took 3.090214252471924s
Currency | Modification date check for Trackloaded Linked Open Data took 3.3174667358398438s
Rep.Conc. | URIs length for Trackloaded Linked Open Data took 1.5916938781738281s
Interoperability | New vocabularies check for Trackloaded Linked Open Data took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Trackloaded Linked Open Data took 0.7962698936462402s
Consistency | Disjoint class check for Trackloaded Linked Open Data took 0.4895644187927246s
Consistency | Check Ontology hijacking for Trackloaded Linked Open Data took 0.7630724906921387s
Consistency | Check Invalid usage of undefined properties for Trackloaded Linked Open Data took 2.0081164836883545s
Security | Sign check for Trackloaded Linked Open Data took 0.777519941329956s
Completeness | Calculation of interlinking completeness for Trackloaded Linked Open Data took 0.2460324764251709s
Reputation | Calculation of the PageRank for Trackloaded Linked Open Data took 0.020626306533813477s
Interlinking | Calculation of Degree of Connection for Trackloaded Linked Open Data took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Trackloaded Linked Open Data took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Trackloaded Linked Open Data took 2.574920654296875e-05s
Interoperability | Check the re-using of existing vocabs for Trackloaded Linked Open Data took 1.9073486328125e-06s
Believability | Calculation of trust value for Trackloaded Linked Open Data took 7.867813110351562e-06s
