Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 4.9591064453125e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0006957054138183594s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.27087998390197754s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.6718809604644775s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.0004525184631347656s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 1.3828277587890625e-05s
INFO | --- Analysis for 0080-3626 took 139.99649500846863s
Availability | SPARQL endpoint availability check for 土地利用图 took 9.34600830078125e-05s
Availability | VoID file availability check for 土地利用图 took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.37775588035583496s
Reputation | Calculation of the PageRank for 土地利用图 took 0.020951032638549805s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 3.62396240234375e-05s
Believability | Calculation of trust value for 土地利用图 took 1.049041748046875e-05s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 103.7575843334198s
Availability | SPARQL endpoint availability check for 113322 took 9.226799011230469e-05s
Availability | VoID file availability check for 113322 took 0.0007288455963134766s
Completeness | Calculation of interlinking completeness for 113322 took 0.36135387420654297s
Reputation | Calculation of the PageRank for 113322 took 0.020733356475830078s
Interlinking | Calculation of Degree of Connection for 113322 took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for 113322 took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for 113322 took 3.647804260253906e-05s
Believability | Calculation of trust value for 113322 took 2.0742416381835938e-05s
INFO | --- Analysis for 11 took 192.6832673549652s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 9.34600830078125e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.30414533615112305s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.02161097526550293s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0008075237274169922s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 3.62396240234375e-05s
Believability | Calculation of trust value for Korepetycje Buki took 1.1682510375976562e-05s
INFO | --- Analysis for 12323 took 56.00802159309387s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.03861069679260254s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.2987220287322998s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.022683143615722656s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 0.00010204315185546875s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 1.239776611328125e-05s
INFO | --- Analysis for 2000-us-census-rdf took 129.7162139415741s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 1.805204153060913s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.3033008575439453s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.020752429962158203s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0008816719055175781s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 4.76837158203125e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 8.58306884765625e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 78.57721495628357s
Availability | SPARQL endpoint availability check for Open Data Web took 11.405954837799072s
Availability | VoID file availability check for Open Data Web took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.3018667697906494s
Reputation | Calculation of the PageRank for Open Data Web took 0.02088308334350586s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 4.00543212890625e-05s
Believability | Calculation of trust value for Open Data Web took 1.2874603271484375e-05s
INFO | --- Analysis for _data.odw.tw took 91.22821927070618s
Availability | SPARQL endpoint availability check for 土地利用 took 5.14984130859375e-05s
Availability | VoID file availability check for 土地利用 took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.3075828552246094s
Reputation | Calculation of the PageRank for 土地利用 took 0.020833492279052734s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 3.647804260253906e-05s
Believability | Calculation of trust value for 土地利用 took 7.3909759521484375e-06s
INFO | --- Analysis for _data1.odw.tw took 100.93027377128601s
Availability | SPARQL endpoint availability check for 土地利用模型 took 0.00010228157043457031s
Availability | VoID file availability check for 土地利用模型 took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 27.101547956466675s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.02098536491394043s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 3.4332275390625e-05s
Believability | Calculation of trust value for 土地利用模型 took 1.239776611328125e-05s
INFO | --- Analysis for _data2.odw.tw took 83.3780312538147s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 9.465217590332031e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 22.399494171142578s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02124309539794922s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0008258819580078125s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.8623809814453125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2636184692382812e-05s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 175.86424899101257s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 0.00011157989501953125s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 23.496188163757324s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.022257089614868164s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.001214742660522461s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 5.316734313964844e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 1.3828277587890625e-05s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 81.2360007762909s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 4.506111145019531e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0007951259613037109s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 23.541887998580933s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.021037578582763672s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 3.647804260253906e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 9.775161743164062e-06s
INFO | --- Analysis for A1 took 93.44519424438477s
Availability | SPARQL endpoint availability check for SummerOlympics took 2.186624526977539s
Availability | VoID file availability check for SummerOlympics took 0.0007379055023193359s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.28896021842956543s
Reputation | Calculation of the PageRank for SummerOlympics took 0.021329641342163086s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 7.2479248046875e-05s
Believability | Calculation of trust value for SummerOlympics took 1.3113021850585938e-05s
INFO | --- Analysis for abc took 100.00596451759338s
Availability | SPARQL endpoint availability check for Test_m took 0.00012111663818359375s
Availability | VoID file availability check for Test_m took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for Test_m took 0.2915222644805908s
Reputation | Calculation of the PageRank for Test_m took 0.02740001678466797s
Interlinking | Calculation of Degree of Connection for Test_m took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Test_m took 0.0014934539794921875s
Interlinking | Calculation of Clustering coefficient for Test_m took 7.05718994140625e-05s
Believability | Calculation of trust value for Test_m took 1.430511474609375e-05s
INFO | --- Analysis for ABC took 109.72451853752136s
Availability | SPARQL endpoint availability check for my intro took 0.0001270771026611328s
Availability | VoID file availability check for my intro took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for my intro took 31.139443159103394s
Reputation | Calculation of the PageRank for my intro took 0.027762174606323242s
Interlinking | Calculation of Degree of Connection for my intro took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for my intro took 0.0014064311981201172s
Interlinking | Calculation of Clustering coefficient for my intro took 7.367134094238281e-05s
Believability | Calculation of trust value for my intro took 1.52587890625e-05s
INFO | --- Analysis for abhay_intro took 178.0493459701538s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.09054040908813477s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.3261685371398926s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.02341914176940918s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0008823871612548828s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00011754035949707031s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 1.4066696166992188e-05s
INFO | --- Analysis for abs-linked-data took 79.45491576194763s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 0.00020265579223632812s
Availability | VoID file availability check for Academic Offer of UNL took 0.0007786750793457031s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 23.876178741455078s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.022284984588623047s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 3.933906555175781e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 1.1920928955078125e-05s
INFO | --- Analysis for academic-offer-of-unl took 250.86810183525085s
Availability | SPARQL endpoint availability check for AcadOnto took 4.6253204345703125e-05s
Availability | VoID file availability check for AcadOnto took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for AcadOnto took 30.822745323181152s
Reputation | Calculation of the PageRank for AcadOnto took 0.02071094512939453s
Interlinking | Calculation of Degree of Connection for AcadOnto took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 4.0531158447265625e-05s
Believability | Calculation of trust value for AcadOnto took 1.2159347534179688e-05s
INFO | --- Analysis for acadonto took 242.57045030593872s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.202847480773926s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007741451263427734s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.35355353355407715s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.021265506744384766s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 4.220008850097656e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.049041748046875e-05s
INFO | --- Analysis for acorn-sat took 165.93074107170105s
Availability | SPARQL endpoint availability check for Addgene took 9.369850158691406e-05s
Availability | VoID file availability check for Addgene took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for Addgene took 0.3121016025543213s
Reputation | Calculation of the PageRank for Addgene took 0.020713329315185547s
Interlinking | Calculation of Degree of Connection for Addgene took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Addgene took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Addgene took 4.1484832763671875e-05s
Believability | Calculation of trust value for Addgene took 1.3113021850585938e-05s
INFO | --- Analysis for addgene took 166.94509148597717s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 5.1021575927734375e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.925243616104126s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.39599061012268066s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.02144765853881836s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0008716583251953125s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 0.00010848045349121094s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.2636184692382812e-05s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 165.0762803554535s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.48043251037597656s
Availability | VoID file availability check for AEMET metereological dataset took 0.2416999340057373s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.3611724376678467s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.022200822830200195s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 4.220008850097656e-05s
Interoperability | Check the re-using of existing vocabs for AEMET metereological dataset took 3.337860107421875e-06s
Believability | Calculation of trust value for AEMET metereological dataset took 1.3113021850585938e-05s
INFO | --- Analysis for aemet took 99.68479585647583s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 8.726119995117188e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.000743865966796875s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 23.74071717262268s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.022444963455200195s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 4.935264587402344e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 1.3828277587890625e-05s
INFO | --- Analysis for agenda-de-zaragoza took 177.4853639602661s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.03785252571105957s
Availability | VoID file availability check for AgriNepalData took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for AgriNepalData took 23.67708730697632s
Reputation | Calculation of the PageRank for AgriNepalData took 0.021384239196777344s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0008654594421386719s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 8.296966552734375e-05s
Believability | Calculation of trust value for AgriNepalData took 1.1920928955078125e-05s
INFO | --- Analysis for agrinepaldata took 157.7939488887787s
Availability | SPARQL endpoint availability check for AGRIS took 263.0827386379242s
Availability | VoID file availability check for AGRIS took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for AGRIS took 0.6289265155792236s
Reputation | Calculation of the PageRank for AGRIS took 0.022726058959960938s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for AGRIS took 9.703636169433594e-05s
Believability | Calculation of trust value for AGRIS took 1.621246337890625e-05s
INFO | --- Analysis for agris took 816.1771466732025s
Availability | SPARQL endpoint availability check for AGROVOC took 0.2152562141418457s
Availability | VoID file availability check for AGROVOC took 0.0006833076477050781s
Extra | Recovery of all triples for AGROVOC took 128.83917689323425s
Performance | Total latancy measurement for AGROVOC took 0.4850590229034424s
Amount of data | Number of triples check for AGROVOC took 171.2202410697937s
Interoperability | New terms check for AGROVOC took 5.037910461425781s
Versatility | Languages check for AGROVOC took 300.07951378822327s
Interpretability | Number of blank nodes check for AGROVOC took 300.12884497642517s
Interpretability | RDF structures check for AGROVOC took 0.0816197395324707s
Versatility | Serialization formats check for AGROVOC took 0.1370558738708496s
Availability | RDF dump link check for AGROVOC took 0.0964822769165039s
License | MR license check for AGROVOC took 0.14205336570739746s
License | HR license check for AGROVOC took 2.115180015563965s
Amount of data | Number of property check for AGROVOC took 0.11459064483642578s
Understandability | Number of label check for AGROVOC took 246.4029519557953s
Understandability | URI regex check for AGROVOC took 0.15344882011413574s
Understandability | Vocabs check for AGROVOC took 0.08813238143920898s
Verifiability | Authors check for AGROVOC took 0.08812427520751953s
Verifiability | Publishers check for AGROVOC took 0.08903050422668457s
Performance | Throughput check for AGROVOC took 10.55921196937561s
Amount of data | Check the number of entities for AGROVOC took 5.14984130859375e-05s
Verifiability | Contribs. check for AGROVOC took 0.1384272575378418s
Interlinking | sameAs chians check for AGROVOC took 0.09366917610168457s
Interlinking | skos check for AGROVOC took 22.850410223007202s
Interlinking | skos check for AGROVOC took 8.065702199935913s
Timeliness | dataset update frequency check for AGROVOC took 0.08814549446105957s
Currency | Creation date check for AGROVOC took 0.24693703651428223s
Currency | Modification date check for AGROVOC took 0.17956852912902832s
Rep.Conc. | URIs length for AGROVOC took 201.52618527412415s
Interoperability | New vocabularies check for AGROVOC took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.08645033836364746s
Accuracy | Check Functional Property for AGROVOC took 0.09567904472351074s
Accuracy | Check Inverse Functional Property for AGROVOC took 0.07174205780029297s
Accuracy | Check Empty annotation labels for AGROVOC took 28.862788438796997s
Accuracy | Check White space in annotation for AGROVOC took 3.0485124588012695s
Accuracy | Check Datatype consistency for AGROVOC took 4.679679870605469s
Consistency | Disjoint class check for AGROVOC took 0.09974837303161621s
Consistency | Check Misplaced properties for AGROVOC took 24.805949211120605s
Consistency | Check Ontology hijacking for AGROVOC took 247.73738431930542s
Consistency | Check Invalid usage of undefined classes for AGROVOC took 1.7282371520996094s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 24.29297423362732s
Conciseness | Check Extensional conciseness for AGROVOC took 2.8755414485931396s
Conciseness | Check Intensional conciseness for AGROVOC took 0.10449552536010742s
Security | Sign check for AGROVOC took 0.07999277114868164s
Availability | Check URIs Dereferenciability for AGROVOC took 5.0659589767456055s
Completeness | Calculation of interlinking completeness for AGROVOC took 22.041951417922974s
Reputation | Calculation of the PageRank for AGROVOC took 0.025102853775024414s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00012087821960449219s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 2.1457672119140625e-06s
Believability | Calculation of trust value for AGROVOC took 1.3113021850585938e-05s
INFO | --- Analysis for agrovoc took 2407.6246173381805s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 1.2042605876922607s
Availability | VoID file availability check for Analytics India Magazine took 0.0007627010345458984s
Extra | Recovery of all triples for Analytics India Magazine took 1.8916351795196533s
Performance | Total latancy measurement for Analytics India Magazine took 2.844733953475952s
Amount of data | Number of triples check for Analytics India Magazine took 1.067962408065796s
Versatility | Languages check for Analytics India Magazine took 1.1527624130249023s
Interpretability | Number of blank nodes check for Analytics India Magazine took 1.2771289348602295s
Interpretability | RDF structures check for Analytics India Magazine took 0.9082725048065186s
Versatility | Serialization formats check for Analytics India Magazine took 1.3833768367767334s
Availability | RDF dump link check for Analytics India Magazine took 1.10587477684021s
License | MR license check for Analytics India Magazine took 1.0261530876159668s
License | HR license check for Analytics India Magazine took 1.2909135818481445s
Amount of data | Number of property check for Analytics India Magazine took 0.8331527709960938s
Understandability | Number of label check for Analytics India Magazine took 0.9376235008239746s
Understandability | URI regex check for Analytics India Magazine took 2.003955125808716s
Understandability | Vocabs check for Analytics India Magazine took 1.1244826316833496s
Verifiability | Authors check for Analytics India Magazine took 1.016329288482666s
Verifiability | Publishers check for Analytics India Magazine took 0.9732534885406494s
Performance | Throughput check for Analytics India Magazine took 14.023266792297363s
Amount of data | Check the number of entities for Analytics India Magazine took 0.00011706352233886719s
Verifiability | Contribs. check for Analytics India Magazine took 1.5419559478759766s
Interlinking | sameAs chians check for Analytics India Magazine took 0.9348158836364746s
Interlinking | skos check for Analytics India Magazine took 1.1230337619781494s
Interlinking | skos check for Analytics India Magazine took 0.9332077503204346s
Timeliness | dataset update frequency check for Analytics India Magazine took 1.0188226699829102s
Currency | Creation date check for Analytics India Magazine took 1.9137260913848877s
Currency | Modification date check for Analytics India Magazine took 2.411621332168579s
Rep.Conc. | URIs length for Analytics India Magazine took 2.592764139175415s
Interoperability | New vocabularies check for Analytics India Magazine took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Analytics India Magazine took 1.0827105045318604s
Consistency | Disjoint class check for Analytics India Magazine took 1.0868384838104248s
Consistency | Check Ontology hijacking for Analytics India Magazine took 1.0950212478637695s
Consistency | Check Invalid usage of undefined properties for Analytics India Magazine took 2.775974750518799s
Conciseness | Check Extensional conciseness for Analytics India Magazine took 0.00015926361083984375s
Security | Sign check for Analytics India Magazine took 1.0484881401062012s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.34868907928466797s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.020792484283447266s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 3.7670135498046875e-05s
Interoperability | Check the re-using of existing vocabs for Analytics India Magazine took 9.5367431640625e-07s
Believability | Calculation of trust value for Analytics India Magazine took 9.059906005859375e-06s
INFO | --- Analysis for AIM took 190.22675156593323s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 8.940696716308594e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 22.563265800476074s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.02182769775390625s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 3.910064697265625e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 1.7404556274414062e-05s
INFO | --- Analysis for AISHE took 117.25816011428833s
Availability | SPARQL endpoint availability check for  equipment ontology took 6.890296936035156e-05s
Availability | VoID file availability check for  equipment ontology took 0.0006005764007568359s
Completeness | Calculation of interlinking completeness for  equipment ontology took 27.64457654953003s
Reputation | Calculation of the PageRank for  equipment ontology took 0.020824670791625977s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.4809112548828125e-05s
Believability | Calculation of trust value for  equipment ontology took 1.33514404296875e-05s
INFO | --- Analysis for akash took 107.55847978591919s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 261.69420099258423s
Availability | VoID file availability check for aliada-scanbit-net took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 29.96984100341797s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.02172708511352539s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00012421607971191406s
Believability | Calculation of trust value for aliada-scanbit-net took 1.1920928955078125e-05s
INFO | --- Analysis for aliada-scanbit-net took 1735.8881330490112s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 0.8494236469268799s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0007169246673583984s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 139.64557099342346s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.884875535964966s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.6379857063293457s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.6406426429748535s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.0879945755005s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 4.43301248550415s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8804986476898193s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.8280062675476074s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.6234996318817139s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.5929591655731201s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.6136794090270996s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 30.83005690574646s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.5766043663024902s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.7521982192993164s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.1999342441558838s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.618091344833374s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.6105685234069824s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.6188709735870361s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.779985904693604s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 7.128715515136719e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5483510494232178s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.6614480018615723s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6803009510040283s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6165199279785156s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.5980219841003418s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.1678423881530762s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.124901294708252s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 54.36453557014465s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 2.8068501949310303s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.565035343170166s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6700358390808105s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6484358310699463s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 34.6949622631073s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.116276502609253s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.870060443878174s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.6020548343658447s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 10.438503980636597s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 9.357058763504028s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 32.89988589286804s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.5504961013793945s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.489052295684814s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.825122833251953s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8501532077789307s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.54433274269104s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 13676.239261865616s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 0.30260539054870605s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.02222466468811035s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 0.00010395050048828125s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 1.5548598766326904s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 1.9311904907226562e-05s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 14496.103660583496s
Availability | SPARQL endpoint availability check for Alojamientos took 8.487701416015625e-05s
Availability | VoID file availability check for Alojamientos took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.2866535186767578s
Reputation | Calculation of the PageRank for Alojamientos took 0.02138972282409668s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 4.9591064453125e-05s
Believability | Calculation of trust value for Alojamientos took 1.2159347534179688e-05s
INFO | --- Analysis for alojamientos-zaragoza took 175.97815823554993s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.3958168029785156s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 30.77746558189392s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.02226734161376953s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 4.458427429199219e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 1.239776611328125e-05s
INFO | --- Analysis for alpino-rdf took 145.1223328113556s
Availability | SPARQL endpoint availability check for AAT-atawil took 4.2438507080078125e-05s
Availability | VoID file availability check for AAT-atawil took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.3282914161682129s
Reputation | Calculation of the PageRank for AAT-atawil took 0.020802736282348633s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.8623809814453125e-05s
Believability | Calculation of trust value for AAT-atawil took 1.1682510375976562e-05s
INFO | --- Analysis for Altawil took 108.87030410766602s
Availability | SPARQL endpoint availability check for Amer Nejma took 8.797645568847656e-05s
Availability | VoID file availability check for Amer Nejma took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for Amer Nejma took 25.603222608566284s
Reputation | Calculation of the PageRank for Amer Nejma took 0.02051067352294922s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.4332275390625e-05s
Believability | Calculation of trust value for Amer Nejma took 8.106231689453125e-06s
INFO | --- Analysis for Amer_Nejma took 125.33037257194519s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 26.203742742538452s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.020461082458496094s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.4809112548828125e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for amon took 208.85435152053833s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.6922941207885742s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 23.49812602996826s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.020792722702026367s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.441375732421875e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.239776611328125e-05s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 178.61772871017456s
Availability | SPARQL endpoint availability check for Anime Dataset took 5.555152893066406e-05s
Availability | VoID file availability check for Anime Dataset took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.28713226318359375s
Reputation | Calculation of the PageRank for Anime Dataset took 0.021548032760620117s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 3.3855438232421875e-05s
Believability | Calculation of trust value for Anime Dataset took 1.2159347534179688e-05s
INFO | --- Analysis for Anime took 154.37953662872314s
Availability | SPARQL endpoint availability check for ANNO took 8.797645568847656e-05s
Availability | VoID file availability check for ANNO took 0.0007624626159667969s
Completeness | Calculation of interlinking completeness for ANNO took 21.3050377368927s
Reputation | Calculation of the PageRank for ANNO took 0.020740747451782227s
Interlinking | Calculation of Degree of Connection for ANNO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.4809112548828125e-05s
Believability | Calculation of trust value for ANNO took 1.2636184692382812e-05s
INFO | --- Analysis for anno took 134.31664419174194s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 4.1961669921875e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 21.703051328659058s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.02289295196533203s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0008225440979003906s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 9.393692016601562e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 1.239776611328125e-05s
INFO | --- Analysis for AntiqueCarsCollection took 169.9962122440338s
Availability | SPARQL endpoint availability check for apache took 9.059906005859375e-05s
Availability | VoID file availability check for apache took 0.0008170604705810547s
Completeness | Calculation of interlinking completeness for apache took 23.163265466690063s
Reputation | Calculation of the PageRank for apache took 0.02046799659729004s
Interlinking | Calculation of Degree of Connection for apache took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for apache took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for apache took 6.794929504394531e-05s
Believability | Calculation of trust value for apache took 1.2159347534179688e-05s
INFO | --- Analysis for apache took 124.13417387008667s
Availability | SPARQL endpoint availability check for Apertium RDF took 1.2779910564422607s
Availability | VoID file availability check for Apertium RDF took 0.0007369518280029297s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.37496471405029297s
Reputation | Calculation of the PageRank for Apertium RDF took 0.020585298538208008s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 5.221366882324219e-05s
Believability | Calculation of trust value for Apertium RDF took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf took 176.54153752326965s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 0.2704746723175049s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0006611347198486328s
Extra | Recovery of all triples for Apertium RDF CA-IT took 165.44529509544373s
Performance | Total latancy measurement for Apertium RDF CA-IT took 1.214839220046997s
Amount of data | Number of triples check for Apertium RDF CA-IT took 2.240068197250366s
Interoperability | New terms check for Apertium RDF CA-IT took 3.175833225250244s
Versatility | Languages check for Apertium RDF CA-IT took 44.42260408401489s
Interpretability | Number of blank nodes check for Apertium RDF CA-IT took 1.0974302291870117s
Security | Check HTTPS for Apertium RDF CA-IT took 0.14463305473327637s
Interpretability | RDF structures check for Apertium RDF CA-IT took 0.48224687576293945s
Versatility | Serialization formats check for Apertium RDF CA-IT took 0.2931702136993408s
Availability | RDF dump link check for Apertium RDF CA-IT took 0.29369425773620605s
License | MR license check for Apertium RDF CA-IT took 0.290210485458374s
License | HR license check for Apertium RDF CA-IT took 0.3689587116241455s
Amount of data | Number of property check for Apertium RDF CA-IT took 0.3098909854888916s
Understandability | Number of label check for Apertium RDF CA-IT took 0.33290648460388184s
Understandability | URI regex check for Apertium RDF CA-IT took 0.5322351455688477s
Understandability | Vocabs check for Apertium RDF CA-IT took 0.29820752143859863s
Verifiability | Authors check for Apertium RDF CA-IT took 0.27638792991638184s
Verifiability | Publishers check for Apertium RDF CA-IT took 0.26160168647766113s
Performance | Throughput check for Apertium RDF CA-IT took 11.039811372756958s
Amount of data | Check the number of entities for Apertium RDF CA-IT took 0.00011944770812988281s
Verifiability | Contribs. check for Apertium RDF CA-IT took 0.2882108688354492s
Interlinking | sameAs chians check for Apertium RDF CA-IT took 0.29263806343078613s
Interlinking | skos check for Apertium RDF CA-IT took 0.28693151473999023s
Interlinking | skos check for Apertium RDF CA-IT took 0.21246862411499023s
Timeliness | dataset update frequency check for Apertium RDF CA-IT took 0.2888834476470947s
Currency | Creation date check for Apertium RDF CA-IT took 0.5644667148590088s
Currency | Modification date check for Apertium RDF CA-IT took 0.6085047721862793s
Rep.Conc. | URIs length for Apertium RDF CA-IT took 58.45627188682556s
Interoperability | New vocabularies check for Apertium RDF CA-IT took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF CA-IT took 0.29764628410339355s
Accuracy | Check Functional Property for Apertium RDF CA-IT took 0.28339433670043945s
Accuracy | Check Inverse Functional Property for Apertium RDF CA-IT took 0.26795244216918945s
Accuracy | Check Empty annotation labels for Apertium RDF CA-IT took 1.020810604095459s
Accuracy | Check White space in annotation for Apertium RDF CA-IT took 0.010315656661987305s
Accuracy | Check Datatype consistency for Apertium RDF CA-IT took 2.716320753097534s
Consistency | Disjoint class check for Apertium RDF CA-IT took 0.5103757381439209s
Consistency | Check Misplaced properties for Apertium RDF CA-IT took 4.849035024642944s
Consistency | Misplaced classes for Apertium RDF CA-IT took 8.553147554397583s
Consistency | Check Ontology hijacking for Apertium RDF CA-IT took 44.322635889053345s
Consistency | Check Invalid usage of undefined classes for Apertium RDF CA-IT took 1.7020976543426514s
Consistency | Check Invalid usage of undefined properties for Apertium RDF CA-IT took 5.891970634460449s
Conciseness | Check Extensional conciseness for Apertium RDF CA-IT took 2.950364112854004s
Conciseness | Check Intensional conciseness for Apertium RDF CA-IT took 0.28282618522644043s
Security | Sign check for Apertium RDF CA-IT took 0.29888010025024414s
Availability | Check URIs Dereferenciability for Apertium RDF CA-IT took 10.453301668167114s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 22.586742401123047s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.021104812622070312s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.57763671875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF CA-IT took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF CA-IT took 1.0967254638671875e-05s
INFO | --- Analysis for apertium-rdf-ca-it took 523.033050775528s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 0.00015425682067871094s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0006475448608398438s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.32717299461364746s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.020985841751098633s
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.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.649162292480469e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 1.1444091796875e-05s
INFO | --- Analysis for apertium-rdf-en-ca took 57.06812286376953s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 0.2220017910003662s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0006477832794189453s
Extra | Recovery of all triples for Apertium RDF EN-ES took 159.59978342056274s
Performance | Total latancy measurement for Apertium RDF EN-ES took 1.2253499031066895s
Amount of data | Number of triples check for Apertium RDF EN-ES took 2.0822219848632812s
Interoperability | New terms check for Apertium RDF EN-ES took 3.3394298553466797s
Versatility | Languages check for Apertium RDF EN-ES took 44.26269054412842s
Interpretability | Number of blank nodes check for Apertium RDF EN-ES took 1.202174186706543s
Security | Check HTTPS for Apertium RDF EN-ES took 0.13462138175964355s
Interpretability | RDF structures check for Apertium RDF EN-ES took 0.2769508361816406s
Versatility | Serialization formats check for Apertium RDF EN-ES took 0.28516483306884766s
Availability | RDF dump link check for Apertium RDF EN-ES took 0.27474284172058105s
License | MR license check for Apertium RDF EN-ES took 0.28732752799987793s
License | HR license check for Apertium RDF EN-ES took 0.38524889945983887s
Amount of data | Number of property check for Apertium RDF EN-ES took 0.28051257133483887s
Understandability | Number of label check for Apertium RDF EN-ES took 0.31122469902038574s
Understandability | URI regex check for Apertium RDF EN-ES took 0.5754594802856445s
Understandability | Vocabs check for Apertium RDF EN-ES took 0.2892746925354004s
Verifiability | Authors check for Apertium RDF EN-ES took 2.283137798309326s
Verifiability | Publishers check for Apertium RDF EN-ES took 0.2888681888580322s
Performance | Throughput check for Apertium RDF EN-ES took 11.129586219787598s
Amount of data | Check the number of entities for Apertium RDF EN-ES took 7.081031799316406e-05s
Verifiability | Contribs. check for Apertium RDF EN-ES took 0.28206396102905273s
Interlinking | sameAs chians check for Apertium RDF EN-ES took 0.282214879989624s
Interlinking | skos check for Apertium RDF EN-ES took 0.29325056076049805s
Interlinking | skos check for Apertium RDF EN-ES took 0.23623991012573242s
Timeliness | dataset update frequency check for Apertium RDF EN-ES took 0.2920112609863281s
Currency | Creation date check for Apertium RDF EN-ES took 0.5673599243164062s
Currency | Modification date check for Apertium RDF EN-ES took 0.5833103656768799s
Rep.Conc. | URIs length for Apertium RDF EN-ES took 59.424089193344116s
Interoperability | New vocabularies check for Apertium RDF EN-ES took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF EN-ES took 0.2846355438232422s
Accuracy | Check Functional Property for Apertium RDF EN-ES took 0.2775580883026123s
Accuracy | Check Inverse Functional Property for Apertium RDF EN-ES took 0.2749519348144531s
Accuracy | Check Empty annotation labels for Apertium RDF EN-ES took 1.0063693523406982s
Accuracy | Check White space in annotation for Apertium RDF EN-ES took 0.010490179061889648s
Accuracy | Check Datatype consistency for Apertium RDF EN-ES took 2.694554328918457s
Consistency | Disjoint class check for Apertium RDF EN-ES took 0.2826056480407715s
Consistency | Check Misplaced properties for Apertium RDF EN-ES took 4.648665428161621s
Consistency | Misplaced classes for Apertium RDF EN-ES took 8.665645837783813s
Consistency | Check Ontology hijacking for Apertium RDF EN-ES took 44.33506989479065s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EN-ES took 1.7069430351257324s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EN-ES took 5.942493677139282s
Conciseness | Check Extensional conciseness for Apertium RDF EN-ES took 2.95184588432312s
Conciseness | Check Intensional conciseness for Apertium RDF EN-ES took 0.3089027404785156s
Security | Sign check for Apertium RDF EN-ES took 0.2633631229400635s
Availability | Check URIs Dereferenciability for Apertium RDF EN-ES took 9.661059617996216s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.411731481552124s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.02101874351501465s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 5.245208740234375e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EN-ES took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF EN-ES took 1.33514404296875e-05s
INFO | --- Analysis for apertium-rdf-en-es took 488.34965920448303s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 9.369850158691406e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.28944921493530273s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.020903348922729492s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007386207580566406s
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 1.3113021850585938e-05s
INFO | --- Analysis for apertium-rdf-en-gl took 34.746915102005005s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 0.2865941524505615s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0006377696990966797s
Extra | Recovery of all triples for Apertium RDF EO-CA took 159.52479147911072s
Performance | Total latancy measurement for Apertium RDF EO-CA took 1.239393711090088s
Amount of data | Number of triples check for Apertium RDF EO-CA took 2.0703585147857666s
Interoperability | New terms check for Apertium RDF EO-CA took 3.363718271255493s
Versatility | Languages check for Apertium RDF EO-CA took 44.15306520462036s
Interpretability | Number of blank nodes check for Apertium RDF EO-CA took 1.2306437492370605s
Security | Check HTTPS for Apertium RDF EO-CA took 0.13453102111816406s
Interpretability | RDF structures check for Apertium RDF EO-CA took 0.2751927375793457s
Versatility | Serialization formats check for Apertium RDF EO-CA took 0.29790759086608887s
Availability | RDF dump link check for Apertium RDF EO-CA took 0.2805633544921875s
License | MR license check for Apertium RDF EO-CA took 0.29445981979370117s
License | HR license check for Apertium RDF EO-CA took 0.37874388694763184s
Amount of data | Number of property check for Apertium RDF EO-CA took 0.2963099479675293s
Understandability | Number of label check for Apertium RDF EO-CA took 0.32299208641052246s
Understandability | URI regex check for Apertium RDF EO-CA took 0.558272123336792s
Understandability | Vocabs check for Apertium RDF EO-CA took 0.2772848606109619s
Verifiability | Authors check for Apertium RDF EO-CA took 0.27562952041625977s
Verifiability | Publishers check for Apertium RDF EO-CA took 0.2630581855773926s
Performance | Throughput check for Apertium RDF EO-CA took 11.081268548965454s
Amount of data | Check the number of entities for Apertium RDF EO-CA took 7.724761962890625e-05s
Verifiability | Contribs. check for Apertium RDF EO-CA took 0.2809889316558838s
Interlinking | sameAs chians check for Apertium RDF EO-CA took 0.28660106658935547s
Interlinking | skos check for Apertium RDF EO-CA took 0.29465484619140625s
Interlinking | skos check for Apertium RDF EO-CA took 0.22786951065063477s
Timeliness | dataset update frequency check for Apertium RDF EO-CA took 0.2787027359008789s
Currency | Creation date check for Apertium RDF EO-CA took 0.5547730922698975s
Currency | Modification date check for Apertium RDF EO-CA took 0.5808932781219482s
Rep.Conc. | URIs length for Apertium RDF EO-CA took 59.37004828453064s
Interoperability | New vocabularies check for Apertium RDF EO-CA took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-CA took 0.2938041687011719s
Accuracy | Check Functional Property for Apertium RDF EO-CA took 0.3005242347717285s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-CA took 0.28020167350769043s
Accuracy | Check Empty annotation labels for Apertium RDF EO-CA took 0.9750206470489502s
Accuracy | Check White space in annotation for Apertium RDF EO-CA took 0.010373830795288086s
Accuracy | Check Datatype consistency for Apertium RDF EO-CA took 2.6903884410858154s
Consistency | Disjoint class check for Apertium RDF EO-CA took 0.30480527877807617s
Consistency | Check Misplaced properties for Apertium RDF EO-CA took 4.561134576797485s
Consistency | Misplaced classes for Apertium RDF EO-CA took 8.525918960571289s
Consistency | Check Ontology hijacking for Apertium RDF EO-CA took 44.73684501647949s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-CA took 1.7124755382537842s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-CA took 5.95975661277771s
Conciseness | Check Extensional conciseness for Apertium RDF EO-CA took 2.960644245147705s
Conciseness | Check Intensional conciseness for Apertium RDF EO-CA took 0.31743454933166504s
Security | Sign check for Apertium RDF EO-CA took 0.3064579963684082s
Availability | Check URIs Dereferenciability for Apertium RDF EO-CA took 9.405216455459595s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 24.00010919570923s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.02183985710144043s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0009562969207763672s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 5.698204040527344e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-CA took 1.1682510375976562e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-eo-ca took 631.8443295955658s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 9.655952453613281e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 32.62712907791138s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.021346330642700195s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.863739013671875e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.2636184692382812e-05s
INFO | --- Analysis for apertium-rdf-eo-en took 124.64194822311401s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 9.131431579589844e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.3226015567779541s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.696846008300781e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-eo-es took 166.75934982299805s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 0.27518296241760254s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0006377696990966797s
Extra | Recovery of all triples for Apertium RDF EO-FR took 158.44646334648132s
Performance | Total latancy measurement for Apertium RDF EO-FR took 1.2058017253875732s
Amount of data | Number of triples check for Apertium RDF EO-FR took 2.0740644931793213s
Interoperability | New terms check for Apertium RDF EO-FR took 3.331169605255127s
Versatility | Languages check for Apertium RDF EO-FR took 44.70015549659729s
Interpretability | Number of blank nodes check for Apertium RDF EO-FR took 1.2312250137329102s
Security | Check HTTPS for Apertium RDF EO-FR took 0.1343400478363037s
Interpretability | RDF structures check for Apertium RDF EO-FR took 0.28867411613464355s
Versatility | Serialization formats check for Apertium RDF EO-FR took 0.2970247268676758s
Availability | RDF dump link check for Apertium RDF EO-FR took 0.27315759658813477s
License | MR license check for Apertium RDF EO-FR took 0.2959935665130615s
License | HR license check for Apertium RDF EO-FR took 0.4016993045806885s
Amount of data | Number of property check for Apertium RDF EO-FR took 0.28435182571411133s
Understandability | Number of label check for Apertium RDF EO-FR took 0.3059718608856201s
Understandability | URI regex check for Apertium RDF EO-FR took 0.5708937644958496s
Understandability | Vocabs check for Apertium RDF EO-FR took 0.2885568141937256s
Verifiability | Authors check for Apertium RDF EO-FR took 0.27950525283813477s
Verifiability | Publishers check for Apertium RDF EO-FR took 0.29174041748046875s
Performance | Throughput check for Apertium RDF EO-FR took 11.061394691467285s
Amount of data | Check the number of entities for Apertium RDF EO-FR took 7.152557373046875e-05s
Verifiability | Contribs. check for Apertium RDF EO-FR took 0.2606179714202881s
Interlinking | sameAs chians check for Apertium RDF EO-FR took 0.28660035133361816s
Interlinking | skos check for Apertium RDF EO-FR took 0.2772221565246582s
Interlinking | skos check for Apertium RDF EO-FR took 0.22744011878967285s
Timeliness | dataset update frequency check for Apertium RDF EO-FR took 0.2867856025695801s
Currency | Creation date check for Apertium RDF EO-FR took 0.5496606826782227s
Currency | Modification date check for Apertium RDF EO-FR took 0.540503740310669s
Rep.Conc. | URIs length for Apertium RDF EO-FR took 58.41964268684387s
Interoperability | New vocabularies check for Apertium RDF EO-FR took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF EO-FR took 0.3009326457977295s
Accuracy | Check Functional Property for Apertium RDF EO-FR took 0.26273679733276367s
Accuracy | Check Inverse Functional Property for Apertium RDF EO-FR took 0.2780647277832031s
Accuracy | Check Empty annotation labels for Apertium RDF EO-FR took 0.9591002464294434s
Accuracy | Check White space in annotation for Apertium RDF EO-FR took 0.010612249374389648s
Accuracy | Check Datatype consistency for Apertium RDF EO-FR took 2.7100770473480225s
Consistency | Disjoint class check for Apertium RDF EO-FR took 0.26291370391845703s
Consistency | Check Misplaced properties for Apertium RDF EO-FR took 4.725358963012695s
Consistency | Misplaced classes for Apertium RDF EO-FR took 8.700406551361084s
Consistency | Check Ontology hijacking for Apertium RDF EO-FR took 44.4854736328125s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EO-FR took 1.7188024520874023s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EO-FR took 5.886904239654541s
Conciseness | Check Extensional conciseness for Apertium RDF EO-FR took 2.9376304149627686s
Conciseness | Check Intensional conciseness for Apertium RDF EO-FR took 0.3129756450653076s
Security | Sign check for Apertium RDF EO-FR took 0.2736632823944092s
Availability | Check URIs Dereferenciability for Apertium RDF EO-FR took 10.625612735748291s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.4119710922241211s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.02128314971923828s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.649162292480469e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EO-FR took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EO-FR took 1.0967254638671875e-05s
INFO | --- Analysis for apertium-rdf-eo-fr took 545.3445222377777s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.696846008300781e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0007104873657226562s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.29348158836364746s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.021243572235107422s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.9591064453125e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-es-an took 176.50051546096802s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 0.2626330852508545s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0007092952728271484s
Extra | Recovery of all triples for Apertium RDF ES-AST took 160.12814021110535s
Performance | Total latancy measurement for Apertium RDF ES-AST took 1.2057948112487793s
Amount of data | Number of triples check for Apertium RDF ES-AST took 2.1425154209136963s
Interoperability | New terms check for Apertium RDF ES-AST took 3.1693286895751953s
Versatility | Languages check for Apertium RDF ES-AST took 44.47447061538696s
Interpretability | Number of blank nodes check for Apertium RDF ES-AST took 1.2227683067321777s
Security | Check HTTPS for Apertium RDF ES-AST took 0.1329951286315918s
Interpretability | RDF structures check for Apertium RDF ES-AST took 0.27611756324768066s
Versatility | Serialization formats check for Apertium RDF ES-AST took 0.26753783226013184s
Availability | RDF dump link check for Apertium RDF ES-AST took 0.2851994037628174s
License | MR license check for Apertium RDF ES-AST took 0.2824745178222656s
License | HR license check for Apertium RDF ES-AST took 0.3590219020843506s
Amount of data | Number of property check for Apertium RDF ES-AST took 0.278109073638916s
Understandability | Number of label check for Apertium RDF ES-AST took 0.32228565216064453s
Understandability | URI regex check for Apertium RDF ES-AST took 0.5354678630828857s
Understandability | Vocabs check for Apertium RDF ES-AST took 0.273576021194458s
Verifiability | Authors check for Apertium RDF ES-AST took 0.2783479690551758s
Verifiability | Publishers check for Apertium RDF ES-AST took 0.2639336585998535s
Performance | Throughput check for Apertium RDF ES-AST took 11.153698444366455s
Amount of data | Check the number of entities for Apertium RDF ES-AST took 7.081031799316406e-05s
Verifiability | Contribs. check for Apertium RDF ES-AST took 0.2823977470397949s
Interlinking | sameAs chians check for Apertium RDF ES-AST took 0.27905821800231934s
Interlinking | skos check for Apertium RDF ES-AST took 0.28336620330810547s
Interlinking | skos check for Apertium RDF ES-AST took 0.2411336898803711s
Timeliness | dataset update frequency check for Apertium RDF ES-AST took 0.26863574981689453s
Currency | Creation date check for Apertium RDF ES-AST took 0.5434799194335938s
Currency | Modification date check for Apertium RDF ES-AST took 0.5530984401702881s
Rep.Conc. | URIs length for Apertium RDF ES-AST took 58.63574934005737s
Interoperability | New vocabularies check for Apertium RDF ES-AST took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-AST took 0.29366397857666016s
Accuracy | Check Functional Property for Apertium RDF ES-AST took 0.2702140808105469s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-AST took 0.27974534034729004s
Accuracy | Check Empty annotation labels for Apertium RDF ES-AST took 0.9699335098266602s
Accuracy | Check White space in annotation for Apertium RDF ES-AST took 0.01036834716796875s
Accuracy | Check Datatype consistency for Apertium RDF ES-AST took 2.709357976913452s
Consistency | Disjoint class check for Apertium RDF ES-AST took 0.3019280433654785s
Consistency | Check Misplaced properties for Apertium RDF ES-AST took 4.680490732192993s
Consistency | Misplaced classes for Apertium RDF ES-AST took 8.652740240097046s
Consistency | Check Ontology hijacking for Apertium RDF ES-AST took 44.34994673728943s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-AST took 1.7194294929504395s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-AST took 5.992154359817505s
Conciseness | Check Extensional conciseness for Apertium RDF ES-AST took 2.9521548748016357s
Conciseness | Check Intensional conciseness for Apertium RDF ES-AST took 0.3396451473236084s
Security | Sign check for Apertium RDF ES-AST took 0.2701847553253174s
Availability | Check URIs Dereferenciability for Apertium RDF ES-AST took 9.825947999954224s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.4810466766357422s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.021138906478881836s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.935264587402344e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-AST took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF ES-AST took 1.0728836059570312e-05s
INFO | --- Analysis for apertium-rdf-es-ast took 624.9508180618286s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 0.21983909606933594s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0007653236389160156s
Extra | Recovery of all triples for Apertium RDF ES-CA took 162.0172905921936s
Performance | Total latancy measurement for Apertium RDF ES-CA took 1.2312872409820557s
Amount of data | Number of triples check for Apertium RDF ES-CA took 2.2361817359924316s
Interoperability | New terms check for Apertium RDF ES-CA took 3.095139503479004s
Versatility | Languages check for Apertium RDF ES-CA took 44.5915253162384s
Interpretability | Number of blank nodes check for Apertium RDF ES-CA took 1.074782133102417s
Security | Check HTTPS for Apertium RDF ES-CA took 0.1448056697845459s
Interpretability | RDF structures check for Apertium RDF ES-CA took 0.27803683280944824s
Versatility | Serialization formats check for Apertium RDF ES-CA took 0.2695779800415039s
Availability | RDF dump link check for Apertium RDF ES-CA took 0.2912883758544922s
License | MR license check for Apertium RDF ES-CA took 0.2777750492095947s
License | HR license check for Apertium RDF ES-CA took 0.3573575019836426s
Amount of data | Number of property check for Apertium RDF ES-CA took 0.28574657440185547s
Understandability | Number of label check for Apertium RDF ES-CA took 0.3177523612976074s
Understandability | URI regex check for Apertium RDF ES-CA took 0.5594654083251953s
Understandability | Vocabs check for Apertium RDF ES-CA took 0.27120518684387207s
Verifiability | Authors check for Apertium RDF ES-CA took 0.27080631256103516s
Verifiability | Publishers check for Apertium RDF ES-CA took 0.2780299186706543s
Performance | Throughput check for Apertium RDF ES-CA took 11.017431735992432s
Amount of data | Check the number of entities for Apertium RDF ES-CA took 7.224082946777344e-05s
Verifiability | Contribs. check for Apertium RDF ES-CA took 0.2680642604827881s
Interlinking | sameAs chians check for Apertium RDF ES-CA took 0.2809128761291504s
Interlinking | skos check for Apertium RDF ES-CA took 0.27573132514953613s
Interlinking | skos check for Apertium RDF ES-CA took 0.215958833694458s
Timeliness | dataset update frequency check for Apertium RDF ES-CA took 0.2635498046875s
Currency | Creation date check for Apertium RDF ES-CA took 0.5530300140380859s
Currency | Modification date check for Apertium RDF ES-CA took 0.5507187843322754s
Rep.Conc. | URIs length for Apertium RDF ES-CA took 59.312071800231934s
Interoperability | New vocabularies check for Apertium RDF ES-CA took 1.33514404296875e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-CA took 0.29956984519958496s
Accuracy | Check Functional Property for Apertium RDF ES-CA took 0.2755908966064453s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-CA took 0.2646346092224121s
Accuracy | Check Empty annotation labels for Apertium RDF ES-CA took 1.0207321643829346s
Accuracy | Check White space in annotation for Apertium RDF ES-CA took 0.01059103012084961s
Accuracy | Check Datatype consistency for Apertium RDF ES-CA took 2.7885403633117676s
Consistency | Disjoint class check for Apertium RDF ES-CA took 0.27614307403564453s
Consistency | Check Misplaced properties for Apertium RDF ES-CA took 4.680782079696655s
Consistency | Misplaced classes for Apertium RDF ES-CA took 8.8054039478302s
Consistency | Check Ontology hijacking for Apertium RDF ES-CA took 46.92809009552002s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-CA took 1.7032604217529297s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-CA took 5.889324188232422s
Conciseness | Check Extensional conciseness for Apertium RDF ES-CA took 3.03611159324646s
Conciseness | Check Intensional conciseness for Apertium RDF ES-CA took 0.28235793113708496s
Security | Sign check for Apertium RDF ES-CA took 0.2825636863708496s
Availability | Check URIs Dereferenciability for Apertium RDF ES-CA took 9.639632940292358s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 1.075334072113037s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.02102208137512207s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.839897155761719e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-CA took 2.384185791015625e-06s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.33514404296875e-05s
INFO | --- Analysis for apertium-rdf-es-ca took 621.0418856143951s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.172325134277344e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 25.61143732070923s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.02202439308166504s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.649162292480469e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-es-gl took 200.66379594802856s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 0.29549431800842285s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0006885528564453125s
Extra | Recovery of all triples for Apertium RDF ES-PT took 160.9031217098236s
Performance | Total latancy measurement for Apertium RDF ES-PT took 1.1965570449829102s
Amount of data | Number of triples check for Apertium RDF ES-PT took 2.1770169734954834s
Interoperability | New terms check for Apertium RDF ES-PT took 3.1744637489318848s
Versatility | Languages check for Apertium RDF ES-PT took 44.592315673828125s
Interpretability | Number of blank nodes check for Apertium RDF ES-PT took 1.218804121017456s
Security | Check HTTPS for Apertium RDF ES-PT took 0.14573025703430176s
Interpretability | RDF structures check for Apertium RDF ES-PT took 0.28959035873413086s
Versatility | Serialization formats check for Apertium RDF ES-PT took 0.2833695411682129s
Availability | RDF dump link check for Apertium RDF ES-PT took 0.2821028232574463s
License | MR license check for Apertium RDF ES-PT took 0.2809007167816162s
License | HR license check for Apertium RDF ES-PT took 0.3594677448272705s
Amount of data | Number of property check for Apertium RDF ES-PT took 0.27484750747680664s
Understandability | Number of label check for Apertium RDF ES-PT took 0.2992546558380127s
Understandability | URI regex check for Apertium RDF ES-PT took 0.5319805145263672s
Understandability | Vocabs check for Apertium RDF ES-PT took 0.29895782470703125s
Verifiability | Authors check for Apertium RDF ES-PT took 0.28748559951782227s
Verifiability | Publishers check for Apertium RDF ES-PT took 0.27280259132385254s
Performance | Throughput check for Apertium RDF ES-PT took 11.088501453399658s
Amount of data | Check the number of entities for Apertium RDF ES-PT took 5.1975250244140625e-05s
Verifiability | Contribs. check for Apertium RDF ES-PT took 0.2687697410583496s
Interlinking | sameAs chians check for Apertium RDF ES-PT took 0.2763671875s
Interlinking | skos check for Apertium RDF ES-PT took 0.28169751167297363s
Interlinking | skos check for Apertium RDF ES-PT took 0.24195313453674316s
Timeliness | dataset update frequency check for Apertium RDF ES-PT took 0.28087496757507324s
Currency | Creation date check for Apertium RDF ES-PT took 0.5710968971252441s
Currency | Modification date check for Apertium RDF ES-PT took 0.5732362270355225s
Rep.Conc. | URIs length for Apertium RDF ES-PT took 58.65184307098389s
Interoperability | New vocabularies check for Apertium RDF ES-PT took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF ES-PT took 0.30902791023254395s
Accuracy | Check Functional Property for Apertium RDF ES-PT took 0.25879979133605957s
Accuracy | Check Inverse Functional Property for Apertium RDF ES-PT took 0.27650952339172363s
Accuracy | Check Empty annotation labels for Apertium RDF ES-PT took 0.9634969234466553s
Accuracy | Check White space in annotation for Apertium RDF ES-PT took 0.01034855842590332s
Accuracy | Check Datatype consistency for Apertium RDF ES-PT took 2.709399461746216s
Consistency | Disjoint class check for Apertium RDF ES-PT took 0.2690761089324951s
Consistency | Check Misplaced properties for Apertium RDF ES-PT took 4.676162004470825s
Consistency | Misplaced classes for Apertium RDF ES-PT took 8.641030073165894s
Consistency | Check Ontology hijacking for Apertium RDF ES-PT took 44.49181246757507s
Consistency | Check Invalid usage of undefined classes for Apertium RDF ES-PT took 1.6941742897033691s
Consistency | Check Invalid usage of undefined properties for Apertium RDF ES-PT took 6.028682470321655s
Conciseness | Check Extensional conciseness for Apertium RDF ES-PT took 2.9557971954345703s
Conciseness | Check Intensional conciseness for Apertium RDF ES-PT took 0.31412267684936523s
Security | Sign check for Apertium RDF ES-PT took 0.29204583168029785s
Availability | Check URIs Dereferenciability for Apertium RDF ES-PT took 10.026532649993896s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.46138930320739746s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.021055221557617188s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.744529724121094e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF ES-PT took 2.1457672119140625e-06s
Believability | Calculation of trust value for Apertium RDF ES-PT took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 521.6282644271851s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 23.837608814239502s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.021736621856689453s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 8.559226989746094e-05s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 5.125999450683594e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-es-ro took 208.4546353816986s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 0.2896397113800049s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0006833076477050781s
Extra | Recovery of all triples for Apertium RDF EU-EN took 160.21154928207397s
Performance | Total latancy measurement for Apertium RDF EU-EN took 1.1939613819122314s
Amount of data | Number of triples check for Apertium RDF EU-EN took 2.213076591491699s
Interoperability | New terms check for Apertium RDF EU-EN took 3.152621030807495s
Versatility | Languages check for Apertium RDF EU-EN took 44.503061294555664s
Interpretability | Number of blank nodes check for Apertium RDF EU-EN took 1.2683942317962646s
Security | Check HTTPS for Apertium RDF EU-EN took 0.1449434757232666s
Interpretability | RDF structures check for Apertium RDF EU-EN took 0.2905895709991455s
Versatility | Serialization formats check for Apertium RDF EU-EN took 0.278822660446167s
Availability | RDF dump link check for Apertium RDF EU-EN took 0.2906358242034912s
License | MR license check for Apertium RDF EU-EN took 0.29313111305236816s
License | HR license check for Apertium RDF EU-EN took 0.37961649894714355s
Amount of data | Number of property check for Apertium RDF EU-EN took 0.2906367778778076s
Understandability | Number of label check for Apertium RDF EU-EN took 0.3003346920013428s
Understandability | URI regex check for Apertium RDF EU-EN took 0.5827999114990234s
Understandability | Vocabs check for Apertium RDF EU-EN took 0.28761863708496094s
Verifiability | Authors check for Apertium RDF EU-EN took 0.2899208068847656s
Verifiability | Publishers check for Apertium RDF EU-EN took 0.2785515785217285s
Performance | Throughput check for Apertium RDF EU-EN took 11.2457435131073s
Amount of data | Check the number of entities for Apertium RDF EU-EN took 3.170967102050781e-05s
Verifiability | Contribs. check for Apertium RDF EU-EN took 0.27825236320495605s
Interlinking | sameAs chians check for Apertium RDF EU-EN took 0.29239797592163086s
Interlinking | skos check for Apertium RDF EU-EN took 0.2803943157196045s
Interlinking | skos check for Apertium RDF EU-EN took 0.25447630882263184s
Timeliness | dataset update frequency check for Apertium RDF EU-EN took 0.28878259658813477s
Currency | Creation date check for Apertium RDF EU-EN took 0.5707447528839111s
Currency | Modification date check for Apertium RDF EU-EN took 0.554903507232666s
Rep.Conc. | URIs length for Apertium RDF EU-EN took 61.5209903717041s
Interoperability | New vocabularies check for Apertium RDF EU-EN took 1.2636184692382812e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF EU-EN took 0.3109898567199707s
Accuracy | Check Functional Property for Apertium RDF EU-EN took 0.32355666160583496s
Accuracy | Check Inverse Functional Property for Apertium RDF EU-EN took 0.29035258293151855s
Accuracy | Check Empty annotation labels for Apertium RDF EU-EN took 0.971668004989624s
Accuracy | Check White space in annotation for Apertium RDF EU-EN took 0.010516166687011719s
Accuracy | Check Datatype consistency for Apertium RDF EU-EN took 2.732865810394287s
Consistency | Disjoint class check for Apertium RDF EU-EN took 0.2854335308074951s
Consistency | Check Misplaced properties for Apertium RDF EU-EN took 4.593918800354004s
Consistency | Misplaced classes for Apertium RDF EU-EN took 8.724555015563965s
Consistency | Check Ontology hijacking for Apertium RDF EU-EN took 44.523720502853394s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EU-EN took 1.6971874237060547s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EU-EN took 5.918456315994263s
Conciseness | Check Extensional conciseness for Apertium RDF EU-EN took 2.9491286277770996s
Conciseness | Check Intensional conciseness for Apertium RDF EU-EN took 0.27110958099365234s
Security | Sign check for Apertium RDF EU-EN took 0.2839775085449219s
Availability | Check URIs Dereferenciability for Apertium RDF EU-EN took 10.049009084701538s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.4794430732727051s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.021462440490722656s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 5.2928924560546875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EU-EN took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF EU-EN took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-eu-en took 501.64249873161316s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 0.21983814239501953s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0008635520935058594s
Extra | Recovery of all triples for Apertium RDF EU-ES took 165.70755124092102s
Performance | Total latancy measurement for Apertium RDF EU-ES took 1.2309386730194092s
Amount of data | Number of triples check for Apertium RDF EU-ES took 2.1717145442962646s
Interoperability | New terms check for Apertium RDF EU-ES took 3.1242692470550537s
Versatility | Languages check for Apertium RDF EU-ES took 44.57327198982239s
Interpretability | Number of blank nodes check for Apertium RDF EU-ES took 1.2248106002807617s
Security | Check HTTPS for Apertium RDF EU-ES took 0.13307762145996094s
Interpretability | RDF structures check for Apertium RDF EU-ES took 0.2857511043548584s
Versatility | Serialization formats check for Apertium RDF EU-ES took 0.2888779640197754s
Availability | RDF dump link check for Apertium RDF EU-ES took 0.28017377853393555s
License | MR license check for Apertium RDF EU-ES took 0.29918694496154785s
License | HR license check for Apertium RDF EU-ES took 0.3868978023529053s
Amount of data | Number of property check for Apertium RDF EU-ES took 0.273425817489624s
Understandability | Number of label check for Apertium RDF EU-ES took 0.3172280788421631s
Understandability | URI regex check for Apertium RDF EU-ES took 0.539747953414917s
Understandability | Vocabs check for Apertium RDF EU-ES took 0.27968382835388184s
Verifiability | Authors check for Apertium RDF EU-ES took 0.2890458106994629s
Verifiability | Publishers check for Apertium RDF EU-ES took 0.2832019329071045s
Performance | Throughput check for Apertium RDF EU-ES took 11.120732545852661s
Amount of data | Check the number of entities for Apertium RDF EU-ES took 7.557868957519531e-05s
Verifiability | Contribs. check for Apertium RDF EU-ES took 0.2932271957397461s
Interlinking | sameAs chians check for Apertium RDF EU-ES took 0.26322269439697266s
Interlinking | skos check for Apertium RDF EU-ES took 0.3105933666229248s
Interlinking | skos check for Apertium RDF EU-ES took 0.2293086051940918s
Timeliness | dataset update frequency check for Apertium RDF EU-ES took 0.2735936641693115s
Currency | Creation date check for Apertium RDF EU-ES took 0.5416300296783447s
Currency | Modification date check for Apertium RDF EU-ES took 0.5592832565307617s
Rep.Conc. | URIs length for Apertium RDF EU-ES took 59.269307136535645s
Interoperability | New vocabularies check for Apertium RDF EU-ES took 1.33514404296875e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF EU-ES took 0.288224458694458s
Accuracy | Check Functional Property for Apertium RDF EU-ES took 0.2685420513153076s
Accuracy | Check Inverse Functional Property for Apertium RDF EU-ES took 0.27939915657043457s
Accuracy | Check Empty annotation labels for Apertium RDF EU-ES took 0.9338958263397217s
Accuracy | Check White space in annotation for Apertium RDF EU-ES took 0.0106048583984375s
Accuracy | Check Datatype consistency for Apertium RDF EU-ES took 2.792393445968628s
Consistency | Disjoint class check for Apertium RDF EU-ES took 0.28778624534606934s
Consistency | Check Misplaced properties for Apertium RDF EU-ES took 4.688937664031982s
Consistency | Misplaced classes for Apertium RDF EU-ES took 8.717916250228882s
Consistency | Check Ontology hijacking for Apertium RDF EU-ES took 44.615463972091675s
Consistency | Check Invalid usage of undefined classes for Apertium RDF EU-ES took 1.7112982273101807s
Consistency | Check Invalid usage of undefined properties for Apertium RDF EU-ES took 5.80008864402771s
Conciseness | Check Extensional conciseness for Apertium RDF EU-ES took 3.0515055656433105s
Conciseness | Check Intensional conciseness for Apertium RDF EU-ES took 0.294863224029541s
Security | Sign check for Apertium RDF EU-ES took 0.2701129913330078s
Availability | Check URIs Dereferenciability for Apertium RDF EU-ES took 10.413815975189209s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.48505616188049316s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.02140188217163086s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.9114227294921875e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF EU-ES took 2.384185791015625e-06s
Believability | Calculation of trust value for Apertium RDF EU-ES took 1.6450881958007812e-05s
INFO | --- Analysis for apertium-rdf-eu-es took 477.01867270469666s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 0.22866606712341309s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0007171630859375s
Extra | Recovery of all triples for Apertium RDF FR-CA took 162.00509643554688s
Performance | Total latancy measurement for Apertium RDF FR-CA took 1.206895112991333s
Amount of data | Number of triples check for Apertium RDF FR-CA took 2.1947405338287354s
Interoperability | New terms check for Apertium RDF FR-CA took 3.0758605003356934s
Versatility | Languages check for Apertium RDF FR-CA took 44.436052083969116s
Interpretability | Number of blank nodes check for Apertium RDF FR-CA took 1.066117763519287s
Security | Check HTTPS for Apertium RDF FR-CA took 0.14438223838806152s
Interpretability | RDF structures check for Apertium RDF FR-CA took 0.2873213291168213s
Versatility | Serialization formats check for Apertium RDF FR-CA took 0.2906181812286377s
Availability | RDF dump link check for Apertium RDF FR-CA took 0.2833249568939209s
License | MR license check for Apertium RDF FR-CA took 0.2861642837524414s
License | HR license check for Apertium RDF FR-CA took 0.3742797374725342s
Amount of data | Number of property check for Apertium RDF FR-CA took 0.28563737869262695s
Understandability | Number of label check for Apertium RDF FR-CA took 0.3363628387451172s
Understandability | URI regex check for Apertium RDF FR-CA took 0.5782308578491211s
Understandability | Vocabs check for Apertium RDF FR-CA took 0.2788395881652832s
Verifiability | Authors check for Apertium RDF FR-CA took 0.2774677276611328s
Verifiability | Publishers check for Apertium RDF FR-CA took 0.28173375129699707s
Performance | Throughput check for Apertium RDF FR-CA took 11.189303159713745s
Amount of data | Check the number of entities for Apertium RDF FR-CA took 0.00011372566223144531s
Verifiability | Contribs. check for Apertium RDF FR-CA took 0.29479503631591797s
Interlinking | sameAs chians check for Apertium RDF FR-CA took 0.2840845584869385s
Interlinking | skos check for Apertium RDF FR-CA took 0.3314485549926758s
Interlinking | skos check for Apertium RDF FR-CA took 0.2304832935333252s
Timeliness | dataset update frequency check for Apertium RDF FR-CA took 0.2853860855102539s
Currency | Creation date check for Apertium RDF FR-CA took 0.5994930267333984s
Currency | Modification date check for Apertium RDF FR-CA took 0.5835652351379395s
Rep.Conc. | URIs length for Apertium RDF FR-CA took 60.0600380897522s
Interoperability | New vocabularies check for Apertium RDF FR-CA took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Apertium RDF FR-CA took 0.3043978214263916s
Accuracy | Check Functional Property for Apertium RDF FR-CA took 0.2674894332885742s
Accuracy | Check Inverse Functional Property for Apertium RDF FR-CA took 0.28584766387939453s
Accuracy | Check Empty annotation labels for Apertium RDF FR-CA took 0.9480884075164795s
Accuracy | Check White space in annotation for Apertium RDF FR-CA took 0.01043558120727539s
Accuracy | Check Datatype consistency for Apertium RDF FR-CA took 2.7977309226989746s
Consistency | Disjoint class check for Apertium RDF FR-CA took 0.2692101001739502s
Consistency | Check Misplaced properties for Apertium RDF FR-CA took 4.656938076019287s
Consistency | Misplaced classes for Apertium RDF FR-CA took 8.6979341506958s
Consistency | Check Ontology hijacking for Apertium RDF FR-CA took 44.90068864822388s
Consistency | Check Invalid usage of undefined classes for Apertium RDF FR-CA took 1.7239990234375s
Consistency | Check Invalid usage of undefined properties for Apertium RDF FR-CA took 5.82073712348938s
Conciseness | Check Extensional conciseness for Apertium RDF FR-CA took 3.128934621810913s
Conciseness | Check Intensional conciseness for Apertium RDF FR-CA took 0.29939723014831543s
Security | Sign check for Apertium RDF FR-CA took 0.28955626487731934s
Availability | Check URIs Dereferenciability for Apertium RDF FR-CA took 10.321662664413452s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.4574897289276123s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.02151179313659668s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 5.0067901611328125e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF FR-CA took 1.6689300537109375e-06s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-fr-ca took 592.2283232212067s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 9.083747863769531e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0007226467132568359s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 25.453485250473022s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020936965942382812s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 5.626678466796875e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.2874603271484375e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 106.42836475372314s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 0.27840471267700195s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0007410049438476562s
Extra | Recovery of all triples for Apertium RDF OC-CA took 159.1997058391571s
Performance | Total latancy measurement for Apertium RDF OC-CA took 1.2039995193481445s
Amount of data | Number of triples check for Apertium RDF OC-CA took 2.153348684310913s
Interoperability | New terms check for Apertium RDF OC-CA took 3.375765800476074s
Versatility | Languages check for Apertium RDF OC-CA took 44.20062470436096s
Interpretability | Number of blank nodes check for Apertium RDF OC-CA took 1.2627942562103271s
Security | Check HTTPS for Apertium RDF OC-CA took 0.12179064750671387s
Interpretability | RDF structures check for Apertium RDF OC-CA took 0.2840383052825928s
Versatility | Serialization formats check for Apertium RDF OC-CA took 0.28273630142211914s
Availability | RDF dump link check for Apertium RDF OC-CA took 0.2918105125427246s
License | MR license check for Apertium RDF OC-CA took 0.3029665946960449s
License | HR license check for Apertium RDF OC-CA took 0.3636295795440674s
Amount of data | Number of property check for Apertium RDF OC-CA took 0.29047584533691406s
Understandability | Number of label check for Apertium RDF OC-CA took 0.306535005569458s
Understandability | URI regex check for Apertium RDF OC-CA took 0.5504062175750732s
Understandability | Vocabs check for Apertium RDF OC-CA took 0.2825653553009033s
Verifiability | Authors check for Apertium RDF OC-CA took 0.2921433448791504s
Verifiability | Publishers check for Apertium RDF OC-CA took 0.26996350288391113s
Performance | Throughput check for Apertium RDF OC-CA took 11.252300500869751s
Amount of data | Check the number of entities for Apertium RDF OC-CA took 7.343292236328125e-05s
Verifiability | Contribs. check for Apertium RDF OC-CA took 0.26322197914123535s
Interlinking | sameAs chians check for Apertium RDF OC-CA took 0.29160523414611816s
Interlinking | skos check for Apertium RDF OC-CA took 0.2897977828979492s
Interlinking | skos check for Apertium RDF OC-CA took 0.22316741943359375s
Timeliness | dataset update frequency check for Apertium RDF OC-CA took 0.2815248966217041s
Currency | Creation date check for Apertium RDF OC-CA took 0.5829133987426758s
Currency | Modification date check for Apertium RDF OC-CA took 0.5518724918365479s
Rep.Conc. | URIs length for Apertium RDF OC-CA took 58.589574337005615s
Interoperability | New vocabularies check for Apertium RDF OC-CA took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF OC-CA took 0.3091399669647217s
Accuracy | Check Functional Property for Apertium RDF OC-CA took 0.27978062629699707s
Accuracy | Check Inverse Functional Property for Apertium RDF OC-CA took 0.28156447410583496s
Accuracy | Check Empty annotation labels for Apertium RDF OC-CA took 1.025768756866455s
Accuracy | Check White space in annotation for Apertium RDF OC-CA took 0.010651826858520508s
Accuracy | Check Datatype consistency for Apertium RDF OC-CA took 2.7007594108581543s
Consistency | Disjoint class check for Apertium RDF OC-CA took 0.2685074806213379s
Consistency | Check Misplaced properties for Apertium RDF OC-CA took 4.599158525466919s
Consistency | Misplaced classes for Apertium RDF OC-CA took 8.57955813407898s
Consistency | Check Ontology hijacking for Apertium RDF OC-CA took 44.07644772529602s
Consistency | Check Invalid usage of undefined classes for Apertium RDF OC-CA took 1.7001066207885742s
Consistency | Check Invalid usage of undefined properties for Apertium RDF OC-CA took 5.961536169052124s
Conciseness | Check Extensional conciseness for Apertium RDF OC-CA took 2.947533369064331s
Conciseness | Check Intensional conciseness for Apertium RDF OC-CA took 0.3236098289489746s
Security | Sign check for Apertium RDF OC-CA took 0.28720545768737793s
Availability | Check URIs Dereferenciability for Apertium RDF OC-CA took 10.038549423217773s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.4750335216522217s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.02097320556640625s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.792213439941406e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF OC-CA took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.0967254638671875e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 458.8733687400818s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 9.226799011230469e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0007052421569824219s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 29.9697003364563s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.020769596099853516s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.673004150390625e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-oc-es took 120.51716089248657s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 8.463859558105469e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 28.206703186035156s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.020720243453979492s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.6253204345703125e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.4066696166992188e-05s
INFO | --- Analysis for apertium-rdf-pt-ca took 112.17850255966187s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 0.2210237979888916s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0006589889526367188s
Extra | Recovery of all triples for Apertium RDF PT-GL took 160.28278422355652s
Performance | Total latancy measurement for Apertium RDF PT-GL took 1.2717697620391846s
Amount of data | Number of triples check for Apertium RDF PT-GL took 2.113710403442383s
Interoperability | New terms check for Apertium RDF PT-GL took 3.354715585708618s
Versatility | Languages check for Apertium RDF PT-GL took 44.82362222671509s
Interpretability | Number of blank nodes check for Apertium RDF PT-GL took 1.1842296123504639s
Security | Check HTTPS for Apertium RDF PT-GL took 0.13316845893859863s
Interpretability | RDF structures check for Apertium RDF PT-GL took 0.31076955795288086s
Versatility | Serialization formats check for Apertium RDF PT-GL took 0.28400087356567383s
Availability | RDF dump link check for Apertium RDF PT-GL took 0.28047990798950195s
License | MR license check for Apertium RDF PT-GL took 0.2865874767303467s
License | HR license check for Apertium RDF PT-GL took 0.3657526969909668s
Amount of data | Number of property check for Apertium RDF PT-GL took 0.28901004791259766s
Understandability | Number of label check for Apertium RDF PT-GL took 0.33005452156066895s
Understandability | URI regex check for Apertium RDF PT-GL took 0.5630321502685547s
Understandability | Vocabs check for Apertium RDF PT-GL took 0.2797362804412842s
Verifiability | Authors check for Apertium RDF PT-GL took 0.2732574939727783s
Verifiability | Publishers check for Apertium RDF PT-GL took 0.28095316886901855s
Performance | Throughput check for Apertium RDF PT-GL took 11.247270107269287s
Amount of data | Check the number of entities for Apertium RDF PT-GL took 7.414817810058594e-05s
Verifiability | Contribs. check for Apertium RDF PT-GL took 0.2879788875579834s
Interlinking | sameAs chians check for Apertium RDF PT-GL took 0.2734107971191406s
Interlinking | skos check for Apertium RDF PT-GL took 0.281125545501709s
Interlinking | skos check for Apertium RDF PT-GL took 0.24351954460144043s
Timeliness | dataset update frequency check for Apertium RDF PT-GL took 0.27828025817871094s
Currency | Creation date check for Apertium RDF PT-GL took 0.5353024005889893s
Currency | Modification date check for Apertium RDF PT-GL took 0.5831875801086426s
Rep.Conc. | URIs length for Apertium RDF PT-GL took 58.80522418022156s
Interoperability | New vocabularies check for Apertium RDF PT-GL took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Apertium RDF PT-GL took 0.5826244354248047s
Accuracy | Check Functional Property for Apertium RDF PT-GL took 0.2897346019744873s
Accuracy | Check Inverse Functional Property for Apertium RDF PT-GL took 0.28209805488586426s
Accuracy | Check Empty annotation labels for Apertium RDF PT-GL took 0.969402551651001s
Accuracy | Check White space in annotation for Apertium RDF PT-GL took 0.010572195053100586s
Accuracy | Check Datatype consistency for Apertium RDF PT-GL took 2.7093594074249268s
Consistency | Disjoint class check for Apertium RDF PT-GL took 0.30348896980285645s
Consistency | Check Misplaced properties for Apertium RDF PT-GL took 4.571489334106445s
Consistency | Misplaced classes for Apertium RDF PT-GL took 8.603998899459839s
Consistency | Check Ontology hijacking for Apertium RDF PT-GL took 44.161349058151245s
Consistency | Check Invalid usage of undefined classes for Apertium RDF PT-GL took 1.6965043544769287s
Consistency | Check Invalid usage of undefined properties for Apertium RDF PT-GL took 5.960338354110718s
Conciseness | Check Extensional conciseness for Apertium RDF PT-GL took 3.029559850692749s
Conciseness | Check Intensional conciseness for Apertium RDF PT-GL took 0.29874086380004883s
Security | Sign check for Apertium RDF PT-GL took 0.27227163314819336s
Availability | Check URIs Dereferenciability for Apertium RDF PT-GL took 9.605159997940063s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.4897797107696533s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.02135944366455078s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.839897155761719e-05s
Interoperability | Check the re-using of existing vocabs for Apertium RDF PT-GL took 1.9073486328125e-06s
Believability | Calculation of trust value for Apertium RDF PT-GL took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-pt-gl took 679.091117143631s
Availability | SPARQL endpoint availability check for AragoDBpedia - aragon open data took 0.56325364112854s
Availability | VoID file availability check for AragoDBpedia - aragon open data took 0.0006809234619140625s
Extra | Recovery of all triples for AragoDBpedia - aragon open data took 3.5916597843170166s
Performance | Total latancy measurement for AragoDBpedia - aragon open data took 1.602849006652832s
Amount of data | Number of triples check for AragoDBpedia - aragon open data took 0.7366890907287598s
Interoperability | New terms check for AragoDBpedia - aragon open data took 2.198134422302246s
Versatility | Languages check for AragoDBpedia - aragon open data took 60.44190573692322s
Interpretability | Number of blank nodes check for AragoDBpedia - aragon open data took 4.157399415969849s
Security | Check HTTPS for AragoDBpedia - aragon open data took 0.23269128799438477s
Interpretability | RDF structures check for AragoDBpedia - aragon open data took 0.6968872547149658s
Versatility | Serialization formats check for AragoDBpedia - aragon open data took 0.7885479927062988s
Availability | RDF dump link check for AragoDBpedia - aragon open data took 0.341799259185791s
License | MR license check for AragoDBpedia - aragon open data took 0.7115881443023682s
License | HR license check for AragoDBpedia - aragon open data took 8.028987884521484s
Amount of data | Number of property check for AragoDBpedia - aragon open data took 0.33040475845336914s
Understandability | Number of label check for AragoDBpedia - aragon open data took 0.533254861831665s
Understandability | URI regex check for AragoDBpedia - aragon open data took 0.8143231868743896s
Understandability | Vocabs check for AragoDBpedia - aragon open data took 0.4342021942138672s
Verifiability | Authors check for AragoDBpedia - aragon open data took 0.5066943168640137s
Verifiability | Publishers check for AragoDBpedia - aragon open data took 0.3398122787475586s
Performance | Throughput check for AragoDBpedia - aragon open data took 12.374841690063477s
Amount of data | Check the number of entities for AragoDBpedia - aragon open data took 8.511543273925781e-05s
Verifiability | Contribs. check for AragoDBpedia - aragon open data took 0.4790635108947754s
Interlinking | sameAs chians check for AragoDBpedia - aragon open data took 0.41387414932250977s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.555628776550293s
Interlinking | skos check for AragoDBpedia - aragon open data took 0.31328439712524414s
Timeliness | dataset update frequency check for AragoDBpedia - aragon open data took 0.42893195152282715s
Currency | Creation date check for AragoDBpedia - aragon open data took 1.0562071800231934s
Currency | Modification date check for AragoDBpedia - aragon open data took 0.3503842353820801s
Rep.Conc. | URIs length for AragoDBpedia - aragon open data took 5.572421312332153s
Interoperability | New vocabularies check for AragoDBpedia - aragon open data took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for AragoDBpedia - aragon open data took 0.34082889556884766s
Accuracy | Check Functional Property for AragoDBpedia - aragon open data took 0.41683483123779297s
Accuracy | Check Inverse Functional Property for AragoDBpedia - aragon open data took 0.39136505126953125s
Accuracy | Check Datatype consistency for AragoDBpedia - aragon open data took 0.032636404037475586s
Consistency | Disjoint class check for AragoDBpedia - aragon open data took 0.3519132137298584s
Consistency | Check Misplaced properties for AragoDBpedia - aragon open data took 4.161203861236572s
Consistency | Misplaced classes for AragoDBpedia - aragon open data took 0.5411734580993652s
Consistency | Check Ontology hijacking for AragoDBpedia - aragon open data took 2.6075961589813232s
Consistency | Check Invalid usage of undefined classes for AragoDBpedia - aragon open data took 1.632136583328247s
Consistency | Check Invalid usage of undefined properties for AragoDBpedia - aragon open data took 5.376922845840454s
Conciseness | Check Extensional conciseness for AragoDBpedia - aragon open data took 0.034217119216918945s
Conciseness | Check Intensional conciseness for AragoDBpedia - aragon open data took 0.6157941818237305s
Security | Sign check for AragoDBpedia - aragon open data took 0.5593278408050537s
Availability | Check URIs Dereferenciability for AragoDBpedia - aragon open data took 2717.6187105178833s
Completeness | Calculation of interlinking completeness for AragoDBpedia - aragon open data took 31.07655119895935s
Reputation | Calculation of the PageRank for AragoDBpedia - aragon open data took 0.02175736427307129s
Interlinking | Calculation of Degree of Connection for AragoDBpedia - aragon open data took 2.6226043701171875e-05s
Interlinking | Calculation of Centrality for AragoDBpedia - aragon open data took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for AragoDBpedia - aragon open data took 4.839897155761719e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBpedia - aragon open data took 1.1920928955078125e-06s
Believability | Calculation of trust value for AragoDBpedia - aragon open data took 1.2874603271484375e-05s
INFO | --- Analysis for aragodbpedia took 3142.476597547531s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.22983431816101s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0008463859558105469s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.3020656108856201s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.0230867862701416s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.14984130859375e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 1.1682510375976562e-05s
INFO | --- Analysis for archiveshub-linkeddata took 131.81408786773682s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 95.59861421585083s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0007791519165039062s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 28.795633792877197s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.020975112915039062s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 3.933906555175781e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 1.1920928955078125e-05s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 801.5155961513519s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 250.5438666343689s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007138252258300781s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 23.249480962753296s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.02126026153564453s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 5.8650970458984375e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.2159347534179688e-05s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 662.2461340427399s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 8.869171142578125e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007321834564208984s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.3668212890625s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.021259784698486328s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00010800361633300781s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.1920928955078125e-05s
INFO | --- Analysis for artenuevosmedios-gnoss took 201.29212164878845s
Availability | SPARQL endpoint availability check for Arthroscopy community took 9.775161743164062e-05s
Availability | VoID file availability check for Arthroscopy community took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 27.382776260375977s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.020870447158813477s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.0001125335693359375s
Believability | Calculation of trust value for Arthroscopy community took 1.2159347534179688e-05s
INFO | --- Analysis for arthroscopy took 173.52720546722412s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 0.5025930404663086s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0006625652313232422s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 19.76470446586609s
Performance | Total latancy measurement for Wikidata entry for Art × Science International took 0.8781828880310059s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 60.51494312286377s
Interoperability | New terms check for Wikidata entry for Art × Science International took 2.0696749687194824s
Versatility | Languages check for Wikidata entry for Art × Science International took 65.17045211791992s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 60.17770481109619s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.23639297485351562s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.2697145938873291s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.28211498260498047s
License | MR license check for Wikidata entry for Art × Science International took 0.19310235977172852s
License | HR license check for Wikidata entry for Art × Science International took 65.16315388679504s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.3638014793395996s
Understandability | Number of label check for Wikidata entry for Art × Science International took 65.16367483139038s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.35799098014831543s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.18120503425598145s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.4045109748840332s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.1608419418334961s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 7.152557373046875e-05s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.1841907501220703s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 24.30777931213379s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.18136167526245117s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.19306206703186035s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.18581938743591309s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.3651704788208008s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.44477200508117676s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 26.035025596618652s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.19482946395874023s
Accuracy | Check Empty annotation labels for Wikidata entry for Art × Science International took 14.135843276977539s
Accuracy | Check White space in annotation for Wikidata entry for Art × Science International took 2.721676826477051s
Accuracy | Check Datatype consistency for Wikidata entry for Art × Science International took 4.792538166046143s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.1853024959564209s
Consistency | Check Misplaced properties for Wikidata entry for Art × Science International took 21.09815526008606s
Consistency | Misplaced classes for Wikidata entry for Art × Science International took 9.141569375991821s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 39.96136116981506s
Consistency | Check Invalid usage of undefined classes for Wikidata entry for Art × Science International took 1.6099166870117188s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 9.045976638793945s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 2.8767147064208984s
Conciseness | Check Intensional conciseness for Wikidata entry for Art × Science International took 1.5794041156768799s
Security | Sign check for Wikidata entry for Art × Science International took 0.1829366683959961s
Availability | Check URIs Dereferenciability for Wikidata entry for Art × Science International took 9.105244398117065s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 29.27986979484558s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.021402835845947266s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 2.956390380859375e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 1.6689300537109375e-06s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 9.5367431640625e-06s
INFO | --- Analysis for artxscienceinternational-wikidata took 943.292382478714s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 2.997465133666992s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006997585296630859s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.3179025650024414s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020927906036376953s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.106231689453125e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.1682510375976562e-05s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 135.24445915222168s
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.118421792984009s
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.0005996227264404297s
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.3020355701446533s
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.02082085609436035s
Interlinking | Calculation of Degree of Connection for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 7.62939453125e-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.1444091796875e-05s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 91.29312896728516s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.1632468700408936s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006837844848632812s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.3250551223754883s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.021326541900634766s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.679794311523438e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.1444091796875e-05s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 160.84792828559875s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.1240458488464355s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 30.043264150619507s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.021825790405273438s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 5.054473876953125e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 1.1205673217773438e-05s
INFO | --- Analysis for ASCDC-CRB took 120.28680849075317s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.128298044204712s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007157325744628906s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.3210127353668213s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.020960092544555664s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.34600830078125e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 1.1920928955078125e-05s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 150.9785590171814s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.112621545791626s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 23.674010276794434s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.022495746612548828s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 4.1961669921875e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 1.1920928955078125e-05s
INFO | --- Analysis for ASCDC-DQOT took 116.30736088752747s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.1827304363250732s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 22.72569966316223s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.021622657775878906s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 8.225440979003906e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.7894973754882812e-05s
INFO | --- Analysis for ASCDC-IHP-WCD took 130.08793091773987s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 2.8891139030456543s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 27.89722776412964s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.02084064483642578s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 7.915496826171875e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.1920928955078125e-05s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 172.59265446662903s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.4557764530181885s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006883144378662109s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 27.514402389526367s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.02183985710144043s
Interlinking | Calculation of Degree of Connection for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.7220458984375e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.1205673217773438e-05s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 164.33836555480957s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.1737475395202637s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0006623268127441406s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 25.497068405151367s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.021239519119262695s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.435943603515625e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.1682510375976562e-05s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 152.3533844947815s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 3.2873945236206055s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0005991458892822266s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.30651354789733887s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.021318674087524414s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 6.532669067382812e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.1682510375976562e-05s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 94.31011652946472s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.166515588760376s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0006740093231201172s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.3887310028076172s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.020833492279052734s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.700920104980469e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.239776611328125e-05s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 116.0033187866211s
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.200874090194702s
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.0006582736968994141s
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.2923915386199951s
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.021518945693969727s
Interlinking | Calculation of Degree of Connection for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.0007915496826171875s
Interlinking | Calculation of Clustering coefficient for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 8.749961853027344e-05s
Believability | Calculation of trust value for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 1.0967254638671875e-05s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 131.92564630508423s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.1932218074798584s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0007264614105224609s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.2926914691925049s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.020850181579589844s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 6.461143493652344e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 1.1444091796875e-05s
INFO | --- Analysis for ASCDC_-_DNB took 67.63123154640198s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 8.96453857421875e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0005464553833007812s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.3107264041900635s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.021096229553222656s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 7.891654968261719e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.5020370483398438e-05s
INFO | --- Analysis for asit took 63.26970434188843s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 5.1021575927734375e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 24.061352491378784s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.022844791412353516s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0008258819580078125s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 4.649162292480469e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 1.1682510375976562e-05s
INFO | --- Analysis for asjp took 194.92322397232056s
Availability | SPARQL endpoint availability check for ASN:US took 1.4652047157287598s
Availability | VoID file availability check for ASN:US took 0.0005967617034912109s
Completeness | Calculation of interlinking completeness for ASN:US took 0.30097198486328125s
Reputation | Calculation of the PageRank for ASN:US took 0.021959304809570312s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for ASN:US took 8.749961853027344e-05s
Believability | Calculation of trust value for ASN:US took 9.775161743164062e-06s
INFO | --- Analysis for asn-us took 183.1837465763092s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 0.00010371208190917969s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0007970333099365234s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.34986186027526855s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.022160053253173828s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.600120544433594e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 9.298324584960938e-06s
INFO | --- Analysis for aspire-mmu took 165.5125412940979s
Availability | SPARQL endpoint availability check for associations took 9.059906005859375e-05s
Availability | VoID file availability check for associations took 0.000736236572265625s
Completeness | Calculation of interlinking completeness for associations took 24.672250032424927s
Reputation | Calculation of the PageRank for associations took 0.021320104598999023s
Interlinking | Calculation of Degree of Connection for associations took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for associations took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for associations took 7.224082946777344e-05s
Believability | Calculation of trust value for associations took 1.2159347534179688e-05s
INFO | --- Analysis for associations took 78.27703499794006s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 0.24067330360412598s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 24.682054042816162s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.02282118797302246s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 4.2438507080078125e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 1.1682510375976562e-05s
INFO | --- Analysis for atc-publikovan--s-kl took 156.01753282546997s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 8.726119995117188e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 27.225038766860962s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.02080988883972168s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 9.393692016601562e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.1920928955078125e-05s
INFO | --- Analysis for athelia-rfid took 135.72983646392822s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 8.535385131835938e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.00089263916015625s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.3922700881958008s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.024948596954345703s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0011897087097167969s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 5.91278076171875e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 6.318092346191406e-05s
INFO | --- Analysis for aueb-linked-open-data took 136.3639636039734s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.5750608444213867s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0007922649383544922s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 26.736268997192383s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.024715662002563477s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 6.031990051269531e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 1.0967254638671875e-05s
INFO | --- Analysis for AugustiniConfessiones took 177.14074182510376s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.5008161067962646s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005691051483154297s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.403688907623291s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.02096271514892578s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 9.655952453613281e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 1.0728836059570312e-05s
INFO | --- Analysis for austrian_ski_racers took 114.53418707847595s
Availability | SPARQL endpoint availability check for AVsOnto took 8.893013000488281e-05s
Availability | VoID file availability check for AVsOnto took 0.0006418228149414062s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.30260682106018066s
Reputation | Calculation of the PageRank for AVsOnto took 0.020803213119506836s
Interlinking | Calculation of Degree of Connection for AVsOnto took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 5.364418029785156e-05s
Believability | Calculation of trust value for AVsOnto took 1.1444091796875e-05s
INFO | --- Analysis for AVsOnto took 171.3789563179016s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.32901859283447266s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0006425380706787109s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 170.51031041145325s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.4932711124420166s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.05678486824036s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 249.8624119758606s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0858905315399s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0977427959442s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24594783782958984s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24643707275390625s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1986238956451416s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15384316444396973s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 58.594608783721924s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1002779006958s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12168145179748535s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10494804382324s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.3801403045654297s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11478948593139648s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1126546859741211s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09789729118347168s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.470677614212036s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.440017700195312e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10104751586914062s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0403983592987s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16368675231933594s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14739346504211426s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12946820259094238s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24402070045471191s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2804429531097412s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 801.1074194908142s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13511347770690918s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 11.61284613609314s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.237273931503296s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.914238691329956s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13419628143310547s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.2390327453613s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 26.133652687072754s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.9658634662628174s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.72771430015564s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.8924131393432617s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.3807258605957031s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.1140868663787842s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.47059035301208496s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.02219223976135254s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0008075237274169922s
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 2.6226043701171875e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.8596649169921875e-05s
INFO | --- Analysis for b3kat took 4463.159896373749s
Availability | SPARQL endpoint availability check for BabelNet took 0.4661600589752197s
Availability | VoID file availability check for BabelNet took 0.0006549358367919922s
Completeness | Calculation of interlinking completeness for BabelNet took 30.39745283126831s
Reputation | Calculation of the PageRank for BabelNet took 0.0211334228515625s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.00017213821411132812s
Believability | Calculation of trust value for BabelNet took 1.2159347534179688e-05s
INFO | --- Analysis for babelnet took 151.83779287338257s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 4.982948303222656e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.3366713523864746s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.02088475227355957s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 3.24249267578125e-05s
Believability | Calculation of trust value for Bacevicius.lt took 9.5367431640625e-06s
INFO | --- Analysis for Bacevicius.lt took 34.06818699836731s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.5088965892791748s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 33.463563203811646s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.020970821380615234s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 5.6743621826171875e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 1.1444091796875e-05s
INFO | --- Analysis for bag took 174.37182664871216s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 2.9661755561828613s
Availability | VoID file availability check for 红色经典歌曲 took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.3610374927520752s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.0208437442779541s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.4332275390625e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.2159347534179688e-05s
INFO | --- Analysis for baixue took 95.14582538604736s
Availability | SPARQL endpoint availability check for baixue composer took 4.100799560546875e-05s
Availability | VoID file availability check for baixue composer took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for baixue composer took 0.28081488609313965s
Reputation | Calculation of the PageRank for baixue composer took 0.020965576171875s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for baixue composer took 3.147125244140625e-05s
Believability | Calculation of trust value for baixue composer took 1.2636184692382812e-05s
INFO | --- Analysis for baixue_composer took 161.0036268234253s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 9.655952453613281e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 24.544437408447266s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.021089792251586914s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.552436828613281e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.1682510375976562e-05s
INFO | --- Analysis for baixue_imagery took 157.87851357460022s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 8.988380432128906e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0007295608520507812s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 25.22438359260559s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02084803581237793s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.147125244140625e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.239776611328125e-05s
INFO | --- Analysis for baixue_imagery1 took 162.1933662891388s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 9.202957153320312e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.00038909912109375s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 25.26320767402649s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.021318912506103516s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 5.221366882324219e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 1.239776611328125e-05s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 134.9158535003662s
Availability | SPARQL endpoint availability check for BBC Music took 0.3626241683959961s
Availability | VoID file availability check for BBC Music took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for BBC Music took 0.309096097946167s
Reputation | Calculation of the PageRank for BBC Music took 0.020838260650634766s
Interlinking | Calculation of Degree of Connection for BBC Music took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BBC Music took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.000133514404296875s
Believability | Calculation of trust value for BBC Music took 1.0967254638671875e-05s
INFO | --- Analysis for bbc-music took 108.43577432632446s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.2737717628479004s
Availability | VoID file availability check for BBC Programmes took 0.0007281303405761719s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.4080953598022461s
Reputation | Calculation of the PageRank for BBC Programmes took 0.022382497787475586s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010895729064941406s
Believability | Calculation of trust value for BBC Programmes took 1.1682510375976562e-05s
INFO | --- Analysis for bbc-programmes took 138.36642289161682s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.35882091522216797s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0007178783416748047s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 27.943795680999756s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.021810293197631836s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010275840759277344s
Believability | Calculation of trust value for BBC Wildlife Finder took 1.0967254638671875e-05s
INFO | --- Analysis for bbc-wildlife-finder took 139.51577639579773s
Availability | SPARQL endpoint availability check for BBOP took 4.410743713378906e-05s
Availability | VoID file availability check for BBOP took 0.00035643577575683594s
Completeness | Calculation of interlinking completeness for BBOP took 29.462252140045166s
Reputation | Calculation of the PageRank for BBOP took 0.02104973793029785s
Interlinking | Calculation of Degree of Connection for BBOP took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.504753112792969e-05s
Believability | Calculation of trust value for BBOP took 1.2159347534179688e-05s
INFO | --- Analysis for bbop-selected took 136.98044443130493s
Availability | SPARQL endpoint availability check for Bdgp took 0.8863632678985596s
Availability | VoID file availability check for Bdgp took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for Bdgp took 27.736618280410767s
Reputation | Calculation of the PageRank for Bdgp took 0.021068334579467773s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.3855438232421875e-05s
Believability | Calculation of trust value for Bdgp took 1.1205673217773438e-05s
INFO | --- Analysis for bdgp took 167.32884550094604s
Availability | SPARQL endpoint availability check for Bendev Junior took 8.869171142578125e-05s
Availability | VoID file availability check for Bendev Junior took 0.0007076263427734375s
Completeness | Calculation of interlinking completeness for Bendev Junior took 24.99512529373169s
Reputation | Calculation of the PageRank for Bendev Junior took 0.020805835723876953s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 3.147125244140625e-05s
Believability | Calculation of trust value for Bendev Junior took 7.152557373046875e-06s
INFO | --- Analysis for bendevoficial took 111.92275500297546s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 6.023555755615234s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0006773471832275391s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 25.666906356811523s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.0216982364654541s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0011069774627685547s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 8.463859558105469e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 9.059906005859375e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 155.0374150276184s
Availability | SPARQL endpoint availability check for berlios took 0.00010061264038085938s
Availability | VoID file availability check for berlios took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for berlios took 0.3372929096221924s
Reputation | Calculation of the PageRank for berlios took 0.02067852020263672s
Interlinking | Calculation of Degree of Connection for berlios took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for berlios took 9.131431579589844e-05s
Believability | Calculation of trust value for berlios took 1.1444091796875e-05s
INFO | --- Analysis for berlios took 66.10968852043152s
Availability | SPARQL endpoint availability check for Between Our Worlds took 8.916854858398438e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 27.855074405670166s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.02224111557006836s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 7.128715515136719e-05s
Believability | Calculation of trust value for Between Our Worlds took 1.3589859008789062e-05s
INFO | --- Analysis for betweenourworlds took 148.5415234565735s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.09373688697814941s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.35970616340637207s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.02080368995666504s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.202957153320312e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 8.58306884765625e-06s
INFO | --- Analysis for bfs-linked-data took 109.80529618263245s
Availability | SPARQL endpoint availability check for BibBase took 0.07024550437927246s
Availability | VoID file availability check for BibBase took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for BibBase took 0.31132936477661133s
Reputation | Calculation of the PageRank for BibBase took 0.020854949951171875s
Interlinking | Calculation of Degree of Connection for BibBase took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.775161743164062e-05s
Believability | Calculation of trust value for BibBase took 1.1682510375976562e-05s
INFO | --- Analysis for bibbase took 125.31271648406982s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 9.202957153320312e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0007147789001464844s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.3256375789642334s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.021129846572875977s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0008344650268554688s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.00012373924255371094s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 7.152557373046875e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 112.86806511878967s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 9.822845458984375e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.2986149787902832s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.022568702697753906s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 0.00011563301086425781s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 1.2159347534179688e-05s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 136.06070566177368s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.00039458274841308594s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0006139278411865234s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 27.761420011520386s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.021128416061401367s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.5762786865234375e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.1444091796875e-05s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 112.18467259407043s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 4.291534423828125e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 29.93009305000305s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.02092266082763672s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.743171691894531e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 1.1444091796875e-05s
INFO | --- Analysis for BibSonomy took 171.051607131958s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 0.0001308917999267578s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.31586194038391113s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.022549867630004883s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.743171691894531e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 1.0728836059570312e-05s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 143.32787823677063s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 8.296966552734375e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 30.67804503440857s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.0218966007232666s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.147125244140625e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 9.775161743164062e-06s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 135.42792582511902s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 1.2500016689300537s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0006947517395019531s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 20.42021608352661s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.5303609371185303s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 46.37946271896362s
Interoperability | New terms check for Bio2RDF::Affymetrix took 41.14668822288513s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.13152503967285s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.15336227416992188s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.6309773921966553s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.21535062789916992s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 2.18245267868042s
License | MR license check for Bio2RDF::Affymetrix took 0.3458857536315918s
License | HR license check for Bio2RDF::Affymetrix took 60.10433626174927s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.13764619827270508s
Understandability | Number of label check for Bio2RDF::Affymetrix took 9.86330509185791s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.399733304977417s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.13219070434570312s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.12826824188232422s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.14899539947509766s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.705474138259888s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 80.30240631103516s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.45308780670166016s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.24297356605529785s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.6949656009674072s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.18559908866882324s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.1150662899017334s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.2731645107269287s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.23701977729797363s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 111.50611305236816s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 23.480071544647217s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.3203921318054199s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.15291690826416016s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.12787628173828125s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 7.05083441734314s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.9045867919921875s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.675936222076416s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.36896181106567383s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 64.8333203792572s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.3187975883483887s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.1864917278289795s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.4367499351501465s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.53483581542969s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.7101287841796875s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.3298780918121338s
Security | Sign check for Bio2RDF::Affymetrix took 0.11951947212219238s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 10.248395919799805s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 29.82108759880066s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020981550216674805s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 9.894371032714844e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 32.655043840408325s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 1268.8192994594574s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.5572600364685059s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0003581047058105469s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 19.372544527053833s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.23215651512146s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 45.65272784233093s
Interoperability | New terms check for Bio2RDF::Biomodels took 42.492802143096924s
Versatility | Languages check for Bio2RDF::Biomodels took 60.25086426734924s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.24886822700500488s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.14467787742614746s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.8444795608520508s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.32614922523498535s
Availability | RDF dump link check for Bio2RDF::Biomodels took 2.070465087890625s
License | MR license check for Bio2RDF::Biomodels took 0.4893338680267334s
License | HR license check for Bio2RDF::Biomodels took 60.26388216018677s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.25465869903564453s
Understandability | Number of label check for Bio2RDF::Biomodels took 10.626637697219849s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5980057716369629s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.274477481842041s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.24614953994750977s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.2670857906341553s
Performance | Throughput check for Bio2RDF::Biomodels took 10.634451627731323s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 79.15007972717285s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 1.3954846858978271s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.37157344818115234s
Interlinking | skos check for Bio2RDF::Biomodels took 0.8387148380279541s
Interlinking | skos check for Bio2RDF::Biomodels took 0.385028600692749s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.26319098472595215s
Currency | Creation date check for Bio2RDF::Biomodels took 0.5234372615814209s
Currency | Modification date check for Bio2RDF::Biomodels took 0.5155363082885742s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 111.11092042922974s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 17.101097345352173s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.43242788314819336s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.2654685974121094s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.29002833366394043s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 7.3844311237335205s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.9112663269042969s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6685452461242676s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.4332997798919678s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.62621331214905s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.4755783081054688s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 6.6115028858184814s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.6839990615844727s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.725637912750244s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.8108530044555664s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.44388866424560547s
Security | Sign check for Bio2RDF::Biomodels took 0.2649266719818115s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 10.087327241897583s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 36.85315656661987s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.03549075126647949s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.0001342296600341797s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 48.12585425376892s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-biomodels took 1206.2674310207367s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.48218679428100586s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0003845691680908203s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 19.136746644973755s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.3000528812408447s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 45.80698108673096s
Interoperability | New terms check for Bio2RDF::Bioportal took 42.2710235118866s
Versatility | Languages check for Bio2RDF::Bioportal took 60.26647400856018s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.25740790367126465s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.16814541816711426s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 1.0236179828643799s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.31552696228027344s
Availability | RDF dump link check for Bio2RDF::Bioportal took 2.2306370735168457s
License | MR license check for Bio2RDF::Bioportal took 0.48511242866516113s
License | HR license check for Bio2RDF::Bioportal took 60.25677132606506s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.2791581153869629s
Understandability | Number of label check for Bio2RDF::Bioportal took 11.835961818695068s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.6041195392608643s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.2503390312194824s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.2608034610748291s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.26644229888916016s
Performance | Throughput check for Bio2RDF::Bioportal took 11.430155754089355s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 80.0829827785492s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.6476128101348877s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.3684391975402832s
Interlinking | skos check for Bio2RDF::Bioportal took 0.8373105525970459s
Interlinking | skos check for Bio2RDF::Bioportal took 0.34597158432006836s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.25789666175842285s
Currency | Creation date check for Bio2RDF::Bioportal took 0.532311201095581s
Currency | Modification date check for Bio2RDF::Bioportal took 0.5052809715270996s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 108.55634713172913s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 26.4437038898468s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.43477940559387207s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.26465630531311035s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.2748990058898926s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 7.082317590713501s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.8953654766082764s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6735193729400635s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.4880828857421875s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 65.50513315200806s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.4379119873046875s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.822753429412842s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.419039249420166s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.66101360321045s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7310967445373535s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.4709293842315674s
Security | Sign check for Bio2RDF::Bioportal took 0.28681349754333496s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 10.153982877731323s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 23.314362287521362s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.02097344398498535s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.00046443939208984375s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 42.51787996292114s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-bioportal took 1177.170345067978s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.14180850982666016s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.29749202728271484s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.021286964416503906s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 6.222724914550781e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-chembl took 123.18025517463684s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.6239914894104004s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0005745887756347656s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 19.13245940208435s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.2384278774261475s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 46.09281945228577s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 44.24928307533264s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.23877310752869s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.3164544105529785s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.16738486289978027s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.2667856216430664s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.32412028312683105s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 2.1827635765075684s
License | MR license check for Bio2RDF::Clinicaltrials took 0.4879152774810791s
License | HR license check for Bio2RDF::Clinicaltrials took 60.25823450088501s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.2588963508605957s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 10.402994632720947s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.5929045677185059s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.26694464683532715s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.2584373950958252s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.26221799850463867s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 10.883517503738403s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 80.65867280960083s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.5644640922546387s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.3482999801635742s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.8239254951477051s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.33903932571411133s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.2929985523223877s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.5496265888214111s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.5367300510406494s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 108.06776189804077s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 39.92063879966736s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.45748090744018555s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.28607964515686035s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.28824639320373535s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 8.105578660964966s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.8997607231140137s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6863861083984375s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.3970775604248047s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 65.18064379692078s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.462803602218628s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 7.01471471786499s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.4939172267913818s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.73369550704956s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.7228631973266602s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.5815291404724121s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.27481961250305176s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 12.148512840270996s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 22.917629957199097s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.02099323272705078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 5.602836608886719e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 36.50494432449341s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1277.6325051784515s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.49367356300354004s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0006706714630126953s
Extra | Recovery of all triples for Bio2RDF::Ctd took 20.15150785446167s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.237036943435669s
Amount of data | Number of triples check for Bio2RDF::Ctd took 46.075098752975464s
Interoperability | New terms check for Bio2RDF::Ctd took 44.73410105705261s
Versatility | Languages check for Bio2RDF::Ctd took 60.25484561920166s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.27306413650512695s
Security | Check HTTPS for Bio2RDF::Ctd took 0.1475374698638916s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.9226584434509277s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.33736085891723633s
Availability | RDF dump link check for Bio2RDF::Ctd took 2.277420997619629s
License | MR license check for Bio2RDF::Ctd took 0.49932003021240234s
License | HR license check for Bio2RDF::Ctd took 60.26246118545532s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.2607245445251465s
Understandability | Number of label check for Bio2RDF::Ctd took 9.915256977081299s
Understandability | URI regex check for Bio2RDF::Ctd took 0.5686371326446533s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.2615644931793213s
Verifiability | Authors check for Bio2RDF::Ctd took 0.23917126655578613s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.26284170150756836s
Performance | Throughput check for Bio2RDF::Ctd took 10.691580057144165s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 79.08049774169922s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.5709173679351807s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.375277042388916s
Interlinking | skos check for Bio2RDF::Ctd took 0.8165318965911865s
Interlinking | skos check for Bio2RDF::Ctd took 0.35916829109191895s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.26521944999694824s
Currency | Creation date check for Bio2RDF::Ctd took 0.5249443054199219s
Currency | Modification date check for Bio2RDF::Ctd took 0.5067787170410156s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 109.59100413322449s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 58.3996365070343s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.44692516326904297s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.278536319732666s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.2917013168334961s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 7.322108745574951s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.9110434055328369s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6735827922821045s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.4198310375213623s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.36718773841858s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.4498913288116455s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.615633964538574s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.4280738830566406s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.66112971305847s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.7228338718414307s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.8143351078033447s
Security | Sign check for Bio2RDF::Ctd took 0.2531914710998535s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 9.997076749801636s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 30.915775537490845s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.021064043045043945s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 7.104873657226562e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 49.716065645217896s
Believability | Calculation of trust value for Bio2RDF::Ctd took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-ctd took 1279.9110612869263s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.410743713378906e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0006668567657470703s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 27.980303049087524s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.02210831642150879s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 6.127357482910156e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-dataset took 55.6656551361084s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.47908663749694824s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0007152557373046875s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 20.158087015151978s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.2739074230194092s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 45.23599123954773s
Interoperability | New terms check for Bio2RDF::Dbsnp took 42.1515736579895s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.23809742927551s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.2688286304473877s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.1557931900024414s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.9008874893188477s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.33414721488952637s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 2.0406899452209473s
License | MR license check for Bio2RDF::Dbsnp took 0.5951001644134521s
License | HR license check for Bio2RDF::Dbsnp took 60.232219219207764s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.2961914539337158s
Understandability | Number of label check for Bio2RDF::Dbsnp took 10.4640793800354s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.578444242477417s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.25377845764160156s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.270050048828125s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.2609264850616455s
Performance | Throughput check for Bio2RDF::Dbsnp took 10.673464059829712s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 82.24947786331177s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.5568647384643555s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.35268378257751465s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.7886247634887695s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.3362720012664795s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.24956870079040527s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.5371494293212891s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.5434563159942627s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 108.92499327659607s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 23.987337350845337s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.45304155349731445s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.2571406364440918s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.2807621955871582s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 6.917510747909546s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.8988268375396729s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6787643432617188s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.4421525001525879s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 65.20919513702393s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.451801061630249s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.497205972671509s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.4576811790466309s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.68214702606201s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7471218109130859s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.41330456733703613s
Security | Sign check for Bio2RDF::Dbsnp took 0.2724645137786865s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 12.100577354431152s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.36005663871765137s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.021151065826416016s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0008459091186523438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 8.0108642578125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 47.998915672302246s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 1176.163029909134s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.4909968376159668s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0005970001220703125s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 19.222262859344482s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.2694447040557861s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 45.20646286010742s
Interoperability | New terms check for Bio2RDF::Drugbank took 43.8221001625061s
Versatility | Languages check for Bio2RDF::Drugbank took 60.26884579658508s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.2673611640930176s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.163621187210083s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.9707210063934326s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.3224625587463379s
Availability | RDF dump link check for Bio2RDF::Drugbank took 2.0123531818389893s
License | MR license check for Bio2RDF::Drugbank took 0.6098802089691162s
License | HR license check for Bio2RDF::Drugbank took 60.26755213737488s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.27953171730041504s
Understandability | Number of label check for Bio2RDF::Drugbank took 10.558139085769653s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.5542330741882324s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.2418684959411621s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.25036048889160156s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.2676656246185303s
Performance | Throughput check for Bio2RDF::Drugbank took 11.074630975723267s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 78.3250744342804s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.6137642860412598s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.3512420654296875s
Interlinking | skos check for Bio2RDF::Drugbank took 0.8223557472229004s
Interlinking | skos check for Bio2RDF::Drugbank took 0.33553409576416016s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.25775766372680664s
Currency | Creation date check for Bio2RDF::Drugbank took 0.5047357082366943s
Currency | Modification date check for Bio2RDF::Drugbank took 0.4943678379058838s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 110.28232645988464s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 44.224215507507324s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.4598073959350586s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.27262187004089355s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.2729504108428955s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 7.986613035202026s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.9004180431365967s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.6600961685180664s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.4319896697998047s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 65.25743794441223s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.413313150405884s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 6.651196479797363s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.442598819732666s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.67978644371033s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.7107703685760498s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 1.40220308303833s
Security | Sign check for Bio2RDF::Drugbank took 0.27249813079833984s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 9.977346420288086s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 22.275584936141968s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.022149324417114258s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0009126663208007812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00011587142944335938s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 45.6548228263855s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 2.3603439331054688e-05s
INFO | --- Analysis for bio2rdf-drugbank took 1214.235381603241s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.47127342224121094s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0006308555603027344s
Extra | Recovery of all triples for Bio2RDF::Genage took 22.521013021469116s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.297339916229248s
Amount of data | Number of triples check for Bio2RDF::Genage took 45.47500920295715s
Interoperability | New terms check for Bio2RDF::Genage took 42.90493822097778s
Versatility | Languages check for Bio2RDF::Genage took 60.24824833869934s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.2927870750427246s
Security | Check HTTPS for Bio2RDF::Genage took 0.1569688320159912s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.8670351505279541s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.3053255081176758s
Availability | RDF dump link check for Bio2RDF::Genage took 2.043865203857422s
License | MR license check for Bio2RDF::Genage took 0.5135993957519531s
License | HR license check for Bio2RDF::Genage took 60.253283977508545s
Amount of data | Number of property check for Bio2RDF::Genage took 0.2683894634246826s
Understandability | Number of label check for Bio2RDF::Genage took 14.37406039237976s
Understandability | URI regex check for Bio2RDF::Genage took 0.5959639549255371s
Understandability | Vocabs check for Bio2RDF::Genage took 0.25322556495666504s
Verifiability | Authors check for Bio2RDF::Genage took 0.25086498260498047s
Verifiability | Publishers check for Bio2RDF::Genage took 0.2579188346862793s
Performance | Throughput check for Bio2RDF::Genage took 10.996495723724365s
Amount of data | Check the number of entities for Bio2RDF::Genage took 81.61773014068604s
Verifiability | Contribs. check for Bio2RDF::Genage took 0.5655524730682373s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.3772590160369873s
Interlinking | skos check for Bio2RDF::Genage took 0.8875417709350586s
Interlinking | skos check for Bio2RDF::Genage took 0.35091114044189453s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.26967287063598633s
Currency | Creation date check for Bio2RDF::Genage took 0.5440101623535156s
Currency | Modification date check for Bio2RDF::Genage took 0.5317683219909668s
Rep.Conc. | URIs length for Bio2RDF::Genage took 110.2642297744751s
Interoperability | New vocabularies check for Bio2RDF::Genage took 49.69409441947937s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.4505589008331299s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.27088499069213867s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.264446496963501s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 7.373437881469727s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.9005844593048096s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.69378662109375s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.4321012496948242s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 65.38155198097229s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.4761476516723633s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.424911975860596s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.4297785758972168s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.685476779937744s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.727503776550293s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.6280274391174316s
Security | Sign check for Bio2RDF::Genage took 0.2891414165496826s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 10.324839115142822s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 27.48768711090088s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.021033287048339844s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 6.222724914550781e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 36.70446300506592s
Believability | Calculation of trust value for Bio2RDF::Genage took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-genage took 1296.3748371601105s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 8.416175842285156e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 28.72026014328003s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.0210268497467041s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 8.225440979003906e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-genbank took 81.54988527297974s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.5003604888916016s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0006732940673828125s
Extra | Recovery of all triples for Bio2RDF::Gendr took 19.205687761306763s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.2429702281951904s
Amount of data | Number of triples check for Bio2RDF::Gendr took 45.674739837646484s
Interoperability | New terms check for Bio2RDF::Gendr took 42.597119092941284s
Versatility | Languages check for Bio2RDF::Gendr took 60.25699806213379s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.29984617233276367s
Security | Check HTTPS for Bio2RDF::Gendr took 0.1553816795349121s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.3686394691467285s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.29932093620300293s
Availability | RDF dump link check for Bio2RDF::Gendr took 2.090714931488037s
License | MR license check for Bio2RDF::Gendr took 0.567542552947998s
License | HR license check for Bio2RDF::Gendr took 60.24824357032776s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.8458027839660645s
Understandability | Number of label check for Bio2RDF::Gendr took 10.345194101333618s
Understandability | URI regex check for Bio2RDF::Gendr took 0.6210901737213135s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.2686886787414551s
Verifiability | Authors check for Bio2RDF::Gendr took 0.24512457847595215s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.26952433586120605s
Performance | Throughput check for Bio2RDF::Gendr took 10.821642875671387s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 81.1139714717865s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.570392370223999s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.4008002281188965s
Interlinking | skos check for Bio2RDF::Gendr took 0.9280495643615723s
Interlinking | skos check for Bio2RDF::Gendr took 0.33866024017333984s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.2634422779083252s
Currency | Creation date check for Bio2RDF::Gendr took 0.5108554363250732s
Currency | Modification date check for Bio2RDF::Gendr took 0.5023050308227539s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 109.36183428764343s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 103.59239077568054s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.42357492446899414s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.28551745414733887s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.2686018943786621s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 6.878448963165283s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.9133074283599854s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6751885414123535s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.48999476432800293s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 65.56920099258423s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.4409658908843994s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.897775173187256s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.4618675708770752s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.85038208961487s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.7309324741363525s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.43090367317199707s
Security | Sign check for Bio2RDF::Gendr took 0.2665975093841553s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 12.906963109970093s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.3724043369293213s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.021138906478881836s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.507469177246094e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 91.59423565864563s
Believability | Calculation of trust value for Bio2RDF::Gendr took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-gendr took 1362.8054745197296s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.49446582794189453s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0007405281066894531s
Extra | Recovery of all triples for Bio2RDF::Goa took 19.316858291625977s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.2643458843231201s
Amount of data | Number of triples check for Bio2RDF::Goa took 45.92996835708618s
Interoperability | New terms check for Bio2RDF::Goa took 42.231918811798096s
Versatility | Languages check for Bio2RDF::Goa took 60.24436378479004s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.2896435260772705s
Security | Check HTTPS for Bio2RDF::Goa took 0.15578770637512207s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.611781120300293s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.3119394779205322s
Availability | RDF dump link check for Bio2RDF::Goa took 2.1282460689544678s
License | MR license check for Bio2RDF::Goa took 0.4402585029602051s
License | HR license check for Bio2RDF::Goa took 60.241610288619995s
Amount of data | Number of property check for Bio2RDF::Goa took 0.3191952705383301s
Understandability | Number of label check for Bio2RDF::Goa took 10.357405424118042s
Understandability | URI regex check for Bio2RDF::Goa took 0.5957896709442139s
Understandability | Vocabs check for Bio2RDF::Goa took 0.26553893089294434s
Verifiability | Authors check for Bio2RDF::Goa took 0.26439404487609863s
Verifiability | Publishers check for Bio2RDF::Goa took 0.24269962310791016s
Performance | Throughput check for Bio2RDF::Goa took 10.862143278121948s
Amount of data | Check the number of entities for Bio2RDF::Goa took 78.237313747406s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.6016654968261719s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.3769862651824951s
Interlinking | skos check for Bio2RDF::Goa took 0.8009188175201416s
Interlinking | skos check for Bio2RDF::Goa took 0.35369443893432617s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.2538881301879883s
Currency | Creation date check for Bio2RDF::Goa took 0.5010280609130859s
Currency | Modification date check for Bio2RDF::Goa took 0.4981982707977295s
Rep.Conc. | URIs length for Bio2RDF::Goa took 108.60240602493286s
Interoperability | New vocabularies check for Bio2RDF::Goa took 43.163248777389526s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.41712069511413574s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.28467464447021484s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.266033411026001s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 6.74063515663147s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.9070193767547607s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6681234836578369s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.5652987957000732s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 65.37391471862793s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.4238510131835938s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 6.407874822616577s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.4293458461761475s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.68921494483948s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.7158839702606201s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.5915517807006836s
Security | Sign check for Bio2RDF::Goa took 0.2679424285888672s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 13.713287591934204s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.348405122756958s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.024894237518310547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.628036499023438e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 31.77578115463257s
Believability | Calculation of trust value for Bio2RDF::Goa took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-goa took 1207.6566188335419s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.45835447311401367s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0006842613220214844s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 18.368844509124756s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.2380247116088867s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 45.91711068153381s
Interoperability | New terms check for Bio2RDF::Hgnc took 41.35151290893555s
Versatility | Languages check for Bio2RDF::Hgnc took 60.245625495910645s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.2714884281158447s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.15784764289855957s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.7307660579681396s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.3157925605773926s
Availability | RDF dump link check for Bio2RDF::Hgnc took 1.9857192039489746s
License | MR license check for Bio2RDF::Hgnc took 0.34684228897094727s
License | HR license check for Bio2RDF::Hgnc took 60.23279643058777s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.263446569442749s
Understandability | Number of label check for Bio2RDF::Hgnc took 10.498214483261108s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.5803840160369873s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.24717283248901367s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.2767322063446045s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.2671468257904053s
Performance | Throughput check for Bio2RDF::Hgnc took 10.773759126663208s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 80.29061102867126s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.7101888656616211s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.38609838485717773s
Interlinking | skos check for Bio2RDF::Hgnc took 1.0372791290283203s
Interlinking | skos check for Bio2RDF::Hgnc took 0.33704257011413574s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.2598867416381836s
Currency | Creation date check for Bio2RDF::Hgnc took 0.5054998397827148s
Currency | Modification date check for Bio2RDF::Hgnc took 0.5186214447021484s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 108.88306045532227s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 31.84223484992981s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.42530107498168945s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.28455638885498047s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.28182435035705566s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 7.124025821685791s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.8983972072601318s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6804659366607666s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.3848731517791748s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.82295608520508s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.4370527267456055s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 6.634257793426514s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.4306726455688477s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.67299723625183s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7289586067199707s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.42522454261779785s
Security | Sign check for Bio2RDF::Hgnc took 0.2729160785675049s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 1.4367260932922363s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.3091163635253906s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.0209043025970459s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00011515617370605469s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 31.284133195877075s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-hgnc took 1178.5784916877747s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.47719764709472656s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0007052421569824219s
Extra | Recovery of all triples for Bio2RDF::Homologene took 19.128281354904175s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.237102746963501s
Amount of data | Number of triples check for Bio2RDF::Homologene took 45.27556109428406s
Interoperability | New terms check for Bio2RDF::Homologene took 43.549209117889404s
Versatility | Languages check for Bio2RDF::Homologene took 60.248066425323486s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.2761540412902832s
Security | Check HTTPS for Bio2RDF::Homologene took 0.16411590576171875s
Interpretability | RDF structures check for Bio2RDF::Homologene took 1.0921142101287842s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.31488537788391113s
Availability | RDF dump link check for Bio2RDF::Homologene took 2.0723378658294678s
License | MR license check for Bio2RDF::Homologene took 0.5734748840332031s
License | HR license check for Bio2RDF::Homologene took 60.24232459068298s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.28658127784729004s
Understandability | Number of label check for Bio2RDF::Homologene took 10.419984817504883s
Understandability | URI regex check for Bio2RDF::Homologene took 0.6006059646606445s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.24934101104736328s
Verifiability | Authors check for Bio2RDF::Homologene took 0.2707202434539795s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.2512633800506592s
Performance | Throughput check for Bio2RDF::Homologene took 10.490118980407715s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 80.6138825416565s
Verifiability | Contribs. check for Bio2RDF::Homologene took 2.020536184310913s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.385547399520874s
Interlinking | skos check for Bio2RDF::Homologene took 1.2116849422454834s
Interlinking | skos check for Bio2RDF::Homologene took 0.3441627025604248s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.26035284996032715s
Currency | Creation date check for Bio2RDF::Homologene took 0.516693115234375s
Currency | Modification date check for Bio2RDF::Homologene took 0.5233809947967529s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 112.36083436012268s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 40.104098320007324s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.45943474769592285s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.3114628791809082s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.28778862953186035s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 6.958204030990601s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8982739448547363s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.674612283706665s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.4023168087005615s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.67525148391724s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.4760518074035645s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.319584608078003s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.4354679584503174s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.67014002799988s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.724036455154419s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.5907139778137207s
Security | Sign check for Bio2RDF::Homologene took 0.2638580799102783s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 11.67610216140747s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.3139967918395996s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.023955583572387695s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 7.319450378417969e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 33.59940314292908s
Believability | Calculation of trust value for Bio2RDF::Homologene took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-homologene took 1212.0080680847168s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.4656662940979004s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0006251335144042969s
Extra | Recovery of all triples for Bio2RDF::Interpro took 18.568570375442505s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.2355060577392578s
Amount of data | Number of triples check for Bio2RDF::Interpro took 45.73953104019165s
Interoperability | New terms check for Bio2RDF::Interpro took 41.94942831993103s
Versatility | Languages check for Bio2RDF::Interpro took 60.240957260131836s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.2570164203643799s
Security | Check HTTPS for Bio2RDF::Interpro took 0.1578211784362793s
Interpretability | RDF structures check for Bio2RDF::Interpro took 1.0624911785125732s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.32030296325683594s
Availability | RDF dump link check for Bio2RDF::Interpro took 2.258333444595337s
License | MR license check for Bio2RDF::Interpro took 0.5820434093475342s
License | HR license check for Bio2RDF::Interpro took 60.23764371871948s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.25731515884399414s
Understandability | Number of label check for Bio2RDF::Interpro took 10.008965969085693s
Understandability | URI regex check for Bio2RDF::Interpro took 0.5661592483520508s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.2508687973022461s
Verifiability | Authors check for Bio2RDF::Interpro took 0.24933886528015137s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.2593569755554199s
Performance | Throughput check for Bio2RDF::Interpro took 10.916764259338379s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 81.5371150970459s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.6117660999298096s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.37960243225097656s
Interlinking | skos check for Bio2RDF::Interpro took 0.8559970855712891s
Interlinking | skos check for Bio2RDF::Interpro took 0.3486025333404541s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.2579159736633301s
Currency | Creation date check for Bio2RDF::Interpro took 0.52944016456604s
Currency | Modification date check for Bio2RDF::Interpro took 0.5296871662139893s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 109.6626410484314s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 20.04144549369812s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.44548821449279785s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.2712416648864746s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.27199625968933105s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 6.856015682220459s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.902644157409668s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6850967407226562s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.39546751976013184s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.51954960823059s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.4949958324432373s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.757505655288696s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.4445064067840576s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.68800640106201s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.7435817718505859s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.4290804862976074s
Security | Sign check for Bio2RDF::Interpro took 0.26253557205200195s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 10.92171335220337s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.662914514541626s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.02167987823486328s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0010135173797607422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00012063980102539062s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 24.82972812652588s
Believability | Calculation of trust value for Bio2RDF::Interpro took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-interpro took 1151.7687129974365s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.14203548431396484s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0006680488586425781s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 24.795421361923218s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.021078109741210938s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 9.036064147949219e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-iproclass took 136.008455991745s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.4855191707611084s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0005629062652587891s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 18.98052144050598s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.2080225944519043s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 47.03362250328064s
Interoperability | New terms check for Bio2RDF::Irefindex took 45.56893801689148s
Versatility | Languages check for Bio2RDF::Irefindex took 60.28381562232971s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.2909986972808838s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.157135009765625s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.7054033279418945s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.32945919036865234s
Availability | RDF dump link check for Bio2RDF::Irefindex took 2.233781337738037s
License | MR license check for Bio2RDF::Irefindex took 0.543562650680542s
License | HR license check for Bio2RDF::Irefindex took 60.25114965438843s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.26233983039855957s
Understandability | Number of label check for Bio2RDF::Irefindex took 10.173816204071045s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.5705304145812988s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.2589132785797119s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.2732079029083252s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.2583589553833008s
Performance | Throughput check for Bio2RDF::Irefindex took 10.47750735282898s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 81.50906825065613s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.5529451370239258s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.3460824489593506s
Interlinking | skos check for Bio2RDF::Irefindex took 0.7799065113067627s
Interlinking | skos check for Bio2RDF::Irefindex took 0.38732457160949707s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.26079320907592773s
Currency | Creation date check for Bio2RDF::Irefindex took 0.5039310455322266s
Currency | Modification date check for Bio2RDF::Irefindex took 0.5180244445800781s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 108.68375897407532s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 50.809054374694824s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.42127490043640137s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.28347158432006836s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.29879331588745117s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 7.03961181640625s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.9141805171966553s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6862313747406006s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.42475104331970215s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 65.14501929283142s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.557907581329346s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.4919674396514893s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.742936849594116s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7360484600067139s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.7075109481811523s
Security | Sign check for Bio2RDF::Irefindex took 0.3201291561126709s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 11.2331862449646s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.3954181671142578s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.020951032638549805s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 8.821487426757812e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 58.85180878639221s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-irefindex took 1261.7184889316559s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.13532686233520508s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 27.145423650741577s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.02122974395751953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 4.6253204345703125e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 2.3603439331054688e-05s
INFO | --- Analysis for bio2rdf-linkedspl took 180.57989740371704s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.5139102935791016s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0005750656127929688s
Extra | Recovery of all triples for Bio2RDF::Lsr took 19.206887006759644s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.3342854976654053s
Amount of data | Number of triples check for Bio2RDF::Lsr took 45.9109160900116s
Interoperability | New terms check for Bio2RDF::Lsr took 41.684022426605225s
Versatility | Languages check for Bio2RDF::Lsr took 60.241981983184814s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.27941274642944336s
Security | Check HTTPS for Bio2RDF::Lsr took 0.1692667007446289s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.6420209407806396s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.33553075790405273s
Availability | RDF dump link check for Bio2RDF::Lsr took 2.353877305984497s
License | MR license check for Bio2RDF::Lsr took 0.49062156677246094s
License | HR license check for Bio2RDF::Lsr took 60.25079965591431s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.2803332805633545s
Understandability | Number of label check for Bio2RDF::Lsr took 9.837247610092163s
Understandability | URI regex check for Bio2RDF::Lsr took 0.6130697727203369s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.2597777843475342s
Verifiability | Authors check for Bio2RDF::Lsr took 0.2545332908630371s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.25796961784362793s
Performance | Throughput check for Bio2RDF::Lsr took 11.259607553482056s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 82.1524167060852s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.578045129776001s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.367281436920166s
Interlinking | skos check for Bio2RDF::Lsr took 0.8223841190338135s
Interlinking | skos check for Bio2RDF::Lsr took 0.3977925777435303s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.266355037689209s
Currency | Creation date check for Bio2RDF::Lsr took 0.5351207256317139s
Currency | Modification date check for Bio2RDF::Lsr took 0.5083606243133545s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 109.45212244987488s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 24.891942262649536s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.416919469833374s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.26467251777648926s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.27521729469299316s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 6.98393177986145s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.9066765308380127s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.6853766441345215s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.4366273880004883s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 64.9649486541748s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.4424147605895996s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 6.88524866104126s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.4901318550109863s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.74717450141907s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.7214252948760986s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.442471981048584s
Security | Sign check for Bio2RDF::Lsr took 0.2751619815826416s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 11.18074917793274s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 23.08560085296631s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.0218355655670166s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 5.9604644775390625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 41.11071467399597s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-lsr took 1218.9652545452118s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.486508846282959s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.00033974647521972656s
Extra | Recovery of all triples for Bio2RDF::Mesh took 19.387683391571045s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.235661268234253s
Amount of data | Number of triples check for Bio2RDF::Mesh took 45.15488028526306s
Interoperability | New terms check for Bio2RDF::Mesh took 43.433348655700684s
Versatility | Languages check for Bio2RDF::Mesh took 60.279292821884155s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.2553837299346924s
Security | Check HTTPS for Bio2RDF::Mesh took 0.14542436599731445s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.9537143707275391s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.35263848304748535s
Availability | RDF dump link check for Bio2RDF::Mesh took 1.9529123306274414s
License | MR license check for Bio2RDF::Mesh took 0.47213053703308105s
License | HR license check for Bio2RDF::Mesh took 60.23829221725464s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.25846171379089355s
Understandability | Number of label check for Bio2RDF::Mesh took 10.301061153411865s
Understandability | URI regex check for Bio2RDF::Mesh took 0.5861594676971436s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.23861908912658691s
Verifiability | Authors check for Bio2RDF::Mesh took 0.2657287120819092s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.24442386627197266s
Performance | Throughput check for Bio2RDF::Mesh took 11.195690631866455s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 82.73600172996521s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.6070494651794434s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.37165331840515137s
Interlinking | skos check for Bio2RDF::Mesh took 1.1028125286102295s
Interlinking | skos check for Bio2RDF::Mesh took 0.3496875762939453s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.25135135650634766s
Currency | Creation date check for Bio2RDF::Mesh took 0.529360294342041s
Currency | Modification date check for Bio2RDF::Mesh took 0.5151433944702148s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 108.32852602005005s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 74.495197057724s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.4462258815765381s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.2970147132873535s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.26450395584106445s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 7.122865438461304s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.9115490913391113s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.684274435043335s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.4046025276184082s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 65.43464088439941s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.4754178524017334s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.385725498199463s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.412519931793213s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.64824438095093s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.7199058532714844s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.6480028629302979s
Security | Sign check for Bio2RDF::Mesh took 0.2615478038787842s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 10.313685894012451s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.6868560314178467s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.02103447914123535s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.939338684082031e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 42.56406617164612s
Believability | Calculation of trust value for Bio2RDF::Mesh took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-mesh took 1259.6879603862762s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.4778015613555908s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0006191730499267578s
Extra | Recovery of all triples for Bio2RDF::Mgi took 19.081878185272217s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.2456564903259277s
Amount of data | Number of triples check for Bio2RDF::Mgi took 45.464828968048096s
Interoperability | New terms check for Bio2RDF::Mgi took 42.049400806427s
Versatility | Languages check for Bio2RDF::Mgi took 60.25476837158203s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.2981081008911133s
Security | Check HTTPS for Bio2RDF::Mgi took 0.1592094898223877s
Interpretability | RDF structures check for Bio2RDF::Mgi took 1.153322458267212s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.3209352493286133s
Availability | RDF dump link check for Bio2RDF::Mgi took 2.413585662841797s
License | MR license check for Bio2RDF::Mgi took 0.47756314277648926s
License | HR license check for Bio2RDF::Mgi took 60.255802392959595s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.25943613052368164s
Understandability | Number of label check for Bio2RDF::Mgi took 11.046605825424194s
Understandability | URI regex check for Bio2RDF::Mgi took 0.604264497756958s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.25642967224121094s
Verifiability | Authors check for Bio2RDF::Mgi took 0.2522878646850586s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.25040388107299805s
Performance | Throughput check for Bio2RDF::Mgi took 11.142045021057129s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 82.70087313652039s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.573371171951294s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.3513002395629883s
Interlinking | skos check for Bio2RDF::Mgi took 0.7934305667877197s
Interlinking | skos check for Bio2RDF::Mgi took 0.36077880859375s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.2584362030029297s
Currency | Creation date check for Bio2RDF::Mgi took 0.5347840785980225s
Currency | Modification date check for Bio2RDF::Mgi took 0.5239231586456299s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 108.88587236404419s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 53.14487147331238s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.45621442794799805s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.2859227657318115s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.2835984230041504s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 7.588827133178711s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.9151883125305176s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6894307136535645s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.4353294372558594s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.70328378677368s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.5277318954467773s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 6.928902864456177s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.3986146450042725s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.64098143577576s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7321724891662598s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.6146550178527832s
Security | Sign check for Bio2RDF::Mgi took 0.26933789253234863s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 9.58197283744812s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 24.39172124862671s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.0209348201751709s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0008254051208496094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 9.965896606445312e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 35.102041482925415s
Believability | Calculation of trust value for Bio2RDF::Mgi took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-mgi took 1320.4375169277191s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.48894476890563965s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0006151199340820312s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 19.523349046707153s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.238952398300171s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 45.5133216381073s
Interoperability | New terms check for Bio2RDF::Ncbigene took 43.96969413757324s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.243942737579346s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.3590681552886963s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.16942906379699707s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.9085862636566162s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.33852624893188477s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 2.0834665298461914s
License | MR license check for Bio2RDF::Ncbigene took 0.46462488174438477s
License | HR license check for Bio2RDF::Ncbigene took 60.24476861953735s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.2628490924835205s
Understandability | Number of label check for Bio2RDF::Ncbigene took 9.735799789428711s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.5792274475097656s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.2553389072418213s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.25169920921325684s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.2532482147216797s
Performance | Throughput check for Bio2RDF::Ncbigene took 10.80839991569519s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 83.52506375312805s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.2604100704193115s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.3847658634185791s
Interlinking | skos check for Bio2RDF::Ncbigene took 1.096867322921753s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.4082660675048828s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.2696394920349121s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.548882007598877s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.5155394077301025s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 109.63995051383972s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 19.570892810821533s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.47573041915893555s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2632272243499756s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.275634765625s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 7.51298451423645s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.9049198627471924s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6993141174316406s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.4140787124633789s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.64049053192139s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.7965598106384277s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.897342681884766s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.41316556930542s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.66670060157776s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.7416152954101562s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.43431758880615234s
Security | Sign check for Bio2RDF::Ncbigene took 0.2594642639160156s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 11.59387731552124s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.5355560779571533s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.020958423614501953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012135505676269531s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 39.19803977012634s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-ncbigene took 1256.640174150467s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.47639918327331543s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0006561279296875s
Extra | Recovery of all triples for Bio2RDF::Ndc took 19.366722106933594s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.2677803039550781s
Amount of data | Number of triples check for Bio2RDF::Ndc took 45.93579292297363s
Interoperability | New terms check for Bio2RDF::Ndc took 42.97627282142639s
Versatility | Languages check for Bio2RDF::Ndc took 60.244967460632324s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.2786269187927246s
Security | Check HTTPS for Bio2RDF::Ndc took 0.16910743713378906s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.856787919998169s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.30404019355773926s
Availability | RDF dump link check for Bio2RDF::Ndc took 2.1201400756835938s
License | MR license check for Bio2RDF::Ndc took 0.46113157272338867s
License | HR license check for Bio2RDF::Ndc took 60.25399661064148s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.30902814865112305s
Understandability | Number of label check for Bio2RDF::Ndc took 10.095789194107056s
Understandability | URI regex check for Bio2RDF::Ndc took 0.5945596694946289s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.27701711654663086s
Verifiability | Authors check for Bio2RDF::Ndc took 0.2562127113342285s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.2552764415740967s
Performance | Throughput check for Bio2RDF::Ndc took 10.774693965911865s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 83.59708380699158s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.5763440132141113s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.39591336250305176s
Interlinking | skos check for Bio2RDF::Ndc took 0.8196804523468018s
Interlinking | skos check for Bio2RDF::Ndc took 0.333005428314209s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.266599178314209s
Currency | Creation date check for Bio2RDF::Ndc took 0.5093903541564941s
Currency | Modification date check for Bio2RDF::Ndc took 0.5241739749908447s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 109.58259916305542s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 37.95491170883179s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.4309818744659424s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.2810201644897461s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.2601478099822998s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 7.802313804626465s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.9166884422302246s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6951675415039062s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.4317281246185303s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 65.90358924865723s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.4345450401306152s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.817936658859253s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.4056401252746582s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.66167116165161s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7464494705200195s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 1.3698396682739258s
Security | Sign check for Bio2RDF::Ndc took 0.26834607124328613s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 9.50587272644043s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.6467280387878418s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.021109580993652344s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 5.6743621826171875e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 33.337833404541016s
Believability | Calculation of trust value for Bio2RDF::Ndc took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-ndc took 1231.6155514717102s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.13985633850097656s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 27.093710899353027s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.02172565460205078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.9577484130859375e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-nextprot took 151.2593493461609s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.5530250072479248s
Availability | VoID file availability check for Bio2RDF::Omim took 0.00038170814514160156s
Extra | Recovery of all triples for Bio2RDF::Omim took 18.4498291015625s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.276663064956665s
Amount of data | Number of triples check for Bio2RDF::Omim took 45.64803338050842s
Interoperability | New terms check for Bio2RDF::Omim took 41.909010887145996s
Versatility | Languages check for Bio2RDF::Omim took 60.26663088798523s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.27966809272766113s
Security | Check HTTPS for Bio2RDF::Omim took 0.1447582244873047s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.7469067573547363s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.30620265007019043s
Availability | RDF dump link check for Bio2RDF::Omim took 2.053680419921875s
License | MR license check for Bio2RDF::Omim took 0.4991610050201416s
License | HR license check for Bio2RDF::Omim took 60.23690843582153s
Amount of data | Number of property check for Bio2RDF::Omim took 0.25822949409484863s
Understandability | Number of label check for Bio2RDF::Omim took 9.833726644515991s
Understandability | URI regex check for Bio2RDF::Omim took 0.5887868404388428s
Understandability | Vocabs check for Bio2RDF::Omim took 0.26008105278015137s
Verifiability | Authors check for Bio2RDF::Omim took 0.24505138397216797s
Verifiability | Publishers check for Bio2RDF::Omim took 0.26546764373779297s
Performance | Throughput check for Bio2RDF::Omim took 11.615252256393433s
Amount of data | Check the number of entities for Bio2RDF::Omim took 81.13971853256226s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.603069543838501s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.37780237197875977s
Interlinking | skos check for Bio2RDF::Omim took 0.7137513160705566s
Interlinking | skos check for Bio2RDF::Omim took 0.36190176010131836s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.25836992263793945s
Currency | Creation date check for Bio2RDF::Omim took 0.5054326057434082s
Currency | Modification date check for Bio2RDF::Omim took 0.5396387577056885s
Rep.Conc. | URIs length for Bio2RDF::Omim took 108.4261167049408s
Interoperability | New vocabularies check for Bio2RDF::Omim took 30.753566026687622s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.4093351364135742s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.276137113571167s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.27344465255737305s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 7.3564512729644775s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.9114282131195068s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6833877563476562s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.42354345321655273s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 64.86313152313232s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.4621331691741943s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 6.662850856781006s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.5064172744750977s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.743019104003906s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.7328307628631592s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.43656229972839355s
Security | Sign check for Bio2RDF::Omim took 0.27791714668273926s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 10.295057535171509s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.3512239456176758s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.02099895477294922s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00013828277587890625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 30.4992253780365s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-omim took 1202.1331918239594s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 8.821487426757812e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.2900731563568115s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.022444486618041992s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.8623809814453125e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-omim-resources took 119.29899096488953s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.7058122158050537s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0004100799560546875s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 20.49276876449585s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.2723140716552734s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 45.25429081916809s
Interoperability | New terms check for Bio2RDF::Orphanet took 41.839048862457275s
Versatility | Languages check for Bio2RDF::Orphanet took 60.2377655506134s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.2852499485015869s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.18256855010986328s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.824699878692627s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.32445740699768066s
Availability | RDF dump link check for Bio2RDF::Orphanet took 2.011854410171509s
License | MR license check for Bio2RDF::Orphanet took 0.48856139183044434s
License | HR license check for Bio2RDF::Orphanet took 60.25468921661377s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.2619359493255615s
Understandability | Number of label check for Bio2RDF::Orphanet took 9.910138607025146s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.590137243270874s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.2676694393157959s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.25634217262268066s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.25450682640075684s
Performance | Throughput check for Bio2RDF::Orphanet took 10.829319953918457s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 83.29506301879883s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.7673261165618896s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.35920190811157227s
Interlinking | skos check for Bio2RDF::Orphanet took 1.0587193965911865s
Interlinking | skos check for Bio2RDF::Orphanet took 0.3397393226623535s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.26491212844848633s
Currency | Creation date check for Bio2RDF::Orphanet took 0.5419294834136963s
Currency | Modification date check for Bio2RDF::Orphanet took 0.5366344451904297s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 109.14161276817322s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 22.775397300720215s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.44655346870422363s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.2773270606994629s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.28649258613586426s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 7.246287822723389s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.9192342758178711s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6883955001831055s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.4366168975830078s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 65.2459979057312s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.472073554992676s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.554066181182861s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.4979040622711182s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.72787857055664s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7350637912750244s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.43363499641418457s
Security | Sign check for Bio2RDF::Orphanet took 0.27138304710388184s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 11.461720705032349s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 23.562736988067627s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.023222923278808594s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.001168966293334961s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 9.751319885253906e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 30.341132164001465s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-orphanet took 1158.7145609855652s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.1400315761566162s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0004107952117919922s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 30.73561954498291s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020882129669189453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.314018249511719e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 193.68658256530762s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.638970136642456s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0011560916900634766s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 18.48897099494934s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.2759883403778076s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 45.80223107337952s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 43.62477922439575s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.250887870788574s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.26479220390319824s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.15436697006225586s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 1.2041780948638916s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.3083193302154541s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 1.897383213043213s
License | MR license check for Bio2RDF::Pharmgkb took 0.5544710159301758s
License | HR license check for Bio2RDF::Pharmgkb took 60.266664028167725s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.2726287841796875s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 9.538525819778442s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.6118037700653076s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.23633599281311035s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.2612745761871338s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.2395167350769043s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.023340463638306s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 82.67575335502625s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.5906393527984619s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.35362887382507324s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.8007979393005371s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.35802412033081055s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.2513558864593506s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.5112969875335693s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.5059034824371338s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 108.8975145816803s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 31.044371604919434s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.45705294609069824s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.2747173309326172s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.28625988960266113s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 7.366560935974121s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.9075188636779785s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.6951498985290527s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.4300498962402344s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 65.11469340324402s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.4473986625671387s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 6.496676921844482s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.5104727745056152s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.727548599243164s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7365913391113281s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.4341850280761719s
Security | Sign check for Bio2RDF::Pharmgkb took 0.28519749641418457s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 9.992055177688599s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.49606919288635254s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.02106761932373047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.462501525878906e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 40.28905010223389s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-pharmgkb took 1258.4801683425903s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.48239827156066895s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0006234645843505859s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 19.320679664611816s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2966079711914062s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 46.131500005722046s
Interoperability | New terms check for Bio2RDF::Pubmed took 41.66825294494629s
Versatility | Languages check for Bio2RDF::Pubmed took 60.25105381011963s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.2545430660247803s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.15137720108032227s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.6914865970611572s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.30345702171325684s
Availability | RDF dump link check for Bio2RDF::Pubmed took 1.9636483192443848s
License | MR license check for Bio2RDF::Pubmed took 0.45058155059814453s
License | HR license check for Bio2RDF::Pubmed took 60.25952482223511s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.3136107921600342s
Understandability | Number of label check for Bio2RDF::Pubmed took 9.75527310371399s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.6437227725982666s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.2725818157196045s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.3039510250091553s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.2738938331604004s
Performance | Throughput check for Bio2RDF::Pubmed took 10.937623500823975s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 82.18149662017822s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.5989305973052979s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.3864724636077881s
Interlinking | skos check for Bio2RDF::Pubmed took 0.9702556133270264s
Interlinking | skos check for Bio2RDF::Pubmed took 0.521897554397583s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.28319859504699707s
Currency | Creation date check for Bio2RDF::Pubmed took 0.5787124633789062s
Currency | Modification date check for Bio2RDF::Pubmed took 0.5764467716217041s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 111.65557980537415s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 25.74614715576172s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.510582685470581s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.3064267635345459s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.2925913333892822s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 7.25399374961853s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.9051821231842041s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6928153038024902s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.5855293273925781s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.93148398399353s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.4982717037200928s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.751861572265625s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.397937297821045s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.68449282646179s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.7230963706970215s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.4996457099914551s
Security | Sign check for Bio2RDF::Pubmed took 0.2859935760498047s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 9.989484548568726s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 23.300061464309692s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.021279573440551758s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00014495849609375s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 26.632031202316284s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-pubmed took 1233.6445143222809s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.13835430145263672s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.3021240234375s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.021889448165893555s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 8.320808410644531e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 9.5367431640625e-06s
INFO | --- Analysis for bio2rdf-sabiork took 158.2746422290802s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.6828136444091797s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.00042176246643066406s
Extra | Recovery of all triples for Bio2RDF::Sgd took 19.342301845550537s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.3531529903411865s
Amount of data | Number of triples check for Bio2RDF::Sgd took 46.30908489227295s
Interoperability | New terms check for Bio2RDF::Sgd took 44.62471127510071s
Versatility | Languages check for Bio2RDF::Sgd took 60.309340476989746s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.29400062561035156s
Security | Check HTTPS for Bio2RDF::Sgd took 0.18186640739440918s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.7318007946014404s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.3370974063873291s
Availability | RDF dump link check for Bio2RDF::Sgd took 2.0933659076690674s
License | MR license check for Bio2RDF::Sgd took 0.5854566097259521s
License | HR license check for Bio2RDF::Sgd took 60.287461042404175s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.2855832576751709s
Understandability | Number of label check for Bio2RDF::Sgd took 10.30939769744873s
Understandability | URI regex check for Bio2RDF::Sgd took 0.6433191299438477s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.2727658748626709s
Verifiability | Authors check for Bio2RDF::Sgd took 0.2990758419036865s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.2806696891784668s
Performance | Throughput check for Bio2RDF::Sgd took 11.10617733001709s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 82.7075936794281s
Verifiability | Contribs. check for Bio2RDF::Sgd took 0.6439588069915771s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.3581390380859375s
Interlinking | skos check for Bio2RDF::Sgd took 0.743614673614502s
Interlinking | skos check for Bio2RDF::Sgd took 0.4304220676422119s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.288236141204834s
Currency | Creation date check for Bio2RDF::Sgd took 0.5683865547180176s
Currency | Modification date check for Bio2RDF::Sgd took 0.5555191040039062s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 108.83703565597534s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 24.384350299835205s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.4877140522003174s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.3074936866760254s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.30258655548095703s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 7.474096059799194s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.9047927856445312s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6776642799377441s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.5432794094085693s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 65.14981389045715s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.4596500396728516s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 6.599966049194336s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.4890267848968506s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.743093490600586s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.7187020778656006s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.45686984062194824s
Security | Sign check for Bio2RDF::Sgd took 0.28769779205322266s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 12.281595706939697s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 25.49838924407959s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.026749610900878906s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00011181831359863281s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 44.213167667388916s
Believability | Calculation of trust value for Bio2RDF::Sgd took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-sgd took 1251.8857510089874s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.363059997558594e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.33971619606018066s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.021329641342163086s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0011756420135498047s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 5.030632019042969e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-sgd-resources took 126.8901584148407s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.6648814678192139s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0006003379821777344s
Extra | Recovery of all triples for Bio2RDF::Sider took 19.900680541992188s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.3780510425567627s
Amount of data | Number of triples check for Bio2RDF::Sider took 47.15063738822937s
Interoperability | New terms check for Bio2RDF::Sider took 41.89888310432434s
Versatility | Languages check for Bio2RDF::Sider took 60.315205812454224s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.30790114402770996s
Security | Check HTTPS for Bio2RDF::Sider took 0.17289376258850098s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.4988226890563965s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.3427767753601074s
Availability | RDF dump link check for Bio2RDF::Sider took 2.0429580211639404s
License | MR license check for Bio2RDF::Sider took 0.5947966575622559s
License | HR license check for Bio2RDF::Sider took 60.263128995895386s
Amount of data | Number of property check for Bio2RDF::Sider took 0.2765648365020752s
Understandability | Number of label check for Bio2RDF::Sider took 9.890260696411133s
Understandability | URI regex check for Bio2RDF::Sider took 0.614387035369873s
Understandability | Vocabs check for Bio2RDF::Sider took 0.2742013931274414s
Verifiability | Authors check for Bio2RDF::Sider took 0.2965264320373535s
Verifiability | Publishers check for Bio2RDF::Sider took 0.2840561866760254s
Performance | Throughput check for Bio2RDF::Sider took 10.948190927505493s
Amount of data | Check the number of entities for Bio2RDF::Sider took 80.66952133178711s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.6078526973724365s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.387315034866333s
Interlinking | skos check for Bio2RDF::Sider took 0.745694637298584s
Interlinking | skos check for Bio2RDF::Sider took 0.36096930503845215s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.29789161682128906s
Currency | Creation date check for Bio2RDF::Sider took 0.5837216377258301s
Currency | Modification date check for Bio2RDF::Sider took 0.5757317543029785s
Rep.Conc. | URIs length for Bio2RDF::Sider took 109.73385405540466s
Interoperability | New vocabularies check for Bio2RDF::Sider took 28.496397495269775s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.47023916244506836s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.3198528289794922s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.29613566398620605s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 6.887813329696655s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.8999836444854736s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6785943508148193s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.45511484146118164s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 65.13523030281067s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.507000207901001s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 6.495434284210205s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.4808974266052246s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.757930517196655s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7314281463623047s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.5027732849121094s
Security | Sign check for Bio2RDF::Sider took 0.28575587272644043s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 9.895292282104492s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.5054445266723633s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.021494388580322266s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 5.793571472167969e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 34.67643737792969s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-sider took 1198.8069696426392s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.2438507080078125e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 28.544042348861694s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.02072739601135254s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 6.079673767089844e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-taxon took 157.7837691307068s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.6816411018371582s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0006809234619140625s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 19.362865686416626s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.378202199935913s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 45.65296506881714s
Interoperability | New terms check for Bio2RDF::Taxonomy took 41.32297396659851s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.32213091850281s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.2955818176269531s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.18209171295166016s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 0.8780574798583984s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.3510148525238037s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 2.0795929431915283s
License | MR license check for Bio2RDF::Taxonomy took 0.4957313537597656s
License | HR license check for Bio2RDF::Taxonomy took 60.27496910095215s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.28568363189697266s
Understandability | Number of label check for Bio2RDF::Taxonomy took 9.403512716293335s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.6637346744537354s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.27748584747314453s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.30726027488708496s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.28174662590026855s
Performance | Throughput check for Bio2RDF::Taxonomy took 11.124598264694214s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 82.2023515701294s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.6055958271026611s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.40014171600341797s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.9603326320648193s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.39287829399108887s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.2875401973724365s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.590038537979126s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.5682404041290283s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 108.6097400188446s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 17.843664169311523s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.49152517318725586s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.3118124008178711s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.29670286178588867s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 6.841640949249268s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.9100301265716553s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6802706718444824s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.5373663902282715s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 65.34748959541321s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.477485418319702s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 7.098895072937012s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.4990296363830566s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.772294759750366s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7385118007659912s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.47301268577575684s
Security | Sign check for Bio2RDF::Taxonomy took 0.3184340000152588s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 10.481276273727417s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.42656636238098145s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.021120071411132812s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.0001289844512939453s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 20.942270040512085s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-taxonomy took 1180.5357687473297s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.13565683364868164s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0004048347473144531s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.29514431953430176s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.02114701271057129s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 4.863739013671875e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 88.4882423877716s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.6642396450042725s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0006780624389648438s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 19.447046041488647s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.366006851196289s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 45.75009536743164s
Interoperability | New terms check for Bio2RDF::Wormbase took 41.29783844947815s
Versatility | Languages check for Bio2RDF::Wormbase took 60.282397985458374s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.29728150367736816s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.16847729682922363s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.29534244537353516s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.4031534194946289s
Availability | RDF dump link check for Bio2RDF::Wormbase took 2.3227176666259766s
License | MR license check for Bio2RDF::Wormbase took 0.5339615345001221s
License | HR license check for Bio2RDF::Wormbase took 60.26559829711914s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.28105854988098145s
Understandability | Number of label check for Bio2RDF::Wormbase took 9.833310604095459s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.652991771697998s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.2745811939239502s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.2974119186401367s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.2904696464538574s
Performance | Throughput check for Bio2RDF::Wormbase took 11.117777347564697s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 82.921710729599s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.6157684326171875s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.41001152992248535s
Interlinking | skos check for Bio2RDF::Wormbase took 0.9254755973815918s
Interlinking | skos check for Bio2RDF::Wormbase took 0.3766500949859619s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.27651429176330566s
Currency | Creation date check for Bio2RDF::Wormbase took 0.5921740531921387s
Currency | Modification date check for Bio2RDF::Wormbase took 0.5908663272857666s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 108.2892553806305s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 23.684282779693604s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.46184825897216797s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.2992515563964844s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.30141520500183105s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 7.361802816390991s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.9047122001647949s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6866321563720703s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.4992799758911133s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 65.26181840896606s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.4995291233062744s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 6.6007490158081055s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.4920053482055664s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.77657628059387s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7207913398742676s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.4856140613555908s
Security | Sign check for Bio2RDF::Wormbase took 0.29717493057250977s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 12.024296283721924s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.556283712387085s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.020967721939086914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.559226989746094e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 19.97815465927124s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-wormbase took 1176.5528552532196s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.27974987030029297s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 29.709651708602905s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.02231121063232422s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0010213851928710938s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 0.00013184547424316406s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 1.1205673217773438e-05s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 179.30802989006042s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 4.1961669921875e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 27.481796503067017s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.020841121673583984s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 4.220008850097656e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 1.2159347534179688e-05s
INFO | --- Analysis for biolod-pdb took 133.9885609149933s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.6069056987762451s
Availability | VoID file availability check for BioModels RDF took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for BioModels RDF took 22.617104291915894s
Reputation | Calculation of the PageRank for BioModels RDF took 0.021296977996826172s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0008251667022705078s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 5.221366882324219e-05s
Believability | Calculation of trust value for BioModels RDF took 1.1444091796875e-05s
INFO | --- Analysis for biomodels-rdf took 125.60430884361267s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.162414073944092s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 27.99669313430786s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.021179914474487305s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.504753112792969e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 7.3909759521484375e-06s
INFO | --- Analysis for Biop took 168.12759447097778s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.57763671875e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0004229545593261719s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 28.080862522125244s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.021254777908325195s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.076957702636719e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1444091796875e-05s
INFO | --- Analysis for Bioportal took 130.39184403419495s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 8.845329284667969e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.0006132125854492188s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 25.075706958770752s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.026511192321777344s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006549358367919922s
Believability | Calculation of trust value for Amphibian gross anatomy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-aao took 198.89598751068115s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.38690185546875e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 26.847909927368164s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.02493429183959961s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0012958049774169922s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.00039958953857421875s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-aba took 184.63076376914978s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 28.87496280670166s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.021756887435913086s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015382766723632812s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-acgt took 102.38658237457275s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 5.6743621826171875e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0003192424774169922s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 29.82921552658081s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.022213459014892578s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0008633136749267578s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0004096031188964844s
Believability | Calculation of trust value for Animal natural history and life history took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-adw took 208.44577288627625s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 22.4499032497406s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.021422386169433594s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0005395412445068359s
Believability | Calculation of trust value for Anatomical Entity Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-aeo took 144.2641909122467s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 5.316734313964844e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.00034928321838378906s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 23.060348510742188s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.021788358688354492s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0010356903076171875s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-aero took 150.85837697982788s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.5299530029296875e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0003235340118408203s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 33.417396545410156s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.021404266357421875s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0009119510650634766s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0004782676696777344s
Believability | Calculation of trust value for AI/RHEUM took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-air took 155.66079759597778s
Availability | SPARQL endpoint availability check for Amino Acid took 4.744529724121094e-05s
Availability | VoID file availability check for Amino Acid took 0.00033974647521972656s
Completeness | Calculation of interlinking completeness for Amino Acid took 25.85317063331604s
Reputation | Calculation of the PageRank for Amino Acid took 0.024850130081176758s
Interlinking | Calculation of Degree of Connection for Amino Acid took 2.7894973754882812e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0012252330780029297s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.00034689903259277344s
Believability | Calculation of trust value for Amino Acid took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-amino-acid took 193.2886266708374s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 5.507469177246094e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 29.24715828895569s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.023497581481933594s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0002930164337158203s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-apo took 170.40069484710693s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 0.00010395050048828125s
Availability | VoID file availability check for African Traditional Medicine took 0.0003116130828857422s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 23.755804538726807s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.02176356315612793s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00026035308837890625s
Believability | Calculation of trust value for African Traditional Medicine took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-atmo took 171.47475624084473s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.673004150390625e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0003497600555419922s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 23.48610544204712s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.02508687973022461s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.001300811767578125s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 0.00012803077697753906s
Believability | Calculation of trust value for Amphibian taxonomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ato took 136.86964631080627s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 5.030632019042969e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 27.895442247390747s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.02134227752685547s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.00135040283203125s
Believability | Calculation of trust value for BioAssay Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-bao took 204.60737657546997s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 9.870529174804688e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 27.319275379180908s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.021236419677734375s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0004172325134277344s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 177.07422947883606s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 8.440017700195312e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.3021402359008789s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.02119588851928711s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003514289855957031s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-bcgo took 116.8288745880127s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.29068922996520996s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.02279376983642578s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0014061927795410156s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-bdo took 155.1431384086609s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 9.036064147949219e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 28.983664512634277s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.020838022232055664s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0005021095275878906s
Believability | Calculation of trust value for Basic Formal Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-bfo took 173.23358845710754s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 8.797645568847656e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.3085668087005615s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.020878076553344727s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007269382476806641s
Believability | Calculation of trust value for Bleeding History Phenotype took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-bho took 194.06576371192932s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 8.821487426757812e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0005998611450195312s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.32931041717529297s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.021182775497436523s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.0004763603210449219s
Believability | Calculation of trust value for Bilateria anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bila took 197.73072934150696s
Availability | SPARQL endpoint availability check for BIRNLex took 5.2928924560546875e-05s
Availability | VoID file availability check for BIRNLex took 0.0005669593811035156s
Completeness | Calculation of interlinking completeness for BIRNLex took 28.979827404022217s
Reputation | Calculation of the PageRank for BIRNLex took 0.02156352996826172s
Interlinking | Calculation of Degree of Connection for BIRNLex took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014946460723876953s
Believability | Calculation of trust value for BIRNLex took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-birnlex took 206.52563738822937s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 5.8650970458984375e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005459785461425781s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 27.96897292137146s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02069091796875s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0008308887481689453s
Believability | Calculation of trust value for Gene Regulation Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bootstrep took 130.84859418869019s
Availability | SPARQL endpoint availability check for BioPAX took 8.988380432128906e-05s
Availability | VoID file availability check for BioPAX took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for BioPAX took 31.339922428131104s
Reputation | Calculation of the PageRank for BioPAX took 0.02126169204711914s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for BioPAX took 9.894371032714844e-05s
Believability | Calculation of trust value for BioPAX took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-bp took 111.75888395309448s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.3231689929962158s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.020992040634155273s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.00035262107849121094s
Believability | Calculation of trust value for Biomedical Resource Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-bro_x1 took 157.1628406047821s
Availability | SPARQL endpoint availability check for Spatial Ontology took 9.465217590332031e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0006823539733886719s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 30.48798704147339s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.020990371704101562s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.0002162456512451172s
Believability | Calculation of trust value for Spatial Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-bspo took 105.10052490234375s
Availability | SPARQL endpoint availability check for BioTop took 0.000110626220703125s
Availability | VoID file availability check for BioTop took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for BioTop took 28.64815402030945s
Reputation | Calculation of the PageRank for BioTop took 0.021091461181640625s
Interlinking | Calculation of Degree of Connection for BioTop took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006814002990722656s
Believability | Calculation of trust value for BioTop took 1.5497207641601562e-05s
INFO | --- Analysis for bioportal-bt took 149.97782254219055s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.601478576660156e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0006909370422363281s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.31166887283325195s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.02093362808227539s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008878707885742188s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-bto took 142.06427145004272s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3489086627960205s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.021445035934448242s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0019805431365966797s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-canco took 113.02044248580933s
Availability | SPARQL endpoint availability check for CAO took 9.059906005859375e-05s
Availability | VoID file availability check for CAO took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for CAO took 21.203731536865234s
Reputation | Calculation of the PageRank for CAO took 0.021146535873413086s
Interlinking | Calculation of Degree of Connection for CAO took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for CAO took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0006394386291503906s
Believability | Calculation of trust value for CAO took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-cao took 142.46583676338196s
Availability | SPARQL endpoint availability check for CareLex took 4.220008850097656e-05s
Availability | VoID file availability check for CareLex took 0.0006003379821777344s
Completeness | Calculation of interlinking completeness for CareLex took 0.3249685764312744s
Reputation | Calculation of the PageRank for CareLex took 0.021093368530273438s
Interlinking | Calculation of Degree of Connection for CareLex took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CareLex took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for CareLex took 5.793571472167969e-05s
Believability | Calculation of trust value for CareLex took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-carelex took 149.1878046989441s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.32947564125061035s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.023452281951904297s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.00092315673828125s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0009391307830810547s
Believability | Calculation of trust value for Cell Cycle Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cco took 211.304345369339s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.31931352615356445s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020962238311767578s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.00028705596923828125s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-cdao took 158.62900519371033s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 4.124641418457031e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0005793571472167969s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 21.98470163345337s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.020920515060424805s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0008065700531005859s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0008358955383300781s
Believability | Calculation of trust value for Chemical entities of biological interest took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-chebi took 129.46668982505798s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 8.893013000488281e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.3511481285095215s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.022707700729370117s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.000263214111328125s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 1.430511474609375e-05s
INFO | --- Analysis for bioportal-chem2bio2owl took 147.30865025520325s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 21.405869960784912s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.02069544792175293s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007967948913574219s
Believability | Calculation of trust value for Chemical Information Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-cheminf took 157.43720483779907s
Availability | SPARQL endpoint availability check for Cell type took 8.606910705566406e-05s
Availability | VoID file availability check for Cell type took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for Cell type took 0.35794496536254883s
Reputation | Calculation of the PageRank for Cell type took 0.030599117279052734s
Interlinking | Calculation of Degree of Connection for Cell type took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0004336833953857422s
Believability | Calculation of trust value for Cell type took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-cl took 147.1693365573883s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 9.083747863769531e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0006682872772216797s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.32561373710632324s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.020874500274658203s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008578300476074219s
Believability | Calculation of trust value for Cell Line Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-clo took 165.47598338127136s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 21.300419569015503s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.02142477035522461s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00020837783813476562s
Believability | Calculation of trust value for Clinical Measurement Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cmo took 218.97793745994568s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.9114227294921875e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 29.493978023529053s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.021254301071166992s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.0002315044403076172s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cno took 174.61253905296326s
Availability | SPARQL endpoint availability check for Wheat trait took 8.606910705566406e-05s
Availability | VoID file availability check for Wheat trait took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for Wheat trait took 22.705857276916504s
Reputation | Calculation of the PageRank for Wheat trait took 0.02066349983215332s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.507469177246094e-05s
Believability | Calculation of trust value for Wheat trait took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-co_wheat took 133.89807510375977s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.220008850097656e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 25.046544790267944s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.021184921264648438s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.00036835670471191406s
Believability | Calculation of trust value for Cognitive Atlas took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cogat took 192.23493099212646s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 0.00014734268188476562s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.3116629123687744s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020917892456054688s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007801055908203125s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007929801940917969s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-cogpo took 92.00055193901062s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 8.940696716308594e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 22.718884229660034s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.022151947021484375s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.00044035911560058594s
Believability | Calculation of trust value for Current Procedural Terminology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-cpt took 120.94845175743103s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 8.821487426757812e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 29.311273336410522s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.022904634475708008s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0008721351623535156s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0019235610961914062s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-csp took 127.82594180107117s
Availability | SPARQL endpoint availability check for COSTART took 0.0001499652862548828s
Availability | VoID file availability check for COSTART took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for COSTART took 0.327350378036499s
Reputation | Calculation of the PageRank for COSTART took 0.021001100540161133s
Interlinking | Calculation of Degree of Connection for COSTART took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0010073184967041016s
Believability | Calculation of trust value for COSTART took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-cst took 153.09981441497803s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.1961669921875e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 23.17409348487854s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.02089214324951172s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0005156993865966797s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ctcae took 145.02896213531494s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 4.172325134277344e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0006804466247558594s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 22.538052082061768s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.020983457565307617s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004649162292480469s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ctx took 175.358624458313s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.649162292480469e-05s
Availability | VoID file availability check for Dendritic cell took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for Dendritic cell took 31.08907985687256s
Reputation | Calculation of the PageRank for Dendritic cell took 0.02294015884399414s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.00032901763916015625s
Believability | Calculation of trust value for Dendritic cell took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-dc_cl took 152.29789686203003s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 0.0001556873321533203s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 26.359959602355957s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.022263526916503906s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 9.322166442871094e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ddanat took 182.36083674430847s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.4345855712890625e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0003261566162109375s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.30185937881469727s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.023016691207885742s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0010101795196533203s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-ddi took 122.7157838344574s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 0.00015735626220703125s
Availability | VoID file availability check for Diagnostic Ontology took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.2929542064666748s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.02184128761291504s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 0.00010037422180175781s
Believability | Calculation of trust value for Diagnostic Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-diagnosticont took 158.35305404663086s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.792213439941406e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.3612971305847168s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.028754711151123047s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0009129047393798828s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00022101402282714844s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 82.73783373832703s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.839897155761719e-05s
Availability | VoID file availability check for Human disease ontology took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.36159300804138184s
Reputation | Calculation of the PageRank for Human disease ontology took 0.03038477897644043s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.001543283462524414s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0009229183197021484s
Believability | Calculation of trust value for Human disease ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-doid took 144.94096517562866s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.3392481803894043s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.020788192749023438s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008134841918945312s
Believability | Calculation of trust value for Electrocardiography Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ecg took 129.40140533447266s
Availability | SPARQL endpoint availability check for Evidence codes took 4.887580871582031e-05s
Availability | VoID file availability check for Evidence codes took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.30252981185913086s
Reputation | Calculation of the PageRank for Evidence codes took 0.021472692489624023s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 4.220008850097656e-05s
Believability | Calculation of trust value for Evidence codes took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-eco took 122.48140096664429s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 8.96453857421875e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.4259324073791504s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.02129387855529785s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0018160343170166016s
Believability | Calculation of trust value for Experimental Factor Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-efo took 137.7291259765625s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.363059997558594e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 30.796124696731567s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.02090907096862793s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0012197494506835938s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ehda took 131.46649193763733s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.267692565917969e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 28.935091972351074s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.021032333374023438s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007507801055908203s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ehdaa took 144.40496349334717s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.506111145019531e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 28.43734884262085s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.021030902862548828s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005624294281005859s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 187.06617879867554s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 8.726119995117188e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 21.701277256011963s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.020851850509643555s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 3.9577484130859375e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-emap took 72.44001269340515s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for Environment Ontology took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for Environment Ontology took 22.182952880859375s
Reputation | Calculation of the PageRank for Environment Ontology took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.00042629241943359375s
Believability | Calculation of trust value for Environment Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-envo took 126.4183599948883s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 4.220008850097656e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.3209114074707031s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.021543502807617188s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.000331878662109375s
Believability | Calculation of trust value for Plant environmental conditions took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-eo took 173.95459699630737s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 8.225440979003906e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.33956480026245117s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.021375656127929688s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0008897781372070312s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012955665588378906s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ep took 225.35262036323547s
Availability | SPARQL endpoint availability check for Epilepsy took 4.220008850097656e-05s
Availability | VoID file availability check for Epilepsy took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.32726240158081055s
Reputation | Calculation of the PageRank for Epilepsy took 0.021355867385864258s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.00016880035400390625s
Believability | Calculation of trust value for Epilepsy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-epileponto took 80.17678308486938s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.9114227294921875e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.340118408203125s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.02081155776977539s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0008342266082763672s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011844635009765625s
Believability | Calculation of trust value for eagle-i research resource ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-ero took 96.91967487335205s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.00012445449829101562s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 29.88344407081604s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.022448062896728516s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011703968048095703s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ev took 225.73889565467834s
Availability | SPARQL endpoint availability check for ExO took 8.726119995117188e-05s
Availability | VoID file availability check for ExO took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for ExO took 22.045226097106934s
Reputation | Calculation of the PageRank for ExO took 0.0215151309967041s
Interlinking | Calculation of Degree of Connection for ExO took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for ExO took 0.0009205341339111328s
Interlinking | Calculation of Clustering coefficient for ExO took 0.0003032684326171875s
Believability | Calculation of trust value for ExO took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-exo took 129.8437535762787s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 8.821487426757812e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.35982847213745117s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.02275872230529785s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0008428096771240234s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.0001316070556640625s
Believability | Calculation of trust value for Fungal gross anatomy took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-fao took 138.53495740890503s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.38690185546875e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.3346121311187744s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.023238658905029297s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00020694732666015625s
Believability | Calculation of trust value for Biological imaging methods took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-fbbi took 99.74095249176025s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 4.291534423828125e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.00030350685119628906s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.2984757423400879s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.02059459686279297s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006654262542724609s
Believability | Calculation of trust value for Drosophila gross anatomy took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-fbbt took 105.79960131645203s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 0.00015616416931152344s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.3025209903717041s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.027338027954101562s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.00043702125549316406s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-fbcv took 142.74116230010986s
Availability | SPARQL endpoint availability check for Drosophila development took 8.559226989746094e-05s
Availability | VoID file availability check for Drosophila development took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.37918758392333984s
Reputation | Calculation of the PageRank for Drosophila development took 0.020895719528198242s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.887580871582031e-05s
Believability | Calculation of trust value for Drosophila development took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-fbdv took 105.782057762146s
Availability | SPARQL endpoint availability check for Fly taxonomy took 0.00013709068298339844s
Availability | VoID file availability check for Fly taxonomy took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.28935861587524414s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.021875858306884766s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0008821487426757812s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0004425048828125s
Believability | Calculation of trust value for Fly taxonomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-fbsp took 93.15125775337219s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.3392181396484375e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 26.7322940826416s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.021168947219848633s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.0002262592315673828s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 154.2320282459259s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0005736351013183594s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 20.779035091400146s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.021291732788085938s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0010635852813720703s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0005459785461425781s
Believability | Calculation of trust value for Family Health History Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-fhho took 164.01986122131348s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 28.96562433242798s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.020735740661621094s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0010743141174316406s
Believability | Calculation of trust value for Influenza Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-flu took 83.79982852935791s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 0.00010728836059570312s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.2893393039703369s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.02106499671936035s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.914138793945312e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-fma took 71.12429785728455s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 9.441375732421875e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 27.713844776153564s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.020946502685546875s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 2.288818359375e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007989406585693359s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00014829635620117188s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-fypo took 172.77253127098083s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.3155817985534668s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.021093130111694336s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 0.00010013580322265625s
Believability | Calculation of trust value for GeoSpecies Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-geospecies took 106.49194407463074s
Availability | SPARQL endpoint availability check for General Formal Ontology took 8.344650268554688e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 29.920233011245728s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.020793437957763672s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.0002148151397705078s
Believability | Calculation of trust value for General Formal Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-gfo took 151.04724097251892s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 8.845329284667969e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 29.010857105255127s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.020777225494384766s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0006110668182373047s
Believability | Calculation of trust value for General Formal Ontology: Biology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-gfo-bio took 154.63857984542847s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.3392181396484375e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0005848407745361328s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.3413856029510498s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.021886110305786133s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0009505748748779297s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0010528564453125s
Believability | Calculation of trust value for Gene Ontology Extension took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-go_x1 took 205.04377222061157s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.839897155761719e-05s
Availability | VoID file availability check for Gene Ontology took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.2980372905731201s
Reputation | Calculation of the PageRank for Gene Ontology took 0.021399497985839844s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0009403228759765625s
Believability | Calculation of trust value for Gene Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-go_x2 took 79.83769631385803s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 5.125999450683594e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 31.255642652511597s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.02061748504638672s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.409385681152344e-05s
Believability | Calculation of trust value for Cereal Plant Development took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-gro took 155.57405805587769s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.172325134277344e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 23.97899866104126s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.020861148834228516s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.00045800209045410156s
Believability | Calculation of trust value for Cereal plant gross anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-gro_x1 took 146.09866452217102s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.000316619873046875s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 23.380589246749878s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02307295799255371s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007894039154052734s
Believability | Calculation of trust value for Gene Regulation Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-gro_x2 took 153.44249629974365s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.0005502700805664062s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.3140904903411865s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.021396398544311523s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0008041858673095703s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0006349086761474609s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-hao took 113.04866790771484s
Availability | SPARQL endpoint availability check for HCPCS took 0.00010752677917480469s
Availability | VoID file availability check for HCPCS took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for HCPCS took 27.483508825302124s
Reputation | Calculation of the PageRank for HCPCS took 0.021087646484375s
Interlinking | Calculation of Degree of Connection for HCPCS took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0008096694946289062s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.0002429485321044922s
Believability | Calculation of trust value for HCPCS took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-hcpcs took 207.2082827091217s
Availability | SPARQL endpoint availability check for Health Level Seven took 4.482269287109375e-05s
Availability | VoID file availability check for Health Level Seven took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for Health Level Seven took 18.712345123291016s
Reputation | Calculation of the PageRank for Health Level Seven took 0.02094244956970215s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012814998626708984s
Believability | Calculation of trust value for Health Level Seven took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-hl7 took 179.63176107406616s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 5.1021575927734375e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.34239673614501953s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.02255392074584961s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.00039696693420410156s
Believability | Calculation of trust value for HEALTH_INDICATORS took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-hlth_indics took 156.55005478858948s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 4.267692565917969e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.3228607177734375s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.021286964416503906s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.409385681152344e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-hom took 66.14942264556885s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.744529724121094e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 29.46236562728882s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.021266937255859375s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 2.3603439331054688e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 4.2438507080078125e-05s
Believability | Calculation of trust value for HOM-HARVARD took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-hom_harvard took 183.65914916992188s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0003218650817871094s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.4025747776031494s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.03318047523498535s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0013988018035888672s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0008995532989501953s
Believability | Calculation of trust value for Human Phenotype Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-hp_x1 took 130.17122268676758s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.381274938583374s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.02081298828125s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010509490966796875s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-hpio took 142.8772382736206s
Availability | SPARQL endpoint availability check for HUGO took 8.678436279296875e-05s
Availability | VoID file availability check for HUGO took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for HUGO took 21.10715937614441s
Reputation | Calculation of the PageRank for HUGO took 0.023508071899414062s
Interlinking | Calculation of Degree of Connection for HUGO took 2.4557113647460938e-05s
Interlinking | Calculation of Centrality for HUGO took 0.0010263919830322266s
Interlinking | Calculation of Clustering coefficient for HUGO took 0.00011277198791503906s
Believability | Calculation of trust value for HUGO took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-hugo took 189.79786252975464s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 26.43493342399597s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.021126508712768555s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0008556842803955078s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0007412433624267578s
Believability | Calculation of trust value for Information Artifact Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-iao took 147.17411589622498s
Availability | SPARQL endpoint availability check for ICD10 took 0.00010657310485839844s
Availability | VoID file availability check for ICD10 took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for ICD10 took 27.474953651428223s
Reputation | Calculation of the PageRank for ICD10 took 0.02086782455444336s
Interlinking | Calculation of Degree of Connection for ICD10 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ICD10 took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0008232593536376953s
Believability | Calculation of trust value for ICD10 took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-icd10 took 84.77721214294434s
Availability | SPARQL endpoint availability check for ICD10CM took 4.315376281738281e-05s
Availability | VoID file availability check for ICD10CM took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.3115806579589844s
Reputation | Calculation of the PageRank for ICD10CM took 0.021030426025390625s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006120204925537109s
Believability | Calculation of trust value for ICD10CM took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-icd10cm took 56.88507318496704s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.267692565917969e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.3014233112335205s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.0210568904876709s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.0001819133758544922s
Believability | Calculation of trust value for ICD-10-PCS took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-icd10pcs took 137.8690004348755s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 9.989738464355469e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 23.577932596206665s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020994901657104492s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006885528564453125s
Believability | Calculation of trust value for International Classification of Diseases took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-icd9cm took 219.2599663734436s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 8.559226989746094e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.3220088481903076s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.021236658096313477s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004642009735107422s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-icf_x1 took 74.3539559841156s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 8.368492126464844e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 24.195786952972412s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.0227658748626709s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.001424551010131836s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0015482902526855469s
Believability | Calculation of trust value for International Classification for Nursing Practice took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-icnp took 127.65077257156372s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 4.172325134277344e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.000316619873046875s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 29.80694556236267s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.021017074584960938s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.00046372413635253906s
Believability | Calculation of trust value for International Classification of Primary Care took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-icpc took 126.9306640625s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 4.1961669921875e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.34242820739746094s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.022162199020385742s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008571147918701172s
Believability | Calculation of trust value for ICPC-2 PLUS took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icpc2p took 122.98923468589783s
Availability | SPARQL endpoint availability check for ICPS Network took 8.153915405273438e-05s
Availability | VoID file availability check for ICPS Network took 0.00034117698669433594s
Completeness | Calculation of interlinking completeness for ICPS Network took 20.210809469223022s
Reputation | Calculation of the PageRank for ICPS Network took 0.022251129150390625s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.0002562999725341797s
Believability | Calculation of trust value for ICPS Network took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-icps took 139.80805587768555s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 5.078315734863281e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 27.888957500457764s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.020945310592651367s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0008385181427001953s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0009491443634033203s
Believability | Calculation of trust value for Infectious Disease Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ido took 139.00485944747925s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 9.512901306152344e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 23.9494149684906s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.023076772689819336s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0012099742889404297s
Believability | Calculation of trust value for Brucellosis Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-idobru took 177.43782234191895s
Availability | SPARQL endpoint availability check for Malaria Ontology took 0.0001590251922607422s
Availability | VoID file availability check for Malaria Ontology took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.3069303035736084s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.020893573760986328s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007767677307128906s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.001308441162109375s
Believability | Calculation of trust value for Malaria Ontology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-idomal took 186.3282504081726s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 0.000213623046875s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0003285408020019531s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 29.215533018112183s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020985126495361328s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0003533363342285156s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-iev took 79.03231620788574s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 0.00015807151794433594s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0003151893615722656s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.2995786666870117s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.022809743881225586s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00018262863159179688s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-imgt took 82.8150863647461s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.2438507080078125e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0005803108215332031s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.3219156265258789s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020782947540283203s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005478858947753906s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-imr took 147.43362879753113s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 8.487701416015625e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.29243040084838867s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.020778894424438477s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0008087158203125s
Believability | Calculation of trust value for Interaction Network Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ino took 140.84075736999512s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.220008850097656e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 20.177226781845093s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.022045612335205078s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.409385681152344e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-invertebrata took 99.58243107795715s
Availability | SPARQL endpoint availability check for IxnO took 8.487701416015625e-05s
Availability | VoID file availability check for IxnO took 0.0005502700805664062s
Completeness | Calculation of interlinking completeness for IxnO took 22.48873734474182s
Reputation | Calculation of the PageRank for IxnO took 0.020781993865966797s
Interlinking | Calculation of Degree of Connection for IxnO took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00019812583923339844s
Believability | Calculation of trust value for IxnO took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ixno took 152.6980710029602s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.124641418457031e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 26.712450742721558s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.021231651306152344s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.00043582916259765625s
Believability | Calculation of trust value for SysMO-JERM took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-jerm took 149.9463369846344s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.29326438903808594s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.02117919921875s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 6.604194641113281e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-kisao took 125.7233157157898s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.3392181396484375e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.3522524833679199s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.020612478256225586s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00021219253540039062s
Believability | Calculation of trust value for Loggerhead nesting took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-lhn took 76.33914589881897s
Availability | SPARQL endpoint availability check for Lipid Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0002963542938232422s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 21.288000106811523s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.02238774299621582s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00020885467529296875s
Believability | Calculation of trust value for Lipid Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-lipro took 125.8410120010376s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.267692565917969e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.35476088523864746s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.026320695877075195s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018792152404785156s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-lnc took 122.08152890205383s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.029273986816406e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0007295608520507812s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.3537256717681885s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.0227963924407959s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0007610321044921875s
Believability | Calculation of trust value for Mouse adult gross anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ma took 113.81831192970276s
Availability | SPARQL endpoint availability check for Multiple alignment took 5.888938903808594e-05s
Availability | VoID file availability check for Multiple alignment took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for Multiple alignment took 30.49111533164978s
Reputation | Calculation of the PageRank for Multiple alignment took 0.02148580551147461s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.0002338886260986328s
Believability | Calculation of trust value for Multiple alignment took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-mao took 180.77220678329468s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 8.702278137207031e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0005693435668945312s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.3150773048400879s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.021048307418823242s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0007963180541992188s
Believability | Calculation of trust value for Minimal anatomical terminology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mat took 165.36687660217285s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 8.416175842285156e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0007028579711914062s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 30.208588123321533s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020966291427612305s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0008323192596435547s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0005080699920654297s
Believability | Calculation of trust value for Breast tissue cell lines took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mcbcc took 110.67339372634888s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.744529724121094e-05s
Availability | VoID file availability check for Cell line ontology took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for Cell line ontology took 28.651127338409424s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020885944366455078s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007557868957519531s
Believability | Calculation of trust value for Cell line ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mccl took 160.80579042434692s
Availability | SPARQL endpoint availability check for Cell line ontology took 0.00011754035949707031s
Availability | VoID file availability check for Cell line ontology took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.38805460929870605s
Reputation | Calculation of the PageRank for Cell line ontology took 0.021324634552001953s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.001535177230834961s
Believability | Calculation of trust value for Cell line ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 165.66731524467468s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 9.369850158691406e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 21.85136604309082s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.022753477096557617s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.00026297569274902344s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mcv took 143.81197786331177s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 0.00012040138244628906s
Availability | VoID file availability check for Master Drug Data Base took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 25.399852514266968s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.02230548858642578s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0008826255798339844s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00021982192993164062s
Believability | Calculation of trust value for Master Drug Data Base took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mddb took 161.5096414089203s
Availability | SPARQL endpoint availability check for MedDRA took 0.0001049041748046875s
Availability | VoID file availability check for MedDRA took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for MedDRA took 0.29427409172058105s
Reputation | Calculation of the PageRank for MedDRA took 0.02170085906982422s
Interlinking | Calculation of Degree of Connection for MedDRA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MedDRA took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011029243469238281s
Believability | Calculation of trust value for MedDRA took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mdr took 85.56135320663452s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 6.818771362304688e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 28.378105401992798s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.020622730255126953s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008826255798339844s
Believability | Calculation of trust value for MedlinePlus Health Topics took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-medlineplus took 149.73441338539124s
Availability | SPARQL endpoint availability check for MeGO took 9.34600830078125e-05s
Availability | VoID file availability check for MeGO took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for MeGO took 29.1169331073761s
Reputation | Calculation of the PageRank for MeGO took 0.022110700607299805s
Interlinking | Calculation of Degree of Connection for MeGO took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00015282630920410156s
Believability | Calculation of trust value for MeGO took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mego took 130.791330575943s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.291534423828125e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0003120899200439453s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 28.02579092979431s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.02083563804626465s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0018990039825439453s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mesh-owl took 188.8410828113556s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.00033020973205566406s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 23.58677911758423s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.021026611328125s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006642341613769531s
Believability | Calculation of trust value for Mental Functioning Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mf took 235.00060510635376s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 0.00011157989501953125s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0004172325134277344s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 27.564180374145508s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.02086186408996582s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005962848663330078s
Believability | Calculation of trust value for Medaka fish anatomy and development took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mfo took 173.74598860740662s
Availability | SPARQL endpoint availability check for Emotion Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 25.811471939086914s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.02080845832824707s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007731914520263672s
Believability | Calculation of trust value for Emotion Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mfoem took 159.12821888923645s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 21.025806188583374s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.021160125732421875s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00012993812561035156s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mhc took 143.5361909866333s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 0.00014638900756835938s
Availability | VoID file availability check for Protein-protein interaction took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 23.408167123794556s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.02104496955871582s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006849765777587891s
Believability | Calculation of trust value for Protein-protein interaction took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mi took 116.28584170341492s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 5.1021575927734375e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 26.436375856399536s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020937204360961914s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007534027099609375s
Believability | Calculation of trust value for Mosquito insecticide resistance took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-miro took 100.90398097038269s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.36551976203918457s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.02086639404296875s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00015592575073242188s
Believability | Calculation of trust value for Measurement Method Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mmo took 93.2942545413971s
Availability | SPARQL endpoint availability check for MGED Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for MGED Ontology took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.3111417293548584s
Reputation | Calculation of the PageRank for MGED Ontology took 0.021570205688476562s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0004100799560546875s
Believability | Calculation of trust value for MGED Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-mo took 71.94801092147827s
Availability | SPARQL endpoint availability check for Protein modification took 8.487701416015625e-05s
Availability | VoID file availability check for Protein modification took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for Protein modification took 0.31942081451416016s
Reputation | Calculation of the PageRank for Protein modification took 0.023209810256958008s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0010175704956054688s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.0002894401550292969s
Believability | Calculation of trust value for Protein modification took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-mod took 135.31037163734436s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.1961669921875e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.32139062881469727s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.021506786346435547s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.000690460205078125s
Believability | Calculation of trust value for Mammalian phenotype took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-mp took 150.98599362373352s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.220008850097656e-05s
Availability | VoID file availability check for Mouse pathology took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.3572566509246826s
Reputation | Calculation of the PageRank for Mouse pathology took 0.0207061767578125s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0005028247833251953s
Believability | Calculation of trust value for Mouse pathology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mpath took 127.64840054512024s
Availability | SPARQL endpoint availability check for Mass spectrometry took 0.00011110305786132812s
Availability | VoID file availability check for Mass spectrometry took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.30222272872924805s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.022069931030273438s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.00038170814514160156s
Believability | Calculation of trust value for Mass spectrometry took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ms took 128.60445261001587s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 8.988380432128906e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.36989378929138184s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.021241426467895508s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.001974344253540039s
Believability | Calculation of trust value for Medical Subject Headings took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-msh took 175.2168152332306s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.291534423828125e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 27.433714866638184s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.02292609214782715s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.0001983642578125s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-mthch took 121.76393604278564s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 9.417533874511719e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 21.182799577713013s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020810604095458984s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0008108615875244141s
Believability | Calculation of trust value for Natural Products Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-natpro took 122.62163257598877s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 4.124641418457031e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.3037381172180176s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.02135467529296875s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008256435394287109s
Believability | Calculation of trust value for NCBI organismal classification took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 24.242651224136353s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 8.821487426757812e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.3360779285430908s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02197575569152832s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0010538101196289062s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0022826194763183594s
Believability | Calculation of trust value for NCI Thesaurus took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ncit took 58.31648063659668s
Availability | SPARQL endpoint availability check for National Drug Data File took 0.00017118453979492188s
Availability | VoID file availability check for National Drug Data File took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for National Drug Data File took 29.040493726730347s
Reputation | Calculation of the PageRank for National Drug Data File took 0.020887374877929688s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006747245788574219s
Believability | Calculation of trust value for National Drug Data File took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-nddf took 188.96230340003967s
Availability | SPARQL endpoint availability check for National Drug File took 0.00013756752014160156s
Availability | VoID file availability check for National Drug File took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for National Drug File took 26.409740686416626s
Reputation | Calculation of the PageRank for National Drug File took 0.0208740234375s
Interlinking | Calculation of Degree of Connection for National Drug File took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0013060569763183594s
Believability | Calculation of trust value for National Drug File took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ndfrt took 161.43661904335022s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 8.940696716308594e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.2973906993865967s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.021696805953979492s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011734962463378906s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 128.30772876739502s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 19.1923987865448s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.021167993545532227s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0007441043853759766s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-neomark took 203.58848810195923s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 9.34600830078125e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0003819465637207031s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 21.596582412719727s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.021831989288330078s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00015544891357421875s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-neomarkontology took 115.23100805282593s
Availability | SPARQL endpoint availability check for NIFSTD took 8.797645568847656e-05s
Availability | VoID file availability check for NIFSTD took 0.0006728172302246094s
Completeness | Calculation of interlinking completeness for NIFSTD took 30.400192260742188s
Reputation | Calculation of the PageRank for NIFSTD took 0.021090030670166016s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0019614696502685547s
Believability | Calculation of trust value for NIFSTD took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-nif took 179.36978006362915s
Availability | SPARQL endpoint availability check for NIF Cell took 9.608268737792969e-05s
Availability | VoID file availability check for NIF Cell took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for NIF Cell took 32.04781532287598s
Reputation | Calculation of the PageRank for NIF Cell took 0.021129608154296875s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.001402139663696289s
Believability | Calculation of trust value for NIF Cell took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-nif_cell took 165.75103998184204s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 8.916854858398438e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 22.608136653900146s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020982742309570312s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0014164447784423828s
Believability | Calculation of trust value for NIF Dysfunction took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 112.78344893455505s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 8.821487426757812e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.00055694580078125s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.30350542068481445s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.02085399627685547s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0006022453308105469s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-nigo took 128.18720173835754s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 8.916854858398438e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 23.307406902313232s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.020891904830932617s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005767345428466797s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-nmr took 148.48512601852417s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 4.601478576660156e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 28.148507356643677s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.021399497985839844s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00011515617370605469s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-nonrctontology took 147.1582944393158s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 9.822845458984375e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.3003580570220947s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.022963523864746094s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.00115966796875s
Believability | Calculation of trust value for NanoParticle Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-npo took 101.55433630943298s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 9.202957153320312e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 32.34335112571716s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.021036624908447266s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007576942443847656s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-oae took 170.00634241104126s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 9.72747802734375e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 22.974407196044922s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.02097630500793457s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0014913082122802734s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-obi took 190.46814131736755s
Availability | SPARQL endpoint availability check for OBOE took 4.792213439941406e-05s
Availability | VoID file availability check for OBOE took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for OBOE took 0.29410529136657715s
Reputation | Calculation of the PageRank for OBOE took 0.020700454711914062s
Interlinking | Calculation of Degree of Connection for OBOE took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00012922286987304688s
Believability | Calculation of trust value for OBOE took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-oboe took 148.78495168685913s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.458427429199219e-05s
Availability | VoID file availability check for OBOE SBC took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for OBOE SBC took 21.855034351348877s
Reputation | Calculation of the PageRank for OBOE SBC took 0.022559165954589844s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0008537769317626953s
Believability | Calculation of trust value for OBOE SBC took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 153.87364792823792s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.172325134277344e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.3412361145019531s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.0217440128326416s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0008344650268554688s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0007359981536865234s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ocre took 86.86776161193848s
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.0003650188446044922s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 21.286476612091064s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.021236896514892578s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008423328399658203s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-odgi took 161.90569233894348s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 7.510185241699219e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0006763935089111328s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.28709936141967773s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.022234201431274414s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0009169578552246094s
Believability | Calculation of trust value for Ontology for Genetic Interval took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ogi took 130.14307117462158s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 5.602836608886719e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.3538646697998047s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.021028757095336914s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.0003161430358886719s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ogmd took 149.99288630485535s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.744529724121094e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.31769871711730957s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.0212252140045166s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 5.245208740234375e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0007116794586181641s
Believability | Calculation of trust value for Ontology for General Medical Science took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ogms took 110.26881885528564s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 8.702278137207031e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.3017232418060303s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.023001670837402344s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011458396911621094s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-omim took 106.89008498191833s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 9.250640869140625e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 26.189356803894043s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.022840023040771484s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0011184215545654297s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0005114078521728516s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-omit took 148.44276022911072s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.291534423828125e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.29352450370788574s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.02077317237854004s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0008025169372558594s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0006046295166015625s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 1.0013580322265625e-05s
INFO | --- Analysis for bioportal-omrse took 102.94579982757568s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 8.559226989746094e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0007066726684570312s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.39110660552978516s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.02124333381652832s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0009915828704833984s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0009181499481201172s
Believability | Calculation of trust value for Ontology of Data Mining took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ontodm took 116.47615098953247s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.172325134277344e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 25.785516500473022s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.0206606388092041s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.00026535987854003906s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ontodt took 185.69877076148987s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 9.5367431640625e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 28.805313110351562s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.02082681655883789s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006229877471923828s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ontoorpha took 111.86904692649841s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 8.630752563476562e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 29.608522653579712s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.02195453643798828s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009624958038330078s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-opl took 87.32027316093445s
Availability | SPARQL endpoint availability check for Phenotypic quality took 8.58306884765625e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.36400461196899414s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020597457885742188s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008668899536132812s
Believability | Calculation of trust value for Phenotypic quality took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-pato took 97.1752655506134s
Availability | SPARQL endpoint availability check for Physician Data Query took 0.0001430511474609375s
Availability | VoID file availability check for Physician Data Query took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.294888973236084s
Reputation | Calculation of the PageRank for Physician Data Query took 0.021188735961914062s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0008544921875s
Believability | Calculation of trust value for Physician Data Query took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-pdq took 147.71961164474487s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 0.0001327991485595703s
Availability | VoID file availability check for Pediatric Terminology took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 22.357776165008545s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.020717144012451172s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0010330677032470703s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0009369850158691406s
Believability | Calculation of trust value for Pediatric Terminology took 9.775161743164062e-06s
INFO | --- Analysis for bioportal-pedterm took 143.8622326850891s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 26.65871000289917s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.021350622177124023s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0008442401885986328s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00022459030151367188s
Believability | Calculation of trust value for Parasite Experiment Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-peo took 153.37802529335022s
Availability | SPARQL endpoint availability check for PHARE took 9.918212890625e-05s
Availability | VoID file availability check for PHARE took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for PHARE took 26.334147930145264s
Reputation | Calculation of the PageRank for PHARE took 0.02091240882873535s
Interlinking | Calculation of Degree of Connection for PHARE took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0008225440979003906s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.00069427490234375s
Believability | Calculation of trust value for PHARE took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-phare took 107.55974173545837s
Availability | SPARQL endpoint availability check for PKO_Re took 8.487701416015625e-05s
Availability | VoID file availability check for PKO_Re took 0.0006201267242431641s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.3328826427459717s
Reputation | Calculation of the PageRank for PKO_Re took 0.022148847579956055s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.0002009868621826172s
Believability | Calculation of trust value for PKO_Re took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-pko took 29.0953471660614s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.315376281738281e-05s
Availability | VoID file availability check for PMA 2010 took 0.0006093978881835938s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.32027530670166016s
Reputation | Calculation of the PageRank for PMA 2010 took 0.021691322326660156s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0009377002716064453s
Believability | Calculation of trust value for PMA 2010 took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-pma took 102.40956997871399s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 8.893013000488281e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 25.691508293151855s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.020801305770874023s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00019216537475585938s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pmr took 97.91891193389893s
Availability | SPARQL endpoint availability check for Plant Anatomy took 8.7738037109375e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.3056197166442871s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.021131038665771484s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.00040268898010253906s
Believability | Calculation of trust value for Plant Anatomy took 1.6689300537109375e-05s
INFO | --- Analysis for bioportal-po took 31.64109230041504s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 8.511543273925781e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.3028285503387451s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.020985841751098633s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 7.486343383789062e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 2.0742416381835938e-05s
INFO | --- Analysis for bioportal-po_x1 took 25.627375841140747s
Availability | SPARQL endpoint availability check for Plant Ontology took 5.412101745605469e-05s
Availability | VoID file availability check for Plant Ontology took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for Plant Ontology took 25.439298391342163s
Reputation | Calculation of the PageRank for Plant Ontology took 0.020574569702148438s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.000461578369140625s
Believability | Calculation of trust value for Plant Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-po_x2 took 57.61427664756775s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 0.00016164779663085938s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0003001689910888672s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.45806145668029785s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.02088451385498047s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006759166717529297s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 3.0517578125e-05s
INFO | --- Analysis for bioportal-pr took 58.42494249343872s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 8.58306884765625e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.00030040740966796875s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 32.27926301956177s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.021742582321166992s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.0002644062042236328s
Believability | Calculation of trust value for Proteomics data and process provenance took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-propreo took 141.40889048576355s
Availability | SPARQL endpoint availability check for Pathway ontology took 4.601478576660156e-05s
Availability | VoID file availability check for Pathway ontology took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for Pathway ontology took 32.06938934326172s
Reputation | Calculation of the PageRank for Pathway ontology took 0.02093338966369629s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.0001277923583984375s
Believability | Calculation of trust value for Pathway ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-pw took 137.89469027519226s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.31299829483032227s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.02223968505859375s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.647804260253906e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-qibo took 59.4671196937561s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.1961669921875e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0003075599670410156s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.39145588874816895s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.02082657814025879s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017731189727783203s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-rcd took 131.08573055267334s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 9.393692016601562e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0003960132598876953s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.3385441303253174s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.021519184112548828s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00018024444580078125s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-rctontology took 51.91054081916809s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 8.153915405273438e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0003020763397216797s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.33744263648986816s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.023488283157348633s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0009191036224365234s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 0.00012874603271484375s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-repo took 79.08632040023804s
Availability | SPARQL endpoint availability check for Physico-chemical process took 4.673004150390625e-05s
Availability | VoID file availability check for Physico-chemical process took 0.00033473968505859375s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.3242008686065674s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.022080659866333008s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.0002110004425048828s
Believability | Calculation of trust value for Physico-chemical process took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-rex took 102.83808135986328s
Availability | SPARQL endpoint availability check for RadLex took 0.00015115737915039062s
Availability | VoID file availability check for RadLex took 0.00033473968505859375s
Completeness | Calculation of interlinking completeness for RadLex took 0.31044864654541016s
Reputation | Calculation of the PageRank for RadLex took 0.021826744079589844s
Interlinking | Calculation of Degree of Connection for RadLex took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.001605987548828125s
Believability | Calculation of trust value for RadLex took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-rid took 57.70178151130676s
Availability | SPARQL endpoint availability check for RNA ontology took 4.220008850097656e-05s
Availability | VoID file availability check for RNA ontology took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for RNA ontology took 23.822915077209473s
Reputation | Calculation of the PageRank for RNA ontology took 0.020609378814697266s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005762577056884766s
Believability | Calculation of trust value for RNA ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-rnao took 26.704212427139282s
Availability | SPARQL endpoint availability check for Role Ontology took 7.43865966796875e-05s
Availability | VoID file availability check for Role Ontology took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.39600229263305664s
Reputation | Calculation of the PageRank for Role Ontology took 0.021180391311645508s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.0002129077911376953s
Believability | Calculation of trust value for Role Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-roleo took 97.46622705459595s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 25.021101236343384s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.02077484130859375s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.000186920166015625s
Believability | Calculation of trust value for Rat Strain Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-rs took 130.95025444030762s
Availability | SPARQL endpoint availability check for RxNORM took 8.749961853027344e-05s
Availability | VoID file availability check for RxNORM took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for RxNORM took 0.29448866844177246s
Reputation | Calculation of the PageRank for RxNORM took 0.020995378494262695s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006456375122070312s
Believability | Calculation of trust value for RxNORM took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-rxnorm took 94.06493902206421s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.124641418457031e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 24.005858898162842s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.021019697189331055s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010364055633544922s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-sao took 105.62574338912964s
Availability | SPARQL endpoint availability check for Systems Biology took 4.172325134277344e-05s
Availability | VoID file availability check for Systems Biology took 0.00033020973205566406s
Completeness | Calculation of interlinking completeness for Systems Biology took 31.265892267227173s
Reputation | Calculation of the PageRank for Systems Biology took 0.02156662940979004s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.00048279762268066406s
Believability | Calculation of trust value for Systems Biology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-sbo took 86.8385169506073s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 8.249282836914062e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 29.09496760368347s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.02096724510192871s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00011205673217773438s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sbro took 84.31213569641113s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 0.0001506805419921875s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0006108283996582031s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.3217048645019531s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.021101713180541992s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013790130615234375s
Believability | Calculation of trust value for Sleep Domain Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-sdo took 23.893930435180664s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.6253204345703125e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.30980396270751953s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.02080368995666504s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.00036072731018066406s
Believability | Calculation of trust value for Sample processing and separation techniques took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sep took 32.65959644317627s
Availability | SPARQL endpoint availability check for Student Health Record took 4.601478576660156e-05s
Availability | VoID file availability check for Student Health Record took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.4546329975128174s
Reputation | Calculation of the PageRank for Student Health Record took 0.02091383934020996s
Interlinking | Calculation of Degree of Connection for Student Health Record took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0005078315734863281s
Believability | Calculation of trust value for Student Health Record took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-shr took 111.33054566383362s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.863739013671875e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0007233619689941406s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 30.021642923355103s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.021305561065673828s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0008473396301269531s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0015125274658203125s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-sio took 82.88820457458496s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 9.584426879882812e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.000606536865234375s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 29.16257119178772s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.021075963973999023s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00021028518676757812s
Believability | Calculation of trust value for Situation-Based Access Control took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-sitbac took 60.06461501121521s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 6.175041198730469e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 24.62787652015686s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.022709369659423828s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019295215606689453s
Believability | Calculation of trust value for SNOMED Clinical Terms took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-snomedct took 162.64030385017395s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 25.276153802871704s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.021158933639526367s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0007152557373046875s
Believability | Calculation of trust value for SNP-Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-snpo took 60.58215546607971s
Availability | SPARQL endpoint availability check for Sequence types and features took 8.749961853027344e-05s
Availability | VoID file availability check for Sequence types and features took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.3266744613647461s
Reputation | Calculation of the PageRank for Sequence types and features took 0.0208740234375s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0006160736083984375s
Believability | Calculation of trust value for Sequence types and features took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-so_x1 took 26.395989656448364s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 8.511543273925781e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 32.055726766586304s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.02117466926574707s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007960796356201172s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015902519226074219s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-sopharm took 65.43803906440735s
Availability | SPARQL endpoint availability check for SoyOntology took 4.100799560546875e-05s
Availability | VoID file availability check for SoyOntology took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.34368443489074707s
Reputation | Calculation of the PageRank for SoyOntology took 0.020752668380737305s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.0001404285430908203s
Believability | Calculation of trust value for SoyOntology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-soy took 93.50788187980652s
Availability | SPARQL endpoint availability check for Spider Ontology took 9.846687316894531e-05s
Availability | VoID file availability check for Spider Ontology took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.3192896842956543s
Reputation | Calculation of the PageRank for Spider Ontology took 0.021114110946655273s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00033092498779296875s
Believability | Calculation of trust value for Spider Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-spd took 55.26718068122864s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.310014009475708s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.021396636962890625s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00028777122497558594s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-spto took 108.91385126113892s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.00028443336486816406s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 31.214974641799927s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.020990848541259766s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0008141994476318359s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004684925079345703s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-sso took 193.5173785686493s
Availability | SPARQL endpoint availability check for Software Ontology took 8.487701416015625e-05s
Availability | VoID file availability check for Software Ontology took 0.0005600452423095703s
Completeness | Calculation of interlinking completeness for Software Ontology took 31.351691484451294s
Reputation | Calculation of the PageRank for Software Ontology took 0.020795106887817383s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.0004260540008544922s
Believability | Calculation of trust value for Software Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-swo took 60.87261366844177s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 7.581710815429688e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.3393232822418213s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.021237611770629883s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.0002727508544921875s
Believability | Calculation of trust value for Tick gross anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tads took 138.08194708824158s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 0.00013446807861328125s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 28.41912078857422s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.020923852920532227s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007834434509277344s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0009694099426269531s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tao took 165.08247637748718s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.506111145019531e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.33441877365112305s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.022576332092285156s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0009946823120117188s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 0.00012063980102539062s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-taxrank took 80.04997253417969s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 8.678436279296875e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0006585121154785156s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 24.008398294448853s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.02178168296813965s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007998943328857422s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 9.775161743164062e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-teddy took 162.08072185516357s
Availability | SPARQL endpoint availability check for Time Event Ontology took 9.894371032714844e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0004353523254394531s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.2884089946746826s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.0211031436920166s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008633136749267578s
Believability | Calculation of trust value for Time Event Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-teo took 122.29717588424683s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 8.749961853027344e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.29265403747558594s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.021965503692626953s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0004267692565917969s
Believability | Calculation of trust value for Mosquito gross anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-tgma took 78.66724848747253s
Availability | SPARQL endpoint availability check for thesaurus took 4.482269287109375e-05s
Availability | VoID file availability check for thesaurus took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for thesaurus took 0.3295769691467285s
Reputation | Calculation of the PageRank for thesaurus took 0.021803617477416992s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for thesaurus took 0.00010848045349121094s
Believability | Calculation of trust value for thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-thesaurus took 74.27656960487366s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 8.940696716308594e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.3637983798980713s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.02091193199157715s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.00036072731018066406s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 101.262535572052s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.30475640296936035s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.02106642723083496s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008478164672851562s
Believability | Calculation of trust value for Translational Medicine Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-tmo took 79.92872738838196s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.2892117500305176s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.0209653377532959s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.001184225082397461s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00021982192993164062s
Believability | Calculation of trust value for Plant Trait Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-to took 28.338587760925293s
Availability | SPARQL endpoint availability check for TOK_Ontology took 9.465217590332031e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 31.4345760345459s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.021383285522460938s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.0002129077911376953s
Believability | Calculation of trust value for TOK_Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tok took 113.65648746490479s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 8.320808410644531e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 20.820101261138916s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.021219253540039062s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.0002124309539794922s
Believability | Calculation of trust value for Teleost taxonomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-tto took 134.77685356140137s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 8.678436279296875e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0003437995910644531s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 28.708759307861328s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.02095341682434082s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0011820793151855469s
Believability | Calculation of trust value for Uber anatomy ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-uberon took 109.53250741958618s
Availability | SPARQL endpoint availability check for Units Ontology took 0.0001628398895263672s
Availability | VoID file availability check for Units Ontology took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.3551175594329834s
Reputation | Calculation of the PageRank for Units Ontology took 0.021405935287475586s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0009882450103759766s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.00033092498779296875s
Believability | Calculation of trust value for Units Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-unitsontology took 76.45865750312805s
Availability | SPARQL endpoint availability check for Units of measurement took 8.821487426757812e-05s
Availability | VoID file availability check for Units of measurement took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for Units of measurement took 28.694297790527344s
Reputation | Calculation of the PageRank for Units of measurement took 0.02081894874572754s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.0009374618530273438s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0003571510314941406s
Believability | Calculation of trust value for Units of measurement took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-uo took 80.76863241195679s
Availability | SPARQL endpoint availability check for VANDF took 4.38690185546875e-05s
Availability | VoID file availability check for VANDF took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for VANDF took 31.697513818740845s
Reputation | Calculation of the PageRank for VANDF took 0.02102947235107422s
Interlinking | Calculation of Degree of Connection for VANDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0007326602935791016s
Believability | Calculation of trust value for VANDF took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-vandf took 83.56584429740906s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.2893385887145996s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.02110004425048828s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0004730224609375s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-vao took 86.71686387062073s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 0.00011348724365234375s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0002963542938232422s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.3789074420928955s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020695209503173828s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006401538848876953s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-vhog took 84.38602924346924s
Availability | SPARQL endpoint availability check for VIVO took 6.747245788574219e-05s
Availability | VoID file availability check for VIVO took 0.00035834312438964844s
Completeness | Calculation of interlinking completeness for VIVO took 30.654104471206665s
Reputation | Calculation of the PageRank for VIVO took 0.021058082580566406s
Interlinking | Calculation of Degree of Connection for VIVO took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0008909702301025391s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0004398822784423828s
Believability | Calculation of trust value for VIVO took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-vivo took 131.36995792388916s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.601478576660156e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.29134678840637207s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.021167993545532227s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012664794921875s
Believability | Calculation of trust value for Vaccine Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-vo took 157.32792830467224s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.76837158203125e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.32332921028137207s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.020947933197021484s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.0002319812774658203s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-vt took 96.62926769256592s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 6.818771362304688e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0005247592926025391s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 25.89730429649353s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.02081894874572754s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0005388259887695312s
Believability | Calculation of trust value for C. elegans gross anatomy took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-wbbt took 126.66175627708435s
Availability | SPARQL endpoint availability check for C. elegans development took 4.1484832763671875e-05s
Availability | VoID file availability check for C. elegans development took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.3252067565917969s
Reputation | Calculation of the PageRank for C. elegans development took 0.021957874298095703s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.887580871582031e-05s
Believability | Calculation of trust value for C. elegans development took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-wbls took 124.99770641326904s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 4.100799560546875e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.30249667167663574s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.02106022834777832s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007960796356201172s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 0.00011515617370605469s
Believability | Calculation of trust value for C. elegans phenotype took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-wbphenotype took 120.07711935043335s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 6.580352783203125e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.3130497932434082s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.024079084396362305s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0007226467132568359s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-who took 78.06058883666992s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 0.000102996826171875s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.3555607795715332s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020746469497680664s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0007257461547851562s
Believability | Calculation of trust value for Xenopus anatomy and development took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-xao took 54.18504214286804s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.28284239768981934s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.02068805694580078s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.0002493858337402344s
Believability | Calculation of trust value for Experimental Conditions Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-xco took 131.82884573936462s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 7.62939453125e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.3100574016571045s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.021640539169311523s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0002772808074951172s
Believability | Calculation of trust value for Yeast phenotypes took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ypo took 137.88447785377502s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 8.392333984375e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.37680602073669434s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.020864009857177734s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0008714199066162109s
Believability | Calculation of trust value for Zebrafish anatomy and development took 2.0503997802734375e-05s
INFO | --- Analysis for bioportal-zfa took 52.22907590866089s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 8.535385131835938e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 24.034362316131592s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.021320819854736328s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 3.647804260253906e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 1.2159347534179688e-05s
INFO | --- Analysis for Bioportal_link took 51.38898158073425s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.5852723121643066s
Availability | VoID file availability check for BioSamples RDF took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.306088924407959s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.020986318588256836s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0008497238159179688s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 4.172325134277344e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.1920928955078125e-05s
INFO | --- Analysis for biosamples-rdf took 78.58066868782043s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.10182857513427734s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 31.072261810302734s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.021291017532348633s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00012040138244628906s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for bis-linked-data took 105.93228101730347s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0001475811004638672s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007584095001220703s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 31.960179090499878s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.020857572555541992s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.3392181396484375e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.0251998901367188e-05s
INFO | --- Analysis for bll-thesaurus took 79.5123929977417s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.0168147087097168s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.4456453323364258s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.021088361740112305s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 7.224082946777344e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.239776611328125e-05s
INFO | --- Analysis for bluk-bnb took 147.03922772407532s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 1.2735724449157715s
Availability | VoID file availability check for Thesaurus BNCF took 0.0006766319274902344s
Extra | Recovery of all triples for Thesaurus BNCF took 73.19900012016296s
Performance | Total latancy measurement for Thesaurus BNCF took 0.8239953517913818s
Amount of data | Number of triples check for Thesaurus BNCF took 0.6219887733459473s
Interoperability | New terms check for Thesaurus BNCF took 2.079019784927368s
Versatility | Languages check for Thesaurus BNCF took 7.2135350704193115s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.7859995365142822s
Security | Check HTTPS for Thesaurus BNCF took 0.07691836357116699s
Interpretability | RDF structures check for Thesaurus BNCF took 0.16448593139648438s
Versatility | Serialization formats check for Thesaurus BNCF took 0.1375131607055664s
Availability | RDF dump link check for Thesaurus BNCF took 0.1264662742614746s
License | MR license check for Thesaurus BNCF took 0.13916659355163574s
License | HR license check for Thesaurus BNCF took 0.19605708122253418s
Amount of data | Number of property check for Thesaurus BNCF took 0.1395883560180664s
Understandability | Number of label check for Thesaurus BNCF took 0.28315114974975586s
Understandability | URI regex check for Thesaurus BNCF took 0.2637789249420166s
Understandability | Vocabs check for Thesaurus BNCF took 0.13232111930847168s
Verifiability | Authors check for Thesaurus BNCF took 0.12013721466064453s
Verifiability | Publishers check for Thesaurus BNCF took 0.16608166694641113s
Performance | Throughput check for Thesaurus BNCF took 10.679315567016602s
Amount of data | Check the number of entities for Thesaurus BNCF took 3.0517578125e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.13415884971618652s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.12805843353271484s
Interlinking | skos check for Thesaurus BNCF took 0.18915677070617676s
Interlinking | skos check for Thesaurus BNCF took 0.14275312423706055s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.13221096992492676s
Currency | Creation date check for Thesaurus BNCF took 0.2776036262512207s
Currency | Modification date check for Thesaurus BNCF took 0.29476141929626465s
Rep.Conc. | URIs length for Thesaurus BNCF took 25.957987070083618s
Interoperability | New vocabularies check for Thesaurus BNCF took 1.0251998901367188e-05s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.12609481811523438s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.13411664962768555s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.18487548828125s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 13.193902015686035s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.503899335861206s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.944424629211426s
Consistency | Disjoint class check for Thesaurus BNCF took 0.14563202857971191s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.8186144828796387s
Consistency | Misplaced classes for Thesaurus BNCF took 6.9015538692474365s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 9.654783248901367s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.6010277271270752s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.35891056060791s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.4427828788757324s
Security | Sign check for Thesaurus BNCF took 0.13321590423583984s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 20.693278551101685s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 30.897717714309692s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.02134418487548828s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 7.62939453125e-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 1.2159347534179688e-05s
INFO | --- Analysis for bncf-ns took 357.9386761188507s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7641608715057373s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007443428039550781s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.101604700088501s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.5309700965881348s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.25608134269714355s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.51201057434082s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.47597813606262s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2631833553314209s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3275744915008545s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4380669593811035s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5866117477416992s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.663445234298706s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5724916458129883s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.45567774772644s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.46233224868774414s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3246912956237793s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0216708183288574s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.460845947265625s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4600551128387451s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5064005851745605s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.215266704559326s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.081031799316406e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4062509536743164s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2950742244720459s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2642984390258789s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3443892002105713s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5810847282409668s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1192424297332764s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5147905349731445s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 17.58880925178528s
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.3959174156188965s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.188941240310669s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02394270896911621s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02910614013671875s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3159615993499756s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.004220247268677s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.47751665115356445s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.7222671508789062s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.7905066013336182s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 14.412234544754028s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.03235316276550293s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6110532283782959s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5393025875091553s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.292356967926025s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5088517665863037s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.022174596786499023s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0008158683776855469s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.745887756347656e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6689300537109375e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.2636184692382812e-05s
INFO | --- Analysis for bpr took 472.8551621437073s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 9.298324584960938e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.3062896728515625s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.030315399169921875s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0010998249053955078s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 9.107589721679688e-05s
Believability | Calculation of trust value for Brazilian Politicians took 9.059906005859375e-06s
INFO | --- Analysis for brazilian-politicians took 31.971060037612915s
Availability | SPARQL endpoint availability check for Bricklink took 1.435605764389038s
Availability | VoID file availability check for Bricklink took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for Bricklink took 0.3010725975036621s
Reputation | Calculation of the PageRank for Bricklink took 0.02076578140258789s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.937980651855469e-05s
Believability | Calculation of trust value for Bricklink took 1.1920928955078125e-05s
INFO | --- Analysis for bricklink took 92.35819816589355s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.145299911499023s
Availability | VoID file availability check for British Museum Collection took 0.0006945133209228516s
Completeness | Calculation of interlinking completeness for British Museum Collection took 29.462064743041992s
Reputation | Calculation of the PageRank for British Museum Collection took 0.021042346954345703s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.62396240234375e-05s
Believability | Calculation of trust value for British Museum Collection took 1.1682510375976562e-05s
INFO | --- Analysis for british-museum-collection took 237.55957627296448s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 8.7738037109375e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0011138916015625s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.3164026737213135s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.021704673767089844s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0011012554168701172s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 5.364418029785156e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.0967254638671875e-05s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 56.95712733268738s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2518177032470703s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0005483627319335938s
Extra | Recovery of all triples for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 11.775886297225952s
Performance | Total latancy measurement for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.5912938117980957s
Amount of data | Number of triples check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.9979426860809326s
Interoperability | New terms check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.0182769298553467s
Versatility | Languages check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 6.343792200088501s
Interpretability | Number of blank nodes check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.835047721862793s
Interpretability | RDF structures check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12255382537841797s
Versatility | Serialization formats check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12292075157165527s
Availability | RDF dump link check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1279773712158203s
License | MR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12871813774108887s
License | HR license check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 16.2536678314209s
Amount of data | Number of property check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11600542068481445s
Understandability | Number of label check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.16625523567199707s
Understandability | URI regex check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.24144458770751953s
Understandability | Vocabs check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.11420679092407227s
Verifiability | Authors check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.13007497787475586s
Verifiability | Publishers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.13301610946655273s
Performance | Throughput check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.782420873641968s
Amount of data | Check the number of entities for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 7.271766662597656e-05s
Verifiability | Contribs. check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12253355979919434s
Interlinking | sameAs chians check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12200927734375s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.1139841079711914s
Interlinking | skos check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12217831611633301s
Timeliness | dataset update frequency check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12907075881958008s
Currency | Creation date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.23848628997802734s
Currency | Modification date check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.23721027374267578s
Rep.Conc. | URIs length for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 10.80269718170166s
Interoperability | New vocabularies check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.2159347534179688e-05s
Consistency | Deprecated classes/propertiers check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12265968322753906s
Accuracy | Check Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12653136253356934s
Accuracy | Check Inverse Functional Property for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.12048053741455078s
Accuracy | Check Empty annotation labels for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.2649831771850586s
Accuracy | Check White space in annotation for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2484910488128662s
Accuracy | Check Datatype consistency for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 4.622544765472412s
Consistency | Disjoint class check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.13140368461608887s
Consistency | Check Misplaced properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.2171807289123535s
Consistency | Check Ontology hijacking for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 5.537806749343872s
Consistency | Check Invalid usage of undefined classes for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.4383392333984375s
Consistency | Check Invalid usage of undefined properties for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.6027610301971436s
Conciseness | Check Extensional conciseness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.806398630142212s
Security | Sign check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.129014253616333s
Availability | Check URIs Dereferenciability for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3569.5268716812134s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 23.80155348777771s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.023382186889648438s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 6.222724914550781e-05s
Interoperability | Check the re-using of existing vocabs for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.9073486328125e-06s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.3589859008789062e-05s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 3749.522795200348s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.20665931701660156s
Availability | VoID file availability check for business.data.gov.uk took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 24.778427839279175s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.020757198333740234s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.555152893066406e-05s
Believability | Calculation of trust value for business.data.gov.uk took 8.821487426757812e-06s
INFO | --- Analysis for business-data-gov-uk took 136.82411074638367s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.519935131072998s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0006973743438720703s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 1.8711934089660645s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.511146068572998s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.37472057342529297s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.8441970348358154s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 41.94073247909546s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.3502829074859619s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.1887683868408203s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.5300107002258301s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.30723118782043457s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.3126237392425537s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.36635518074035645s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 12.207809448242188s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.3109118938446045s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.8506195545196533s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.5872819423675537s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.3128645420074463s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.43922877311706543s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.3824307918548584s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.931132316589355s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 7.104873657226562e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.3105292320251465s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.3317599296569824s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.3901071548461914s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.2893404960632324s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.32982826232910156s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.7392222881317139s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.6105632781982422s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 4.495835304260254s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.28571414947509766s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.37299108505249023s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.3703594207763672s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 1.5859217643737793s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.03166079521179199s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.02975177764892578s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.3896808624267578s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.4107532501220703s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.3712756633758545s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.90533709526062s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.4302482604980469s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.5370240211486816s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.03333640098571777s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.3170592784881592s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.30669450759887695s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1550.2076168060303s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 28.225976943969727s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.02151346206665039s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.1975250244140625e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.1920928955078125e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 1.1444091796875e-05s
INFO | --- Analysis for BVMC took 1800.2707798480988s
Availability | SPARQL endpoint availability check for cablegate took 3.9932332038879395s
Availability | VoID file availability check for cablegate took 0.0007655620574951172s
Completeness | Calculation of interlinking completeness for cablegate took 0.29907655715942383s
Reputation | Calculation of the PageRank for cablegate took 0.022953033447265625s
Interlinking | Calculation of Degree of Connection for cablegate took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for cablegate took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for cablegate took 7.271766662597656e-05s
Believability | Calculation of trust value for cablegate took 1.239776611328125e-05s
INFO | --- Analysis for cablegate took 125.14002299308777s
Availability | SPARQL endpoint availability check for Calames took 9.560585021972656e-05s
Availability | VoID file availability check for Calames took 0.0007109642028808594s
Completeness | Calculation of interlinking completeness for Calames took 25.038204431533813s
Reputation | Calculation of the PageRank for Calames took 0.02175736427307129s
Interlinking | Calculation of Degree of Connection for Calames took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Calames took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Calames took 3.981590270996094e-05s
Believability | Calculation of trust value for Calames took 1.2636184692382812e-05s
INFO | --- Analysis for calames took 108.62171292304993s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.4156174659729004s
Availability | VoID file availability check for CaLiGraph took 0.0005102157592773438s
Extra | Recovery of all triples for CaLiGraph took 1.1508338451385498s
Performance | Total latancy measurement for CaLiGraph took 1.2190263271331787s
Amount of data | Number of triples check for CaLiGraph took 13.521527528762817s
Interoperability | New terms check for CaLiGraph took 2.3913259506225586s
Versatility | Languages check for CaLiGraph took 60.31513214111328s
Interpretability | Number of blank nodes check for CaLiGraph took 0.2780160903930664s
Security | Check HTTPS for CaLiGraph took 0.14064550399780273s
Interpretability | RDF structures check for CaLiGraph took 0.2734706401824951s
Versatility | Serialization formats check for CaLiGraph took 0.2755107879638672s
Availability | RDF dump link check for CaLiGraph took 0.26333045959472656s
License | MR license check for CaLiGraph took 0.25747108459472656s
License | HR license check for CaLiGraph took 60.320051431655884s
Amount of data | Number of property check for CaLiGraph took 0.2781829833984375s
Understandability | Number of label check for CaLiGraph took 3.3644816875457764s
Understandability | URI regex check for CaLiGraph took 0.5077121257781982s
Understandability | Vocabs check for CaLiGraph took 0.24091100692749023s
Verifiability | Authors check for CaLiGraph took 0.2614121437072754s
Verifiability | Publishers check for CaLiGraph took 0.25862836837768555s
Performance | Throughput check for CaLiGraph took 11.299945592880249s
Amount of data | Check the number of entities for CaLiGraph took 0.015143156051635742s
Verifiability | Contribs. check for CaLiGraph took 0.2524387836456299s
Interlinking | sameAs chians check for CaLiGraph took 0.6579177379608154s
Interlinking | skos check for CaLiGraph took 0.27472615242004395s
Interlinking | skos check for CaLiGraph took 0.22269821166992188s
Timeliness | dataset update frequency check for CaLiGraph took 0.2655375003814697s
Currency | Creation date check for CaLiGraph took 0.5298864841461182s
Currency | Modification date check for CaLiGraph took 0.530695915222168s
Rep.Conc. | URIs length for CaLiGraph took 62.34271025657654s
Interoperability | New vocabularies check for CaLiGraph took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.2603425979614258s
Accuracy | Check Functional Property for CaLiGraph took 0.27178335189819336s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.24743962287902832s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5928792953491211s
Accuracy | Check White space in annotation for CaLiGraph took 0.02715921401977539s
Accuracy | Check Datatype consistency for CaLiGraph took 0.05279850959777832s
Consistency | Disjoint class check for CaLiGraph took 0.2805302143096924s
Consistency | Check Misplaced properties for CaLiGraph took 60.917327880859375s
Consistency | Misplaced classes for CaLiGraph took 0.5177268981933594s
Consistency | Check Ontology hijacking for CaLiGraph took 2.1215877532958984s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.4435977935791016s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.749300479888916s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.0397188663482666s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.473330020904541s
Security | Sign check for CaLiGraph took 0.2627847194671631s
Availability | Check URIs Dereferenciability for CaLiGraph took 10.302267074584961s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.3741629123687744s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02126026153564453s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 3.790855407714844e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 9.5367431640625e-07s
Believability | Calculation of trust value for CaLiGraph took 8.344650268554688e-06s
INFO | --- Analysis for CaLiGraph took 1533.4615035057068s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.23877882957458496s
Availability | VoID file availability check for CaLiGraph took 0.0007534027099609375s
Extra | Recovery of all triples for CaLiGraph took 1.2015795707702637s
Performance | Total latancy measurement for CaLiGraph took 1.139413833618164s
Amount of data | Number of triples check for CaLiGraph took 13.507404804229736s
Interoperability | New terms check for CaLiGraph took 2.176290988922119s
Versatility | Languages check for CaLiGraph took 60.275296688079834s
Interpretability | Number of blank nodes check for CaLiGraph took 0.25364017486572266s
Security | Check HTTPS for CaLiGraph took 0.13819575309753418s
Interpretability | RDF structures check for CaLiGraph took 0.25821971893310547s
Versatility | Serialization formats check for CaLiGraph took 0.26851987838745117s
Availability | RDF dump link check for CaLiGraph took 0.27207493782043457s
License | MR license check for CaLiGraph took 0.2532343864440918s
License | HR license check for CaLiGraph took 60.32884907722473s
Amount of data | Number of property check for CaLiGraph took 0.24123620986938477s
Understandability | Number of label check for CaLiGraph took 3.2666752338409424s
Understandability | URI regex check for CaLiGraph took 0.5121114253997803s
Understandability | Vocabs check for CaLiGraph took 0.25080060958862305s
Verifiability | Authors check for CaLiGraph took 0.2596006393432617s
Verifiability | Publishers check for CaLiGraph took 0.2708265781402588s
Performance | Throughput check for CaLiGraph took 11.457717895507812s
Amount of data | Check the number of entities for CaLiGraph took 0.011708974838256836s
Verifiability | Contribs. check for CaLiGraph took 7.335500478744507s
Interlinking | sameAs chians check for CaLiGraph took 11.696823596954346s
Interlinking | skos check for CaLiGraph took 10.36741304397583s
Interlinking | skos check for CaLiGraph took 10.914806604385376s
Timeliness | dataset update frequency check for CaLiGraph took 10.563807010650635s
Currency | Creation date check for CaLiGraph took 22.227137327194214s
Currency | Modification date check for CaLiGraph took 2.649815559387207s
Rep.Conc. | URIs length for CaLiGraph took 60.98710656166077s
Interoperability | New vocabularies check for CaLiGraph took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.2797067165374756s
Accuracy | Check Functional Property for CaLiGraph took 0.24588441848754883s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2579004764556885s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5875084400177002s
Accuracy | Check White space in annotation for CaLiGraph took 0.0262451171875s
Accuracy | Check Datatype consistency for CaLiGraph took 0.04990530014038086s
Consistency | Disjoint class check for CaLiGraph took 0.24320054054260254s
Consistency | Check Misplaced properties for CaLiGraph took 60.95410943031311s
Consistency | Misplaced classes for CaLiGraph took 0.5336997509002686s
Consistency | Check Ontology hijacking for CaLiGraph took 2.0910933017730713s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.415921926498413s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.832003593444824s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.030649662017822266s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.49224305152893066s
Security | Sign check for CaLiGraph took 0.26813626289367676s
Availability | Check URIs Dereferenciability for CaLiGraph took 10.994068384170532s
Completeness | Calculation of interlinking completeness for CaLiGraph took 29.87298560142517s
Reputation | Calculation of the PageRank for CaLiGraph took 0.021610021591186523s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 7.987022399902344e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.1920928955078125e-06s
Believability | Calculation of trust value for CaLiGraph took 1.33514404296875e-05s
INFO | --- Analysis for caligraph took 1665.3931214809418s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.07182002067565918s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 28.1523175239563s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.021274328231811523s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.24249267578125e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 1.1920928955078125e-05s
INFO | --- Analysis for cap-italy-rdf took 142.39189171791077s
Availability | SPARQL endpoint availability check for person took 8.821487426757812e-05s
Availability | VoID file availability check for person took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for person took 28.1497859954834s
Reputation | Calculation of the PageRank for person took 0.020831584930419922s
Interlinking | Calculation of Degree of Connection for person took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for person took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for person took 3.504753112792969e-05s
Believability | Calculation of trust value for person took 1.0967254638671875e-05s
INFO | --- Analysis for card took 121.70008993148804s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 8.678436279296875e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 27.966663360595703s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.02216506004333496s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 5.340576171875e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 1.430511474609375e-05s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 166.437828540802s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.5037240982055664s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.0005669593811035156s
Extra | Recovery of all triples for Norway catch records dataset @PSNC took 109.29469132423401s
Performance | Total latancy measurement for Norway catch records dataset @PSNC took 0.990623950958252s
Amount of data | Number of triples check for Norway catch records dataset @PSNC took 9.246397495269775s
Interoperability | New terms check for Norway catch records dataset @PSNC took 14.656099319458008s
Versatility | Languages check for Norway catch records dataset @PSNC took 300.2391893863678s
Interpretability | Number of blank nodes check for Norway catch records dataset @PSNC took 2.267177104949951s
Interpretability | RDF structures check for Norway catch records dataset @PSNC took 0.35321807861328125s
Versatility | Serialization formats check for Norway catch records dataset @PSNC took 8.548630952835083s
Availability | RDF dump link check for Norway catch records dataset @PSNC took 0.3565788269042969s
License | MR license check for Norway catch records dataset @PSNC took 0.8608863353729248s
License | HR license check for Norway catch records dataset @PSNC took 300.20370602607727s
Amount of data | Number of property check for Norway catch records dataset @PSNC took 0.22231626510620117s
Understandability | Number of label check for Norway catch records dataset @PSNC took 3.0999462604522705s
Understandability | URI regex check for Norway catch records dataset @PSNC took 1.2514801025390625s
Understandability | Vocabs check for Norway catch records dataset @PSNC took 0.6371123790740967s
Verifiability | Authors check for Norway catch records dataset @PSNC took 0.19108319282531738s
Verifiability | Publishers check for Norway catch records dataset @PSNC took 0.2570004463195801s
Performance | Throughput check for Norway catch records dataset @PSNC took 11.571025848388672s
Amount of data | Check the number of entities for Norway catch records dataset @PSNC took 3.0517578125e-05s
Verifiability | Contribs. check for Norway catch records dataset @PSNC took 0.1988081932067871s
Interlinking | sameAs chians check for Norway catch records dataset @PSNC took 0.20357465744018555s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.5199613571166992s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.4131596088409424s
Timeliness | dataset update frequency check for Norway catch records dataset @PSNC took 4.115184783935547s
Currency | Creation date check for Norway catch records dataset @PSNC took 0.5017683506011963s
Currency | Modification date check for Norway catch records dataset @PSNC took 0.25130486488342285s
Rep.Conc. | URIs length for Norway catch records dataset @PSNC took 150.36101508140564s
Interoperability | New vocabularies check for Norway catch records dataset @PSNC took 1.1444091796875e-05s
Consistency | Deprecated classes/propertiers check for Norway catch records dataset @PSNC took 0.19819331169128418s
Accuracy | Check Functional Property for Norway catch records dataset @PSNC took 0.5172140598297119s
Accuracy | Check Inverse Functional Property for Norway catch records dataset @PSNC took 0.49782729148864746s
Accuracy | Check Empty annotation labels for Norway catch records dataset @PSNC took 34.77903628349304s
Accuracy | Check White space in annotation for Norway catch records dataset @PSNC took 2.6971518993377686s
Accuracy | Check Datatype consistency for Norway catch records dataset @PSNC took 2.6649017333984375s
Consistency | Disjoint class check for Norway catch records dataset @PSNC took 0.20628690719604492s
Consistency | Check Misplaced properties for Norway catch records dataset @PSNC took 86.9539635181427s
Consistency | Misplaced classes for Norway catch records dataset @PSNC took 8.345309972763062s
Consistency | Check Ontology hijacking for Norway catch records dataset @PSNC took 26.060662508010864s
Consistency | Check Invalid usage of undefined classes for Norway catch records dataset @PSNC took 1.4893758296966553s
Consistency | Check Invalid usage of undefined properties for Norway catch records dataset @PSNC took 88.91337513923645s
Conciseness | Check Extensional conciseness for Norway catch records dataset @PSNC took 2.790695905685425s
Conciseness | Check Intensional conciseness for Norway catch records dataset @PSNC took 0.5329017639160156s
Security | Sign check for Norway catch records dataset @PSNC took 1.6256227493286133s
Availability | Check URIs Dereferenciability for Norway catch records dataset @PSNC took 10.360908031463623s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.9703760147094727s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.022168636322021484s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 4.982948303222656e-05s
Interoperability | Check the re-using of existing vocabs for Norway catch records dataset @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 1.2159347534179688e-05s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2357.7613201141357s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.57763671875e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0003914833068847656s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.3488118648529053s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.02204298973083496s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0009286403656005859s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00013017654418945312s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.1205673217773438e-05s
INFO | --- Analysis for ce4r took 143.0321295261383s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4755585193634033s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0005407333374023438s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.7894461154937744s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 1.0747711658477783s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3116602897644043s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.8273417949676514s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.149407625198364s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3103013038635254s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.455655574798584s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18374013900756836s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1733989715576172s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3066983222961426s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.31069445610046387s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.19695496559143066s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4453303813934326s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3091156482696533s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17377448081970215s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.23113679885864258s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.25788068771362305s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 11.136993408203125s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.152557373046875e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.34058332443237305s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18208885192871094s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5620558261871338s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15688276290893555s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2930924892425537s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.64180588722229s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5060443878173828s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.0255017280578613s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.26862502098083496s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.2677013874053955s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.31483006477355957s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 2.375156879425049s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.02883458137512207s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.02926492691040039s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3316617012023926s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.2821125984191895s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 2.2178046703338623s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.4383111000061035s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.7521462440490723s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03132891654968262s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.22638463973999023s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15728020668029785s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 5895.027394771576s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 27.158655881881714s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.022394657135009766s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.76837158203125e-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 1.2159347534179688e-05s
INFO | --- Analysis for ceo took 6144.242963552475s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.649162292480469e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0006589889526367188s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 27.44244384765625s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.02123570442199707s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 4.220008850097656e-05s
Believability | Calculation of trust value for Chat Game corpus took 8.821487426757812e-06s
INFO | --- Analysis for chat-game-corpus took 99.1743700504303s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 9.1552734375e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.000766754150390625s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 27.657078504562378s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.021220922470092773s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 7.104873657226562e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 1.1920928955078125e-05s
INFO | --- Analysis for chem2bio2rdf took 280.13802337646484s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.5705640316009521s
Availability | VoID file availability check for ChEMBL RDF took 0.08855366706848145s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 26.782996654510498s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.022773027420043945s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.4836273193359375e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.2159347534179688e-05s
INFO | --- Analysis for chembl-rdf took 142.85859990119934s
Availability | SPARQL endpoint availability check for chemdb  dataset took 1.3084125518798828s
Availability | VoID file availability check for chemdb  dataset took 0.0005409717559814453s
Extra | Recovery of all triples for chemdb  dataset took 4.90277361869812s
Performance | Total latancy measurement for chemdb  dataset took 2.5371768474578857s
Amount of data | Number of triples check for chemdb  dataset took 0.5669121742248535s
Interoperability | New terms check for chemdb  dataset took 3.6121699810028076s
Versatility | Languages check for chemdb  dataset took 22.465147495269775s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5287652015686035s
Interpretability | RDF structures check for chemdb  dataset took 0.5881671905517578s
Versatility | Serialization formats check for chemdb  dataset took 0.5502369403839111s
Availability | RDF dump link check for chemdb  dataset took 0.5059943199157715s
License | MR license check for chemdb  dataset took 0.5345897674560547s
License | HR license check for chemdb  dataset took 3.0568125247955322s
Amount of data | Number of property check for chemdb  dataset took 0.5394871234893799s
Understandability | Number of label check for chemdb  dataset took 0.7359540462493896s
Understandability | URI regex check for chemdb  dataset took 1.038393259048462s
Understandability | Vocabs check for chemdb  dataset took 0.4982774257659912s
Verifiability | Authors check for chemdb  dataset took 0.49674034118652344s
Verifiability | Publishers check for chemdb  dataset took 0.4938056468963623s
Performance | Throughput check for chemdb  dataset took 14.021243810653687s
Amount of data | Check the number of entities for chemdb  dataset took 6.985664367675781e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.4940476417541504s
Interlinking | sameAs chians check for chemdb  dataset took 0.5537068843841553s
Interlinking | skos check for chemdb  dataset took 0.5480892658233643s
Interlinking | skos check for chemdb  dataset took 0.512352705001831s
Timeliness | dataset update frequency check for chemdb  dataset took 0.5308310985565186s
Currency | Creation date check for chemdb  dataset took 1.0287833213806152s
Currency | Modification date check for chemdb  dataset took 1.0322980880737305s
Rep.Conc. | URIs length for chemdb  dataset took 2.915776491165161s
Interoperability | New vocabularies check for chemdb  dataset took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5384585857391357s
Accuracy | Check Functional Property for chemdb  dataset took 0.536029577255249s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.49678683280944824s
Accuracy | Check Empty annotation labels for chemdb  dataset took 2.2026546001434326s
Accuracy | Check White space in annotation for chemdb  dataset took 0.030721187591552734s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.03403830528259277s
Consistency | Disjoint class check for chemdb  dataset took 0.5120298862457275s
Consistency | Check Misplaced properties for chemdb  dataset took 1.2148644924163818s
Consistency | Misplaced classes for chemdb  dataset took 1.309023141860962s
Consistency | Check Ontology hijacking for chemdb  dataset took 3.5877630710601807s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.4345157146453857s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 2.1453511714935303s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.03509020805358887s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.5304214954376221s
Security | Sign check for chemdb  dataset took 0.5811793804168701s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2555.6182646751404s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 28.390770435333252s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.02692890167236328s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 0.00012230873107910156s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb  dataset took 1.2159347534179688e-05s
INFO | --- Analysis for chemdb-basicInfo took 5780.552188396454s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.5258584022521973s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.0005767345428466797s
Extra | Recovery of all triples for chemdb estimated properties dataset took 4.990123510360718s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.4742865562438965s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.5642709732055664s
Interoperability | New terms check for chemdb estimated properties dataset took 3.639861822128296s
Versatility | Languages check for chemdb estimated properties dataset took 22.39040231704712s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.53421950340271s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.5357954502105713s
Versatility | Serialization formats check for chemdb estimated properties dataset took 0.547619104385376s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.5082907676696777s
License | MR license check for chemdb estimated properties dataset took 0.5130829811096191s
License | HR license check for chemdb estimated properties dataset took 3.0946807861328125s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5497944355010986s
Understandability | Number of label check for chemdb estimated properties dataset took 0.5371761322021484s
Understandability | URI regex check for chemdb estimated properties dataset took 0.9817991256713867s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.5537288188934326s
Verifiability | Authors check for chemdb estimated properties dataset took 0.498199462890625s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.5020668506622314s
Performance | Throughput check for chemdb estimated properties dataset took 12.023621320724487s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 3.24249267578125e-05s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.5113372802734375s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 0.5859003067016602s
Interlinking | skos check for chemdb estimated properties dataset took 0.5023810863494873s
Interlinking | skos check for chemdb estimated properties dataset took 0.5079126358032227s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 0.4982728958129883s
Currency | Creation date check for chemdb estimated properties dataset took 1.0300865173339844s
Currency | Modification date check for chemdb estimated properties dataset took 1.0463459491729736s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 2.9293816089630127s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.49951171875s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.5394024848937988s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.5063340663909912s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 2.1997952461242676s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.0314638614654541s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.03542375564575195s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.4924125671386719s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.2366271018981934s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.6399908065795898s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 3.5709338188171387s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.432511329650879s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 2.148463487625122s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.03312063217163086s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.5314540863037109s
Security | Sign check for chemdb estimated properties dataset took 0.49816203117370605s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 2519.781750202179s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 27.656254768371582s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.021730422973632812s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 0.00010323524475097656s
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 1.2159347534179688e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 5694.029006958008s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5183048248291016s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0005195140838623047s
Extra | Recovery of all triples for chemdb phase transition dataset took 13.414368152618408s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.507833957672119s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.5591826438903809s
Interoperability | New terms check for chemdb phase transition dataset took 4.028701543807983s
Versatility | Languages check for chemdb phase transition dataset took 22.304619550704956s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.5279221534729004s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.5423660278320312s
Versatility | Serialization formats check for chemdb phase transition dataset took 0.533207893371582s
Availability | RDF dump link check for chemdb phase transition dataset took 0.49080824851989746s
License | MR license check for chemdb phase transition dataset took 0.5051257610321045s
License | HR license check for chemdb phase transition dataset took 3.0503990650177s
Amount of data | Number of property check for chemdb phase transition dataset took 0.53857421875s
Understandability | Number of label check for chemdb phase transition dataset took 0.5432474613189697s
Understandability | URI regex check for chemdb phase transition dataset took 0.9912154674530029s
Understandability | Vocabs check for chemdb phase transition dataset took 0.4968886375427246s
Verifiability | Authors check for chemdb phase transition dataset took 0.5039150714874268s
Verifiability | Publishers check for chemdb phase transition dataset took 0.49562788009643555s
Performance | Throughput check for chemdb phase transition dataset took 12.669810771942139s
Amount of data | Check the number of entities for chemdb phase transition dataset took 3.218650817871094e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.5079677104949951s
Interlinking | sameAs chians check for chemdb phase transition dataset took 0.5297207832336426s
Interlinking | skos check for chemdb phase transition dataset took 0.4974029064178467s
Interlinking | skos check for chemdb phase transition dataset took 0.5037915706634521s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 0.5003650188446045s
Currency | Creation date check for chemdb phase transition dataset took 1.0206263065338135s
Currency | Modification date check for chemdb phase transition dataset took 1.0256435871124268s
Rep.Conc. | URIs length for chemdb phase transition dataset took 3.423844575881958s
Interoperability | New vocabularies check for chemdb phase transition dataset took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.49090123176574707s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.5136268138885498s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.5076658725738525s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 2.829662561416626s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.031161785125732422s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.036119699478149414s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.49553990364074707s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.2174928188323975s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.6207284927368164s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 4.277721405029297s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.430924892425537s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 2.1558003425598145s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.03336977958679199s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.5320320129394531s
Security | Sign check for chemdb phase transition dataset took 0.49504566192626953s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2508.189394712448s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 30.90344548225403s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.02153921127319336s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 9.799003601074219e-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 1.2636184692382812e-05s
INFO | --- Analysis for chemdb-phaseTransition took 5726.6056871414185s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.5447878837585449s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.0005776882171630859s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 9.611421346664429s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.523094892501831s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.5674762725830078s
Interoperability | New terms check for chemdb thermochemistry dataset took 4.1249260902404785s
Versatility | Languages check for chemdb thermochemistry dataset took 23.2022807598114s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.5308821201324463s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.5381186008453369s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 0.5484988689422607s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.4882509708404541s
License | MR license check for chemdb thermochemistry dataset took 0.4996457099914551s
License | HR license check for chemdb thermochemistry dataset took 3.1565988063812256s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.5390186309814453s
Understandability | Number of label check for chemdb thermochemistry dataset took 0.5555729866027832s
Understandability | URI regex check for chemdb thermochemistry dataset took 1.0080111026763916s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.48464441299438477s
Verifiability | Authors check for chemdb thermochemistry dataset took 0.500525712966919s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.5036249160766602s
Performance | Throughput check for chemdb thermochemistry dataset took 12.99634599685669s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 7.724761962890625e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.4921393394470215s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 0.5240738391876221s
Interlinking | skos check for chemdb thermochemistry dataset took 0.4918994903564453s
Interlinking | skos check for chemdb thermochemistry dataset took 0.4913485050201416s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 0.49646925926208496s
Currency | Creation date check for chemdb thermochemistry dataset took 1.0311987400054932s
Currency | Modification date check for chemdb thermochemistry dataset took 1.047539472579956s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 3.388305187225342s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.49558520317077637s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.5394420623779297s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.49166154861450195s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 2.8446264266967773s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.030563831329345703s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.03481125831604004s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.49337124824523926s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.2398669719696045s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.6282327175140381s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 4.273039102554321s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.425839900970459s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 2.1231276988983154s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.03394150733947754s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.5297882556915283s
Security | Sign check for chemdb thermochemistry dataset took 0.4913942813873291s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2516.921551465988s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 0.6213893890380859s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.021457672119140625s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 0.00011849403381347656s
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 1.1682510375976562e-05s
INFO | --- Analysis for chemdb-thermochemistry took 5669.772239685059s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 8.845329284667969e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 25.016469478607178s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.02449202537536621s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.2901763916015625e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.2159347534179688e-05s
INFO | --- Analysis for chempedia-rdf took 107.47905778884888s
Availability | SPARQL endpoint availability check for Chiman Maru took 8.7738037109375e-05s
Availability | VoID file availability check for Chiman Maru took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for Chiman Maru took 25.966248035430908s
Reputation | Calculation of the PageRank for Chiman Maru took 0.020949125289916992s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.552436828613281e-05s
Believability | Calculation of trust value for Chiman Maru took 1.1444091796875e-05s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 176.1403956413269s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 391.33340311050415s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0007681846618652344s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 29.314427375793457s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.021901369094848633s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 4.076957702636719e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 1.239776611328125e-05s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 908.7330446243286s
Availability | SPARQL endpoint availability check for Chronicling America took 9.012222290039062e-05s
Availability | VoID file availability check for Chronicling America took 0.0009317398071289062s
Completeness | Calculation of interlinking completeness for Chronicling America took 23.503008365631104s
Reputation | Calculation of the PageRank for Chronicling America took 0.02184271812438965s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00012946128845214844s
Believability | Calculation of trust value for Chronicling America took 9.059906005859375e-06s
INFO | --- Analysis for chronicling-america took 385.4726779460907s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.6320874691009521s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0006794929504394531s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 82.27742505073547s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.5396642684936523s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 1.1590473651885986s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.2414324283599854s
Versatility | Languages check for Cultural Heritage Thesaurus took 6.010241508483887s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 1.369260549545288s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.3042910099029541s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.30583882331848145s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 6.048576354980469s
License | MR license check for Cultural Heritage Thesaurus took 0.30702662467956543s
License | HR license check for Cultural Heritage Thesaurus took 0.5067830085754395s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.3382737636566162s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.3368563652038574s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.7158782482147217s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.32225656509399414s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.30811500549316406s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.33495140075683594s
Performance | Throughput check for Cultural Heritage Thesaurus took 12.303343057632446s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 7.128715515136719e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.33403611183166504s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.31739377975463867s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.3355255126953125s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.36154937744140625s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.3775181770324707s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.6903982162475586s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.6227736473083496s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 27.91226315498352s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 1.4444506168365479s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.34419727325439453s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.31302309036254883s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.31841373443603516s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 7.696085453033447s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.2250199317932129s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.29407191276550293s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.8900988101959229s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.2958223819732666s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 6.949150323867798s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.9360926151275635s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00015497207641601562s
Security | Sign check for Cultural Heritage Thesaurus took 0.299318790435791s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 388.2220232486725s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.5846998691558838s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.02116680145263672s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 9.560585021972656e-05s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 0.9053821563720703s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for cht took 687.3007941246033s
Availability | SPARQL endpoint availability check for ciard-ring took 9.131431579589844e-05s
Availability | VoID file availability check for ciard-ring took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.4024679660797119s
Reputation | Calculation of the PageRank for ciard-ring took 0.022319555282592773s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.76837158203125e-05s
Believability | Calculation of trust value for ciard-ring took 1.1682510375976562e-05s
INFO | --- Analysis for ciard-ring took 84.14839839935303s
Availability | SPARQL endpoint availability check for Cine Figure took 8.988380432128906e-05s
Availability | VoID file availability check for Cine Figure took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for Cine Figure took 23.781029224395752s
Reputation | Calculation of the PageRank for Cine Figure took 0.021271705627441406s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 5.173683166503906e-05s
Believability | Calculation of trust value for Cine Figure took 1.2636184692382812e-05s
INFO | --- Analysis for Cine_Figure took 134.93501234054565s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 1.8076505661010742s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0007162094116210938s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 26.736571788787842s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.020871639251708984s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 8.082389831542969e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 1.2636184692382812e-05s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 184.98579335212708s
Availability | SPARQL endpoint availability check for CIPFA took 0.00011038780212402344s
Availability | VoID file availability check for CIPFA took 0.00032019615173339844s
Completeness | Calculation of interlinking completeness for CIPFA took 31.85666823387146s
Reputation | Calculation of the PageRank for CIPFA took 0.02148723602294922s
Interlinking | Calculation of Degree of Connection for CIPFA took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CIPFA took 0.0008175373077392578s
Interlinking | Calculation of Clustering coefficient for CIPFA took 5.8650970458984375e-05s
Believability | Calculation of trust value for CIPFA took 8.58306884765625e-06s
INFO | --- Analysis for cipfa took 114.23156213760376s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.059590101242065s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0007777214050292969s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.3536086082458496s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.021309614181518555s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.0004096031188964844s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 1.1205673217773438e-05s
INFO | --- Analysis for ckan took 368.1227779388428s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.6283633708953857s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007269382476806641s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 25.687851667404175s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.021051883697509766s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 4.863739013671875e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.2636184692382812e-05s
INFO | --- Analysis for CLaSSES took 103.68180274963379s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 8.797645568847656e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 26.279258489608765s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.021012067794799805s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.528594970703125e-05s
Believability | Calculation of trust value for Temples of the Classical World took 1.2159347534179688e-05s
INFO | --- Analysis for classical_temples took 135.89764189720154s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 1.0895450115203857s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0006103515625s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 24.579226970672607s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.020780324935913086s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.726119995117188e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 8.821487426757812e-06s
INFO | --- Analysis for clean-energy-data-reegle took 132.0330514907837s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.2438507080078125e-05s
Availability | VoID file availability check for CLLD-afbo took 0.5560338497161865s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.42735958099365234s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.02083587646484375s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.82012939453125e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-afbo took 2.384185791015625e-06s
Believability | Calculation of trust value for CLLD-afbo took 1.1444091796875e-05s
INFO | --- Analysis for clld-afbo took 106.87740540504456s
Availability | SPARQL endpoint availability check for CLLD-APICS took 6.079673767089844e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0006957054138183594s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 26.119717121124268s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.02138996124267578s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 8.606910705566406e-05s
Believability | Calculation of trust value for CLLD-APICS took 7.3909759521484375e-06s
INFO | --- Analysis for clld-apics took 132.20216536521912s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 8.273124694824219e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.3710501194000244s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.02092599868774414s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 4.601478576660156e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 7.867813110351562e-06s
INFO | --- Analysis for clld-ewave took 113.33855295181274s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 8.368492126464844e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.5285308361053467s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 24.292386770248413s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.02120518684387207s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00010347366333007812s
Interoperability | Check the re-using of existing vocabs for CLLD-GLOTTOLOG took 1.1920928955078125e-06s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 1.1444091796875e-05s
INFO | --- Analysis for clld-glottolog took 102.29087281227112s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 8.559226989746094e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.5341262817382812s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.29795217514038086s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.022404909133911133s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 0.00010085105895996094s
Interoperability | Check the re-using of existing vocabs for CLLD-PHOIBLE took 1.1920928955078125e-06s
Believability | Calculation of trust value for CLLD-PHOIBLE took 1.2159347534179688e-05s
INFO | --- Analysis for clld-phoible took 164.35394477844238s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 8.845329284667969e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0006659030914306641s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 26.182486534118652s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.020843029022216797s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 8.893013000488281e-05s
Believability | Calculation of trust value for CLLD-SAILS took 9.059906005859375e-06s
INFO | --- Analysis for clld-sails took 83.80728697776794s
Availability | SPARQL endpoint availability check for CLLD-WALS took 8.988380432128906e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.37383103370666504s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.023291826248168945s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0008096694946289062s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 0.0001068115234375s
Believability | Calculation of trust value for CLLD-WALS took 1.8835067749023438e-05s
INFO | --- Analysis for clld-wals took 57.564858198165894s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.38690185546875e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.5447564125061035s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 25.8783016204834s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.021050453186035156s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 2.5510787963867188e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 8.106231689453125e-05s
Interoperability | Check the re-using of existing vocabs for CLLD-WOLD took 1.430511474609375e-06s
Believability | Calculation of trust value for CLLD-WOLD took 1.0967254638671875e-05s
INFO | --- Analysis for clld-wold took 215.60795903205872s
Availability | SPARQL endpoint availability check for COD inventory took 0.2532682418823242s
Availability | VoID file availability check for COD inventory took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for COD inventory took 0.46663832664489746s
Reputation | Calculation of the PageRank for COD inventory took 0.0207822322845459s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for COD inventory took 3.170967102050781e-05s
Believability | Calculation of trust value for COD inventory took 1.2159347534179688e-05s
INFO | --- Analysis for cod-inventory took 105.07797002792358s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.17057180404663086s
Availability | VoID file availability check for Cooperation Databank took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.32480859756469727s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.020955801010131836s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 4.100799560546875e-05s
Believability | Calculation of trust value for Cooperation Databank took 7.3909759521484375e-06s
INFO | --- Analysis for CoDa took 135.3027491569519s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 0.9584996700286865s
Availability | VoID file availability check for OpenUpLabs COINS took 0.0002989768981933594s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 25.478150129318237s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.021819114685058594s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.1948089599609375e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 1.049041748046875e-05s
INFO | --- Analysis for coins-openuplabs took 78.2630307674408s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.435300827026367s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.00030803680419921875s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.357712984085083s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.021020174026489258s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.96453857421875e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 7.3909759521484375e-06s
INFO | --- Analysis for CoLChina_sp2000 took 90.83458471298218s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.056145429611206055s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 29.975176572799683s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.020745038986206055s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 4.076957702636719e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 1.2636184692382812e-05s
INFO | --- Analysis for colinda took 160.66598677635193s
Availability | SPARQL endpoint availability check for CN  2012 took 26.16772985458374s
Availability | VoID file availability check for CN  2012 took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.32973718643188477s
Reputation | Calculation of the PageRank for CN  2012 took 0.021020889282226562s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 7.653236389160156e-05s
Believability | Calculation of trust value for CN  2012 took 9.298324584960938e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 262.97899651527405s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.5715727806091309s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0006654262542724609s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 23.93692135810852s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.02103877067565918s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 4.553794860839844e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for CompHistSem took 128.03097319602966s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 0.7863953113555908s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0005946159362792969s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 26.161909341812134s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.02104973793029785s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 4.553794860839844e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 1.1444091796875e-05s
INFO | --- Analysis for comsode-d3-2 took 164.57312035560608s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 8.749961853027344e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 26.334742069244385s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.0209958553314209s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 9.417533874511719e-05s
Believability | Calculation of trust value for 2011 US Congress People took 9.298324584960938e-06s
INFO | --- Analysis for congresspeople took 135.89571380615234s
Availability | SPARQL endpoint availability check for MIMO took 0.28804540634155273s
Availability | VoID file availability check for MIMO took 0.0006804466247558594s
Completeness | Calculation of interlinking completeness for MIMO took 29.514113187789917s
Reputation | Calculation of the PageRank for MIMO took 0.021222352981567383s
Interlinking | Calculation of Degree of Connection for MIMO took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.52587890625e-05s
Believability | Calculation of trust value for MIMO took 1.1920928955078125e-05s
INFO | --- Analysis for CONNECTED took 217.5651412010193s
Availability | SPARQL endpoint availability check for Copyright Free Music took 8.988380432128906e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 29.588011980056763s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.02345442771911621s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0010089874267578125s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 4.553794860839844e-05s
Believability | Calculation of trust value for Copyright Free Music took 1.2874603271484375e-05s
INFO | --- Analysis for Copyright_Free_Music took 187.56522417068481s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 7.104873657226562e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.32575178146362305s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.020817279815673828s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 7.152557373046875e-05s
Believability | Calculation of trust value for CopyrightTermBank took 1.1682510375976562e-05s
INFO | --- Analysis for copyrighttermbank took 69.7502830028534s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 2.0135843753814697s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.3329300880432129s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.021317720413208008s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0008602142333984375s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 5.2928924560546875e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 1.2636184692382812e-05s
INFO | --- Analysis for core took 164.5763645172119s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.5136597156524658s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0005197525024414062s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 113.30026006698608s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 0.991520881652832s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 9.258225440979004s
Interoperability | New terms check for Corine linked dataset @PSNC took 14.36617398262024s
Versatility | Languages check for Corine linked dataset @PSNC took 300.15208864212036s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 2.039741277694702s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.2969493865966797s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 6.7670557498931885s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.33484482765197754s
License | MR license check for Corine linked dataset @PSNC took 0.7488696575164795s
License | HR license check for Corine linked dataset @PSNC took 300.1938989162445s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.22683072090148926s
Understandability | Number of label check for Corine linked dataset @PSNC took 2.9790427684783936s
Understandability | URI regex check for Corine linked dataset @PSNC took 1.182525634765625s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.5156474113464355s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.20467329025268555s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.2591252326965332s
Performance | Throughput check for Corine linked dataset @PSNC took 11.481131553649902s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 8.225440979003906e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.2013564109802246s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.20027756690979004s
Interlinking | skos check for Corine linked dataset @PSNC took 0.49141907691955566s
Interlinking | skos check for Corine linked dataset @PSNC took 0.41358160972595215s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 4.949844598770142s
Currency | Creation date check for Corine linked dataset @PSNC took 0.48475003242492676s
Currency | Modification date check for Corine linked dataset @PSNC took 0.21783161163330078s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 149.41777205467224s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.21686315536499023s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.2698171138763428s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.2699136734008789s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 43.24136447906494s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.6865148544311523s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.69046950340271s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.20962858200073242s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 87.18647050857544s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.379383087158203s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 30.250260829925537s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.5738282203674316s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 87.461341381073s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.76702618598938s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.5074067115783691s
Security | Sign check for Corine linked dataset @PSNC took 1.2727618217468262s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 10.806972980499268s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 0.9768428802490234s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.023744821548461914s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 3.838539123535156e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 1.1682510375976562e-05s
INFO | --- Analysis for Corine_linked_dataset took 2413.5059320926666s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 4.744529724121094e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.339402437210083s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.026592493057250977s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 7.271766662597656e-05s
Believability | Calculation of trust value for Cornetto1.2 took 1.2874603271484375e-05s
INFO | --- Analysis for cornetto took 179.14984035491943s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.15305447578430176s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0005028247833251953s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 172.47683095932007s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.5615389347076416s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 48.696242570877075s
Interoperability | New terms check for Corporate Body Named Authority List  took 58.75681281089783s
Versatility | Languages check for Corporate Body Named Authority List  took 300.1296236515045s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 24.010282278060913s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.33435988426208496s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.4839816093444824s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 4.450525522232056s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.22121787071228027s
License | MR license check for Corporate Body Named Authority List  took 0.37276124954223633s
License | HR license check for Corporate Body Named Authority List  took 300.06523418426514s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.19379019737243652s
Understandability | Number of label check for Corporate Body Named Authority List  took 3.551813840866089s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.35848546028137207s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.1316988468170166s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.31700897216796875s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.2841789722442627s
Performance | Throughput check for Corporate Body Named Authority List  took 10.29758906364441s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 0.00011181831359863281s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.13616704940795898s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 7.085116624832153s
Interlinking | skos check for Corporate Body Named Authority List  took 0.418837308883667s
Interlinking | skos check for Corporate Body Named Authority List  took 0.31985020637512207s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.3082401752471924s
Currency | Creation date check for Corporate Body Named Authority List  took 4.8656792640686035s
Currency | Modification date check for Corporate Body Named Authority List  took 0.18345141410827637s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 418.0962736606598s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.17224550247192383s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.2358720302581787s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.1682577133178711s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 42.505454540252686s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.0929019451141357s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.674562454223633s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.15960192680358887s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.4333019256592s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.748668432235718s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 40.657116651535034s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.9448933601379395s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.58758330345154s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 3.1329259872436523s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.48595166206359863s
Security | Sign check for Corporate Body Named Authority List  took 0.28367018699645996s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 11.508374691009521s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 0.8285393714904785s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.02132415771484375s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 5.841255187988281e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 1.9073486328125e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 1.1444091796875e-05s
INFO | --- Analysis for corporate-body took 14577.236552476883s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.5603997707366943s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0007526874542236328s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 23.5021812915802s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.020992755889892578s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 4.0531158447265625e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 1.2636184692382812e-05s
INFO | --- Analysis for CorpusFibonacci took 174.98312950134277s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.16896653175354004s
Availability | VoID file availability check for Country Name Authority List took 0.0013740062713623047s
Extra | Recovery of all triples for Country Name Authority List took 160.6411693096161s
Performance | Total latancy measurement for Country Name Authority List took 0.5835649967193604s
Amount of data | Number of triples check for Country Name Authority List took 42.366867542266846s
Interoperability | New terms check for Country Name Authority List took 53.85378956794739s
Versatility | Languages check for Country Name Authority List took 300.1363821029663s
Interpretability | Number of blank nodes check for Country Name Authority List took 18.08805227279663s
Security | Check HTTPS for Country Name Authority List took 0.3152289390563965s
Interpretability | RDF structures check for Country Name Authority List took 0.2711942195892334s
Versatility | Serialization formats check for Country Name Authority List took 3.8428525924682617s
Availability | RDF dump link check for Country Name Authority List took 0.23779606819152832s
License | MR license check for Country Name Authority List took 0.4940216541290283s
License | HR license check for Country Name Authority List took 300.0576591491699s
Amount of data | Number of property check for Country Name Authority List took 0.19008445739746094s
Understandability | Number of label check for Country Name Authority List took 3.413179397583008s
Understandability | URI regex check for Country Name Authority List took 0.4335308074951172s
Understandability | Vocabs check for Country Name Authority List took 0.10618853569030762s
Verifiability | Authors check for Country Name Authority List took 0.24738740921020508s
Verifiability | Publishers check for Country Name Authority List took 0.22292399406433105s
Performance | Throughput check for Country Name Authority List took 10.545780897140503s
Amount of data | Check the number of entities for Country Name Authority List took 9.083747863769531e-05s
Verifiability | Contribs. check for Country Name Authority List took 0.1875753402709961s
Interlinking | sameAs chians check for Country Name Authority List took 7.206573009490967s
Interlinking | skos check for Country Name Authority List took 0.165236234664917s
Interlinking | skos check for Country Name Authority List took 0.13559913635253906s
Timeliness | dataset update frequency check for Country Name Authority List took 0.3611791133880615s
Currency | Creation date check for Country Name Authority List took 0.5574169158935547s
Currency | Modification date check for Country Name Authority List took 0.15174436569213867s
Rep.Conc. | URIs length for Country Name Authority List took 417.37576174736023s
Interoperability | New vocabularies check for Country Name Authority List took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.16414999961853027s
Accuracy | Check Functional Property for Country Name Authority List took 0.24296021461486816s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.1538698673248291s
Accuracy | Check Empty annotation labels for Country Name Authority List took 39.29027485847473s
Accuracy | Check White space in annotation for Country Name Authority List took 3.1162972450256348s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.6794347763061523s
Consistency | Disjoint class check for Country Name Authority List took 0.16956210136413574s
Consistency | Check Misplaced properties for Country Name Authority List took 300.4212062358856s
Consistency | Misplaced classes for Country Name Authority List took 8.709505081176758s
Consistency | Check Ontology hijacking for Country Name Authority List took 37.753889322280884s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.9311318397521973s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.6761589050293s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.1661722660064697s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.5242562294006348s
Security | Sign check for Country Name Authority List took 0.14516019821166992s
Availability | Check URIs Dereferenciability for Country Name Authority List took 11.440948724746704s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 23.45950722694397s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.02122354507446289s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 6.198883056640625e-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 1.239776611328125e-05s
INFO | --- Analysis for country-authority-list took 14446.021684646606s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.08737444877624512s
Availability | VoID file availability check for Courts thesaurus took 0.00031065940856933594s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 29.050711154937744s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.02097463607788086s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 7.843971252441406e-05s
Believability | Calculation of trust value for Courts thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for courts-thesaurus took 188.20061993598938s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 20.37052869796753s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.31060171127319336s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.020956754684448242s
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.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 9.870529174804688e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 1.2159347534179688e-05s
INFO | --- Analysis for Covid-on-the-Web took 169.26454854011536s
Availability | SPARQL endpoint availability check for CPA 2008 took 25.463273763656616s
Availability | VoID file availability check for CPA 2008 took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for CPA 2008 took 31.15164589881897s
Reputation | Calculation of the PageRank for CPA 2008 took 0.021577835083007812s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 4.220008850097656e-05s
Believability | Calculation of trust value for CPA 2008 took 1.0013580322265625e-05s
INFO | --- Analysis for cpa-2008 took 264.3385155200958s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.34215879440307617s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0005662441253662109s
Extra | Recovery of all triples for Cooperative Patent Classification took 27.29225754737854s
Performance | Total latancy measurement for Cooperative Patent Classification took 2.1722095012664795s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.9514307975769s
Versatility | Languages check for Cooperative Patent Classification took 100.2871322631836s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.56754112243652s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.6645047664642334s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.5518386363983154s
Availability | RDF dump link check for Cooperative Patent Classification took 0.3810873031616211s
License | MR license check for Cooperative Patent Classification took 1.5504143238067627s
License | HR license check for Cooperative Patent Classification took 90.458988904953s
Amount of data | Number of property check for Cooperative Patent Classification took 0.32957959175109863s
Understandability | Number of label check for Cooperative Patent Classification took 90.19025826454163s
Understandability | URI regex check for Cooperative Patent Classification took 0.8529813289642334s
Understandability | Vocabs check for Cooperative Patent Classification took 0.7758362293243408s
Verifiability | Authors check for Cooperative Patent Classification took 0.29324841499328613s
Verifiability | Publishers check for Cooperative Patent Classification took 0.49924421310424805s
Performance | Throughput check for Cooperative Patent Classification took 12.809895038604736s
Amount of data | Check the number of entities for Cooperative Patent Classification took 3.361701965332031e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.22606301307678223s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.3027801513671875s
Interlinking | skos check for Cooperative Patent Classification took 0.6424438953399658s
Interlinking | skos check for Cooperative Patent Classification took 0.7321057319641113s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.33490729331970215s
Currency | Creation date check for Cooperative Patent Classification took 0.7417593002319336s
Currency | Modification date check for Cooperative Patent Classification took 1.0087692737579346s
Rep.Conc. | URIs length for Cooperative Patent Classification took 132.9886336326599s
Interoperability | New vocabularies check for Cooperative Patent Classification took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.20513153076171875s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 19.67079210281372s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 3.0438950061798096s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.992836236953735s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.5125277042388916s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 100.66674876213074s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 23.514944791793823s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.8095834255218506s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 101.74035263061523s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.903773784637451s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.3973846435546875s
Security | Sign check for Cooperative Patent Classification took 0.5368542671203613s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 4.8243958950042725s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.6898584365844727s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.02196025848388672s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 5.221366882324219e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 5.0067901611328125e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 8.106231689453125e-06s
INFO | --- Analysis for CPC took 1314.8429102897644s
Availability | SPARQL endpoint availability check for CPC 2008 took 25.51888608932495s
Availability | VoID file availability check for CPC 2008 took 0.0008475780487060547s
Completeness | Calculation of interlinking completeness for CPC 2008 took 25.168788194656372s
Reputation | Calculation of the PageRank for CPC 2008 took 0.02738499641418457s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 4.76837158203125e-05s
Believability | Calculation of trust value for CPC 2008 took 9.5367431640625e-06s
INFO | --- Analysis for cpc-2008 took 360.61966943740845s
Availability | SPARQL endpoint availability check for CPV  2003 took 21.375985145568848s
Availability | VoID file availability check for CPV  2003 took 0.0008957386016845703s
Completeness | Calculation of interlinking completeness for CPV  2003 took 25.808850288391113s
Reputation | Calculation of the PageRank for CPV  2003 took 0.021286964416503906s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 4.7206878662109375e-05s
Believability | Calculation of trust value for CPV  2003 took 5.7220458984375e-06s
INFO | --- Analysis for cpv-2003 took 283.15560007095337s
Availability | SPARQL endpoint availability check for CPV 2008 took 25.457186937332153s
Availability | VoID file availability check for CPV 2008 took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for CPV 2008 took 27.362964391708374s
Reputation | Calculation of the PageRank for CPV 2008 took 0.021265268325805664s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 5.602836608886719e-05s
Believability | Calculation of trust value for CPV 2008 took 9.059906005859375e-06s
INFO | --- Analysis for cpv-2008 took 232.5301012992859s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 260.9510443210602s
Availability | VoID file availability check for crowdsourcing-fb took 0.0009603500366210938s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 26.910858154296875s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.021054506301879883s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 5.412101745605469e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 1.239776611328125e-05s
INFO | --- Analysis for crowdsourcing-fb took 856.493273973465s
Availability | SPARQL endpoint availability check for CRTM took 20.30003046989441s
Availability | VoID file availability check for CRTM took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for CRTM took 23.76592993736267s
Reputation | Calculation of the PageRank for CRTM took 0.022403478622436523s
Interlinking | Calculation of Degree of Connection for CRTM took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for CRTM took 3.314018249511719e-05s
Believability | Calculation of trust value for CRTM took 1.621246337890625e-05s
INFO | --- Analysis for crtm took 185.17946600914001s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.602877616882324s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 30.145562887191772s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.023272037506103516s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0010879039764404297s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 7.009506225585938e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 9.775161743164062e-06s
INFO | --- Analysis for ctic-public-dataset took 240.65914964675903s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.5112466812133789s
Availability | VoID file availability check for CulturaLinkedData took 0.0005192756652832031s
Extra | Recovery of all triples for CulturaLinkedData took 142.88917231559753s
Performance | Total latancy measurement for CulturaLinkedData took 8.054145574569702s
Amount of data | Number of triples check for CulturaLinkedData took 2.562252998352051s
Interoperability | New terms check for CulturaLinkedData took 2.435741901397705s
Versatility | Languages check for CulturaLinkedData took 62.115089893341064s
Interpretability | Number of blank nodes check for CulturaLinkedData took 2.001796007156372s
Interpretability | RDF structures check for CulturaLinkedData took 2.176229238510132s
Versatility | Serialization formats check for CulturaLinkedData took 2.100365161895752s
Availability | RDF dump link check for CulturaLinkedData took 0.20828652381896973s
License | MR license check for CulturaLinkedData took 2.308563470840454s
License | HR license check for CulturaLinkedData took 60.6681706905365s
Amount of data | Number of property check for CulturaLinkedData took 1.898120403289795s
Understandability | Number of label check for CulturaLinkedData took 0.7764301300048828s
Understandability | URI regex check for CulturaLinkedData took 4.414276361465454s
Understandability | Vocabs check for CulturaLinkedData took 0.2274184226989746s
Verifiability | Authors check for CulturaLinkedData took 0.2608461380004883s
Verifiability | Publishers check for CulturaLinkedData took 1.9587554931640625s
Performance | Throughput check for CulturaLinkedData took 22.920918941497803s
Amount of data | Check the number of entities for CulturaLinkedData took 7.033348083496094e-05s
Verifiability | Contribs. check for CulturaLinkedData took 0.23200464248657227s
Interlinking | sameAs chians check for CulturaLinkedData took 2.119659900665283s
Interlinking | skos check for CulturaLinkedData took 0.3784518241882324s
Interlinking | skos check for CulturaLinkedData took 0.18415069580078125s
Timeliness | dataset update frequency check for CulturaLinkedData took 0.25617241859436035s
Currency | Creation date check for CulturaLinkedData took 0.3999757766723633s
Currency | Modification date check for CulturaLinkedData took 2.2262744903564453s
Rep.Conc. | URIs length for CulturaLinkedData took 52.41989278793335s
Interoperability | New vocabularies check for CulturaLinkedData took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 0.19803500175476074s
Accuracy | Check Functional Property for CulturaLinkedData took 2.004122257232666s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 0.1859753131866455s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 44.87872076034546s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.627152919769287s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.314725399017334s
Consistency | Disjoint class check for CulturaLinkedData took 1.9427847862243652s
Consistency | Check Misplaced properties for CulturaLinkedData took 10.016948699951172s
Consistency | Misplaced classes for CulturaLinkedData took 4.252265691757202s
Consistency | Check Ontology hijacking for CulturaLinkedData took 43.65932750701904s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.4793405532836914s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 9.462070226669312s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.408487319946289s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 1.9753599166870117s
Security | Sign check for CulturaLinkedData took 0.8147256374359131s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 11.434662818908691s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 24.452598094940186s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.021894216537475586s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 5.14984130859375e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 2.384185791015625e-06s
Believability | Calculation of trust value for CulturaLinkedData took 1.1444091796875e-05s
INFO | --- Analysis for culturalinkeddata took 694.1352944374084s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.2849395275115967s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.313382625579834s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.020972013473510742s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 4.267692565917969e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 8.58306884765625e-06s
INFO | --- Analysis for cz-ares-or took 57.40880513191223s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.11237859725952148s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0008382797241210938s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.3132946491241455s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.021372079849243164s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 4.029273986816406e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 5.245208740234375e-06s
INFO | --- Analysis for cz-ares-rzp took 129.875506401062s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.1156620979309082s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 24.13800358772278s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.021791696548461914s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.8623809814453125e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 9.5367431640625e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 104.82231187820435s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.13559961318969727s
Availability | VoID file availability check for Integrated pollution registry took 0.0017459392547607422s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.4142448902130127s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.17446351051330566s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 6.508827209472656e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.00628662109375s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 0.0002334117889404297s
Believability | Calculation of trust value for Integrated pollution registry took 3.0040740966796875e-05s
INFO | --- Analysis for cz-cenia-pollution took 83.93137240409851s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.14143061637878418s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.002843618392944336s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.41055846214294434s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.17207789421081543s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 4.00543212890625e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.006207704544067383s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 0.000255584716796875s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 8.58306884765625e-06s
INFO | --- Analysis for cz-contracts took 99.87535405158997s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.1323227882385254s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 21.521061420440674s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.022776126861572266s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.838539123535156e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 9.298324584960938e-06s
INFO | --- Analysis for cz-ctia-bans took 155.1257197856903s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.1299428939819336s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0006234645843505859s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 24.365046739578247s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.02254009246826172s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0011839866638183594s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 5.745887756347656e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 8.821487426757812e-06s
INFO | --- Analysis for cz-ctia-confiscations took 193.96260261535645s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.12402606010437012s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 24.925095796585083s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.021195650100708008s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 4.6253204345703125e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 9.775161743164062e-06s
INFO | --- Analysis for cz-ctia-focus took 194.95577669143677s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.13901042938232422s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0007770061492919922s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 25.324809074401855s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.021259546279907227s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.553794860839844e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 3.0517578125e-05s
INFO | --- Analysis for cz-ctia-inspections took 181.48790192604065s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.14032316207885742s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0017938613891601562s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.5030865669250488s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.16949224472045898s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 6.175041198730469e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.006339073181152344s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 0.00026798248291015625s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 5.030632019042969e-05s
INFO | --- Analysis for cz-ctia-sanctions took 125.44224166870117s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.22356653213500977s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.002832651138305664s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 26.913507223129272s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.1763169765472412s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 6.628036499023438e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.006959438323974609s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 0.0002884864807128906s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 4.792213439941406e-05s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 146.58520793914795s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.13255643844604492s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0019481182098388672s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.47987914085388184s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.17140722274780273s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 6.0558319091796875e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.006313800811767578s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 0.00020575523376464844s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 3.0040740966796875e-05s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 205.15949487686157s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 1.089021921157837s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0020389556884765625s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 22.465599060058594s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.02124643325805664s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 4.4345855712890625e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 8.821487426757812e-06s
INFO | --- Analysis for cz-czso-average-salaries took 170.55508637428284s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.6089282035827637s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0017621517181396484s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 24.395928621292114s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.17273950576782227s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 5.745887756347656e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.006259441375732422s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 0.0002410411834716797s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 3.0279159545898438e-05s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 86.57439494132996s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.5811967849731445s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 21.969592571258545s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.17724323272705078s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 9.679794311523438e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0071637630462646484s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0002529621124267578s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 5.340576171875e-05s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 159.13307571411133s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.5625667572021484s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.00031685829162597656s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.3944740295410156s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.022022247314453125s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0009410381317138672s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 5.340576171875e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 3.2901763916015625e-05s
INFO | --- Analysis for cz-czso-job-applicants took 103.43361210823059s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.6316375732421875s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0018529891967773438s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.4704711437225342s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.17226934432983398s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 0.00010657310485839844s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.00667572021484375s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 0.00029277801513671875s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 2.9802322387695312e-05s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 107.75971984863281s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.5989012718200684s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0028581619262695312s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 26.814741373062134s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.17353487014770508s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 5.91278076171875e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.006245136260986328s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 0.00021982192993164062s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 3.075599670410156e-05s
INFO | --- Analysis for cz-czso-regions took 112.008944272995s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.617560625076294s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0018630027770996094s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 25.71342658996582s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.17403244972229004s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 6.127357482910156e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.006335735321044922s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 0.00023889541625976562s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 3.147125244140625e-05s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 127.18231916427612s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.6556432247161865s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0016586780548095703s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 22.81249189376831s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.17679905891418457s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 6.246566772460938e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.006290435791015625s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 0.00023865699768066406s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 3.147125244140625e-05s
INFO | --- Analysis for cz-czso-social-service-facilities took 209.81215691566467s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.6058342456817627s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.002405405044555664s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.47555017471313477s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.17348694801330566s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 5.7697296142578125e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0062923431396484375s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 0.00032067298889160156s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 2.9325485229492188e-05s
INFO | --- Analysis for cz-czso-unemployment-rate took 110.63406872749329s
Availability | SPARQL endpoint availability check for ATC groups took 0.12648534774780273s
Availability | VoID file availability check for ATC groups took 0.003042936325073242s
Completeness | Calculation of interlinking completeness for ATC groups took 0.47676634788513184s
Reputation | Calculation of the PageRank for ATC groups took 0.17077326774597168s
Interlinking | Calculation of Degree of Connection for ATC groups took 5.984306335449219e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.006500720977783203s
Interlinking | Calculation of Clustering coefficient for ATC groups took 0.0005259513854980469s
Believability | Calculation of trust value for ATC groups took 3.743171691894531e-05s
INFO | --- Analysis for cz-eh-1-atc took 130.69911003112793s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.13775348663330078s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0021715164184570312s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.48541688919067383s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.17679572105407715s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 6.365776062011719e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0066416263580322266s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0002281665802001953s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 2.8848648071289062e-05s
INFO | --- Analysis for cz-fulfillments took 110.61776065826416s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.061606407165527344s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0018069744110107422s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.46674418449401855s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.17286133766174316s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 6.914138793945312e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.006367921829223633s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 0.00038623809814453125s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 2.9802322387695312e-05s
INFO | --- Analysis for cz-ic took 134.8749692440033s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.18762660026550293s
Availability | VoID file availability check for List of Czech data boxes took 0.7231559753417969s
Extra | Recovery of all triples for List of Czech data boxes took 178.02460432052612s
Performance | Total latancy measurement for List of Czech data boxes took 0.7100231647491455s
Amount of data | Number of triples check for List of Czech data boxes took 57.118163108825684s
Interoperability | New terms check for List of Czech data boxes took 19.623539447784424s
Versatility | Languages check for List of Czech data boxes took 300.1891984939575s
Interpretability | Number of blank nodes check for List of Czech data boxes took 1.3584952354431152s
Interpretability | RDF structures check for List of Czech data boxes took 0.32912158966064453s
Versatility | Serialization formats check for List of Czech data boxes took 0.28354668617248535s
Availability | RDF dump link check for List of Czech data boxes took 20.713656425476074s
License | MR license check for List of Czech data boxes took 0.6747407913208008s
License | HR license check for List of Czech data boxes took 60.62645602226257s
Amount of data | Number of property check for List of Czech data boxes took 0.138716459274292s
Understandability | Number of label check for List of Czech data boxes took 1.9902966022491455s
Understandability | URI regex check for List of Czech data boxes took 0.5036571025848389s
Understandability | Vocabs check for List of Czech data boxes took 0.1445150375366211s
Verifiability | Authors check for List of Czech data boxes took 0.26545238494873047s
Verifiability | Publishers check for List of Czech data boxes took 0.14451885223388672s
Performance | Throughput check for List of Czech data boxes took 10.489380359649658s
Amount of data | Check the number of entities for List of Czech data boxes took 21.6310555934906s
Verifiability | Contribs. check for List of Czech data boxes took 0.16815185546875s
Interlinking | sameAs chians check for List of Czech data boxes took 0.4866206645965576s
Interlinking | skos check for List of Czech data boxes took 0.2260596752166748s
Interlinking | skos check for List of Czech data boxes took 0.13346624374389648s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.3397998809814453s
Currency | Creation date check for List of Czech data boxes took 0.2993311882019043s
Currency | Modification date check for List of Czech data boxes took 0.1519477367401123s
Rep.Conc. | URIs length for List of Czech data boxes took 183.27596163749695s
Interoperability | New vocabularies check for List of Czech data boxes took 27.043553590774536s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.4666571617126465s
Accuracy | Check Functional Property for List of Czech data boxes took 0.19504070281982422s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.1837451457977295s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 63.44409990310669s
Accuracy | Check White space in annotation for List of Czech data boxes took 23.342403888702393s
Accuracy | Check Datatype consistency for List of Czech data boxes took 20.658989429473877s
Consistency | Disjoint class check for List of Czech data boxes took 0.16005492210388184s
Consistency | Check Misplaced properties for List of Czech data boxes took 93.51940178871155s
Consistency | Misplaced classes for List of Czech data boxes took 66.33345794677734s
Consistency | Check Ontology hijacking for List of Czech data boxes took 52.918766021728516s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 9.611098766326904s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 75.20552492141724s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 23.709869384765625s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.5107600688934326s
Security | Sign check for List of Czech data boxes took 0.17407584190368652s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 570.2138524055481s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 29.25844693183899s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.1876370906829834s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 0.00013327598571777344s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.008515119552612305s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 0.00035119056701660156s
Interoperability | Check the re-using of existing vocabs for List of Czech data boxes took 29.245846033096313s
Believability | Calculation of trust value for List of Czech data boxes took 3.0279159545898438e-05s
INFO | --- Analysis for cz-list-of-databoxes took 2709.1178164482117s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1438298225402832s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6811883449554443s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 175.21626210212708s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.704580545425415s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 56.19060707092285s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 19.699172496795654s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.1202201843262s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.3743128776550293s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.18010878562927246s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.18255066871643066s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 19.574162244796753s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6748998165130615s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 58.50273418426514s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1487898826599121s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.552353858947754s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5317440032958984s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13306689262390137s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.15802526473999023s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.14931821823120117s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.73377776145935s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 22.654719352722168s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.25673389434814453s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.48244309425354004s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.14309096336364746s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1401655673980713s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1436605453491211s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.31681227684020996s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1556553840637207s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 201.99068808555603s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 27.924761056900024s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4559168815612793s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2533431053161621s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.23844218254089355s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 63.97266674041748s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 23.35281252861023s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 20.881314992904663s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.17723989486694336s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 95.01512432098389s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 67.33663940429688s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 53.112966537475586s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 9.66908311843872s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 75.90845489501953s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 23.856258869171143s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5832195281982422s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.18035149574279785s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 600.6791198253632s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 23.383232355117798s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.17490315437316895s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.00010538101196289062s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.006438016891479492s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0003199577331542969s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 27.74474000930786s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.9802322387695312e-05s
INFO | --- Analysis for cz-nace took 2678.9509150981903s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.31616759300231934s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0023338794708251953s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.1 took 417.5823986530304s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.9195804595947266s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.118898630142212s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.1 took 10.091283321380615s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.1 took 212.88374423980713s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.753312349319458s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.3381030559539795s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.1 took 7.0479254722595215s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.1 took 5.353247404098511s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.6732010841369629s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.2871193885803223s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.16040873527526855s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.5434110164642334s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.48845601081848145s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.23994827270507812s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.4120619297027588s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2771010398864746s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.1 took 11.219332695007324s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.1 took 7.772445678710938e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.2139585018157959s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.20620250701904297s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.42176294326782227s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.16731595993041992s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.470440149307251s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.6283969879150391s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.42378687858581543s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.1 took 86.8816750049591s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.16686415672302246s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.28220701217651367s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.28995847702026367s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.1 took 72.1442379951477s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.4402947425842285s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.778369188308716s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.24545812606811523s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.4664618968963623s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 8.64736294746399s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.1 took 74.07783460617065s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.9287991523742676s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.1 took 4.987547159194946s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 3.3482136726379395s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.28969717025756836s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.858069896697998s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.1 took 1005.2123749256134s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.1 took 33.57483792304993s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.022446155548095703s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.1 took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.1 took 4.601478576660156e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.1 took 2.1457672119140625e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.1 took 1.0013580322265625e-05s
INFO | --- Analysis for cz-nkod took 29840.815983772278s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.23660492897033691s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0018129348754882812s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 27.604381799697876s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.020931482315063477s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 4.029273986816406e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 1.0251998901367188e-05s
INFO | --- Analysis for cz-orders took 136.78186774253845s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.22045016288757324s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.2718217372894287s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 157.06891441345215s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.6012194156646729s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 57.78481459617615s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 12.0877206325531s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.1606957912445s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 1.482839822769165s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.1392219066619873s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.18181848526000977s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 14.721924543380737s
License | MR license check for Institutions of public power of the Czech Republic took 0.5389723777770996s
License | HR license check for Institutions of public power of the Czech Republic took 59.514155626297s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.12271952629089355s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 1.0865774154663086s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.451019287109375s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.12597966194152832s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.12551116943359375s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.11791682243347168s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.716105222702026s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.3279688358306885s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.13559198379516602s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.3481712341308594s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.15948486328125s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.11577725410461426s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.19628548622131348s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.24015474319458008s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.11695122718811035s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 119.83033442497253s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 18.271533012390137s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.37152743339538574s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.151961088180542s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.1417837142944336s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 34.02569389343262s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 2.840677499771118s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.683685541152954s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.12182497978210449s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 76.01386427879333s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 8.466064214706421s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 35.70099711418152s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.416860580444336s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 69.15188145637512s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.9546802043914795s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 0.3895299434661865s
Security | Sign check for Institutions of public power of the Czech Republic took 0.17214131355285645s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 386.5594058036804s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 32.04737401008606s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.021854400634765625s
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.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 6.604194641113281e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 13.835858821868896s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 9.775161743164062e-06s
INFO | --- Analysis for cz-ovm took 2020.4756138324738s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.11659717559814453s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 27.16948890686035s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.0211789608001709s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 5.555152893066406e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 5.7220458984375e-06s
INFO | --- Analysis for cz-ovm-agendas took 116.16265511512756s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12458586692810059s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0005884170532226562s
Extra | Recovery of all triples for Registry of territorial identification, addresses and real estate of the Czech Republic took 42.52680468559265s
Performance | Total latancy measurement for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.6132636070251465s
Amount of data | Number of triples check for Registry of territorial identification, addresses and real estate of the Czech Republic took 110.13606262207031s
Interoperability | New terms check for Registry of territorial identification, addresses and real estate of the Czech Republic took 18.17304491996765s
Versatility | Languages check for Registry of territorial identification, addresses and real estate of the Czech Republic took 300.1707615852356s
Interpretability | Number of blank nodes check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.20497870445251465s
Interpretability | RDF structures check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.6437201499938965s
Versatility | Serialization formats check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2280423641204834s
Availability | RDF dump link check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.8398258686065674s
License | MR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1907792091369629s
License | HR license check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.15565061569213867s
Amount of data | Number of property check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.11037921905517578s
Understandability | Number of label check for Registry of territorial identification, addresses and real estate of the Czech Republic took 3.8080356121063232s
Understandability | URI regex check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.24470162391662598s
Understandability | Vocabs check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13361406326293945s
Verifiability | Authors check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2093355655670166s
Verifiability | Publishers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.21764445304870605s
Performance | Throughput check for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.48809552192688s
Amount of data | Check the number of entities for Registry of territorial identification, addresses and real estate of the Czech Republic took 3.0517578125e-05s
Verifiability | Contribs. check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12339901924133301s
Interlinking | sameAs chians check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1200709342956543s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.14284634590148926s
Interlinking | skos check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12221813201904297s
Timeliness | dataset update frequency check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12811946868896484s
Currency | Creation date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2630770206451416s
Currency | Modification date check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13366270065307617s
Rep.Conc. | URIs length for Registry of territorial identification, addresses and real estate of the Czech Republic took 123.19095182418823s
Interoperability | New vocabularies check for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1310420036315918s
Accuracy | Check Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.1411879062652588s
Accuracy | Check Inverse Functional Property for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.14112043380737305s
Accuracy | Check Empty annotation labels for Registry of territorial identification, addresses and real estate of the Czech Republic took 11.200313329696655s
Accuracy | Check White space in annotation for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.2227694988250732s
Accuracy | Check Datatype consistency for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.6748526096343994s
Consistency | Disjoint class check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.13337922096252441s
Consistency | Check Misplaced properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 87.81471681594849s
Consistency | Misplaced classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 8.46941590309143s
Consistency | Check Ontology hijacking for Registry of territorial identification, addresses and real estate of the Czech Republic took 15.201326847076416s
Consistency | Check Invalid usage of undefined classes for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.4263331890106201s
Consistency | Check Invalid usage of undefined properties for Registry of territorial identification, addresses and real estate of the Czech Republic took 88.8661937713623s
Conciseness | Check Extensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 2.953871488571167s
Conciseness | Check Intensional conciseness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2938716411590576s
Security | Sign check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.12300515174865723s
Availability | Check URIs Dereferenciability for Registry of territorial identification, addresses and real estate of the Czech Republic took 10.332609415054321s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 20.426345348358154s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.024192094802856445s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.724761962890625e-05s
Interoperability | Check the re-using of existing vocabs for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.430511474609375e-06s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 7.62939453125e-06s
INFO | --- Analysis for cz-ruian took 1519.7213952541351s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.7140064239501953s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.32827091217041016s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.021311283111572266s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 9.560585021972656e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 8.106231689453125e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 145.34294414520264s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.48949646949768066s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 33.918803215026855s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.021188974380493164s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.00107574462890625s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 6.508827209472656e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 1.0013580322265625e-05s
INFO | --- Analysis for cz-sao-check-actions took 150.32635259628296s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.41953325271606445s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.29459261894226074s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.021540164947509766s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.457069396972656e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 8.821487426757812e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 95.90297770500183s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.10928058624267578s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 32.375962018966675s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.022211313247680664s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0008106231689453125s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.743171691894531e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 1.3828277587890625e-05s
INFO | --- Analysis for cz-sidc-drug-ingredients took 125.13875150680542s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.11760330200195312s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0008368492126464844s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.3141965866088867s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.02112293243408203s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.7670135498046875e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 9.298324584960938e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 168.98703169822693s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.1247107982635498s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.39147257804870605s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.021225452423095703s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 4.00543212890625e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 1.1920928955078125e-05s
INFO | --- Analysis for cz-sidc-drugs took 32.502620220184326s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.19367337226867676s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0006952285766601562s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 159.98482489585876s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.5957808494567871s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 57.54992604255676s
Interoperability | New terms check for Summary types of Czech institutions of public power took 12.143975973129272s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.16255021095276s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 1.360304594039917s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.13895630836486816s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.15429139137268066s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 14.585009098052979s
License | MR license check for Summary types of Czech institutions of public power took 0.4559366703033447s
License | HR license check for Summary types of Czech institutions of public power took 59.22721886634827s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.12067079544067383s
Understandability | Number of label check for Summary types of Czech institutions of public power took 1.0520708560943604s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.46038174629211426s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.1363542079925537s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.13260602951049805s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.1366255283355713s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.674124479293823s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.3222928047180176s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.13613343238830566s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.32149744033813477s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.1669478416442871s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.1185460090637207s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.18572378158569336s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.23075103759765625s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.12419962882995605s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 120.92046618461609s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 21.100367546081543s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.493194580078125s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.2607548236846924s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.25694799423217773s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 33.9767165184021s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 2.8399648666381836s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.67696475982666s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.11588931083679199s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 74.57321953773499s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 8.473860740661621s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 34.5135817527771s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.4029872417449951s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 69.56329846382141s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.9769763946533203s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 0.38733530044555664s
Security | Sign check for Summary types of Czech institutions of public power took 0.1532127857208252s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 376.4314033985138s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 27.288225650787354s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.021558046340942383s
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.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 4.696846008300781e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 15.088191270828247s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 1.0013580322265625e-05s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 2067.285164117813s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.133345365524292s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0007634162902832031s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.2985537052154541s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.021032333374023438s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 5.91278076171875e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 8.58306884765625e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 56.279422998428345s
Availability | SPARQL endpoint availability check for State funding providers took 0.11469030380249023s
Availability | VoID file availability check for State funding providers took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for State funding providers took 27.08899164199829s
Reputation | Calculation of the PageRank for State funding providers took 0.02076864242553711s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for State funding providers took 4.315376281738281e-05s
Believability | Calculation of trust value for State funding providers took 1.049041748046875e-05s
INFO | --- Analysis for cz-vavai-funding-providers took 146.82309198379517s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.11542725563049316s
Availability | VoID file availability check for Organizations active in R&D took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 27.946471452713013s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.021199703216552734s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 4.3392181396484375e-05s
Believability | Calculation of trust value for Organizations active in R&D took 8.821487426757812e-06s
INFO | --- Analysis for cz-vavai-organizations took 93.75553178787231s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.10847616195678711s
Availability | VoID file availability check for R&D Programmes took 0.0008974075317382812s
Completeness | Calculation of interlinking completeness for R&D Programmes took 25.195310592651367s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020812034606933594s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 5.364418029785156e-05s
Believability | Calculation of trust value for R&D Programmes took 9.5367431640625e-06s
INFO | --- Analysis for cz-vavai-programmes took 107.88938021659851s
Availability | SPARQL endpoint availability check for R&D Projects took 0.11630034446716309s
Availability | VoID file availability check for R&D Projects took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for R&D Projects took 28.68511652946472s
Reputation | Calculation of the PageRank for R&D Projects took 0.021007776260375977s
Interlinking | Calculation of Degree of Connection for R&D Projects took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 5.793571472167969e-05s
Believability | Calculation of trust value for R&D Projects took 8.58306884765625e-06s
INFO | --- Analysis for cz-vavai-projects took 117.99731659889221s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.10950112342834473s
Availability | VoID file availability check for Institutional research plans took 0.0003151893615722656s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.34252452850341797s
Reputation | Calculation of the PageRank for Institutional research plans took 0.025125741958618164s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.673004150390625e-05s
Believability | Calculation of trust value for Institutional research plans took 9.775161743164062e-06s
INFO | --- Analysis for cz-vavai-research-plans took 141.92927718162537s
Availability | SPARQL endpoint availability check for Results of R&D took 0.12444329261779785s
Availability | VoID file availability check for Results of R&D took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.36136722564697266s
Reputation | Calculation of the PageRank for Results of R&D took 0.021051406860351562s
Interlinking | Calculation of Degree of Connection for Results of R&D took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.5299530029296875e-05s
Believability | Calculation of trust value for Results of R&D took 1.52587890625e-05s
INFO | --- Analysis for cz-vavai-results took 114.22193551063538s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.11614847183227539s
Availability | VoID file availability check for Tenders in R&D took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.3459179401397705s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.0211334228515625s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0008366107940673828s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.839897155761719e-05s
Believability | Calculation of trust value for Tenders in R&D took 9.059906005859375e-06s
INFO | --- Analysis for cz-vavai-tenders took 28.04301905632019s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 9.131431579589844e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0008416175842285156s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 26.472798109054565s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.1811201572418213s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 7.605552673339844e-05s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.007925987243652344s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 0.00023508071899414062s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 4.0531158447265625e-05s
INFO | --- Analysis for czech_addresses took 141.32972264289856s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.6185386180877686s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0007505416870117188s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.3239598274230957s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.02197122573852539s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 4.410743713378906e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 1.3589859008789062e-05s
INFO | --- Analysis for DanteLatinLoanwords took 91.1194658279419s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.39922642707824707s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0006723403930664062s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 141.05202865600586s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.0061969757080078s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 15.177039384841919s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.111057996749878s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.29507327079773s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.26337218284606934s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.13565635681152344s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.3335397243499756s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.2511725425720215s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.24399495124816895s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.24409699440002441s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 120.33011507987976s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.2411048412322998s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 2.3472676277160645s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.5197865962982178s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.26461362838745117s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.26207733154296875s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.254408597946167s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.37387728691101s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 8.58306884765625e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.25020313262939453s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 1.6513919830322266s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 1.035426378250122s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.2250218391418457s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.22197699546813965s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 3.1037755012512207s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 1.3803484439849854s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 88.6522045135498s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.238816499710083s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.5419933795928955s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.3165278434753418s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 43.02876543998718s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.269063949584961s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.6567940711975098s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.2698190212249756s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 21.761691093444824s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.643967866897583s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 41.40198302268982s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.5292353630065918s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 22.847111225128174s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.905272960662842s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.2777583599090576s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.2471907138824463s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 10.495917797088623s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.5906670093536377s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.021494626998901367s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.000171661376953125s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 1.430511474609375e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 1.2874603271484375e-05s
INFO | --- Analysis for data-bnf-fr took 927.228830575943s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.6994123458862305s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 27.958717823028564s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.02208542823791504s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 7.200241088867188e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 8.58306884765625e-06s
INFO | --- Analysis for data-cnr-it took 130.57031226158142s
Availability | SPARQL endpoint availability check for Data.gov took 1.6017043590545654s
Availability | VoID file availability check for Data.gov took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for Data.gov took 0.34160923957824707s
Reputation | Calculation of the PageRank for Data.gov took 0.02098250389099121s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.6716461181640625e-05s
Believability | Calculation of trust value for Data.gov took 8.821487426757812e-06s
INFO | --- Analysis for data-gov took 97.47201108932495s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.06418752670288086s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.3127436637878418s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.021266460418701172s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 7.534027099609375e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 8.58306884765625e-06s
INFO | --- Analysis for data-gov-ie took 79.99550890922546s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 9.012222290039062e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.33399009704589844s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.02091383934020996s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.534027099609375e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 8.344650268554688e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 113.8497166633606s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 22.382864475250244s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0006926059722900391s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 25.562336683273315s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.021590471267700195s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.723403930664062e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 1.239776611328125e-05s
INFO | --- Analysis for data-hnm-hu took 302.88373613357544s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.14249467849731445s
Availability | VoID file availability check for Climb Dataincubator took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.34035515785217285s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.02116084098815918s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 8.845329284667969e-05s
Believability | Calculation of trust value for Climb Dataincubator took 1.1205673217773438e-05s
INFO | --- Analysis for data-incubator-climb took 50.45317196846008s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.363059997558594e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0003669261932373047s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.3392772674560547s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.021213293075561523s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 0.00010204315185546875s
Believability | Calculation of trust value for Discogs in RDF took 1.1444091796875e-05s
INFO | --- Analysis for data-incubator-discogs took 103.25043654441833s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.05190849304199219s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.36237406730651855s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.02106499671936035s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.745887756347656e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 8.58306884765625e-06s
INFO | --- Analysis for data-incubator-metoffice took 86.79758358001709s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.059128522872924805s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0022797584533691406s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 31.098881483078003s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.02122330665588379s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 0.00011229515075683594s
Believability | Calculation of trust value for Moseley Folk Festival Data took 1.6927719116210938e-05s
INFO | --- Analysis for data-incubator-moseley took 205.50655126571655s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.044328927993774414s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.00029921531677246094s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 21.04695725440979s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.021208763122558594s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007948875427246094s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 9.72747802734375e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 7.867813110351562e-06s
INFO | --- Analysis for data-incubator-musicbrainz took 79.99799537658691s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.529853343963623s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0007808208465576172s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.28129053115844727s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.021186113357543945s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 9.131431579589844e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 9.775161743164062e-06s
INFO | --- Analysis for data-incubator-nasa took 134.2681601047516s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.08961653709411621s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.3304777145385742s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.023488283157348633s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 2.47955322265625e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0008304119110107422s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 8.821487426757812e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 1.1920928955078125e-05s
INFO | --- Analysis for data-incubator-our-airports took 82.35194492340088s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.04887700080871582s
Availability | VoID file availability check for Pokedex data in RDF took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.2877798080444336s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.02128458023071289s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.846687316894531e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 1.1205673217773438e-05s
INFO | --- Analysis for data-incubator-pokedex took 92.04367542266846s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.04875779151916504s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.3095252513885498s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.020696401596069336s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 9.036064147949219e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 1.2159347534179688e-05s
INFO | --- Analysis for data-incubator-smcjournals took 27.152098894119263s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 0.28850317001342773s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0006198883056640625s
Extra | Recovery of all triples for data.open.ac.uk, Linked Data from the Open University took 25.72041630744934s
Performance | Total latancy measurement for data.open.ac.uk, Linked Data from the Open University took 0.6285431385040283s
Amount of data | Number of triples check for data.open.ac.uk, Linked Data from the Open University took 17.095232486724854s
Interoperability | New terms check for data.open.ac.uk, Linked Data from the Open University took 1.5076072216033936s
Versatility | Languages check for data.open.ac.uk, Linked Data from the Open University took 30.16922378540039s
Interpretability | Number of blank nodes check for data.open.ac.uk, Linked Data from the Open University took 30.153218984603882s
Security | Check HTTPS for data.open.ac.uk, Linked Data from the Open University took 0.25844287872314453s
Interpretability | RDF structures check for data.open.ac.uk, Linked Data from the Open University took 0.25088977813720703s
Versatility | Serialization formats check for data.open.ac.uk, Linked Data from the Open University took 0.4016757011413574s
Availability | RDF dump link check for data.open.ac.uk, Linked Data from the Open University took 0.24639177322387695s
License | MR license check for data.open.ac.uk, Linked Data from the Open University took 0.20967674255371094s
License | HR license check for data.open.ac.uk, Linked Data from the Open University took 30.15937042236328s
Amount of data | Number of property check for data.open.ac.uk, Linked Data from the Open University took 0.42066121101379395s
Understandability | Number of label check for data.open.ac.uk, Linked Data from the Open University took 30.15703248977661s
Understandability | URI regex check for data.open.ac.uk, Linked Data from the Open University took 1.124819040298462s
Understandability | Vocabs check for data.open.ac.uk, Linked Data from the Open University took 0.4423091411590576s
Verifiability | Authors check for data.open.ac.uk, Linked Data from the Open University took 0.7587828636169434s
Verifiability | Publishers check for data.open.ac.uk, Linked Data from the Open University took 0.3735826015472412s
Performance | Throughput check for data.open.ac.uk, Linked Data from the Open University took 12.047752141952515s
Amount of data | Check the number of entities for data.open.ac.uk, Linked Data from the Open University took 7.104873657226562e-05s
Verifiability | Contribs. check for data.open.ac.uk, Linked Data from the Open University took 0.18782329559326172s
Interlinking | sameAs chians check for data.open.ac.uk, Linked Data from the Open University took 0.7041811943054199s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.25900745391845703s
Interlinking | skos check for data.open.ac.uk, Linked Data from the Open University took 0.23789334297180176s
Timeliness | dataset update frequency check for data.open.ac.uk, Linked Data from the Open University took 0.2693955898284912s
Currency | Creation date check for data.open.ac.uk, Linked Data from the Open University took 0.5057852268218994s
Currency | Modification date check for data.open.ac.uk, Linked Data from the Open University took 0.7139017581939697s
Rep.Conc. | URIs length for data.open.ac.uk, Linked Data from the Open University took 33.49097657203674s
Interoperability | New vocabularies check for data.open.ac.uk, Linked Data from the Open University took 69.32746887207031s
Consistency | Deprecated classes/propertiers check for data.open.ac.uk, Linked Data from the Open University took 0.23225879669189453s
Accuracy | Check Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.21650457382202148s
Accuracy | Check Inverse Functional Property for data.open.ac.uk, Linked Data from the Open University took 0.19524073600769043s
Accuracy | Check Empty annotation labels for data.open.ac.uk, Linked Data from the Open University took 34.85131502151489s
Accuracy | Check White space in annotation for data.open.ac.uk, Linked Data from the Open University took 2.9970786571502686s
Accuracy | Check Datatype consistency for data.open.ac.uk, Linked Data from the Open University took 5.226222038269043s
Consistency | Disjoint class check for data.open.ac.uk, Linked Data from the Open University took 0.826242208480835s
Consistency | Check Misplaced properties for data.open.ac.uk, Linked Data from the Open University took 0.66255784034729s
Consistency | Misplaced classes for data.open.ac.uk, Linked Data from the Open University took 8.092061519622803s
Consistency | Check Ontology hijacking for data.open.ac.uk, Linked Data from the Open University took 23.150721788406372s
Consistency | Check Invalid usage of undefined classes for data.open.ac.uk, Linked Data from the Open University took 1.3809216022491455s
Consistency | Check Invalid usage of undefined properties for data.open.ac.uk, Linked Data from the Open University took 1.66062593460083s
Conciseness | Check Extensional conciseness for data.open.ac.uk, Linked Data from the Open University took 2.9186112880706787s
Conciseness | Check Intensional conciseness for data.open.ac.uk, Linked Data from the Open University took 0.3613443374633789s
Security | Sign check for data.open.ac.uk, Linked Data from the Open University took 0.12940621376037598s
Availability | Check URIs Dereferenciability for data.open.ac.uk, Linked Data from the Open University took 13.559282541275024s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 30.742674827575684s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.021747827529907227s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 9.059906005859375e-05s
Interoperability | Check the re-using of existing vocabs for data.open.ac.uk, Linked Data from the Open University took 75.0838258266449s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 1.9788742065429688e-05s
INFO | --- Analysis for data-open-ac-uk took 812.4274363517761s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.7936291694641113s
Availability | VoID file availability check for Persée in RDF took 0.0007588863372802734s
Extra | Recovery of all triples for Persée in RDF took 1.6102826595306396s
Performance | Total latancy measurement for Persée in RDF took 0.6692600250244141s
Amount of data | Number of triples check for Persée in RDF took 0.7424707412719727s
Interoperability | New terms check for Persée in RDF took 1.989222764968872s
Versatility | Languages check for Persée in RDF took 120.89476561546326s
Interpretability | Number of blank nodes check for Persée in RDF took 0.4721698760986328s
Interpretability | RDF structures check for Persée in RDF took 1.0847811698913574s
Versatility | Serialization formats check for Persée in RDF took 1.2743644714355469s
Availability | RDF dump link check for Persée in RDF took 0.33583521842956543s
License | MR license check for Persée in RDF took 1.9980545043945312s
License | HR license check for Persée in RDF took 40.573291301727295s
Amount of data | Number of property check for Persée in RDF took 0.13706445693969727s
Understandability | Number of label check for Persée in RDF took 2.8463802337646484s
Understandability | URI regex check for Persée in RDF took 1.170621633529663s
Understandability | Vocabs check for Persée in RDF took 0.6059055328369141s
Verifiability | Authors check for Persée in RDF took 0.1275629997253418s
Verifiability | Publishers check for Persée in RDF took 0.13637518882751465s
Performance | Throughput check for Persée in RDF took 10.657366514205933s
Amount of data | Check the number of entities for Persée in RDF took 7.367134094238281e-05s
Verifiability | Contribs. check for Persée in RDF took 0.1383371353149414s
Interlinking | sameAs chians check for Persée in RDF took 0.17763996124267578s
Interlinking | skos check for Persée in RDF took 1.015547275543213s
Interlinking | skos check for Persée in RDF took 0.13199591636657715s
Timeliness | dataset update frequency check for Persée in RDF took 0.9966254234313965s
Currency | Creation date check for Persée in RDF took 0.7126317024230957s
Currency | Modification date check for Persée in RDF took 0.25558972358703613s
Rep.Conc. | URIs length for Persée in RDF took 3.6018097400665283s
Interoperability | New vocabularies check for Persée in RDF took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.13445758819580078s
Accuracy | Check Functional Property for Persée in RDF took 0.15874052047729492s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.1364295482635498s
Accuracy | Check Empty annotation labels for Persée in RDF took 0.7241237163543701s
Accuracy | Check White space in annotation for Persée in RDF took 0.04121732711791992s
Accuracy | Check Datatype consistency for Persée in RDF took 0.029903411865234375s
Consistency | Disjoint class check for Persée in RDF took 0.39778733253479004s
Consistency | Check Misplaced properties for Persée in RDF took 2.6331324577331543s
Consistency | Misplaced classes for Persée in RDF took 0.21625852584838867s
Consistency | Check Ontology hijacking for Persée in RDF took 1.9699220657348633s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.3786821365356445s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.8839282989501953s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.032517194747924805s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.13475370407104492s
Security | Sign check for Persée in RDF took 1.075882911682129s
Availability | Check URIs Dereferenciability for Persée in RDF took 1382.097541809082s
Completeness | Calculation of interlinking completeness for Persée in RDF took 25.788029670715332s
Reputation | Calculation of the PageRank for Persée in RDF took 0.022218704223632812s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 8.630752563476562e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.000118255615234375s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 1.6689300537109375e-06s
Believability | Calculation of trust value for Persée in RDF took 1.1682510375976562e-05s
INFO | --- Analysis for data-persee-fr took 1704.4195868968964s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.0876414775848389s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 29.623249053955078s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.021265506744384766s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00013327598571777344s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 1.1920928955078125e-05s
INFO | --- Analysis for data-szepmuveszeti-hu took 175.63078546524048s
Availability | SPARQL endpoint availability check for Open Data Web took 11.52469515800476s
Availability | VoID file availability check for Open Data Web took 0.000690460205078125s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.33867454528808594s
Reputation | Calculation of the PageRank for Open Data Web took 0.02077460289001465s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.3855438232421875e-05s
Believability | Calculation of trust value for Open Data Web took 1.33514404296875e-05s
INFO | --- Analysis for data.odw.tw took 72.87238121032715s
Availability | SPARQL endpoint availability check for DataFAQs took 9.393692016601562e-05s
Availability | VoID file availability check for DataFAQs took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.3056159019470215s
Reputation | Calculation of the PageRank for DataFAQs took 0.026252269744873047s
Interlinking | Calculation of Degree of Connection for DataFAQs took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for DataFAQs took 0.0014157295227050781s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 5.3882598876953125e-05s
Believability | Calculation of trust value for DataFAQs took 1.1920928955078125e-05s
INFO | --- Analysis for datafaqs took 142.16097235679626s
Availability | SPARQL endpoint availability check for datahub took 4.1961669921875e-05s
Availability | VoID file availability check for datahub took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for datahub took 23.871737957000732s
Reputation | Calculation of the PageRank for datahub took 0.02107524871826172s
Interlinking | Calculation of Degree of Connection for datahub took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for datahub took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for datahub took 4.9591064453125e-05s
Believability | Calculation of trust value for datahub took 1.2636184692382812e-05s
INFO | --- Analysis for datahub took 55.843501806259155s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 4.523984909057617s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0007641315460205078s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 25.31648087501526s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.020975589752197266s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.528594970703125e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 1.1682510375976562e-05s
INFO | --- Analysis for datahub-kr-datamap took 139.20224142074585s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.36078429222106934s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.3189687728881836s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.02104353904724121s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0008192062377929688s
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 2.0503997802734375e-05s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 124.71302461624146s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.099989652633667s
Availability | VoID file availability check for datos-artium-org took 0.0007839202880859375s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.3625521659851074s
Reputation | Calculation of the PageRank for datos-artium-org took 0.021666526794433594s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00012636184692382812s
Believability | Calculation of trust value for datos-artium-org took 1.239776611328125e-05s
INFO | --- Analysis for datos-artium-org took 265.18874979019165s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.8174610137939453s
Availability | VoID file availability check for Datos.bcn.cl took 0.0008318424224853516s
Extra | Recovery of all triples for Datos.bcn.cl took 40.66781210899353s
Performance | Total latancy measurement for Datos.bcn.cl took 5.88844108581543s
Amount of data | Number of triples check for Datos.bcn.cl took 4.327064752578735s
Interoperability | New terms check for Datos.bcn.cl took 3.6809394359588623s
Versatility | Languages check for Datos.bcn.cl took 292.8830318450928s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.2414577007293701s
Security | Check HTTPS for Datos.bcn.cl took 0.7340447902679443s
Interpretability | RDF structures check for Datos.bcn.cl took 1.2739169597625732s
Versatility | Serialization formats check for Datos.bcn.cl took 1.1966381072998047s
Availability | RDF dump link check for Datos.bcn.cl took 1.1860926151275635s
License | MR license check for Datos.bcn.cl took 1.219968557357788s
License | HR license check for Datos.bcn.cl took 30.77483057975769s
Amount of data | Number of property check for Datos.bcn.cl took 1.2246785163879395s
Understandability | Number of label check for Datos.bcn.cl took 1.4212427139282227s
Understandability | URI regex check for Datos.bcn.cl took 2.405104160308838s
Understandability | Vocabs check for Datos.bcn.cl took 1.188493251800537s
Verifiability | Authors check for Datos.bcn.cl took 1.204106092453003s
Verifiability | Publishers check for Datos.bcn.cl took 1.1902151107788086s
Performance | Throughput check for Datos.bcn.cl took 13.454463243484497s
Amount of data | Check the number of entities for Datos.bcn.cl took 7.319450378417969e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.194929599761963s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.2065856456756592s
Interlinking | skos check for Datos.bcn.cl took 1.1837184429168701s
Interlinking | skos check for Datos.bcn.cl took 1.187159776687622s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.1791715621948242s
Currency | Creation date check for Datos.bcn.cl took 301.7759051322937s
Currency | Modification date check for Datos.bcn.cl took 1.2614467144012451s
Rep.Conc. | URIs length for Datos.bcn.cl took 32.148555755615234s
Interoperability | New vocabularies check for Datos.bcn.cl took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.1863815784454346s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.1951801776885986s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.1805329322814941s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 20.908059120178223s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.324420690536499s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.27541017532348633s
Consistency | Disjoint class check for Datos.bcn.cl took 1.2136685848236084s
Consistency | Check Misplaced properties for Datos.bcn.cl took 7.630425453186035s
Consistency | Misplaced classes for Datos.bcn.cl took 2.0440797805786133s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 20.500835418701172s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.305621862411499s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 7.231220960617065s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.3032567501068115s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.4220919609069824s
Security | Sign check for Datos.bcn.cl took 1.1872031688690186s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 7394.917533159256s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 0.7456188201904297s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.022312641143798828s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 5.817413330078125e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 0.0002231597900390625s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 2.1457672119140625e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 5.245208740234375e-06s
INFO | --- Analysis for datos-bcn-cl took 8543.4840259552s
Availability | SPARQL endpoint availability check for datos.bne.es took 2.3796443939208984s
Availability | VoID file availability check for datos.bne.es took 0.000644683837890625s
Extra | Recovery of all triples for datos.bne.es took 114.736971616745s
Performance | Total latancy measurement for datos.bne.es took 3.1889562606811523s
Amount of data | Number of triples check for datos.bne.es took 0.8897445201873779s
Interoperability | New terms check for datos.bne.es took 4.177323818206787s
Versatility | Languages check for datos.bne.es took 62.86607313156128s
Interpretability | Number of blank nodes check for datos.bne.es took 0.29001450538635254s
Security | Check HTTPS for datos.bne.es took 0.16652464866638184s
Interpretability | RDF structures check for datos.bne.es took 2.3671817779541016s
Versatility | Serialization formats check for datos.bne.es took 0.5126338005065918s
Availability | RDF dump link check for datos.bne.es took 2.2076520919799805s
License | MR license check for datos.bne.es took 0.6619384288787842s
License | HR license check for datos.bne.es took 61.74212861061096s
Amount of data | Number of property check for datos.bne.es took 0.29743242263793945s
Understandability | Number of label check for datos.bne.es took 0.915003776550293s
Understandability | URI regex check for datos.bne.es took 2.548924446105957s
Understandability | Vocabs check for datos.bne.es took 2.155320405960083s
Verifiability | Authors check for datos.bne.es took 2.3598453998565674s
Verifiability | Publishers check for datos.bne.es took 2.201098680496216s
Performance | Throughput check for datos.bne.es took 24.349647283554077s
Amount of data | Check the number of entities for datos.bne.es took 9.512901306152344e-05s
Verifiability | Contribs. check for datos.bne.es took 2.132446527481079s
Interlinking | sameAs chians check for datos.bne.es took 2.3325936794281006s
Interlinking | skos check for datos.bne.es took 2.4177703857421875s
Interlinking | skos check for datos.bne.es took 0.2751593589782715s
Timeliness | dataset update frequency check for datos.bne.es took 2.311811685562134s
Currency | Creation date check for datos.bne.es took 0.6781294345855713s
Currency | Modification date check for datos.bne.es took 2.407848834991455s
Rep.Conc. | URIs length for datos.bne.es took 55.34428954124451s
Interoperability | New vocabularies check for datos.bne.es took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for datos.bne.es took 0.3176558017730713s
Accuracy | Check Functional Property for datos.bne.es took 4.232574701309204s
Accuracy | Check Inverse Functional Property for datos.bne.es took 2.1687026023864746s
Accuracy | Check Empty annotation labels for datos.bne.es took 41.42417669296265s
Accuracy | Check White space in annotation for datos.bne.es took 1.6317801475524902s
Accuracy | Check Datatype consistency for datos.bne.es took 1.3422632217407227s
Consistency | Disjoint class check for datos.bne.es took 2.2665090560913086s
Consistency | Check Misplaced properties for datos.bne.es took 10.63900876045227s
Consistency | Misplaced classes for datos.bne.es took 4.437190055847168s
Consistency | Check Ontology hijacking for datos.bne.es took 45.353821992874146s
Consistency | Check Invalid usage of undefined classes for datos.bne.es took 1.2939362525939941s
Consistency | Check Invalid usage of undefined properties for datos.bne.es took 11.431150436401367s
Conciseness | Check Extensional conciseness for datos.bne.es took 1.4190220832824707s
Conciseness | Check Intensional conciseness for datos.bne.es took 0.33633875846862793s
Security | Sign check for datos.bne.es took 1.122539758682251s
Availability | Check URIs Dereferenciability for datos.bne.es took 10.105368852615356s
Completeness | Calculation of interlinking completeness for datos.bne.es took 29.66857600212097s
Reputation | Calculation of the PageRank for datos.bne.es took 0.02171015739440918s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011563301086425781s
Interoperability | Check the re-using of existing vocabs for datos.bne.es took 1.9073486328125e-06s
Believability | Calculation of trust value for datos.bne.es took 8.344650268554688e-06s
INFO | --- Analysis for datos-bne-es took 817.2009592056274s
Availability | SPARQL endpoint availability check for dbacademic took 0.04917097091674805s
Availability | VoID file availability check for dbacademic took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for dbacademic took 21.950207471847534s
Reputation | Calculation of the PageRank for dbacademic took 0.02103734016418457s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for dbacademic took 3.981590270996094e-05s
Believability | Calculation of trust value for dbacademic took 9.298324584960938e-06s
INFO | --- Analysis for dbacademic took 75.17962527275085s
Availability | SPARQL endpoint availability check for DBkWik took 0.21549439430236816s
Availability | VoID file availability check for DBkWik took 0.0007042884826660156s
Extra | Recovery of all triples for DBkWik took 1.4310815334320068s
Performance | Total latancy measurement for DBkWik took 0.4493904113769531s
Amount of data | Number of triples check for DBkWik took 4.2942588329315186s
Interoperability | New terms check for DBkWik took 2.1176559925079346s
Versatility | Languages check for DBkWik took 60.32025694847107s
Interpretability | Number of blank nodes check for DBkWik took 0.1368105411529541s
Interpretability | RDF structures check for DBkWik took 0.21321535110473633s
Versatility | Serialization formats check for DBkWik took 0.21170759201049805s
Availability | RDF dump link check for DBkWik took 2.875136613845825s
License | MR license check for DBkWik took 0.3830442428588867s
License | HR license check for DBkWik took 61.79126024246216s
Amount of data | Number of property check for DBkWik took 18.75896167755127s
Understandability | Number of label check for DBkWik took 2.5616068840026855s
Understandability | URI regex check for DBkWik took 0.3211023807525635s
Understandability | Vocabs check for DBkWik took 0.14421606063842773s
Verifiability | Authors check for DBkWik took 0.13218235969543457s
Verifiability | Publishers check for DBkWik took 0.09681367874145508s
Performance | Throughput check for DBkWik took 10.566812515258789s
Amount of data | Check the number of entities for DBkWik took 7.62939453125e-05s
Verifiability | Contribs. check for DBkWik took 0.13030457496643066s
Interlinking | sameAs chians check for DBkWik took 0.4570498466491699s
Interlinking | skos check for DBkWik took 0.5674781799316406s
Interlinking | skos check for DBkWik took 0.08317828178405762s
Timeliness | dataset update frequency check for DBkWik took 0.24631977081298828s
Currency | Creation date check for DBkWik took 0.7581562995910645s
Currency | Modification date check for DBkWik took 0.21558380126953125s
Rep.Conc. | URIs length for DBkWik took 11.323920249938965s
Interoperability | New vocabularies check for DBkWik took 4.600351095199585s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.14566707611083984s
Accuracy | Check Functional Property for DBkWik took 0.34045910835266113s
Accuracy | Check Inverse Functional Property for DBkWik took 0.292142391204834s
Accuracy | Check Empty annotation labels for DBkWik took 0.8202879428863525s
Accuracy | Check White space in annotation for DBkWik took 0.023561716079711914s
Accuracy | Check Datatype consistency for DBkWik took 0.03814339637756348s
Consistency | Disjoint class check for DBkWik took 0.12884020805358887s
Consistency | Check Misplaced properties for DBkWik took 11.657843112945557s
Consistency | Misplaced classes for DBkWik took 0.6169991493225098s
Consistency | Check Ontology hijacking for DBkWik took 1.7269830703735352s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.2375242710113525s
Consistency | Check Invalid usage of undefined properties for DBkWik took 11.515111684799194s
Conciseness | Check Extensional conciseness for DBkWik took 0.03397989273071289s
Conciseness | Check Intensional conciseness for DBkWik took 42.6985981464386s
Security | Sign check for DBkWik took 43.164979219436646s
Availability | Check URIs Dereferenciability for DBkWik took 9.912704706192017s
Completeness | Calculation of interlinking completeness for DBkWik took 31.486153602600098s
Reputation | Calculation of the PageRank for DBkWik took 0.02163529396057129s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for DBkWik took 7.796287536621094e-05s
Interoperability | Check the re-using of existing vocabs for DBkWik took 6.1067955493927s
Believability | Calculation of trust value for DBkWik took 1.0251998901367188e-05s
INFO | --- Analysis for dbkwik took 1497.978441476822s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 8.463859558105469e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 34.30629777908325s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.022723674774169922s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00012159347534179688s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 1.2636184692382812e-05s
INFO | --- Analysis for dblp-deusto-gnoss took 147.4777956008911s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.3123462200164795s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0007417201995849609s
Extra | Recovery of all triples for dblp Knowledge Graph took 6.982572317123413s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.746776819229126s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.14258384704589844s
Interoperability | New terms check for dblp Knowledge Graph took 1.7493896484375s
Versatility | Languages check for dblp Knowledge Graph took 0.1594538688659668s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 7.0404932498931885s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.1556224822998047s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.1631793975830078s
Availability | RDF dump link check for dblp Knowledge Graph took 0.13161063194274902s
License | MR license check for dblp Knowledge Graph took 0.1534595489501953s
License | HR license check for dblp Knowledge Graph took 30.13709545135498s
Amount of data | Number of property check for dblp Knowledge Graph took 0.13344621658325195s
Understandability | Number of label check for dblp Knowledge Graph took 0.399341344833374s
Understandability | URI regex check for dblp Knowledge Graph took 0.2626378536224365s
Understandability | Vocabs check for dblp Knowledge Graph took 0.13651156425476074s
Verifiability | Authors check for dblp Knowledge Graph took 0.14687132835388184s
Verifiability | Publishers check for dblp Knowledge Graph took 0.1370706558227539s
Performance | Throughput check for dblp Knowledge Graph took 10.72784423828125s
Amount of data | Check the number of entities for dblp Knowledge Graph took 0.000110626220703125s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.1380295753479004s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.20698809623718262s
Interlinking | skos check for dblp Knowledge Graph took 0.12792658805847168s
Interlinking | skos check for dblp Knowledge Graph took 0.13311457633972168s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.13744306564331055s
Currency | Creation date check for dblp Knowledge Graph took 0.29016661643981934s
Currency | Modification date check for dblp Knowledge Graph took 0.2720794677734375s
Rep.Conc. | URIs length for dblp Knowledge Graph took 15.43373441696167s
Interoperability | New vocabularies check for dblp Knowledge Graph took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.1392509937286377s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.12729978561401367s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.13615751266479492s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 29.861600160598755s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.1233279705047607s
Accuracy | Check Datatype consistency for dblp Knowledge Graph took 6.3517069816589355s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.13025474548339844s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.270097017288208s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 42.053704261779785s
Consistency | Check Invalid usage of undefined classes for dblp Knowledge Graph took 19859.226693868637s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 5.363996505737305s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 2.7755038738250732s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.15407657623291016s
Security | Sign check for dblp Knowledge Graph took 0.12844061851501465s
Availability | Check URIs Dereferenciability for dblp Knowledge Graph took 11.149883508682251s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 25.49144673347473s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.021881818771362305s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 2.09808349609375e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 1.9073486328125e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 1.3589859008789062e-05s
INFO | --- Analysis for dblp-kg took 20248.500044584274s
Availability | SPARQL endpoint availability check for DBnary took 30.329243659973145s
Availability | VoID file availability check for DBnary took 0.0007643699645996094s
Completeness | Calculation of interlinking completeness for DBnary took 34.16650867462158s
Reputation | Calculation of the PageRank for DBnary took 0.02153325080871582s
Interlinking | Calculation of Degree of Connection for DBnary took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for DBnary took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for DBnary took 5.9604644775390625e-05s
Believability | Calculation of trust value for DBnary took 1.2159347534179688e-05s
INFO | --- Analysis for dbnary took 358.68497705459595s
Availability | SPARQL endpoint availability check for DBpedia took 0.9144670963287354s
Availability | VoID file availability check for DBpedia took 0.8358645439147949s
Extra | Recovery of all triples for DBpedia took 3.0867109298706055s
Performance | Total latancy measurement for DBpedia took 3.567103624343872s
Amount of data | Number of triples check for DBpedia took 1.0050380229949951s
Interoperability | New terms check for DBpedia took 6.006946086883545s
Versatility | Languages check for DBpedia took 31.610053777694702s
Interpretability | Number of blank nodes check for DBpedia took 0.5693995952606201s
Security | Check HTTPS for DBpedia took 0.3493645191192627s
Interpretability | RDF structures check for DBpedia took 0.8013932704925537s
Versatility | Serialization formats check for DBpedia took 0.7028603553771973s
Availability | RDF dump link check for DBpedia took 0.5864608287811279s
License | MR license check for DBpedia took 0.8493525981903076s
License | HR license check for DBpedia took 32.22235918045044s
Amount of data | Number of property check for DBpedia took 0.6210737228393555s
Understandability | Number of label check for DBpedia took 4.686122417449951s
Understandability | URI regex check for DBpedia took 1.1836764812469482s
Understandability | Vocabs check for DBpedia took 0.6769323348999023s
Verifiability | Authors check for DBpedia took 0.7165265083312988s
Verifiability | Publishers check for DBpedia took 0.6012678146362305s
Performance | Throughput check for DBpedia took 11.642621755599976s
Amount of data | Check the number of entities for DBpedia took 7.462501525878906e-05s
Verifiability | Contribs. check for DBpedia took 0.6263771057128906s
Interlinking | sameAs chians check for DBpedia took 2.4282655715942383s
Interlinking | skos check for DBpedia took 0.9560220241546631s
Interlinking | skos check for DBpedia took 0.564486026763916s
Timeliness | dataset update frequency check for DBpedia took 0.7392394542694092s
Currency | Creation date check for DBpedia took 1.3798260688781738s
Currency | Modification date check for DBpedia took 1.255255937576294s
Rep.Conc. | URIs length for DBpedia took 32.98819613456726s
Interoperability | New vocabularies check for DBpedia took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.638526439666748s
Accuracy | Check Functional Property for DBpedia took 0.5990135669708252s
Accuracy | Check Inverse Functional Property for DBpedia took 0.5974202156066895s
Accuracy | Check Empty annotation labels for DBpedia took 2.492872476577759s
Accuracy | Check White space in annotation for DBpedia took 0.030559778213500977s
Accuracy | Check Datatype consistency for DBpedia took 0.0289461612701416s
Consistency | Disjoint class check for DBpedia took 0.5908210277557373s
Consistency | Check Misplaced properties for DBpedia took 32.1746141910553s
Consistency | Misplaced classes for DBpedia took 1.7741291522979736s
Consistency | Check Ontology hijacking for DBpedia took 2.958726167678833s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.2340900897979736s
Consistency | Check Invalid usage of undefined properties for DBpedia took 2.7416038513183594s
Conciseness | Check Extensional conciseness for DBpedia took 0.03334236145019531s
Conciseness | Check Intensional conciseness for DBpedia took 3.5700063705444336s
Security | Sign check for DBpedia took 0.6274142265319824s
Availability | Check URIs Dereferenciability for DBpedia took 4314.055358171463s
Completeness | Calculation of interlinking completeness for DBpedia took 23.900431871414185s
Reputation | Calculation of the PageRank for DBpedia took 0.021941661834716797s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0009417533874511719s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBpedia took 8.58306884765625e-06s
INFO | --- Analysis for dbpedia took 7125.683558940887s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 4.649162292480469e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0006330013275146484s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 29.37462544441223s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.021320819854736328s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 9.870529174804688e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 2.1219253540039062e-05s
INFO | --- Analysis for dbpedia-abstract-corpus took 129.51518774032593s
Availability | SPARQL endpoint availability check for DBpedia Commons took 4.515260457992554s
Availability | VoID file availability check for DBpedia Commons took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.3174877166748047s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.0216677188873291s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0008871555328369141s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 8.416175842285156e-05s
Believability | Calculation of trust value for DBpedia Commons took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-commons took 134.2124729156494s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 0.38205432891845703s
Availability | VoID file availability check for DBpedia in Greek took 0.0003647804260253906s
Extra | Recovery of all triples for DBpedia in Greek took 1.4034247398376465s
Performance | Total latancy measurement for DBpedia in Greek took 1.2111752033233643s
Amount of data | Number of triples check for DBpedia in Greek took 0.28136491775512695s
Interoperability | New terms check for DBpedia in Greek took 1.6700425148010254s
Versatility | Languages check for DBpedia in Greek took 15.600672483444214s
Interpretability | Number of blank nodes check for DBpedia in Greek took 0.24598455429077148s
Security | Check HTTPS for DBpedia in Greek took 0.1319444179534912s
Interpretability | RDF structures check for DBpedia in Greek took 0.3838963508605957s
Versatility | Serialization formats check for DBpedia in Greek took 0.2348039150238037s
Availability | RDF dump link check for DBpedia in Greek took 0.2438664436340332s
License | MR license check for DBpedia in Greek took 0.3431417942047119s
License | HR license check for DBpedia in Greek took 2.718548059463501s
Amount of data | Number of property check for DBpedia in Greek took 0.26147937774658203s
Understandability | Number of label check for DBpedia in Greek took 0.4615330696105957s
Understandability | URI regex check for DBpedia in Greek took 0.5158665180206299s
Understandability | Vocabs check for DBpedia in Greek took 0.226226806640625s
Verifiability | Authors check for DBpedia in Greek took 0.27681517601013184s
Verifiability | Publishers check for DBpedia in Greek took 0.27258992195129395s
Performance | Throughput check for DBpedia in Greek took 11.888620853424072s
Amount of data | Check the number of entities for DBpedia in Greek took 8.344650268554688e-05s
Verifiability | Contribs. check for DBpedia in Greek took 0.2263638973236084s
Interlinking | sameAs chians check for DBpedia in Greek took 0.23798871040344238s
Interlinking | skos check for DBpedia in Greek took 0.24040818214416504s
Interlinking | skos check for DBpedia in Greek took 0.41706275939941406s
Timeliness | dataset update frequency check for DBpedia in Greek took 0.24998807907104492s
Currency | Creation date check for DBpedia in Greek took 0.5533099174499512s
Currency | Modification date check for DBpedia in Greek took 0.550234317779541s
Rep.Conc. | URIs length for DBpedia in Greek took 1.7493705749511719s
Interoperability | New vocabularies check for DBpedia in Greek took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Greek took 0.22403812408447266s
Accuracy | Check Functional Property for DBpedia in Greek took 0.2544398307800293s
Accuracy | Check Inverse Functional Property for DBpedia in Greek took 0.26335668563842773s
Accuracy | Check Empty annotation labels for DBpedia in Greek took 0.7586069107055664s
Accuracy | Check White space in annotation for DBpedia in Greek took 0.03225588798522949s
Accuracy | Check Datatype consistency for DBpedia in Greek took 0.030802488327026367s
Consistency | Disjoint class check for DBpedia in Greek took 0.3026716709136963s
Consistency | Check Misplaced properties for DBpedia in Greek took 1.3698451519012451s
Consistency | Misplaced classes for DBpedia in Greek took 0.7309906482696533s
Consistency | Check Ontology hijacking for DBpedia in Greek took 1.913463830947876s
Consistency | Check Invalid usage of undefined classes for DBpedia in Greek took 1.2358417510986328s
Consistency | Check Invalid usage of undefined properties for DBpedia in Greek took 2.2097082138061523s
Conciseness | Check Extensional conciseness for DBpedia in Greek took 0.03523898124694824s
Conciseness | Check Intensional conciseness for DBpedia in Greek took 0.785597562789917s
Security | Sign check for DBpedia in Greek took 0.24718093872070312s
Availability | Check URIs Dereferenciability for DBpedia in Greek took 2153.3686978816986s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 1.0044889450073242s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.021709442138671875s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00026416778564453125s
Interoperability | Check the re-using of existing vocabs for DBpedia in Greek took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia in Greek took 9.059906005859375e-06s
INFO | --- Analysis for dbpedia-el took 2408.2511897087097s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.6346759796142578s
Availability | VoID file availability check for DBpedia in Spanish took 0.0006525516510009766s
Extra | Recovery of all triples for DBpedia in Spanish took 1.8982908725738525s
Performance | Total latancy measurement for DBpedia in Spanish took 1.391089916229248s
Amount of data | Number of triples check for DBpedia in Spanish took 0.9040486812591553s
Interoperability | New terms check for DBpedia in Spanish took 2.8658037185668945s
Versatility | Languages check for DBpedia in Spanish took 62.11371350288391s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.4559483528137207s
Security | Check HTTPS for DBpedia in Spanish took 0.15350961685180664s
Interpretability | RDF structures check for DBpedia in Spanish took 0.9289371967315674s
Versatility | Serialization formats check for DBpedia in Spanish took 0.5537395477294922s
Availability | RDF dump link check for DBpedia in Spanish took 0.4586644172668457s
License | MR license check for DBpedia in Spanish took 0.698448657989502s
License | HR license check for DBpedia in Spanish took 61.492887020111084s
Amount of data | Number of property check for DBpedia in Spanish took 0.3868422508239746s
Understandability | Number of label check for DBpedia in Spanish took 1.4515159130096436s
Understandability | URI regex check for DBpedia in Spanish took 0.9473421573638916s
Understandability | Vocabs check for DBpedia in Spanish took 0.44487428665161133s
Verifiability | Authors check for DBpedia in Spanish took 0.3842179775238037s
Verifiability | Publishers check for DBpedia in Spanish took 0.37368273735046387s
Performance | Throughput check for DBpedia in Spanish took 11.428608179092407s
Amount of data | Check the number of entities for DBpedia in Spanish took 8.416175842285156e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 0.3775811195373535s
Interlinking | sameAs chians check for DBpedia in Spanish took 0.6940627098083496s
Interlinking | skos check for DBpedia in Spanish took 0.7462906837463379s
Interlinking | skos check for DBpedia in Spanish took 0.25071239471435547s
Timeliness | dataset update frequency check for DBpedia in Spanish took 0.5408191680908203s
Currency | Creation date check for DBpedia in Spanish took 0.7648673057556152s
Currency | Modification date check for DBpedia in Spanish took 0.7562766075134277s
Rep.Conc. | URIs length for DBpedia in Spanish took 7.1722731590271s
Interoperability | New vocabularies check for DBpedia in Spanish took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 0.3751366138458252s
Accuracy | Check Functional Property for DBpedia in Spanish took 0.5136468410491943s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 0.522676944732666s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 1.0015249252319336s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.031075716018676758s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.034221649169921875s
Consistency | Disjoint class check for DBpedia in Spanish took 0.3763551712036133s
Consistency | Check Misplaced properties for DBpedia in Spanish took 7.833752870559692s
Consistency | Misplaced classes for DBpedia in Spanish took 1.365546703338623s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 2.1842472553253174s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.2273139953613281s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 6.5632617473602295s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.03388500213623047s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 1.0352251529693604s
Security | Sign check for DBpedia in Spanish took 0.40604233741760254s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 3.1300623416900635s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 34.50559639930725s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.021746158599853516s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00012969970703125s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia in Spanish took 9.059906005859375e-06s
INFO | --- Analysis for dbpedia-es took 2577.305363893509s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.2693076133728027s
Availability | VoID file availability check for DBpedia in Basque took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.3065197467803955s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.02191781997680664s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.814697265625e-05s
Believability | Calculation of trust value for DBpedia in Basque took 9.059906005859375e-06s
INFO | --- Analysis for dbpedia-eu took 152.6957607269287s
Availability | SPARQL endpoint availability check for DBpedia in French took 0.16463613510131836s
Availability | VoID file availability check for DBpedia in French took 0.0004506111145019531s
Extra | Recovery of all triples for DBpedia in French took 224.2546398639679s
Performance | Total latancy measurement for DBpedia in French took 0.4032747745513916s
Amount of data | Number of triples check for DBpedia in French took 5.930164337158203s
Interoperability | New terms check for DBpedia in French took 5.619210481643677s
Versatility | Languages check for DBpedia in French took 300.1033043861389s
Interpretability | Number of blank nodes check for DBpedia in French took 3.890450954437256s
Security | Check HTTPS for DBpedia in French took 0.2000732421875s
Interpretability | RDF structures check for DBpedia in French took 0.6885755062103271s
Versatility | Serialization formats check for DBpedia in French took 0.5464589595794678s
Availability | RDF dump link check for DBpedia in French took 7.512969255447388s
License | MR license check for DBpedia in French took 1.9962291717529297s
License | HR license check for DBpedia in French took 300.1037883758545s
Amount of data | Number of property check for DBpedia in French took 3.154937982559204s
Understandability | Number of label check for DBpedia in French took 16.109511375427246s
Understandability | URI regex check for DBpedia in French took 4.488248825073242s
Understandability | Vocabs check for DBpedia in French took 7.967655897140503s
Verifiability | Authors check for DBpedia in French took 1.3275644779205322s
Verifiability | Publishers check for DBpedia in French took 0.4248182773590088s
Performance | Throughput check for DBpedia in French took 21.043586492538452s
Amount of data | Check the number of entities for DBpedia in French took 2.330803871154785s
Verifiability | Contribs. check for DBpedia in French took 0.1453564167022705s
Interlinking | sameAs chians check for DBpedia in French took 4.398409366607666s
Interlinking | skos check for DBpedia in French took 0.21157264709472656s
Interlinking | skos check for DBpedia in French took 0.09199833869934082s
Timeliness | dataset update frequency check for DBpedia in French took 0.3132450580596924s
Currency | Creation date check for DBpedia in French took 0.40341949462890625s
Currency | Modification date check for DBpedia in French took 1.1917507648468018s
Rep.Conc. | URIs length for DBpedia in French took 195.4989321231842s
Interoperability | New vocabularies check for DBpedia in French took 10.7391836643219s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 0.13942217826843262s
Accuracy | Check Functional Property for DBpedia in French took 0.15534043312072754s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.11211013793945312s
Accuracy | Check Empty annotation labels for DBpedia in French took 29.750094652175903s
Accuracy | Check White space in annotation for DBpedia in French took 3.104989528656006s
Accuracy | Check Datatype consistency for DBpedia in French took 2.6934399604797363s
Consistency | Disjoint class check for DBpedia in French took 0.19871211051940918s
Consistency | Check Misplaced properties for DBpedia in French took 7.8769214153289795s
Consistency | Misplaced classes for DBpedia in French took 10.130529642105103s
Consistency | Check Ontology hijacking for DBpedia in French took 25.587592124938965s
Consistency | Check Invalid usage of undefined classes for DBpedia in French took 1.3854780197143555s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 7.517738342285156s
Conciseness | Check Extensional conciseness for DBpedia in French took 3.0879597663879395s
Conciseness | Check Intensional conciseness for DBpedia in French took 2.0103933811187744s
Security | Sign check for DBpedia in French took 0.11784029006958008s
Availability | Check URIs Dereferenciability for DBpedia in French took 3154.6885194778442s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.7664251327514648s
Reputation | Calculation of the PageRank for DBpedia in French took 0.023101329803466797s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 7.176399230957031e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.00010418891906738281s
Interoperability | Check the re-using of existing vocabs for DBpedia in French took 7.855145454406738s
Believability | Calculation of trust value for DBpedia in French took 9.5367431640625e-06s
INFO | --- Analysis for dbpedia-fr took 5120.338364601135s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.9070625305175781s
Availability | VoID file availability check for DBpedia in Japanese took 3.9550440311431885s
Extra | Recovery of all triples for DBpedia in Japanese took 5.538574934005737s
Performance | Total latancy measurement for DBpedia in Japanese took 6.651065111160278s
Amount of data | Number of triples check for DBpedia in Japanese took 88.09020662307739s
Interoperability | New terms check for DBpedia in Japanese took 21.37791919708252s
Versatility | Languages check for DBpedia in Japanese took 1.3239691257476807s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.3310737609863281s
Security | Check HTTPS for DBpedia in Japanese took 0.8106660842895508s
Interpretability | RDF structures check for DBpedia in Japanese took 1.3818297386169434s
Versatility | Serialization formats check for DBpedia in Japanese took 1.3602051734924316s
Availability | RDF dump link check for DBpedia in Japanese took 1.324228286743164s
License | MR license check for DBpedia in Japanese took 1.7294330596923828s
License | HR license check for DBpedia in Japanese took 121.33395981788635s
Amount of data | Number of property check for DBpedia in Japanese took 1.3514580726623535s
Understandability | Number of label check for DBpedia in Japanese took 8.391104936599731s
Understandability | URI regex check for DBpedia in Japanese took 2.850395679473877s
Understandability | Vocabs check for DBpedia in Japanese took 1.479832410812378s
Verifiability | Authors check for DBpedia in Japanese took 1.3438689708709717s
Verifiability | Publishers check for DBpedia in Japanese took 1.3330669403076172s
Performance | Throughput check for DBpedia in Japanese took 13.279843807220459s
Amount of data | Check the number of entities for DBpedia in Japanese took 7.271766662597656e-05s
Verifiability | Contribs. check for DBpedia in Japanese took 1.3303422927856445s
Interlinking | sameAs chians check for DBpedia in Japanese took 3.6122617721557617s
Interlinking | skos check for DBpedia in Japanese took 2.2096071243286133s
Interlinking | skos check for DBpedia in Japanese took 1.3234164714813232s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.366772174835205s
Currency | Creation date check for DBpedia in Japanese took 2.8592920303344727s
Currency | Modification date check for DBpedia in Japanese took 2.6766419410705566s
Rep.Conc. | URIs length for DBpedia in Japanese took 138.7408425807953s
Interoperability | New vocabularies check for DBpedia in Japanese took 5.0067901611328125e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.3283443450927734s
Accuracy | Check Functional Property for DBpedia in Japanese took 1.3480720520019531s
Accuracy | Check Inverse Functional Property for DBpedia in Japanese took 1.3636786937713623s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 3.1907029151916504s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.02630305290222168s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.02942061424255371s
Consistency | Disjoint class check for DBpedia in Japanese took 1.4823520183563232s
Consistency | Check Misplaced properties for DBpedia in Japanese took 122.68680334091187s
Consistency | Misplaced classes for DBpedia in Japanese took 3.0145580768585205s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 4.344303846359253s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.4020109176635742s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 122.7757408618927s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.035027265548706055s
Conciseness | Check Intensional conciseness for DBpedia in Japanese took 3.2167108058929443s
Security | Sign check for DBpedia in Japanese took 1.3599820137023926s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 9.148452997207642s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.38222193717956543s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.02137136459350586s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007827281951904297s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00011181831359863281s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 2.384185791015625e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 9.298324584960938e-06s
INFO | --- Analysis for dbpedia-ja took 1399.109209060669s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.6253204345703125e-05s
Availability | VoID file availability check for dbpedia lite took 0.0006859302520751953s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.41693925857543945s
Reputation | Calculation of the PageRank for dbpedia lite took 0.02152085304260254s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.00010991096496582031s
Believability | Calculation of trust value for dbpedia lite took 5.9604644775390625e-06s
INFO | --- Analysis for dbpedia-lite took 91.41583943367004s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.23841452598571777s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.34957027435302734s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.021106243133544922s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.0001742839813232422s
Believability | Calculation of trust value for DBpedia in Dutch took 3.0994415283203125e-05s
INFO | --- Analysis for dbpedia-nl took 90.38945245742798s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 5.312736988067627s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 32.481035232543945s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.02174997329711914s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.511543273925781e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-pt took 190.81513619422913s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.482269287109375e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0023169517517089844s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.40274691581726074s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.1744844913482666s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 6.127357482910156e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0067996978759765625s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 0.00048065185546875s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 1.1682510375976562e-05s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 101.45006012916565s
Availability | SPARQL endpoint availability check for DBTropes took 8.916854858398438e-05s
Availability | VoID file availability check for DBTropes took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for DBTropes took 28.47116255760193s
Reputation | Calculation of the PageRank for DBTropes took 0.020856618881225586s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0008285045623779297s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.703636169433594e-05s
Believability | Calculation of trust value for DBTropes took 1.3828277587890625e-05s
INFO | --- Analysis for dbtropes took 140.68765783309937s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 8.749961853027344e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 28.17095184326172s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.17235302925109863s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 5.602836608886719e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0062103271484375s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 0.00036454200744628906s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 4.00543212890625e-05s
INFO | --- Analysis for dbtune-artists-last-fm took 112.91288328170776s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 8.678436279296875e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.3302464485168457s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.02194523811340332s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 5.7697296142578125e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 1.1682510375976562e-05s
INFO | --- Analysis for dbtune-audioscrobbler took 82.23827457427979s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 5.84099817276001s
Availability | VoID file availability check for DBTune.org/classical took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.38126635551452637s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.020850181579589844s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.486343383789062e-05s
Believability | Calculation of trust value for DBTune.org/classical took 1.6927719116210938e-05s
INFO | --- Analysis for dbtune-classical took 174.58619499206543s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 0.4669516086578369s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.32828521728515625s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.021203994750976562s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 7.796287536621094e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 1.1920928955078125e-05s
INFO | --- Analysis for dbtune-john-peel-sessions took 140.08357548713684s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 0.27448201179504395s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.2941606044769287s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.02121257781982422s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 7.081031799316406e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 1.1444091796875e-05s
INFO | --- Analysis for dbtune-magnatune took 164.8288025856018s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 180.4208836555481s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0008547306060791016s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 29.334277868270874s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.03037428855895996s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0008685588836669922s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.0001361370086669922s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 1.239776611328125e-05s
INFO | --- Analysis for dbtune-musicbrainz took 637.5394718647003s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 0.35904979705810547s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0006833076477050781s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 26.76061511039734s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.02135324478149414s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 6.461143493652344e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 1.1682510375976562e-05s
INFO | --- Analysis for dbtune-myspace took 176.3696506023407s
Availability | SPARQL endpoint availability check for data.dcs took 9.512901306152344e-05s
Availability | VoID file availability check for data.dcs took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for data.dcs took 30.985435009002686s
Reputation | Calculation of the PageRank for data.dcs took 0.022799968719482422s
Interlinking | Calculation of Degree of Connection for data.dcs took 3.075599670410156e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.001584768295288086s
Interlinking | Calculation of Clustering coefficient for data.dcs took 0.0001347064971923828s
Believability | Calculation of trust value for data.dcs took 1.1920928955078125e-05s
INFO | --- Analysis for dcs-sheffield took 181.48579359054565s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 9.107589721679688e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0008435249328613281s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 24.778289079666138s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.02137446403503418s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0008327960968017578s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 4.839897155761719e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 1.0728836059570312e-05s
INFO | --- Analysis for de-gaap-ontology-lexicon took 141.84142208099365s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 4.6253204345703125e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0006814002990722656s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 25.335551500320435s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.021367788314819336s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 5.4836273193359375e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 1.2159347534179688e-05s
INFO | --- Analysis for debian-package-tracking-system took 146.99372458457947s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 8.440017700195312e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0005872249603271484s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.322831392288208s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.02246713638305664s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 3.8623809814453125e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.2636184692382812e-05s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 179.06578135490417s
Availability | SPARQL endpoint availability check for Demografie took 8.678436279296875e-05s
Availability | VoID file availability check for Demografie took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for Demografie took 29.910821676254272s
Reputation | Calculation of the PageRank for Demografie took 0.02267932891845703s
Interlinking | Calculation of Degree of Connection for Demografie took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Demografie took 3.337860107421875e-05s
Believability | Calculation of trust value for Demografie took 1.1920928955078125e-05s
INFO | --- Analysis for demografie took 240.40185070037842s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 0.5185775756835938s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.4082305431365967s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.025564193725585938s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0014476776123046875s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 4.124641418457031e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 1.049041748046875e-05s
INFO | --- Analysis for desaparecidos took 178.50782895088196s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 8.7738037109375e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.385575532913208s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.022529125213623047s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 2.9325485229492188e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0010704994201660156s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 0.00013518333435058594s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 1.239776611328125e-05s
INFO | --- Analysis for deustoentrepreneurship took 129.48715329170227s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 8.869171142578125e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 1.8795859813690186s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 29.12759041786194s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.02298283576965332s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00011777877807617188s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 1.2636184692382812e-05s
INFO | --- Analysis for deustotech took 119.16960859298706s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 2.682739019393921s
Availability | VoID file availability check for Deutsche Biographie took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 28.699207305908203s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.021417617797851562s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 4.57763671875e-05s
Believability | Calculation of trust value for Deutsche Biographie took 1.1682510375976562e-05s
INFO | --- Analysis for deutsche-biographie took 182.40900683403015s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 0.00011706352233886719s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0004208087921142578s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 29.41610836982727s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.021630048751831055s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0008690357208251953s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 7.033348083496094e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 1.621246337890625e-05s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 152.96789073944092s
Availability | SPARQL endpoint availability check for dev8d took 0.00012350082397460938s
Availability | VoID file availability check for dev8d took 0.0006952285766601562s
Completeness | Calculation of interlinking completeness for dev8d took 29.054876804351807s
Reputation | Calculation of the PageRank for dev8d took 0.02095198631286621s
Interlinking | Calculation of Degree of Connection for dev8d took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for dev8d took 7.414817810058594e-05s
Believability | Calculation of trust value for dev8d took 1.1920928955078125e-05s
INFO | --- Analysis for dev8d took 118.39864826202393s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.15523672103882s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.001153707504272461s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 23.940433025360107s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.022968053817749023s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 7.724761962890625e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 7.867813110351562e-06s
INFO | --- Analysis for dewey_decimal_classification took 262.16058015823364s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 4.1484832763671875e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 28.016961336135864s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.02123713493347168s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.4809112548828125e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 1.5735626220703125e-05s
INFO | --- Analysis for DHSVM took 182.67548298835754s
Availability | SPARQL endpoint availability check for Diavgeia took 0.9207537174224854s
Availability | VoID file availability check for Diavgeia took 0.0006277561187744141s
Completeness | Calculation of interlinking completeness for Diavgeia took 28.495609283447266s
Reputation | Calculation of the PageRank for Diavgeia took 0.021024227142333984s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.726119995117188e-05s
Believability | Calculation of trust value for Diavgeia took 8.58306884765625e-06s
INFO | --- Analysis for diavgeia took 125.41143989562988s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011873245239257812s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0008332729339599609s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.33316540718078613s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.021373510360717773s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 2.574920654296875e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0001304149627685547s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 7.867813110351562e-06s
INFO | --- Analysis for didactalia took 185.34734559059143s
Availability | SPARQL endpoint availability check for DisGeNET took 2.1353085041046143s
Availability | VoID file availability check for DisGeNET took 0.0007345676422119141s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.44022130966186523s
Reputation | Calculation of the PageRank for DisGeNET took 0.021032333374023438s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00016641616821289062s
Believability | Calculation of trust value for DisGeNET took 1.2159347534179688e-05s
INFO | --- Analysis for disgenet took 150.54906368255615s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 8.797645568847656e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.42097926139831543s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.022670745849609375s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 3.4332275390625e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 7.3909759521484375e-06s
INFO | --- Analysis for distritos-zaragoza took 120.161780834198s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 0.00010609626770019531s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0008087158203125s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 28.402872800827026s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.02103877067565918s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.886222839355469e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 1.2874603271484375e-05s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 119.11032795906067s
Availability | SPARQL endpoint availability check for DM2E took 8.797645568847656e-05s
Availability | VoID file availability check for DM2E took 0.0007555484771728516s
Completeness | Calculation of interlinking completeness for DM2E took 25.71073317527771s
Reputation | Calculation of the PageRank for DM2E took 0.02331089973449707s
Interlinking | Calculation of Degree of Connection for DM2E took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00012183189392089844s
Believability | Calculation of trust value for DM2E took 1.1205673217773438e-05s
INFO | --- Analysis for dm2e took 200.94934558868408s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 0.00010371208190917969s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 29.298092126846313s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.03292441368103027s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 2.5987625122070312e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.001374959945678711s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.0002486705780029297s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 1.1920928955078125e-05s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 216.5982527732849s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 8.678436279296875e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 25.635172605514526s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.021252155303955078s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 0.00011348724365234375s
Believability | Calculation of trust value for CrossRef DOI Resolver took 8.821487426757812e-06s
INFO | --- Analysis for doi took 143.9803078174591s
Availability | SPARQL endpoint availability check for Driggu Florentino took 4.9114227294921875e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.3176107406616211s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.020958900451660156s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 4.00543212890625e-05s
Believability | Calculation of trust value for Driggu Florentino took 1.1205673217773438e-05s
INFO | --- Analysis for Driggu took 63.01059126853943s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 1.1759212017059326s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0006189346313476562s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 27.84011197090149s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.02125072479248047s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007925033569335938s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 5.5789947509765625e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 1.1444091796875e-05s
INFO | --- Analysis for drug-data-hifm took 216.09132409095764s
Availability | SPARQL endpoint availability check for dspace took 9.417533874511719e-05s
Availability | VoID file availability check for dspace took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for dspace took 0.32338690757751465s
Reputation | Calculation of the PageRank for dspace took 0.021254777908325195s
Interlinking | Calculation of Degree of Connection for dspace took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for dspace took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for dspace took 3.5762786865234375e-05s
Believability | Calculation of trust value for dspace took 1.3589859008789062e-05s
INFO | --- Analysis for dspace took 143.3042995929718s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 272.34768080711365s
Availability | VoID file availability check for MetaLex Document Server took 0.0007219314575195312s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.3751952648162842s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.021928071975708008s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 4.9114227294921875e-05s
Believability | Calculation of trust value for MetaLex Document Server took 6.9141387939453125e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 801.7134392261505s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 1.5342905521392822s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0007321834564208984s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 26.804402589797974s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.02172708511352539s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 4.4345855712890625e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 7.3909759521484375e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 125.02292561531067s
Availability | SPARQL endpoint availability check for DWS-Group took 8.559226989746094e-05s
Availability | VoID file availability check for DWS-Group took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for DWS-Group took 29.239213943481445s
Reputation | Calculation of the PageRank for DWS-Group took 0.02135467529296875s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.0001087188720703125s
Believability | Calculation of trust value for DWS-Group took 1.2159347534179688e-05s
INFO | --- Analysis for dws-group took 192.60872173309326s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 8.749961853027344e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.33775925636291504s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.02113962173461914s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 3.361701965332031e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 1.1920928955078125e-05s
INFO | --- Analysis for E1 took 148.3186435699463s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 30.119224071502686s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0007226467132568359s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 29.772646188735962s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.027330398559570312s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.0001342296600341797s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-alaska took 245.40120768547058s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 30.17992877960205s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0008690357208251953s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.3703181743621826s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.02281928062438965s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.817413330078125e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-cau took 223.63902139663696s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 30.190658569335938s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.0008296966552734375s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.34003591537475586s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.021101713180541992s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 7.82012939453125e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-ccny-cuny took 234.02897596359253s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 30.23131513595581s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0007059574127197266s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 24.40710425376892s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.021437644958496094s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 0.00012445449829101562s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-cdrewu took 252.7437162399292s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 30.034122705459595s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.3587932586669922s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.0209958553314209s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00015163421630859375s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-dartmouth took 145.32540893554688s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 30.12227511405945s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0008337497711181641s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 28.684441804885864s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.022054672241210938s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 0.00010585784912109375s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-famu took 261.4362473487854s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.0623776912689209s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.000400543212890625s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.2882537841796875s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.02140069007873535s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007877349853515625s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00014138221740722656s
Believability | Calculation of trust value for eagle-i @ Harvard University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-harvard took 139.97824954986572s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 30.166300296783447s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0006451606750488281s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 27.857088565826416s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.023094892501831055s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0008158683776855469s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00015282630920410156s
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 172.9851896762848s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 30.216492652893066s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0009546279907226562s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 25.090147018432617s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.021154165267944336s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007984638214111328s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.961822509765625e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-howard took 200.04187512397766s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 30.12687110900879s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.000713348388671875s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.41494274139404297s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.021279335021972656s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.914138793945312e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-hunter-cuny took 321.72429895401s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 30.15306520462036s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.0007994174957275391s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.35962963104248047s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.021801233291625977s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.0001506805419921875s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-jsu took 299.73652029037476s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 30.133694171905518s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.0008232593536376953s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 29.22765278816223s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.02279376983642578s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 4.863739013671875e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-meharry took 304.341331243515s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 30.15540361404419s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0007989406585693359s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 29.96328330039978s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.021362781524658203s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 0.0001251697540283203s
Believability | Calculation of trust value for eagle-i @ Montana State University took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-montana took 313.44176149368286s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 30.21522808074951s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0007333755493164062s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 31.47252345085144s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.021042346954345703s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.942054748535156e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 1.1444091796875e-05s
INFO | --- Analysis for eagle-i-msm took 269.7285475730896s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 30.03860068321228s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0007123947143554688s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 29.537835121154785s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.02107524871826172s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00014090538024902344s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 1.33514404296875e-05s
INFO | --- Analysis for eagle-i-ohsu took 198.5423641204834s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 30.126587867736816s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0008029937744140625s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.3905973434448242s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.0212247371673584s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 8.678436279296875e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-psm took 268.9376790523529s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 30.138959646224976s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.000926971435546875s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 26.242544651031494s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.02192544937133789s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0008139610290527344s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 9.012222290039062e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-tsu took 269.2428948879242s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 30.0709388256073s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0008883476257324219s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.2943603992462158s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.021664857864379883s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 7.414817810058594e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-tuskegee took 265.02884554862976s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 30.17495346069336s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0007128715515136719s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 26.91946029663086s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.023031234741210938s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.00012803077697753906s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 1.2874603271484375e-05s
INFO | --- Analysis for eagle-i-uccaribe took 253.0355417728424s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 30.20069932937622s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007569789886474609s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 26.728016138076782s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.02525496482849121s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0008563995361328125s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00014281272888183594s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-upr took 330.3510570526123s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 30.07325553894043s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.0007081031799316406s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 27.91488242149353s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.021281003952026367s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 7.224082946777344e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-utep took 236.6361644268036s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 30.130484342575073s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0007126331329345703s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.3360137939453125s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.021018505096435547s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 7.557868957519531e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-utsa took 155.3312110900879s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.16006207466125488s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.30176472663879395s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.02065300941467285s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.441375732421875e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 1.3113021850585938e-05s
INFO | --- Analysis for eagle-i-vanderbilt took 120.8310034275055s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 30.079077005386353s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.5529825687408447s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.02142953872680664s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.891654968261719e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-xula took 332.8242275714874s
Availability | SPARQL endpoint availability check for Emergency situation took 0.6517434120178223s
Availability | VoID file availability check for Emergency situation took 0.0007588863372802734s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.3054485321044922s
Reputation | Calculation of the PageRank for Emergency situation took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 5.698204040527344e-05s
Believability | Calculation of trust value for Emergency situation took 7.3909759521484375e-06s
INFO | --- Analysis for Earthquake took 87.98845291137695s
Availability | SPARQL endpoint availability check for ESO took 0.5117499828338623s
Availability | VoID file availability check for ESO took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for ESO took 31.60367202758789s
Reputation | Calculation of the PageRank for ESO took 0.020969152450561523s
Interlinking | Calculation of Degree of Connection for ESO took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for ESO took 9.083747863769531e-05s
Believability | Calculation of trust value for ESO took 2.002716064453125e-05s
INFO | --- Analysis for Earthquake_case took 149.48651432991028s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.11762142181396484s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.2843761444091797s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.02116537094116211s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00011444091796875s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for ecb-linked-data took 148.1736946105957s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 5.91400671005249s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0007178783416748047s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 26.907552480697632s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.02097320556640625s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 4.3392181396484375e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 5.4836273193359375e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 178.44998407363892s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.5812604427337646s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007393360137939453s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 23.583297729492188s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.02141547203063965s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 8.082389831542969e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 1.71661376953125e-05s
INFO | --- Analysis for ecco-tcp-linked-data took 203.1289026737213s
Availability | SPARQL endpoint availability check for ECLAP took 20.239466428756714s
Availability | VoID file availability check for ECLAP took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for ECLAP took 0.36545610427856445s
Reputation | Calculation of the PageRank for ECLAP took 0.021085739135742188s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for ECLAP took 4.363059997558594e-05s
Believability | Calculation of trust value for ECLAP took 1.2159347534179688e-05s
INFO | --- Analysis for eclap took 114.11621141433716s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 9.179115295410156e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 26.35975694656372s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.021366596221923828s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.4066696166992188e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 1.2636184692382812e-05s
INFO | --- Analysis for ECNU-GISer took 215.00385427474976s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 9.059906005859375e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 26.093122482299805s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.021498680114746094s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 7.963180541992188e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.0967254638671875e-05s
INFO | --- Analysis for ecs took 208.48351955413818s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 0.00012373924255371094s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 29.52442717552185s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.021270751953125s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 3.337860107421875e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 1.239776611328125e-05s
INFO | --- Analysis for edificios-historicos-zaragoza took 181.15500020980835s
Availability | SPARQL endpoint availability check for Edublogs took 0.00010061264038085938s
Availability | VoID file availability check for Edublogs took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for Edublogs took 24.4201078414917s
Reputation | Calculation of the PageRank for Edublogs took 0.021605253219604492s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.00010728836059570312s
Believability | Calculation of trust value for Edublogs took 1.1920928955078125e-05s
INFO | --- Analysis for edublogs took 153.73452806472778s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.4818384647369385s
Availability | VoID file availability check for education.data.gov.uk took 0.0006427764892578125s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.29184818267822266s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.02099752426147461s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 9.918212890625e-05s
Believability | Calculation of trust value for education.data.gov.uk took 9.5367431640625e-06s
INFO | --- Analysis for education-data-gov-uk took 118.46765494346619s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 393.33165407180786s
Availability | VoID file availability check for Educational programs - SISVU took 0.0008826255798339844s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.3637881278991699s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.021606922149658203s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 5.459785461425781e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 1.2874603271484375e-05s
INFO | --- Analysis for educationalprograms_sisvu took 1561.3677752017975s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 1.227522850036621s
Availability | VoID file availability check for European Environment Agency Published Products took 0.002187013626098633s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 30.387075424194336s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.17454743385314941s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 6.532669067382812e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.00673222541809082s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 0.00026702880859375s
Believability | Calculation of trust value for European Environment Agency Published Products took 2.2411346435546875e-05s
INFO | --- Analysis for eea took 173.07299375534058s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.5512945652008057s
Availability | VoID file availability check for EEA Reporting Obligations Database took 1.0722780227661133s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.45645618438720703s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.17539095878601074s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 6.723403930664062e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.006853580474853516s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 0.0003848075866699219s
Interoperability | Check the re-using of existing vocabs for EEA Reporting Obligations Database took 4.524747133255005s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 3.0994415283203125e-05s
INFO | --- Analysis for eea-rod took 185.27117037773132s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.33261728286743164s
Availability | VoID file availability check for EEA Vocabularies took 0.0023152828216552734s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 32.89224433898926s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.16977286338806152s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 6.031990051269531e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.006241321563720703s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 0.0006806850433349609s
Believability | Calculation of trust value for EEA Vocabularies took 3.5762786865234375e-05s
INFO | --- Analysis for eea-vocabularies took 101.37674760818481s
Availability | SPARQL endpoint availability check for E-Government Ontology took 1.8745536804199219s
Availability | VoID file availability check for E-Government Ontology took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 30.842321395874023s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.020888805389404297s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 2.6464462280273438e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 3.790855407714844e-05s
Believability | Calculation of trust value for E-Government Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for EGovOntology took 230.18563985824585s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4435710906982422s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0006563663482666016s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 2.368778944015503s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.046722650527954s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6168787479400635s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.8911919593811035s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.276893854141235s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 4.157307147979736s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5683097839355469s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6768088340759277s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.22319602966308594s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.49326586723327637s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 6.125865936279297s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2389826774597168s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3374745845794678s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5356576442718506s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2815687656402588s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.287553071975708s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.19772911071777344s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 10.703855991363525s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0001392364501953125s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3168151378631592s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24272584915161133s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.39229440689086914s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.19665288925170898s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2910459041595459s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7827670574188232s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.21741700172424316s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 5.7081780433654785s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.22347021102905273s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.31324052810668945s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2908504009246826s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 1.0712521076202393s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.031009435653686523s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.029494524002075195s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.22271180152893066s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.1404101848602295s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.37494707107543945s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.096076488494873s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2337608337402344s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.024855136871338s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03517746925354004s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3784198760986328s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4768803119659424s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 2927.0130989551544s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 29.784783840179443s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.02195572853088379s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 2.8371810913085938e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 6.651878356933594e-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 1.2874603271484375e-05s
INFO | --- Analysis for ei2a took 3358.643114089966s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 8.96453857421875e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 26.077426433563232s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.022055387496948242s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.0001125335693359375s
Believability | Calculation of trust value for EIONET RDF Data took 9.059906005859375e-06s
INFO | --- Analysis for eionet-rdf took 136.81116795539856s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 8.797645568847656e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 24.466342210769653s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.020961523056030273s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.4809112548828125e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 1.33514404296875e-05s
INFO | --- Analysis for ElgooG_ took 159.2833595275879s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 9.20137357711792s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 30.575722217559814s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.021193742752075195s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0009133815765380859s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 0.00010943412780761719s
Believability | Calculation of trust value for El Viajero's tourism dataset took 2.0742416381835938e-05s
INFO | --- Analysis for elviajero took 245.40741515159607s
Availability | SPARQL endpoint availability check for EMN took 4.267692565917969e-05s
Availability | VoID file availability check for EMN took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for EMN took 26.80685544013977s
Reputation | Calculation of the PageRank for EMN took 0.0231168270111084s
Interlinking | Calculation of Degree of Connection for EMN took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for EMN took 6.914138793945312e-05s
Believability | Calculation of trust value for EMN took 1.2636184692382812e-05s
INFO | --- Analysis for emn took 80.83048987388611s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 9.34600830078125e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 27.150578022003174s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.02129673957824707s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 6.103515625e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 8.821487426757812e-06s
INFO | --- Analysis for enakting-co2emission took 122.36713910102844s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 4.4345855712890625e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 31.036081075668335s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.023614168167114258s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0010154247283935547s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 6.29425048828125e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 9.059906005859375e-06s
INFO | --- Analysis for enakting-crime took 151.2119653224945s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.220008850097656e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 23.474989891052246s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.021224260330200195s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 6.508827209472656e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 4.76837158203125e-06s
INFO | --- Analysis for enakting-energy took 107.8519082069397s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 8.678436279296875e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0006403923034667969s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 29.90792155265808s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.021342992782592773s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007936954498291016s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 9.72747802734375e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 8.821487426757812e-06s
INFO | --- Analysis for enakting-mortality took 119.69971990585327s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.601478576660156e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.3142547607421875s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.020976781845092773s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 4.673004150390625e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 4.76837158203125e-06s
INFO | --- Analysis for enakting-nhs took 132.6813747882843s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 7.748603820800781e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.3001563549041748s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.021042823791503906s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.817413330078125e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 9.298324584960938e-06s
INFO | --- Analysis for enakting-population took 169.30922770500183s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.6017906665802002s
Availability | VoID file availability check for English Heritage Periods List took 4.221892595291138s
Extra | Recovery of all triples for English Heritage Periods List took 0.33706140518188477s
Performance | Total latancy measurement for English Heritage Periods List took 1.5854434967041016s
Amount of data | Number of triples check for English Heritage Periods List took 0.4471015930175781s
Versatility | Languages check for English Heritage Periods List took 0.25725626945495605s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.5084998607635498s
Security | Check HTTPS for English Heritage Periods List took 0.21072888374328613s
Interpretability | RDF structures check for English Heritage Periods List took 0.2861955165863037s
Versatility | Serialization formats check for English Heritage Periods List took 0.46780896186828613s
Availability | RDF dump link check for English Heritage Periods List took 0.32865333557128906s
License | MR license check for English Heritage Periods List took 0.40813469886779785s
License | HR license check for English Heritage Periods List took 0.34427809715270996s
Amount of data | Number of property check for English Heritage Periods List took 0.368253231048584s
Understandability | Number of label check for English Heritage Periods List took 0.5003135204315186s
Understandability | URI regex check for English Heritage Periods List took 0.6115357875823975s
Understandability | Vocabs check for English Heritage Periods List took 0.3845787048339844s
Verifiability | Authors check for English Heritage Periods List took 0.37932300567626953s
Verifiability | Publishers check for English Heritage Periods List took 0.4084489345550537s
Performance | Throughput check for English Heritage Periods List took 12.083200931549072s
Amount of data | Check the number of entities for English Heritage Periods List took 7.748603820800781e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.32332539558410645s
Interlinking | sameAs chians check for English Heritage Periods List took 0.31775593757629395s
Interlinking | skos check for English Heritage Periods List took 0.30731654167175293s
Interlinking | skos check for English Heritage Periods List took 0.33988118171691895s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.38730621337890625s
Currency | Creation date check for English Heritage Periods List took 0.6339058876037598s
Currency | Modification date check for English Heritage Periods List took 0.6462488174438477s
Rep.Conc. | URIs length for English Heritage Periods List took 0.7220280170440674s
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.3163125514984131s
Accuracy | Check Functional Property for English Heritage Periods List took 0.2982640266418457s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.2997629642486572s
Consistency | Disjoint class check for English Heritage Periods List took 0.290987491607666s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.36806583404541016s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.6451380252838135s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.0006809234619140625s
Security | Sign check for English Heritage Periods List took 0.31777429580688477s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.3342320919036865s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.023305654525756836s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.719329833984375e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.430511474609375e-06s
Believability | Calculation of trust value for English Heritage Periods List took 1.049041748046875e-05s
INFO | --- Analysis for english-heritage-periods-list took 199.57865047454834s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.433809757232666s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0006620883941650391s
Extra | Recovery of all triples for English Index of Multiple Deprivation Ranking 2010 took 1.1242506504058838s
Performance | Total latancy measurement for English Index of Multiple Deprivation Ranking 2010 took 1.131349802017212s
Amount of data | Number of triples check for English Index of Multiple Deprivation Ranking 2010 took 0.3371241092681885s
Interoperability | New terms check for English Index of Multiple Deprivation Ranking 2010 took 1.641979455947876s
Versatility | Languages check for English Index of Multiple Deprivation Ranking 2010 took 0.3960099220275879s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Ranking 2010 took 0.23224687576293945s
Security | Check HTTPS for English Index of Multiple Deprivation Ranking 2010 took 0.519599437713623s
Interpretability | RDF structures check for English Index of Multiple Deprivation Ranking 2010 took 0.3145751953125s
Versatility | Serialization formats check for English Index of Multiple Deprivation Ranking 2010 took 0.13613557815551758s
Availability | RDF dump link check for English Index of Multiple Deprivation Ranking 2010 took 69.6553087234497s
License | MR license check for English Index of Multiple Deprivation Ranking 2010 took 0.3544728755950928s
License | HR license check for English Index of Multiple Deprivation Ranking 2010 took 30.17971658706665s
Amount of data | Number of property check for English Index of Multiple Deprivation Ranking 2010 took 0.19713163375854492s
Understandability | Number of label check for English Index of Multiple Deprivation Ranking 2010 took 0.38322901725769043s
Understandability | URI regex check for English Index of Multiple Deprivation Ranking 2010 took 0.6687679290771484s
Understandability | Vocabs check for English Index of Multiple Deprivation Ranking 2010 took 0.21648645401000977s
Verifiability | Authors check for English Index of Multiple Deprivation Ranking 2010 took 0.1471238136291504s
Verifiability | Publishers check for English Index of Multiple Deprivation Ranking 2010 took 0.26343250274658203s
Performance | Throughput check for English Index of Multiple Deprivation Ranking 2010 took 10.9676833152771s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Ranking 2010 took 8.344650268554688e-05s
Verifiability | Contribs. check for English Index of Multiple Deprivation Ranking 2010 took 0.20691227912902832s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Ranking 2010 took 0.306365966796875s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.6386294364929199s
Interlinking | skos check for English Index of Multiple Deprivation Ranking 2010 took 0.2022113800048828s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Ranking 2010 took 0.2230842113494873s
Currency | Creation date check for English Index of Multiple Deprivation Ranking 2010 took 0.3785574436187744s
Currency | Modification date check for English Index of Multiple Deprivation Ranking 2010 took 0.29580116271972656s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Ranking 2010 took 1.8598921298980713s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Ranking 2010 took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Ranking 2010 took 0.14406585693359375s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.21943140029907227s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Ranking 2010 took 0.22070646286010742s
Consistency | Disjoint class check for English Index of Multiple Deprivation Ranking 2010 took 0.2586066722869873s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Ranking 2010 took 0.7796392440795898s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Ranking 2010 took 1.5131452083587646s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Ranking 2010 took 1.5953645706176758s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.000156402587890625s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Ranking 2010 took 0.415355920791626s
Security | Sign check for English Index of Multiple Deprivation Ranking 2010 took 0.6112608909606934s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 31.12824320793152s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.02155447006225586s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 5.507469177246094e-05s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Ranking 2010 took 9.5367431640625e-07s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 8.106231689453125e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 433.2014479637146s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.15037274360656738s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0007500648498535156s
Extra | Recovery of all triples for English Index of Multiple Deprivation Score 2010 took 1.133678913116455s
Performance | Total latancy measurement for English Index of Multiple Deprivation Score 2010 took 0.9953911304473877s
Amount of data | Number of triples check for English Index of Multiple Deprivation Score 2010 took 0.21816563606262207s
Interoperability | New terms check for English Index of Multiple Deprivation Score 2010 took 1.5660626888275146s
Versatility | Languages check for English Index of Multiple Deprivation Score 2010 took 0.4475436210632324s
Interpretability | Number of blank nodes check for English Index of Multiple Deprivation Score 2010 took 0.20517849922180176s
Security | Check HTTPS for English Index of Multiple Deprivation Score 2010 took 0.1183021068572998s
Interpretability | RDF structures check for English Index of Multiple Deprivation Score 2010 took 0.14908099174499512s
Versatility | Serialization formats check for English Index of Multiple Deprivation Score 2010 took 0.22664618492126465s
Availability | RDF dump link check for English Index of Multiple Deprivation Score 2010 took 53.307493686676025s
License | MR license check for English Index of Multiple Deprivation Score 2010 took 0.1469430923461914s
License | HR license check for English Index of Multiple Deprivation Score 2010 took 30.240740537643433s
Amount of data | Number of property check for English Index of Multiple Deprivation Score 2010 took 0.1677110195159912s
Understandability | Number of label check for English Index of Multiple Deprivation Score 2010 took 0.21225237846374512s
Understandability | URI regex check for English Index of Multiple Deprivation Score 2010 took 0.44321489334106445s
Understandability | Vocabs check for English Index of Multiple Deprivation Score 2010 took 0.14325857162475586s
Verifiability | Authors check for English Index of Multiple Deprivation Score 2010 took 0.21100425720214844s
Verifiability | Publishers check for English Index of Multiple Deprivation Score 2010 took 0.21624064445495605s
Performance | Throughput check for English Index of Multiple Deprivation Score 2010 took 11.11702299118042s
Amount of data | Check the number of entities for English Index of Multiple Deprivation Score 2010 took 0.0002524852752685547s
Verifiability | Contribs. check for English Index of Multiple Deprivation Score 2010 took 0.17812490463256836s
Interlinking | sameAs chians check for English Index of Multiple Deprivation Score 2010 took 0.22750258445739746s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.22400116920471191s
Interlinking | skos check for English Index of Multiple Deprivation Score 2010 took 0.22020840644836426s
Timeliness | dataset update frequency check for English Index of Multiple Deprivation Score 2010 took 0.2450542449951172s
Currency | Creation date check for English Index of Multiple Deprivation Score 2010 took 0.5059185028076172s
Currency | Modification date check for English Index of Multiple Deprivation Score 2010 took 0.2138841152191162s
Rep.Conc. | URIs length for English Index of Multiple Deprivation Score 2010 took 1.584352970123291s
Interoperability | New vocabularies check for English Index of Multiple Deprivation Score 2010 took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for English Index of Multiple Deprivation Score 2010 took 0.21429967880249023s
Accuracy | Check Functional Property for English Index of Multiple Deprivation Score 2010 took 0.1693429946899414s
Accuracy | Check Inverse Functional Property for English Index of Multiple Deprivation Score 2010 took 0.6980535984039307s
Consistency | Disjoint class check for English Index of Multiple Deprivation Score 2010 took 0.23799705505371094s
Consistency | Check Misplaced properties for English Index of Multiple Deprivation Score 2010 took 0.6014974117279053s
Consistency | Check Ontology hijacking for English Index of Multiple Deprivation Score 2010 took 1.231868028640747s
Consistency | Check Invalid usage of undefined properties for English Index of Multiple Deprivation Score 2010 took 8.443905353546143s
Conciseness | Check Extensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.0007114410400390625s
Conciseness | Check Intensional conciseness for English Index of Multiple Deprivation Score 2010 took 0.3477911949157715s
Security | Sign check for English Index of Multiple Deprivation Score 2010 took 0.24173974990844727s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.4270944595336914s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.1715238094329834s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 5.8650970458984375e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.006234407424926758s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 0.00022459030151367188s
Interoperability | Check the re-using of existing vocabs for English Index of Multiple Deprivation Score 2010 took 1.0013580322265625e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 3.218650817871094e-05s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 366.89733505249023s
Availability | SPARQL endpoint availability check for English WordNet took 0.00031304359436035156s
Availability | VoID file availability check for English WordNet took 0.00223541259765625s
Completeness | Calculation of interlinking completeness for English WordNet took 33.174182176589966s
Reputation | Calculation of the PageRank for English WordNet took 0.17258715629577637s
Interlinking | Calculation of Degree of Connection for English WordNet took 5.3882598876953125e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.006260395050048828s
Interlinking | Calculation of Clustering coefficient for English WordNet took 0.0002243518829345703s
Believability | Calculation of trust value for English WordNet took 3.814697265625e-05s
INFO | --- Analysis for english-wordnet took 183.32971286773682s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.09650111198425293s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.00033736228942871094s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.2922842502593994s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.02094888687133789s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 9.512901306152344e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 1.2874603271484375e-05s
INFO | --- Analysis for enipedia took 154.0427315235138s
Availability | SPARQL endpoint availability check for Enslaved.org took 4.291534423828125e-05s
Availability | VoID file availability check for Enslaved.org took 0.0021810531616210938s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.3652489185333252s
Reputation | Calculation of the PageRank for Enslaved.org took 0.17586851119995117s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 5.9604644775390625e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.006410121917724609s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 0.0001785755157470703s
Believability | Calculation of trust value for Enslaved.org took 3.719329833984375e-05s
INFO | --- Analysis for enslaved.org took 116.75559973716736s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.33209896087646484s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 28.800989866256714s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.02105879783630371s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 5.888938903808594e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 1.1205673217773438e-05s
INFO | --- Analysis for entice-graph took 163.73092126846313s
Availability | SPARQL endpoint availability check for Entrez Gene took 4.315376281738281e-05s
Availability | VoID file availability check for Entrez Gene took 0.0008561611175537109s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.4082372188568115s
Reputation | Calculation of the PageRank for Entrez Gene took 0.02274036407470703s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.981590270996094e-05s
Believability | Calculation of trust value for Entrez Gene took 1.239776611328125e-05s
INFO | --- Analysis for entrez_gene took 110.35394620895386s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.02303147315979s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0006344318389892578s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 27.06692886352539s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.02146005630493164s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0008273124694824219s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 6.937980651855469e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 9.298324584960938e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 176.80660009384155s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 1.0732922554016113s
Availability | VoID file availability check for environment.data.gov.uk took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 29.92419195175171s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.020818710327148438s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 5.2928924560546875e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 9.775161743164062e-06s
INFO | --- Analysis for environment-data-gov-uk took 178.78974843025208s
Availability | SPARQL endpoint availability check for EARTh took 272.35761308670044s
Availability | VoID file availability check for EARTh took 3.8869218826293945s
Completeness | Calculation of interlinking completeness for EARTh took 27.275431394577026s
Reputation | Calculation of the PageRank for EARTh took 0.02664804458618164s
Interlinking | Calculation of Degree of Connection for EARTh took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0008151531219482422s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00010752677917480469s
Interoperability | Check the re-using of existing vocabs for EARTh took 1.8851640224456787s
Believability | Calculation of trust value for EARTh took 1.2636184692382812e-05s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 894.317538022995s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.5910477638244629s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.0002994537353515625s
Extra | Recovery of all triples for Micka (EO metadata) @PSNC took 104.66578578948975s
Performance | Total latancy measurement for Micka (EO metadata) @PSNC took 0.949636697769165s
Amount of data | Number of triples check for Micka (EO metadata) @PSNC took 9.285530090332031s
Interoperability | New terms check for Micka (EO metadata) @PSNC took 14.694239139556885s
Versatility | Languages check for Micka (EO metadata) @PSNC took 300.2292034626007s
Interpretability | Number of blank nodes check for Micka (EO metadata) @PSNC took 2.2334396839141846s
Interpretability | RDF structures check for Micka (EO metadata) @PSNC took 0.34393739700317383s
Versatility | Serialization formats check for Micka (EO metadata) @PSNC took 10.30376935005188s
Availability | RDF dump link check for Micka (EO metadata) @PSNC took 0.2627260684967041s
License | MR license check for Micka (EO metadata) @PSNC took 0.43956589698791504s
License | HR license check for Micka (EO metadata) @PSNC took 300.2510578632355s
Amount of data | Number of property check for Micka (EO metadata) @PSNC took 0.21199941635131836s
Understandability | Number of label check for Micka (EO metadata) @PSNC took 3.0356101989746094s
Understandability | URI regex check for Micka (EO metadata) @PSNC took 1.3265302181243896s
Understandability | Vocabs check for Micka (EO metadata) @PSNC took 0.6098082065582275s
Verifiability | Authors check for Micka (EO metadata) @PSNC took 0.20851445198059082s
Verifiability | Publishers check for Micka (EO metadata) @PSNC took 0.27253007888793945s
Performance | Throughput check for Micka (EO metadata) @PSNC took 11.090523719787598s
Amount of data | Check the number of entities for Micka (EO metadata) @PSNC took 7.009506225585938e-05s
Verifiability | Contribs. check for Micka (EO metadata) @PSNC took 0.21804451942443848s
Interlinking | sameAs chians check for Micka (EO metadata) @PSNC took 0.21819639205932617s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.48598456382751465s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.40546703338623047s
Timeliness | dataset update frequency check for Micka (EO metadata) @PSNC took 5.173379182815552s
Currency | Creation date check for Micka (EO metadata) @PSNC took 0.48651790618896484s
Currency | Modification date check for Micka (EO metadata) @PSNC took 0.23334002494812012s
Rep.Conc. | URIs length for Micka (EO metadata) @PSNC took 150.791006565094s
Interoperability | New vocabularies check for Micka (EO metadata) @PSNC took 1.1682510375976562e-05s
Consistency | Deprecated classes/propertiers check for Micka (EO metadata) @PSNC took 0.20113182067871094s
Accuracy | Check Functional Property for Micka (EO metadata) @PSNC took 0.2755124568939209s
Accuracy | Check Inverse Functional Property for Micka (EO metadata) @PSNC took 0.2810235023498535s
Accuracy | Check Empty annotation labels for Micka (EO metadata) @PSNC took 30.74606680870056s
Accuracy | Check White space in annotation for Micka (EO metadata) @PSNC took 2.693479061126709s
Accuracy | Check Datatype consistency for Micka (EO metadata) @PSNC took 2.648892879486084s
Consistency | Disjoint class check for Micka (EO metadata) @PSNC took 0.22235369682312012s
Consistency | Check Misplaced properties for Micka (EO metadata) @PSNC took 88.20654559135437s
Consistency | Misplaced classes for Micka (EO metadata) @PSNC took 8.480125427246094s
Consistency | Check Ontology hijacking for Micka (EO metadata) @PSNC took 35.53075695037842s
Consistency | Check Invalid usage of undefined classes for Micka (EO metadata) @PSNC took 1.3676412105560303s
Consistency | Check Invalid usage of undefined properties for Micka (EO metadata) @PSNC took 88.06839203834534s
Conciseness | Check Extensional conciseness for Micka (EO metadata) @PSNC took 2.7917871475219727s
Conciseness | Check Intensional conciseness for Micka (EO metadata) @PSNC took 0.6159794330596924s
Security | Sign check for Micka (EO metadata) @PSNC took 1.5438854694366455s
Availability | Check URIs Dereferenciability for Micka (EO metadata) @PSNC took 10.226897478103638s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 26.490574598312378s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.021660566329956055s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 6.461143493652344e-05s
Interoperability | Check the re-using of existing vocabs for Micka (EO metadata) @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 1.239776611328125e-05s
INFO | --- Analysis for EO_metadata took 2392.8085730075836s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 4.3392181396484375e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.35691142082214355s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.02097630500793457s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 4.5299530029296875e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 7.3909759521484375e-06s
INFO | --- Analysis for EOKP-Datasets took 120.077476978302s
Availability | SPARQL endpoint availability check for EPA-CDR took 9.036064147949219e-05s
Availability | VoID file availability check for EPA-CDR took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for EPA-CDR took 30.69804310798645s
Reputation | Calculation of the PageRank for EPA-CDR took 0.02166152000427246s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.910064697265625e-05s
Believability | Calculation of trust value for EPA-CDR took 5.245208740234375e-06s
INFO | --- Analysis for epa-cdr took 143.8451931476593s
Availability | SPARQL endpoint availability check for EPA-FRS took 4.649162292480469e-05s
Availability | VoID file availability check for EPA-FRS took 0.0007195472717285156s
Completeness | Calculation of interlinking completeness for EPA-FRS took 28.362878799438477s
Reputation | Calculation of the PageRank for EPA-FRS took 0.02376580238342285s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.891654968261719e-05s
Believability | Calculation of trust value for EPA-FRS took 9.775161743164062e-06s
INFO | --- Analysis for epa-frs took 121.89283871650696s
Availability | SPARQL endpoint availability check for EPA-RCRA took 8.7738037109375e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.3037292957305908s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.02147507667541504s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0010597705841064453s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 4.482269287109375e-05s
Believability | Calculation of trust value for EPA-RCRA took 1.0013580322265625e-05s
INFO | --- Analysis for epa-rcra took 147.62686371803284s
Availability | SPARQL endpoint availability check for EPA-SRS took 8.916854858398438e-05s
Availability | VoID file availability check for EPA-SRS took 0.0007162094116210938s
Completeness | Calculation of interlinking completeness for EPA-SRS took 28.26103639602661s
Reputation | Calculation of the PageRank for EPA-SRS took 0.021276235580444336s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 2.9087066650390625e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 9.179115295410156e-05s
Believability | Calculation of trust value for EPA-SRS took 8.58306884765625e-06s
INFO | --- Analysis for epa-srs took 197.98431754112244s
Availability | SPARQL endpoint availability check for EPA-TRI took 8.869171142578125e-05s
Availability | VoID file availability check for EPA-TRI took 0.0007321834564208984s
Completeness | Calculation of interlinking completeness for EPA-TRI took 25.04017424583435s
Reputation | Calculation of the PageRank for EPA-TRI took 0.021078109741210938s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 4.673004150390625e-05s
Believability | Calculation of trust value for EPA-TRI took 9.298324584960938e-06s
INFO | --- Analysis for epa-tri took 137.6843717098236s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.03889346122741699s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 27.994245767593384s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.020896196365356445s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.0001304149627685547s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 148.2253806591034s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.4519021511077881s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0006246566772460938s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 30.133310079574585s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.021253108978271484s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.535385131835938e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 7.62939453125e-06s
INFO | --- Analysis for eprtr took 117.4630434513092s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.4336686134338379s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0006320476531982422s
Extra | Recovery of all triples for Railway Infrastructure KG took 58.733060121536255s
Performance | Total latancy measurement for Railway Infrastructure KG took 1.1169512271881104s
Amount of data | Number of triples check for Railway Infrastructure KG took 0.2382059097290039s
Interoperability | New terms check for Railway Infrastructure KG took 1.600045919418335s
Versatility | Languages check for Railway Infrastructure KG took 77.1944751739502s
Interpretability | Number of blank nodes check for Railway Infrastructure KG took 0.2522313594818115s
Interpretability | RDF structures check for Railway Infrastructure KG took 0.38454627990722656s
Versatility | Serialization formats check for Railway Infrastructure KG took 0.22725152969360352s
Availability | RDF dump link check for Railway Infrastructure KG took 0.22329163551330566s
License | MR license check for Railway Infrastructure KG took 0.2951381206512451s
License | HR license check for Railway Infrastructure KG took 60.64913320541382s
Amount of data | Number of property check for Railway Infrastructure KG took 0.20768022537231445s
Understandability | Number of label check for Railway Infrastructure KG took 0.4862034320831299s
Understandability | URI regex check for Railway Infrastructure KG took 0.45459747314453125s
Understandability | Vocabs check for Railway Infrastructure KG took 0.23633480072021484s
Verifiability | Authors check for Railway Infrastructure KG took 0.2525291442871094s
Verifiability | Publishers check for Railway Infrastructure KG took 0.2552175521850586s
Performance | Throughput check for Railway Infrastructure KG took 10.885385990142822s
Verifiability | Contribs. check for Railway Infrastructure KG took 0.25535154342651367s
Interlinking | sameAs chians check for Railway Infrastructure KG took 0.23512697219848633s
Interlinking | skos check for Railway Infrastructure KG took 0.25246238708496094s
Interlinking | skos check for Railway Infrastructure KG took 0.28899574279785156s
Timeliness | dataset update frequency check for Railway Infrastructure KG took 0.23151683807373047s
Currency | Creation date check for Railway Infrastructure KG took 0.4627711772918701s
Currency | Modification date check for Railway Infrastructure KG took 0.22354483604431152s
Rep.Conc. | URIs length for Railway Infrastructure KG took 22.33767867088318s
Interoperability | New vocabularies check for Railway Infrastructure KG took 10.006562948226929s
Consistency | Deprecated classes/propertiers check for Railway Infrastructure KG took 0.21787023544311523s
Accuracy | Check Functional Property for Railway Infrastructure KG took 0.23755836486816406s
Accuracy | Check Inverse Functional Property for Railway Infrastructure KG took 0.24077129364013672s
Accuracy | Check Empty annotation labels for Railway Infrastructure KG took 14.815222978591919s
Accuracy | Check White space in annotation for Railway Infrastructure KG took 2.6180338859558105s
Accuracy | Check Datatype consistency for Railway Infrastructure KG took 2.696958541870117s
Consistency | Disjoint class check for Railway Infrastructure KG took 0.2327594757080078s
Consistency | Check Misplaced properties for Railway Infrastructure KG took 1.7088508605957031s
Consistency | Misplaced classes for Railway Infrastructure KG took 8.531412839889526s
Consistency | Check Ontology hijacking for Railway Infrastructure KG took 19.774482250213623s
Consistency | Check Invalid usage of undefined classes for Railway Infrastructure KG took 1.4652044773101807s
Consistency | Check Invalid usage of undefined properties for Railway Infrastructure KG took 2.8209235668182373s
Conciseness | Check Extensional conciseness for Railway Infrastructure KG took 2.926175355911255s
Conciseness | Check Intensional conciseness for Railway Infrastructure KG took 0.32212305068969727s
Security | Sign check for Railway Infrastructure KG took 0.3031959533691406s
Availability | Check URIs Dereferenciability for Railway Infrastructure KG took 2181.8832337856293s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 28.67085313796997s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.022831201553344727s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 6.651878356933594e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 4.029273986816406e-05s
Interoperability | Check the re-using of existing vocabs for Railway Infrastructure KG took 8.510455846786499s
Believability | Calculation of trust value for Railway Infrastructure KG took 2.3603439331054688e-05s
INFO | --- Analysis for ERAKG took 2709.778186559677s
Availability | SPARQL endpoint availability check for reg took 4.363059997558594e-05s
Availability | VoID file availability check for reg took 0.00030612945556640625s
Completeness | Calculation of interlinking completeness for reg took 0.3452601432800293s
Reputation | Calculation of the PageRank for reg took 0.021085500717163086s
Interlinking | Calculation of Degree of Connection for reg took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for reg took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for reg took 1.4781951904296875e-05s
Believability | Calculation of trust value for reg took 8.344650268554688e-06s
INFO | --- Analysis for erg took 84.3394238948822s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.23947620391845703s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.001094818115234375s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 28.02476954460144s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.0212247371673584s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.600120544433594e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 9.5367431640625e-06s
INFO | --- Analysis for es-msssi-drug-prices took 166.95372796058655s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 8.821487426757812e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.000751495361328125s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 25.538312196731567s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.021222829818725586s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 9.441375732421875e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 9.775161743164062e-06s
INFO | --- Analysis for esd-standards took 154.45242428779602s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 8.320808410644531e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.30153775215148926s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.02097296714782715s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.772445678710938e-05s
Believability | Calculation of trust value for ESD-Toolkit took 9.298324584960938e-06s
INFO | --- Analysis for esd-toolkit took 106.68616437911987s
Availability | SPARQL endpoint availability check for Dataset Esis took 8.606910705566406e-05s
Availability | VoID file availability check for Dataset Esis took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.3099849224090576s
Reputation | Calculation of the PageRank for Dataset Esis took 0.022565603256225586s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.7670135498046875e-05s
Believability | Calculation of trust value for Dataset Esis took 1.1920928955078125e-05s
INFO | --- Analysis for esislearning took 157.34690523147583s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 8.845329284667969e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.28574371337890625s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.021239042282104492s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 3.814697265625e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 1.2159347534179688e-05s
INFO | --- Analysis for ESV took 81.18298888206482s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.5747385025024414s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.000873565673828125s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.30204010009765625s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.02132439613342285s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0008156299591064453s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 5.1975250244140625e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 142.02570056915283s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 5.516932725906372s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 25.336318492889404s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.02117609977722168s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 8.177757263183594e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 1.3113021850585938e-05s
INFO | --- Analysis for eu-agencies-bodies took 88.58221316337585s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 4.673004150390625e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0007650852203369141s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.38306689262390137s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.021464109420776367s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.891654968261719e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 8.821487426757812e-06s
INFO | --- Analysis for eu-institutions took 93.6623649597168s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 1.0724923610687256s
Availability | VoID file availability check for EU Parliament Media Library took 1.649501085281372s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 29.17037272453308s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.02903127670288086s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0016028881072998047s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 8.463859558105469e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 1.1205673217773438e-05s
INFO | --- Analysis for eu-parliament-media took 145.14057612419128s
Availability | SPARQL endpoint availability check for EU Who Is Who took 1.3066658973693848s
Availability | VoID file availability check for EU Who Is Who took 0.0007884502410888672s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.28824758529663086s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.021078824996948242s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 4.482269287109375e-05s
Believability | Calculation of trust value for EU Who Is Who took 8.821487426757812e-06s
INFO | --- Analysis for eu-who-is-who took 153.0249502658844s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 0.94171142578125s
Availability | VoID file availability check for EUMIDA as Linked Data took 1.5379548072814941s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 28.90221858024597s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.021032333374023438s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.1484832763671875e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for eumida-linked-data took 137.8278272151947s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.3593330383300781s
Availability | VoID file availability check for European Nature Information System took 0.48665308952331543s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.36571478843688965s
Reputation | Calculation of the PageRank for European Nature Information System took 0.020921707153320312s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00011491775512695312s
Interoperability | Check the re-using of existing vocabs for European Nature Information System took 4.40415620803833s
Believability | Calculation of trust value for European Nature Information System took 1.1444091796875e-05s
INFO | --- Analysis for eunis took 57.01987648010254s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 5.5378944873809814s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0007803440093994141s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.31156420707702637s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.021094322204589844s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 8.106231689453125e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 1.3589859008789062e-05s
INFO | --- Analysis for eur-lex-rdf took 73.60218143463135s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 1.0751307010650635s
Availability | VoID file availability check for Standard Eurobarometer took 0.0007448196411132812s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.3139352798461914s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.0208432674407959s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.4345855712890625e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 1.0967254638671875e-05s
INFO | --- Analysis for eurobarometer-standard took 104.86981916427612s
Availability | SPARQL endpoint availability check for European Election Results took 1.011336326599121s
Availability | VoID file availability check for European Election Results took 0.0006833076477050781s
Completeness | Calculation of interlinking completeness for European Election Results took 28.53804588317871s
Reputation | Calculation of the PageRank for European Election Results took 0.021011829376220703s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.9577484130859375e-05s
Believability | Calculation of trust value for European Election Results took 9.5367431640625e-06s
INFO | --- Analysis for european-election-results took 192.47754669189453s
Availability | SPARQL endpoint availability check for EPO patents took 0.4183027744293213s
Availability | VoID file availability check for EPO patents took 0.0006928443908691406s
Extra | Recovery of all triples for EPO patents took 29.844462871551514s
Performance | Total latancy measurement for EPO patents took 0.8930306434631348s
Amount of data | Number of triples check for EPO patents took 90.19851517677307s
Versatility | Languages check for EPO patents took 100.16865086555481s
Interpretability | Number of blank nodes check for EPO patents took 100.22715187072754s
Interpretability | RDF structures check for EPO patents took 29.71728825569153s
Versatility | Serialization formats check for EPO patents took 0.21657538414001465s
Availability | RDF dump link check for EPO patents took 0.16233539581298828s
License | MR license check for EPO patents took 0.2480626106262207s
License | HR license check for EPO patents took 90.17599534988403s
Amount of data | Number of property check for EPO patents took 0.24828052520751953s
Understandability | Number of label check for EPO patents took 90.28106999397278s
Understandability | URI regex check for EPO patents took 0.5625941753387451s
Understandability | Vocabs check for EPO patents took 0.1795039176940918s
Verifiability | Authors check for EPO patents took 0.1797623634338379s
Verifiability | Publishers check for EPO patents took 0.20268774032592773s
Performance | Throughput check for EPO patents took 10.87719178199768s
Amount of data | Check the number of entities for EPO patents took 0.00011324882507324219s
Verifiability | Contribs. check for EPO patents took 0.1731572151184082s
Interlinking | sameAs chians check for EPO patents took 0.25689029693603516s
Interlinking | skos check for EPO patents took 0.21376252174377441s
Interlinking | skos check for EPO patents took 0.17768096923828125s
Timeliness | dataset update frequency check for EPO patents took 0.16044855117797852s
Currency | Creation date check for EPO patents took 0.3821067810058594s
Currency | Modification date check for EPO patents took 0.3636305332183838s
Rep.Conc. | URIs length for EPO patents took 207.5471007823944s
Interoperability | New vocabularies check for EPO patents took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 64.86691689491272s
Accuracy | Check Empty annotation labels for EPO patents took 17.21355104446411s
Accuracy | Check White space in annotation for EPO patents took 3.0463156700134277s
Accuracy | Check Datatype consistency for EPO patents took 5.043259143829346s
Consistency | Disjoint class check for EPO patents took 0.2515852451324463s
Consistency | Check Misplaced properties for EPO patents took 100.46572923660278s
Consistency | Check Ontology hijacking for EPO patents took 39.05097842216492s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.6420907974243164s
Consistency | Check Invalid usage of undefined properties for EPO patents took 101.58422374725342s
Conciseness | Check Extensional conciseness for EPO patents took 2.8864901065826416s
Conciseness | Check Intensional conciseness for EPO patents took 15.85207200050354s
Security | Sign check for EPO patents took 0.18583035469055176s
Availability | Check URIs Dereferenciability for EPO patents took 1.8502185344696045s
Completeness | Calculation of interlinking completeness for EPO patents took 0.48549509048461914s
Reputation | Calculation of the PageRank for EPO patents took 0.022216320037841797s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for EPO patents took 6.318092346191406e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 2.384185791015625e-06s
Believability | Calculation of trust value for EPO patents took 1.2159347534179688e-05s
INFO | --- Analysis for European_Patent_Information took 1549.1050164699554s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 0.00010728836059570312s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.19219255447387695s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 23.607731580734253s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.022409677505493164s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 0.00011110305786132812s
Interoperability | Check the re-using of existing vocabs for Europeana Linked Open Data V1.0 took 18.57044744491577s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 7.152557373046875e-06s
INFO | --- Analysis for europeana-lod-v1 took 275.60681557655334s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.4263191223144531s
Availability | VoID file availability check for Europeana SPARQL took 0.24045228958129883s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 24.914911031723022s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.02128291130065918s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 5.459785461425781e-05s
Interoperability | Check the re-using of existing vocabs for Europeana SPARQL took 16.04733633995056s
Believability | Calculation of trust value for Europeana SPARQL took 7.62939453125e-06s
INFO | --- Analysis for europeana-sparql took 190.79536843299866s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.07341551780700684s
Availability | VoID file availability check for EuroSentiment took 0.0004086494445800781s
Completeness | Calculation of interlinking completeness for EuroSentiment took 24.54213309288025s
Reputation | Calculation of the PageRank for EuroSentiment took 0.02114558219909668s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 4.649162292480469e-05s
Believability | Calculation of trust value for EuroSentiment took 1.1920928955078125e-05s
INFO | --- Analysis for eurosentiment took 164.60362434387207s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 8.940696716308594e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 22.777925729751587s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.022359848022460938s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007987022399902344s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 8.726119995117188e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 5.245208740234375e-06s
INFO | --- Analysis for eurostat-rdf took 243.48142099380493s
Availability | SPARQL endpoint availability check for EuroVoc took 0.18799185752868652s
Availability | VoID file availability check for EuroVoc took 0.0007171630859375s
Extra | Recovery of all triples for EuroVoc took 175.9482524394989s
Performance | Total latancy measurement for EuroVoc took 0.570955753326416s
Amount of data | Number of triples check for EuroVoc took 93.58031034469604s
Interoperability | New terms check for EuroVoc took 55.52960920333862s
Versatility | Languages check for EuroVoc took 300.0734694004059s
Interpretability | Number of blank nodes check for EuroVoc took 16.46065926551819s
Security | Check HTTPS for EuroVoc took 0.3211507797241211s
Interpretability | RDF structures check for EuroVoc took 0.2658979892730713s
Versatility | Serialization formats check for EuroVoc took 2.7701504230499268s
Availability | RDF dump link check for EuroVoc took 0.1915442943572998s
License | MR license check for EuroVoc took 0.3637673854827881s
License | HR license check for EuroVoc took 300.078715801239s
Amount of data | Number of property check for EuroVoc took 0.1577768325805664s
Understandability | Number of label check for EuroVoc took 1.9325802326202393s
Understandability | URI regex check for EuroVoc took 0.3792109489440918s
Understandability | Vocabs check for EuroVoc took 0.10594487190246582s
Verifiability | Authors check for EuroVoc took 0.2412550449371338s
Verifiability | Publishers check for EuroVoc took 0.19483017921447754s
Performance | Throughput check for EuroVoc took 10.634533643722534s
Amount of data | Check the number of entities for EuroVoc took 8.463859558105469e-05s
Verifiability | Contribs. check for EuroVoc took 0.10902237892150879s
Interlinking | sameAs chians check for EuroVoc took 6.146873235702515s
Interlinking | skos check for EuroVoc took 0.32810282707214355s
Interlinking | skos check for EuroVoc took 0.14093375205993652s
Timeliness | dataset update frequency check for EuroVoc took 0.3048117160797119s
Currency | Creation date check for EuroVoc took 0.45734596252441406s
Currency | Modification date check for EuroVoc took 0.14207100868225098s
Rep.Conc. | URIs length for EuroVoc took 413.3172171115875s
Interoperability | New vocabularies check for EuroVoc took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.18146586418151855s
Accuracy | Check Functional Property for EuroVoc took 0.21660399436950684s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.1884922981262207s
Accuracy | Check Empty annotation labels for EuroVoc took 42.33331751823425s
Accuracy | Check White space in annotation for EuroVoc took 3.238891839981079s
Accuracy | Check Datatype consistency for EuroVoc took 2.6688075065612793s
Consistency | Disjoint class check for EuroVoc took 0.14487767219543457s
Consistency | Check Misplaced properties for EuroVoc took 300.47249603271484s
Consistency | Misplaced classes for EuroVoc took 8.741683959960938s
Consistency | Check Ontology hijacking for EuroVoc took 65.9583911895752s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.7407851219177246s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 301.4315733909607s
Conciseness | Check Extensional conciseness for EuroVoc took 3.1253387928009033s
Conciseness | Check Intensional conciseness for EuroVoc took 0.5052485466003418s
Security | Sign check for EuroVoc took 0.1431593894958496s
Availability | Check URIs Dereferenciability for EuroVoc took 11.422823190689087s
Completeness | Calculation of interlinking completeness for EuroVoc took 0.7408320903778076s
Reputation | Calculation of the PageRank for EuroVoc took 0.02219414710998535s
Interlinking | Calculation of Degree of Connection for EuroVoc took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 9.083747863769531e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 1.430511474609375e-06s
Believability | Calculation of trust value for EuroVoc took 1.2159347534179688e-05s
INFO | --- Analysis for eurovoc took 14729.262580633163s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 8.630752563476562e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0008270740509033203s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 28.311206579208374s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.021334409713745117s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 5.030632019042969e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 9.298324584960938e-06s
INFO | --- Analysis for euskadi-farmacias took 162.52354955673218s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.7211382389068604s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.29275083541870117s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.020756006240844727s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.5762786865234375e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 1.239776611328125e-05s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 130.09708166122437s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.5260190963745117s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0009181499481201172s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 23.869768619537354s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.021083593368530273s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.700920104980469e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 1.239776611328125e-05s
INFO | --- Analysis for eutc-productions took 145.3374786376953s
Availability | SPARQL endpoint availability check for EventMedia took 0.36325502395629883s
Availability | VoID file availability check for EventMedia took 0.0006678104400634766s
Completeness | Calculation of interlinking completeness for EventMedia took 0.3172879219055176s
Reputation | Calculation of the PageRank for EventMedia took 0.023422956466674805s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00011444091796875s
Believability | Calculation of trust value for EventMedia took 1.1444091796875e-05s
INFO | --- Analysis for event-media took 141.27971386909485s
Availability | SPARQL endpoint availability check for EventKG took 0.00011324882507324219s
Availability | VoID file availability check for EventKG took 0.0007114410400390625s
Completeness | Calculation of interlinking completeness for EventKG took 0.31452107429504395s
Reputation | Calculation of the PageRank for EventKG took 0.02121424674987793s
Interlinking | Calculation of Degree of Connection for EventKG took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0008068084716796875s
Interlinking | Calculation of Clustering coefficient for EventKG took 0.0001010894775390625s
Believability | Calculation of trust value for EventKG took 1.2159347534179688e-05s
INFO | --- Analysis for eventkg took 129.5626459121704s
Availability | SPARQL endpoint availability check for Eventseer took 1.4589924812316895s
Availability | VoID file availability check for Eventseer took 0.00041031837463378906s
Completeness | Calculation of interlinking completeness for Eventseer took 0.31799793243408203s
Reputation | Calculation of the PageRank for Eventseer took 0.023726701736450195s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.001134634017944336s
Interlinking | Calculation of Clustering coefficient for Eventseer took 6.389617919921875e-05s
Believability | Calculation of trust value for Eventseer took 1.0967254638671875e-05s
INFO | --- Analysis for eventseer took 186.32303619384766s
Availability | SPARQL endpoint availability check for Face Link took 8.702278137207031e-05s
Availability | VoID file availability check for Face Link took 0.0003390312194824219s
Completeness | Calculation of interlinking completeness for Face Link took 26.750927209854126s
Reputation | Calculation of the PageRank for Face Link took 0.022226333618164062s
Interlinking | Calculation of Degree of Connection for Face Link took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0008325576782226562s
Interlinking | Calculation of Clustering coefficient for Face Link took 5.507469177246094e-05s
Believability | Calculation of trust value for Face Link took 1.0728836059570312e-05s
INFO | --- Analysis for Face_Link took 163.77636551856995s
Availability | SPARQL endpoint availability check for Fact Forge took 0.6877782344818115s
Availability | VoID file availability check for Fact Forge took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Fact Forge took 28.398791313171387s
Reputation | Calculation of the PageRank for Fact Forge took 0.021273374557495117s
Interlinking | Calculation of Degree of Connection for Fact Forge took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Fact Forge took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 3.266334533691406e-05s
Believability | Calculation of trust value for Fact Forge took 1.2874603271484375e-05s
INFO | --- Analysis for fact-forge took 165.40148043632507s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5517866611480713s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0005185604095458984s
Extra | Recovery of all triples for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 117.36449670791626s
Performance | Total latancy measurement for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9811663627624512s
Amount of data | Number of triples check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.338280439376831s
Interoperability | New terms check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 14.319025754928589s
Versatility | Languages check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.24699997901917s
Interpretability | Number of blank nodes check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.3223092555999756s
Interpretability | RDF structures check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.33913373947143555s
Versatility | Serialization formats check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.33716082572937s
Availability | RDF dump link check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.39777326583862305s
License | MR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.8893885612487793s
License | HR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.15606784820557s
Amount of data | Number of property check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.20645809173583984s
Understandability | Number of label check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.4218409061431885s
Understandability | URI regex check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.4122333526611328s
Understandability | Vocabs check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.7003703117370605s
Verifiability | Authors check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.20876741409301758s
Verifiability | Publishers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.23125433921813965s
Performance | Throughput check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 11.302010774612427s
Amount of data | Check the number of entities for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.176399230957031e-05s
Verifiability | Contribs. check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.20255827903747559s
Interlinking | sameAs chians check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.18345975875854492s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4655790328979492s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4335031509399414s
Timeliness | dataset update frequency check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 4.444304943084717s
Currency | Creation date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4785168170928955s
Currency | Modification date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.25897860527038574s
Rep.Conc. | URIs length for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 164.06488919258118s
Interoperability | New vocabularies check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.20225811004638672s
Accuracy | Check Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2754368782043457s
Accuracy | Check Inverse Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2906665802001953s
Accuracy | Check Empty annotation labels for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 37.39484000205994s
Accuracy | Check White space in annotation for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.722761631011963s
Accuracy | Check Datatype consistency for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6843533515930176s
Consistency | Disjoint class check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.195267915725708s
Consistency | Check Misplaced properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 86.1325957775116s
Consistency | Misplaced classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.491893529891968s
Consistency | Check Ontology hijacking for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 33.14381122589111s
Consistency | Check Invalid usage of undefined classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.3998603820800781s
Consistency | Check Invalid usage of undefined properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 86.71686387062073s
Conciseness | Check Extensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.8044228553771973s
Conciseness | Check Intensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.541330099105835s
Security | Sign check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.4495110511779785s
Availability | Check URIs Dereferenciability for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.330674171447754s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 24.309016227722168s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.022143125534057617s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0009515285491943359s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 5.841255187988281e-05s
Interoperability | Check the re-using of existing vocabs for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.4066696166992188e-05s
INFO | --- Analysis for FADN_(2019) took 2393.839010953903s
Availability | SPARQL endpoint availability check for FAMEData took 8.749961853027344e-05s
Availability | VoID file availability check for FAMEData took 0.0008034706115722656s
Completeness | Calculation of interlinking completeness for FAMEData took 23.135544538497925s
Reputation | Calculation of the PageRank for FAMEData took 0.022483110427856445s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for FAMEData took 5.245208740234375e-05s
Believability | Calculation of trust value for FAMEData took 1.1682510375976562e-05s
INFO | --- Analysis for famedata took 217.0179181098938s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 0.00010704994201660156s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0006940364837646484s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 25.20784640312195s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.021048307418823242s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 0.00012445449829101562s
Believability | Calculation of trust value for FAO geopolitical ontology took 8.344650268554688e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 93.31622099876404s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.11287426948547363s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 28.27453351020813s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.022709131240844727s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00012373924255371094s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.5497207641601562e-05s
INFO | --- Analysis for fao-linked-data took 136.06671118736267s
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.0006916522979736328s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.3440585136413574s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.021286487579345703s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 3.24249267578125e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 1.1682510375976562e-05s
INFO | --- Analysis for FAO_species took 84.76445627212524s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.588708877563477s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0007872581481933594s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.31169986724853516s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.022433042526245117s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.982948303222656e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 1.1682510375976562e-05s
INFO | --- Analysis for farmbio-chembl took 231.03950762748718s
Availability | SPARQL endpoint availability check for I4.0-Onto took 0.0002834796905517578s
Availability | VoID file availability check for I4.0-Onto took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.29105496406555176s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.02109503746032715s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 3.552436828613281e-05s
Believability | Calculation of trust value for I4.0-Onto took 1.1682510375976562e-05s
INFO | --- Analysis for fatimazahra took 135.13503193855286s
Availability | SPARQL endpoint availability check for FHIR STU3 took 4.291534423828125e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0005838871002197266s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 34.32960891723633s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.02119898796081543s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 3.337860107421875e-05s
Believability | Calculation of trust value for FHIR STU3 took 1.0251998901367188e-05s
INFO | --- Analysis for FHIR_STU3 took 161.572651386261s
Availability | SPARQL endpoint availability check for FiESTA took 4.1484832763671875e-05s
Availability | VoID file availability check for FiESTA took 0.0008292198181152344s
Completeness | Calculation of interlinking completeness for FiESTA took 25.62481188774109s
Reputation | Calculation of the PageRank for FiESTA took 0.021018266677856445s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for FiESTA took 4.6253204345703125e-05s
Believability | Calculation of trust value for FiESTA took 1.1920928955078125e-05s
INFO | --- Analysis for fiesta took 133.9156677722931s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00014400482177734375s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 24.173547744750977s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.020995140075683594s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 2.5510787963867188e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.1948089599609375e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.239776611328125e-05s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 141.1669921875s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 4.291534423828125e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0007276535034179688s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 31.622663736343384s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.021704673767089844s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0009889602661132812s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 8.821487426757812e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 5.245208740234375e-06s
INFO | --- Analysis for finnish-municipalities took 142.84332537651062s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.21439290046691895s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0006501674652099609s
Extra | Recovery of all triples for Norway fishery stocks dataset @PSNC took 105.33224058151245s
Performance | Total latancy measurement for Norway fishery stocks dataset @PSNC took 1.005995512008667s
Amount of data | Number of triples check for Norway fishery stocks dataset @PSNC took 8.985068798065186s
Interoperability | New terms check for Norway fishery stocks dataset @PSNC took 14.34290885925293s
Versatility | Languages check for Norway fishery stocks dataset @PSNC took 300.2388710975647s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset @PSNC took 2.3683011531829834s
Interpretability | RDF structures check for Norway fishery stocks dataset @PSNC took 0.3203427791595459s
Versatility | Serialization formats check for Norway fishery stocks dataset @PSNC took 6.819148063659668s
Availability | RDF dump link check for Norway fishery stocks dataset @PSNC took 0.40420079231262207s
License | MR license check for Norway fishery stocks dataset @PSNC took 0.8168840408325195s
License | HR license check for Norway fishery stocks dataset @PSNC took 300.1714472770691s
Amount of data | Number of property check for Norway fishery stocks dataset @PSNC took 0.2064955234527588s
Understandability | Number of label check for Norway fishery stocks dataset @PSNC took 3.0800044536590576s
Understandability | URI regex check for Norway fishery stocks dataset @PSNC took 1.2459149360656738s
Understandability | Vocabs check for Norway fishery stocks dataset @PSNC took 0.6208488941192627s
Verifiability | Authors check for Norway fishery stocks dataset @PSNC took 0.21898555755615234s
Verifiability | Publishers check for Norway fishery stocks dataset @PSNC took 0.25135302543640137s
Performance | Throughput check for Norway fishery stocks dataset @PSNC took 11.42557668685913s
Amount of data | Check the number of entities for Norway fishery stocks dataset @PSNC took 7.343292236328125e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset @PSNC took 0.18813681602478027s
Interlinking | sameAs chians check for Norway fishery stocks dataset @PSNC took 0.20251965522766113s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.4436454772949219s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.4271507263183594s
Timeliness | dataset update frequency check for Norway fishery stocks dataset @PSNC took 5.312131643295288s
Currency | Creation date check for Norway fishery stocks dataset @PSNC took 0.4653162956237793s
Currency | Modification date check for Norway fishery stocks dataset @PSNC took 0.21823954582214355s
Rep.Conc. | URIs length for Norway fishery stocks dataset @PSNC took 145.58799195289612s
Interoperability | New vocabularies check for Norway fishery stocks dataset @PSNC took 1.2874603271484375e-05s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset @PSNC took 0.2170114517211914s
Accuracy | Check Functional Property for Norway fishery stocks dataset @PSNC took 0.3168911933898926s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset @PSNC took 0.3896970748901367s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset @PSNC took 35.43664312362671s
Accuracy | Check White space in annotation for Norway fishery stocks dataset @PSNC took 2.6935768127441406s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset @PSNC took 2.685267210006714s
Consistency | Disjoint class check for Norway fishery stocks dataset @PSNC took 0.213942289352417s
Consistency | Check Misplaced properties for Norway fishery stocks dataset @PSNC took 88.15467429161072s
Consistency | Misplaced classes for Norway fishery stocks dataset @PSNC took 8.440043926239014s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset @PSNC took 31.757610082626343s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset @PSNC took 1.3921425342559814s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset @PSNC took 88.7987539768219s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset @PSNC took 2.7847509384155273s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset @PSNC took 0.5339584350585938s
Security | Sign check for Norway fishery stocks dataset @PSNC took 0.6981358528137207s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset @PSNC took 16.559861660003662s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 28.37524962425232s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.021074771881103516s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 4.792213439941406e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 1.239776611328125e-05s
INFO | --- Analysis for Fishery_Stock_Dataset took 2415.621211051941s
Availability | SPARQL endpoint availability check for Fishes of Texas took 9.059906005859375e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0006930828094482422s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.3772869110107422s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.023001909255981445s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0008869171142578125s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 9.822845458984375e-05s
Believability | Calculation of trust value for Fishes of Texas took 1.1682510375976562e-05s
INFO | --- Analysis for fishes-of-texas took 252.58544969558716s
Availability | SPARQL endpoint availability check for flickr? wrappr took 8.845329284667969e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 30.03096842765808s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.021987438201904297s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.52587890625e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 0.000102996826171875s
Believability | Calculation of trust value for flickr? wrappr took 1.1920928955078125e-05s
INFO | --- Analysis for flickr-wrappr took 143.5102105140686s
Availability | SPARQL endpoint availability check for Future land use simulation model took 8.368492126464844e-05s
Availability | VoID file availability check for Future land use simulation model took 0.00067901611328125s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 22.476269721984863s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.02136850357055664s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.457069396972656e-05s
Believability | Calculation of trust value for Future land use simulation model took 1.239776611328125e-05s
INFO | --- Analysis for FLUS took 154.63909244537354s
Availability | SPARQL endpoint availability check for Flybase took 1.1333820819854736s
Availability | VoID file availability check for Flybase took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for Flybase took 26.21263575553894s
Reputation | Calculation of the PageRank for Flybase took 0.021323204040527344s
Interlinking | Calculation of Degree of Connection for Flybase took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Flybase took 4.076957702636719e-05s
Believability | Calculation of trust value for Flybase took 1.1920928955078125e-05s
INFO | --- Analysis for flybase took 144.3101167678833s
Availability | SPARQL endpoint availability check for Flyted took 0.8986458778381348s
Availability | VoID file availability check for Flyted took 0.0006103515625s
Completeness | Calculation of interlinking completeness for Flyted took 28.592406034469604s
Reputation | Calculation of the PageRank for Flyted took 0.02113795280456543s
Interlinking | Calculation of Degree of Connection for Flyted took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.933906555175781e-05s
Believability | Calculation of trust value for Flyted took 1.239776611328125e-05s
INFO | --- Analysis for flyted took 170.45710158348083s
Availability | SPARQL endpoint availability check for Foodista took 6.42499303817749s
Availability | VoID file availability check for Foodista took 0.000690460205078125s
Completeness | Calculation of interlinking completeness for Foodista took 30.576541423797607s
Reputation | Calculation of the PageRank for Foodista took 0.021035194396972656s
Interlinking | Calculation of Degree of Connection for Foodista took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Foodista took 3.337860107421875e-05s
Believability | Calculation of trust value for Foodista took 1.1920928955078125e-05s
INFO | --- Analysis for foodista took 246.03985118865967s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.28593993186950684s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.29909658432006836s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.021151304244995117s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007789134979248047s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 8.726119995117188e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.1205673217773438e-05s
INFO | --- Analysis for foodpedia took 155.02564072608948s
Availability | SPARQL endpoint availability check for FORGE Course information took 0.8925933837890625s
Availability | VoID file availability check for FORGE Course information took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for FORGE Course information took 28.361010789871216s
Reputation | Calculation of the PageRank for FORGE Course information took 0.020987749099731445s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 3.337860107421875e-05s
Believability | Calculation of trust value for FORGE Course information took 1.0728836059570312e-05s
INFO | --- Analysis for forge-course-information took 128.7402355670929s
Availability | SPARQL endpoint availability check for FrameBase schema took 4.1961669921875e-05s
Availability | VoID file availability check for FrameBase schema took 0.0006322860717773438s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.299544095993042s
Reputation | Calculation of the PageRank for FrameBase schema took 0.021273374557495117s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.839897155761719e-05s
Believability | Calculation of trust value for FrameBase schema took 1.1682510375976562e-05s
INFO | --- Analysis for framebase-schema took 199.59833478927612s
Availability | SPARQL endpoint availability check for Framester took 0.7385768890380859s
Availability | VoID file availability check for Framester took 0.0006990432739257812s
Extra | Recovery of all triples for Framester took 60.53826451301575s
Performance | Total latancy measurement for Framester took 2.083993911743164s
Amount of data | Number of triples check for Framester took 55.037466049194336s
Versatility | Languages check for Framester took 60.55506181716919s
Interpretability | Number of blank nodes check for Framester took 0.5723509788513184s
Interpretability | RDF structures check for Framester took 1.2852351665496826s
Versatility | Serialization formats check for Framester took 1.4095442295074463s
Availability | RDF dump link check for Framester took 4.908158302307129s
License | MR license check for Framester took 2.1882498264312744s
License | HR license check for Framester took 60.532530069351196s
Amount of data | Number of property check for Framester took 0.45812344551086426s
Understandability | Number of label check for Framester took 13.312927484512329s
Understandability | URI regex check for Framester took 1.535461664199829s
Understandability | Vocabs check for Framester took 0.64247727394104s
Verifiability | Authors check for Framester took 0.8743412494659424s
Verifiability | Publishers check for Framester took 0.6437375545501709s
Performance | Throughput check for Framester took 12.494192600250244s
Amount of data | Check the number of entities for Framester took 0.00011563301086425781s
Verifiability | Contribs. check for Framester took 0.909947395324707s
Interlinking | sameAs chians check for Framester took 0.64017653465271s
Interlinking | skos check for Framester took 1.655411958694458s
Interlinking | skos check for Framester took 0.446225643157959s
Timeliness | dataset update frequency check for Framester took 0.4654545783996582s
Currency | Creation date check for Framester took 1.3117163181304932s
Currency | Modification date check for Framester took 1.0398571491241455s
Rep.Conc. | URIs length for Framester took 121.07998013496399s
Interoperability | New vocabularies check for Framester took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for Framester took 0.4426236152648926s
Accuracy | Check Functional Property for Framester took 0.5649116039276123s
Accuracy | Check Inverse Functional Property for Framester took 0.5371918678283691s
Consistency | Disjoint class check for Framester took 0.6239423751831055s
Consistency | Misplaced classes for Framester took 0.5638163089752197s
Consistency | Check Ontology hijacking for Framester took 60.56579279899597s
Consistency | Check Invalid usage of undefined properties for Framester took 61.80323505401611s
Conciseness | Check Extensional conciseness for Framester took 0.00019693374633789062s
Conciseness | Check Intensional conciseness for Framester took 0.6277999877929688s
Security | Sign check for Framester took 1.5821325778961182s
Completeness | Calculation of interlinking completeness for Framester took 30.126177549362183s
Reputation | Calculation of the PageRank for Framester took 0.0210421085357666s
Interlinking | Calculation of Degree of Connection for Framester took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Framester took 8.726119995117188e-05s
Interoperability | Check the re-using of existing vocabs for Framester took 1.1920928955078125e-06s
Believability | Calculation of trust value for Framester took 1.1205673217773438e-05s
INFO | --- Analysis for framester took 1236.9461307525635s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.09656572341918945s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.000274658203125s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 29.55123519897461s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.021091461181640625s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 0.00014519691467285156s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0015723705291748047s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 0.0001983642578125s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 1.33514404296875e-05s
INFO | --- Analysis for frb-linked-data took 206.12673592567444s
Availability | SPARQL endpoint availability check for 1989shack Inc. E-Commerce  took 4.9114227294921875e-05s
Availability | VoID file availability check for 1989shack Inc. E-Commerce  took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for 1989shack Inc. E-Commerce  took 0.3151516914367676s
Reputation | Calculation of the PageRank for 1989shack Inc. E-Commerce  took 0.020881175994873047s
Interlinking | Calculation of Degree of Connection for 1989shack Inc. E-Commerce  took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for 1989shack Inc. E-Commerce  took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for 1989shack Inc. E-Commerce  took 0.00028014183044433594s
Believability | Calculation of trust value for 1989shack Inc. E-Commerce  took 1.1920928955078125e-05s
INFO | --- Analysis for freebase took 158.28587889671326s
Availability | SPARQL endpoint availability check for Freeyork took 4.363059997558594e-05s
Availability | VoID file availability check for Freeyork took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for Freeyork took 23.900630474090576s
Reputation | Calculation of the PageRank for Freeyork took 0.02124166488647461s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.0001201629638671875s
Believability | Calculation of trust value for Freeyork took 7.3909759521484375e-06s
INFO | --- Analysis for freeyork-org took 112.80947303771973s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.6985578536987305s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0006723403930664062s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.28902292251586914s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.02079629898071289s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.581710815429688e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 9.5367431640625e-06s
INFO | --- Analysis for fu-berlin-cordis took 4.79627799987793s
Availability | SPARQL endpoint availability check for DailyMed took 0.9734835624694824s
Availability | VoID file availability check for DailyMed took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for DailyMed took 24.59353733062744s
Reputation | Calculation of the PageRank for DailyMed took 0.020871877670288086s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for DailyMed took 0.00010800361633300781s
Believability | Calculation of trust value for DailyMed took 1.1920928955078125e-05s
INFO | --- Analysis for fu-berlin-dailymed took 136.27043628692627s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.7119753360748291s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0006804466247558594s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.517085075378418s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.021310806274414062s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 0.00010442733764648438s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 1.1920928955078125e-05s
INFO | --- Analysis for fu-berlin-dblp took 201.8555827140808s
Availability | SPARQL endpoint availability check for Diseasome took 0.6944718360900879s
Availability | VoID file availability check for Diseasome took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for Diseasome took 24.075978755950928s
Reputation | Calculation of the PageRank for Diseasome took 0.02108931541442871s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.0001246929168701172s
Believability | Calculation of trust value for Diseasome took 1.239776611328125e-05s
INFO | --- Analysis for fu-berlin-diseasome took 160.83063077926636s
Availability | SPARQL endpoint availability check for DrugBank took 0.7216598987579346s
Availability | VoID file availability check for DrugBank took 0.000606536865234375s
Completeness | Calculation of interlinking completeness for DrugBank took 0.3656327724456787s
Reputation | Calculation of the PageRank for DrugBank took 0.020957231521606445s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00012254714965820312s
Believability | Calculation of trust value for DrugBank took 1.1682510375976562e-05s
INFO | --- Analysis for fu-berlin-drugbank took 116.58659601211548s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.7077162265777588s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.33719944953918457s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.02126312255859375s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 3.4809112548828125e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 1.239776611328125e-05s
INFO | --- Analysis for fu-berlin-ec-competition took 54.172388792037964s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.703510046005249s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0006601810455322266s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 23.83753490447998s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.021302223205566406s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.748603820800781e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 9.059906005859375e-06s
INFO | --- Analysis for fu-berlin-euraxess took 99.50725197792053s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.7041816711425781s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.3124501705169678s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.02174997329711914s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 8.797645568847656e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 1.239776611328125e-05s
INFO | --- Analysis for fu-berlin-eures took 50.77099633216858s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.7050755023956299s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 24.02680802345276s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.021715164184570312s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0010447502136230469s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 0.00013685226440429688s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 9.5367431640625e-06s
INFO | --- Analysis for fu-berlin-eurostat took 130.1650583744049s
Availability | SPARQL endpoint availability check for MediCare took 0.7145006656646729s
Availability | VoID file availability check for MediCare took 0.0006463527679443359s
Completeness | Calculation of interlinking completeness for MediCare took 31.568055629730225s
Reputation | Calculation of the PageRank for MediCare took 0.021701335906982422s
Interlinking | Calculation of Degree of Connection for MediCare took 2.288818359375e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0012159347534179688s
Interlinking | Calculation of Clustering coefficient for MediCare took 7.510185241699219e-05s
Believability | Calculation of trust value for MediCare took 7.152557373046875e-06s
INFO | --- Analysis for fu-berlin-medicare took 218.6997663974762s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.705510139465332s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0005898475646972656s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 29.00754737854004s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.02096867561340332s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 8.130073547363281e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 1.1205673217773438e-05s
INFO | --- Analysis for fu-berlin-project-gutenberg took 81.89137816429138s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.7472336292266846s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 30.741790294647217s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.021358966827392578s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 0.0001068115234375s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 1.5735626220703125e-05s
INFO | --- Analysis for fu-berlin-sider took 196.58741974830627s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 30.56279683113098s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 30.263885259628296s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.022139549255371094s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0011670589447021484s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 0.00011444091796875s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 1.2636184692382812e-05s
INFO | --- Analysis for fu-berlin-stitch took 226.93273949623108s
Availability | SPARQL endpoint availability check for fvdb took 4.172325134277344e-05s
Availability | VoID file availability check for fvdb took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for fvdb took 24.425594091415405s
Reputation | Calculation of the PageRank for fvdb took 0.021117210388183594s
Interlinking | Calculation of Degree of Connection for fvdb took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for fvdb took 5.1021575927734375e-05s
Believability | Calculation of trust value for fvdb took 1.430511474609375e-05s
INFO | --- Analysis for fv took 112.96740889549255s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 8.678436279296875e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0007326602935791016s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 31.223053216934204s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.022195816040039062s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 3.504753112792969e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 1.1205673217773438e-05s
INFO | --- Analysis for GACS took 88.15182876586914s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0001468658447265625s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0010616779327392578s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.3031580448150635s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.026898622512817383s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.001451730728149414s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 7.390975952148438e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 1.1920928955078125e-05s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 89.43249607086182s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 6.67572021484375e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 24.375787019729614s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.02116560935974121s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.00010848045349121094s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 1.1682510375976562e-05s
INFO | --- Analysis for garnicaplywood took 108.67692565917969s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 4.1961669921875e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.3843543529510498s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.021086931228637695s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.00010895729064941406s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.2636184692382812e-05s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 196.35130143165588s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.4047353267669678s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.32520174980163574s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.020931243896484375s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 0.00010848045349121094s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for gemet took 100.60266494750977s
Availability | SPARQL endpoint availability check for gemet-annotated took 8.320808410644531e-05s
Availability | VoID file availability check for gemet-annotated took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for gemet-annotated took 27.938292980194092s
Reputation | Calculation of the PageRank for gemet-annotated took 0.021176815032958984s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 4.100799560546875e-05s
Believability | Calculation of trust value for gemet-annotated took 7.152557373046875e-06s
INFO | --- Analysis for gemet-annotated took 107.26608157157898s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.7849416732788086s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 23.431543588638306s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.020998716354370117s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 4.9114227294921875e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 1.2159347534179688e-05s
INFO | --- Analysis for gene-expression-atlas-rdf took 122.1106948852539s
Availability | SPARQL endpoint availability check for Super Ontology took 1.48240065574646s
Availability | VoID file availability check for Super Ontology took 0.000518798828125s
Completeness | Calculation of interlinking completeness for Super Ontology took 29.93273115158081s
Reputation | Calculation of the PageRank for Super Ontology took 0.020821094512939453s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for Super Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for Generalized_Super_Ontology took 163.9347596168518s
Availability | SPARQL endpoint availability check for Geographic detector model took 9.655952453613281e-05s
Availability | VoID file availability check for Geographic detector model took 0.0006704330444335938s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.35108160972595215s
Reputation | Calculation of the PageRank for Geographic detector model took 0.021325111389160156s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 4.124641418457031e-05s
Believability | Calculation of trust value for Geographic detector model took 1.0967254638671875e-05s
INFO | --- Analysis for GeoDetector took 212.69104480743408s
Availability | SPARQL endpoint availability check for geodomainwn took 4.315376281738281e-05s
Availability | VoID file availability check for geodomainwn took 0.0006253719329833984s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.3142738342285156s
Reputation | Calculation of the PageRank for geodomainwn took 0.020856618881225586s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 4.839897155761719e-05s
Believability | Calculation of trust value for geodomainwn took 1.1444091796875e-05s
INFO | --- Analysis for geodomainwn took 112.36983752250671s
Availability | SPARQL endpoint availability check for GeoEcuador took 20.037779331207275s
Availability | VoID file availability check for GeoEcuador took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.31625819206237793s
Reputation | Calculation of the PageRank for GeoEcuador took 0.021927595138549805s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 8.177757263183594e-05s
Believability | Calculation of trust value for GeoEcuador took 1.2159347534179688e-05s
INFO | --- Analysis for geoecuador took 210.83257031440735s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 2.69767427444458s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0011513233184814453s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.41080522537231445s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.020853757858276367s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 8.440017700195312e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 1.2159347534179688e-05s
INFO | --- Analysis for geographic-names-information-system-gnis took 333.87456607818604s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.42824888229370117s
Availability | VoID file availability check for GeoLinkedData took 0.0005702972412109375s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 28.64455533027649s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.02145075798034668s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 9.72747802734375e-05s
Believability | Calculation of trust value for GeoLinkedData took 8.344650268554688e-06s
INFO | --- Analysis for geolinkeddata took 119.29046583175659s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.20565390586853027s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.15681672096252441s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 9.760420083999634s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.39990997314453125s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.16289401054382324s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.4125885963439941s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.1998910903930664s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.17428970336914062s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.2127244472503662s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.09160208702087402s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.10778331756591797s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.0770876407623291s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.09795594215393066s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 2.4450745582580566s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.10682964324951172s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.11385250091552734s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.1401832103729248s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.09777498245239258s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.07571578025817871s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.10531306266784668s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.270705699920654s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 8.082389831542969e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.06252074241638184s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.06186270713806152s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.09602904319763184s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.06967854499816895s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.06933784484863281s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.15752530097961426s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.1745283603668213s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.3465650081634521s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 4.199568510055542s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.09813642501831055s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.07696652412414551s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06940722465515137s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.32500267028808594s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.0074923038482666016s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.2326643466949463s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.07168316841125488s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.20863080024719238s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.541820764541626s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 3.2439842224121094s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.4839825630187988s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.639094591140747s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.17937159538269043s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.07553911209106445s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 1.1063756942749023s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.4954979419708252s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.02147960662841797s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.869171142578125e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 3.969780921936035s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 1.2159347534179688e-05s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 235.14015340805054s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 4.172325134277344e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.000579833984375s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.3795027732849121s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.020712852478027344s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0004658699035644531s
Believability | Calculation of trust value for GeoNames Semantic Web took 1.2636184692382812e-05s
INFO | --- Analysis for geonames-semantic-web took 93.78687834739685s
Availability | SPARQL endpoint availability check for Geospatial World  took 9.584426879882812e-05s
Availability | VoID file availability check for Geospatial World  took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.3322439193725586s
Reputation | Calculation of the PageRank for Geospatial World  took 0.021022558212280273s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0008528232574462891s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00011920928955078125s
Believability | Calculation of trust value for Geospatial World  took 1.811981201171875e-05s
INFO | --- Analysis for geospatialworld-net took 83.14685559272766s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.5617504119873047s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.3683333396911621s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.021568775177001953s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00015091896057128906s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 2.1696090698242188e-05s
INFO | --- Analysis for geospecies took 102.00250792503357s
Availability | SPARQL endpoint availability check for GeoWordNet took 0.0001010894775390625s
Availability | VoID file availability check for GeoWordNet took 0.0009906291961669922s
Completeness | Calculation of interlinking completeness for GeoWordNet took 29.384708166122437s
Reputation | Calculation of the PageRank for GeoWordNet took 0.021345853805541992s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 6.842613220214844e-05s
Believability | Calculation of trust value for GeoWordNet took 1.1444091796875e-05s
INFO | --- Analysis for geowordnet took 197.39195108413696s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.09780359268188477s
Availability | VoID file availability check for German labor law thesaurus took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.3357889652252197s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.02270221710205078s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0015888214111328125s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 0.00017595291137695312s
Believability | Calculation of trust value for German labor law thesaurus took 1.6450881958007812e-05s
INFO | --- Analysis for german-labor-law-thesaurus took 168.0632164478302s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 8.940696716308594e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0007481575012207031s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 27.943900108337402s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.020776748657226562s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 5.245208740234375e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 1.2636184692382812e-05s
INFO | --- Analysis for germlex took 135.25342845916748s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.40436816215515137s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.28263187408447266s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.021147727966308594s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0008056163787841797s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.608268737792969e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.2874603271484375e-05s
INFO | --- Analysis for gesis-thesoz took 163.5098958015442s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.7155709266662598s
Availability | VoID file availability check for Art & Architecture Thesaurus took 2.780500888824463s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 25.773380994796753s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.02103590965270996s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 8.7738037109375e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for getty-aat took 178.14320373535156s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.4455804824829102s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.4540977478027344s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.02098989486694336s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 6.365776062011719e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 1.1444091796875e-05s
INFO | --- Analysis for getty-tgn took 105.26898527145386s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 262.6128237247467s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0008046627044677734s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 26.998390913009644s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.021725177764892578s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007932186126708984s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 4.100799560546875e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 9.5367431640625e-06s
INFO | --- Analysis for gipuzkoademografia took 656.1109395027161s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 4.7206878662109375e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0006811618804931641s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.3236713409423828s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.02142190933227539s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 2.7894973754882812e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0010716915130615234s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 4.553794860839844e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 1.0967254638671875e-05s
INFO | --- Analysis for glastonbury-2011 took 149.37863898277283s
Availability | SPARQL endpoint availability check for Global Change Information System took 40.037192583084106s
Availability | VoID file availability check for Global Change Information System took 0.0007579326629638672s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.3528468608856201s
Reputation | Calculation of the PageRank for Global Change Information System took 0.0220487117767334s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 4.100799560546875e-05s
Believability | Calculation of trust value for Global Change Information System took 1.2874603271484375e-05s
INFO | --- Analysis for global-change-information-system took 230.30332946777344s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 8.821487426757812e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0006546974182128906s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 28.336015939712524s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.02104020118713379s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0009739398956298828s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 6.628036499023438e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 6.9141387939453125e-06s
INFO | --- Analysis for global-hunger-index-2011 took 147.0265552997589s
Availability | SPARQL endpoint availability check for Glottolog took 0.00011587142944335938s
Availability | VoID file availability check for Glottolog took 0.0007328987121582031s
Completeness | Calculation of interlinking completeness for Glottolog took 27.150761365890503s
Reputation | Calculation of the PageRank for Glottolog took 0.02263021469116211s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Glottolog took 6.508827209472656e-05s
Believability | Calculation of trust value for Glottolog took 1.1444091796875e-05s
INFO | --- Analysis for glottolog took 141.20552945137024s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 8.726119995117188e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0007784366607666016s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 25.06388211250305s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.020804405212402344s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.000118255615234375s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 1.2159347534179688e-05s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 126.05845975875854s
Availability | SPARQL endpoint availability check for 1121 took 4.38690185546875e-05s
Availability | VoID file availability check for 1121 took 0.0007910728454589844s
Completeness | Calculation of interlinking completeness for 1121 took 0.2951502799987793s
Reputation | Calculation of the PageRank for 1121 took 0.021577119827270508s
Interlinking | Calculation of Degree of Connection for 1121 took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for 1121 took 3.910064697265625e-05s
Believability | Calculation of trust value for 1121 took 1.4543533325195312e-05s
INFO | --- Analysis for God_ took 61.38326811790466s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 0.0009272098541259766s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0007193088531494141s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 24.728872060775757s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.023627281188964844s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0009589195251464844s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 7.033348083496094e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 1.239776611328125e-05s
INFO | --- Analysis for gold took 135.60559058189392s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 4.315376281738281e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0005769729614257812s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 30.140209197998047s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.025238513946533203s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007710456848144531s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 8.296966552734375e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 1.2159347534179688e-05s
INFO | --- Analysis for googleart-wrapper took 115.11398243904114s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.0981903076171875s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.3383784294128418s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.021358489990234375s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 4.9591064453125e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 1.0967254638671875e-05s
INFO | --- Analysis for govagribus-denmark took 172.17222571372986s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.3902156352996826s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0006787776947021484s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.3020012378692627s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.021662473678588867s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 0.00010061264038085938s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 141.57239365577698s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 2.6191930770874023s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0006859302520751953s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 23.867336750030518s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.02079033851623535s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 9.369850158691406e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 5.0067901611328125e-06s
INFO | --- Analysis for govtrack took 150.62724137306213s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 7.486343383789062e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.2868950366973877s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.022026538848876953s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 6.699562072753906e-05s
Believability | Calculation of trust value for greek-administrative-geography took 1.1682510375976562e-05s
INFO | --- Analysis for greek-administrative-geography took 114.28416085243225s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.174332857131958s
Availability | VoID file availability check for Greek Wordnet took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 27.57625675201416s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.022871732711791992s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 5.173683166503906e-05s
Believability | Calculation of trust value for Greek Wordnet took 1.2159347534179688e-05s
INFO | --- Analysis for greek-wordnet took 200.36772990226746s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.30011916160583496s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0008494853973388672s
Extra | Recovery of all triples for Greek prisons releases Jan 2018 - Dec 2023 took 12.343549013137817s
Performance | Total latancy measurement for Greek prisons releases Jan 2018 - Dec 2023 took 0.6384730339050293s
Amount of data | Number of triples check for Greek prisons releases Jan 2018 - Dec 2023 took 0.851823091506958s
Interoperability | New terms check for Greek prisons releases Jan 2018 - Dec 2023 took 1.6550030708312988s
Versatility | Languages check for Greek prisons releases Jan 2018 - Dec 2023 took 2.0748651027679443s
Interpretability | Number of blank nodes check for Greek prisons releases Jan 2018 - Dec 2023 took 0.5454239845275879s
Interpretability | RDF structures check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13204097747802734s
Versatility | Serialization formats check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12920689582824707s
Availability | RDF dump link check for Greek prisons releases Jan 2018 - Dec 2023 took 0.14414310455322266s
License | MR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13393163681030273s
License | HR license check for Greek prisons releases Jan 2018 - Dec 2023 took 0.460507869720459s
Amount of data | Number of property check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12458300590515137s
Understandability | Number of label check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1943955421447754s
Understandability | URI regex check for Greek prisons releases Jan 2018 - Dec 2023 took 0.25174665451049805s
Understandability | Vocabs check for Greek prisons releases Jan 2018 - Dec 2023 took 0.13283443450927734s
Verifiability | Authors check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1319115161895752s
Verifiability | Publishers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1251389980316162s
Performance | Throughput check for Greek prisons releases Jan 2018 - Dec 2023 took 10.679213047027588s
Amount of data | Check the number of entities for Greek prisons releases Jan 2018 - Dec 2023 took 0.00010466575622558594s
Verifiability | Contribs. check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12369704246520996s
Interlinking | sameAs chians check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12462162971496582s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12267303466796875s
Interlinking | skos check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1148366928100586s
Timeliness | dataset update frequency check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1303102970123291s
Currency | Creation date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.25275135040283203s
Currency | Modification date check for Greek prisons releases Jan 2018 - Dec 2023 took 0.24470996856689453s
Rep.Conc. | URIs length for Greek prisons releases Jan 2018 - Dec 2023 took 8.310002088546753s
Interoperability | New vocabularies check for Greek prisons releases Jan 2018 - Dec 2023 took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Greek prisons releases Jan 2018 - Dec 2023 took 0.11958479881286621s
Accuracy | Check Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.12144660949707031s
Accuracy | Check Inverse Functional Property for Greek prisons releases Jan 2018 - Dec 2023 took 0.11733126640319824s
Accuracy | Check Empty annotation labels for Greek prisons releases Jan 2018 - Dec 2023 took 2.8025200366973877s
Accuracy | Check White space in annotation for Greek prisons releases Jan 2018 - Dec 2023 took 0.2882242202758789s
Accuracy | Check Datatype consistency for Greek prisons releases Jan 2018 - Dec 2023 took 4.849608659744263s
Consistency | Disjoint class check for Greek prisons releases Jan 2018 - Dec 2023 took 0.12384200096130371s
Consistency | Check Misplaced properties for Greek prisons releases Jan 2018 - Dec 2023 took 1.3325083255767822s
Consistency | Check Ontology hijacking for Greek prisons releases Jan 2018 - Dec 2023 took 3.1534042358398438s
Consistency | Check Invalid usage of undefined classes for Greek prisons releases Jan 2018 - Dec 2023 took 1.3701722621917725s
Consistency | Check Invalid usage of undefined properties for Greek prisons releases Jan 2018 - Dec 2023 took 2.6086690425872803s
Conciseness | Check Extensional conciseness for Greek prisons releases Jan 2018 - Dec 2023 took 2.9395034313201904s
Security | Sign check for Greek prisons releases Jan 2018 - Dec 2023 took 0.1296398639678955s
Availability | Check URIs Dereferenciability for Greek prisons releases Jan 2018 - Dec 2023 took 4852.725338935852s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 1.6944084167480469s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.02155756950378418s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.52587890625e-05s
Interoperability | Check the re-using of existing vocabs for Greek prisons releases Jan 2018 - Dec 2023 took 1.6689300537109375e-06s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 1.2874603271484375e-05s
INFO | --- Analysis for greek_prisons_releases took 5082.953032255173s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.7985174655914307s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0006430149078369141s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 28.059061527252197s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.0214841365814209s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 9.560585021972656e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.1920928955078125e-05s
INFO | --- Analysis for greekchildrensartmuseum took 92.40331196784973s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 8.7738037109375e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0008060932159423828s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 31.41919994354248s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.021096467971801758s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.0001289844512939453s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 1.1920928955078125e-05s
INFO | --- Analysis for green-competitiveness-gnoss took 95.18073606491089s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 1.5147302150726318s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 29.137344360351562s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.021528005599975586s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 5.340576171875e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 1.2874603271484375e-05s
INFO | --- Analysis for grrp took 119.06338715553284s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.935636043548584s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 30.98173952102661s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.02133321762084961s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0008747577667236328s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 8.225440979003906e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 5.9604644775390625e-06s
INFO | --- Analysis for grrt took 145.66861152648926s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.0294952392578125s
Availability | VoID file availability check for Geological Timescale took 0.0007672309875488281s
Extra | Recovery of all triples for Geological Timescale took 3.8787343502044678s
Performance | Total latancy measurement for Geological Timescale took 5.29537558555603s
Amount of data | Number of triples check for Geological Timescale took 0.4296121597290039s
Interoperability | New terms check for Geological Timescale took 2.221247911453247s
Versatility | Languages check for Geological Timescale took 1.0348119735717773s
Interpretability | Number of blank nodes check for Geological Timescale took 1.116262674331665s
Security | Check HTTPS for Geological Timescale took 0.3822174072265625s
Interpretability | RDF structures check for Geological Timescale took 0.9943876266479492s
Versatility | Serialization formats check for Geological Timescale took 1.1228315830230713s
Availability | RDF dump link check for Geological Timescale took 1.7725512981414795s
License | MR license check for Geological Timescale took 0.9202988147735596s
License | HR license check for Geological Timescale took 0.9986617565155029s
Amount of data | Number of property check for Geological Timescale took 0.9039173126220703s
Understandability | Number of label check for Geological Timescale took 0.949852705001831s
Understandability | URI regex check for Geological Timescale took 1.9377727508544922s
Understandability | Vocabs check for Geological Timescale took 1.0946245193481445s
Verifiability | Authors check for Geological Timescale took 0.9584615230560303s
Verifiability | Publishers check for Geological Timescale took 0.9641578197479248s
Performance | Throughput check for Geological Timescale took 15.906078338623047s
Amount of data | Check the number of entities for Geological Timescale took 0.026110172271728516s
Verifiability | Contribs. check for Geological Timescale took 0.9377455711364746s
Interlinking | sameAs chians check for Geological Timescale took 0.948819637298584s
Interlinking | skos check for Geological Timescale took 0.9949014186859131s
Interlinking | skos check for Geological Timescale took 1.1123459339141846s
Timeliness | dataset update frequency check for Geological Timescale took 0.9678514003753662s
Currency | Creation date check for Geological Timescale took 2.32794189453125s
Currency | Modification date check for Geological Timescale took 0.9759068489074707s
Rep.Conc. | URIs length for Geological Timescale took 2.1416022777557373s
Interoperability | New vocabularies check for Geological Timescale took 3.3046510219573975s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 0.9653818607330322s
Accuracy | Check Functional Property for Geological Timescale took 0.9722530841827393s
Accuracy | Check Inverse Functional Property for Geological Timescale took 0.9699318408966064s
Accuracy | Check Empty annotation labels for Geological Timescale took 1.277160882949829s
Accuracy | Check White space in annotation for Geological Timescale took 0.015845298767089844s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07562661170959473s
Consistency | Disjoint class check for Geological Timescale took 1.0024893283843994s
Consistency | Check Misplaced properties for Geological Timescale took 1.998807668685913s
Consistency | Misplaced classes for Geological Timescale took 1.1080944538116455s
Consistency | Check Ontology hijacking for Geological Timescale took 2.239957809448242s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.2348713874816895s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 2.2460145950317383s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.05233001708984375s
Conciseness | Check Intensional conciseness for Geological Timescale took 0.9941341876983643s
Security | Sign check for Geological Timescale took 0.9775571823120117s
Availability | Check URIs Dereferenciability for Geological Timescale took 3.1168205738067627s
Completeness | Calculation of interlinking completeness for Geological Timescale took 28.644521713256836s
Reputation | Calculation of the PageRank for Geological Timescale took 0.02273249626159668s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 2.5987625122070312e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0008223056793212891s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 9.584426879882812e-05s
Interoperability | Check the re-using of existing vocabs for Geological Timescale took 2.5051474571228027s
Believability | Calculation of trust value for Geological Timescale took 2.384185791015625e-05s
INFO | --- Analysis for GTS took 275.07051491737366s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 8.726119995117188e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0006709098815917969s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 26.638697147369385s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.020990848541259766s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 4.100799560546875e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for GTS-ont took 151.40316724777222s
Availability | SPARQL endpoint availability check for GUTSTOK  took 8.749961853027344e-05s
Availability | VoID file availability check for GUTSTOK  took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.28948283195495605s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.021625757217407227s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 3.5762786865234375e-05s
Believability | Calculation of trust value for GUTSTOK  took 9.775161743164062e-06s
INFO | --- Analysis for Guillaume_Forget took 91.21797156333923s
Availability | SPARQL endpoint availability check for Project Gutenberg took 8.821487426757812e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0008034706115722656s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.3364439010620117s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.022728681564331055s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 8.392333984375e-05s
Believability | Calculation of trust value for Project Gutenberg took 1.1682510375976562e-05s
INFO | --- Analysis for gutenberg took 116.14928984642029s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 0.00013589859008789062s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0007843971252441406s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 27.97546362876892s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.021031618118286133s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 4.100799560546875e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 1.8835067749023438e-05s
INFO | --- Analysis for gwa-ili took 164.57329440116882s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 9.775161743164062e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0007288455963134766s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 29.815539121627808s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.021002769470214844s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 4.172325134277344e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 7.152557373046875e-06s
INFO | --- Analysis for GWR took 214.09817790985107s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 8.368492126464844e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0007498264312744141s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.37549591064453125s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.026102542877197266s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 4.3392181396484375e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 1.1920928955078125e-05s
INFO | --- Analysis for HASM took 107.3552680015564s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 5.793571472167969e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 33.11320376396179s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.020955801010131836s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 3.528594970703125e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 2.2411346435546875e-05s
INFO | --- Analysis for hcls-knowledge-base took 146.59222650527954s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 3.1624133586883545s
Availability | VoID file availability check for HealthCare Ontology took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 26.511924266815186s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.021783828735351562s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 2.0742416381835938e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 4.172325134277344e-05s
Believability | Calculation of trust value for HealthCare Ontology took 1.239776611328125e-05s
INFO | --- Analysis for HealthCare_Ontology took 173.77448678016663s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 6.29425048828125e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0007693767547607422s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.33693790435791016s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.022335052490234375s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 7.891654968261719e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 8.106231689453125e-06s
INFO | --- Analysis for heartfailure took 145.19304513931274s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.89522933959961s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007762908935546875s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 29.234097719192505s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.021409034729003906s
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.2159347534179688e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 5.340576171875e-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.2874603271484375e-05s
INFO | --- Analysis for hebis-bibliographic-resources took 228.5422501564026s
Availability | SPARQL endpoint availability check for Hedatuz took 0.2506730556488037s
Availability | VoID file availability check for Hedatuz took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for Hedatuz took 26.65499234199524s
Reputation | Calculation of the PageRank for Hedatuz took 0.022247791290283203s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 6.222724914550781e-05s
Believability | Calculation of trust value for Hedatuz took 1.1444091796875e-05s
INFO | --- Analysis for hedatuz took 134.34487462043762s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.13327407836914062s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.3318057060241699s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.02125239372253418s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007903575897216797s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00015282630920410156s
Believability | Calculation of trust value for Hellenic Fire Brigade took 9.059906005859375e-06s
INFO | --- Analysis for hellenic-fire-brigade took 187.92550039291382s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.0274507999420166s
Availability | VoID file availability check for Hellenic Police took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for Hellenic Police took 29.353675842285156s
Reputation | Calculation of the PageRank for Hellenic Police took 0.02131175994873047s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00013637542724609375s
Believability | Calculation of trust value for Hellenic Police took 9.5367431640625e-06s
INFO | --- Analysis for hellenic-police took 115.2180655002594s
Availability | SPARQL endpoint availability check for Hermos took 5.316734313964844e-05s
Availability | VoID file availability check for Hermos took 0.0006847381591796875s
Completeness | Calculation of interlinking completeness for Hermos took 0.3254413604736328s
Reputation | Calculation of the PageRank for Hermos took 0.02208232879638672s
Interlinking | Calculation of Degree of Connection for Hermos took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Hermos took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for Hermos took 3.409385681152344e-05s
Believability | Calculation of trust value for Hermos took 1.1920928955078125e-05s
INFO | --- Analysis for Hermos took 155.66122341156006s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 8.821487426757812e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 26.6432843208313s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.020923614501953125s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 4.076957702636719e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 1.2874603271484375e-05s
INFO | --- Analysis for Himanshu_Mahawar took 166.7675473690033s
Availability | SPARQL endpoint availability check for HITO took 0.5144040584564209s
Availability | VoID file availability check for HITO took 0.0021648406982421875s
Extra | Recovery of all triples for HITO took 2.1617724895477295s
Performance | Total latancy measurement for HITO took 1.0233473777770996s
Amount of data | Number of triples check for HITO took 0.19830965995788574s
Interoperability | New terms check for HITO took 1.4917044639587402s
Versatility | Languages check for HITO took 0.2336750030517578s
Interpretability | Number of blank nodes check for HITO took 0.20389151573181152s
Interpretability | RDF structures check for HITO took 0.2154066562652588s
Versatility | Serialization formats check for HITO took 0.20174455642700195s
Availability | RDF dump link check for HITO took 0.20998787879943848s
License | MR license check for HITO took 0.20939898490905762s
License | HR license check for HITO took 0.22109675407409668s
Amount of data | Number of property check for HITO took 0.21645689010620117s
Understandability | Number of label check for HITO took 0.23978757858276367s
Understandability | URI regex check for HITO took 0.4347865581512451s
Understandability | Vocabs check for HITO took 0.2264997959136963s
Verifiability | Authors check for HITO took 0.21699070930480957s
Verifiability | Publishers check for HITO took 0.22711730003356934s
Performance | Throughput check for HITO took 10.86997675895691s
Amount of data | Check the number of entities for HITO took 0.00011491775512695312s
Verifiability | Contribs. check for HITO took 0.2131335735321045s
Interlinking | sameAs chians check for HITO took 0.20128655433654785s
Interlinking | skos check for HITO took 0.20473957061767578s
Interlinking | skos check for HITO took 0.20953726768493652s
Timeliness | dataset update frequency check for HITO took 0.21437478065490723s
Currency | Creation date check for HITO took 0.39432358741760254s
Currency | Modification date check for HITO took 0.4255545139312744s
Rep.Conc. | URIs length for HITO took 1.1153788566589355s
Interoperability | New vocabularies check for HITO took 5.4836273193359375e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.20239663124084473s
Accuracy | Check Functional Property for HITO took 0.20048022270202637s
Accuracy | Check Inverse Functional Property for HITO took 0.2082958221435547s
Accuracy | Check Empty annotation labels for HITO took 0.5382218360900879s
Accuracy | Check White space in annotation for HITO took 0.013536214828491211s
Accuracy | Check Datatype consistency for HITO took 0.07556653022766113s
Consistency | Disjoint class check for HITO took 0.19300341606140137s
Consistency | Check Misplaced properties for HITO took 0.5420105457305908s
Consistency | Misplaced classes for HITO took 0.3730027675628662s
Consistency | Check Ontology hijacking for HITO took 1.7525355815887451s
Consistency | Check Invalid usage of undefined classes for HITO took 1.2255990505218506s
Consistency | Check Invalid usage of undefined properties for HITO took 1.5124731063842773s
Conciseness | Check Extensional conciseness for HITO took 0.06250333786010742s
Conciseness | Check Intensional conciseness for HITO took 0.20386528968811035s
Security | Sign check for HITO took 0.20522093772888184s
Availability | Check URIs Dereferenciability for HITO took 2688.4234716892242s
Completeness | Calculation of interlinking completeness for HITO took 26.908052444458008s
Reputation | Calculation of the PageRank for HITO took 0.1750810146331787s
Interlinking | Calculation of Degree of Connection for HITO took 0.0003101825714111328s
Interlinking | Calculation of Centrality for HITO took 0.0061283111572265625s
Interlinking | Calculation of Clustering coefficient for HITO took 0.0005977153778076172s
Interoperability | Check the re-using of existing vocabs for HITO took 9.775161743164062e-06s
Believability | Calculation of trust value for HITO took 4.029273986816406e-05s
INFO | --- Analysis for hito took 2937.5171267986298s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 15.660218477249146s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0024123191833496094s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 24.642406940460205s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.17067885398864746s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 6.008148193359375e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.006760835647583008s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 0.00019049644470214844s
Believability | Calculation of trust value for Hoa Thịnh Phát took 3.814697265625e-05s
INFO | --- Analysis for Hoa_Thinh_Phat took 159.11486196517944s
Availability | SPARQL endpoint availability check for Homologene took 0.0004134178161621094s
Availability | VoID file availability check for Homologene took 0.0018219947814941406s
Completeness | Calculation of interlinking completeness for Homologene took 0.39220285415649414s
Reputation | Calculation of the PageRank for Homologene took 0.17351937294006348s
Interlinking | Calculation of Degree of Connection for Homologene took 5.936622619628906e-05s
Interlinking | Calculation of Centrality for Homologene took 0.006499528884887695s
Interlinking | Calculation of Clustering coefficient for Homologene took 0.00021147727966308594s
Believability | Calculation of trust value for Homologene took 6.103515625e-05s
INFO | --- Analysis for homologene took 136.5800437927246s
Availability | SPARQL endpoint availability check for gseg took 0.00031280517578125s
Availability | VoID file availability check for gseg took 0.0018703937530517578s
Completeness | Calculation of interlinking completeness for gseg took 25.524735689163208s
Reputation | Calculation of the PageRank for gseg took 0.1775040626525879s
Interlinking | Calculation of Degree of Connection for gseg took 9.226799011230469e-05s
Interlinking | Calculation of Centrality for gseg took 0.006672859191894531s
Interlinking | Calculation of Clustering coefficient for gseg took 0.000179290771484375s
Believability | Calculation of trust value for gseg took 3.552436828613281e-05s
INFO | --- Analysis for hongse took 81.22377061843872s
Availability | SPARQL endpoint availability check for Noticias Universia took 0.0003008842468261719s
Availability | VoID file availability check for Noticias Universia took 0.001789093017578125s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.4205472469329834s
Reputation | Calculation of the PageRank for Noticias Universia took 0.16784930229187012s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 5.53131103515625e-05s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0061986446380615234s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 0.0001728534698486328s
Believability | Calculation of trust value for Noticias Universia took 3.695487976074219e-05s
INFO | --- Analysis for http-data-noticias-universia-net took 35.71299505233765s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0002994537353515625s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0023109912872314453s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.38283848762512207s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.18326568603515625s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 6.175041198730469e-05s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.005833625793457031s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0001842975616455078s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 3.695487976074219e-05s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 86.4386682510376s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 2.7111995220184326s
Availability | VoID file availability check for COURAGE Dataset took 0.002202749252319336s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 27.729641675949097s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.17602038383483887s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 5.817413330078125e-05s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.006428718566894531s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 0.00021004676818847656s
Believability | Calculation of trust value for COURAGE Dataset took 3.814697265625e-05s
INFO | --- Analysis for http:cultural-opposition.eu took 116.29350757598877s
Availability | SPARQL endpoint availability check for RoadTrb took 0.0003154277801513672s
Availability | VoID file availability check for RoadTrb took 0.00194549560546875s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.38509249687194824s
Reputation | Calculation of the PageRank for RoadTrb took 0.17357254028320312s
Interlinking | Calculation of Degree of Connection for RoadTrb took 5.7220458984375e-05s
Interlinking | Calculation of Centrality for RoadTrb took 0.007138252258300781s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 0.00018858909606933594s
Believability | Calculation of trust value for RoadTrb took 7.939338684082031e-05s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 134.76026248931885s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 0.00032401084899902344s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.002132892608642578s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 29.561771631240845s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.17396092414855957s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 5.7220458984375e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0063517093658447266s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 0.0002751350402832031s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 3.790855407714844e-05s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 216.2700126171112s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 0.0003070831298828125s
Availability | VoID file availability check for Polictical History of Pakistan took 0.0019156932830810547s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 30.49633550643921s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.17365503311157227s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 5.9604644775390625e-05s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0065305233001708984s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 0.00010848045349121094s
Believability | Calculation of trust value for Polictical History of Pakistan took 4.792213439941406e-05s
INFO | --- Analysis for http:pakistan.com took 167.680602312088s
Availability | SPARQL endpoint availability check for CEDICT took 0.0003044605255126953s
Availability | VoID file availability check for CEDICT took 0.0023086071014404297s
Completeness | Calculation of interlinking completeness for CEDICT took 0.439373254776001s
Reputation | Calculation of the PageRank for CEDICT took 0.17487883567810059s
Interlinking | Calculation of Degree of Connection for CEDICT took 5.841255187988281e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.005242824554443359s
Interlinking | Calculation of Clustering coefficient for CEDICT took 0.00017714500427246094s
Believability | Calculation of trust value for CEDICT took 3.790855407714844e-05s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 104.77709484100342s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 5.9970622062683105s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0018079280853271484s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 25.904871225357056s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.17000603675842285s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.00010967254638671875s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.006466865539550781s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.00046253204345703125s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 3.600120544433594e-05s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 120.93034982681274s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 0.00030517578125s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0018398761749267578s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 27.46846580505371s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.17613554000854492s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 6.270408630371094e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.006959676742553711s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 0.0002167224884033203s
Believability | Calculation of trust value for Pakistan Stock Market Data took 3.9577484130859375e-05s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 194.24649167060852s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 0.0003197193145751953s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.0018794536590576172s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 25.99509024620056s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.1850590705871582s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 6.222724914550781e-05s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.007248401641845703s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 0.000217437744140625s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 3.933906555175781e-05s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 135.91423416137695s
Availability | SPARQL endpoint availability check for Soccer Dataset took 0.0003120899200439453s
Availability | VoID file availability check for Soccer Dataset took 0.0018732547760009766s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 25.324852228164673s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.17169642448425293s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 5.7697296142578125e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.006485700607299805s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 0.00021338462829589844s
Believability | Calculation of trust value for Soccer Dataset took 3.743171691894531e-05s
INFO | --- Analysis for http:www.msm.com took 114.55445313453674s
Availability | SPARQL endpoint availability check for Game Ontology took 0.0003044605255126953s
Availability | VoID file availability check for Game Ontology took 0.0018129348754882812s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.3508162498474121s
Reputation | Calculation of the PageRank for Game Ontology took 0.17260360717773438s
Interlinking | Calculation of Degree of Connection for Game Ontology took 5.5789947509765625e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.006296634674072266s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 0.00017690658569335938s
Believability | Calculation of trust value for Game Ontology took 3.9577484130859375e-05s
INFO | --- Analysis for http:www.RAG.comgameonto# took 150.70445656776428s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0003006458282470703s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0023622512817382812s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 29.33568549156189s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.17801213264465332s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 7.200241088867188e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.007210254669189453s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0002288818359375s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.267692565917969e-05s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 113.38903784751892s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0003743171691894531s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0018277168273925781s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.38106393814086914s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.1732618808746338s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 5.626678466796875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0064411163330078125s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.00021600723266601562s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.695487976074219e-05s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 142.62205529212952s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 0.00030612945556640625s
Availability | VoID file availability check for Indian Biodiversity took 0.0018551349639892578s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.41356587409973145s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.1713712215423584s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 6.031990051269531e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0066983699798583984s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 0.0001819133758544922s
Believability | Calculation of trust value for Indian Biodiversity took 3.528594970703125e-05s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 177.45609188079834s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 0.00030040740966796875s
Availability | VoID file availability check for Indian Biodiversity took 0.0017549991607666016s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.41379427909851074s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.1727142333984375s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 5.7697296142578125e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.006249427795410156s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 0.0004162788391113281s
Believability | Calculation of trust value for Indian Biodiversity took 3.9577484130859375e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 112.85595035552979s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 0.00030159950256347656s
Availability | VoID file availability check for Indian Biodiversity took 0.0022940635681152344s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 28.819411516189575s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.16997957229614258s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 5.650520324707031e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.006250858306884766s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 0.00025773048400878906s
Believability | Calculation of trust value for Indian Biodiversity took 3.719329833984375e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 196.81919240951538s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 0.00031828880310058594s
Availability | VoID file availability check for Indian Biodiversity took 0.0020837783813476562s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.43921661376953125s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.17053484916687012s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 5.4836273193359375e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.006322622299194336s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 0.00020599365234375s
Believability | Calculation of trust value for Indian Biodiversity took 3.790855407714844e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 91.81370639801025s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 0.0003120899200439453s
Availability | VoID file availability check for Indian Biodiversity took 0.0017600059509277344s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.39669322967529297s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.17534136772155762s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 5.9604644775390625e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.005467653274536133s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 0.00012731552124023438s
Believability | Calculation of trust value for Indian Biodiversity took 3.719329833984375e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 59.98520874977112s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0003178119659423828s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.002515554428100586s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.44703149795532227s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.17696595191955566s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.00011348724365234375s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.006310224533081055s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.00011134147644042969s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 3.62396240234375e-05s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 120.19791984558105s
Availability | SPARQL endpoint availability check for Bookkeeping took 1.3178610801696777s
Availability | VoID file availability check for Bookkeeping took 0.002343416213989258s
Completeness | Calculation of interlinking completeness for Bookkeeping took 30.968711376190186s
Reputation | Calculation of the PageRank for Bookkeeping took 0.1731424331665039s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 5.6743621826171875e-05s
Interlinking | Calculation of Centrality for Bookkeeping took 0.006382465362548828s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 0.0001800060272216797s
Believability | Calculation of trust value for Bookkeeping took 3.814697265625e-05s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 119.90614891052246s
Availability | SPARQL endpoint availability check for Legal Ontology took 0.0002982616424560547s
Availability | VoID file availability check for Legal Ontology took 0.0018651485443115234s
Completeness | Calculation of interlinking completeness for Legal Ontology took 27.79536247253418s
Reputation | Calculation of the PageRank for Legal Ontology took 0.17434096336364746s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 5.745887756347656e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.00648808479309082s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 0.0002071857452392578s
Believability | Calculation of trust value for Legal Ontology took 3.910064697265625e-05s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 140.49521160125732s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.00030112266540527344s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0013442039489746094s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 26.980944395065308s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.17182636260986328s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 0.00019812583923339844s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.006123065948486328s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 0.0005993843078613281s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 3.504753112792969e-05s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 110.09123492240906s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 0.0005674362182617188s
Availability | VoID file availability check for Writer Luigi Usai took 0.001999378204345703s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.4279026985168457s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.17092442512512207s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 5.793571472167969e-05s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.006477832794189453s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 0.00022721290588378906s
Believability | Calculation of trust value for Writer Luigi Usai took 3.5762786865234375e-05s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 117.10708999633789s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 0.0015931129455566406s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.0017189979553222656s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.37760353088378906s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.17233610153198242s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 5.9604644775390625e-05s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.006230592727661133s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 0.0001780986785888672s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 3.743171691894531e-05s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 113.2330276966095s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 1.7850630283355713s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.0022897720336914062s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 29.307815551757812s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.1760265827178955s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 7.414817810058594e-05s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.007958173751831055s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 0.0002694129943847656s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 8.797645568847656e-05s
INFO | --- Analysis for hud-library-usagedata took 230.1189901828766s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 0.4701113700866699s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0018372535705566406s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 28.78793454170227s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.17623543739318848s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 6.937980651855469e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.006552219390869141s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.0009377002716064453s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 0.0001442432403564453s
INFO | --- Analysis for hungarian-national-library-catalog took 141.5164976119995s
Availability | SPARQL endpoint availability check for IATE RDF took 0.0003414154052734375s
Availability | VoID file availability check for IATE RDF took 0.002077817916870117s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.37067103385925293s
Reputation | Calculation of the PageRank for IATE RDF took 0.1735975742340088s
Interlinking | Calculation of Degree of Connection for IATE RDF took 5.030632019042969e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0061762332916259766s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 0.0003693103790283203s
Believability | Calculation of trust value for IATE RDF took 3.62396240234375e-05s
INFO | --- Analysis for iate-rdf took 145.7124252319336s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.571547508239746s
Availability | VoID file availability check for IATI as Linked Data took 0.0021507740020751953s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.3796868324279785s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.17302560806274414s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 6.079673767089844e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.005293607711791992s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 0.0006148815155029297s
Believability | Calculation of trust value for IATI as Linked Data took 3.528594970703125e-05s
INFO | --- Analysis for iati-as-linked-data took 103.11838006973267s
Availability | SPARQL endpoint availability check for ICANE took 0.30162549018859863s
Availability | VoID file availability check for ICANE took 0.0018627643585205078s
Completeness | Calculation of interlinking completeness for ICANE took 29.800798177719116s
Reputation | Calculation of the PageRank for ICANE took 0.17819809913635254s
Interlinking | Calculation of Degree of Connection for ICANE took 7.677078247070312e-05s
Interlinking | Calculation of Centrality for ICANE took 0.006200075149536133s
Interlinking | Calculation of Clustering coefficient for ICANE took 0.0007431507110595703s
Believability | Calculation of trust value for ICANE took 3.24249267578125e-05s
INFO | --- Analysis for icane took 181.57871270179749s
Availability | SPARQL endpoint availability check for ichoose took 0.15702438354492188s
Availability | VoID file availability check for ichoose took 0.0018391609191894531s
Completeness | Calculation of interlinking completeness for ichoose took 29.053354501724243s
Reputation | Calculation of the PageRank for ichoose took 0.19729399681091309s
Interlinking | Calculation of Degree of Connection for ichoose took 0.0001220703125s
Interlinking | Calculation of Centrality for ichoose took 0.007840394973754883s
Interlinking | Calculation of Clustering coefficient for ichoose took 0.00036597251892089844s
Believability | Calculation of trust value for ichoose took 3.933906555175781e-05s
INFO | --- Analysis for ichoose took 161.73860144615173s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 0.783937931060791s
Availability | VoID file availability check for The Iconology Dataset took 0.002435922622680664s
Extra | Recovery of all triples for The Iconology Dataset took 5.477511167526245s
Performance | Total latancy measurement for The Iconology Dataset took 0.5839500427246094s
Amount of data | Number of triples check for The Iconology Dataset took 0.276702880859375s
Interoperability | New terms check for The Iconology Dataset took 8.367079496383667s
Versatility | Languages check for The Iconology Dataset took 0.6631405353546143s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.22137212753295898s
Interpretability | RDF structures check for The Iconology Dataset took 0.1554720401763916s
Versatility | Serialization formats check for The Iconology Dataset took 0.12692713737487793s
Availability | RDF dump link check for The Iconology Dataset took 0.10581731796264648s
License | MR license check for The Iconology Dataset took 0.14397811889648438s
License | HR license check for The Iconology Dataset took 0.3987724781036377s
Amount of data | Number of property check for The Iconology Dataset took 0.12458229064941406s
Understandability | Number of label check for The Iconology Dataset took 0.1643662452697754s
Understandability | URI regex check for The Iconology Dataset took 0.2015366554260254s
Understandability | Vocabs check for The Iconology Dataset took 0.11199831962585449s
Verifiability | Authors check for The Iconology Dataset took 0.17529988288879395s
Verifiability | Publishers check for The Iconology Dataset took 0.1055138111114502s
Performance | Throughput check for The Iconology Dataset took 10.501993656158447s
Amount of data | Check the number of entities for The Iconology Dataset took 0.0003218650817871094s
Verifiability | Contribs. check for The Iconology Dataset took 0.10570049285888672s
Interlinking | sameAs chians check for The Iconology Dataset took 0.11678695678710938s
Interlinking | skos check for The Iconology Dataset took 0.11063766479492188s
Interlinking | skos check for The Iconology Dataset took 0.10816669464111328s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.12032699584960938s
Currency | Creation date check for The Iconology Dataset took 0.21771645545959473s
Currency | Modification date check for The Iconology Dataset took 0.22021055221557617s
Rep.Conc. | URIs length for The Iconology Dataset took 5.463236570358276s
Interoperability | New vocabularies check for The Iconology Dataset took 2.1457672119140625e-05s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.09769034385681152s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.5022532939910889s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.14105749130249023s
Accuracy | Check Datatype consistency for The Iconology Dataset took 3.6257975101470947s
Consistency | Disjoint class check for The Iconology Dataset took 0.0977785587310791s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.19117212295532227s
Consistency | Misplaced classes for The Iconology Dataset took 6.3828654289245605s
Consistency | Check Ontology hijacking for The Iconology Dataset took 8.443928718566895s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 7.981730222702026s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 8.057082653045654s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 2.3149023056030273s
Security | Sign check for The Iconology Dataset took 0.10151076316833496s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 6019.749525785446s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 0.8284099102020264s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.17650771141052246s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 0.0006630420684814453s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.006457805633544922s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 0.00036787986755371094s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 1.1682510375976562e-05s
Believability | Calculation of trust value for The Iconology Dataset took 3.838539123535156e-05s
INFO | --- Analysis for iconology-dataset took 6215.952701091766s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 0.0003094673156738281s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0021219253540039062s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 33.14597201347351s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.17433834075927734s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 6.222724914550781e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.007069826126098633s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 0.0007126331329345703s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 3.7670135498046875e-05s
INFO | --- Analysis for idreffr took 203.95951414108276s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 1.715876817703247s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0018486976623535156s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 30.39678382873535s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.1721484661102295s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 9.369850158691406e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.006300449371337891s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 0.0003197193145751953s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 3.647804260253906e-05s
INFO | --- Analysis for ids took 175.40143299102783s
Availability | SPARQL endpoint availability check for ietflang took 0.0004572868347167969s
Availability | VoID file availability check for ietflang took 0.0015175342559814453s
Completeness | Calculation of interlinking completeness for ietflang took 28.225783109664917s
Reputation | Calculation of the PageRank for ietflang took 0.17121291160583496s
Interlinking | Calculation of Degree of Connection for ietflang took 5.6743621826171875e-05s
Interlinking | Calculation of Centrality for ietflang took 0.006391763687133789s
Interlinking | Calculation of Clustering coefficient for ietflang took 0.00031828880310058594s
Believability | Calculation of trust value for ietflang took 3.790855407714844e-05s
INFO | --- Analysis for ietflang took 196.04704666137695s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.6182336807250977s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.002229452133178711s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 29.68109393119812s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.174574613571167s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 8.726119995117188e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.00488591194152832s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 0.0002486705780029297s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 4.00543212890625e-05s
INFO | --- Analysis for IGVLL took 96.35154867172241s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.5120441913604736s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0020036697387695312s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.486511468887329s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 4.947287321090698s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 1.078099012374878s
Interoperability | New terms check for 3LGM² IHE Ontology took 8.36902403831482s
Versatility | Languages check for 3LGM² IHE Ontology took 0.24794983863830566s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.20798277854919434s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.26996350288391113s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.21824932098388672s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.21497273445129395s
License | MR license check for 3LGM² IHE Ontology took 0.23431849479675293s
License | HR license check for 3LGM² IHE Ontology took 0.22582030296325684s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.1951291561126709s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.2200181484222412s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.40735769271850586s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.21777844429016113s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.22500371932983398s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.20824122428894043s
Performance | Throughput check for 3LGM² IHE Ontology took 10.679482221603394s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 0.0002548694610595703s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.20229196548461914s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.21535444259643555s
Interlinking | skos check for 3LGM² IHE Ontology took 0.2173171043395996s
Interlinking | skos check for 3LGM² IHE Ontology took 0.19540905952453613s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.22122836112976074s
Currency | Creation date check for 3LGM² IHE Ontology took 0.41654443740844727s
Currency | Modification date check for 3LGM² IHE Ontology took 0.4189901351928711s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 1.2522835731506348s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 1.3113021850585938e-05s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.20814180374145508s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.20159482955932617s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.20682120323181152s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.3757660388946533s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.014026880264282227s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.3981189727783203s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.21519827842712402s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.5238008499145508s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.8385443687438965s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 8.305397272109985s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 7.911792755126953s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 9.461568593978882s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.22109317779541016s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.19516277313232422s
Security | Sign check for 3LGM² IHE Ontology took 0.21916484832763672s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 731.402455329895s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 28.876766204833984s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.17720293998718262s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 5.340576171875e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.006169319152832031s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 0.0004267692565917969s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.1682510375976562e-05s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 3.743171691894531e-05s
INFO | --- Analysis for IHE took 991.7661345005035s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 5.1383585929870605s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.002351522445678711s
Extra | Recovery of all triples for Test Site, LOD Lab 317 took 6.912303924560547s
Performance | Total latancy measurement for Test Site, LOD Lab 317 took 13.888751029968262s
Amount of data | Number of triples check for Test Site, LOD Lab 317 took 20.81066370010376s
Interoperability | New terms check for Test Site, LOD Lab 317 took 15.311547756195068s
Versatility | Languages check for Test Site, LOD Lab 317 took 62.93480038642883s
Interpretability | Number of blank nodes check for Test Site, LOD Lab 317 took 5.098877668380737s
Security | Check HTTPS for Test Site, LOD Lab 317 took 2.2287051677703857s
Interpretability | RDF structures check for Test Site, LOD Lab 317 took 2.849490165710449s
Versatility | Serialization formats check for Test Site, LOD Lab 317 took 1.969043254852295s
Availability | RDF dump link check for Test Site, LOD Lab 317 took 1.9534974098205566s
License | MR license check for Test Site, LOD Lab 317 took 1.9800891876220703s
License | HR license check for Test Site, LOD Lab 317 took 3.2252426147460938s
Amount of data | Number of property check for Test Site, LOD Lab 317 took 2.936058521270752s
Understandability | Number of label check for Test Site, LOD Lab 317 took 3.626112461090088s
Understandability | URI regex check for Test Site, LOD Lab 317 took 3.8552229404449463s
Understandability | Vocabs check for Test Site, LOD Lab 317 took 1.9739935398101807s
Verifiability | Authors check for Test Site, LOD Lab 317 took 1.9925222396850586s
Verifiability | Publishers check for Test Site, LOD Lab 317 took 3.026492118835449s
Performance | Throughput check for Test Site, LOD Lab 317 took 28.817967414855957s
Amount of data | Check the number of entities for Test Site, LOD Lab 317 took 0.00025463104248046875s
Verifiability | Contribs. check for Test Site, LOD Lab 317 took 2.955677032470703s
Interlinking | sameAs chians check for Test Site, LOD Lab 317 took 2.8216874599456787s
Interlinking | skos check for Test Site, LOD Lab 317 took 2.9258460998535156s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.9984800815582275s
Timeliness | dataset update frequency check for Test Site, LOD Lab 317 took 1.8838529586791992s
Currency | Creation date check for Test Site, LOD Lab 317 took 4.811671257019043s
Currency | Modification date check for Test Site, LOD Lab 317 took 5.751234531402588s
Rep.Conc. | URIs length for Test Site, LOD Lab 317 took 40.72594904899597s
Interoperability | New vocabularies check for Test Site, LOD Lab 317 took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Test Site, LOD Lab 317 took 1.9766101837158203s
Accuracy | Check Functional Property for Test Site, LOD Lab 317 took 1.9730992317199707s
Accuracy | Check Inverse Functional Property for Test Site, LOD Lab 317 took 2.853163957595825s
Consistency | Disjoint class check for Test Site, LOD Lab 317 took 1.9079911708831787s
Consistency | Check Misplaced properties for Test Site, LOD Lab 317 took 30.296715021133423s
Consistency | Misplaced classes for Test Site, LOD Lab 317 took 3.6259658336639404s
Consistency | Check Ontology hijacking for Test Site, LOD Lab 317 took 3.7127623558044434s
Consistency | Check Invalid usage of undefined properties for Test Site, LOD Lab 317 took 32.54552173614502s
Conciseness | Check Extensional conciseness for Test Site, LOD Lab 317 took 0.0007128715515136719s
Conciseness | Check Intensional conciseness for Test Site, LOD Lab 317 took 6.59929895401001s
Security | Sign check for Test Site, LOD Lab 317 took 2.863717794418335s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 28.07769227027893s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.1897444725036621s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 0.0001327991485595703s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.007447481155395508s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 0.00023055076599121094s
Interoperability | Check the re-using of existing vocabs for Test Site, LOD Lab 317 took 1.049041748046875e-05s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 3.743171691894531e-05s
INFO | --- Analysis for iislod-test took 861.7515597343445s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 0.0004630088806152344s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.002067089080810547s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 30.910488605499268s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.17263507843017578s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 0.00010204315185546875s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0061359405517578125s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 0.00019788742065429688s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 0.00022077560424804688s
INFO | --- Analysis for ILUSOC took 196.71298265457153s
Availability | SPARQL endpoint availability check for im@sparql took 6.393466234207153s
Availability | VoID file availability check for im@sparql took 0.0021986961364746094s
Completeness | Calculation of interlinking completeness for im@sparql took 0.35959696769714355s
Reputation | Calculation of the PageRank for im@sparql took 0.1760547161102295s
Interlinking | Calculation of Degree of Connection for im@sparql took 6.008148193359375e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0067255496978759766s
Interlinking | Calculation of Clustering coefficient for im@sparql took 0.00018310546875s
Believability | Calculation of trust value for im@sparql took 3.695487976074219e-05s
INFO | --- Analysis for im@sparql took 94.64203429222107s
Availability | SPARQL endpoint availability check for imagery bailingniao took 0.0003306865692138672s
Availability | VoID file availability check for imagery bailingniao took 0.002224445343017578s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.4434678554534912s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.18025636672973633s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 6.29425048828125e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.006812572479248047s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 0.00018262863159179688s
Believability | Calculation of trust value for imagery bailingniao took 3.743171691894531e-05s
INFO | --- Analysis for imagery_bailingniao took 62.34669041633606s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.1603851318359375s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0020439624786376953s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 40.49019193649292s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.5898945331573486s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 9.772150039672852s
Interoperability | New terms check for Imagesnippets Image Descriptions took 10.78721022605896s
Versatility | Languages check for Imagesnippets Image Descriptions took 19.477842330932617s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 8.632906913757324s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.7203505039215088s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7855720520019531s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.714181661605835s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7688536643981934s
License | MR license check for Imagesnippets Image Descriptions took 0.7318079471588135s
License | HR license check for Imagesnippets Image Descriptions took 30.74747896194458s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.7502422332763672s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.555665969848633s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.4426486492156982s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.7402939796447754s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.738335132598877s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.7552676200866699s
Performance | Throughput check for Imagesnippets Image Descriptions took 14.283957242965698s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 0.0002548694610595703s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.7106521129608154s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.7325232028961182s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7486793994903564s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7031662464141846s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.7376489639282227s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.489375114440918s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.4469811916351318s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 106.20374989509583s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 3.62396240234375e-05s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.7352824211120605s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.7481133937835693s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.7635300159454346s
Accuracy | Check Empty annotation labels for Imagesnippets Image Descriptions took 38.825610637664795s
Accuracy | Check White space in annotation for Imagesnippets Image Descriptions took 18.369971752166748s
Accuracy | Check Datatype consistency for Imagesnippets Image Descriptions took 34.796517848968506s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.7166340351104736s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 8.074432134628296s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 14.827762603759766s
Consistency | Check Invalid usage of undefined classes for Imagesnippets Image Descriptions took 8.554022550582886s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 15.516668558120728s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 23.311312437057495s
Security | Sign check for Imagesnippets Image Descriptions took 0.7487797737121582s
Availability | Check URIs Dereferenciability for Imagesnippets Image Descriptions took 15.612101316452026s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.48839402198791504s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.17747783660888672s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 9.226799011230469e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.006396770477294922s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 0.0007371902465820312s
Interoperability | Check the re-using of existing vocabs for Imagesnippets Image Descriptions took 1.1444091796875e-05s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 3.981590270996094e-05s
INFO | --- Analysis for imagesnippets took 642.6805686950684s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.1137228012084961s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0012104511260986328s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.3531510829925537s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.17662262916564941s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 6.341934204101562e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.006720542907714844s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 0.0007100105285644531s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 3.790855407714844e-05s
INFO | --- Analysis for imf-linked-data took 188.31753611564636s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 0.0004336833953857422s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0019304752349853516s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 29.281347513198853s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.1715095043182373s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 8.821487426757812e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.006468772888183594s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 6.4849853515625e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 3.647804260253906e-05s
INFO | --- Analysis for Imtiaz took 120.87990188598633s
Availability | SPARQL endpoint availability check for Royalty Free Music took 0.0004832744598388672s
Availability | VoID file availability check for Royalty Free Music took 0.0021119117736816406s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.42122530937194824s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.16927003860473633s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 8.96453857421875e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.006182432174682617s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 0.0001704692840576172s
Believability | Calculation of trust value for Royalty Free Music took 4.0531158447265625e-05s
INFO | --- Analysis for inaudio.org took 34.831809759140015s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.6506853103637695s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0021932125091552734s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 30.35733151435852s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.1744368076324463s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 6.103515625e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.006314277648925781s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 0.0002532005310058594s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 3.504753112792969e-05s
INFO | --- Analysis for IndexThomisticusTreebank took 181.83019495010376s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0013959407806396484s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0016977787017822266s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 27.14883255958557s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.17307543754577637s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 5.9604644775390625e-05s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.006275653839111328s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.00017952919006347656s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 3.838539123535156e-05s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 154.04911041259766s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.00033402442932128906s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0029044151306152344s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.38402724266052246s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.17353105545043945s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 6.222724914550781e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.006731748580932617s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.0007932186126708984s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 3.695487976074219e-05s
INFO | --- Analysis for ineverycrea took 138.22776699066162s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0004105567932128906s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0024008750915527344s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 29.085726737976074s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.17467951774597168s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.799003601074219e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.006675004959106445s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007898807525634766s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 4.935264587402344e-05s
INFO | --- Analysis for ineverycrea-argentina took 216.47919082641602s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 271.0734326839447s
Availability | VoID file availability check for Influence Tracker Dataset took 0.002460002899169922s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 26.912251949310303s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.17258191108703613s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 0.00015807151794433594s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.006565570831298828s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 0.0005283355712890625s
Believability | Calculation of trust value for Influence Tracker Dataset took 3.695487976074219e-05s
INFO | --- Analysis for influence-tracker-dataset took 938.3671855926514s
Availability | SPARQL endpoint availability check for INSEMTIVES took 0.0002906322479248047s
Availability | VoID file availability check for INSEMTIVES took 0.0017542839050292969s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 25.777320384979248s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.18132972717285156s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 6.67572021484375e-05s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.007611274719238281s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 0.00021767616271972656s
Believability | Calculation of trust value for INSEMTIVES took 3.910064697265625e-05s
INFO | --- Analysis for insemtives took 56.790685415267944s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 0.0003027915954589844s
Availability | VoID file availability check for Instance Hub Countries took 0.0019576549530029297s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 28.29539728164673s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.1730976104736328s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 9.775161743164062e-05s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0062067508697509766s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 0.00017595291137695312s
Believability | Calculation of trust value for Instance Hub Countries took 3.743171691894531e-05s
INFO | --- Analysis for instance-hub-countries took 202.9979965686798s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 0.00034165382385253906s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.001710653305053711s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 27.061471939086914s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.17466259002685547s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 6.270408630371094e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0059015750885009766s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 0.000179290771484375s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 3.838539123535156e-05s
INFO | --- Analysis for instance-hub-fiscal-years took 233.7312581539154s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 0.00029730796813964844s
Availability | VoID file availability check for Instance Hub Organizations took 0.0016932487487792969s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.3875720500946045s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.16892504692077637s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 5.841255187988281e-05s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0064775943756103516s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 0.0002071857452392578s
Believability | Calculation of trust value for Instance Hub Organizations took 8.320808410644531e-05s
INFO | --- Analysis for instance-hub-organizations took 202.97489666938782s
Availability | SPARQL endpoint availability check for Instance Hub People took 0.0001697540283203125s
Availability | VoID file availability check for Instance Hub People took 0.0017764568328857422s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.43615150451660156s
Reputation | Calculation of the PageRank for Instance Hub People took 0.17495012283325195s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 6.151199340820312e-05s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0066661834716796875s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 0.00018835067749023438s
Believability | Calculation of trust value for Instance Hub People took 4.00543212890625e-05s
INFO | --- Analysis for instance-hub-people took 123.51557874679565s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 0.0003361701965332031s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.0018036365509033203s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 28.36650800704956s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.17243528366088867s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 5.91278076171875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.006337881088256836s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 0.000244140625s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 3.790855407714844e-05s
INFO | --- Analysis for instance-hub-us-civil-servants took 229.25331354141235s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 0.0003025531768798828s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.0017685890197753906s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 37.048290967941284s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.17331957817077637s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 5.6743621826171875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.007132053375244141s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 0.0001800060272216797s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 3.981590270996094e-05s
INFO | --- Analysis for instance-hub-us-congressional-committees took 133.3114411830902s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 0.00032901763916015625s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.002315998077392578s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 27.909846782684326s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.17368292808532715s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 9.870529174804688e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.007455348968505859s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 0.0001857280731201172s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 3.9577484130859375e-05s
INFO | --- Analysis for instance-hub-us-congressional-districts took 257.0096478462219s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 0.00034689903259277344s
Availability | VoID file availability check for Instance Hub US Crops took 0.0019533634185791016s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.38091039657592773s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.17179560661315918s
Interlinking | Calculation of Degree of Connection for Instance Hub US Crops took 6.914138793945312e-05s
Interlinking | Calculation of Centrality for Instance Hub US Crops took 0.006316661834716797s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 0.00017213821411132812s
Believability | Calculation of trust value for Instance Hub US Crops took 3.8623809814453125e-05s
INFO | --- Analysis for instance-hub-us-crops took 94.31511974334717s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 0.00030517578125s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.0017914772033691406s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 33.394166469573975s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.17150521278381348s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 9.226799011230469e-05s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.006330251693725586s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 0.00022029876708984375s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 3.62396240234375e-05s
INFO | --- Analysis for instance-hub-us-federal-agencies took 198.7195029258728s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 0.00033164024353027344s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.0017409324645996094s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 31.666855335235596s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.17683100700378418s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 0.0001220703125s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.006593942642211914s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 0.0002300739288330078s
Believability | Calculation of trust value for Instance Hub US States and Territories took 5.412101745605469e-05s
INFO | --- Analysis for instance-hub-us-states-and-territories took 297.78650999069214s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 0.00020241737365722656s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.0017690658569335938s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 34.84001183509827s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.17500734329223633s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 5.984306335449219e-05s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.006394863128662109s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 0.00017404556274414062s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 5.0067901611328125e-05s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 231.8042368888855s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 20.807045221328735s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.003611326217651367s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 32.8334596157074s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.17516469955444336s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.00011229515075683594s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.008112668991088867s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.00020837783813476562s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 3.886222839355469e-05s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 293.6292607784271s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00030732154846191406s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.5310351848602295s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.4029664993286133s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.17557501792907715s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 5.7697296142578125e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.006346225738525391s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0004367828369140625s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 3.9577484130859375e-05s
INFO | --- Analysis for interactivemaps-gnoss took 217.34473204612732s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 0.9318192005157471s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.0021758079528808594s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 32.34668684005737s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.18395137786865234s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 5.698204040527344e-05s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.006182432174682617s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 0.0002493858337402344s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 5.555152893066406e-05s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 296.33367896080017s
Availability | SPARQL endpoint availability check for intervalue took 0.14073681831359863s
Availability | VoID file availability check for intervalue took 0.0018153190612792969s
Completeness | Calculation of interlinking completeness for intervalue took 33.486098527908325s
Reputation | Calculation of the PageRank for intervalue took 0.17579960823059082s
Interlinking | Calculation of Degree of Connection for intervalue took 5.793571472167969e-05s
Interlinking | Calculation of Centrality for intervalue took 0.006680727005004883s
Interlinking | Calculation of Clustering coefficient for intervalue took 0.000522613525390625s
Believability | Calculation of trust value for intervalue took 3.790855407714844e-05s
INFO | --- Analysis for intervalue took 207.98190569877625s
Availability | SPARQL endpoint availability check for Inztrow took 0.0003032684326171875s
Availability | VoID file availability check for Inztrow took 0.0023736953735351562s
Completeness | Calculation of interlinking completeness for Inztrow took 0.3459506034851074s
Reputation | Calculation of the PageRank for Inztrow took 0.17376947402954102s
Interlinking | Calculation of Degree of Connection for Inztrow took 5.936622619628906e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.006856203079223633s
Interlinking | Calculation of Clustering coefficient for Inztrow took 0.00018310546875s
Believability | Calculation of trust value for Inztrow took 3.743171691894531e-05s
INFO | --- Analysis for Inztrow took 135.19558548927307s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 0.0004260540008544922s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0025238990783691406s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 35.71090340614319s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.17388677597045898s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 6.651878356933594e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.007478952407836914s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 0.00020003318786621094s
Believability | Calculation of trust value for IPBES Assessments Ontology took 6.389617919921875e-05s
INFO | --- Analysis for ipbes took 282.6524701118469s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 0.0002925395965576172s
Availability | VoID file availability check for IPTC NewsCodes took 0.0021102428436279297s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.39000797271728516s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.17269301414489746s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 9.131431579589844e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.006587505340576172s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 0.00030422210693359375s
Believability | Calculation of trust value for IPTC NewsCodes took 3.790855407714844e-05s
INFO | --- Analysis for iptc-newscodes took 262.51317143440247s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 2.5007565021514893s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.002038717269897461s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 35.40866661071777s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.17698097229003906s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 5.7220458984375e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0061893463134765625s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 0.0008127689361572266s
Believability | Calculation of trust value for iServe: Linked Services Registry took 4.744529724121094e-05s
INFO | --- Analysis for iserve took 149.41283464431763s
Availability | SPARQL endpoint availability check for ISIC V4 took 21.130173683166504s
Availability | VoID file availability check for ISIC V4 took 0.0027298927307128906s
Completeness | Calculation of interlinking completeness for ISIC V4 took 35.508315086364746s
Reputation | Calculation of the PageRank for ISIC V4 took 0.17457914352416992s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 6.318092346191406e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.006616115570068359s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 0.00031280517578125s
Believability | Calculation of trust value for ISIC V4 took 3.0994415283203125e-05s
INFO | --- Analysis for isic-v4 took 259.3150517940521s
Availability | SPARQL endpoint availability check for Isidore took 0.0003075599670410156s
Availability | VoID file availability check for Isidore took 0.0019006729125976562s
Completeness | Calculation of interlinking completeness for Isidore took 2.0874598026275635s
Reputation | Calculation of the PageRank for Isidore took 0.17563748359680176s
Interlinking | Calculation of Degree of Connection for Isidore took 6.103515625e-05s
Interlinking | Calculation of Centrality for Isidore took 0.006681203842163086s
Interlinking | Calculation of Clustering coefficient for Isidore took 0.0001838207244873047s
Believability | Calculation of trust value for Isidore took 2.2411346435546875e-05s
INFO | --- Analysis for isidore took 151.97723817825317s
